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?

Metadata collision groups

An object is something representing an entity, and this representation is comprised of a group of files and folders with a specific structure. One such entity is what LIBSAFE calls an object.

When we try to preserve an object in an ingestion job, it could happen that the object to be ingested is related to an object already preserved in the system. This happens when the metadata of the object to be ingested and the metadata of the object already preserved determine (through some of its descriptors) that they are indeed the same object.

A collision group is a set of descriptors (one per schema) that establishes a relation between objects which share a descriptor with the same value, which leads to the consideration that they correspond to the same object.

LIBSAFE lets us define two types of groups:

  1. Unicity.

  2. Versioning.

Note: it is important to point out the metadata associated to these groups can belong to the same or different metadata schemas, with schemas used in the same or different preservation plans, belonging to the same or different preservation areas. The association of every metadata to a group is what lets us identify the collision and thus ensure that any object will be reviewed against all the other existing objects, so that it will not be repeated in the system.

Obviously, the latter is only possible if we make sure that we identify objects correctly with their metadata, since if we ingest objects in the system without any defined metadata it is not possible to establish any relation among them.

PreviousAutomatic audit schema editingNextUnicity metadata collision groups

Last updated 3 years ago

Was this helpful?