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
  2. Metadata filters

Creation of metadata filter

PreviousMetadata filter detailNextMetadata filter editing

Last updated 3 years ago

Was this helpful?

The creation of a metadata filter can be accessed from the main screen of ‘Ingestion Controls’, by means of the link Create a new import filter.

In order to create an import filter, we must fill in the information related to name, description, status (active / inactive) and the mandate to request a metadata file pattern from the user.

In the Filter files section, we must include all the files needed for the correct execution of the metadata filter. LIBSAFE lets us do that by a convenient drag & drop system, whereby we will only have to drag and drop the necessary files, or by the link Drag files or select them here, where a Windows file selection window will open.

Note: there is a limit as for the number of files and the total size of the same that may be added simultaneously when we create a metadata filter. LIBSAFE will consult the server internal configuration and apply set guidelines. It will be the system administrators’ responsibility to configure said server parameters (in the example of the figure below, LIBSAFE is limited to 20 files and a maximum file size of 128 MB).

The added files are listed as shown in the following figure. We can remove from the list any file that has been added, but later deemed not needed. It is possible to add a description for every file.

In case the ingestion control has more than one file, we will have to select which one will be the main or executable file for the ingestion control. LIBSAFE, by default, will select the first file to be added.

If the metadata filter includes an XSLT or XML file for the parsing of the descriptors, we must select the XSLT/XML check related to the corresponding file.

Next, the metadata filter parameters are configured, if needed. By means of the link Add in the Metadata filter parameters section, we will see a form with the information needed to be filled in, such as:

  • Description: a brief description of the parameter, syntax, possible values, etc.

  • Type of parameter: as previously explained, on creating a preservation plan, the value entered for the parameter will be validated when a metadata filter is associated. Besides, if the type of data selected is numeric, we shall be able to assign the parameter value to a range and to specify this range.

  • Recommended Value: we can indicate a value in order to facilitate the configuration of the metadata filter later on. This value will be modifiable when we apply a metadata filter to a preservation plan.

  • Default value: in case a metadata filter will always need a value for the parameter, but there are situations where due to either the functionality of the metadata filter or because the user should not be forced to enter the value, this field can be filled with the value applied if the parameter value is left blank when configuring a metadata filter in a preservation plan.

  • Mandatory: it is a check indicating whether it is mandatory to put a value to the metadata filter parameter or not.

Note: Metadata filters will admit the configuration of up to five parameters.