Step plugins are used to extend tasks within the Goobi workflow. Such plugins can be used, for example, to integrate individual functionality into the workflow that Goobi does not provide out-of-the-box. Examples of such plug-ins include special conversion plug-ins, entry masks, image manipulations, etc.
Such step plugins are installed in the folder:
If a plugin also has a user interface in addition to the actual functionality, the part of the user interface must also be installed in this folder:
Step plugins in Goobi are set up in such a way that they are selected as plugins within a task.
visibility,medium-visibility,large-visibility” class=””” id=”” animation_type=”” animation_direction=”left” animation_speed=”0.3″ animation_offset=”””]https://goobi.io/wp-content/uploads/goobi_workflow_plugin_step2.png[/fusion_imageframe]
Please note that there are currently three different types within Step Plugins:
||The plugin does not have its own user interface and is executed in the background on the server side. Example: A plugin for the automatic conversion of images into another file format.
||The plugin brings along a part for a user interface and is visually integrated within an edited task as if it were part of the Goobi core. Here the user can interact with the user interface. Example: A plugin for uploading images within a task.
||The plugin comes with a complete user interface. This is not directly integrated into the task. Instead, the user is offered a button to enter the plugin so that he can interact with it. Example: Plugin for image control.
Some Step Plugins have their own configuration file. This file is generally named like the plugin itself and is usually located at the following path: