computer.localnetwork.directory.getCharts
The tracks and artists the directory's DJs supported most in sets played in a time and place, counted the way 1001Tracklists counts its Top 101 Producers: a DJ (a project, however many accounts manage it) supports a track once however often they play it, a track charts once 3 DJs support it, and an artist gets at most 5 supports from one DJ, counting only tracks that chart. Also lists every city there are sets from.
Details · query
| Kind | query |
|---|---|
| Authority | directory.localnetwork.computer |
| Commit rev | 3n2kaczwtw42k |
| Indexed |
Query
query · GETParameters
query stringbefore
stringThe day after the last one counted, as YYYY-MM-DD. Without it, every set from `since` on.
minLength: 10maxLength: 10
city
stringOnly sets played in this city (the set's location.locality, any case). Needs country.
maxLength: 200
country
stringThe city's country, as an ISO 3166-1 alpha-2 code.
minLength: 2maxLength: 2
limit
integerThe most tracks, and the most artists.
minimum: 1maximum: 100default: 50
since
stringThe first day counted, as YYYY-MM-DD. Without it, every set before `before`.
minLength: 10maxLength: 10
Output
application/jsonMost supported first.
Cities with sets, by how many, whatever the other params say.
Most supported first, then most recently played.
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
Which of the directory's DJs played an artist's tracks, and where: each track that appears in their sets, most supported first, with every play, newest first (at most 1,000 plays). Asked for by mbid or by name. The output has no artist when no set credits them.
-
Find artists the directory's DJs played, most supported first, with their supports over every set (no track minimum).
-
Get top tracks