Search Mailing List Archives

Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[bioontology-support] SNOMED-CT ontology status

Ray Fergerson ray.fergerson at
Fri Oct 11 14:56:42 PDT 2013


This should work now. The most recent version of SNOMED did not load
correctly into the old version of BioPortal, causing this problem. I
simply deleted this last failed attempt so the Protégé plugin should now
work. Will talk to the protégé people here about updating the plugin to
use the new BioPortal instance.


From: bioontology-support-bounces at
[mailto:bioontology-support-bounces at] On Behalf Of Chris
Sent: Thursday, October 10, 2013 5:05 AM
To: Bioportal support
Subject: [bioontology-support] SNOMED-CT ontology status


When I do the ontologies REST call with the old API
( SNOMED-CT has a status
of 4.

This means it doesn't appear as an ontology to use in the Bioportal
Protege 3.5 plugin. It only lets you choose an ontology with a status of

I was wondering what status 4 meant.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the bioontology-support mailing list