<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Kiran,<div><br></div><div>For the RefSeq models, RefSeq provides us with a flat file giving the genomic coordinates for all genes, transcripts and exons in their gene set. We load this up directly into the otherfeatures database and do not change any coordinates.</div><div><br></div><div>For the CCDS models, our collaboration in the project allows us access to an ftp site that provides daily dumps of the most current CCDS set. Again, the location of genes, transcripts and exons are provided in genomic coordinates and we just load the models into the otherfeatures database. The date for the gene stable IDs is the date of the data freeze when we dumped from the ftp site.</div><div><br></div><div>Thanks,</div><div>Bronwen</div><div><br></div><div><br></div><div><br><div><div>On 27 May 2011, at 18:25, Kiran Mukhyala wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Could someone also explain how RefSeq and CCDS are imported into the otherfeatures database. I'd like to know the source of the exon structures.<br><br>Thanks,<br>-Kiran<br><br><div class="gmail_quote">On Thu, May 26, 2011 at 9:48 PM, Reece Hart <span dir="ltr"><<a href="mailto:reece@harts.net">reece@harts.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi-<div><br></div><div><span style="border-collapse:collapse;font-family:arial, sans-serif;font-size:13px">Does anyone know whether it would work to load NCBI exon structures directly into Ensembl?</span></div>
<div><span style="border-collapse:collapse;font-family:arial, sans-serif;font-size:13px"><br></span></div><div><span style="border-collapse:collapse;font-family:arial, sans-serif;font-size:13px"></span><span style="border-collapse:collapse;font-family:arial, sans-serif;font-size:13px">The goal is to use the Ensembl API to map between genome, transcript, and protein coordinates for variants specified using NCBI accessions. This requires exact NCBI exon structures.</span></div>
<div><span style="border-collapse:collapse;font-family:arial, sans-serif;font-size:13px"><br></span></div><div><span style="border-collapse:collapse;font-family:arial, sans-serif;font-size:13px"></span><span style="border-collapse:collapse;font-family:arial, sans-serif;font-size:13px">I'm hoping that populating the transcript, transcript_stable_id, exon, and exon_transcript tables with original NCBI data would suffice.</span></div>
<div><font face="arial, sans-serif"><span style="border-collapse:collapse"><br></span></font></div><div><font face="arial, sans-serif"><span style="border-collapse:collapse"><span style="font-size:13px">As Kiran Mukhyala pointed out in a separate thread, the RefSeq sequence differs from the GRCh37 sequence in some cases. I am content with using RefSeq exon structures on GRCh37.</span></span></font></div>
<div><font face="arial, sans-serif"><span style="border-collapse:collapse"><br></span></font></div><div><font face="arial, sans-serif"><span style="border-collapse:collapse">All code and advice is appreciated.</span></font></div>
<div><font face="arial, sans-serif"><span style="border-collapse:collapse"><br></span></font></div><div>Thanks,</div>
<div>Reece</div>
<br>_______________________________________________<br>
Dev mailing list <a href="mailto:Dev@ensembl.org">Dev@ensembl.org</a><br>
List admin (including subscribe/unsubscribe): <a href="http://lists.ensembl.org/mailman/listinfo/dev" target="_blank">http://lists.ensembl.org/mailman/listinfo/dev</a><br>
Ensembl Blog: <a href="http://www.ensembl.info/" target="_blank">http://www.ensembl.info/</a><br>
<br></blockquote></div><br>
_______________________________________________<br>Dev mailing list <a href="mailto:Dev@ensembl.org">Dev@ensembl.org</a><br>List admin (including subscribe/unsubscribe): <a href="http://lists.ensembl.org/mailman/listinfo/dev">http://lists.ensembl.org/mailman/listinfo/dev</a><br>Ensembl Blog: <a href="http://www.ensembl.info/">http://www.ensembl.info/</a><br></blockquote></div><br></div></body></html>