Aim 2.6A: Assessment of data propagation and provenance

[schristley]

This aim is about managing and propagating changes. The decisions we make to support this will directly flow into the integration aims. Our goal is to automate these processes as much as possible while still leaving a "human in the loop".

• [ ] Formalize interfaces between AK and data repositories
• [ ] Detecting data changes (add, modify, delete) in repositories
• [ ] Planning and execution of downstream processes to incorporate data changes
• [ ] Detecting schema changes in repositories
• [ ] Transition processes to new schema versions
• [ ] Auto-provenance of propagated changes

[schristley]

• [ ] Formalize interfaces between AK and data repositories

Formalize with OpenAPI V3 specification. In particular, this solidifies the schema (request and response) and places it under version control. ADC already provides this. OGRDB is under development with #36 . VDJbase, IRAD and IEDB still need specification.

Managing data changes should likely be handled through versioned (timestamped) data releases.