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] new Bio API

Ray Fergerson ray.fergerson at
Tue Feb 25 14:57:20 PST 2014



This information doesn't get expanded anymore because we thought that very
few users would actually want it and it greatly slows down the call for
everyone else.


Can you tell me what your use case is for needed the user information for
all ontologies? This doesn't seem very common. As an aside, since the user
data only very rarely changes, you could instead just get the all user
information and cache it on your side. You wouldn't need to retrieve it on
every call.




From: Sergey Nikitin [mailto:snikitin at] 
Sent: Tuesday, February 25, 2014 2:20 AM
To: support at
Cc: Bob Stanley; musen at; Erich Gombocz;
ray.fergerson at
Subject: new Bio API


Hi Support, 


    In the old API the ontologies request returned a lot of information
about each item. We are trying to find a way to receive alomost the same
results with the new API. 


            In the new API one can receive an ontology list in json format
using URL:{api-key}


    The result structures contain links to other objects, like:


"administeredBy": [





     Is there a way to receive ontologies with data obtained by following
the links in one request? For example:


"administeredBy": [ <> "

.         username": "pjd",

.         "email": "pdevries at",

.         "role": [ 



.         "@id":  <>

.         "@type":  <>


"@context": { 

o    "@vocab":  <>




 Perhaps, this is not the right approach? Then, what you recommend? loads pretty fast. We want
to achive the same result.



Sergey Nikitin

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

More information about the bioontology-support mailing list