I’m the author of a C# MusicBrainz library and recently found that a test was failing, that was working well before. Of course this can always happen, since the server data might have changed, but investigating this case, I found something strange.
Is there any way to get the second (correct) recording using the MusicBrainz search? Why isn’t it included in the search results (it clearly matches the query)?
The duplicate recording should probably not have been created. Any idea why this happened (maybe some problem with the Discogs import script)?
Thanks, this answers all my questions. I will take a look at the merge procedure…
I guess MusicBrainz gives a hint, when you try to add an item that already exists? Maybe it should insist on double-checking before the user actually saves a new (probably duplicate) version
I fear such a hint for recordings would be interpreted by many as “please use the existing recording”, even though they should only do this when they are really sure it is the same recording. But if in doubt it is safer to add a new recording. It’s easier to merge later than to split again.
I’m asking, because I try to understand how easy/hard it is to create duplicates. I think we agree, that it should be hard, so some kind of warning should be displayed in such a case.
Yes, if you add a release it does suggest using the existing track lists of similar releases. If the editor would have done that it would have reused the existing recordings.