add Artist Alias Edit: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
m (→‎Editing: Just didn't sound correct the way it was worded. Primitive.)
(No longer need to be unique)
Line 22: Line 22:
==Notes==
==Notes==


At that time, [[Artist Alias|ArtistAlias]]<code><nowiki></nowiki></code>es have to be unique ([[Ticket:780|780]]).


===Prerequisites===
===Prerequisites===


* An AddArtistAliasEdit will fail due to a [[Failed Prerequisite|FailedPrerequisite]] if that alias already exists (be it attached to the same artist or to another one).
* An AddArtistAliasEdit will fail due to a [[Failed Prerequisite|FailedPrerequisite]] if the artist is deleted by a [[Remove Artist Edit|RemoveArtistEdit]].
* An AddArtistAliasEdit will fail due to a [[Failed Prerequisite|FailedPrerequisite]] if the artist is deleted by a [[Remove Artist Edit|RemoveArtistEdit]].



Revision as of 20:14, 3 October 2011

This edit adds an ArtistAlias to an existing Artist aicon.png

How to do it

Guidelines

Editing

  • Aliases are useful to enhance search results; there are a number of legit reasons to create a new alias: misspellings, variants, numbers... Be sure to read ArtistAlias for a complete list.
  • Thanks to the Lucene search engine that MusicBrainz uses, there is no longer a need for aliases containing unaccented characters
  • ArtistAlias in MusicBrainz are not the same as in Discogs: an alias here is nothing more than a search hint, not a way to collect different names used by an artist in different circumstances (use a PerformanceName in that case).
  • There is no reason to add an ArtistSortName as an alias.
  • Adding aliases won't help LastFm! They no longer use MusicBrainz as a source for their data, and never used ArtistAliases anyway.
  • Use ArtistAliases sparingly. Adding too many (bogus) aliases will actually degrade the search quality and encourage misattribution.

Voting

Notes

Prerequisites

Dependencies

  • None

Internal Errors

Symbolic name and id

MOD_ADD_ARTISTALIAS (15)