I did read your OP. I just get bored of hearing “must be new to old” as that is a myth. I agree that is it usually the way, but not always. Better to take a quick check.
Hardest things I find to merge are VA releases. Often find myself double checking my edits after using Mass Merge and finding a couple of recordings that need to be flipped in direction due to more common use. Number of attached AcoustIDs is often a good hint. (Can’t remember which script it is that shows the AcoustIDs on the “current edits” page but that is REALLY handy for a quick check)
Certainly, but I have some grip on how to check for best & most detail. The oldest ID then is a good point of favour between 2 equally detailed duplicates, but somewhat eluding to the eye.
True but maybe all these good things were linked to an MBID that recently disappeared in favour of a brand new MBID (into which it is no longer good to merge, benefit of age is already lost).
It very often happens that people adds duplicates then merge existing into their duplicates.
It’s why older row ID is more sure about which MBID is actually older, not amount of data.
Exactly this. If a quick look you don’t see any difference, then oldest wins.
Now you are off on an odd edge case. Constantly flipping MBIDs would not be good. In that rare example it would not really matter which one was chosen.
Not sure if it’s due to the same issue as the one @chaban wrote on the topic of the MASS MERGE RECORDINGS script, but this one stopped working for me yesterday. Searching through recent merge edits of others (and not just recording mergers) it seems like this may not be just me.
Not sure whether it’s just me but it looks like this script stopped generating the ‘‘Merging into oldest [MBID]’’ text that goes at the bottom of each note for merger edits. At first I thought it might be just me having recently re-installed my browser and there might be some default setting that I forgot changing. I even tried using it with all other userscripts disabled but it didn’t change anything.
On the other hand, I also noticed that no merging edits have been entered with this autogenerated bit in the notes for the last few hours, so maybe there’s some general issue instead.
Same here, it stopped writing this note already long ago, didn’t bother to make noise about it til now.
So today it’s Ubuntu 20.04.6 LTS, Brave v1.56.11, Tampermonkey 4.19.0; tried also Chrome 115.0.5790.110 & Firefox 115.0.2, both with Violentmonkey 2.15 and only “mb. MERGE HELPOR 2” 2023.5.17 enabled. Similar story on Win10 which I rarely use. ¯\_(ツ)_/¯
Does the userscript work when you are still on merge page, before submitting (showing info and pre-selecting oldest MBID)?
Is it only an edit note problem?