Step plugin for the automatic creation of Handle IDs within METS files
| Name | Wert |
|---|---|
The plugin generates a Handle on the Handle server of the GWDG for all logical and physical elements of a METS file. These Handles are then stored in the respective element itself as metadata _urn.
If automatic DOI assignment is installed, a new DOI is generated and stored for each top-level logical element.
To use the plugin, the following files must be installed:
The file goobi-plugin-step-handle-mets.jar contains the program logic and must be installed in the following directory, readable by the Tomcat user:
The file plugin_intranda_step_handle_mets.xml must also be readable by the Tomcat user and installed in the following directory:
Once the plugin is installed and configured, it can be used within a Goobi workflow step. To do this, add the plugin plugin_intranda_step_handle_mets within the desired task. Additionally, ensure that the Metadata and Automatic Task checkboxes are selected.
To utilize automatic DOI assignment, an additional file must be installed at the following path, readable by the Tomcat user:
This file is used to configure the plugin and is located in the mappings folder.
The plugin operates within a correctly configured workflow as follows:
When the plugin is invoked within the workflow, it opens the METS file.
A Handle is generated for each logical and physical element of the METS file (in the form /goobi-Institution-objectId, where objectId is the object identifier, possibly supplemented with -1, -2, etc., if the Handle already exists).
The generated Handle is then written into the respective structural element as metadata of type _urn.
When creating Handles for the top-level logical structural element of a METS file, additional metadata is stored alongside the generated Handle ID and its associated URL. An example of this information is as follows:
These details are used in the case of additional DOI registration to create a DOI with the same ID, for example 21.T119876543/goobi-go-1296243265-17.
The plugin configuration is done in the file plugin_intranda_step_handle_mets.xml as shown below:
The <config> block can occur repeatedly for different projects or work steps in order to be able to perform different actions within different workflows. The other parameters within this configuration file have the following meanings:
In addition to these general parameters, the following parameters are available for further configuration:
For DOI assignment, the file plugin_intranda_step_handle_mets.xml must include the following additional configurations:
The DOIMappingFile parameter defines the path to the plugin_intranda_step_handle_mets.xml file.
In the DOI-Mapping.xml file, each <map> entry describes a mapping between a Dublin Core element and one or more metadata fields from the METS file. The file is structured as follows:
| Parameter | Explanation |
|---|---|
| Parameter | Explanation |
|---|---|
| Parameter | Explanation |
|---|---|
Identifier
intranda_step_handle_mets
Repository
Licence
GPL 2.0 or newer
Last change
26.08.2024 09:19:33
project
This parameter defines which project the current block <config> should apply to. The name of the project is used here. This parameter can occur several times per <config> block.
step
This parameter controls which work steps the <config> block should apply to. The name of the work step is used here. This parameter can occur several times per <config> block.
PEMFile
Path to the Private Key .PEM file provided by GWDG.
HandleInstitutionAbbr
Abbreviation for the institution.
HandleIdPrefix
Prefix for the Handles (e.g., for the application or project).
HandleBase
Identifier for the institution.
UserHandle
Identifier for the user of the Handle registration.
URLPrefix
URL where the documents can be found with their Handle ID after publication.
<doiElt>
Dublin Core element for which this mapping is defined.
<localElt>
Name of the metadata in the METS file whose value should be used for <doiElt>.
<altLocalElt>
Alternative names for the metadata, searched if no entry is found with <localElt>.
<default>
Specifies the value to be used if neither <localElt> nor <altLocalElt> provide suitable entries.
<title>, <author>, <publisher>, <pubdate>, <inst>
These are currently the only five required and at the same time maximum permitted fields for metadata used for registration.