Merge: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
(Created page with "==Definition== Merging is an edit that ''merges'' two (or more) MusicBrainz entities (of the same type) into one. This is the correct way to re...")
 
(add categories, fix formatting)
 
(2 intermediate revisions by one other user not shown)
Line 3: Line 3:


Merging is considered a [[Destructive_Edit]], because some data can be lost.
Merging is considered a [[Destructive_Edit]], because some data can be lost.



==What Happens?==
==What Happens?==
Line 13: Line 12:


==Further Reading==
==Further Reading==
*[[Merge Rather Than Delete]]
[[Merge_Rather_Than_Delete]]
*[[How to Merge Recordings]]
[[How_to_Merge_Releases]]
**Using [[Guides/AcoustID|AcoustIDs]] as evidence when merging recordings
[[How_to_Split_Artists]]
*[[How to Merge Releases]]
*[[How to Split Artists]]

[[Category:Editing]] [[Category:Terminology]] [[Category:To Be Reviewed]]

Latest revision as of 20:37, 16 April 2020

Definition

Merging is an edit that merges two (or more) MusicBrainz entities (of the same type) into one. This is the correct way to resolve duplicate entries.

Merging is considered a Destructive_Edit, because some data can be lost.

What Happens?

When merging multiple entities, one of them will always be designated the "target". If any fields have conflicting data (e.g. duplicate artists with different Areas), the data from the "target" will be kept.

For artists, you will be given an option, "Update matching artist and relationship credits to use the new artist’s name". If you select this option, all instances of the artist's name will be changed to the "target" name. If you don't choose this option, the alternate name(s) will be retained as artist credits.

The end result is that all references to the merged entities will now be redirected to the "target" entity.

Further Reading