Difference between revisions of "Merge Rather Than Delete"

From MusicBrainz Wiki
(remove [""] around CamelCase links (Imported from MoinMoin))
(#912 is already implemented (Imported from MoinMoin))
Line 4: Line 4:
  
 
Deleting releases has two kinds of bad effects on the database:  
 
Deleting releases has two kinds of bad effects on the database:  
* The [[MusicBrainz Identifier|MusicBrainzIdentifier]]<code><nowiki></nowiki></code>s that have been referenced anywhere (tagged files, links to [[MusicBrainz]] from other sites) will become invalid when the item is deleted. When merging it, however, the old [[MusicBrainz Identifier|MusicBrainzIdentifier]]<code><nowiki></nowiki></code>s will forward to the new item. '''Note:''' Not yet implemented, see ticket [[Ticket:912|912]]
+
* The [[MusicBrainz Identifier|MusicBrainzIdentifier]]<code><nowiki></nowiki></code>s that have been referenced anywhere (tagged files, links to [[MusicBrainz]] from other sites) will become invalid when the item is deleted. When merging it, however, the old [[MusicBrainz Identifier|MusicBrainzIdentifier]]<code><nowiki></nowiki></code>s will forward to the new item.  
 
* Even if there's no useful data ([[Disc ID|DiscID]]s, [[TRM]]s, [[Release Event|ReleaseEvent]]<code><nowiki></nowiki></code>s) attached to the release, it's possible that someone may enter a [[Add TR Ms Edit|AddTRMsEdit]], [[Add Disc ID Edit|AddDiscIDEdit]] or [[Edit Release Events Edit|EditReleaseEventsEdit]] before your [[Remove Release Edit|RemoveReleaseEdit]] is approved. If so, the recently added data will be lost.  
 
* Even if there's no useful data ([[Disc ID|DiscID]]s, [[TRM]]s, [[Release Event|ReleaseEvent]]<code><nowiki></nowiki></code>s) attached to the release, it's possible that someone may enter a [[Add TR Ms Edit|AddTRMsEdit]], [[Add Disc ID Edit|AddDiscIDEdit]] or [[Edit Release Events Edit|EditReleaseEventsEdit]] before your [[Remove Release Edit|RemoveReleaseEdit]] is approved. If so, the recently added data will be lost.  
  

Revision as of 22:27, 5 April 2007

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, 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