[RESEARCH SPIKE] Alignment of MC2 Data Model to other models #217
Description
This will likely evolve as a parent issue of several related and child issues.
Discussed in the context of Y4 Milestone planning and 25-8 MC2 Data Model Kick-Off. High level thoughts:
- There is a desire to optimize alignment of the MC2 Center Data Model to other data models in use, including CRDC (already in progress, but need to update to latest version), HTAN2 (currently in development, but builds on/improves from HTAN1, which was a basis for the early MC2 model), and other repositories like GEO.
- The HTAN2 data model is already developing with strong alignment to CRDC. The MC2 data model has also been evolving to maintain alignment with the CRDC, particularly mapping to their CDEs
- The availability and adoption of CDEs are critical here
- Rather than MC2 creating yet another standalone data model, how can we position this model to be an intermediary that maps and aligns nicely with several other data models in use. Think of octopus analogy. This does pivot the driving data model strategy: compatibility / flexibility with downstream repos over community input, but this seems like a natural evolution given the low adoption of RFCs in this project. However, need to acknowledge that while repositories and CDEs prioritize sharing, there is valuable feedback into data reuse that can be driven by the community.
- There is a clear value add here for Sage (increased alignment across projects will help us with various goals in connecting related resources across portals/projects), for contributors (we can be more ready to support sharing data, regardless of the final repository), and our partners at repositories like CRDC (we will evolve with them).
25-8 sprint: Research and draft the plan for discussion at the site visit
- Initiate a research spike to understand the WHAT and HOW we want to pursue monitoring and maintaining this alignment. The WHY can be discussed at the site visit with further details on how we anticipate performing this work in Y4 and how we expect the outcomes of this work to position the MC2 Center.
- Include an initial pass through the backlog to pull out relevant tickets related to alignment between data models. Related or expected outcome/implementation tickets linked for ease of findability