Merge: Difference between revisions
(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...") |
m (listifying "further reading") |
||
| Line 13: | Line 13: | ||
==Further Reading== |
==Further Reading== |
||
[[Merge_Rather_Than_Delete]] |
*[[Merge_Rather_Than_Delete]] |
||
[[How_to_Merge_Releases]] |
*[[How_to_Merge_Releases]] |
||
[[How_to_Split_Artists]] |
*[[How_to_Split_Artists]] |
||
Revision as of 18:16, 26 November 2015
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.
