Difference between revisions of "Merge Rather Than Delete"

From MusicBrainz Wiki
m (1 revision(s))
m (Merge Rather than Delete Duplicate Releases)
Line 1: Line 1:
=Merge Rather than Delete Duplicate Releases=
+
==Merge Rather than Delete Duplicate Releases==
  
 
It's usually best to enter [[Merge Releases Edit|MergeReleasesEdit]]<code><nowiki></nowiki></code>s to deal with [[Duplicate Release|DuplicateRelease]]<code><nowiki></nowiki></code>s instead of entering [[Remove Release Edit|RemoveReleaseEdit]]<code><nowiki></nowiki></code>s.  
 
It's usually best to enter [[Merge Releases Edit|MergeReleasesEdit]]<code><nowiki></nowiki></code>s to deal with [[Duplicate Release|DuplicateRelease]]<code><nowiki></nowiki></code>s instead of entering [[Remove Release Edit|RemoveReleaseEdit]]<code><nowiki></nowiki></code>s.  

Revision as of 06:41, 17 April 2009

Merge Rather than Delete Duplicate Releases

It's usually best to enter MergeReleasesEdits to deal with DuplicateReleases instead of entering RemoveReleaseEdits.

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

This MergeRatherThanDelete guideline also applies to artists, but since a RemoveArtistEdit is not possible for an artist with any releases, relationships, tracks or NonAlbumTracks it is more of a system-enforced rule than a guideline. An analogous guideline is to MergeMisspelledArtists.

However, pay close attention to DeleteRatherThanMerge when dealing with the common "feat artist" problem.

  • And which problem would that be? --Keschte