Expanding my music pipeline

I've written at length about my scrobbling implementation on my site. Until now I'd managed the metadata for my music manually, editing it on macOS before adding it to Navidrome. That gave me direct control, ate time and came with quite a bit of tedium. I'd seen beets mentioned a few times as a tool to programmatically manage and apply metadata. I've wanted to use it, but cutting over a collection with nearly 800 artists and over 5,000 albums was a lot. But, as with most bad ideas I have, this one stuck with me. One habit I'd gotten into while managing music was to assign splits to a single artist. If I had both artists in my collection, I'd split them into two albums, one for each artist. For collaborative albums I'd have either a unique artist for the collaboration or (incorrectly) assign it to whichever artist I preferred. Fixing this meant, for starters, a database migration. My schema supported only a 1:1 relationship between artists and albums. Now an album like When No Birds…