November
Developments and news about Goobi workflow
Last updated
Developments and news about Goobi workflow
Last updated
After extensive testing, the internal management of program libraries and interaction with the 170 plug-ins currently available were converted to . This allows for easier use of repeatedly required functionalities via integrated modules and libraries. As in the past, the switch from to Maven still allows the *.war
file and a *.jar
file to be compiled that can be installed in an application server such as .
With the pom.xml available within Maven projects, it is now relatively easy for anyone interested to download and compile a Goobi from Github themselves, or to develop one themselves with commands such as:
These calls download the source code of Goobi from Github and compile it afterwards. The file goobi.war
existing in the module-war/target/
directory can then be installed in the application server.
Goobi has been enhanced for a new step type: the HTTP step
. GET
, POST
and PUT
requests can be executed automatically here.
If the call is successful and the status code 20x
is returned, the work step (if configured in this way) is closed. Any error messages that occur are stored in the process log and can therefore be traced afterwards.
The following screenshot shows an example configuration for calling the TaskManager OCR plugin:
The configuration used here uses POST and sends it to the address http://localhost:8080/itm/service
:
Goobi workflow now supports the ability to create JSON Web Tokens (JWT) that allow access to the API for a specified time. These JWTs are provided as variables within HTTP calls. So far the JWT {changesteptoken}
already exists, which allows to change a certain work step.