ef4c8110691d5214eff9858bc936929370dd47bf
mspeir
  Wed Sep 18 08:56:04 2024 -0700
updating to point to 2024 NAR article, refs #34463

diff --git src/hg/htdocs/cite.html src/hg/htdocs/cite.html
index b6ee1f1..72ea59d 100755
--- src/hg/htdocs/cite.html
+++ src/hg/htdocs/cite.html
@@ -5,32 +5,32 @@
 <!-- Relative paths to support mirror sites with non-standard GB docs install -->
 <!--#include virtual="$ROOT/inc/gbPageStart.html" -->
 
 <h1>Citing the UCSC Browser in a Publication or Web Page</h1>
 <p>
 <b>You are free to use all graphics produced by this website in your published work or on other websites</b>, 
 there is no need to contact us to request permission. See the <a href="/license/">license page</a> for details.</p>
 
 <h2>How to cite the UCSC Genome Browser</h2>
 <p>
 The UCSC Genome Browser is exclusively funded by the NIH, please consider citing us properly 
 so that we may report usage and continue to develop this resource.</p>
 <h3>What manuscript to cite?</h3>
 <p>
 Please cite our latest paper, currently <a target=_blank 
-href="https://pubmed.ncbi.nlm.nih.gov/36420891/">PMID 36420891</a>, 
-DOI 10.1093/nar/gkac1072. In addition, you can reference the Genome Browser website 
+href="https://pubmed.ncbi.nlm.nih.gov/37953330/">PMID 37953330</a>,
+DOI 10.1093/nar/gkad987. In addition, you can reference the Genome Browser website
 in your manuscript: <a href="index.html" target="_blank">http://genome.ucsc.edu</a> or 
 mention in the text that you used the "UCSC Genome Browser". To cite one of our 
 computational tools, see the <a href="#ref">reference section</a> below.</p>
 
 <h3>General best practices for publications</h3>
 <p>
 The following are recommendations to improve communication in your
 scientific manuscript and ensure readers in 10 years can still find the
 DNA sequence that you analyzed. This requires mention of the assembly, 
 chromosome position, any transcripts, and ideally also a 
 Genome Browser stable link:</p>
 <ol>
 <li><b>Assembly:</b> Provide a clear mention of which genome assembly you are working with, e.g. 
 "hg19" or "hg38". It is often helpful to place the assembly name directly on 
 any supplemental file names if they contain annotations. E.g. "promoters.hg38.bed".</li>