Difference between revisions of "add Artist Alias Edit"

From MusicBrainz Wiki
Jump to navigationJump to search
m (2 revision(s))
Line 1: Line 1:
This edit adds an [[Artist Alias|ArtistAlias]] to an existing Artist [[Image:aicon.png]]
This edit adds an [[Artist Alias|ArtistAlias]] to an existing Artist [[Image:aicon.png]]
Line 41: Line 40:
Is [[Ticket:1162|1162]] still true? Please [[Answer Me|AnswerMe]]. -- [[User:dmppanda|dmppanda]] 03:22, 07 April 2007 (UTC)
Isn't the second [[Failed Prerequisite|FailedPrerequisite]] a [[Failed Dependency|FailedDependency]]? -- [[User:dmppanda|dmppanda]] 03:25, 07 April 2007 (UTC)
[[Category:To Be Reviewed]] [[Category:Edit Types]]
[[Category:To Be Reviewed]] [[Category:Edit Types]]

Revision as of 16:09, 21 March 2009

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

How to do it



  • 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 don't use MusicBrainz data anymore, and don't use ArtistAliases anyhow.
  • Use ArtistAliases sparingly. Adding too many (bogus) aliases will actually degrade the search quality and encourage misattribution.



At that time, ArtistAliases have to be unique (780).



  • None

Internal Errors

Symbolic name and id