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] Feedback from yuki

y-yamagata y-yamagata at
Sat Apr 13 01:08:17 PDT 2019

Hi Michael,

Thank you very much for your detailed investigation.
I can browse my ontology!

With regard to the mapping problem, I only reuse the external ontology term UBERON_0001062, Anatomical entity. The term is also used for many other existing ontologies. I'm not sure why other ontologies do not generate errors.
Also, I guess errors may be more likely to occur as the upper-level entities since they are mapped to more ontologies.

I have annotated manually, so,there might be some other mappings to ontologies that does not exist due to typographical errors during construction. I would be grateful if you could tell me such errors if you have already found automatically.  


-----Original message-----
From:Michael Dorf<mdorf at>
To:y-yamagata<y-yamagata at>
Cc:John Graybeal<jgraybeal at>,support at<support at>
Date: Sat, 13 Apr 2019 05:54:52
Subject: Re: [bioontology-support] Feedback from yuki
Hi Yuki, 

We’ve deployed a fix to our production servers this morning that addressed the issue with viewing classes of your ontology. You should now be able to browse your ontology without issues:

I did not want to include the nitty gritty of the problem, but if you are curious, the two Github issues below provide more detail: 

Unfortunately, the problem with mappings still remains. The error is triggered by a mapping to a non-existent ontology (BILA) that is found in this class:

We are looking into ways of addressing this issue, but it may not happen immediately.

Again, sorry for all the troubles with your ontology.


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

More information about the bioontology-support mailing list