Solutions to address immediate data integrity problems. Solutions can involve architecture, testing plans, development guidelines, Definition of Done, documentation, and analysis of SRS design/intended use, etc...
Strategy to prevent data integrity issues from arising again.
Strategy to build trust in FOLIO SRS (and related) data integrity
Improving confidence in DI:
Logging
Ability to track data through the DI flow
Error messaging in all apps that interact with MARC
Users lose confidence when told to ignore error messages
Logs report incorrect information
What is the canonical version of the database?
Log says "created SRS record"
SRS full of unused, incorrect records
Ordering of MARC and inventory steps in a job can negate later update
Visual would make this easier to understand
Data integrity issues
ie, deleting instance status updated date
issues created in one release live on in the data to future releases even if the issue is fixed
Documentation still needed
technical docs
user docs
Map of data flow was suggested last meeting
Creation of map with
data flow
pain points
affected user roles/people who use X data
Ideal workflow vs what's there now vs design?
Connected visualizations to allow depth at given waypoints
Each pick an area and see how they connect
DI where it creates export in SRS storage, what comes out?
How can we verify what the data looks like with LDP/API? Is this adequate? Also use data export as verification, or try to.
What would it mean to see the database? What is LDP/API missing, if anything?
Upgrade to MetaDB should make it a better tool for this
Next steps
How to be comprehensive
How to ensure it is acted upon
High level view, with things called out and highlighted
Not looking for a bug for each thing, but something more systemic