Music Archive metadata management

Created by: Lester Caine, Last modification: 25 January 2026

While trying to sort material in the Music app on Nextcloud I was pushed back down a path that the old grey cells had neatly switched off.  Processing a disk on MusicBrainz

NOW I remember why I stopped editing on MusicBrainz ... It's so cumbersome especially when the physical disks one has don't have anything to work from. I've been playing with the 20 disks of the '30 Years of Pop' collection of which only a few appear in Discogs and even less in MusicBrainz. At least I have the original disk set, but working through them is going to take some time. Step one has been to install Tampermonkey into Firefox so I can run a UserScript to import Discogs records into MusicBrainz. Something I don't think exsisted last time. But I still need to manually process a lot of things like linking each artist to their corrrect ID and on a couple of disks, the existing running times did not actually match the media. And it does help if you clone between the correct machine before trying to rescan on that machine. Now the lastest metadata is on the nextcloud library as well as in plex on the media server. Just been strugging with the one disk I did not link from discogs but should have and I now have two id's for the one disk.

Picard has provided a better base for the naming convention, but still falls over when there are multiple releases of an album. THAT is one reason for having a date in the album title, especially when MusicBrainz has the same album name for dozens of releases with different track details.
Music maintains the basic folder structure, so starting with an artist folder, one can then add a level to separate material which may be another way to separate new releases from the originals. Such sub-folders as studio, live, compilation, remix, singles and the like make sense for artists that have an extensive catalogue, while for smaller artists with only perhaps a dozen recordings this is probably overkill. When an release consists of multiple items, sub folders for each disk can be useful, but the Picard convention of Disk-Track before the track title seems a little tidier when all of the other data is contained in the metadata. CD1 and CD2 in the Music Display Tree just make things more cumbersome.

Have a working crib sheet now to tidy the original files (TODO). Then after cloning to the nextcloud server data folder I need to run files:scan --path='->Music', music:scan music:cleanup and I'm getting the updated metadata.