-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OCR-D Workflow integration (without entity implementation) #5809
Conversation
…mprove variable replace to replace OCR-D workflow identifier
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Kitodo/src/main/java/org/kitodo/production/services/ocr/OcrdWorkflowService.java
Outdated
Show resolved
Hide resolved
Kitodo/src/main/webapp/WEB-INF/templates/includes/processEdit/details.xhtml
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Kitodo/src/main/java/org/kitodo/production/services/ocr/OcrdWorkflowService.java
Outdated
Show resolved
Hide resolved
Kitodo/src/main/java/org/kitodo/production/services/ocr/OcrdWorkflowService.java
Outdated
Show resolved
Hide resolved
Kitodo/src/main/java/org/kitodo/production/services/ocr/OcrdWorkflowService.java
Outdated
Show resolved
Hide resolved
Kitodo/src/main/java/org/kitodo/production/forms/ProcessForm.java
Outdated
Show resolved
Hide resolved
Kitodo/src/main/java/org/kitodo/production/forms/ProcessForm.java
Outdated
Show resolved
Hide resolved
Kitodo/src/main/java/org/kitodo/production/forms/ProcessForm.java
Outdated
Show resolved
Hide resolved
Kitodo/src/main/java/org/kitodo/production/forms/TemplateForm.java
Outdated
Show resolved
Hide resolved
Kitodo/src/main/java/org/kitodo/production/forms/TemplateForm.java
Outdated
Show resolved
Hide resolved
Kitodo/src/main/java/org/kitodo/production/forms/TemplateForm.java
Outdated
Show resolved
Hide resolved
@markusweigelt I think you need to rename your SQL migration file because there already is another |
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. |
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 usingPair
objects to combine ID and name instead of using a simple string list.ocrd.workflows.directory
parameter(ocrdworkflowid)
placeholder