OCR for image files

[liseandtea]

• As an FOI Mod App user
• I want to convert the text in images/scans into machine-encoded text
• so that it can be searched

Assumptions & Scope What are the assumptions for this story?

Assumption is that we use the Records Review app OCR capability. This will required to enable integrated, global search from within the Records Review app

What is IN scope? All image records are being uploaded into the redaction app.

Redlines that are exported as a PDF from the app will already be OCR'd so that other interest holders can search these PDF.

What is NOT in scope? Non-image file types

Acceptance Criteria

Scenario 1: Uploading image files

• GIVEN an FOI Mod user has a records package with image files that contain text (e.g. scanned records)
• WHEN they are loaded as PDFs into the redaction app
• THEN the PDFs will be automatically run through OCR

Scenario 2: Starting a search in converted image files

• GIVEN an FOI Mod user has the search pane open
• AND they have entered a keyword
• WHEN the FOI Mod User clicks on the search option
• THEN the application will search for that text, including on pages that have been OCR'd

Scenario 3: Searching in converted image files

• GIVEN an FOI Mod user has completed a search action
• WHEN the search completes
• THEN the results will list in the search panel

Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)

Validation Rules? (If yes, list here)

Design @xxx - please link the Design here

Definition of Ready

1. [ ] Is there a well articulated User Story?
2. [ ] Is there Acceptance Criteria that covers all scenarios (happy/sad paths)?
3. [ ] If there is a user interface, is there a design?
4. [ ] Does the user story need user research/validation?
5. [ ] Does this User Story needs stakeholder approval?
6. [ ] Design / Solution accepted by Product Owner
7. [ ] Is this user story small enough to be completed in a Sprint? Should it be split?
8. [ ] Are the dependencies known/ understood? (technical, business, regulatory/policy)
9. [ ] Has the story been estimated?

Definition of Done

1. [ ] Passes developer unit tests
2. [ ] Passes peer code review
3. [ ] If there's a user interface, passes UX assurance
4. [ ] Passes QA of Acceptance Criteria with verification in Dev and Test
5. [ ] Confirm Test cases built and succeeding
6. [ ] No regression test failures
7. [ ] Test coverage acceptable by Product Owner
8. [ ] Ticket ready to be merged to master or story branch
9. [ ] Developer to list Config changes/ Update documents and designs
10. [ ] Can be demoed in Sprint Review
11. [ ] Tagged as part of a Release
12. [ ] Feature flagged if required
13. [ ] Change Management activities done?

[liseandtea]

@lmullane @m-prodan @KyEggleston Feedback please!

[lmullane]

Confirm with developers that once OCR'd the redline that is exported will also be able to be searched in Adobe.

[abin-aot]

OCR - itself is POC at this moment, so I can update it after the POC