LogoLogo
  • LIBSAFE Advanced Pro - System Administrator Manual
  • Introduction
    • Basic concepts
    • General considerations
  • System configuration
    • Storage
      • Storage groups
      • Disks
        • Different storage system types and their integration in LIBSAFE
      • Datamover
    • Digital signature profiles
      • Certificates for the digital signature service
    • Access
      • Users
        • Two-Factor Authentication (2FA)
      • Groups
      • User permissions
    • Alarms and Notifications
      • Alarm definition
      • Configured alarms
        • Configuring an alarm: example 1
        • Configuring an alarm: example 2
      • Notifications panel
    • Extras and tools
      • Programmed tasks
      • Logs manager
      • File management
      • Database management
      • Database management (read-only mode)
      • Web interface configuration variables
      • Configuration variables
      • API system services
      • Server cluster - Parallelization
        • Details of activity in one node
        • Editing or creating a node and its associated services
        • Node deactivation
        • Deleting nodes
        • Processing Cluster customization
      • SAML integration as a SSO (Single Sign On) when login in LIBSAFE
    • License
  • Preservation configuration
    • Ingestion sanitizers
      • Ingestion sanitizers detail
      • Ingestion sanitizer editing
    • Preprocessors
      • Preprocessor details
      • Creation of the preprocessor
      • Preprocessor editing
    • Ingestion checks
      • Ingestion check details
      • Creation of the ingestion check
      • Ingestion check editing
      • Main ingestion checks
    • Metadata filters
      • Metadata filter detail
      • Creation of metadata filter
      • Metadata filter editing
    • Dissemination Information Package (DIP) profiles
      • DIP profile detail
      • Creation of DIP profiles
      • DIP profile edition
    • Connectors
      • Connector Detail
      • Create a new connector
      • Edit a connector
    • 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
  • Frequently Asked Questions (FAQ) and additional notes
Powered by GitBook
On this page

Was this helpful?

  1. Preservation configuration

File format validators

PreviousFile format characterizer detailNextFile format validator detail

Last updated 3 years ago

Was this helpful?

File format validators are the modules used to validate that the files identified (with the characterizers) comply with the official specifications of the file format. It is necessary to indicate the file format of the file to the validator in order to validate it; that is why it is a process that depends on characterization.

After processing the file, validators can bring back one of the following responses:

  • Valid file: the validator has checked that the file structure is correct, according to the specifications defined for the file format.

  • Invalid file: the validator has checked that the file is non-compliant with some of the specifications defined for the file format.

  • Non-validated file: the validator finds difficulties and cannot carry out the file validation process. That does not mean that the file is not valid, it is just that it has not been possible to process it correctly.

When configuring validators in the preservation plan, we must select a minimum level of accepted validation, which will cause that, based on the results of the file validation, the job will continue or end with error.

Note: LIBSAFE has configured by default a group of validators for the default characterizer (DROID).

The File format validators main screen lists all the validators available in the system. The system shows name, description, version, UID identifier, a weblink where we can find detailed information and access to the validator detail.