NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

Contents

About this page

This page explains the operational procedure required to keep Protégé running and publishing data in a clean and well-controlled fashion.

There are two aspects to Protégé operations:

Updating of Protégé software

The Protégé application is undergoing active, continual development. The EVS has extended Protégé using the following plug-ins:

  • NCI Edit tab
  • NCI Workflow tab
  • NCI Code Generator
  • NCI Changes tab
  • Chat tab
  • Prompt tab

As we continue to develop these plug-ins, they need to be tested and eventually moved into the production editing environment.

Publication of data edited in Protégé

This section discusses three aspects of publishing data that has been edited in Protégé:

Publishing to the BiomedGT Wiki

This section discusses two typical scenarios for publishing to the BiomedGT Wiki from Protégé:

Single concept publishing

In this scenario, an editor completes editing of a concept and clicks a Publish button to push data to the Wiki.

Publication of structural changes to vocabulary

In this scenario, new roles are added to or removed from the vocabulary. (Roles are rarely removed.) Properties could be added or have their list values modified. These changes are not things done by editors but are instead done by administrators of the vocabulary. These changes will also need to make their way to the Wiki when they occur.

Publishing the NCI Thesaurus to the DTS (caCORE 3.2)

The caCORE 3.2 will still be supported for many months after we have moved to working on the NCI Thesaurus in Protégé. This will require us to export data from Protégé to an OWL file, then converting this to a vaild Ontylog formatted file for loading into DTS.

Publishing of NCI Thesaurus and BiomedGT to LexBIG (evsapi 4.0)

The evsapi 4.0 , and versions moving forward, will be supported using LexBIG. The LexBIG application takes the OWL format directly for import. There will be several QA points that need to be implemented in this publication tract. The procedure for publishing data to LexBIG (and DTS) can be found here: BiomedGT Publishing to LexBIG

  • No labels