Stanford Export
Goobi Plugin for the Export of Goobi Processes to the Stanford University Digital Library
Overview
Introduction
The present documentation describes the installation, configuration, and use of the Stanford Export Plugin in Goobi workflow.
Installation
To be able to use the plugin, the following files must be installed:
In addition, there is a configuration file that must be located at the following location:
To use the plugin, it must be selected in a workflow step:
Overview and functionality
An export step must be configured:
Export DMS
Automatic task
Plugin for workflow step:
intranda_export_stanford
During the execution of the step, an export of the Goobi process (similar to exporting to the file system) is performed into the configured directory.
Within this directory, subfolders are created based on the identifier. For example, the identifier qx797sg1405
would generate the following structure: /path/to/folder/qx/797/sg/1405
. Within this folder, two additional folders are created: metadata
and content
.
In the content
folder, all generated images, and if available, the ALTO files and single-page PDFs are stored. Additionally, a complete PDF file is generated from the single pages. The metadata
folder contains an XML file with information about the files within the content folder.
Finally, the configured URL to the REST API is called to initiate the ingest into the system.
Configuration
The plugin is configured in the file plugin_intranda_export_stanford.xml
as shown here:
The following table contains a summary of the parameters and their descriptions:
Last updated