Hi, I was wondering if there is a defined policy for Genome Browser track updates? I am most interested in MySQL versions of the tracks available for download. We maintain a local mirror of many UCSC tracks and use them extensively. However, some of the tracks seem to be out of sync with the various external databases and other sources of information they utilize.
I understand updating tracks based on results of previously published research can be difficult without some form of collaboration with the authors. But what about cross-references to external databases? For instance, our validation scripts indicate that currently about 12% of the UniProt identifiers in the hg18.kgXref table are wrong, with the majority of errors coming from incorrectly assigned protein isoforms. dbSNP track also shows substantial number of errors. Considering that dbSNP, RefSeq and UniProtKB databases are all fast moving targets, this accumulation of cross-referencing errors is not surprising. So, what is Genome Browser maintainers position in regard to tracks updates? Best, Ivan -- Ivan Adzhubey, Ph.D. Instructor Division of Genetics, Dept of Medicine Brigham & Women's Hospital, Harvard Medical School HMS New Research Building, Room 0464C 77 Avenue Louis Pasteur Boston, MA 02115 tel.: (617) 525-4728 fax: (617) 525-4705 web: http://genetics.bwh.harvard.edu/genetics/members/Ivan_Adzhubey.html _______________________________________________ Genome maillist - [email protected] https://lists.soe.ucsc.edu/mailman/listinfo/genome
