How popularity works
Every tune in the book gets a popularity score from 1 to 10: how likely you are to hear it, or be able to play it, at a jam. The score comes from local session logs first and the wider internet second. Everything below is read live from the tune book's database, so each score can be checked against its evidence.
Loading…
The badges
Next to each score is a badge saying what the score rests on.
| local + online | Played at one of the local sessions (or on a curated local list) and popular online. The strongest evidence. |
| local | Played locally, but not found online in a way that counts. |
| online | Not played locally (yet); scored from The Session or published jam lists, plus hearsay research where there is some. |
| hearsay | Only hearsay research: forums, blogs, teachers' pages, videos, festival set lists. A judgment call, with sources. |
| no data | Looked for and found nowhere (camp compositions, family tunes, very obscure settings). No score. |
Where the evidence comes from
Loading…
The calculation
Loading…
Every tune
Tap a tune to see its evidence. Each score is recomputed in your browser from the evidence shown, using the same code the server uses; any disagreement is flagged.
Changes over time
A line is written whenever a tune's score or badge changes, with the reason for the update.
- Loading…
Keeping it current
Evidence is gathered by a script (data/popularity/evidence_pipeline.js in the repo) that reads the session spreadsheets, The Session's public data dump and the jam-list panel, merges in the hearsay research, and posts everything to the tune book. The server then recomputes every score with /fiddle/popularity.js, the same file this page uses.
Every new tune gets popularity evidence when it's researched. Tunes that aren't on any local list or online source get hearsay research rather than a guess.