plugin_intranda_step_epic_pid.xmlis 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:
<config>is to apply. The name of the project is used here. This parameter can occur several times per
<config>should apply. The name of the workflow step is used here. This parameter can occur several times per
certificateelement defines the path to the private key used for authentication.
url+ handle ID
objectId. The parameter
prefixdefines the prefix with which the handle should begin. This parameter is optional.
namedefines the content of the handle to which the object IDs are subsequently appended. This parameter is optional.
plugin_intranda_step_epic_pid_mapping.xmlis structured as follows:
metadataparameter is not available, an alternative metadata can be defined here to be used instead. This parameter is optional and repeatable.
altMetadatacannot be found, a default value can be set here.
intranda_step_epic_pidfrom the list of installed plugins.
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.
_urnis usually used for this purpose.