4.2.5. UghConvert
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 read and write the respective formats at command line level with the supplied scripts for Windows and Linux systems. Only a complete version of the UGH library (ughCLI) and a Java runtime environment in version 1.5 is required for execution.
UghConvert reads in a DigitalDocument
in a given serialisation format - if necessary by specifying the rule set used - and then serialises it again in a likewise given format. Data can also be read only, read in one format and saved again in the same format.
4.2.5.1 The command line
The script is called as follows, whereby the path to the Java Runtime Environment must be set:
The basic parameters are the following:
Parameter | Description |
| The path to the rule set file used. |
| The format to read: The following are possible: |
| The format to write: The following serialization formats can be used: |
| The path to the source file, in the format specified with |
| The path where the target file is to be saved; it is serialized in the format specified in |
| This parameter outputs the structural and metadata of the document when it is read. |
| Outputs a help for the syntax. |
| Avoids any kind of output, except errors. |
| Outputs the versions of each |
Example: Reading an XStream file with output of structural and metadata
Example: Converting an XStream file to an (internal) METS file
Example: Converting an RDF file into an (internal) METS file, including output of structural and metadata
4.2.5.2 Administrative metadata section
For the conversion into the zvdd/DFG Viewer METS format, some more values are configurable, which can be divided into three groups (see also "Peculiarities of the METS export"). One of them contains the data for the administrative metadata section v:rights
and v:links
.
Parameter | Description |
| The author of the digitised material. |
| A URL of the author's logo; this logo is displayed accordingly by the DFG Viewer and the zvdd portal |
| A URL of the homepage of the author. |
| A URL to a contact form of the author's homepage or alternatively an e-mail address. This is intended to enable the DFG Viewer to contact the author directly. |
| A URL to the catalogue entry of the digitised material - or to the subordinate structure, for example a volume - if one exists. |
| A URL to the catalogue entry of the digitised material - or to the superordinate structure, for example a journal - if one exists. |
| A URL to the online presentation of the digitised material - or to the subordinate structure, for example a volume - if one exists. |
| A URL to the online presentation of the digitised material - or to the superordinate structure, for example a journal - if one exists. |
4.2.5.3 File groups (FileGroups)
Data for the file groups required for the DFG Viewer (FileGroups
), at least FileGroups
with the names MIN
and DEFAULT
are required:
Parameter | Description |
| The file extension of the file names in the FileGroup |
| The mimetype of the files in the FileGroup |
| The path of the files in the FileGroup |
| The extension of the XML ID used in the METS file for the FileGroup |
All other specifications are equivalent for the file groups DEFAULT
, MAX
, DOWNLOAD
, LOCAL
, PRESENTATION
and THUMBS
. The file group LOCAL
is created automatically, but can be overwritten with your own values if required. The parameters for the other file groups are set equivalent to minfilesuffix
, minmimetype
, minpath
and minidsuffix
, for example defaultpath
, maxpath
, downloadpath
, localpath
, presentationpath
and thumbspath
. All parameters can be found in the help of UghConvert:
For the configuration of the extended parameters (administrative metadata and file groups) the long parameters (--mimidsufffix
, --minmimetype
, etc.) should be used.
Example: Extract from a METS file (FileGroups) From the information
the following METS FileGroup DEFAULT
gets generated...
...and the following administrative METS metadata section:
Last updated