ePIC PID Registration (Handle & DOI)
This step plugin allows the registration of handle and DOI as persistent identifiers via the ePIC service of the GWDG.
The plugin allows digital copies to be registered with the ePIC Service of the GWDG. Both the generation of Handle IDs and the registration of DOIs are possible. The Handles can be generated for each logical and physical element of a METS file and stored as metadata in each case.
To install the plugin, the following file must be installed:
In order to configure how the plugin should behave, the following two configuration files must also be installed:
The configuration of the file
plugin_intranda_step_epic_pid.xmlis structured as follows:
<!-- which projects to use for (can be more then one, otherwise use *) -->
<!-- authentication and main information -->
<!-- configuration for Handles -->
<!-- configuration for DOIs -->
<config>can occur repeatedly for different projects or workflow steps in order to be able to perform different actions within different workflows. The other parameters within this configuration file have the following meanings:
The configuration of the file
plugin_intranda_step_epic_pid_mapping.xmlis structured as follows:
<?xml version="1.0" encoding="UTF-8"?>
This configuration file defines how the available metadata from the METS file are to be used for registering the DOI. At least one metadata is defined for each field of the DOI that is to be used.
To put the plugin into operation, it must be activated for one or more desired tasks in the workflow. This is done as shown in the following screenshot by selecting the plugin
intranda_step_epic_pidfrom the list of installed plugins.
Assigning the plugin to a specific task
Since this plugin is usually to be executed automatically, the work step should be configured as automatic in the workflow.
After the plugin has been fully installed and set up, it is usually executed automatically within the workflow, so there is no manual interaction with the user. Instead, the plugin is called by the workflow in the background and starts generating an identifier depending on the selected configuration. The plugin proceeds as follows:
The way the plugin works within the correctly configured workflow is as follows:
- First, the plugin opens the METS file of the operation.
- For each logical and physical element of this METS file, a handle in the form
PREFIX-CLIENT-OBJECTIDis created. If the planned
OBJECTIDis already assigned as a handle, an incrementing suffix (e.g.:
-2, etc.) is added at the end.
- Finally, the generated handle is stored within the METS file as a metadatum for the respective logical or physical structural element. The metadata type
_urnis usually used for this purpose.
- If the registration of DOIs has been activated, a new DOI identifier is generated for each logical top-level element in addition to the handle generation and stored within the METS file.
If a handle is registered, the following contents result from the communication with the ePIC service:
Handle Values for: BASE/go-goobi-1296243265-17
Index Type Timestamp Data
1 URL 2020-04-21 12:02:30Z https://viewer.goobi.io/idresolver?handle=
2 TITLE 2020-04-21 12:02:30Z [Stammbuch Daniel Schelling]
3 AUTHORS 2020-04-21 12:02:30Z Daniel Schelling
4 PUBLISHER 2020-04-21 12:02:30Z Stadtarchiv Duderstadt
5 PUBDATE 2020-04-21 12:02:30Z 1617
6 INST 2020-04-21 12:02:30Z intranda
100 HS_ADMIN 2020-04-21 12:02:30Z handle=USER; index=300; [create hdl,delete hdl,read val,modify val,del val,add val,modify admin,del admin,add admin,list]
This information is then used by the GWDG's ePIC service to automatically generate a DOI identifier with the same ID: