Convert Image files to PDF

[lmullane]

• As a ministry coordinator
• I want image files to be converted to PDF when I upload them into the Records log
• so that the files can be added to the linear Harms PDF for review

Assumptions & Scope The Records Review app can view and redact image files such as JPEG or PNG

These image files should be converted to PDF for 2 reasons:

1. Converting them to PDF will make it easier to stitch them into the PDFs for harms, redline and the final package

What are the implications for the handwritten notes (image files) commonly found in personal request records?

What is in and not in scope? Upload and dedupe by metadata has is covered in task #3465

Acceptance Criteria

Scenario 1: Convert image files to PDF

• GIVEN a ministry coordinator is on the records log
• WHEN the ministry coordinator uploads image files to the Records log (e.g. PNG, JPEG)
• THEN the image files will be converted to a PDF
• AND the image file will show with as a PDF on the log with a green check mark
• AND a copy of the record in the original file format will be kept

...

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?

[lmullane]

Not needed as we can stitch into harms, redlines and records package.