Mismatched Release Group Report

Tags: #<Tag:0x00007fe31716cf40> #<Tag:0x00007fe31716cd10>

TL;DR version: What causes a release group to be included in this report? Why do some individual release groups appear twice as if they need to be merged with themselves? Why do some individual RGs appear when there are no candidate groups with which to merge?

Discussion: I’ve been occasionally viewing this report to see if there are any releases that need to be merged. However, it’s confusing to me and I can’t find any specific documentation for it.

For example, the top two entries are for Ólafur Arnalds …and They Have Escaped the Weight of Darkness. It looks like a good candidate to merge, except they are both for the same group https://musicbrainz.org/release-group/aee639f8-876d-4fac-9c52-759d4efeeca9. There doesn’t seem to be a duplicate group to merge with this one.

Another issue is there are several release groups listed by themselves with no obvious merge candidates. For example, Agressiva 69 2,47 is listed but there are no other release groups by the same artist or with similar names listed near it in the report. As far as I can tell, the RG doesn’t have any relationship that would trigger its inclusion in this report.

1 Like

This is caused by a deprecated release relationship called “part of set”. If you look at the releases in the release groups that you mention, you’ll see a release relationship called “bonus disc” or “previous disc” (depending on the direction). Remove all of these relationships and the RG should be removed from the report. Many of the relationships that I have come across are however incorrect if you follow the current MB guidelines, so be careful before you start merging releases.

1 Like