Hi Adrienne, There were some mapping issues with rs1304710 to the hg19 assembly so it wasn't included with the latest version. Other sources submitted evidence for the same SNP and this was given a new ID of rs75096060 for this version. dbSNP will be incorporating the fixes in their future builds which means that rs1304710 will return and rs75096060 will likely be dropped.
Hopefully that clarifies the issue for you. If you have further questions, please email the list: [email protected]. Vanessa Kirkup Swing UCSC Genome Bioinformatics Group ---------- Forwarded message ---------- From: Tin, Adrienne <[email protected]> Date: Fri, Apr 6, 2012 at 4:34 PM Subject: [Genome] rs1304710 To: "[email protected]" <[email protected]> Dear UCSC Genome Project staff, When I search this SNP, rs1304710, using the March. 2006 (NCBI36/hg18) assembly, this SNP was in dbSNP build 126, 128, 129, 130. Please see rs1304710_UCSC_search_b36.jpg. When I search using Feb. 2009 (GRCh37/hg19) assembly, this SNP is no longer in dbSNP, but still in the HapMap tables. Please see rs1304710_UCSC_search_b37.jpg But the dbSNP RsMergeArch table has no record of the merging of this SNP to a lower rs number. This rs number is also not in SNPHistory. Would you help clarify whether this SNP is in dbSNP build 135? If this SNP is not in build 135, where can I find out why it was removed? Thanks Adrienne Tin Department of Epidemiology Johns Hopkins Bloomberg School of Public Health _______________________________________________ Genome maillist - [email protected] https://lists.soe.ucsc.edu/mailman/listinfo/genome _______________________________________________ Genome maillist - [email protected] https://lists.soe.ucsc.edu/mailman/listinfo/genome
