Agenda
Items to be discussed | Actions | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Prerelease Content Management Activities:
|
| ||||||||||
| 2 | Content Validation Activities:
| MBR has been analysing the Daily Build RVF results for the past few weeks, and working with Peter to clear down the failures. We just, therefore, need to confirm that the RVF report is now: a) RVF report being checked on a daily basis with the intention of having it cleared down completely by the handover on 8 Nov 2019 b) To be clean by the Final Handover meeting (before we version the content) to confirm 18 Nov 2019 . Early Alpha run by AAT 1st Nov 2019: assertionText" : "All language refset members inactivated in current snapshot must have been active in the previous release." - https://jira.ihtsdotools.org/browse/INFRA-4306 FIXED assertionText" : "Preferred Term exists exactly once in each language refset for each concept." - https://jira.ihtsdotools.org/browse/INFRA-4313 FIXED assertionText" : "Concept should not have any duplicated historical association indicators." - https://jira.ihtsdotools.org/browse/INFRA-4312 FIXED assertionText" : "All OWL Expression inactivated in current release must have been active in the previous release." - https://jira.ihtsdotools.org/browse/INFRA-4308 FIXED assertionText" : "There is a 1:1 relationship between the id and the key values in the ASSOCIATION REFSET snapshot file." - https://jira.ihtsdotools.org/browse/INFRA-4317 FIXED assertionText" : "There is only one member id per description per dialect in the language refset snapshot file." - https://jira.ihtsdotools.org/browse/INFRA-4318 FIXED assertionText" : "Relationship groups contain at least 2 relationships." - https://jira.ihtsdotools.org/browse/INFRA-4197 NOT AN ERROR NEEDS CHANGE TO RVF assertionText" : "Active concepts must have at least one IS A relationship." – 138875005 ROOT CONCEPT NO CHANGES NEEDED https://jira.ihtsdotools.org/browse/INFRA-4197 assertionText" : "An FSN containing the word \"pre-filled\" must be changed to prefilled." – AWAITING CHANGE TO RVF REPORT TO REMOVE ASSERTION https://jira.ihtsdotools.org/browse/ISRS-574 assertionText" : "It is not allowed to add a subtype as a parent." – CHECKED WITH TMO, JCA, YGA NO CHANGES NEEDED. Warnings relating to language ref set inconsistencies, special characters in FSN, case significance, capitalisation etc –a large number of issues addressed during this release cycle, there should be a reduction in the overall number of issues relating to the language ref set since the July release through efforts to ‘fix’ content where needed and also changes to the language ref sets in the author platform. Ticket logged for changes to the RVF report to allow us to identify active versus inactive concepts to help us to prioritise areas of content that need review going forwards https://jira.ihtsdotools.org/browse/INFRA-4052 Ticket is logged to align case sensitivity rules in the RVF with the editorial guidance which should also see a reduction in warnings relating to case sensitivity - https://jira.ihtsdotools.org/browse/INFRA-4301 Will log a new ticket to ask for ability to whitelist in RVF report for correct content that is currently showing upfor various reasons.ACTION: Maria Braithwaite to share the Content report results with the content team - will confirm whether or not any fixes are required before the Alpha release Maria confirms: https://jira.ihtsdotools.org/browse/RP-127 - all issues resolved for Jan 2020 release, new report in RP confirms no new issues. MBR will share content report with team when it is ready.
| ||||||||||
| 3 | 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 , Donna and Yong will all be around to support wherever needed .Donna and Yong on leave at present (8 Nov 2019)
| ||||||||||
| 4 | Early visibility of Release Notes
| Andrew Atkinson has created the template to update on Confluence: SNOMED CT January 2020 International Edition - SNOMED International Release notes - content team to update with relevant figures for January 2020 content..... ACTION: Maria Braithwaite and Donna Morgan will kindly aim to get them to Andrew Atkinson by 15 November 2019 ACTION: Monica Harry and Paul Amos to review and approve once complete
| ||||||||||
| 5 | Discussion of existing Known Issues from the previous Release
|
| ||||||||||
| 6 | Brief run through of the known issues already identified by the content team during the QA batch process, to ensure that technical team are aware of them, and can either resolve them in time for the release, or confirm as known issues.
Mapping: Clean after initial meeting - how are we looking for meeting the planned delivery timelines - DONNA confirmed all on track | Mapping: 8 Nov 2019 Donna is on leave today she sends this update: Technical QA has started. SNOMED has been reloaded and 1 concept has been identified as needing a map in the ICD-10 project - Drip feed must not have picked it up. The concept 32941000119104 Ingestion of toxic substance (disorder) has been mapped and WCI can re commence the release work. GMDN and ICD-O have been completed and WCI notified. Both projects will need to pass technical QA but nothing to report so far. | ||||||||||
| 7 | Versioning and Change Freeze | KAI TO RUN ONE FINAL MANUAL OWL DAILY BUILD BEFORE WE VERSION JUST TO DOUBLE CHECK NO UNEXPECTED CONTENT ISSUES.... HE WILL RUN EITHER THIS AFTERNOON OR TOMORROW MORNING (FRIDAY 10th) - COMPLETED with reasonably clean results. AAT to then get a clean Alpha package built before we can sign off content for versioning...finally got a clean build on AAT to request Rory/Michael to action after all above confirmed.....Versioning and branching completed and authoring tool re-opened on as planned. Validation up and running immediately due to no more reliance on the AMI!! - Maria and team to let us know immediately if any issues found in the validation as might be a few initial niggles... ????????Versioning completed and initial successful builds run - will confirm properly once final validation run after mapping files delivered....has run some manual checks for missing descriptions - no issues found. | ||||||||||
| 8 | Stats Report | MBR has now been using the Daily Build QA report (which will contain data from the next Release Cycle by the time this Release is published) - for stats and has the information needed for release notes, also given access to https://dailybuilddocs.ihtsdotools.org/qa/ ACTION: Maria Braithwaite will run the spell check and RVF one final time after the cut off is complete - completed 7 May 2019 MBR can also now use this for the stats in the Release Notes, as once content cut off is complete, this Daily Build report will show the static version for the July 2018 International Edition. ACTION: Maria Braithwaite The only thing we need to be careful of here is large updates during Alpha/Beta release cycle - so MBR to run this again after Beta release is complete and update Release Notes if required - done?? google.com/spreadsheets/d/1hgDBPG5TjarvGpRJD6LBUN1sHLizhWWchzWDXXjpPRk/edit#gid=3 by Peter for further information that will be useful for release notes. | ||||||||||
| 9 | Risks |
| 9 | Risks | OWL Daily Build has not yet been automated and run, and so Maria has not had sight of the results of this before the handover. ACTION: We therefore need to run some additional checks to ensure that there are no unexpected issues - KAI TO RUN ONE FINAL MANUAL OWL DAILY BUILD BEFORE WE VERSION JUST TO DOUBLE CHECK NO UNEXPECTED CONTENT ISSUES.... HE WILL RUN EITHER THIS AFTERNOON OR TOMORROW MORNING (FRIDAY 10th) - COMPLETED and the few minor issues found have now been fixed - in test now with aim to get them into Production before the Alpha release... ACTION: PLUS Andrew to run the preliminary version of the OWL Delta that Kai has produced through the early validation builds and ensure no failures in the RVF or DROOLS... DONE The next risk is that we don't have the full OWL functionality in place in the termServer as yet - this is coming soon, but not quite in time for the July 2019 release. This is resulting in us having to follow several workarounds for creating the OWL files as we promised for this release package. These workarounds are manageable, but quite manual, and so naturally introduce some additional inherent risks that wouldn't be there if we had the full end to end OWL solution in place already. We will mitigate this with as much validation as is possible in the time, but we should still acknowledge this as a potential risk to the quality of the end deliverables.The other risk is that we still don't have a final decision as yet on the format of the OWL content in the RF2 files -
Other than that, no known risks! Everyone comfortable so far... No new risks raised in the Final Handover meeting - everyone signed off ready to proceed as planned..
| |||||||
| 10 |