LogoLogo
  • LIBSAFE Advanced Pro - User Administration Manual
  • Introduction
    • Basic concepts
    • General considerations
  • Access
    • Access with a two-factor authentication
    • Access via API to the application data
  • General browsing
  • General system configuration
  • Home
  • Catalog
    • Catalog – Browse catalog by object
    • Catalog – Browse by tree
    • Catalog – Search catalog by object
    • Catalog – Object detail
      • General Information
      • Metadata
        • Metadata descriptor value editing
        • Comparing updated metadata set with original
        • Additional information on metadata
      • eXtended Metadata
        • Functional concepts
        • Technical concepts
        • Interface schema
          • Metadata type configuration
          • Sets and Block configurations
        • Creating and editing extended metadata
          • Structured type block
          • Free type block
        • Special links into blocks to an object’s files
        • Visualisation and download of structured blocks
      • File and folder structure
        • Object Explorer
        • Retrieving a complete object by applying a DIP profile
        • Files’ details
      • Object health
      • Storage
      • Data Integrity
        • Provenance metadata and events (Event management)
      • Executing Transfer Connectors
      • Object history
    • Catalog – Object group detail
  • Ingestion
    • Ingestion – Creating a new ingestion job
    • Ingestion – Execution of an ingestion job
  • Retrieval
    • Object retrieve from catalog
    • Retrieval from an object detail
    • Retrieve job details
  • Active preservation
    • File format evolution jobs
      • Manual object evolution
      • Approve evolution jobs selected by the system
    • Digital signature jobs
    • Object metadata update
      • Update via web interface
      • Update through a massive update job
        • Structure and syntax of massive metadata update files
        • In multiple files
        • In a single file
        • Basic conditions of the metadata update operations
        • Available metadata operations
      • Metadata update job detail
  • Document repository
  • Advanced options
    • Audit
      • Creating an audit job
        • Disk audit
        • Object audit
      • Audit job details
    • Reports
      • Reports generation
      • General information on objects and status of the system
      • Customized Reports
      • Evolution of ingestion jobs and preserved objects
      • Ingestion job report
      • Audit job reports
      • METABASE reporting
  • Other user sections
    • User configuration
    • Notifications panel
Powered by GitBook
On this page

Was this helpful?

  1. Catalog
  2. Catalog – Object detail

eXtended Metadata

There is currently a basic metadata version in LIBSAFE, which, depending on the specifications made at the time of creating the preservation plan, are defined and contain a series of descriptors that are used to present additional information about the object files. From this point on, there is a need to present more information related to the application processes, processes prior to ingestion, processes of enrichment of the object data in the process and subsequent ingestion or any other event that happens on the queried object. In addition, this functionality can be managed directly on the information catalog of the preserved object, so the new functionality is not part of the process of creating a preservation plan, but of the visualization and post-management of an object.

In the same way it is necessary to define a simple and hierarchical scheme to store the resulting information during the process and all types of data received in this section in a homogeneous way. For this purpose, a data hierarchy is established to manage the extended metadata; Class à Type à Set à Block. This latter is in charge to storing all the specified information of each object with the possible variation between two extended metadata classes: Structured or Free.

To ensure data traceability and data preservation over time, the system is required to keep versions of blocks and no editing is allowed on an existing one. Similarly, the blocks will not be stored in the database, but will be stored in files with a defined structure and a specific directory path.

This section defines all the technical concepts that cover the functionality and that are relevant for the management or knowledge of the technical limitations. Therefore, it is essential that these concepts are clear when configuring this functionality.

PreviousAdditional information on metadataNextFunctional concepts

Last updated 3 years ago

Was this helpful?