This export plugin allows a very flexible export of Goobi processes based on individual configuration.
| Name | Wert |
|---|---|
This documentation describes how to install, configure and use an export plugin in Goobi.
Using this export plugin for Goobi, Goobi operations can be exported to multiple locations simultaneously within one operation.
This plugin is integrated into the workflow in such a way that it is executed automatically. Manual interaction with the plugin is not necessary. For use within a work step of the workflow, it should be configured as shown in the screenshot below.
The plugin must first be copied into the following directory:
In addition, there is a configuration file that must be located in the following place:
The plugin is configured via the configuration file plugin_intranda_export_configurable-base.jar and via the project settings. The configuration can be adjusted during operation. The following is an example configuration file:
The block <config> is repeatable and can thus define different metadata in different projects. The block with <project>*</project> is applied if no block with the project name of the project exists.
The includeFolders block is located inside each config element. It controls which directories are to be taken into account for the export.
If the attribute enabled is set to false, then no export of the corresponding folder will take place.
The configuration of the destination folder can be done within the project settings in the Goobi workflow user interface. If the checkbox for Create task folder is set there, the task will be stored in a subfolder with its title as name in the target folder.
| Parameter | Explanation |
|---|---|
| Parameter | Explanation |
|---|---|
project
This parameter determines for which project the current block <config> should apply. The name of the project is used here. The <config> block with the project * is always used if no other block matches the project name.
target
This parameter has 3 mandatory attributes: In the key parameter, a Goobi variable of the form {meta.metadata name} should be used. The attribute value can then be used to specify the desired value. If value="" is set, the condition will be met if the metadata is empty or not set. The attribute projectName should contain the name of the export project with whose settings the export is to take place. If an empty string is assigned to the attribute projectName="", the settings of the project of the operation will be used for export. If no target condition is set, a normal export will be performed. An export is triggered for each target condition that applies.
includeMarcXml
This parameter determines whether any existing MARC-XML data should be embedded in the exported metafile. The default value is false.
media
Here you can define whether and how the media folder should be exported.
master
Here you can define whether and how the master folder should be exported.
ocr
Here you can define whether and how the ocr folder should be exported.
source
Here you can define whether and how the source folder should be exported.
import
Here you can define whether and how the import folder should be exported.
export
Here you can define whether and how the export folder should be exported.
itm
Here you can define whether and how the TaskManager folder should be exported.
validation
Here you can define whether and how the validation folder should be exported.
genericFolder
Here you can define a folder free configurable that should be exported.
sourceFolderSuffix
This sub-element of the ocr element is needed when using OCR folders with different suffixes. It specifies which OCR folders should be exported. If not specified, then all OCR folders will be exported.
destinationFolder
This sub-element of all folder elements except ocr allows you to configure which files are to be exported to which folder using its two attributes name and exportFileRegex
Identifier
intranda_export_configurable
Repository
Licence
GPL 2.0 or newer
Last change
07.09.2024 08:52:10
