<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.E-MailFormatvorlage19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>Hi Anja,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>thank you very much for that information!<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The ftp data set of dbsnp was exactly what I was searching for. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Pretty large data size but should not be a problem for our pipeline.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks for pointing me to it!<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Best regards,<o:p></o:p></p><p class=MsoNormal>Danny<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=DE>Von:</span></b><span lang=DE> Dev <dev-bounces@ensembl.org> <b>Im Auftrag von </b>Anja Thormann<br><b>Gesendet:</b> Montag, 22. März 2021 12:37<br><b>An:</b> Ensembl developers list <dev@ensembl.org><br><b>Betreff:</b> Re: [ensembl-dev] FTP + variation rs id synonym mappings<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi Danny,<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal>you will get the most detailed information on the merge history of an rs id from dbSNP.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I recommend that you take a look at dbSNP's API:<o:p></o:p></p></div><div><p class=MsoNormal><a href="https://api.ncbi.nlm.nih.gov/variation/v0/">https://api.ncbi.nlm.nih.gov/variation/v0/</a><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Or flat files from:<o:p></o:p></p></div><div><p class=MsoNormal><a href="https://ftp.ncbi.nih.gov/snp/latest_release/">https://ftp.ncbi.nih.gov/snp/latest_release/</a><o:p></o:p></p></div><div><p class=MsoNormal>This file contains the merge information: <a href="https://ftp.ncbi.nih.gov/snp/latest_release/JSON/refsnp-merged.json.bz2">https://ftp.ncbi.nih.gov/snp/latest_release/JSON/refsnp-merged.json.bz2</a><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>And here is an example of using the API:<o:p></o:p></p></div><div><p class=MsoNormal>Getting information for rs10001600 (<a href="https://www.ncbi.nlm.nih.gov/snp/rs10001600">https://www.ncbi.nlm.nih.gov/snp/rs10001600</a>):<o:p></o:p></p></div><div><p class=MsoNormal><a href="https://api.ncbi.nlm.nih.gov/variation/v0/beta/refsnp/10001600">https://api.ncbi.nlm.nih.gov/variation/v0/beta/refsnp/10001600</a> where merged_snapshot_data stores the id history.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>We are not extracting the full merge history for each rs id into Ensembl and therefore wouldn’t give a complete picture and decided against adding this information into our data dumps.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Best wishes,<o:p></o:p></p></div><div><p class=MsoNormal>Anja<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>On 18 Feb 2021, at 18:08, Andrew Parton <<a href="mailto:aparton@ebi.ac.uk">aparton@ebi.ac.uk</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>Hi Danny,<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Currently, we do not have a file contains all of these mappings. However, VEP will allow you to annotate your VCFs with the variation synonym data that we have, by providing known synonyms for colocated variants: <a href="https://www.ensembl.org/info/docs/tools/vep/script/vep_options.html#opt_var_synonyms">https://www.ensembl.org/info/docs/tools/vep/script/vep_options.html#opt_var_synonyms</a><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Additionally, it may be possible for us to generate these synonyms in a single file as part of our next release, however VEP should be a quicker solution for you.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Kind Regards,<o:p></o:p></p></div><div><p class=MsoNormal>Andrew<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><div><p class=MsoNormal><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>On 12 Feb 2021, at 05:29, <a href="mailto:danny.kunz@gmx.de">danny.kunz@gmx.de</a> wrote:<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>Hi all,<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>Quick question:<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>Our pipeline has to deal with VCF from older assembly releases from the GRCH37 branch.<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>We tried utilizing the FTP variation VCF files, but realized that we only have hits in about 40% of the patient VCF ids matched within the FTP variation data.<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>Obviously the old rs ids (synonyms) from the older assemblies are not contained in those newer releases.<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>Is there any file on the FTP which contains those synonym mappings?<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>-<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>Calling the REST api does not cause a problem with the old rs ids as it translates them to the newer ones, but if we want to reduce the REST communication overhead, it would be helpful to be able to achieve the same with the FTP data, right?<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>Thanks,<o:p></o:p></p></div><div><p class=MsoNormal>Danny<o:p></o:p></p></div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'>_______________________________________________<br>Dev mailing list </span><a href="mailto:Dev@ensembl.org"><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'>Dev@ensembl.org</span></a><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'><br>Posting guidelines and subscribe/unsubscribe info:<span class=apple-converted-space> </span></span><a href="https://lists.ensembl.org/mailman/listinfo/dev_ensembl.org"><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'>https://lists.ensembl.org/mailman/listinfo/dev_ensembl.org</span></a><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'><br>Ensembl Blog:<span class=apple-converted-space> </span></span><a href="http://www.ensembl.info/"><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'>http://www.ensembl.info/</span></a><o:p></o:p></p></div></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></div><p class=MsoNormal>_______________________________________________<br>Dev mailing list <a href="mailto:Dev@ensembl.org">Dev@ensembl.org</a><br>Posting guidelines and subscribe/unsubscribe info: <a href="https://lists.ensembl.org/mailman/listinfo/dev_ensembl.org">https://lists.ensembl.org/mailman/listinfo/dev_ensembl.org</a><br>Ensembl Blog: <a href="http://www.ensembl.info/">http://www.ensembl.info/</a><o:p></o:p></p></div></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>