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

4.4. XStream

Serialization class:

 ugh.fileformats.mets.XStream (v1.2)

Serialization via XStream initially replaced the RDF/XML schema to be independent of mappings and additional entries in the rule set. XStream can completely serialize the document model, but has some disadvantages (see below), so this format will be removed from the UGH library in the future, but reading access will still be possible for compatibility reasons!

XStream serializes the complete Java object DigitalDocument in XStream XML format, so that all structure types, metadata, references, etc. of the document model are saved. Entries in the rule set or a mapping are not necessary here. However, since there are close relationships between the DigitalDocument and the ruleset (names of metadata, quantifiers, etc.), some parts of the ruleset are serialized first. After the serialized object is loaded, it is therefore compared with the current rule set so that changes in the rule set are mapped to the object.

Although XStream as a serialization format has the advantage that no further configuration is required to use it, it has the disadvantage that very large and complex XML files are created in a complex format, which can hardly or not at all be edited outside the UGH library - possibly by hand.

Previous4.3.2. ConfigurationNext4.5. RDF/XML

Last updated 5 years ago

Was this helpful?