{scrollbar:icons=false} |
This page explains the process and the procedural steps for publishing BiomedGT content to LexBIG.
The following sections explain the steps for each procedure in the publishing process.
Using the Prompt plug-in, a workflow manager follows these steps:
Approximately once a month, Operations publishes the baseline file to LexBIG. This section describes each task.
Currently the OWL version of the TDE baseline is loaded into Protégé and classified solely for QA purposes. This is to verify that the removal of roles did not create any classification issues. Since we are going to EVS:classify the Ontylog output, this may no longer be necessary. |
To eliminate unpublishable properties and roles, Operations runs a Prompt comparison. This procedure accomplishes the following:
Operations generates an Ontylog-formatted file for input into the DTS and for download. The baseline processing also generates a flat file for download.
This process supports caCORE 3.2. Once caCORE 3.2 is retired, the process will be discontinued. |
This resides side by side with the previous PRODUCTION version.
These scripts will most likely be run against the LexBIG API, since that is the form in which the user will see the data.
Operations loads the Ontylog version of the vocabulary into DTS. The method of loading requires that the data be loaded into TDE, classified, then transferred into DTS using Apelon-created applications.
The classification step can be considered a QA marker, as some bad transformations can cause classification to fail. Bad formatting can also result in a failure to load to TDE or to transfer to the DTS.
Once the tests return satisfactory results, Operations follows these steps:
The vocabulary enters the promotion schedule and is given an expected publication date in the EVS schedule.
Notes:
The data on Dev will be transferred up the tiers along parallel tracks. We will push the DTS data to QA and make it available on the nciterms-qa website. We will push the LexBIG data to the software QA server and make it available on the bioportal-dataqa website.
After the data has been on QA for one to two weeks, we will send deployment requests to move both DTS and LexBIG up to Stage. After a day there, it can be moved to production.
{scrollbar:icons=false} |