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. 2. Document model

2.5. Anchor

An anchor is a document structure that is more virtual in nature and can combine other structural units into a group. Such anchors are, for example, the structures Multi-volume Work or Journal, which holds all volumes of the work or all volumes of the journal together. The anchor itself has no content files - i.e. no image set with image files, it consists only of a structural unit that has descriptive metadata. The essential metadata is an identifier with which the anchor can be clearly identified.

In principle there are two ways to save the anchor:

  • In the same file as the underlying structural unit. In this case, the structural unit serving as anchor is stored redundantly in each metadata file. For example, the RDF/XML format stores the document structure of the anchor as the top-level structural unit in the file.

  • In a separate file, so that the anchor must be referenced from underlying structural units. For importing into databases and repositories, this means that the anchor must always be imported first. To ensure referencing, the anchor contains an identifier that is used in the reference in the underlying structural unit.

Previous2.4. Metadata groupsNext3. Rule set

Last updated 5 years ago

Was this helpful?