Items to be discussed
Prerelease Content Management Activities:
Content Validation Activities:
MHA 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 10th May 2017
b) Clean in the Final Handover meeting (before we version the content)
ACTION: Michael Chu to therefore run Content Validation through on the final cut-off content from 10th May 2017 onwards, in order to identify any outstanding issues and resolve them before 15th May when the mapping cut off takes place. This was completed and validation passed
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.
Monica and Yong will all be around to support wherever needed, except for the 23rd-28th May, when Monica is away (Yong will cover this)
Early visibility of Release Notes
Discussion of existing Known Issues from the previous Release
Issue ID: ISRS-153
MHA has resolved this already in the July 2017 editing branch. ACTION: Andrew Atkinson to verify this has been fixed in Release testing... resolved - Monica to verify in final Beta browser
Issue ID: ISRS-46
MHA to ensure that she has resolved this already in the July 2017 editing branch, and if not resolve now.
MHA confirmed that she has already changed inactivation reason to "not semantically equivalent" see INTQA-629 - To be reviewed and promoted then MHA will close ticket.
MHA confirmed now promoted and ready for release - ACTION: Andrew Atkinson to verify this has been fixed in Release testing...Monica confirmed all good
Issue ID: ISRS-50
ACTION: Andrew Atkinson Chased KKE to confirm if this has been fixed for July 2017..Confirmed assertions passed in Beta release...AAT to reconfirm in final Production release....
Issue ID: ISRS-102
ACTION: Andrew Atkinson to verify this has been fixed in Release testing...AAT Confirmed maps now included in Beta release...AAT to reconfirm in final Production release....
Issue ID: ISRS-149
ACTION: Andrew Atkinson to verify this has been fixed in Release testing...Confirmed removed in Beta release...AAT to re-confirm in final Production 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.|
There is only one known outstanding issues here (100 outstanding Drugs conflicts) - MHA to confirm that these are all closed down in time for the Final handover meeting - Still being worked through as of 16:00 on 09/05/2017 (due to merge issues in the tool) - this may delay the cut off slightly and have a knock on effect on the release timelines - we will confirm once complete
One other potential issue is the Case Significance change (7000+) - MHA to check with Lesley to ensure that no review is required here... Lesley confirmed that she will ask Yong to action a sample test (AAT to tell Yong once the script has completed successfully and he can therefore start testing). ACTION: Lesley MacNeil to ask Yong to test.
ACTION: Andrew Atkinson to let Yong know when ready to test - done in Alpha
MHA to send AAT the 4 outstanding RVF issues that she is unable to resolve, due to them being warnings (and one being a result of a back end fix to 2 stated relationships)
ACTION: Andrew Atkinson to verify these can be safely ignored as warnings...confirmed
|7||Versioning and Change Freeze|
Monica and Yong will all be around to support wherever needed. And no promotion to main once authoring commences until notified.
Planned for 11th May, with proposed change freeze until 15th May (Monday afterwards) - team to catchup on Admin and Release Notes etc during this period.
Confirmed all completed as planned
MHA 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: Monica Harry will run the spell check and RVF one final time after the cut off is complete...
MHA 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 2017 International Edition.
ACTION: Monica Harry 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.
DMO raised a risk that Yong said there would be another 120 ICD-0 concepts to come through before the cut off date of 4th May, but yet when she looks at the completed queue there are only a few in there - so potentially an issue with hitting the 120 by tomorrow. MHA to chase immediately...
Yong confirmed that the total number is about 100 concepts. Most of them have already been promoted to the mainline. I will provide a list of concept IDs when all tasks are promoted to the mainline. There will be less than 10 concepts tomorrow (May 4th to Main then pending drip feed)
AAT asked why DMO and MHA were unable to view the 100 concepts already promoted to MAIN??YONG REPLIED: Currently, the mapping tool does not automatically push new morphologies in SNOMED CT for mapping. Those new concepts in the mainline are still not visible in the mapping tool. The issue has been reported and discussed at https://jira.ihtsdotools.org/browse/MAP-1409For this release, as noted in the above ticket, I will create a list of all new morphologies when they are all promoted to main. Then, Donna will use this list to get the concepts for mapping. It would be helpful that the new morphologies will be available for mapping in future. The estimated number of concepts for ICD-O mapping is based on the CRS requests. Please let me know if you need any further information.