Closed aclayton555 closed 1 week ago
High level summary of work completed for this:
<component>_id
and <component> Key
reference systemshared
into model-specific foldersSee additional info added in #116
24-7/8 close-out: have made a lot of changes in this refactor, and really want another set of eyes on this to make sure this makes sense. Okay to wait until October for a deep dive.
Priority however is to at least close out the CDS attribute mapping. Want to have this complete by site visit.
Set up meeting with Aditi, Orion, Aditya asap to push through this. Maybe bring Jess in.
24-9: Working session scheduled fro Sept 11 at 9am PT.
Outcome of that meeting will be CDS mapping (priority for site visit). Toward end of that discussion, think about timelines/phased approach for releases (may not want to do this all at once since there will be some major changes).
Notes from Sept 11 working session:
Next steps:
24-9 Close-out: This work will continue on into the next sprint. On track, but check in mid sprint.
24-10: Okay to close. Next phase to work to continue in testing and in docs: https://github.com/mc2-center/data-models/issues/142
To be performed in July 2024. Outcomes of this ticket should be a relatively comprehensive plan and related tickets to coordinate work for to August 2024 and onward.
Cover:
SCOPE: what needs to be done (e.g. data model changes to enhance linkages) OUTPUTS: expects outputs (e.g. RFCs and deployment schedule) DEPENDENCIES AND IMPACT: what, if any, downstream dependencies or required changes (e.g. data model changes that impact syncing scripts...especially since Verena will be OOO). RESOURCES: how and who will perform this work.
Relates to #97 and #56