Merge Rather Than Delete: Difference between revisions
From MusicBrainz Wiki
Jump to navigationJump to search
Line 1: | Line 1: | ||
⚫ | |||
==Merge Rather than Delete Duplicate Releases== |
|||
⚫ | |||
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| |
* The [[MusicBrainz Identifier|MusicBrainz Identifiers]] 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|MusicBrainz Identifiers]] will forward to the new item. |
||
* Even if there's no useful data ([[Disc ID| |
* Even if there's no useful data ([[Disc ID|DiscIDs]], [[PUID|PUIDs]], [[Release Event|Release Events]]) attached to the release, it's possible that someone may enter a [[Add PUIDs Edit|AddPUIDsEdit]], [[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. |
||
This MergeRatherThanDelete guideline also applies to artists, but since a [[Remove Artist Edit|RemoveArtistEdit]] is not possible for an artist with any releases, relationships, tracks or [[Non-Album Tracks|NonAlbumTracks]] it is more of a system-enforced rule than a guideline. An analogous guideline is to [[Merge Misspelled Artists|MergeMisspelledArtists]]. |
This MergeRatherThanDelete guideline also applies to artists, but since a [[Remove Artist Edit|RemoveArtistEdit]] is not possible for an artist with any releases, relationships, tracks or [[Non-Album Tracks|NonAlbumTracks]] it is more of a system-enforced rule than a guideline. An analogous guideline is to [[Merge Misspelled Artists|MergeMisspelledArtists]]. |
||
⚫ | |||
However, pay close attention to [[Delete Rather Than Merge|DeleteRatherThanMerge]] when dealing with the common "feat artist" problem. |
|||
<ul><li style="list-style-type:none">And which problem would that be? --[[User:Keschte|Keschte]] |
|||
</ul> |
|||
⚫ |
Revision as of 10:49, 27 July 2009
It's usually best to enter Merge Releases edits to deal with duplicate releases instead of entering Remove Release edits.
Deleting releases 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 item is deleted. When merging it, however, the old MusicBrainz Identifiers will forward to the new item.
- Even if there's no useful data (DiscIDs, PUIDs, Release Events) attached to the release, it's possible that someone may enter a AddPUIDsEdit, AddDiscIDEdit or EditReleaseEventsEdit before your RemoveReleaseEdit is approved. If so, the recently added data will be lost.
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.