Annotation Extension for GO terms
3
1
Entering edit mode
Michele ▴ 90
@michele-5671
Last seen 8.7 years ago
United States

Hello,

I am interested in searching for all GO terms associated with a specific cell type or tissue.

In

http://wiki.geneontology.org/index.php/Annotation_Extension:_Capturing_cell_and_tissue_types

I see that in the "Extension" field of GO I would find this type of information, referenced to other ontologies as well.

However, I tried to obtain the same information with GO.db and rols, with no success. Specifically, I tried to replicate the use cases in the above link. 

I tried to retrieve all the terms from GO.db and then checked all the GOXXPARENTS, to see if any of the parents has the "occurs_in" relationship with its children, and I found none.

I feel that I am completely off, does anybody have any suggestion on how to retrieve the annotation extension information from R?

Thanks,

Mic

 

gene ontology rols • 1.5k views
ADD COMMENT
2
Entering edit mode
Marc Carlson ★ 7.2k
@marc-carlson-2264
Last seen 7.7 years ago
United States

Hi Michele,

The traditional GO doesn't have any ontology for tissue type.  There is an ontology for biological process (BP), molecular function (MF) and for cellular component (CC).  But there is not a GO for tissue type or anatomical location.  It looks like right now GO is essentially telling people to use other peoples terms for annotating those kinds of things when describing genes (IOW using other peoples IDs and ontologies such as Uberon or cell ontology).

Since that is the case, you can't directly look up GO terms that are associated with a specific tissue type unless the GO actually added a new ontology, or you had some domain specific knowledge to leverage (which could include annotations from other ontologies).  But the gene ontology alone cannot indicate tissue.  So if for example, you wanted to study GO terms that relate only to muscle cell development, you have to know somehow which specific processes are specifically involved in that and then go after those terms (and their child terms).

As for looking up all the specific children for a GO Term here is how you could do that:

library(GO.db) 
muscleProcessID = "GO:0003012"
muscleIDs = unlist(mget(muscleProcessID,GOBPOFFSPRING),use.names=FALSE) 
muscleIDs = c(muscleProcessID,muscleIDs)

And once you have those, you could then take those IDs to something like an org package and look up things like associated gene IDs etc. like this

library(org.Hs.eg.db) 
select(org.Hs.eg.db, muscleIDs, 'SYMBOL', 'GO')

Hope this helps.   If you would like to contribute some more packages to help us also cover some of these other ontologies, then please feel free to contact me. 

ADD COMMENT
0
Entering edit mode
@laurent-gatto-5645
Last seen 2 days ago
Belgium

Dear Michele,

I am afraid that rols will not be of any help here. The ols webservice does not provide access to the term hierarchy. You can get cross references (termXrefs), but I don't think this is will get you want you want.

Have you come across any software or online ressource that implemented extensions across ontologies?

ADD COMMENT
0
Entering edit mode
Michele ▴ 90
@michele-5671
Last seen 8.7 years ago
United States

Hi Laurent,

thanks for your reply.

I found that AmiGO supports such information: if you look at the

http://amigo.geneontology.org/amigo/gene_product/UniProtKB:P63027

page, downloading the table of results shows that some of the terms associated with the gene product are cross-referenced to other ontologies (UBERON and CL).

However, I was not able to retrieve the same information from GO.db.

I was thinking of using SPARQL to find this information, but I admit that I am not proficient enough in SPARQL queries.

Any thought?

 

ADD COMMENT
0
Entering edit mode

Have you tried the check the RamiGO package? I have only used it to draw GO trees, but it might do more. That's all I can think of right now.

ADD REPLY

Login before adding your answer.

Traffic: 938 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6