Fedora Export

Goobi plugin for exporting Goobi processes to a Fedora repository


This documentation describes the installation, configuration and use of the Fedora Export Plugin in Goobi workflow.




Source code


GPL 2.0 or newer


Goobi workflow 3.0 and newer

Documentation date



The plugin must be installed in the following folder:


There is also a configuration file, which must be located at the following location:



The configuration is done via the configuration file intranda_export_fedora.xml and can be adapted during operation.


    <!-- fedoraUrl: REST endpoint of the target Fedora application. -->

    <!-- useVersioning: If true, for each run of the export step, a new revision of the process will be created. Default is true. -->

    <!-- ingestMasterImages: If true, master images of the Goobi process will be ingested into the container /master. Default is true. -->

    <!-- ingestMediaImages: If true, derivate images of the Goobi process will be ingested into the container /media. Default is true. -->

    <!-- ingestMetsFile: If true, a METS/MODS file will be generated and ingested. Default is true. -->

    <!-- exportMetsFile: If true, the METS/MODS file will be exported into the given destination folder. Default is true. -->



REST Endpoint of the Fedora application


If true, the versioning of Fedora is used. In this case, each time the export step is executed, a new version of the process is created in the repository. The default value is true.


If true is set, the master images of the operation are exported to the subcontainer /master. The default value is true.


If true, the derivatives of the operation are exported to the /media subcontainer. The default value is true.


If true is set, a METS/MODS file is created and exported to the container. Default value is true.


If true is set, a METS/MODS file is created and written to the usual export folder (e.g. /hotfolder). Default value is true.


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/&lt;CatalogIdDigital>/

Examples of URLs after successful ingest to Fedora

URL of the data record


URL for the METS file


URL for the master images

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

URL for the derivatives of the images

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

Last updated