Release Process

Overview

Documents the release process.

This is a placeholder page with basic information and will be developed to fully document this aspect of the system.

Information about this is also in Admin Tools.

Assumptions

The process assumes that the admin tool to "Start Editing Cycle" was initiated and that a ReleaseInfo object corresponding to the upcoming release exists with a "planned" flag and not a "published" flag.

Details

The basic process for release has these steps

• Begin Release
  • Marks the release start date (in the ReleaseInfo) process for tacking
  • (Optionally) runs all validation checks on all concepts subject to release
  • Assign identifiers (if desired to assign them at this point)
• Perform release
  • Generate the actual release data files
• Finish Release
  • Assign identifiers (if desired to assign them at this point)
  • Save the publication dates (e.g. effectiveTime) of all components included in the release
  • Update the "terminology version" of all components (TODO: allow the table to have "current" and leave it at that for where specific versions are not needed)

A delta RF2 release of all data is provided as a standard admin tool. 

TODO: describe the process of generating a release for QA purposes and how effective time and identifiers are managed.  Include explanation and examples of how

TODO: describe the process of formally setting release identifiers, setting effective times, managing "release history" information, (aka "enacting" a release)

TODO: describe other things that may be outcomes of the release process 

TODO: show configuration parameters and sample calls of admin release tool

Releasing Data in Other Formats

TODO: describe what would be needed to release data in other formas.

References/Links

• n/a