Page History

Overview

Documents the release process details.  There is an admin page already that indicates how to run the mojo.  See Release Processing Tool for more information.

Assumptions

• Source terminology is SNOMED CT
• Release is in RF2 delta format
• QA of overall release is done by an external system (though project-specific validation rules are processed here)
• That editing was done in conjunction with a "drip feed" system that brought emerging content into the system as it was being developed, so it could be mapped.
• That the mapping files are part of the source terminology release

Timeline

The mapping tool supports a release process that takes into account end-of-editing cycle activities, some quality assurance, production of data files, and upgrading terminology versions when the time comes.  The release processing is specifically tailored to the needs of IHTSDO and maintenance of the RF2 complex and extended map refsets that are part of the SNOMED CT distribution.  (Note: in the below figure, all references to UAT are now handled on the RELEASE server)

...

The release process requires the ability for mappers to resume editing before the release cycle fully completes.  Thus, this release strategy calls for completing the actual release processing on the RELEASE server and feeding back to PROD the final state of the map.   Many of the steps can now be handled via the user interface, as described in this section Running the Release Process with the User Interface.  A more full accounting of the original manual steps can be found in the section below entitled Mapping Tool Release Process. 

Running the Release Process with the User Interface

Mapping Release Process Demo Tutorial

...

Pre-release steps

These steps will be run on PROD.

• Compute Workflow - Recomputes the workflow.  Provided to check for available work prior to running the release.  New work will show up in the 'Available Work' widget on the main dashboard.
• Check Completion - Checks that all in-scope records are ready for publication.  If this check runs clean, the release process can commence with WCI cloning to the RELEASE server.  If this check does not run clean, details can be examined in the Reports accordion, 'Project Dashboard' report.  This report will indicate which users are still editing and where the in-progress mappings are in the workflow.  When the mappings are finalized, this check should be run again to confirm that work is complete. The night after work is confirmed to be complete, the nightly backup will run and the next day, WCI can use that night's backup to do the clone to the RELEASE server.  
• Start Editing Cycle - After WCI has completed the clone to the RELEASE server, the new editing cycle should be started on PROD.  Clicking this button, will update the editing cycle start date to today's date.

Release processing steps

These steps will be run on the RELEASE server after the clone is completed by WCI.  For the alpha, beta, member, and final versions of the international release, ALL of these steps will need to be run for each iteration (with the exception of Reload SNOMEDCT, which does not need to be run for alpha).  For the derivative releases, each of these steps will likely only be run once.

• Reload SNOMEDCT - For beta and later, select the SNOMED version that the release upon which the release will be based.  After the version is selected, another picklist will allow selection of alpha, beta, member, or final releases of that SNOMED version.  Options presented are those available on the AWS S3 instance.  This process generally takes a few hours to complete.  This step must be followed by running 'Reload Refset Members'.
• Reload Refset Members - Loads the refset members from the prior release of this project.  This step is critical and enables the release process to compare what is currently in the db with what was included in the prior release.  This step MUST be rerun every time that 'Reload SNOMEDCT' is rerun.  
• Begin - Creates the 'Release QA' which can be located on the Reports accordion.  Requires effective time to be entered in the Parameters section on the right-hand column of the UI.  If it is established that mappers should make corrections based on this report, mappers should make these modifications on the RELEASE server.  When the editing is complete, the 'Check Completion' step should be rerun and then the 'Begin' step can be rerun.
• Process - Creates release files.  Requires effective time and module id.  Files are available for download in the 'Releases' picklist on the right-hand column of the UI.  When the administrator is satisfied with the release files, WCI will transfer the release file back to the PROD server so it can be integrated back into the current state of the project.

Finalize release steps

These steps will be executed on PROD after the release files have been copied back to the PROD server from the RELEASE server.

...

Running the Release Process from the Command Line

...

Custom release processing can be implemented via an outside package, or in the mapping-custom project (see Custom Release Process).

References/Links

• n/a