Agenda
Items to be discussed | Actions | |||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Prerelease Content Management Activities:
| 2014
|
| done
| by email 11 Nov 2020MBR - done please see https://jira.ihtsdotools.org/browse/INFRA
| 54022 | Discussion of existing Known Issues from the previous Release |
Jira | ||||||
---|---|---|---|---|---|---|
|
- MBR not needed, will add any requests to next available editing cycle going forward.
- MBR confirmed we can remove this from the checkpoint going forward as now just manual task in whatever the next release is for Maria + Yohani!
- MBR - done please see
Jira server IHTSDO JIRA serverId b202d822-d767-33be-b234-fec5accd5d8c key
INFRA-
7176 - MBR - not required for September release - only every year...
- Peter G. Williams to generate + Yong to also create it the old way + compare to ensure valid...
- ????Yong/Peter to generate and deliver by Wednesday 8th????
- Peter G. Williams to generate (FRI-158) + Yong to also create it the old way + compare to ensure valid...
- ????Yong/Peter to generate Daily build and deliver by Wednesday 8th????
- Yong confirmed he will try to follow the deadlines for the monthly releases -
- September 2021 had some Observables changes, BUT they didn't make it in in time for the September deadline, so these will be done for the October 2021 release.
- Therefore there are NO expected MRCM changes for the September 2021 release.
Discussion of existing Known Issues from the previous Release
- ISRS-1023 - awaiting authoring platform update - on hold indefinitely until this happens....
- ISRS-1038 - exception list proper names - permanently whitelisted.
- ISRS-1063 - resolved all changes verified present for September 2021 release. AAT to test in Sept 2021...
- ISRS-1066 - resolved changes verified present for September 2021 release. AAT to test in Sept 2021..
Jira | ||||||
---|---|---|---|---|---|---|
|
I have checked a sample of the attached file, the issue is the same, the concepts are marked fully defined by virtue of their stated IS_A relationships which was in the past acceptable, editorial policy has subsequently changed and we now require a proximal primitive parent and the addition of attribute and value pairs. These modelling issues are being addressed by the QI project in many cases using template based editing, no changes required at present. Can we close this down then?? Yes everyone on the call agreed to resolve the ticket and confirm that the QI project will resolve these outstanding issues over the next few cycles
Jira | ||||||
---|---|---|---|---|---|---|
|
- .
Content Validation Activities in the Current Release cycle:
- Concepts that have changed its high level hierarchy ancestor since last release
- Concepts with FSNs with changed semantic tags
- Active concepts with changed FSNs (check for shifts in meaning)
- Concepts *in*-activated since the last release
- Concepts *re*-activated since the last release
- Concepts that changed from fully defined to primitive
- Concepts that changed from primitive to fully defined
- New FSNs: Check for adherence to naming conventions, no acronyms, etc.
- Spell checking for new descriptions and/or manual inspection
- Review all new and changed text definitions
- Additions/removals of members of VMP refset (Inactive concepts still in the VMP refsets are removed during release extraction)
- Additions/removals of members of VTM refset (Inactive concepts still in the VTM refsets are removed during release extraction)
- Verify that there have been no changes to the Non-human refset in the Workbench.
- Additions/removals of members of ICD-O simple map refset (Inactive concept still in the ICDO map are removed during release extraction)
- Active concepts having active historical associations and reasons for inactivation
***** AS OF NEXT MONTH's RELEASE (October 2021), THIS MANUAL VALIDATION SHOULD HOPEFULLY HAVE BEN REPLACED BY INCREASED SCOPE OF AUTOMATED VALIDATION, AND THEREFORE THIS STEP CAN BE CHANGED TO SOMETHING LIKE "Content Release Lead confirms to Release Manager that all Projects had full automated validation run against them, and all issues identified were resolved before promotion." *****
Content Team Support availability - Confirm which members of the content team will remain on stand-by until clean database milestone is achieved after release build file QA and post-release assertions are validated.
Maria and Yong will be around.
Early visibility of Release Notes
Andrew Atkinson has created the template to update on Confluence:
September 2021 International Edition - SNOMED International Release notes - content team to update with relevant figures for
July 2021 content.....
ACTION: Maria Braithwaite and Donna Morgan
confirmed we don't need these for the September and October releases - instead they'll just log the change notes in their Trello board and add them into the Jan 2022 release when we get to it.
Yong and Linda to confirm whether or not we need to add info on the new metadata concepts....
QUESTION: Do we need a more streamlined format? Or just include a lot less data? - WE'LL PLAY AROUND WITH THIS IN THE NOVEMBER RELEASE - WE SHOULD GO VERY MINIMALIST AND THEN SEE WHO (if anyone) in the community complains about it, and ask them to tell us specifically what hey want us to add back in...
ACTION: Monica Harry and Paul Amos to review and approve once complete
Maria confirmed all tickets complete.
Plan is to follow the new
processes as now defined
AAT walked through and agreed new process with DevOps already, so unless there are any further questions/issues??
- Chris/Terance had questions on how to manage the Daily Build in the following soft launch releases?
- Kai answered their questions and agreed to add a flag in SnowStorm to help them manage it...
Versioning + related issues complete and resolved as of =
Jira | ||||||
---|---|---|---|---|---|---|
|
+
3 Sept 2021 Reports run (by Maria) via the reporting platform:
Inactivated concepts https://docs.google.com/spreadsheets/d/1gpG9sxbw1bL0LAkP90iXPr7FffvjibRUMT3VZk6R3xU/edit#gid=0
Inactivated concepts in ref sets https://docs.google.com/spreadsheets/d/
New and changed components https://docs.google.com/spreadsheets/d/
descriptions https://docs.google.com/spreadsheets/d/
component stats https://docs.google.com/spreadsheets/d/
Peter confirmed reports will not be updated now, as most are based on Delta's, and once we've versioned the Delta files will be empty! So we need to check the original reports run by Maria (above) straight after her authoring checks were complete, and just manually take all of the latest fixes (like
, etc) into account. Jira server IHTSDO JIRA serverId b202d822-d767-33be-b234-fec5accd5d8c key ISRS-921
Just the obvious 8.4 release happening at the same time as Versioning...
- Release schedule task for today - Content Release Lead to request (via Infra ticket) the maintenance screen to be raised in Production, to prevent further updates to International content
Jira | ||||||
---|---|---|---|---|---|---|
|
- .
- This is showing up in a new reporting platform report today:
900000000000441003 SNOMED CT Model Component (metadata) (metadata) Unexpected Inf Rel Module Y Y/Y Concept module 900000000000012004 vs Rel module 900000000000207008 [I0] 116680003 |Is a (attribute)| -> 138875005 |SNOMED CT Concept (SNOMED RT+CTV3)|
Checked with Yong - I think this is a known issue about module dependency. 138875005 |SNOMED CT Concept (SNOMED RT+CTV3)| belongs to the 900000000000207008 |SNOMED CT core module (core metadata concept)|. But its subconcepts include |SNOMED CT Model Component (metadata)| and |SNOMED CT model component module (core metadata concept)| and |SNOMED CT core module (core metadata concept)| are all belong to 900000000000012004 |SNOMED CT model component module (core metadata concept)|.
- CRS requests - will the requests that have a status of ready for release be changed to completed or are we waiting to change them all for the Jan 2022 release?