This documentation describes the installation, configuration and use of the Fedora Export Plugin in Goobi workflow.
Details | ​ |
Identifier | intranda_export_fedora |
Source code | ​https://github.com/intranda/goobi-plugin-export-fedora​ |
Licence | GPL 2.0 or newer |
Compatibility | Goobi workflow 3.0 and newer |
Documentation date | 19.02.2019 |
The plugin must be installed in the following folder:
/opt/digiverso/goobi/plugins/export/plugin_intranda_export_fedora*.jar
There is also a configuration file, which must be located at the following location:
/opt/digiverso/goobi/config/intranda_export_fedora.xml
The configuration is done via the configuration file intranda_export_fedora.xml
and can be adapted during operation.
<config_plugin>​<!-- fedoraUrl: REST endpoint of the target Fedora application. --><fedoraUrl>http://localhost:8888/fedora/rest</fedoraUrl>​<!-- useVersioning: If true, for each run of the export step, a new revision of the process will be created. Default is true. --><useVersioning>true</useVersioning>​<!-- ingestMasterImages: If true, master images of the Goobi process will be ingested into the container /master. Default is true. --><ingestMasterImages>true</ingestMasterImages>​<!-- ingestMediaImages: If true, derivate images of the Goobi process will be ingested into the container /media. Default is true. --><ingestMediaImages>true</ingestMediaImages>​<!-- ingestMetsFile: If true, a METS/MODS file will be generated and ingested. Default is true. --><ingestMetsFile>true</ingestMetsFile>​<!-- exportMetsFile: If true, the METS/MODS file will be exported into the given destination folder. Default is true. --><exportMetsFile>true</exportMetsFile>​</config_plugin>
Parameter | Description |
| REST Endpoint of the Fedora application |
| If |
| If |
| If |
| If |
| If |
An export step must be configured:
Export DMS
Automatic task
Plugin for step: FedoraExport
When the step is executed, the Goobi process is exported (in the same way as it is exported to the file system) to the configured Fedora Repository, taking into account the configuration (see above).
The process data can then be retrieved from the repository using the following URL pattern:
http(s)://<Fedora REST endpoint>/records/<CatalogIdDigital>/
​http://localhost:8888/fedora/rest/records/PPN123456789/​
​http://localhost:8888/fedora/rest/records/PPN123456789/PPN123456789.xml​
​http://localhost:8888/fedora/rest/records/PPN123456789/master/master_00000001.tif http://localhost:8888/fedora/rest/records/PPN123456789/master/master_00000002.tif http://localhost:8888/fedora/rest/records/PPN123456789/master/master_00000003.tif​
​http://localhost:8888/fedora/rest/records/PPN123456789/media/00000001.tif http://localhost:8888/fedora/rest/records/PPN123456789/media/00000002.tif http://localhost:8888/fedora/rest/records/PPN123456789/media/00000003.tif​