Verify that all namespace concepts (in the namespace registry) have been added
Inactivate the root concept synonym referencing previous release, and add synonym to reference current release.
Update copyright date on synonym (January releases only; N/A to July 2014)
Confirm all conflict adjudications have been resolved
Confirm there are no equivalency conflicts after classification
Send updated laterality indicator spreadsheet to technical team to support qualifier generation.
Get SE and SP refset files from Yong
Donna to confirm with the UKTC (on the weekly call) to confirm they have nothing outstanding in QA status after content cut off for each release - as in July 2017 this started to cause problems in our mapping process...
MBR - confirmed with Yohani 31 October 2018
MBR - done please see
Jira
server
IHTSDO JIRA
serverId
b202d822-d767-33be-b234-fec5accd5d8c
key
INFRA-2719
MBR - done please see
Jira
server
IHTSDO JIRA
serverId
b202d822-d767-33be-b234-fec5accd5d8c
key
INFRA-2719
MBR confirmed - again to verify in the Final handover meeting.
MBR and MCH confirmed
MBR and MCH confirmed
MBR confirmed
MBR confirmed
ACTION:Maria Braithwaite/Andrew Atkinsonto speak to Yong about this, as this will now come from the Refset tool ... AAT received to receive from Yong w/c 12/11???????
YONG confirmed he would complete the refset by cop on 13/11/2018, so once Maria reviewed as well AAT should receive the completed version by 14/11/2018 at the latest.
YONG Delivered as requested on
ACTION:Complete and received from YongDonna confirmed that this collaborative work has now reached it's conclusion, and so this is no longer an issue as UKTC no longer have access to our tool.??????? AAT to receive from Yong w/c 12/11???????
YONG confirmed he would complete the refset by cop on 13/11/2018, so once Maria reviewed as well AAT should receive the completed version by 14/11/2018 at the latest.
YONG Delivered as requested on
2
Content Validation Activities:
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
MBR has been analysing the Daily Build RVF results for the past few weeks, and working with Michael Peter 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 November 2018- CONFIRMED
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. Complete and results sent to Maria for verification..??????? to confirm next week...
ACTION: Maria has shared to share the Content report results with the content team - she will confirm whether or not any fixes are required before the Alpha release on Monday - Maria confirmed all clean now and no further issues requiring action, via email at 16:51 on
Final issue found by UK (
Jira
server
IHTSDO JIRA
serverId
b202d822-d767-33be-b234-fec5accd5d8c
key
ISRS-464
) was confirmed by content team as planned for fix in July 2019, so no further fixes required - AAT can therefore start to build the release as soon as we receive the mapping files from WCI....
Elaine in UK is happy with the plan, they're just waiting for Jeremy Rogers to confirm he's also happy with it...
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.
ACTION: Maria Braithwaiteand Donna Morganwill kindly aim to get them to Andrew Atkinson by 17th May 15th November 2018 - done, Lesley signed off on 5/6/2018MARIA COMPLETED HER WORK, WITH LESLEY FOR REVIEW...
ACTION: Lesley MacNeiland Paul Amos to review and approve once complete...- AAT already addressed some of Paul's feedback on the technical sections - Maria has also addressed his feedback on the content sections
5
Discussion of existing Known Issues from the previous Release
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.
Jira
server
IHTSDO JIRA
serverId
b202d822-d767-33be-b234-fec5accd5d8c
key
INFRA-2965
Concepts should now have been inactivated and promoted - Maria confirmed that most have been resolved, but a couple of stragglers that cannot currently be resolved will be carried over to July 2019 - Monica will write this up in the Release Notes to confirm exactly what changes will/will not make into the Jan 2019 release.
Peter confirmed all resolved for Jan 2019 and closed the ticket down.
Jira
server
IHTSDO JIRA
serverId
b202d822-d767-33be-b234-fec5accd5d8c
key
INFRA-2723
Kai promoted final change to MAIN and so AAT + Maria Braithwaite to verify in final testing all the way through the release cycle to Production
Jira
server
IHTSDO JIRA
serverId
b202d822-d767-33be-b234-fec5accd5d8c
key
INFRA-2869
RDA and AAT Just need to confirm the fact it hasn't disappeared form the RVF report isn't a result of the RVF release on 7/11/2018....
RDA confirmed that the last RVF release was last week so couldn't have impacted this issue - therefore we can close this down once myself and Maria Braithwaite have verified in Alpha testing.
AAT + Maria Braithwaite to verify in final testing all the way through the release cycle to Production
Jira
server
IHTSDO JIRA
serverId
b202d822-d767-33be-b234-fec5accd5d8c
key
INFRA-2868
Peter confirmed all resolved for Jan 2019 and closed the ticket down.
Ticket closed - AAT + Maria Braithwaite to verify in final testing all the way through the release cycle to Production
Jira
server
IHTSDO JIRA
serverId
b202d822-d767-33be-b234-fec5accd5d8c
key
MAINT-489
Maria confirmed resolved, AAT + Maria Braithwaite to verify in final testing all the way through the release cycle to Production
Linda Bird to confirm that she has completed the next step...
Maria Braithwaite to incorporate the new HRCM testing into all future Release cycles, to ensure that going forward any similar issues are picked up much earlier in the cycle.
Andrew and Maria to agree the plan for testing... (AAT to setup a call with David to discuss whether or not he's updated the HRCM)...
Maria to confirm if she can now use HRCM to validate these type of issues...
Peter G. Williams will verify assertion is correct, otherwise may need an RVF update as well...
Confirmed resolved, ready to test in Alpha/Beta...
ISRS-380
Michael logged ticket for this - see linked ticket. This linked ticket is marked complete - can we therefore close this down as resolved? (if so why is RVF assertion still failing?)
Michael Chu to investigate and confirm what action is required...
Confirmed resolved, ready to test in Alpha/Beta...
ISRS-381 - New inactive states follow active states in the CONCEPT snapshot.
Peter confirmed fix now gone into Main today, so Andrew Atkinson to re-build and verify no further failures in RVF....
Resolved
ISRS-382 - Complete the traceability analysis for the TermServer export
Ticket assigned to Kai, who will add all info and assign to relevant developer
Rory confirmed complete and all fine
ISRS-350/ISRS-383 - Verification of the new OWLAxiom refset
Kai to write the assertion in DROOLS and pass the standalone DROOLS validation over to Andrew to run on desktop for this release until Huy can automate for next release.
ANY PROGRESS ON DROOLS??
Still no autmoated way to run the DROOLS validation, so...
AAT to ask Kai to run the DROOLS validation manually against the final Alpha build on Monday 21st...
Deferred to Jan 2019 - will continue to run manually for July 2018
ISRS-384 - DROOLS assertion failure: Active concept parents should not belong to more than one top-level hierarchy.
Ticket assigned to Toni, who will resolve the issues shortly...
Maria confirmed Toni resolved this issue
AAT to regression test in final Alpha/Beta builds...
ISRS-385 - DROOLS assertion failure: An active concept must not have two relationships with the same type, target and group. The duplicate can be an inactive relationship that should be reactivated, or an unreleased new relationship that should be deleted.
Ticket assigned to Maria, who is resolving the issues now...
AAT to verify in final builds...
Awaiting confirmation of actual changes made by Maria/Toni......
Jira
server
IHTSDO JIRA
serverId
b202d822-d767-33be-b234-fec5accd5d8c
key
INFRA-
2320 - Michael Chu to pickup and run report for Maria
Maria confirmed resolved
ISRS-286 - Andrew Atkinson to run DROOLS standalone validation against Snapshot once Kai has provided updated version - this will give Maria historical report against this issue
ANY PROGRESS ON DROOLS??
Maria confirmed resolved due to new DROOLS rule to find any new issues, plus Kai's report covering off any historical issues
ISRS-260 - Andrew Atkinson to run DROOLS standalone validation against Snapshot once Kai has provided updated version - this will give Maria historical report against this issue
ANY PROGRESS ON DROOLS??
Maria confirmed resolved due to new DROOLS rule to find any new issues, plus Kai's report covering off any historical issues
6
2792
Peter G. Williams kindly agreed to check that this has now been completely addressed by Michael's extension of the field length. He subsequently confirmed that Yes, Michael Chu said this would be fixed as of RVF version 1.4.6 and we're well passed that now in production (1.6.1). I've also checked the daily build and that text defn is safely present in the full and snapshot files. It hasn't budged since 20160731 so as expected it's not present in the delta file. This problem was purely an artefact of the RVF data schema which has been addressed.
Issue therefore closed as resolved
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: Peter G. Williamsto confirm if we need any further RVF assertions to cover potential known issues caused by new Drugs modelling?report on relationship issue with Yong, and if it has now been completely resolved and reviewed?
Peter confirmed no further action
NO - SO ANDREW TO KEEP IN TOUCH WITH Peter G. Williams, WHO WILL CONTINUE TO RUN MANUAL VALIDATION REPORTS AGAINST THE DRUGS BRANCH UP UNTIL 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...
AAT to ask Peter to run the final validation manually against the final Alpha build on Monday 21st... done, Peter confirmed clean
AAT also sent Beta to Peter for final testing at 18:38 on 5/6/2018 - Peter confirmed no further testing required
ACTION: Maria Braithwaiteto confirm with Farzaneh/Suzanne whether or not any LOINC issues need to be resolved before versioning, depending on volume and complexity/....
They responded yes, but Michael confirmed report all clear and therefore no issues to resolve for LOINC
ACTION: Peter G. Williamsto run one off DROOLS run for case sensitivity to ensure all historical records validated as well as new ones - Peter will confirm ,to Maria if anything needs resolving....Maria has resolved all new issues, and does not believe there's any point in running historical issues as we know they're there and can't be fixed until we have confirmation on the final direction for case sensitivty..
licencing issue
Maria confirmed Farzaneh and Suzanne have comeplted the review and found no isues that need to be resolved - this doens't need to be repeated throughout the cycle - just needs to be done before each subsequent international release.
ACTION: Maria Braithwaitewould like to disable all project on Friday 4th May - She will ask Rory when ready to disable... done
To keep an eye on as we proceed:
Rory found a concept that had been unintentionally inactivated - it looked at first as if this was an automation issue, in the sense that SnowOwl had inactivated a concept off the back of a merge without having been instructed to do so. However, on investigation this was proven to not be the case, with user error being cited as the rot cause. It's worth keeping an eye on all inactivations throughout the cycle however, and myself and Maria will continue to run some spot checks at various points to ensure nothing looks wrong.
See section 2 for remaining current known issues...
Mapping:
Hi Andrew, Quick update for tomorrow as discussed. The drip feed has now been inactivated and all maps for the July 2018 release have been mapped and reviewed and pushed to publication. I have raised a JIRA ticket MAP-1578 for Rick WCI to commence the validation with a view to handover to delivery services when completed. If I have anything further I will keep you updated
+ Andrew Atkinson agreed to formalise the process for disabling projects a few days before content cut off - I've added it into the formal Schedule, so we'll continue to run that for all future releases and see if it continues to have positive effects on lack of impact to Maria's reviews.
Mapping: Clean after initial meeting - how are we looking for delivering tomorrow?? Donna all complete and happy, AAT to verify with WCI that they are cracking on with final release files...
7
Versioning and Change Freeze
AAT to raise ticket now - DONE
Versioning completed and initial successful builds run - will confirm properly once final validation run after mapping files delivered....Completed and successful builds run.
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 Braithwaitewill run the spell check and RVF one final time after the cut off is complete... done??
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 BraithwaiteThe 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 . Maria confirmed all re-tested and passed, via email at 15:30 on 6/6/2018.- done??