Page History

1. MBR - changed manually in this task ORPHANET-3042 verified new description is present 13 May.
2. MBR - not required as only required in January releases...
3. Process has generated the data -  pre-close of editing report 13 16 May 2022

   1. https://docs.google.com/spreadsheets/d/1pfmCEgvzflB8ZikxKEK5jJZufjDDuOMMYe2h6jZ0cHE1L07R3BmtohtBX6UY1rCN3F7GaHKLbDgBPaCE34If0Jk/edit#gid=1

4. Process has generated the data - pre-close of editing report 13 16 May 2022

   1. https://docs.google.com/spreadsheets/d/1pfmCEgvzflB8ZikxKEK5jJZufjDDuOMMYe2h6jZ0cHE1L07R3BmtohtBX6UY1rCN3F7GaHKLbDgBPaCE34If0Jk/edit#gid=2

1. INFRA-8402 / FRI-376 - RefsetDescriptor - RDA confirmed we should just remove them from scope for now, so we’ve raised Dev ticket to fix automated process whilst we continue to generate them manually in the interim... AAT TO TRIAL NEW EXCLUDE REFSET MEMBERS PARAMETER IN THIS RELEASE

2. Mapping failures checked by Donna and then exceptions listed 

   Jira
   server IHTSDO JIRA serverId b202d822-d767-33be-b234-fec5accd5d8c key INFRA-8874

3. Jira
   server IHTSDO JIRA serverId b202d822-d767-33be-b234-fec5accd5d8c key INFRA-8675

    May ticket for failed traceability assertions 

   Jira
   server IHTSDO JIRA serverId b202d822-d767-33be-b234-fec5accd5d8c key INFRA-8889

1. Content Release Lead confirms to Release Manager that all Projects had automated validation run against them, and all issues identified were resolved before promotion - MBR confirmed all done 
2. Still have traceability failures: All components in the branch traceability summary must also be in the RF2 export. All components in the RF2 export must also be in the branch traceability summary. confirmed false positives see 

   Jira
   server IHTSDO JIRA serverId b202d822-d767-33be-b234-fec5accd5d8c key INFRA-8675

   May ticket for failed traceability assertions all false positives 

   Jira
   server IHTSDO JIRA serverId b202d822-d767-33be-b234-fec5accd5d8c key INFRA-8889

Chris/Rick confirmed today that we would not be able to get now have the new automated process up and running for this release cycle - therefore need to confirm that everyone Maria confirmed she'd had a run through from the team, and so is ready to continue with run the old manual process for one more cycle?Ready for testing but no need to rush this cycle - will be ready for May release...

    1.  First rundeck job will pickup the right date from the Release schedule, and then run the data import

Chris to create an automated JIRA ticket (off the master INT Edition ticket) to remind them to schedule the relevant job(s) over the weekend.  Notifications set to be auto-sent to AAT + Maria...

Maria to confirm how the automated process went in final Handover meeting...    2. Second rundeck job will be run by Maria (once Mapping tasks are complete), to add 2x new task id's into the job and generate the maps

Donna confirmed she's happy with the schedule, and they're also already up to date with the final content.

Mapping process delivered ICD-0 + ICD10 files to AAT on time this cycle

Did mapping process work well this time??   Yes, process was good

HOWEVER, the counts don't match Donna's manual counts exactly, so we will investigate further:

• ICD-0 = Manual mapping count = ???? new records, only ???? new records coming through in Delta files
• ICD-10 = Manual mapping count = ???? new records, 485 new records coming through in Delta files
  • Donna sent report:
    • New concepts in release cycle.20220213 (1).xls
  • Compared Delta file changes to report:
    • Delta file showed most differences were due to 47 updated records in the Delta, in addition to that there was only one missing concept:
      • 1196866006
    • Confirmed with Rick that this was a concept that was added to the content (therefore came through to mapping in the drip feed), and was then removed from the content before the monthly release! 
    • Therefore should be missing from the Delta files - just should also be removed from Donna's manual counts (based on the drip feed) - she will work with Rick to get visibility of the Mapping QA report to remove these concepts from her counts
    • (see email trail at 16:24 on 15/2/2022)

Maria confirmed manual process went well again this month

April 2022May 2022:

• Donna ran new report that Rick created to double check no invalid mappings, all clean now
• Mark/Donna to complete mapping on Sunday/Monday (as drip feed failed last night so they won't get final content until Saturday...)

Maria confirmed all tickets complete

Plan is to follow the new processes as now defined: 

• PROVISIONAL - April May 2022 International Edition Release Schedule - Production Monthly Release - INTERNAL

AAT walked through and agreed new process with DevOps already, so unless there are any further questions/issues??AAT to sign off PreProduction (unversioned) build before 10:00 on 12th April17th May, and then:

• Versioning + related issues to be completed and resolved as of 12 Apr 17 May 2022 - DONE!

Reports run via the reporting platform:

• Summary Component stats for edition close of content editing 11 April 2022close of editing 16 May 2022 

  https://docs.google.com/spreadsheets/d/1mIMF25CFydRVyU02F5VdaRrNnvdB4xF9a3V26l3b-z81W97lBwbOCC4urwmhXKP3TIL4sDc0UUIhw2MjytG83JE/edit#gid=0