The original post: /r/datahoarder by /u/nbtm_sh on 2025-06-24 16:20:41.
Unsure if this is the best place to ask, but I’m trying to organise DJ sets in a way that makes most sense and is searchable (especially for external users on platforms like Soulseek). My current music library is structured like this:
Label-Publisher/Album Artist/Album/Track
I’m a little bit unsure what fields to put for DJ sets, and how would you handle concerts with many sets. The structure I’ve come up with is this:
Label-Publisher = Event Organiser
Album Artist = DJ / Producer
Album = Event / Concert (Date)
Track = DJ Set name + queue file for set tracks
But this kinda falls apart if I wanna listen to all DJ sets at a particular concert, as they’re all different albums. If it’s organised like that, and we take an example, it goes like this: HARDCORE TANO*C/DJ Myosuke/DJ Myosuke Live @ TANO*C TOUR 2025 (Tokyo 2025-06-22)/Set.ext
This fits cleanly into the music organisation, but obviously makes it very hard to search for these things. I could put each set at a concert into its own album, but then having each track of each set be seperate would get very messy. If someone was looking to download all the sets from a concert, it would be hard as they’re all under the artist, not organised by the concert. Of course, this all falls apart when there is no concert, and it’s just a DJ set/mix someone published online. And I want all of this to present nicely in music player software, too.
I’m really struggling to find a good balance here. Has anyone done this before that can give some pointers?