ca4b6d0d29c6d29b43df588a4635b556acc84f7f lrnassar Fri Jul 31 16:59:51 2026 -0700 Fix maxCheckboxes spelling in trackDb docs, which listed it as maxCheckBoxes. Setting names are case sensitive and the browser reads the lowercase form, so hubs copying the documented spelling silently got the default. Also adds level-new tags to the faceted composite settings metaDataUrl, primaryKey, maxCheckboxes and dataTypes so hubCheck -checkSettings recognizes them instead of reporting them as unknown. refs #37965 diff --git src/hg/htdocs/goldenPath/help/trackDb/trackDbLibrary.shtml src/hg/htdocs/goldenPath/help/trackDb/trackDbLibrary.shtml index 39585a62e0f..0abbf4c22fe 100644 --- src/hg/htdocs/goldenPath/help/trackDb/trackDbLibrary.shtml +++ src/hg/htdocs/goldenPath/help/trackDb/trackDbLibrary.shtml @@ -6921,32 +6921,32 @@ DRX118407 CellLine iPSC DRX118408 CellLine iMeLC </pre> </p> </div> <DIV class="primaryKey"><span class="types faceted composite"></span> <div class="format"><code>primaryKey <field></code></div> <p> This setting is required and works in tandem with the file specified in the metaDataUrl setting. The named field will be used as a primary key for the metadata table, and those values will be used to identify subtracks. </p> </div> -<DIV class="maxCheckBoxes"><span class="types faceted composite"></span> -<div class="format"><code>maxCheckBoxes <integer></code></div> +<DIV class="maxCheckboxes"><span class="types faceted composite"></span> +<div class="format"><code>maxCheckboxes <integer></code></div> <p> Frequently a facet may have a long list of possible values - too many to display at once in the track selection interface. This setting limits the number of facet values displayed on the left to the N most common, where N is the value of this setting. The default value is 20. </p> </div> <DIV class="dataTypes"><span class="types faceted composite"></span> <div class="format"><code>dataTypes <name1(|"table title") name2(|"table title") ...></code></div> <p> This optional setting identifies a list of datatypes available for each sample in the metadata file (one sample per row). Each datatype is identified by a name, which is combined with the name of the parent track and a primary key to form track names as described above. Spaces cannot be used in data type names; instead, spaces separate the various data types. If present,