Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Source of Truth Delivery/Tracking #4740

Open
jadudm opened this issue Mar 5, 2025 · 0 comments
Open

Source of Truth Delivery/Tracking #4740

jadudm opened this issue Mar 5, 2025 · 0 comments

Comments

@jadudm
Copy link
Contributor

jadudm commented Mar 5, 2025

Problem

The Source of Truth (SoT) aims to provide a single point of contact with the FAC's data. We need to bring this in, which involves touching multiple parts of the system. It is a blocker to other work until this lands.

Job Story(s)

To bring this in with confidence, we need:

  • Monitoring. We need to make sure that the SoT transition and destination are well-covered by NR dashboards/monitoring.
  • Migration. Data needs to move from the SAC table to SoT, and we need confidence that nothing changed in the process.
  • API. The API needs to deliver the exact same experience after the migration.
  • Testing. We want to know that both the SAC and SoT pathways yield data that is identical during the phased transition approach.
  • Cog/Over. We need the cog/over work to connect to the new SoT table.
  • Integration w/ the public-facing front-end. Search and Excel generation from the new SoT table.
  • Integration with the admin-facing UI. So we can still answer questions.
  • Hashing. We want to integrate row-level hashing as well as hashes of PDFs into the SoT tables.

What are we planning to do about it?

All those things.

How will we measure success?

We are going to have automated processes that verify and validate the data at every step of the way. We will have absolute confidence that no data changed or was lost through migration between structures.

Security Considerations

Required per CM-4.

If all mappings are correct, then all access controls (with respect to suppressed data) will continue to "just work." As part of our E2E testing strategy, we will confirm that this is true.

@github-project-automation github-project-automation bot moved this to Triage in FAC Mar 5, 2025
@jadudm jadudm moved this from Triage to In Progress in FAC Mar 5, 2025
@jadudm jadudm added this to the FY25 Q2 (Jan 1 - Mar 31) milestone Mar 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In Progress
Development

No branches or pull requests

1 participant