Currently you can load the sets archive (the_session.load_meta('sets')), where each row is a tune in a set (currently 218_867 rows). And from this you could discover a user's sets and load specific sets. But you can also load a set or discover a user's sets with the API, which should be faster, and always up-to-date, whereas the archive does lag a bit. The API approach also lets you use tags, a new-ish feature (the tune and set archives don't include tags currently).
I have some initial code for this in trad-setlist-helper but would prefer it live here.
For posterity, sets was a new feature in 2016.
Currently you can load the sets archive (
the_session.load_meta('sets')), where each row is a tune in a set (currently 218_867 rows). And from this you could discover a user's sets and load specific sets. But you can also load a set or discover a user's sets with the API, which should be faster, and always up-to-date, whereas the archive does lag a bit. The API approach also lets you use tags, a new-ish feature (the tune and set archives don't include tags currently).I have some initial code for this in trad-setlist-helper but would prefer it live here.
For posterity, sets was a new feature in 2016.