Browse

In this document, the internal, universal document model of the UGH library is first briefly outlined and then the general configuration and the individual serialization formats are discussed. The sou...

This document provides a brief overview of the document model and its customisability using a rule set. Some classes and their configuration options for serialising the data are also described here. I...

...

Structure data describes the structure of a document. For this purpose, however, a rather extensive structural term is used, which does not only concern the internal, hierarchical structure of a docum...

Each structural unit can also be assigned content files, whereby an m:n relation between structural units and content files is possible. These files contain the actual content of the document either a...

Both content files and structural units can have metadata. A metadata is characterized by the fact that it has a specific type and value and is assigned to either a structural unit or a content file; ...

Since version 1.10.0 there is the possibility to group metadata. This makes it possible, for example, to divide titles into a nonSort and a Sort part and to maintain this coherence even across many di...

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

[Structural data](/en/other/ugh/documentmodel/structuraldata) [Content files](/en/other/ugh/documentmodel/contentfiles) [Metadata](/en/other/ugh/documentmodel/metadata) [Metadata groups](/en/other/ugh...

A metadata type is defined within the element. This element must be the only child of the element, which contains the internal name of the metadata type. The internal name is also used to reference th...

A metadata group is defined within the element. This element must be the only child of the element, which contains the internal name of the metadata type. The internal name is also used to reference t...

Structure types are defined similarly to metadata types. The element for defining a structure type is called DocStrctType and just like the metadata types, the elements Name and Language have the same...

The document model described above is quite general, it does not specify any metadata or structure types. To be able to create instances of structural units and metadata at all, it is necessary to def...

The format MARC (MAchine-Readable Cataloging) is a data format developed for the exchange of bibliographic data. The format contains metadata on a single structural unit. Structure data cannot be desc...

The configuration takes place in the rule set within the element. A element can be created there. Within this element the four elements , , and are allowed, each of which must be linked to an internal...

Example: Mapping of metadata Data from MARC XML: xml [Stammbuch Pauline Pichler] Manuskript Mapping in the rule set for data transfer: xml TitleDocMain 245 a any 0 Example: Removing brackets Data from...

Serialization classes: text=de.intranda.ugh.extension.MarcFileformat...

The METS/MODS XML format can completely serialize the internal document model, both read and write methods are implemented. Since it is only a subset of METS - not all METS elements are used - a descr...

Serialization in METS/MODS with the MetsMods class does not require any further configuration, almost all tags within the tag in the Format section of the ruleset refer exclusively to the MetsModsImpo...

Document structures and metadata The mapping of document structure types of the document model - that is, the structure types defined in the rule set - to METS structure types is defined in the lower ...

For various possibilities of the zvdd/DFG-Viewer METS format, no equivalent data are provided in our document model. However, these data are essential for a proper METS export. Setter and getter metho...

To convert the serialisation formats of the used document model described above between each other independently of an external application, UghConvert can be used. It is a Java application that can r...

Serialization classes: text ugh.fileformats.mets.MetsMods (v1.9) ugh.fileformats.mets.MetsModsImportExport (v1.9)...

The PICA+ format is mainly used in library catalogues and describes only the bibliographic unit; only metadata for a structural unit can be found in PICA+ and no structural data at all. If necessary, ...

The PICA+ configuration takes place within the enclosing element, which is directly subordinate to the element. Within the element, the type-specific elements , and are used, each of which maps an int...

Serialization class: text ugh.fileformats.opac.PicaPlus (v1.3)...

Serialization class: text 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. XStr...

The RDF/XML format is the data format originally developed for the AGORA document management system (AGORA DMS), which is supported by the AGORA document management system for import. Furthermore, the...

The configuration of the format takes place exclusively in the enclosing \' element. Structure types are simply mapped 1:1. Therefore, the ' element only includes the two subelements' and '.contains t...

Serialization class: text ugh.fileformats.exel.RDFFile (v1.2) For compatibility reasons, the serialization format RDF/XML is part of the UGH library (for example, to read old RDF/XML files that are to...

The AGORA DMS system is based on a clearly defined database structure. This database structure is so flexible that different meta- and structure types can also be defined in it. However, the structure...

The configuration is located in the enclosing element, which is subordinate to the element. First, some basic parameters of the database must be specified. These are in detail: | Parameter | Descripti...

Furthermore, some functionally relevant information must be provided. For example, the element determines which metadata type is valid for the persistent identification of a structural unit. This elem...

The element contains all the metadata types that are to be inherited from a structural unit to underlying structural units. Corresponding entries are duplicated in the database and thus allow fast acc...

A value list can replace certain values when writing to the database. This can then be useful for rewriting language codes. In a corresponding mapping file, the old values (from the API) are compared ...

However, the main part of the configuration for this serialization class is the mapping of the metadata types to specific tables and table columns. To understand the explanations described below, it i...

The document structure type is mapped relatively simply. As the name of the structure type is also stored in the database but is linked to the actual structural unit by means of a separate table via a...

The AGORA database serialization is no longer included in the UGH library, but the following chapter has been retained for documentation reasons!...

Data created using the API should of course be able to be read and written. For this purpose the API has an internal JAVA interface, which can be implemented by different classes and provides methods ...

About this manual Document management has always been the main task of libraries. With the beginning of the digitisation of information, the task has changed dramatically. Metadata is increasingly use...