March 2021
Developments and innovations to Goobi workflow in March 2021

Coming soon

  • Extension of metadata group support
  • Flex editor for capturing manuscripts and more
  • New pagination type for double pages
  • Markup of double pages in METS
  • Support for IIIF URLs within the Variable Replacer

GoobiScript conversion

GoobiScripts have become an indispensable part of the Goobi user's toolbox. However, although they are extremely practical and helpful, there were always problems with stuck queues or high system load when many GoobiScripts were waiting to be executed. There were also problems with parallel execution from time to time. These problems are now all a thing of the past, as the internal GoobiScript management and execution have been completely rethought and implemented. As a result, GoobiScript is now more efficient than ever before.
Numerous GoobiScripts in the queue

Tiered rights for GoobiScript

Goobi workflow allows GoobiScript to perform extensive operations to influence processes, their workflows, metadata or other areas, and to apply this uniformly to thousands of processes at once. In this respect, GoobiScript is often a great help when it comes to mass changes. Unfortunately, in the past these options were only available to a very limited group of users, as GoobiScript could of course also be used to inadvertently intervene in the processes in a major way, which meant that often only administrators had access to GoobiScript.
With the new developments in the rights system of Goobi workflow, there have been some improvements in this respect, so that it is now possible to grant individual user groups selected rights for the execution of defined Goobi scripts. In this way it is possible, for example, to allow users to execute the GoobiScript for performing the export even for many processes, but not other Goobi scripts such as changing metadata or intervening in the workflow.
Access to some selected GoobiScripts for the user
The configuration of these rights is kept relatively simple. Individual commands can be specifically added here in the user group area, as can be seen in the following screenshot.
Assigning individual rights to execute selected Goobi scripts
The revised rights management for controlling access to GoobiScript is clearly described within the Goobi manual. You can read about it here:
6. User groups
Goobi workflow (English)
https://docs.goobi.io/goobi-workflow-en/manager/6#individual-goobiscripts
By the way, we have also significantly revised the documentation of the GoobiScripts in general to better explain their execution and operation. This documentation can still be found at the following address:
7.4. GoobiScript
Goobi workflow (English)
https://docs.goobi.io/goobi-workflow-en/manager/7/7.4

Improved handling for message queues

The fact that computationally intensive or time-consuming automatisms can be executed via a so-called message queue is still relatively new and brings enormous advantages, especially for larger projects, because in this way, for example, the calculations can also be distributed over several servers. What we have revised here is that tasks that got stuck during processing because one of the available queues was not accessible no longer remain in an uncertain state. Instead, they are now set to a formal error status, so that their faulty processing becomes apparent and their execution can be corrected accordingly.

New step status for automatic workflow steps

A completely new step status INFLIGHT has been introduced. This new status is set when an automatic workflow step is to be processed on another system, is transferred there, but has not yet been picked up by the external system and is accordingly not yet processed. With this new step status, it is possible to check at any time how busy the entire system is and whether additional servers should be connected to process computationally intensive tasks.

Accessibility: Links become buttons

For good accessibility, it is particularly important that HTML elements have the right semantics. For example, a <a> (a link, or anchor) means that a new page is being entered and not that an action is being performed. A <button>, on the other hand, indicates that an action is being carried out. For historical-technical and also visual reasons, every action in Goobi workflow was previously implemented as a link. In the course of the great accessibility efforts of the last few months, we have also made major changes here. All links that actually trigger an action and are not only used for navigation have been converted into buttons.
The numerous navigation elements were changed to buttons for better accessibility
This change should not affect the appearance of the website for the user. If there are any functional surprises because one of the numerous changes did not go smoothly, we would be pleased to receive feedback so that we can make adjustments if necessary.

Individual validation messages for metadata

Long requested and now they are here: customisable validation messages in the metadata editor.
For the very granular controllable validation checks that can be defined within the rule sets, messages were displayed in the metadata editor in the past that were not understandable for everyone because they were too technical. With the developments in this context, these messages are now controllable and can be specified individually and multilingually within the rule sets. Within the rule sets, this looks like this, for example:
1
<MetadataType>
2
<Name>DocLanguage</Name>
3
<language name="de">Sprache</language>
4
<language name="en">Language</language>
5
<language name="es">Idioma</language>
6
<validationExpression>[a-z]{3}</validationExpression>
7
<validationErrorMessage name="de">Der Wert muss ein dreistelliger ISO 639 Code sein. Vorgefunden wurde jedoch der Wert '{}'.</validationErrorMessage>
8
<validationErrorMessage name="en">The value '{}' does not correspond to a three-letter ISO 639 code.</validationErrorMessage>
9
</MetadataType>
Copied!
In the user interface, this message is then displayed accordingly in the event of a violation of the validation requirements, for example:
Better validation messages in the metadata editor

Local translation files are created at start-up if they do not exist

Goobi workflow has local translation files located in the configuration directory. The translations stored in these files overwrite the translations provided by Goobi workflow itself. In this way it is possible to use individual texts in each Goobi workflow instance that are to be displayed in the user interface.
Goobi always monitors these files for changes and reloads these local translations if anything has changed in the files. However, this routine only works if the files are already available when Goobi is started. In the past it often happened that Goobi had to be restarted just to change or display a translation. With the changes we have now made, Goobi also checks on start-up whether all the translation files it may need are available in the corresponding directory and creates any missing files automatically.

Automatic workflows can now be paused

By means of a setting in the process details, the processing of automatic workflow steps can now be paused in individual processes. This is particularly useful if a work has been imported into Goobi workflow earlier than planned, but the rest of the workflow takes place fully automatically. By making this change, the automatic export that should not yet take place can be prevented by just two clicks.
Pausable automatic within a process

Pausing grouped automatic workflow steps (job types)

In the menu Administration there is now a new menu item Automatic Steps. This makes it possible to group automatic steps into so-called "job types". These job types can then be paused. This allows several fully automatic processes to be paused at once at a specific point. When the job type is started again at a later time, all paused steps are started again.
Pauseable tasks within groups

JWT authentication for all endpoints in the Goobi API

Goobi workflow allows to authenticate requests to its API via JSON Web Token (JWT). Such JWTs are created by Goobi workflow itself and sent to a third party service, which later uses them to legitimise the execution of an action in Goobi. The use of such a JWT method has the great advantage that a JWT only ever authenticates a very specific endpoint (for example, to complete a single workflow step from a single concrete process). Furthermore, this approach allows such a JWT to expire after a certain time. Thus, the potential loss of a JWT is also much less problematic than the loss of a token or password that is valid indefinitely for multiple endpoints.
To use this functionality, a central JWT secret must be stored within the central configuration file of Goobi workflow goobi_config.properties. For example, the configuration may look like this:
1
jwtSecret = MySecretForJwt
Copied!

Support for corporate bodies within the metadata editor

After several months of work, Goobi workflow now fully supports corporate bodies. These are now listed as a separate section within the metadata editor, similar to People, Metadata and Metadata Groups, and allow multiple associated metadata to be captured.
Corporations as a separate area within the metadata editor
Of course, it has also been taken into account that the connection to common standards databases is supported. Correspondingly, it is now also possible to search for corporate bodies and transfer their data.
Search for corporate bodies within standards databases
The definition of entities is explained within the central UGH documentation for processing metadata:
3.1. Definition of metadata types
UGH (English)
https://docs.goobi.io/ugh-en/3/3.1#3-1-3-corporate-bodies

Easier configuration of multiple projects

A central configuration file of Goobi workflow is the file goobi_projects.xml. It primarily controls how the creation screen for processes should behave, which fields should be displayed and to what extent this should vary per publication type.
Basically, this configuration of Goobi is already one of the more complex files and not necessarily self-explanatory. In addition, up to now this configuration file has in principle allowed different configurations to be defined for different projects. To do this, however, the entire, usually very extensive blocks had to appear several times in the file, which often led to unnecessary redundancies and repetitions. With a change at this point, this configuration should now become somewhat simpler and avoid such repetitions. Therefore, the previous 'project' elements now allow a repeatable naming of several project names for which the respective section is to apply. A direct comparison makes it easy to see where the innovations are:

Previous configuration

Previous configuration of multiple projects where the configuration for the 'manuscript project' and the 'archive project' is identical and differs from the 'default':
1
<?xml version="1.0" encoding="UTF-8"?>
2
<goobiProjects>
3
4
<project name="Manuscript-Project">
5
<createNewProcess>
6
7
<itemlist>
8
<item from="werk" multiselect="false">
9
Font type
10
<select label="Antiqua">Antiqua </select>
11
<select label="Gothic"> Gothic </select>
12
<select label="Mixed">Mixed </select>
13
</item>
14
15
<!-- Title for Monograph and Periodical -->
16
<item docstruct="topstruct" from="vorlage" isnotdoctype="multivolume" metadata="TitleDocMain" required="true" ughbinding="true"> Title </item>
17
</itemlist>
18
19
<opac use="true">
20
<catalogue>Library of Congress</catalogue>
21
</opac>
22
23
</createNewProcess>
24
</project>
25
26
<project name="Archive-Project">
27
<createNewProcess>
28
29
<itemlist>
30
<item from="werk" multiselect="false">
31
Font type
32
<select label="Antiqua">Antiqua </select>
33
<select label="Gothic"> Gothic </select>
34
<select label="Mixed">Mixed </select>
35
</item>
36
37
<!-- Title for Monograph and Periodical -->
38
<item docstruct="topstruct" from="vorlage" isnotdoctype="multivolume" metadata="TitleDocMain" required="true" ughbinding="true"> Title </item>
39
</itemlist>
40
41
<opac use="true">
42
<catalogue>Library of Congress</catalogue>
43
</opac>
44
45
</createNewProcess>
46
</project>
47
48
<project name="default">
49
<createNewProcess>
50
51
<itemlist>
52
<!-- Title for Monograph and Periodical -->
53
<item docstruct="topstruct" from="vorlage" isnotdoctype="multivolume" metadata="TitleDocMain" required="true" ughbinding="true"> Title </item>
54
</itemlist>
55
56
<opac use="true">
57
<catalogue>K10Plus</catalogue>
58
</opac>
59
60
</createNewProcess>
61
</project>
62
</goobiProjects>
Copied!

New configuration

Future configuration of several projects to be treated in the same way combined in one block:
1
<?xml version="1.0" encoding="UTF-8"?>
2
<goobiProjects>
3
4
<project>
5
<name>Manuscript-Project</name>
6
<name>Archive-Project</name>
7
<name>Biology.*</name>
8
<createNewProcess>
9
10
<itemlist>
11
<item from="werk" multiselect="false">
12
Font type
13
<select label="Antiqua">Antiqua </select>
14
<select label="Gothic"> Gothic </select>
15
<select label="Mixed">Mixed </select>
16
</item>
17
18
<!-- Title for Monograph and Periodical -->
19
<item docstruct="topstruct" from="vorlage" isnotdoctype="multivolume" metadata="TitleDocMain" required="true" ughbinding="true"> Title </item>
20
</itemlist>
21
22
<opac use="true">
23
<catalogue>Library of Congress</catalogue>
24
</opac>
25
26
</createNewProcess>
27
</project>
28
29
<project name="default">
30
<createNewProcess>
31
32
<itemlist>
33
<!-- Title for Monograph and Periodical -->
34
<item docstruct="topstruct" from="vorlage" isnotdoctype="multivolume" metadata="TitleDocMain" required="true" ughbinding="true"> Title </item>
35
</itemlist>
36
37
<opac use="true">
38
<catalogue>K10Plus</catalogue>
39
</opac>
40
41
</createNewProcess>
42
</project>
43
</goobiProjects>
Copied!
Documentation on the structure of the configuration file goobi_projects.xml can be found at the following URL:
7.6 goobi_projects.xml
Goobi workflow (English)
https://docs.goobi.io/goobi-workflow-en/admin/7/7.6
Last modified 4mo ago