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 retrieval

The goal of this programmed task is to be able to create and initiate retrieval tasks automatically, without having to access the control web interface, to create the associated retrieval job.

Automatic retrieval has a directory as the 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.

The basic operation of the automatic retrieval consists of the creation of a folder, naming it with a specific syntax.

There are two ways of indicating the object we want to retrieve:

  • By its LUOI:

[LUOI].LUOI.[request suffix] (i.e.: 45.3.LUOI.Request)

  • By object name:

[name of the object].Identifier.[request suffix] (i.e.: BBL_003.Identifier.Request)

Note: in order to use the retrieval by object name method, the object name must be a metadata and it must be configured as a versioning collision group.

Where:

  • LUOI: identifier for the object identifier search in LIBSAFE

  • Identifier: identifier for the object name search

  • Request suffix: it is a suffix that can be configured by the systems administrator. The automatic retrieval process will recognize it to identify a retrieval request.

To create an automatic retrieval job:

  • Access the automatic retrieval base directory that has been configured.

  • Create a folder, renaming it as previously explained.

  • The retrieval job will start automatically.

Note: both the base directory path and the request suffix can be 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.

If any automatic retrieval job would end in error, the process will rename the folder with the “error” suffix. To know more about the state of the jobs, please consult the logs.

PreviousAutomatic ingestionNextRegex expressions – User reference

Last updated 3 years ago

Was this helpful?