Importation and upserting of BL data from OPRE's authoritative records

[jonnalley]

User Story

As an OPRE budget team member, I want to provide a spreadsheet or similar matrix of data as input and have budget line data updated from that spreadsheet until such time as OPS has more features developed so that data can stay accurate for current OPS users for those users to make more informed decisions.

Acceptance Criteria

• Given a structure agreed-upon by Flexion and the OPRE budget team, OPS support personnel should be able to ingest a csv, tsv, or xlsx flat file of budget line data. Each budget line would consume one row in the file.
• Each new importation of the spreadsheet should be considered authoritative and supersede any prior update.
• For any distinct budget lines that already exist in the OPS database, any corresponding budget line found in a provided spreadsheet should update any differing budget line attributes in the database.
• For any distinct budget lines that do not already exist in the OPS database but are found in the provided spreadsheet, a record should be inserted and matched to the parent contract (which must already exist).
• Each budget line altered or created by this process should have a relevant and meaningful event/history record created for the parent agreement.
• The provided file need not be persisted after the importation/upserting process.
• Upserting success or errors should be recorded and observable in some efficient way.
• Providing a UI and Azure infrastructure necessary for OPRE personnel to do this themselves is not necessary as part of this story

---

Tasks

UX

Dev

Definition of Done Checklist

• PR(s) have been merged to main
• Design/tech debt eliminated
• New design/tech debt documented (if applicable)
• Build process updated
• Documentation updated or added
• Feature flags/toggles created

Additional Context & Resources