Migrate CANs from MAPS

[johndeange]

User Story

As a budget team member, I would like to have the CANs that are/were present in MAPS available in OPS in order to manage them effectively within OPS.

Acceptance Criteria

• A point-in-time snapshot of CAN tuples that are in the MAPS Oracle DB are available in one schema or another in the OPS Postgres DB using guidelines from OPRE about which attributes should persist or be dropped
• Additional CAN data is able to be provided by OPRE in a spreadsheet and imported into OPS by some manner allowing for any extra attributes of an OPS CAN
• If the CAN already exists in OPS, then the ingestion process should update the CAN instead of creating a new one.

---

Tasks

UX

Dev

• Data Analysis for migration of MAPS CANs #2657
• Update CAN model based on migration data analysis and new requirements #2658
• Translate MAPS CANs into OPS CANs #2662
• Extract MAPS CANs into CSV format #2659
• Receive updated CAN spreadsheet from budget team with added columns
• Clean MAPS CANs CSV file #2660
• Generate report of MAPS CANs that failed to import #2661
• Update CAN loading script to insert record into CANHistory #3294
• Add FUNDING_PARTNER to spreadsheet format and load #3343

Updates from CAN spreadsheet:

• Add new Portfolios #3295
• Update FUNDING_SOURCE #3296
• Update METHOD_OF_TRANSFER #3297

Definition of Done Checklist

• UI works as designed (UX team)
• 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

[jonnalley]

@johndeange should we specify something in the AC that alludes to upserting such that we don't have duplicate data or concurrency issues if repeated iterations of the migration are executed ?