Nice approach. I'm the developer of https://www.blisshq.com/ and other projects. The key insight there is that managing large collections is easier with rules applied continuously, rather than thoughts-in-the-moment "I'll run a batch command with a tagger".
You could have the rules encoded in your config (or the DB) and apply those. For example, someone may want a "portable mirror" of their gold library, but that means transcoding AND chopping the embedded album art to size (or maybe their player has max resolutions).
I guess having the DB means you could potentially version control the metadata changes?
You could have the rules encoded in your config (or the DB) and apply those. For example, someone may want a "portable mirror" of their gold library, but that means transcoding AND chopping the embedded album art to size (or maybe their player has max resolutions).
I guess having the DB means you could potentially version control the metadata changes?