Agenda
Items to be discussed | Actions | ||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Prerelease Content Management Activities:
|
| |||||||||||||||||||||||||||||||||
2 | Discussion of existing Known Issues from the previous Release |
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
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
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: SNOMED CT August 2021 International Edition - SNOMED International Release notes - content team to update with relevant figures for January 2021 content.....
ACTION: Maria Braithwaite and Donna Morgan will kindly aim to get them to Andrew Atkinson by 25 November 2020.
Yong and Linda to confirm whether or not we need to add info on the new metadata concepts....
ACTION: Monica Harry and Paul Amos to review and approve once complete
Maria confirmed all tickets complete.
Plan is to follow the new process as defined last cycle: Technical Team Release tasks - September 2021
AAT notified Terance accordingly straight after the call on
Versioning + related issues complete and resolved as of =
Jira | ||||||
---|---|---|---|---|---|---|
|
Jira | ||||||
---|---|---|---|---|---|---|
|
Reports run via the reporting platform:
Concepts changed https://docs.google.com/spreadsheets/d/1QhxK1cja523C8CADBK75wzJ4qeXgIKSOfxgSPCR6E8g/edit#gid=0
Concepts inactivated https://docs.google.com/spreadsheets/d/1GkapGLVanHreMH6Si3cEvlNw0w8oalTEFUDJJ0DoE0w/edit#gid=0
New componentshttps://docs.google.com/spreadsheets/d/1QUsMw39gDeW4lYm0dTVrrWDDlxiV2av7Gqv7NxQmMA4/edit#gid=0
Release stats https://docs.google.com/spreadsheets/d/1HHKS1ZKsvr9WaDqRbhOirG9qgEKa9lWHwr5lrIeAZWA/edit#gid=0
Summary Component stats https://docs.google.com/spreadsheets/d/1-XU7byTRnBJUYaDhvlXdzFpHlFxDV746o5F2Msa1Olk/edit#gid=0
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
None raised
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
still needs to be resolved - Maria will implement in a fix branch off RFBJAN21 and AAT will regression test (as feedback_fix release type) once complete. Jira server IHTSDO JIRA serverId b202d822-d767-33be-b234-fec5accd5d8c key ISRS-921