Linking Rosetta gene accession numbers to GO terms
1
0
Entering edit mode
@goeman-jj-mstat-696
Last seen 10.3 years ago
Dear all, Is there an annotation function in BioConductor to map "Gene Accession Numbers" from a Rosetta chip to GO terms and vice versa? Here's 10 gene accession numbers as an example: [1,] "Contig9452_RC" [2,] "NM_003088" [3,] "Contig13822_RC" [4,] "Contig50838_RC" [5,] "D42043" [6,] "NM_000900" [7,] "NM_001630" [8,] "D42047" [9,] "NM_000902" [10,] "NM_000903" I'd be grateful if someone knows how to do this. Kind regards, Jelle Goeman http://www.math.leidenuniv.nl/~jgoeman
Annotation GO Annotation GO • 644 views
ADD COMMENT
0
Entering edit mode
John Zhang ★ 2.9k
@john-zhang-6
Last seen 10.3 years ago
>Is there an annotation function in BioConductor to map "Gene Accession >Numbers" from a Rosetta chip to GO terms and vice versa? > >Here's 10 gene accession numbers as an example: > > [1,] "Contig9452_RC" > [2,] "NM_003088" > [3,] "Contig13822_RC" > [4,] "Contig50838_RC" > [5,] "D42043" > [6,] "NM_000900" > [7,] "NM_001630" > [8,] "D42047" > [9,] "NM_000902" >[10,] "NM_000903" The AnnBuilder package has functions that map GenBank accession number (D42043 and alike) and RefSeq ids (NM_003088 and alike) to LocusLink ids and then build an annotation data package that contains GO annotations. You can do this if you are willing to convert the other ids (Contig9452_RC and alike) to eith GenBank, RefSeq, or LocusLink ids. > >I'd be grateful if someone knows how to do this. > >Kind regards, > >Jelle Goeman > >http://www.math.leidenuniv.nl/~jgoeman > >_______________________________________________ >Bioconductor mailing list >Bioconductor@stat.math.ethz.ch >https://www.stat.math.ethz.ch/mailman/listinfo/bioconductor Jianhua Zhang Department of Biostatistics Dana-Farber Cancer Institute 44 Binney Street Boston, MA 02115-6084
ADD COMMENT

Login before adding your answer.

Traffic: 571 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