Separating releases based on relationships inferred from matrix codes

[ernstlx]

@blackteadarkmatter

When I look into the edit history of messy release groups, it’s often clear many people are just trying to import Discogs releases into MB

And when I work on it, it becomes this exact release. I can’t verify disc IDs (if it’s not mine), but I look on other information, if there is something, and if pictures are attached, I try to find the correct Discogs release, if there’s also a disc ID I ask the editor who submitted it if their release matches the images, and so on…
If there’s a disc ID (attached by a different editor) and no further information, only the link, I also try to get answers, but I would make it the linked version and would risk having a false disc ID. Most often, there are already a lot of them anyway.

@blackteadarkmatter

To use any information, you need to verify it, by comparing the scans (if you can make out anything) and possibly matrix code.

Exactly! But not “possibly” matrix codes. Matrix codes are the key part of my research. The code (written by LBR, not the “stamped” codes from duplication) has exactly one corresponding disc ID, whatever is printed on the disc or the cover.

@blackteadarkmatter

we can’t just assume all links are accurate, and all information correct.

Never. All we can do is try our best to sort out the mess. That’s sometimes tiresome…