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

utilize ontology hierarchies in browsing features #89

Open
lwaldron opened this issue Jul 9, 2021 · 3 comments
Open

utilize ontology hierarchies in browsing features #89

lwaldron opened this issue Jul 9, 2021 · 3 comments
Labels
blocked can't be worked on now wishlist wishlist items not currently high priority

Comments

@lwaldron
Copy link
Member

lwaldron commented Jul 9, 2021

The Uberon and Experimental Factor ontologies in use are hierarchical. It would be a powerful drill-down feature to be able to select terms at any level of the hierarchy, and display experiments/signatures matching any children of that term. For example, selecting oral cavity body site would return all the Uberon oral cavity subsites. Or selecting cancer would return experiments from all kinds of cancer in EFO.

@lwaldron lwaldron added the wishlist wishlist items not currently high priority label Jul 9, 2021
@tosfos
Copy link
Collaborator

tosfos commented Aug 24, 2021

I have some ideas about it. And now that we have 28K+ values form Condition, we really should look at an alternative like this to make the Condition data set easier to process and use.

Besides for the hierarchy itself, it would be nice to use all of the data about the condition. I think we're essentially duplicating data that already exists by using the Glossary data structure. It would be nice to just use this external data instead.

@tosfos
Copy link
Collaborator

tosfos commented Sep 6, 2021

We have an idea for how to do this. We'd basically pull data on the fly from their API and use that to display a tree-style component that can be used for both storing the correct ontology value in the form and for later drilling down based on that same tree in order to find all Studies that have an experiment with that value.

This will take some time to get it right, but it will be a great site addition. Can we start with 10 hours of experimenting and seeing where that leaves us?

@lwaldron
Copy link
Member Author

lwaldron commented Sep 7, 2021

It's worth doing eventually, but we should probably do a budget review and prioritize essential items for public release first.

@lgeistlinger lgeistlinger added the blocked can't be worked on now label Sep 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked can't be worked on now wishlist wishlist items not currently high priority
Projects
None yet
Development

No branches or pull requests

3 participants