Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Asserted hierarchy is not displayed correctly in some cases when equivalent named classes are present #847

Closed
nicolevasilevsky opened this issue Feb 5, 2019 · 14 comments
Assignees
Labels
Status: Fixed Added to indicate that a closed issue represents a bug that has been fixed Type: Bug Indicates that Protege is not working as expected

Comments

@nicolevasilevsky
Copy link

nicolevasilevsky commented Feb 5, 2019

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:
image

Thanks for looking into this. Let me know if you need any other info.

@csnyulas
Copy link
Member

csnyulas commented Feb 5, 2019

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?

@csnyulas csnyulas added the Status: Waiting for Feedback Indicates that the person who is working on the issue needs feedback from someone else label Feb 5, 2019
@nicolevasilevsky
Copy link
Author

Hi @csnyulas, unfortunately that is not the case, I don't see the class if I scroll.

@matthewhorridge
Copy link
Contributor

Hi @nicolevasilevsky!

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:

image

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!

@matthewhorridge matthewhorridge added Status: Needs Reproducing Assigned to things that are bugs, but that have not been checked and removed Status: Waiting for Feedback Indicates that the person who is working on the issue needs feedback from someone else labels Feb 5, 2019
@matthewhorridge matthewhorridge self-assigned this Feb 5, 2019
@matthewhorridge matthewhorridge added this to the Protégé 5.5.0 milestone Feb 5, 2019
@matthewhorridge
Copy link
Contributor

@nicolevasilevsky I've cloned the repo and I'll open cell-edit.owl (sorry, didn't see this before!)

@matthewhorridge matthewhorridge added Type: Bug Indicates that Protege is not working as expected Status: Reproduced For issues that are (critical) bugs, denotes that the bug is reproduced, but no further action taken and removed Status: Needs Reproducing Assigned to things that are bugs, but that have not been checked labels Feb 5, 2019
@matthewhorridge
Copy link
Contributor

@nicolevasilevsky I can reproduce this, will look into it and thanks for the bug report!

@nicolevasilevsky
Copy link
Author

Hi @matthewhorridge! Thanks for looking into this - it is a really weird bug!

@matthewhorridge
Copy link
Contributor

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?

image

and without the equivalences displayed (perhaps these are unnecessary)

image

@nicolevasilevsky
Copy link
Author

I love it - this is great!

matthewhorridge added a commit that referenced this issue Feb 5, 2019
@matthewhorridge matthewhorridge added Status: Needs Final Testing Indicates that a potential fix is in place and the fix needs manual testing and removed Status: Reproduced For issues that are (critical) bugs, denotes that the bug is reproduced, but no further action taken labels Feb 5, 2019
@matthewhorridge
Copy link
Contributor

Great. I've just pushed the fix so this will be available in the next beta release (or candidate release)

@nicolevasilevsky
Copy link
Author

Awesome, thank you so much!

@matthewhorridge matthewhorridge changed the title issue with Protege and CL Asserted hierarchy is not displayed correctly in some cases when equivalent named classes are present Feb 5, 2019
@cmungall
Copy link

cmungall commented Feb 6, 2019

this is great, thanks!

@matthewhorridge
Copy link
Contributor

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

image

Here "cell" and "anatomical structure" are disambiguated because this label maps to multiple entities. Unambiguous entries aren't disambiguated.

Any thoughts?

@nicolevasilevsky
Copy link
Author

I love it, I think it is super helpful and clutter is not an issue for me.

@addiehl
Copy link

addiehl commented Feb 6, 2019

Thanks Matthew for fixing this!

@matthewhorridge matthewhorridge added Status: Fixed Added to indicate that a closed issue represents a bug that has been fixed and removed Status: Needs Final Testing Indicates that a potential fix is in place and the fix needs manual testing labels Mar 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Fixed Added to indicate that a closed issue represents a bug that has been fixed Type: Bug Indicates that Protege is not working as expected
Projects
None yet
Development

No branches or pull requests

5 participants