Skip to content
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

run_processor: do we really _always_ want to save_mets() ? #1306

Open
bertsky opened this issue Feb 17, 2025 · 0 comments
Open

run_processor: do we really _always_ want to save_mets() ? #1306

bertsky opened this issue Feb 17, 2025 · 0 comments
Assignees

Comments

@bertsky
Copy link
Collaborator

bertsky commented Feb 17, 2025

workspace.save_mets()

Now that we have the METS Server option, we should reconsider this behaviour. It gets used in both the standard processor CLI (via ocrd_cli_wrap_processor) and in ocrd_network (via invoke_processor).

At least the latter should be able to opt out of intermediate METS serialization. (Should only be done when stopping the METS Server.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants