NCBI Bookshelf. A service of the National Library of Medicine, National Institutes of Health.
SNP FAQ Archive [Internet]. Bethesda (MD): National Center for Biotechnology Information (US); 2005-.
This publication is provided for historical reference only and the information may be out of date.
rs4646149 shows the submission of ss69370884 in build 127 on the website, but there's no record of that submission in the dbSNP FTP SubSNP.bcp file.
ss69370884 was submitted on March 22, 2007, but the SubSNP.bcp file on FTP site was created on March 6, 2007. Build 127 was released on March 8, 2007.
In general, new submitted SNPs (ss) are made public more frequently than there are SNP build releases so submitters can see their submissions more quickly(without having to wait months for a new build release). In the past, new submitted SNPs were not clustered until the new build.
Beginning in May 2007, however, we cluster the new submitted SNPs as they arrive, so when these submitted SNPs (including ss69370884) are made public they also show up in their clusters, as you have observed. All the table .bpc files, however, are created only once per build, so that is why you don't see this submitted SNP in the .bcp files. (7/2/07)
- Lag Time between dbSNP Website and FTP Site Following Build - SNP FAQ ArchiveLag Time between dbSNP Website and FTP Site Following Build - SNP FAQ Archive
- Data Changes that Occur Between Builds - SNP FAQ ArchiveData Changes that Occur Between Builds - SNP FAQ Archive
- The SNP Build Schedule/Notification of Build Release - SNP FAQ ArchiveThe SNP Build Schedule/Notification of Build Release - SNP FAQ Archive
- What Triggers a New Build? - SNP FAQ ArchiveWhat Triggers a New Build? - SNP FAQ Archive
- The dbSNP Build Process - SNP FAQ ArchiveThe dbSNP Build Process - SNP FAQ Archive
Your browsing activity is empty.
Activity recording is turned off.
See more...