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

Problem: Tesseract OCR command cannot be disabled through Preservation Planning #1630

Open
5 tasks
sromkey opened this issue Oct 2, 2023 · 0 comments
Open
5 tasks
Assignees
Labels
fpr Issues/enhancements related to the FPR including requests for new rules, etc Severity: low An inconvenient situation where the software is usable but could be better. Status: review The issue's code has been merged and is ready for testing/review. Type: bug A flaw in the code that causes the software to produce an incorrect or unexpected result.
Milestone

Comments

@sromkey
Copy link
Contributor

sromkey commented Oct 2, 2023

Expected behaviour

If any command is disabled in Preservation Planning, the rules should be disabled and the tool shouldn't run.

Current behaviour

This is working as expected for other types of commands e.g. Characterization, but if the Tesseract command is disabled under Transcription, it runs anyway.

The work around is to just to set it to "no" in the processing configuration, but filing it here as a bug just because it's inconsistent with other FPR actions.

Steps to reproduce

  • Go to Preservation Planning and under Transcription, disable the command
  • Ensure your processing configuration has Transcribe SIP contents set to Yes
  • Run through the OCR image sample transfer
  • When the AIP is made, observe that the OCR file has been created and is in the AIP.

Your environment (version of Archivematica, operating system, other relevant details)

Testing the 1.15 on Rocky 9

For Artefactual use:

Before you close this issue, you must check off the following:

  • All pull requests related to this issue are properly linked
  • All pull requests related to this issue have been merged
  • A testing plan for this issue has been implemented and passed (testing plan information should be included in the issue body or comments)
  • Documentation regarding this issue has been written and merged (if applicable)
  • Details about this issue have been added to the release notes (if applicable)
@sromkey sromkey added Severity: low An inconvenient situation where the software is usable but could be better. Type: bug A flaw in the code that causes the software to produce an incorrect or unexpected result. fpr Issues/enhancements related to the FPR including requests for new rules, etc labels Oct 2, 2023
@sromkey sromkey added this to the 1.17.0 milestone Jul 8, 2024
@replaceafill replaceafill added the Status: in progress Issue that is currently being worked on. label Jul 9, 2024
@Dhwaniartefact Dhwaniartefact added Status: review The issue's code has been merged and is ready for testing/review. and removed Status: in progress Issue that is currently being worked on. labels Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fpr Issues/enhancements related to the FPR including requests for new rules, etc Severity: low An inconvenient situation where the software is usable but could be better. Status: review The issue's code has been merged and is ready for testing/review. Type: bug A flaw in the code that causes the software to produce an incorrect or unexpected result.
Projects
None yet
Development

No branches or pull requests

3 participants