Content Handover Meeting minutes - July 2017 International Edition

Prerelease Content Management Activities:

1. Verify that all namespace concepts (in the namespace registry) have been added
   
2. Inactivate the root concept synonym referencing previous release, and add synonym to reference current release.
3. Update copyright date on synonym (January releases only; N/A to July 2014)
4. Confirm all conflict adjudications have been resolved
   
5. Confirm there are no equivalency conflicts after classification
6. Send updated laterality indicator spreadsheet to technical team to support qualifier generation.
   
   

Content Validation Activities:

1. Concepts that have changed its high level hierarchy ancestor since last release
2. Concepts with FSNs with changed semantic tags
3. Active concepts with changed FSNs (check for shifts in meaning)
4. Concepts *in*-activated since the last release
5. Concepts *re*-activated since the last release
6. Concepts that changed from fully defined to primitive
7. Concepts that changed from primitive to fully defined
8. New FSNs: Check for adherence to naming conventions, no acronyms, etc.
9. Spell checking for new descriptions and/or manual inspection
10. Review all new and changed text definitions
11. Additions/removals of members of VMP refset (Inactive concepts still in the VMP refsets are removed during release extraction)
12. Additions/removals of members of VTM refset (Inactive concepts still in the VTM refsets are removed during release extraction)
13. Verify that there have been no changes to the Non-human refset in the Workbench.
14. Additions/removals of members of ICD-O simple map refset (Inactive concept still in the ICDO map are removed during release extraction)
15. Active concepts having active historical associations and reasons for inactivation
16. Verify that the daily build is extracting the correct Workbench path

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)

MICHAEL 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.

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

AAT to provide template to update on Confluence - MHA and DMO will kindly aim to get them to me by 19th May 2017.

Discussion of existing Known Issues from the previous Release

Issue ID: ISRS-153

MHA has resolved this already in the July 2017 editing branch. AAT to verify this has been fixed in Release testing...

Issue ID: ISRS-46

MHA to ensure that she has resolved this already in the July 2017 editing branch, and if not resolve now.

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

One other potential issue is the Case Significance change (7000+) - MHA to check with Lesley to ensure that no review is required here...

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.

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/

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.

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.