|
This Page has been suggested for deletion |
|
Several reasons may lead to a page being suggested for deletion, the most common being: 1. the content of the page is not appropriate, or just irrelevant to MusicBrainz, 2. the page duplicates (or has been entirely superseded) by another one, 3. the page no longer has a purpose (possibly following the introduction of a new server feature) or is entirely bit-rotted while not being of interest enough to be kept as History |
|
Pages marked as deleted won't usually be deleted immediately though, so, if you think the page either should be preserved as History or still serves a purpose and should just be kept, you may discuss this with the editor who marked it as such in order to expose your reasons and reach an agreement. |
|
If you're a newcomer who just stumbled here, chances are high that this page is not relevant for you either way, and you may rather head for the main documentation. |
This page is entirely superseded by SameArtistWithDifferentNames. Need to check if anything in there needs to be fished and archived/moved elsewhere. DeletedPage otherwise. -- dmppanda 2008-03-10 02:32:34
StyleGuidelines for handling performance names
This page describes guidelines that should be kept in mind when adding a PerformanceName for an artist, or when adding data or AdvancedRelationships to artists who have multiple entries in the database.
Only add Performance Names for individuals, not for bands
Guideline
Performance names should not be used for bands - if a band changes their name, it's considered to be a new band, and the relationship between them is indicated by their common membership (MemberOfBandRelationshipType). If a band goes under several different names simultaneously, one name should be chosen to be the primary name and the others should be aliases.
Justification
This is to ensure that people know which artist a relationship should use, and that they don't have to duplicate relationships. With a person, the general rule is that when in doubt, relationships should use the LegalName. However, there is no LegalName for bands. This means there will always be confusion about which name is the right one to relate to, and so there will be duplication of data.
Examples
The Jacksons is another name for
The Jackson 5. A mixture of the two is used to record their various albums. There is currently (2005-06-02) a PerformanceNameRelationshipType between the two. If this situation remains, then either the full membership list, URL list, and other relationships will have to be duplicated, or we'll have to standardise on relating to just one, in which case they'll end up being duplicated by newbies anyway. Instead, we should probably merge the two artists, with "The Jacksons" becoming an alias of "The Jackson 5". This will have the unfortunate side-effect of obliterating information about which albums were credited as "The Jacksons" and which as "The Jackson 5".
Performance Names link only to Legal Names
Guideline
PerformanceNames should only ever be linked to LegalNames, not to other PerformanceNames.
Justification
See DontMakeRelationshipClusters.
Examples
Richard David James performs as
Aphex Twin,
Polygon Window,
The Dice Man,
Bradley Strider,
GAK,
AFX,
Caustic Window,
Power-Pill,
Q-Chastic,
Soit-P.P., and
Blue Calx. To record performance name relationships between all 12 of these names would require 78 relationships, instead of the 11 required with the above rule.
CategoryStyle CategoryProposedStyle







