LogoLogo
  • LIBSAFE Advanced Pro - Preservation Administrator Manual
  • System configuration
  • Preservation configuration, basic sections
    • Ingestion sanitizers
      • Ingestion sanitizers detail
      • Ingestion sanitizer editing
    • Preprocessors
      • Preprocessor detail
      • Creation of the preprocessor
      • Preprocessor editing
    • Ingestion checks
      • Ingestion check detail
      • Creation of the ingestion check
      • Ingestion check editing
      • Main ingestion checks
    • Metadata filters
      • Metadata filter detail
      • Metadata filter creation
      • Metadata filter editing
    • Dissemination Information Package (DIP) profiles
      • DIP profile detail
      • Creation of DIP profiles
      • DIP profile edition
    • Connectors
      • Connector Activation
      • Connector details
    • File formats
      • File format detail
    • File format characterizers
      • File format characterizer detail
    • File format validators
      • File format validator detail
    • File format evolvers
      • File format evolver detail
    • Automatic audit schemas
      • Automatic audit schema detail
      • Automatic audit schema editing
  • Metadata collision groups
    • Unicity metadata collision groups
      • Unicity metadata collision group detail
      • Creation of a unicity metadata collision group
      • Unicity metadata collision group editing
    • Versioning metadata collision groups
      • Versioning metadata collision group detail
      • Creation of a versioning metadata collision group
      • Versioning metadata collision group editing
  • Metadata schemas
    • Metadata schema detail
    • Creation of a metadata schema
    • Metadata schema editing
  • Collection tree
  • Dissemination Information Package (DIP) configured profiles
    • Detail of the DIP profile configured for preservation plans
    • Configuring a new DIP profile for preservation plans
    • Editing DIP profiles configured for preservation plans
  • Preservation areas
    • Preservation area detail
    • Create a preservation area
    • Preservation area editing
  • Preservation plans
    • Preservation plan detail
    • Preservation plan creation
      • Preservation area and plan parameters
      • Metadata
      • Associated thumbnail
      • Storage
      • Sanitizers
      • Preprocessors
      • Checks
      • File format characterizers
      • File format validators
      • File format transformers
      • Digital signature
      • Rollback
      • Data Integrity
  • Alarms and notifications
    • Alarm definition
    • Configured alarms
      • Configuring an alarm: example 1
      • Configuring an alarm: example 2
    • Notifications panel
  • Glossary of Terms
  • Frequently asked Questions and additional considerations
    • About ingestion and retrieval
    • About audit
    • Miscellaneous
  • Annexes
    • Automatic ingestion and retrieval processes
      • Automatic ingestion
      • Automatic retrieval
    • Regex expressions – User reference
    • List of error messages found in audits (log)
Powered by GitBook
On this page

Was this helpful?

  1. Preservation plans
  2. Preservation plan creation

File format transformers

PreviousFile format validatorsNextDigital signature

Last updated 3 years ago

Was this helpful?

Transformers are processes that evolve files from one file format to another before preserving the objects.

Note: to select transformers and relate them to the preservation plan, we must previously have associated some characterizer to the preservation plan.

Transformers are configured by file format. The files of which file format has been identified in the characterization and matched with those configured in the transformers will be evolved.

We have to configure the following parameters for every transformer:

  • Regular expression: to facilitate file selection or to filter to apply only to one subgroup. If left by default, it will affect every file.

  • Priority: it indicates the order of execution of the evolution process, should there be more than one evolver. Contingent upon the configuration of the evolver parameters, a different execution priority may produce different results in the ingestion job.

  • Keep the original: by default, original files are deleted after the file transformation in order to keep the most updated one and save physical space. If we also want to keep the original files transformed by the evolver, we must mark this option.

  • Mandatory: if we mark this option, an ingestion job will end with error if the transformer could not transform a file (the execution will end with error).

Note: it is recommended that later on in the creation of the preservation plan, we mark the ‘repeal changes’ option if we configure any transformer.