-
Notifications
You must be signed in to change notification settings - Fork 233
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Asserted hierarchy is not displayed correctly in some cases when equivalent named classes are present #847
Comments
Actually, to me it seems that 'native cell' is, in fact, selected in the class hierarchy view, as it is displayed in the title of the view: Class hierarchy: 'native cell'. I expect that if you would scroll down, you would probably see the selection. If this is the case, then the real problem is that the class hierarchy view does not automatically scroll the content of the view as to show the newly selected entity. At least not always. Can you confirm that this is indeed the problem? |
Hi @csnyulas, unfortunately that is not the case, I don't see the class if I scroll. |
I've just had a look at this... I loaded CL from https://raw.githubusercontent.com/obophenotype/cell-ontology/master/cl.owl and then switched to the entities tab and performed a search for 'native cell'. The hierarchy expanded and 'native cell' became selected. What I notice though, is that my hierarchy looks like this: You only have 'abnormal cell' under 'cell' in your screenshot. I have two cell classes, one from CL (CL:0000000) and one from GO (GO:0005623). I therefore think it's possible that I've loaded a different ontology and imports closure to you. Please would you be able to double check the URL for me? Thanks a lot! |
@nicolevasilevsky I've cloned the repo and I'll open cell-edit.owl (sorry, didn't see this before!) |
@nicolevasilevsky I can reproduce this, will look into it and thanks for the bug report! |
Hi @matthewhorridge! Thanks for looking into this - it is a really weird bug! |
Definitely a weird bug with the hierarchy! Basically the issue was that CL cell is equivalent to GO cell and Protege arbitrarily just displayed GO cell. I think I've fixed this problem.... Now both cell classes are displayed. See the screenshot below. Where a short name/label maps into multiple terms I've added disambiguation by including the OBO Id in brackets. @nicolevasilevsky do you think this is a good idea or does it add too much clutter? @cmungall, any thoughts about this? and without the equivalences displayed (perhaps these are unnecessary) |
I love it - this is great! |
Great. I've just pushed the fix so this will be available in the next beta release (or candidate release) |
Awesome, thank you so much! |
this is great, thanks! |
Just another follow up to this. For single entity names, I'm experimenting with disambiguation in the class description view too. So the view for CL cell would be Here "cell" and "anatomical structure" are disambiguated because this label maps to multiple entities. Unambiguous entries aren't disambiguated. Any thoughts? |
I love it, I think it is super helpful and clutter is not an issue for me. |
Thanks Matthew for fixing this! |
This is just an issue for me with Cell Ontology, not any other ontology, and it seems to be an issue with different versions of Protege, I am currently using v5.5.0 beta.
When I search for a class, and click on it in the search box, it will bring up the annotations, but it won't pull up the class in the Class hierarchy pane.
Here is a screenshot, you can see that native cell is not displayed in the Class Hierarchy pane:
Thanks for looking into this. Let me know if you need any other info.
The text was updated successfully, but these errors were encountered: