[Synapse Datasets + Collections] Define and incorporate schema for Synapse Datasets

[aclayton555]

Emerges from exploratory and feasibility analysis in: mc2-center/mc2-center-dcc#71

This ticket should track efforts to develop and implement a schema for annotating Synapse Datasets curated as part of the proposed MC2 Center workflow (Note that this is different from the existing 'Datasets' component in the MC2 Center data model). This is the first of several steps, which may be tracked in separate tickets as this work progress:

1. Define the schema (there have been ongoing discussions on this among the data managers group at Sage, but no resolution)
2. implementation as the JSON (this will be applicable and complimentary to ongoing efforts in NF)
3. exploration and incorporation of automation (again, pull in efforts from NF)
4. longer term: how this will look on the portal and what the expected user experience will be.

[aclayton555]

24-9: @aditya-nath-sage will pick this up and chat with @jaybee84 about aligning approaches with NF.

Target output for this sprint: design doc for how to implement datasets across MC2 and NF (much of this captured in linked ticket above), including tentative annotation process. (will this leverage schematic or the Synapse API?)

Additional info on Synapse Datasets: https://help.synapse.org/docs/Datasets.2611281979.html

[aditya-nath-sage]

Goal is to create a design document for how MC2 and NF will want to handle this issue. Example design doc: https://docs.google.com/document/d/1dF1-FjGSdO3nkKArEsrnjnWFLeOV78MlvGZvM8smJVk/edit?pli=1#heading=h.47emx3tcx2wj

[aclayton555]

24-9 Close-Out: Currently working with DM group (at Sage) to create a org-wide Dataset schema. This may take some time to reach consensus, but we can prioritize incorporating a placeholder model that we can then add the finalized schema later. Check on this mid sprint in 24-10.