OCR-D Workflow integration (without entity implementation)

[markusweigelt]

This pull request re-implements the PR #5697 without the use of an explicit OCR-D workflow entity.

The workflows are currently selected from a directory that can be configured via the kitodo_config.properties. In the future, it should be possible to load OCR-D workflows through an OCR-D manager endpoint. This PR provides the preparation for this by using Pair objects to combine ID and name instead of using a simple string list.

• Add new authority to assign OCR-D Workflow
• OCR-D workflow directory can be configured using the ocrd.workflows.directory parameter
• Choose the OCR-D workflow from the workflows directory in the process template, or replace it within the process details.
• Incorporate the OCR-D workflow identifier as a shell script variable using the (ocrdworkflowid) placeholder
• Added documentation among others for the placeholder https://github.com/kitodo/kitodo-production/wiki/Workflow-Editor#platzhalter

[solth]

Code looks good, just some very minor change suggestions. (Please rebase your branch against the current master.)

This is just a code review. Functional review will follow.

[solth]

Code seems to work as intended. (Just some small comments - see below). I was able to configure a OCRD workflow for a template and later change it for individual processes.

Just one small remark I think could be improved upon:

I think the from Template option should contain information about which OCRD workflow it is that will be derived from the template, otherwise this might not be very informative (a user would first have to check the template to see if it defines a workflow appropriate for the current process and whether he has to change something in the process or not)

Also, there is a conflict in ProcessForm.java that needs to be resolved.

[solth]

@markusweigelt I think you need to rename your SQL migration file because there already is another V2_125... sql by now (added by you, too)!

[markusweigelt]

I think the from Template option should contain information about which OCRD workflow it is that will be derived from the template, otherwise this might not be very informative (a user would first have to check the template to see if it defines a workflow appropriate for the current process and whether he has to change something in the process or not)

Good point! I have now added the selected file from the template. If there is no selection in the project template, the message of no selection will be shown.