Nice work Brian.
For me, this is why MC is so good. JRiver do not say "Here's a duplicates view for you to use" They say "Here are the tools for you to create your own views"
The attached is how I do mine.
It's playlist based rather than library field based. I use the four panes to the right of "Status" to see how much of an album I've actually 'hidden', should I be curious about that. I added them there as I'm only ever curious when I'm working on dupes and thought it better to have the info in the same view rather than switching away to another.
The "Possible Duplicates" returns only files that I have not worked on, basically, excludes those on the 'hidden' or 'allowed' playlists, then checks what's left for duplicates. I just go in and clear that up every few months or so.
Select file(s) and tick against the desired playlist to add those files.
After, whenever building a smartlist or view where I don't want those marked as dupes to be played, adding the custom rule "-p=hidden" takes care of that.
"Allowed" is used for live recordings, accoustic versions and the like, where either or will do, and so allows the "Possible Duplicates" entry to work as desired, namely, listing any new duplicates that have arrived since the last time I cleared them up.
I could probably do this just as well using list placed, inline check box library fields, but they didn't exist when I set this up, and as it wasn't broken, and there's no real difference in either approach, I just kept what I had.
My head couldn't cope with the "Not Duplicate" that way around
I would have to reverse that so the ticks were against the files I considered duplicates. Always fascinates me how we are all wired slightly differently like that...