Merge Rather Than Delete: Difference between revisions
From MusicBrainz Wiki
Jump to navigationJump to search
((Imported from MoinMoin)) |
(#912 is already implemented (Imported from MoinMoin)) |
||
| (12 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=Merge Rather than Delete Duplicate |
=Merge Rather than Delete Duplicate Releases= |
||
It's usually best to [[Merge |
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. |
||
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. |
|||
| ⚫ | * 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. |
||
| ⚫ | This MergeRatherThanDelete guideline also applies to artists, but since a [[Remove Artist Edit|RemoveArtistEdit]] is not possible for an artist with any releases, 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> |
|||
| ⚫ | This MergeRatherThanDelete guideline also applies to artists, but since [[Remove Artist| |
||
[[Category:To Be Reviewed]] [[Category:Editing]] [[Category:Style]] |
[[Category:To Be Reviewed]] [[Category:Editing]] [[Category:Style]] |
||
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:
- The MusicBrainzIdentifier
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 MusicBrainzIdentifiers will forward to the new item. - Even if there's no useful data (DiscIDs, TRMs, ReleaseEvent
s) attached to the release, it's possible that someone may enter a AddTRMsEdit, 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, 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
