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. System configuration
  2. Extras and tools

File management

PreviousLogs managerNextDatabase management

Last updated 3 years ago

Was this helpful?

During the configuration of ingestion controls, preprocessing actions or metadata filters, the related files have to be loaded. From this section, the following files loaded into the system can be managed:

  • Ingestion controls: executable and configuration files.

  • Preprocessing actions: executable and configuration files.

  • Metadata filters: executable and configuration files.

  • Metadata filters XSLT/XML: metadata parsing files.

Note: use this section under the monitoring of your LIBSAFE consultant.

In the main File management screen, there is a list of all the files included in the different types permitted. Name, description, date of creation and links for editing, unloading, deletion and access to file detail of each one is shown.

New, needed files can be loaded, or if a specific file has been modified it can be replaced (deleting and then loading).

When loading the files, the type of file to be loaded onto the system has to be selected (one of the four types mentioned initially). Every file can have its own description. LIBSAFE allows for the addition of files by means of an easy drag & drop system, whereby it only takes dragging and dropping the required files, or using the Drag or select files here link, which will open a window to select Windows files

Only the description can be modified when editing a file.

Note: there is a limit regarding the number of files and the total size of them. LIBSAFE will consult the internal configuration of the server and apply set guidelines. It will be the system administrators’ responsibility to configure said server parameters.