plugin_intranda_step_epic_pid.xml
is structured as follows:<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:project
<config>
is to apply. The name of the project is used here. This parameter can occur several times per <config>
block.step
<config>
should apply. The name of the workflow step is used here. This parameter can occur several times per <config>
block.certificate
certificate
element defines the path to the private key used for authentication.user
base
url
url
+ handle IDprefix
prefix
+ separator
+ name
+ separator
+ objectId
. The parameter prefix
defines the prefix with which the handle should begin. This parameter is optional.name
name
defines the content of the handle to which the object IDs are subsequently appended. This parameter is optional.separator
doiGenerate
doiMapping
plugin_intranda_step_epic_pid_mapping.xml
is structured as follows:field
metadata
altMetadata
metadata
parameter is not available, an alternative metadata can be defined here to be used instead. This parameter is optional and repeatable.default
metadata
and altMetadata
cannot be found, a default value can be set here.intranda_step_epic_pid
from the list of installed plugins.PREFIX-CLIENT-OBJECTID
is created. If the planned OBJECTID
is already assigned as a handle, an incrementing suffix (e.g.: -1
, -2
, etc.) is added at the end._urn
is usually used for this purpose.BASE/go-goobi-1296243265-17
.