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. Annexes
  2. Automatic ingestion and retrieval processes

Automatic ingestion

The goal of this programmed task is to be able to create and start ingestion jobs automatically, not needing to access the control web interface to create the associated ingestion job or to press the Start button, once the information has been copied into the ingestion folder.

Automatic ingestion has a directory as a starting point. The directory path is configured initially during the installation process and, later on, the systems administrator will be able to change the path.

Within this directory, the automatic process will generate one directory per each existing preservation area (that is active). Inside every preservation area directory, we have to create the ingestion job folders, keeping in mind that:

  • The creation of an ingestion job folder in a preservation area directory will be sufficient condition (initially) for the creation of an ingestion job in said preservation area.

  • The folder created inside the area directory will be taken as an ingestion folder (by means of the web interface, we can create a folder with a name type ‘INGXXXXXXX”, where we can deposit the objects). The name given is not important, since the process will end up renaming the folder, web interface-style. The objects that we wish to ingest will have to be deposited in this folder.

  • In order to avoid ingestion job problems created without all the objects needed, we must add a blocking suffix to the ingestion job folder. The automatic process will recognize the blocking suffix and will ignore the folder.

To create an automatic ingestion job:

  • Access the configured base directory and, once inside, access the preservation area directory where we want to create an ingestion job.

  • Create a folder where we can deposit the ingestion job objects. For the automatic process to ignore the ingestion job folder until the copying of all the objects is over, the name of the folder has to end with the blocking suffix, as follows: ‘ingestion folder.blocking suffix’.

  • Copy the objects we want to add to the ingestion job.

  • Once the objects are copied, rename the ingestion folder, eliminating “.blocking suffix” from the name of the folder.

  • Close the folder. The automatic ingestion folder will start within a period of time that will depend on how said process was configured.

Note: both the path to the base directory and to the blocking suffix are configurable. It is the systems administrator responsibility to manage said variables. Contact him/her if you need information about that, or contact the LIBNOVA consultants, who may also be able to advise you.

The automatic ingestion process carries out a series of basic checks on the ingestion folder, prior to the start of the creation of an automatic ingestion job. If the process does not pass these validations correctly, its default behavior will be as follows:

  • If the folder happened to be empty, the process will delete the folder (in order to clean up the directory)

  • If the folder contains files, the process will rename the folder with the blocking suffix (in order to avoid having to process the folder again).

PreviousAutomatic ingestion and retrieval processesNextAutomatic retrieval

Last updated 3 years ago

Was this helpful?