Preservation plan detail

The preservation plan detail shows its information grouped by sections. In the General Information section, the system shows name, preservation area to which it is assigned, date of creation, status (active / inactive), automatic audit schema (if assigned) and the type of preservation plan (ingestion / evolution).

The creation of a preservation plan based on the detail is also an option.

The Metadata section shows the metadata schema selected, as well as its import filter. It also shows the associated metadata import filter parameters and their values applied to the preservation plan.

In the associated Thumbnail section, the system shows the configured regular expression with which we will try to locate an image, to generate the icon of the object.

In the Storage section, the system shows the storage groups configured for the preservation plan, together with the assigned read and write priorities.

The Sanitizers section shows configured sanitizers, grouped by their scope of application. Of each sanitizer, we can see name, parameters and access to the sanitizer detail.

In the Preprocessors section, these are shown organized by their order of execution (preprocessors are susceptible of producing different results on the ingestion job if the order of execution is altered). Of each one, the system shows name, order of execution, parameters and access to the preprocessor detail.

The Checks section shows configured ingestion checks, grouped by their scope of application. For each one, we can see name, Regex pattern (regular expression to facilitate selection), parameters and access to the ingestion check detail.

The Characterizers section shows the characterizers configured for the preservation plan. Of each one, the system shows name, description, priority (it sets the order of execution of the characterizers, in case it is not possible to identify the format of some file, and they will be executed in that order) and access to the characterizer detail.

It also shows whether the selection referred that the characterization be mandatory (if marked as mandatory, an ingestion job will fail if after characterization there is at least one file that has not been able to be identified).

The Validators section shows all the file format validators that have been configured. Of each one, the system shows name, description, UID identifier, priority (it sets the order of execution of the validators, in case we have configured more than one for the same file format), mandatory validator (it specifically indicates whether that file format validator should validate all the files to be processed, respecting the priority of execution established), and access to the validator detail.

The File format transformers section lists the transformers (evolvers applied in the ingestion process) configured in the preservation plan. These transformers will be in charge of transforming files with one specific file format into another one, giving data contained in the transformed file a new container (with a healthier file format).

Of each one, we can see name, UID identifier at origin (file format the file has to have to be transformed), UID identifier at destination (file format into which it has to be transformed) regex expression (regular expression to facilitate file selection), priority (in case there is more than one transformer for the same configured file format, it will indicate the order of execution), whether we need to keep the original file after transformation, whether it is mandatory (a failure in the execution of a file transformation will cause the job to end with error), and access to the transformer detail.

The ‘Digital signature’ section shows the digital signature profiles configured for the preservation plan. They set the signature configuration to be applied to the objects. Of each one, the system shows name, description, status and access to the digital signature profile detail.

Last, the Rollback section shows if the repeal of the changes made on the objects was selected, in case the ingestion job is restarted.

Note: it is recommended to mark the repeal of changes, if preprocessors or file format transformers have been configured.