76eabae1c28bb07c02af6a12fa9222c348b039d9
max
  Sun Sep 6 07:02:29 2026 -0700
DANIO-CODE: open each subtrack description with the sentence saying that the track is part of the DANIO-CODE container, linking to its hgTrackUi page, instead of burying it in a paragraph at the end of the description. refs #38265

diff --git src/hg/makeDb/trackDb/zebrafish/danRer11/dcEvalidation.html src/hg/makeDb/trackDb/zebrafish/danRer11/dcEvalidation.html
index 59c824e4c7d..ea15a0d81e7 100644
--- src/hg/makeDb/trackDb/zebrafish/danRer11/dcEvalidation.html
+++ src/hg/makeDb/trackDb/zebrafish/danRer11/dcEvalidation.html
@@ -1,37 +1,34 @@
 <h2>Description</h2>
 
 <p>
+This track is part of the <a href="hgTrackUi?g=danioCode">DANIO-CODE</a> track collection.
 A candidate enhancer predicted from chromatin data is a hypothesis until it is tested.
 The usual test in zebrafish is a transgenic reporter assay: the candidate sequence is
 placed in front of a minimal promoter driving a fluorescent protein, the construct is
 injected into embryos, and the embryos are examined for fluorescence. If the sequence
 is an enhancer, the fluorescence appears in a specific tissue at a specific stage.
 </p>
 
 <p>
 This track shows 246 zebrafish enhancers that have been validated this way and that the
 DANIO-CODE consortium collected from the published literature into one curated
 catalogue. The consortium used them as an independent check on its own predictions, and
 they fall predominantly on elements that the chromatin data had classified as
 enhancers.
 </p>
 
-<p>
-This track is part of the <a href="hgTrackUi?g=danioCode">DANIO-CODE</a> collection.
-</p>
-
 <h2>Display Conventions and Configuration</h2>
 
 <p>
 Enhancers are drawn as blocks, in the colors stored in the data file.
 </p>
 
 <h2>Methods</h2>
 
 <p>
 The DANIO-CODE consortium assembled 1,802 zebrafish developmental genomics datasets,
 1,438 of them already published and 366 generated by consortium members, and
 reprocessed all of them from the raw sequencing reads so that samples from different
 laboratories and different protocols can be compared with each other. ChIP-seq and
 ATAC-seq were run through the ENCODE pipelines, CAGE-seq through the FANTOM pipeline,
 and Hi-C and 4C-seq through the pipelines of the groups that produced them. The