Skip to content
This repository has been archived by the owner on Feb 7, 2025. It is now read-only.

Upload file with result count to Sharepoint #1683

Open
31 tasks
brick-green opened this issue Jan 6, 2025 · 0 comments
Open
31 tasks

Upload file with result count to Sharepoint #1683

brick-green opened this issue Jan 6, 2025 · 0 comments

Comments

@brick-green
Copy link

brick-green commented Jan 6, 2025

As the CDC, in order to understand how much the ETOR service is being used, I need to view the total number of ETOR results received in a file in sharepoint.

Pre-conditions

  • No automation needed at this time

Assumptions

  • This story will focus only on results that TI is aware of.

Acceptance Criteria

  • We've documented the process for determining the number of ETOR results received.
  • An a file has been uploaded to sharepoint with the total number of results

Research

  • Determine the Sharepoint folder
  • Determine the filetype and structure
  • Determine the filename
  • Determine frequency
  • Should the CDC ask or do we just send unsolicited
  • Should this be a new file or append existing?
  • If new files, what are retention (or what to do with them) rules for old files?

Engineering

  • Engineering work needed to complete the story
  • Foundational: Technical runway work to support this and future efforts

Definition of Done

  • Documentation tasks completed
    • Documentation and diagrams created or updated
      • ADRs (/adr folder)
      • Main README.md
      • Other READMEs in the repo
      • If applicable, update the ReportStream Setup section in README.md
    • Threat model updated
    • API documentation updated
  • Code quality tasks completed
    • Code refactored for clarity and no design/technical debt
    • Adhere to separation of concerns; code is not tightly coupled, especially to 3rd party dependencies
  • Testing tasks completed
    • Load tests passed
    • Additional e2e tests created
    • Additional RS e2e assertions created in the rs-e2e project for any new transformations. Includes improvements to the assertion code required to make the new assertions
  • Build & Deploy tasks completed
    • Build process updated
    • API(s) are versioned
    • Feature toggles created and/or deleted. Document the feature toggle
    • Source code is merged to the main branch

Note: Please remove any DoD items that are not applicable

Research Questions

  • Optional: Any initial questions for research

Decisions

  • Optional: Any decisions we've made while working on this story

Notes

  • Optional: Any reference material or thoughts we may need for later reference
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants