April 2020
Developments and innovations to Goobi workflow in April 2020
In the coming weeks we will probably focus on the following points:
- Refactorization of the LayoutWizzard plugin for automatic image cropping
- Conversion of the Goobi code to use CDI
The LayoutWizzard as a plugin for convenient cropping of images is becoming more and more popular. This was accompanied by the wish that its use should also be possible within the Amazon Cloud. For this reason, LayoutWizzard has now been revised so that it can be used on the S3 storage system in addition to a regular file system, just like Goobi workflow.

The LayoutWizzard plugin for cropping images using the example of double pages
For more information about the LayoutWizzard, please refer to the detailed documentation for operation and configuration options:
https://docs.goobi.io/goobi-workflow-plugins-en/step-plugins/layoutwizzard
docs.goobi.io
https://docs.goobi.io/goobi-workflow-plugins-en/step-plugins/layoutwizzard
Goobi workflow has been supporting the handling of 3D objects for several months now. This has already proved to be very useful for various data formats. However, handling very large files and their high-performance delivery and display was repeatedly a particular challenge. With the newly added functionality to support
DRACO
compression, the visualisation of qualitative 3D models has now become much better, as the file sizes are considerably smaller than in the previously supported formats.More information about compression using DRACO can be found here:
There is no significant change for the user in handling these new and already supported 3D formats. Objects can still be displayed, zoomed and rotated within the QA plug-in as well as within the METS editor as before.

3D objects visualised within the METS editor of Goobi workflow
Within the METS Editor, a user has also been able to manipulate the image stack for a long time, for example, to change the order of the files, delete files or even rename them. In the past, however, the operation of these functions was sometimes problematic, because after changes to the image stack, the METS file always had to be saved as well. With the revisions we have now made in this area, this is no longer necessary. Changes to files within the METS Editor are now always saved in the METS file as well, so that the METS file can no longer become asynchronous to the file names. In addition, we have conducted extensive testing to ensure that changes made will always affect all folders. For example, when renaming or deleting master files, derivative files, thumbnails, OCR results, LayoutWizzard files and also PDF files are immediately changed so that the changes made have the same effect in all versions of the digitised material.

Manipulations to the image stack in the METS Editor immediately affect all folders and the METS file
There was an error within the GoobiScripts
addStep
that prevented its execution. The GoobiScript has now been revised and is working again.
The GoobiScript createStep and its associated parameters