EWIG Long term archiving

Introduction

This documentation describes the installation, configuration and use of a plugin for creating a METS file for long-term archiving EWIG.
Details
Identifier
intranda_step_lza_ewig
Licence
GPL 2.0 or newer
Compatibility
Goobi workflow 3.0
Documentation date
05.12.2019

Installation and Configuration

The plugin consists of two files:
1
plugin_intranda_step_LZA_EWIG.jar
2
plugin_intranda_step_lza_ewig.xml
Copied!
The file plugin_intranda_step_LZA_EWIG.jar contains the program logic and must be installed in the following directory so that it is readable for the tomcat user:
1
/opt/digiverso/goobi/plugins/step/
Copied!
The plugin_intranda_step_lza_ewig.xml file must also be readable by the tomcat user and installed in the following directory:
1
/opt/digiverso/goobi/config/
Copied!
​ The following file serves to configure the plugin and must be structured as follows: ​
1
<?xml version="1.0" encoding="UTF-8"?>
2
<config_plugin>
3
<config>
4
<project>*</project>
5
<step>*</step>
6
<exportFolder>/opt/digiverso/</exportFolder>
7
<exportXmlLog>true</exportXmlLog>
8
<createManifest>true</createManifest>
9
10
<manifestParameter
11
name="SubmissionManifestVersion">2.0</manifestParameter>
12
<manifestParameter name="SubmittingOrganization">Example
13
organisation</manifestParameter>
14
<manifestParameter
15
name="OrganizationIdentifier">DE-1</manifestParameter>
16
<manifestParameter name="ContractNumber">1234567</manifestParameter>
17
<manifestParameter name="Contact">Mustermann,
18
Max</manifestParameter>
19
<manifestParameter name="ContactRole">Abteilungsleitung
20
Bibliothek</manifestParameter>
21
<manifestParameter
22
name="ContactEmail">[email protected]</manifestParameter>
23
<manifestParameter name="TransferCurator">Doe,
24
John</manifestParameter>
25
<manifestParameter
26
name="TransferCuratorEmail">[email protected]</manifestParameter>
27
<manifestParameter
28
name="SubmissionName">[Abteilungskürzel]_[eindeutiger
29
Name]</manifestParameter>
30
<manifestParameter
31
name="SubmissionDescription">${meta.singleDigCollection};Digitalisierungsprojekt
32
der ZLB</manifestParameter>
33
<manifestParameter
34
name="RightsHolder">${meta.rightsHolder};N/A</manifestParameter>
35
<manifestParameter
36
name="Rights">http://id.loc.gov/vocabulary/preservation/copyrightStatus/pub</manifestParameter>
37
<manifestParameter name="RightsDescription">''</manifestParameter>
38
<manifestParameter
39
name="License">${meta.AccessLicense};${meta.AccessStatus};https://creativecommons.org/publicdomain/mark/1.0/</manifestParameter>
40
<manifestParameter
41
name="AccessRights">${meta.AccessStatus};public</manifestParameter>
42
<manifestParameter
43
name="MetadataFileFormat">http://www.loc.gov/METS/</manifestParameter>
44
<manifestParameter
45
name="endpoint">https://goobi.example.com/api/endpoint/wi</manifestParameter>
46
</config>
47
</config_plugin>
Copied!
The <config> block is repeatable and can therefore define different parameters in different projects. The subelements <project> and <step> are used to check whether the present block should be used for the current step. First, the system checks whether there is an entry containing both the project name and the step name. If this is not the case, an entry for any project marked by the arbitrary project name and the step name used is searched for. If no entry is found, a search is performed for the project name and any steps, otherwise the default block is used, which contains both <project> and <step>.
The element <exportFolder> defines where in the file system the exported METS files are stored.
With <exportXmlLog> you can determine whether the XML log should also be exported and written to the METS file. The log contains information about the workflow.
The <createManifest> element controls whether a submission manifest should be created. If this is the case, the <manifestParameter> must also be configured.
Each <manifestParameter> consists of two parts, the name attribute, which contains the name of the parameter, and the text in which the desired field contents are configured. Both static texts and all variables known in Goobi can be used. Several parameters can be specified separated by semicolons. If the first value is not known because, for example, the configured metadata has not been filled in, the next value is then tried.

Settings in Goobi workflow

After the plugin has been installed and configured, it can be used within one step. To do this, the intranda_step_lza_ewig plugin must be selected within the desired task. The Automatic Task checkbox must also be selected.

​Precondition

​To use the plugin, you must be using Goobi workflow 3.0, install and configure the plugin correctly and integrate it correctly into the required workflow steps.

Miscellaneous

This step within Goobi workflow exports all the files required for EWIG Ingest. The upload itself is carried out via the intranda TaskManager. This is useful to avoid several upload processes running in parallel having conflicts with each other and slowing down the system. For uploads, see chapter 4.17 in the intranda TaskManager documentation.
Last modified 1yr ago