-
Notifications
You must be signed in to change notification settings - Fork 7
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
correct workflow #86
correct workflow #86
Conversation
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.
LGTM
|
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.
I suggest also discussing format conversion at the entry stage. (With pointers to our workspace
terminology and METS/PAGE specs.) That is: TEI to METS, ALTO to PAGE, or even just image/PAGE directories (ocrd-import
).
Co-Authored-By: Robert Sachunsky <[email protected]>
Co-Authored-By: Robert Sachunsky <[email protected]>
Co-Authored-By: Robert Sachunsky <[email protected]>
Co-Authored-By: Robert Sachunsky <[email protected]>
Co-Authored-By: Robert Sachunsky <[email protected]>
Co-Authored-By: Robert Sachunsky <[email protected]>
Co-Authored-By: Robert Sachunsky <[email protected]>
Co-Authored-By: Robert Sachunsky <[email protected]>
Co-Authored-By: Robert Sachunsky <[email protected]>
Co-Authored-By: Robert Sachunsky <[email protected]>
Co-Authored-By: Robert Sachunsky <[email protected]>
Co-Authored-By: Robert Sachunsky <[email protected]>
Co-Authored-By: Robert Sachunsky <[email protected]>
Co-Authored-By: Robert Sachunsky <[email protected]>
Co-Authored-By: Robert Sachunsky <[email protected]>
Co-Authored-By: Robert Sachunsky <[email protected]>
Co-Authored-By: Robert Sachunsky <[email protected]>
Co-Authored-By: Robert Sachunsky <[email protected]>
Co-Authored-By: Robert Sachunsky <[email protected]>
Co-Authored-By: Robert Sachunsky <[email protected]>
…to new_workflow update branches
Co-Authored-By: Robert Sachunsky <[email protected]>
Co-Authored-By: Robert Sachunsky <[email protected]>
Co-Authored-By: Robert Sachunsky <[email protected]>
Co-Authored-By: Robert Sachunsky <[email protected]>
Co-Authored-By: Robert Sachunsky <[email protected]>
Co-Authored-By: Robert Sachunsky <[email protected]>
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.
Regarding the line breaks in the tables, IMO generally it would be advisable to use code
plus pre
to prevent newlines and have typewriter style.
Co-Authored-By: Robert Sachunsky <[email protected]>
Co-Authored-By: Robert Sachunsky <[email protected]>
Co-Authored-By: Robert Sachunsky <[email protected]>
Co-Authored-By: Robert Sachunsky <[email protected]>
Actually, I was hoping for the above checks to be filled, esp.:
Since in GH I cannot comment/suggest outside of patch contexts, I have added my comments to the commit I found responsible via blame today, cf. b0eeb7a#commitcomment-38800544 Does anyone know who gets these and how I can control this? What's the proper way to do that within the PR context? |
Those are the easy changes to the worklow as discussed in the VC
Further tasks:
explain difference between clipping and resegment
probably change sequence of processing steps for block optimization
add links to available model repos and description of the most important models (https://wiki.de.dariah.eu/pages/viewpage.action?pageId=108140929 can be used as a starting point)
adjust the recommended workflows accordingly