63d2e22e2faf0c23235a743c35b0d52755e455b9
gperez2
  Thu Jun 5 15:58:39 2025 -0700
Updating the EVA SNP track description page, adding pennantIcon, and adding beta tag, refs #35504

diff --git src/hg/makeDb/trackDb/evaSnpContainer.html src/hg/makeDb/trackDb/evaSnpContainer.html
index 3c57cd10b7b..c9db5f626d1 100644
--- src/hg/makeDb/trackDb/evaSnpContainer.html
+++ src/hg/makeDb/trackDb/evaSnpContainer.html
@@ -38,31 +38,31 @@
 <p>Variants can be filtered using the track controls to show subsets of the 
 data by either EVA Sequence Ontology (SO) term, UCSC-generated functional effect, or
 by color, which bins the UCSC functional effects into general classes.</p>
 
 <h3>Mouse-over</h3>
 <p>
 Mousing over an item shows the ucscClass, which is the consequence according to the
 <a target="_blank" href="/cgi-bin/hgVai">Variant Annotation Integrator</a>, and
 the aaChange when one is available, which is the change in amino acid in HGVS.p
 terms. Items may have multiple ucscClasses, which will all be shown in the mouse-over
 in a comma-separated list. Likewise, multiple HGVS.p terms may be shown for each rsID
 separated by spaces describing all possible AA changes.</p>
 <p>
 Multiple items may appear due to different variant predictions on multiple gene transcripts.
 For all organisms, the gene models used were the NCBI RefSeq curated when available, if not then 
-ensembl genes, or finally UCSC mappings of RefSeq if neither of the previous models was possible.
+ensembl genes, or finally, UCSC mappings of RefSeq if neither of the previous models was possible.
 </p>
 
 <h3>Track colors</h3>
 
 <p>
 Variants are colored according to the most potentially deleterious functional effect prediction
 according to the Variant Annotation Integrator. Specific bins can be seen in the Methods section
 below.
 </p>
 
 <p>
 <table cellpadding='2'>
   <thead><tr>
     <th style="border-bottom: 2px solid;">Color</th>
     <th style="border-bottom: 2px solid;">Variant Type</th>
@@ -71,41 +71,41 @@
   <tr><td style="background-color: green"></td><td>Synonymous codon variants</td></tr>
   <tr><td style="background-color: blue"></td><td>Non-coding transcript or Untranslated Region (UTR) variants</td></tr>
   <tr><td style="background-color: black"></td><td>Intergenic and intronic variants</td></tr>
 </table>
 </p>
 
 <h3>Sequence Ontology (SO)</h3>
 
 <p>
 Variants are classified by EVA into one of the following <a target="_blank"
 href="http://www.sequenceontology.org/">sequence ontology</a> terms:
 </p>
 
 <ul>
   <li> <b>substitution</b> &mdash;
-       A single nucleotide in the reference is replaced by another, alternate allele
+       A single nucleotide in the reference is replaced by another, alternate allele.
   <li> <b>deletion</b> &mdash; 
        One or more nucleotides are deleted.  The representation in the database is to
        display one additional nucleotide in both the Reference field (Ref) and the 
        Alternate Allele field (Alt).  E.g. a variant that is a deletion of an A
        maybe be represented as Ref = GA and Alt = G.
   <li> <b>insertion</b> &mdash; 
        One or more nucleotides are inserted.  The representation in the database is to
        display one additional nucleotide in both the Reference field (Ref) and the 
        Alternate Allele field (Alt).  E.g. a variant that is an insertion of a T may 
-       be represented as Ref = G and Alt = GT 
+       be represented as Ref = G and Alt = GT.
   <li> <b>delins</b> &mdash; 
        Similar to a tandem repeat, in that the runs of Ref and Alt Alleles are of
        different length, except that there is more than one type of nucleotide,
        e.g., Ref = CCAAAAACAAAAACA, Alt = ACAAAAAC.
   <li> <b>multipleNucleotideVariant</b> &mdash; 
        More than one nucleotide is substituted by an equal number of different 
        nucleotides, e.g.,  Ref = AA, Alt = GC.
   <li> <b>sequence alteration</b> &mdash;
        A parent term meant to signify a deviation from another sequence. Can be
        assigned to variants that have not been characterized yet.
 </ul>
 </p>
 
 <h2>Methods</h2>
 <p>
@@ -140,62 +140,62 @@
 
 <p>
 Sequence Ontology (&quot;<a href="http://www.sequenceontology.org/browser/current_release"
 target="_blank">SO</a>:&quot;)
 terms were converted to the variant classes, then the files were converted to BED,
 and then bigBed format.
 </p>
 <p>
 No functional annotations were provided by the EVA (e.g., missense, nonsense, etc).
 These were computed using UCSC's Variant Annotation Integrator (Hinrichs, et al., 2016).
 Amino-acid substitutions for missense variants are based
 on RefSeq alignments of mRNA transcripts, which do not always match the amino acids
 predicted from translating the genomic sequence.  Therefore, in some instances, the
 variant and the genomic nucleotide and associated amino acid may be reversed.
 E.g., a Pro &gt; Arg change from the perspective of the mRNA would be Arg &gt; Pro from
-the persepective the genomic sequence. Also, in  bosTau9, galGal5, rheMac8, 
-danRer10 and danRer11 the mitochondrial sequence was removed or renamed to match UCSC. 
+the perspective of the genomic sequence. Also, in bosTau9, galGal5, rheMac10,
+and danRer11 the mitochondrial sequence was removed or renamed to match UCSC.
 For complete documentation of the processing of these tracks, see the makedoc corresponding
 to the version of interest. For example, the
-<a href="https://github.com/ucscGenomeBrowser/kent/blob/master/src/hg/makeDb/doc/evaSnp6.txt">
-EVA Release 6 MakeDoc</a>.</p>
+<a href="https://github.com/ucscGenomeBrowser/kent/blob/master/src/hg/makeDb/doc/evaSnp7.txt">
+EVA Release 7 MakeDoc</a>.</p>
 
 <h2>Data Access</h2>
 <p>
 <b>Note:</b> It is not recommended to use LiftOver to convert SNPs between assemblies,
 and more information about how to convert SNPs between assemblies can be found on the following
 <a href="/FAQ/FAQreleases.html#snpConversion">FAQ entry</a>.</p>
 <p>
 The data can be explored interactively with the <a href="/cgi-bin/hgTables">Table Browser</a>,
 or the <a href="/cgi-bin/hgIntegrator">Data Integrator</a>. For automated analysis, the data may be
 queried from our <a href="/goldenPath/help/api.html">REST API</a>. Please refer to our
 <a href="https://groups.google.com/a/soe.ucsc.edu/forum/#!forum/genome">mailing list archives</a>
 for questions, or our <a href="/FAQ/FAQdownloads.html#download36">Data Access FAQ</a> for more
 information.</p>
 
 <p>
 For automated download and analysis, this annotation is stored in a bigBed file that
 can be downloaded from <a href="https://hgdownload.soe.ucsc.edu/gbdb/$db/bbi/"
 target="_blank">our download server</a>. Use the corresponding version number for the track
-of interest, e.g. <tt>evaSnp6.bb</tt>.
+of interest, e.g. <tt>evaSnp7.bb</tt>.
 Individual regions or the whole genome annotation can be obtained using our tool
 <tt>bigBedToBed</tt> which can be compiled from the source code or downloaded as a precompiled
 binary for your system. Instructions for downloading source code and binaries can be found
 <a href="https://hgdownload.soe.ucsc.edu/downloads.html#utilities_downloads">here</a>.
 The tool can also be used to obtain only features within a given range, e.g.
 <br><br>
-<tt>bigBedToBed https://hgdownload.soe.ucsc.edu/gbdb/$db/bbi/evaSnp6.bb -chrom=chr21 -start=0 -end=100000000 stdout</tt>
+<tt>bigBedToBed https://hgdownload.soe.ucsc.edu/gbdb/$db/bbi/evaSnp7.bb -chrom=chr21 -start=0 -end=100000000 stdout</tt>
 </p>
 
 <h2>Credits</h2>
 <p>
 This track was produced from the <a target="_blank" href="https://www.ebi.ac.uk/eva/">European
 Variation Archive release</a> data. Consequences were predicted using UCSC's Variant Annotation
 Integrator and NCBI's RefSeq as well as ensembl gene models. 
 </p>
 
 <h2>References</h2>
 <p>
 Cezard T, Cunningham F, Hunt SE, Koylass B, Kumar N, Saunders G, Shen A, Silva AF,
 Tsukanov K, Venkataraman S <em>et al.</em> <a href="https://doi.org/10.1093/nar/gkab960"
 target="_blank">The European Variation Archive: a FAIR resource of genomic variation for all
 species</a>.  <em>Nucleic Acids Res.</em> 2021 Oct 28:gkab960.