1cf2d7c2d88b736e4d18e1bff47f16c270470ee1 hiram Tue Jan 14 13:19:13 2020 -0800 now have working dataVersion string in the track details page refs #24748 diff --git src/hg/utils/automation/asmHubNcbiRefSeq.pl src/hg/utils/automation/asmHubNcbiRefSeq.pl index c2a5acf..48c4d58 100755 --- src/hg/utils/automation/asmHubNcbiRefSeq.pl +++ src/hg/utils/automation/asmHubNcbiRefSeq.pl @@ -54,34 +54,31 @@ my $em = "<em>"; my $noEm = "</em>"; my $assemblyDate = `grep -v "^#" $namesFile | cut -f9`; chomp $assemblyDate; my $ncbiAssemblyId = `grep -v "^#" $namesFile | cut -f10`; chomp $ncbiAssemblyId; my $organism = `grep -v "^#" $namesFile | cut -f5`; chomp $organism; print <<_EOF_ <h2>Description</h2> <p> The NCBI RefSeq Genes composite track shows $assemblyDate $em${organism}$noEm/$asmId protein-coding and non-protein-coding genes taken from the NCBI RNA reference -sequences collection (RefSeq). All subtracks use coordinates provided by RefSeq, -except for the <em>UCSC RefSeq</em> track, which UCSC produces by realigning -the RefSeq RNAs to the genome. This realignment may result in occasional -differences between the annotation coordinates provided by UCSC and NCBI. +sequences collection (RefSeq). All subtracks use coordinates provided by RefSeq. See the <a href="#methods">Methods</a> section for more details about how the different tracks were created. </p> <p> Please visit NCBI's <a href="https://www.ncbi.nlm.nih.gov/projects/RefSeq/update.cgi" target="_blank"> Feedback for Gene and Reference Sequences (RefSeq)</a> page to make suggestions, submit additions and corrections, or ask for help concerning RefSeq records. </p> <p> For more information on the different gene tracks, see our <a target=_blank href="/FAQ/FAQgenes.html">Genes FAQ</a>. </p>