Skip to content
English
Get Help
  • There are no suggestions because the search field is empty.

Building a Sort Rule

  1. Build a Sort Rule
  2. Most Frequently (What Does It Do?)
  3. Folder Columns
  4. Count/Percent Column
  5. Plain Ordering
  6. Attaching and Related Knobs

Build a Sort Rule

Give it a Name, then add columns one at a time: pick the column in Add column, pick its Sort order — Ascending, Descending, Most Frequent, or Least Frequent — and click Add.

Drag rows to set priority — the top row is the first sort key. Each row
carries three checkboxes:

  • Folder — split into sub-folders at this column.

  • Count / Pct — group bands in the grid showing the count and/or percentage.

Folder and Count/Pct are either/or per column — checking one side unchecks the
other. And folder columns must come before any Count/Pct column; if they
don't, the editor tells you when you save: "Count / Pct columns must come
after all Folder columns."

Commit with Add Sort Rule (or Update Sort Rule). Back in the catalog,
each row summarizes itself — "DN (Asc), DIST (Asc)" — and a folder rule that
attaches one shows "· Sort: {name}" in its own row. Deleting from the catalog
asks first: "Delete this sort rule? This can't be undone."

Most Frequently (What Does It Do?)

Most Frequent is the tendency finder: the biggest bucket floats to the top. Sort Personnel most-frequent and your opponent's "11" snaps arrive first — all of them, together — then every "12" snap, and so on down to the one-off looks at the bottom.

It works level by level. Inside the "11" block, the next column's most-frequent re-ranks just those plays — so the most common formation out of "11" comes first within that block. Groups always stay intact; it never interleaves an "11" play among the "12"s to satisfy a lower sort key.

Two details it quietly gets right: numbers sort as numbers (2 comes before 14, not after "13"), and ties fall back to alphabetical so the order is always predictable.

Folder Columns (Splitting into Sub-Folders)

Each Folder column becomes a folder level under the playlist, named "{Column}: {value}" — "Down: 3", and inside it "Distance: Long". The folders themselves order by the column's own sort order, so under Most Frequent the biggest folder lands on top.

Columns after the last Folder column don't create more folders — they order the plays inside each leaf.

One exception to know: ad-hoc playlists never split (ch. 11). The sort still orders their grid, but the playlist stays one piece so you always have a single place to curate.

Count/Percent Column

Wherever the group value changes, a tinted band row appears in the grid:

> PLAY TYPE: Pass (3/12 - 25.0%)


Count, percentage, or both — per your checkboxes. Blank values read "(Empty)", and multiple group columns join on one band.

What the percentage means — worth thirty seconds, because it's built to answer the question a coach would actually ask:

  • At the **top level**, it's a share of the whole playlist: "Pass (3/12 -  25.0%)" means 3 of this playlist's 12 plays.

  • At **nested levels**, it's a share *within the parent band*: of the 3rd-down plays in the band above, 60% were Pass. Each level answers "of the group I'm looking at, how much is this?"

  • One special case: on a Wildcard rule grouped by *the same column it split on*, the top-level percentage is measured against **all the plays that fed the rule** — so the "EVEN" front playlist reads "EVEN (36/146 - 24.7%)", its true share of the film, instead of a useless 100%.

Plain Ordering

No checkboxes at all? Then the rule simply orders every attached playlist's plays — no folders, no bands. That's the everyday case: a default film order like Down, then Distance, applied to every playlist that attaches it.

Attaching and Related Knobs

Attach a sort rule via the folder rule's Sort Rule picker in the rule editor — " none)" by default, with a ☰ button that manages the sort-rule catalog right in place. Ad-Hoc rules attach per playlist instead.

Don't confuse sort rules with the definition's Sort Prefix checkbox — that renumbers folder names ("01 - ", "02 - ") so their order survives after upload; sort rules order the plays and structure inside.

And a tip before you build: audition an ordering with the grid's column menu first — it's the same engine, applied on the fly and never saved. When the view looks right, bake it into a sort rule here.