8a3f24f0e70e94dc4812283bbd60c715651d6c46
lrnassar
  Mon Nov 3 14:50:27 2025 -0800
Staging the ENCODE4 cCREs track. Next step is asking for feedback from the authors, refs #34923

diff --git src/hg/makeDb/trackDb/human/hg38/cCREsSuper.html src/hg/makeDb/trackDb/human/hg38/cCREsSuper.html
new file mode 100644
index 00000000000..2812a3bc4fa
--- /dev/null
+++ src/hg/makeDb/trackDb/human/hg38/cCREsSuper.html
@@ -0,0 +1,20 @@
+<H2>Description</H2>
+<p>
+This track contains cCREs (candidate Cis-Regulatory Elements) data from ENCODE3 and ENCODE4.
+Below is a short summary of each track.</p>
+<ul>
+<li><b>ENCODE4 cCREs</b>: ENCODE4 data containing the cCREs identified and classified from all
+ENCODE4 samples. The data were combined, so this track is a representation of all
+the underlying data in one track.</li>
+<li><b>ENCODE4 Core Collection</b>: ENCODE4 data containing additional subtracks of the 
+underlying signals used to create
+the ENCODE4 cCREs track above. The track also contains cCREs tracks that are sample-specific.</li>
+<li><b>ENCODE3 cCREs</b>: This track is similar to the ENCODE4 cCREs, but created from the ENCODE3
+data. ENCODE4 includes the ENCODE3 data, so ENCODE4 should be used whenever possible. This track
+exists for archival and reproducibility purposes.</li>
+</ul>
+
+<H2>Display conventions, data access, and credits</H2>
+<p>
+For information on track configuration, data description, data access, methods, and data provenance, 
+see the individual track description pages via their links above</p>