plugin_intranda_step_datacite_doi.jarcontains the program logic. it needs to be installed at this path:
plugin_intranda_step_datacite_mapping.xmlis the mapping file, defining how local metadata should be translated to the form required for the DOI registration. It needs to be installed at this path:
plugin_intranda_step_datacite_doi.xmlis the main configuration file for the plugin. It needs to be installed at this path:
plugin_intranda_step_datacite_doi.xmland can be adapted during operation. It 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:
<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
<field>specifies the name of the DOI element, and the
<altMetadata>entries indicate from which metadata of the DocStruct the value should be taken, in order. If there is no such entry in the DocStruct, then the
<default>value is taken. The value
"unkn"for "unknown" is recommended by Datacite for data which is missing.
<default>must be specified; for optional fields this is not necessary, but may be done if wished.
#CurrentYearis a special case: it is replaced with the current year in the DOI.
intranda_step_datacite_doifrom the list of installed plugins.
Update metadata index when finishingshould be ticked.
<typeForDOI>is specified, then it will go through each DocStruct of this type in the file. If not, then it will take the top DocStruct. From these it creates the data for a DOI, using the mapping file to translate. It then registers the DOI via the MDS API of DataCite, with DOI given by the
<base>together with any
<name>, and the ID of the document (its
CatalogIDDigital) plus an increment, if there are more than one DOIs generated for the given document. The record is given a registered URL defined by the
<url>followed by the DOI. The generated DOI is written into the METS/MODS file under the metadata specified in
<handleMetadata>. If the
Articlefor example, then each Article in the METS/MODS file will be given a DOI, which is saved in the metadata under
<handleMetadata>for each Article.