Feedback on Artist Identity Correction - Not Simple..

[ginjaninja 605]

http://www.musicbrainz.org/ws/2/artist/?query=artist:%22Adele%22

 

My Adele was identified as Adèle.....fair enough...would need more logic to override mbz's api confidence ..... However.......

 

this is the user experience to correct - imo a bit long winded...

 

1. find the identified object name in library.... click identify...interface auto populated with identified value 'Adèle' rather than source value "Adele".....think source would be more useful..

The search interface autopopulated with the mbzid (which is a 1-1 mapping) of the current identify...why bother identifying again with the same identity - presumably its wrong - is there another reason to use the identify interface/workflow..

3. change name in search criteria to Adele..click go....http://www.musicbrainz.org/ws/2/artist/?query=artist:%22Adele%22 ..all returned results are titled... Adèle...emby really doesnt want me to correct :-)

4. Pick the 3rd object ..titled Adèle ...but which actually is the correct Adele...(by matching manually to the api http response)...a casual user wouldnt stand a chance...

5. The name of the artist object is still Adèle despite now having Adele's bio/ mbz ids etc...emby still fighting me :-)

6. Manually change the name from Adèle to Adele....finish..

 

not easy...

Edited March 26, 2015 by ginjaninja

[ginjaninja 605]

Version 3.0.5607.42442...some improvements but still not functional.

 

1. Adele identified as 'Adèle', due to mbz response

In general, accented matches do have value, but it would be an improvement if exact matches were preferred over accented matches...in this example both have a 100% confidence.

 

2. Press Identify..Interface defaults to matched name 'Adèle' rather than tag source name Adele..identify interface defaults to search on old mbz id which is presumably wrong, as why else would you be identifying...

perhaps each current matched tag could have a radio tick..to include in the search..so that the best default radio on/off can be designed into ui...

 

3. Amend interface fields manually to search against source tag values rather than incorrect match....

 

4. All results returned are unhelpfully suffixed by the old name rather than at least the named searched for...or better yet the name from the xml result...to give the user a chance to select the correct identity.

5. The name field is (now) updated correctly in emby/nfo when the 2nd object is selected from the search..ie 'Adele'...

 

Fellow users are you seeing this as an opportunity? .... stand up and be counted please....:-)...wants the devs to hear...

Edited May 10, 2015 by ginjaninja