Date: Thu, 28 Mar 2024 13:16:56 -0400 (EDT) Message-ID: <1281921785.768.1711646216730@ip-10-208-27-219.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_767_2031084614.1711646216727" ------=_Part_767_2031084614.1711646216727 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This page explains the process and the procedural steps for publishing B= iomedGT content to LexBIG.
The following sections explain the steps for each procedure in the publi= shing process.
Using the Prompt plug-in, a workflow manager follows these steps:
Approximately once a month, Operations publishes the baseline file to Le= xBIG. This section describes each task.
Note
Currently the OWL version of the TDE baseline is loaded into Prot=C3=A9g= =C3=A9 and classified solely for QA purposes. This is to verify that the re= moval of roles did not create any classification issues. Since we are going= to EVS:classify the Ontylog output, this may no longer be nec= essary.
To eliminate unpublishable properties and roles, Operations runs a Promp= t comparison. This procedure accomplishes the following:
Operations generates an Ontylog-formatted file for input into the DTS an= d for download. The baseline processing also generates a flat file for down= load.
Note
This process supports caCORE 3.2. Once caCORE 3.2 is retired, the proces= s 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 met= hod 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 trans= formations 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 ste= ps:
The vocabulary enters the promotion schedule and is given an expected pu= blication 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 webs=
ite. We will push the LexBIG data to the software QA server and make it ava=
ilable on the bioportal-dataqa website.
After the data has been on QA for one to two weeks, we will send deploym= ent requests to move both DTS and LexBIG up to Stage. After a day there, it= can be moved to production.