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] [BioPortal] Feedback from brycemecum

Jennifer Leigh Vendetti vendetti at
Mon Jul 29 15:49:03 PDT 2019


On Jul 26, 2019, at 7:17 PM, support at<mailto:support at> wrote:

I'm using the term lookup API to find information such as prefLabels for URIs I have. This has mostly worked perfectly (thank you!) but I noticed one oddity:

When searching with the URI "", which is a term from the UO ontology, the first result from the API is for what appears to be an import of the term into the EFO ontology. The second result is for an instance of the term in the CHEAR ontology and finally, the third result is for the instance of it in UO which is the one I really want.

We have an internal script that runs once per week to calculate an ontology ranking list:

Here’s an example snapshot of what the ranking file looks like:

 The BioPortal REST API will order the search results according to ontology rank, which is why EFO and CHEAR appear above UO.

You mentioned that the result from UO is the one you really want. I’m not sure if you’re aware that you can narrow your search results to a particular ontology using the “ontologies” parameter, e.g.:<>

A complete list of the parameters you can use with the search endpoint is available in the documentation:

It'd be really great if the API had listed the result from UO first. The web-based seach does this:

Apologies that I don’t have an immediate response to this last part of your message. I’m unclear on why the BioPortal web application (which is built on top of the REST API) is showing the ordering differently. I would need to investigate the code further.

Kind regards,

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

More information about the bioontology-support mailing list