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 Michael to clear down the failures. We just, therefore, need to confirm that the RVF report is now: a) In the Preliminary Handover meeting it is being cleaned on a daily basis, with the intention of having it cleared down completely by the handover on 9th May 2018 b) Clean in the Final Handover meeting (before we version the content)? ACTION: Andrew Atkinson to therefore run the Content Validation report through on the final cut-off content from 10th May 2018 onwards, in order to identify any outstanding issues and resolve them before 16th May 2018 when the mapping cut off takes place.
|
| 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...........
|
| 4 | Early visibility of Release Notes
| Andrew Atkinson has created the template to update on Confluence: SNOMED CT July 2018 International Edition - SNOMED International Release notes - see here with relevant figures replaced with ??????? ready to be replaced with the relevant July 2018 figures ACTION: Maria Braithwaite and Donna Morgan will kindly aim to get them to Andrew Atkinson by 17th May 2018. ACTION: Lesley MacNeil 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. | ACTION: EVERYONE to confirm if we need any further RVF assertions to cover potential known issues caused by new Drugs modelling ?????????????????????????? NO - SO ANDREW TO KEEP IN TOUCH WITH PETER, WHO WILL CONTINUET O RUN MANUAL VALIDATION REPORTS AGAINST HTE DRUGS BRANCH UP UNTIOL THE CUT OFF AND VERSIOING ON 9th May, AND THEN WE MAY NEED TO RUN THEM AGAIN AGAINST THE RELEASE BRANCH FROM THAT POINT ONWARDS IF ANY DRUGS FIXES NEED TO BE IMPLEMENTED DURING HTE ALPHA/BETA CYCLE... ACTION: We need to complete the traceability analysis for the TermServer export, to ensure that everything is being exported as expected. Andrew to raise a ticket track it and assign to Kai to keep us updated. ACTION: We need to verify the new OWLAxiom refset - either we need to get the new assertions into Production RVF asap, or we need to create and run the validation in a manual script that we need to run this release. Andrew to raise ticket to track... Kai to write the assertion in DROOLS and pasas the standalone DROOLS validation over to Andrew to run on desktop for this release until Huy can autaomte for next release. ACTION: Maria to confirm with Farzaneh/Suzanne whether or not any LOINC issues need to be resolved before versioning, depending on volume and complexity/.... ACTION - Maria would like to disable all project on Friday 4th May - She will ask Rory when ready to disable... See section 2 for remaining current known issues... |
| 7 | Versioning and Change Freeze | Everyone still fine with all dates on this... |
| 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) - https://dailybuild.ihtsdotools.org/qa/ ACTION: Maria Braithwaite will run the spell check and RVF one final time after the cut off is complete... 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 MHA to run this again after Beta release is complete and update Release Notes if required. | |
| 9 | Risks | No known risks! Everyone comfortable so far... |