search

mc2-center / data-models

Versioned history of the MC2 Center data model
https://mc2-center.github.io/data-models/
Creative Commons Zero v1.0 Universal
1 stars 1 forks source link

Establish if/how data model lucid files should be updated #54

Open aclayton555 opened 5 months ago

aclayton555 commented 5 months ago

Back in the day, when our data model was much "simpler," we maintained visualization of the data model in Lucidchart:

https://lucid.app/lucidchart/5c8160b1-f087-4fbd-a679-1e6d175e4a69/edit?invitationId=inv_ad91d3a1-968e-4414-ba33-f537e1b2b179&page=lpgYV5TpYyu8#

These diagrams were critical in helping us design and transition our data model to a schematic-based data model (this occurred at the end of the CSBC/PS-ON grant in 2022).

With updates expected to occur on a monthly cadence in MC2, do we still want to maintain these? Are there alternative solutions that we can adopt that are more automated (e.g. updates occur with our data model releases)? If we do want to maintain these, need to establish an owner and process for keeping these up to date.

FAIR Data has been doing some data model visualization work, but this hasn't been consistent supported (was beta tested in HTAN, but updates were not automated)

Consider this in the context of WHO might want to browse a visual representation of the data model. Might compliment efforts in https://github.com/mc2-center/data-models/issues/49

aclayton555 commented 4 months ago

Keep this as a stretch for 24-2 sprint. Will be helpful to bring to upcoming team discussions on RFC/data model strategy.

Bankso commented 4 months ago

Current plan is to update the lucid charts to include 1) the current implementation of the MC2 data model, 2) the next planned features/modification to the data model (once decided)

Concerning the data decision tree, it will likely be a while before we can 100% fill this out, since I think it makes sense to pilot data flows before releasing a decision tree for others to reference, but my current plan is to store the information for the flow chart in a CSV and build the diagrams using Graphviz and pydot

I've started collecting information and ideas about our data model in this deck Since I'm using them to think/brainstorm, those slides are not in any useable form right now, but I wanted to make sure they were linked, since I plan for them to be helpful down the road.

aclayton555 commented 3 months ago

Continue work on this in 24-3. Opportunity to pair this down in scope to maximize utility. Tidy up view of normalized vs denormalized table since guidance from FAIR on this has evolved.

aclayton555 commented 3 months ago

In 24-3 sprint, really prioritize the draft decision tree component of this. Also consider CFDE in data routing ecosystem. Aim to have internal review and feedback on decision tree within this sprint.

Bankso commented 2 months ago

Summary of progress

Mostly done:

In progress:

aclayton555 commented 2 months ago

Continue work through 24-5 sprint, including feedback from team. Consider different audiences for aspects of this (decision tree). Maybe bring this for discussion at an internal team meeting in late May.

aclayton555 commented 4 weeks ago

Bring for discussion on June 12 MC2 Center Team meeting for feedback from the group.

aclayton555 commented 4 days ago

Presented on June 12 MC2 Center Team meeting. Specific asks for the team:

I will include a reminder to the team to take a look at these this week!