Alternate CD matrix/runout inscriptions: enough for a new release?

[mfmeulenbelt]

I think Discogs’ approach is very sensible. And while having more releases doesn’t degrade the data quality, it could add confusion, especially because MB’s interface isn’t very good at displaying lots of information in a way that makes differences clear. So I’m not really in favour of having a different release for every matrix number or run-out code. I am of course, very much in favour of the “if in doubt make a different entity because merging later is easier than untangling” rule of thumb.

Here’s a little draft of what an updated guideline or FAQ could be like:

When should I create a new release?
Generally, a new release should be added if any information stored in our database differs between the version you want to add and a release already in MusicBrainz.

Reasons for adding a new release are:

• The release has a different track list.
• One of the relationships differs between the release in MusicBrainz and the one you consider adding.
• The release you consider adding has different artwork. This only applies to differences resulting from concious decisions made before or during manufacturing. Damage or degradations are not reasons for creating a new release.
• If you think the release you have might be different, but you are not sure, you can create a new release. Simply because it is easier to merge two releases than it is to untangle them later. Please make a note in the release annotation to explain your decision, because that information may prove useful to other editors.

Reasons for not adding a new release are:

• The release has a different matrix number. Matrix numbers are a result of the manufacturing process and not artistic decisions that MusicBrainz cares about. But feel free to add them to the annotation and to upload cover art displaying the matrix number.