You mean like the people/roles such as mentioned here? : https://musicbrainz.org/release/e9fd5395-94a3-4c0c-8c7e-edb8e131cdfa
I went to the Guidelines and only found "Special Purpose Artist." Maybe I should have looked up an album. This looks like it will work a treat.
I would urge you to download and install Picard and try it on a few albums rather than picking through the MusicBrainz website for data. Like I said, you don't ultimately have to tag the files with the data it retrieves, but you can see your old data side by side with its proposed changes and compare the two for anything missing.
Point taken, and I will be doing this.
If your stuff is already tagged I wouldn't recommend retagging it with MBrainz. The data isn't that radically different or earth-shatteringly better. But going forward, especially in the interest of abandoning MediaMonkey and its plug-in if that's your intent, it's something to look at.
Quite the contrary. I looked at "The Girl is Mine" to compare to my tags. All I have is "Co-Producer," "Mixed By," and "Vocals" for Involved people. My tagging completeness fetish keeps getting me into so much trouble.
To complement frankz good info and tips: Just for the purpose of your original issue, you could setup Picard to only write the releasegroup tags. Just be warned that Picards learning curve is a bit steep (or long, or erratic, what should you call it) to accomplish such refinement, and you will need some scripting for it.
This is definitely a solution to my original query. It works, and I can shoe-horn it into my workflow.
I fear no learning curve. (Except the ones that can result in death or dismemberment if you fail.)
I would still rather find a way to use my Auto-Playlist for this. My desire is to have a folder of Auto-Playlists that I can cycle through to check for issues that have happened when I import files (If everything is good, they should be empty.)
To get a bit "meta," and explain my thought process; I am a Database / Network Administrator. I have a couple of databases that pull from an external flat file. Since I have no control over the input, I have no way of knowing if there was a dropped comma, or if the source has changed their field order, or name. To combat this, I have fields that will only accept the type of data I expect. If something like the above happens, the import will fail, and I will know to look at the incoming file. My data integrity is preserved.
I don't see any way to maintain my data integrity using MusicBee/MediaMonkey, or MusicBee/MusicBrainz. Since I can't check the input, I need to check the output. Auto-Playlists give me the ability to target the issues I've had in the past, so that I can at least check for those in the future. If I can get a couple more concepts down with the Auto-Playlist, I can find other things to look for as well.
As long as I'm on this, I also want to avoid application lock-in. My end goal is to be able to drop my file structure into any media manager, and have all of the information available. It looks like MusicBrainz is going to help me to this end.
TL;DR; I'm concerned about data integrity, and want a way to verify that the incoming tags are at least reasonable. Auto-playlists are my perfect solution. Ya'll suck, because now you've convinced me to dive down the MusicBrainz/Picard rabbit hole.
