The strength of Goobi workflow lies in the processing and control of workflows. For this purpose, the desired workflows are stored in advance in repeatedly applicable production templates. Such a production template describes any number of tasks, which in turn are subject to a predefined sequence. Typical examples of production templates include these:
- Standard workflow for digitization and publishing
- Digitization on Demand
- Mass import of a legacy data project
On the basis of such a production template, a process is created in Goobi for each object to be digitised. This then allows the tasks taken over from the production template to be processed. Each of these tasks is assigned to at least one user group or user and receives various rights, functions or plug-ins for data processing and validation. In this way, among other things, it is controlled whether such a task is executed manually by a user or fully automatically by the server.
For example, a prototypical workflow for digitizing books can consist of the following tasks:
Within Goobi workflow, the workflows and associated tasks are visualized as follows: