An editor should use the name per the standard rules and guidelines; however, the best practice would be to anticipate name derivatives for the search function and use hidden alias fields:a) VV Contributor
b) V. V. Contributor
c) Virile & The Vagabonds
I'm not supporting creating artist aliases by anticipation, and certainly not creating data for search objectives.
An editor should use the name per the standard rules and guidelines; however, the best practice would be to anticipate name derivatives for the search function and use hidden alias fields:a) VV Contributor
b) V. V. Contributor
c) Virile & The Vagabonds
I'm not supporting creating artist aliases by anticipation, and certainly not creating data for search objectives.
Then I share JC's concerns re: your low interest in the user experience and functionality....
(I did say "hidden alias fields", and I'm certainly not suggesting anticipating spelling errors.)
Hmm... Got curious and tried some common aliases:
CCR returns Creedence Clearwater Revival
I see no performances nor releases credited on site to "CCR"
ARS does not return Atlanta Rhythm Section
ELO does not return Electric Light Orchestra
BTO returns Bachman-Turner Overdrive
One release credited to "BTO"
BOC does not return Blue Öyster Cult
OMD returns Orchestral Manoeuvres in the Dark
Some performances and releases credited to "OMD"
Not a scientific sample by any means, and I suppose the CCR exception can be attributed to the aforementioned editor discretion.
How do accented letters work under the search function? Does the search treat them as unaccented? If not, should an unaccented hidden alias be used.
Even after further consideration, my position remains the same and has actually broadened to encourage hidden aliases for:
a) Reasonably anticipated name derivatives (i.e. the specific question at hand);
b) Common artist aliases (e.g. ARS, ELO); and
c) Accented letters (if not already handled by the search function).
