74c5e052d6546daa0cdf2962b1c1f11961832af5
gperez2
  Tue Oct 29 12:42:40 2024 -0700
Adding the latest nar paper to the htdoc pages, No RM

diff --git src/hg/htdocs/cite.html src/hg/htdocs/cite.html
index 72ea59d..99fe387 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/37953330/">PMID 37953330</a>,
-DOI 10.1093/nar/gkad987. In addition, you can reference the Genome Browser website
+href="https://pubmed.ncbi.nlm.nih.gov/39460617/">PMID 39460617</a>,
+DOI 10.1093/nar/gkae974. 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>