HTAN 1.0 Data Model: sunset planning

[aclayton555]

Initiate as part of 24-5 sprint.

This ticket (likely one of several to emerge from this ticket) to facilitate scoping and planning of actions related to sunsetting the HTAN data model through the end of HTAN 1.0 (current end date August 31, 2024). Consider a phased approach:

1. LOCK - Initial thought is to implement a "lock" of the data model as of June 1, 2024. This will be the deadline for incorporating any new components into the data model. After this, support for the data model will transition to a maintenance mode to ensure continued alignment with FAIR Data tooling and implement any fixes to unblock submission for the final HTAN Data Release 6.0.
2. RETROSPECTIVE - Proposed for July 2024. Should be focus of activities for this sprint, in parallel with any essential data model support related to HTAN Data Release 6.0. Suggest focused discussion among HTAN DCC staff and key contributors (e.g during liaison meetings). Additional participation from FAIR Data staff. Expected outcomes are to help consolidate key learnings and considerations of the development and implementation of the data model in HTAN 1.0, which will help inform efforts and approach in HTAN 2.0
3. ARCHIVE - Proposed for August 2024. Understand and planning of steps to 'archive' the HTAN 1.0 Data Model. This will include understand if/what data are potentially still expected to be submitted under this model beyond August 31, 2024, and how this will be supported.
4. RENEWAL PLANNING - Proposed for August-September 2024. Scoping of efforts related to the HTAN 2.0 Data Model in the first 6 months of the renewal. Will include review of retrospective analysis above to understand priorities and dependencies to, as well as determination and set up of related infrastructure to support the data model (e.g. new github repo? updated versioning? etc)

[aclayton555]

Re: 1. LOCK - Additional components expected and triaged for 24-5 sprint:

• microarray (minimal) - Implement minimal template for microarray data  #393
• multiplex-CITE-seq (minimal) - Implement minimal template for multiplex-CITE-seq assay #394
• CDS-friendly seq - Develop and implement HTAN/CDS seq template #396

[aclayton555]

Re: 2. RETROSPECTIVE

2 key retrospectives:
Data model

• key: Adam, Aditi, Jess, Ashley, Milen, Kristen, Dar'ya, Dave, Ino, Amy H, maybe another FAIR eng; recorded; optional observers: Orion? Christina? ANV? Jineta?
• scope: RFC-> data model -> implementation

Schematic/DCA - chat with Amy H

[aclayton555]

HTAN DCC Data Model Retrospective scheduled for July 10. I will be working with Tiara to coordinate planning and outcomes through our 24-7 sprint.

[aclayton555]

Re: 3. ARCHIVE

See #448

[aclayton555]

24-8 Close-Out

Re: 4. RENEWAL PLANNING

• We need to a design document that outlines key changes that we need to make (e.g. keep as CSV; graph object improvements)
• Set up the infrastructure the phase 2 data model
• Two approaches: Sage vs DCC. Ideally have the first conversation, then bring proposal to the DCC. Need understand THE way we at Sage want to handle these data models and how we approach this with an established, mature model. This could include what opportunities that exist to simplify the model and adapt this based on valid valid usage and cleanup. Are there simple/standard ways to implement Boolean values. Start with establishing minimal feature.
• Timing: Want to align with ongoing developments with Schematic.
• For 24-9/10: have an output be a design doc that outlines key considerations and decision points, as well as nice to have/wishlist features. 1) Define architecture, and pull out minimal layer that addresses issues and emerging pain points, 2) establish how will we set this up and the overall infrastructure (i.e. csv or YAML formal as input for JSON - AD using CSV with modularization; NF and Gray using YAML. csv may be better from visualization, which we see in MC2); 3) integration across end to end process (up front docs and downstream release infrastructure.