Difference between revisions of "Merge Rather Than Delete"

From MusicBrainz Wiki
Line 5: Line 5:
 
* Even if there's no useful data attached to the entity when you enter the edit, it's possible that someone may enter it before your removal is approved. If so, the recently added data will be lost.
 
* Even if there's no useful data attached to the entity when you enter the edit, it's possible that someone may enter it before your removal is approved. If so, the recently added data will be lost.
 
   
 
   
 +
For similar reasons, it is better to merge misspelled [[Artist|artists]] into their correct names, instead of just moving their releases and/or recordings to the right artist. This also adds the misspelled version as an [[Artist Alias|alias]] for the artist, which makes more unlikely that the wrong name will be recreated.
  
 
[[Category:Editing]]
 
[[Category:Editing]]

Revision as of 17:45, 29 September 2011

It's usually best to merge duplicate entities (releases, release groups, recordings, etc.) instead of deleting them.

Deleting entities has two kinds of bad effects on the database:

  • The MusicBrainz identifiers that have been referenced anywhere (tagged files, links to MusicBrainz from other sites) will become invalid when the entity is deleted. When merging it, however, the old identifiers will forward to the entity it is merged into.
  • Even if there's no useful data attached to the entity when you enter the edit, it's possible that someone may enter it before your removal is approved. If so, the recently added data will be lost.

For similar reasons, it is better to merge misspelled artists into their correct names, instead of just moving their releases and/or recordings to the right artist. This also adds the misspelled version as an alias for the artist, which makes more unlikely that the wrong name will be recreated.