UGH (English)
Documentation
  • Documentation UGH Library
  • 1. Introduction
  • 2. Document model
    • 2.1. Structural data
    • 2.2. Content files
    • 2.3. Metadata
    • 2.4. Metadata groups
    • 2.5. Anchor
  • 3. Rule set
    • 3.1. Definition of metadata types
    • 3.2. Definition of metadata groups
    • 3.3. Definition of structure types
  • 4. Serialization
    • 4.1. MARC
      • 4.1.1. Introduction
      • 4.1.2. Configuration
      • 4.1.3. Example configurations
    • 4.2. METS/MODS
      • 4.2.1. Introduction
      • 4.2.2. General configuration
      • 4.2.3. Configuration of the mapping of structure and metadata
      • 4.2.4. Extended METS export options
      • 4.2.5. UghConvert
    • 4.3. PICA+
      • 4.3.1. Introduction
      • 4.3.2. Configuration
    • 4.4. XStream
    • 4.5. RDF/XML
      • 4.5.1. Introduction
      • 4.5.2. Configuration
    • 4.6. AGORA-Database
      • 4.6.1. Introduction
      • 4.6.2. Database configuration
      • 4.6.3. Definition of the Persistent Identifier in the database
      • 4.6.4. Inheritable metadata types
      • 4.6.5. Value lists
      • 4.6.6. Metadata Type Mapping
      • 4.6.7. Structure Type Mapping
  • 5. Outlook
  • 6. Additional details
Powered by GitBook
On this page

Was this helpful?

  1. 4. Serialization
  2. 4.6. AGORA-Database

4.6.3. Definition of the Persistent Identifier in the database

Furthermore, some functionally relevant information must be provided. For example, the element <persistentIdentifier> determines which metadata type is valid for the persistent identification of a structural unit. This element must exist exactly once, since it is used to check whether a document has already been imported into the repository and, if so, to reject serialization.

Example: Configuration of the PPN as persistent identifier:

<persistentIdentifier>CatalogIDDigital</persistentIdentifier>
Previous4.6.2. Database configurationNext4.6.4. Inheritable metadata types

Last updated 5 years ago

Was this helpful?