May 2021
Developments and innovations to Goobi workflow in May 2021

Coming soon

    Extension of the Archive Management Plugin
    Extended Java 11 support
    Adaptation of the export options
    Extension of the handling of museum data from LIDO

New functionality for full text editing in the metadata editor as ALTO files

For some time now, the Goobi workflow metadata editor has allowed OCR results to be viewed in text format. However, if you then discovered a recognition error, you were left with only three options:
    1.
    use the transcription plugin in Goobi workflow and export text instead of ALTO-XML, which however prevents the marking of search hits on an image in Goobi viewer.
    2.
    edit the ALTO file with a separate text editor in the file system. This is very time-consuming and hardly feasible for non-professionals.
    3.
    do not correct the recognition error and try to sleep peacefully anyway.
Since this Goobi workflow version there is a new possibility:
Above the image display, a new inconspicuous button is available to enter the Alto editor
You can use the new integrated ALTO editor within the metadata editor. The coordinates of the words are thus preserved and the full text can be edited almost like regular continuous text.
Within the ALTO editor you can navigate through the pages and edit the text.
Highlighting the lines and words allows it to be easily seen where on the page each word is printed.
The currently selected word is also highlighted on the image with a frame
The documentation for the new functionality can also already be found in the Goobi workflow manual available online:
https://docs.goobi.io/goobi-workflow-en/user/4/4.4

Layout adjustments in the metadata editor and faster loading times

When an action is triggered in the metadata editor, the entire page is rarely reloaded so that the workflow is not interrupted and the scroll position of the individual containers can be maintained. When refreshing the page in this way, the developer can decide exactly which parts of the page should be refreshed.
In the past, some actions also updated parts of the page where it was not necessary. As a result, some actions, such as setting the representative, took an unusually long time. We have completely checked the metadata editor for this problem and optimised the updating for all actions.

Avoiding unwanted caching for layouts

In the past, it was often the case that after an update, the first time you entered the just freshly updated Goobi, the layout and/or some stylings were completely broken. This was not because the developers did a bad job, but because browsers like Chrome or Firefox cache files on the local device to save resources and bandwidth. The files are only re-downloaded from the server if they have changed. Therefore, it sometimes happened after an update that old files were mixed with new files and therefore the layout was broken. In this case, the page had to be completely reloaded (with the key combination Ctrl+Shift+R) to discard the cached files and reload them.
To prevent this from happening in the future, we now append a unique text associated with the version to the address of each file that could potentially be cached locally for each Goobi release. This way, the browser will always request a new file for new versions and the layout will look correct immediately after the update, without having to press secret key combinations.
The internal version numbers are reused in the source code of the generated HTML pages to avoid unwanted caching.

Better handling of processes without metadata

Goobi workflow is used in many different ways. For example, there are some institutions that are not interested in metadata in METS/MODS or LIDO format. For these institutions it has been noticed that script calls mandatorily require a meta.xml file in the task folder, otherwise they are aborted with an error. This has now been changed so that the meta.xml file is only read for script calls if metadata information is actually required within the script call.
For workflows where the files do not exist or have already been deleted, scripts now continue to work if they do not rely on the metadata.

Adjustments to the functionality of GoobiScript

After the GoobiScript runtime was completely re-implemented last month, some problems with GoobiScripts from plugins still arose that caused the plugins not to work properly. These problems have now been fixed and everything is working as usual again.
Corrections to GoobiScript

New functions and setting options of the dashboard

The enhanced dashboard has been extended even further. There are two new widgets: The widget Changes in the last 7 days shows steps that were completed, in progress or had errors in the last 7 days. The second new widget shows the steps that are currently in the queue. This is based on the new INFLIGHT status introduced last month.
The revised dashboard allows individual definition of the positions for the widgets
Another new feature is that the layout of the dashboard can now be configured individually via the user settings. This configuration can be done by editing the setting Arrangement of dashboard elements within the user-specific User configuration in the tab General. Each line within the text box adds an element to the dashboard. Each line consists of two parts, separated by a space: First is a number that specifies the column in which the widget is to be displayed. The second part after the space is then the name of the widget to be added.
The list of currently available widgets is: assignedSteps, batches, htmlBox, itm, processSearch, processTemplates, queue, rss, statisticsProcesses2, statisticsProcesses, taskHistory, tasksLastChanges.
An example configuration could look as follows:
1
1 processSearch
2
1 assignedSteps
3
1 tasksLastChanges
4
1 taskHistory
5
1 htmlBox
6
2 statisticsProcesses
7
2 processTemplates
8
2 queue
9
3 rss
Copied!
Editing the contents of the dashboard
Last modified 3mo ago