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

Ingestion checks

PreviousPreprocessor editingNextIngestion check details

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.