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

Ingestion checks

PreviousPreprocessor editingNextIngestion check detail

Last updated 3 years ago

Was this helpful?

Ingestion checks are programmed processes that will block an object from ingestion if it does not comply with certain set conditions. Said conditions are established in a submission agreement, which includes the definition of an SIP (submission information package), and they are configured through a preservation plan.

They are established at object root folder, folder and file level. Ingestion checks may have a regular expression (RegEx) associated to them, in order to facilitate the selection of the objects, folders or files to which we will apply the following, according to the type of check:

  • In case of checks at object root folder level, the expression is applied to the name of the object folder or, similarly, to its name.

  • In case of checks at folder level, the expression is applied to the name of the folder, not including the previous complete path; that is, for subfolders, the top levels are not part of the chain to which the regular expression is applied.

  • In case of checks at file level, the expression is applied only to the file name, regardless of its relative path.

A standard installation includes checks to guarantee the existence of files by type, sequential numbering, maximum object and folder size, existence of particular paths, file count, etc.

In the main screen of the ingestion checks, the different ingestion checks available for the above mentioned types are listed. In the list, we can see name, status (active / inactive), the ingestion check detail and we can access its edit.

The function and particular use of every ingestion check can be consulted in its detail record, although there is a reference to the main ones further along in this document.