bcgov / foi-file-conversion

Apache License 2.0
0 stars 0 forks source link

Convert Excel to PDF #5

Closed lmullane closed 3 years ago

lmullane commented 3 years ago

As a Flex team analyst, I want Excel files pre-processed so that I can load them into Intella to create one PDF for redaction that can easily be created with no errors or delays

Acceptance Criteria

Scenario 1: Convert Excel files (XLS, XLSX) into a PDF

Happy path Scenario 2: Scale Excel file(s) onto a single PDF

Scenario 3: Create PDF page for each worksheet

GIVEN a Call for Records folder on the LAN contained Excel or iCalendar files WHEN these files are processed and converted to PDF THEN a subfolder called 'Output' will be saved as a subfolder of the original folder on the LAN Scenario 2: Save processed files in Output folder

Scenario 5: Save in Output folder

GIVEN a Call for Records folder on the LAN contained Excel or iCalendar files WHEN these files are processed and converted to PDF THEN these processed PDFs are saved in the 'Output' folder

Dependencies?

Technical:

Validation Rules? (If yes, list here)

Design This is a backend process with no user interface.

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 commented 3 years ago

@abin-aot, @divyav-aot , please review the Acceptance Criteria, aka scenarios

lmullane commented 3 years ago

Agreed. Let's discuss in refinement how we will do that.

m-prodan commented 3 years ago

AC looks good to me - did we want to add a criteria that the PDF integrates with Intella and can still be de-duplicated? We know this is possible from @abin-aot testing, just wondering if it needs to be added to the AC for this story.

lmullane commented 3 years ago

@m-prodan, updated Scenario 1 to capture that point.

lmullane commented 3 years ago

Team discussion - for edge case large Excel files (i.e. columns cannot be easily printed to another page) another solution may be required.