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 configuration, basic sections
  2. Ingestion checks

Main ingestion checks

The main ingestion checks available are:

At root object level:

1. 1004 There is a specific folder inside the object: it checks that there is a subfolder at the root of the object. It is recommended for checking the main folder structure of an object.

2. 1006 Maximum object size: it checks the maximum size of an object. Depending on how we use the application, it could be a good way to avoid the preservation of objects that are too big, or that require a specific check of their good conformation.

3. 1007 The file name starts with the object name: it checks that the file names of the object start with the name of the very object. Recommended for well-structured objects, whereby their conformation has taken into account a strict file identification system.

At folder level:

4. 2001 File extension: it checks that all the files in a folder have a specific extension. It is recommended for when the structure of the ingestion package has clearly defined folders by file type.

5. 2003 Sequential file names: it checks that the name in all of the files of a directory follows a numbered sequence. It is applied at the final part of the name, without considering the extension. It is recommended for use in strongly structured packages, as an added verification to guarantee the integrity of all the files saved in the folder.

6. 2006 Minimum file size: it checks that all the files in a folder have a minimum size. It is highly recommended that it be used at least in a configuration that sets a minimum size of 1 byte for its files; this way, the ingestion of objects with badly copied files (usually with zero size) can be avoided.

At file level:

7. 3003 File name with invalid characters: it checks that the file name does not contain invalid characters. Although initially it is taken for granted that a file has a valid name because of the mere fact that it can be copied by the file system, it could be convenient to use this check to ensure a correct name in any type of file system (LIBSAFE can have different types configured, with some sort of incompatibility among them)

8. 3004 Maximum number of characters in the file name: it checks that file names do not exceed a certain maximum length. It is recommended to help guarantee that file names length (when adding their particular path to the path of the destination directories) stays within the limits permitted by the file system.

PreviousIngestion check editingNextMetadata filters

Last updated 3 years ago

Was this helpful?