We actually used to do this but stopped due to feedback.
If the item was mis-matched, that means that our "best guess" is incorrect - perhaps wildly so. Therefore, populating the screen with this incorrect data just made people have to go blank it out in order to get any result other than what had already been found (and was wrong). So, starting with a blank screen should actually be quicker in these instances.
You can just type in part of the title or one of the provider IDs (if you know it) and off you go...
i am surprised by the comments favoring embys identify interface and the confidence in the current identify design. cant argue with the feedback i guess but i am surprised.
i use both regularly and am familiar with the pros and cons in real world use. there is opprtunity to take the best from both and improve emby's identify process.
imo it would be better to pre populate the identify interface with current data ie data that emby used to get an incorrect match. and offer a clear button against each field (perhaps a clear all button to satisfy die hard supporters of the current design) for the following reasons.
1. in my case the incorrect match is never because the search data is wrong but a unique result is not possible, having to reenter the title is annoying.
2. seeing the data used for match would highlight mistakes in file naming etc and why a match is not working.
3. its quicker to clear a field than to type it in...especially when using a controller rather than keyboard . so starting with something gives the best of both worlds imo.
there is an argument that some of the search terms hinder more than help eg an incorrect year..but title is 100% useful search term (in all but straight id lookups)... better to start with what youve got than type in again. maybe there is a case for when results are 0, show "no results but these are results when eg 'year' is dropped".
emby has been making improvements in the identify results with pictures and metadata against the results to aid disambiguation i would urge that to continue.
going outside emby to imdb/tmdb/tvdb ids is a useful last unequivocal resort but shouldnt be neccessary with the right interface.
plexs identify interface gives the option to change provider priority for a single media item, complete overkill but shows a powerful capability in the 'agent' design that touches the identify capability.
full disclosure: all my library content is cleaned through other tools before emby sees it, so is 100% correct, maybe this is the discrepancy that explains the surprise..for people with messy data its better to start from scratch..still think my suggestion would work well for both.
slightly off topic..
there is more than enough metdata available in music libraries and flexibilty in musicbrainz api for matches to become ~100% (artists with albums with tracknames with track number)..plex's music artist match is significantly more robust.
i would love a plugin to store manual corrections in a separate area, so when an inevitable full rebuild comes along these can be read back in to save all the hard work.
Sent from my SM-G955F using Tapatalk
Edited by ginjaninja, 05 January 2019 - 01:35 AM.