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. Metadata schemas

Creation of a metadata schema

PreviousMetadata schema detailNextMetadata schema editing

Last updated 3 years ago

Was this helpful?

A metadata schema can be created from the Create a new metadata schema button, in the metadata schema main screen.

Note: we can create a new metadata schema as a copy of an existing schema. First, we have to create the new metadata schema and then edit it later on.

As a first step, we request the name for the new metadata schema and the status with which we want to create it (active / inactive).

Once created, we go to the edit screen, where we can add the metadata descriptors and the import filters we desire.

Note: at this point, the metadata schema is already created; it is empty, but created. If in the end we would not want to continue with the process of the metadata schema creation, it is recommended to make use of the link to delete the metadata schema, so that we do not leave empty metadata schemas.