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

Target selection by ontology #7

Open
leeharland opened this issue Jan 9, 2012 · 6 comments
Open

Target selection by ontology #7

leeharland opened this issue Jan 9, 2012 · 6 comments
Assignees
Milestone

Comments

@leeharland
Copy link

[USC Feedback]
while target ontology is not yet available should be able to pick by any ontology, can prototype using GO?

@askjaer
Copy link
Contributor

askjaer commented Jan 12, 2012

This would be an issue relating to the ConceptWiki API lookup and could perhaps be a feature enhancement to this. I am reassigning this issue to Kees fto get his comment.

@ghost ghost assigned keesburger Jan 12, 2012
@leeharland
Copy link
Author

I think this is more a question of data in the cache. Essentially we need to be able to build and navigate protein taxonomies, so i think this is more a get the data, write the query, write the widget issue

@askjaer
Copy link
Contributor

askjaer commented Jan 12, 2012

It would be cool if we had data on target taxonomies in the LDC such that we could do a target broswing tool like they have on ChEMBL. Doing the tree and the pie chart stuff is very easy in ExtJS and something we would need. Can we get the target ontology/taxonomy used by ChEMBL?

@leeharland
Copy link
Author

There are two answers to this! Firstly, there is a new working group on target ontology that is led by christine which will look to addressing exactly this. The idea to create a full ontology by merging different EFPIA lists. But this will take a long time to deliver. In any case, the functionality we build should be generic. Any tree which has proteins as leaves should be able to be loaded up in the same widget "browse proteins by tree X". So, developing against the GO tree would be the same code as the chembl tree, just a different query. I do like the idea of using the chembl tree BUT i am not sure if its in the RDF we have. We need to check if that data has been RDFised, if not then we cant do this and should choose GO.

@leeharland
Copy link
Author

At the TTF the manchester group agreed to look into this, a series of areas to consider:

  1. Is the target tree from chembl available (check with egon)
  2. Can we load GO + GOA into the system to enable queries of the form "give me a list of proteins who are defined by the ontology node X". This of course should include all proteins attached to siblings of that node
  3. with sune/steve, look at tree widgets that could be used in the GUI to select nodes in the first place

@leeharland
Copy link
Author

Oh, and 4. decide which order we can do these 2 examples, GO or chembl tree first (or both together)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants