| Review of PC's original request: Recommend to PC by : 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 Logs report incorrect information
What is the canonical version of the database? 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
|
| Map of data flow was suggested last meeting | | Creation of map with 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 How can we verify what the data looks like with LDP/API? Is this adequate? Also use data export as verification, or try to.
|