Since version 1.9.2, Goobi has allowed users to fully automate workflow tasks using plug-ins, e.g. to delete images that are no longer required. This ImageDeletion plug-in should be the last step in the workflow. When configuring this workflow step, it is important to note that it has to be an automated task and must be defined as a Step plug-in for the identifier intranda_step_imageDeletion.
Once configured, the workflow step plug-in is called automatically from within the workflow. An explanation of how this works is given below.
First, the plug-in starts the validation process for the JP2 derivative that has been generated. A check is then made to confirm the existence and validity of an AMD results file from SDB containing at least one object description. The subsequent final validation ensures that the number of objects in the master and media directories matches the number of objects described in the AMD file.
The images will not be deleted until these validations have been completed. At this point, the master and media directories will be deleted.
If the above validations fail, the workflow step will remain open. This will prevent automatic deletion, and the user will have to perform a manual validation before data can be deleted from the corresponding process.
Goobi automatically exports METS files to a pre-defined folder. This is usually the directory shown below:
A sub-folder is created in this directory for each process, and all the data being exported is copied within this new folder. As well as the actual METS file, this may include the anchor file, the images and OCR data.
Once the export has been completed, Goobi calls PostExport.jar. This program renames the exported METS file (so that the file name corresponds with the b-number) and merges it with the SDB-AMD file.
As a first step, this involves reading in the AMD file and for each element creating a mets:techMD element within the mets:amdSec section of the METS file. The second step involves checking all the FileGroups individually. The file name, checksum and Mime type are formed from the values in the AMD file. Finally, the structure elements of the physical structMap are linked to the individual techMD.
After this, the enriched METS file is written to the pre-defined folder, and from here the presentation can read in the data.
If the data includes multiple manifestation objects and one or more manifestations have already been exported, the anchor files are also merged. This involves entering into the logical structMap a new child element that contains the information for the new object. The sequence within the structMap is defined using the metadata item order number.
In most cases, an automatic task is combined with a script task. Goobi then responds to the script output. Goobi will treat any messages issued on the default output console as simple status reports and will continue operation. However, Goobi will treat any messages issued on the error output console as errors and will interrupt workflow processing.
One example for the combination of an automatic workflow task and a script task is the conversion of images to TIFF/JPEG. Goobi automatically calls a script and converts the images in the specified folder to TIFF/JPEG format.
The following example shows how Goobi calls a script for the intranda image improver:
The call involves providing two parameters. The first of these, convert_images, is defined in the script itself. Goobi replaces the other parameter {tifpath} dynamically by the path to the folder in which the image set is located.
Parameters can be combined with quotation marks (") to pass them as an argument to the called process. If a quotation mark is to be passed directly to the new process as an argument, it must be escaped with a preceding second quotation mark (then: "").
Goobi allows you to mark individual tasks as automatic. These tasks are opened and performed automatically once the preceding workflow task has been completed. Whenever an error occurs in such an automatic workflow task, that task will remain paused and will not be processed any further.
To mark a workflow task as automatic, you need to activate the Automatic task checkbox. This is located in the Task details box as shown in the following screenshot:
