User type: archivist

Preservation policies define how the technical preservation of PIA should be carried out to ensure the intellectual permanence of PIA, as well as to ensure the authenticity, integrity, reliability and availability of electronic archival documents over time. In addition to its definition, it also controls its execution.

Includes the following strategies o preservation operations

  • Migration: This policy allows the transformation o of an electronic archive document into a certain format a a more well-known, stable o standardized format, while preserving the integrity of the content of the corresponding document i ensuring its correct consultation i visualization in the future. In the following document you will find the formats that can be migrated i the possible migration formats ( <a href="https://www.aoc.cat/wp-content/uploads/2020/04/llistat_formats_migracio_iarxiu_20200409.xlsx" target="_blank" rel="noopener noreferrer"> excel )
  • Consistency: L'the objective is to periodically verify that the PIAs maintain their integrity for the entire time they remain a iARCHIU. The way to do-this is to verify that the cryptographic summary of the digital objects obtained at the time of their entry is the same as the one calculated when executing the policy.

A preservation policy defines:

  • A preservation operation
  • A selection criterion
  • Dates on which that policy is executed

High preservation policy

To register a new policy l'user must click a "Add" within l'section "Maintenance of preservation policies".

Maintaining preservation policies

The a fields to report are the following:

  • Identification data:
    • All packages in the fund
    • Sdocumentary series (listed with registered documentary series)
  • Descriptive data:
    • Policy name
    • Policy description
    • TAAD code
    • Reason for the policy i email a who will be notified when the policy is going to be a proceed a l'execution.
  • Action a perform. Choose one of the following:
    • Migration
      • Indication of source format i destination format
    • Consistency (integrity check)
  • Policy execution:
    • Execution start date.
    • Execution frequency (in years, months o days)
Fields a report

Once all the fields on the previous screen have been filled in i and it has been verified that there are no errors, the policy is registered a on the platform.

Additionally, the system will associate a unique identifier for each policy.

The creation of technical policies allows you to indicate a documentary series o an entire collection. If a series has a specific policy, then the policy specified for the collection will not apply to it. a That is, the policy with the series identifier takes precedence over the collection identifier.

New policy created

Political modification

Modifying a policy allows a l'archiver to modify all the data in a policy.

Policy activation/deactivation

L'activating/deactivating policies allows a l'archiver to start o stop a certain policy. Active policies create the tasks i corresponding operations, i inactive policies do not execute any action, but their data can be consulted.

Check executions

The query of executions i results allows a l'archiver to see which executions of the policy have been, sorted from most recent a to oldest. To check which PIAs have been affected by l'application of the policy, it is necessary to consult the action log.

The data shown in the query for each of the policy executions is as follows:

  • l'execution start time
  • l'execution end time
  • Result of l'execution. The possible states are:
    • Correct
    • Error
    • Execution in progress
  • Number of affected packages o processed during l execution

Political elimination

This option allows you to delete a policy.

Note: it should be noted that l'deleting a policy does not imply that the executions made of the policy before its deletion are “restored”.