You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Translator UI calls NameRes as an autocomplete provider, i.e. it calls it for a list of concepts every time the user enters a new character. For a smooth autocomplete experience, NameRes should meet three criteria:
Adding additional characters should not radically change search results.
Once the expected result has shown up, adding additional characters shouldn't get rid of it.
Every additional character should move the expected results further up the search result.
I think this was an artifact of our previous Solr query, but we should write a test to make sure the new query doesn't have the same problem.
Translator UI calls NameRes as an autocomplete provider, i.e. it calls it for a list of concepts every time the user enters a new character. For a smooth autocomplete experience, NameRes should meet three criteria:
I think this was an artifact of our previous Solr query, but we should write a test to make sure the new query doesn't have the same problem.
Should fix NCATSTranslator/Feedback#315, NCATSTranslator/Feedback#312
The text was updated successfully, but these errors were encountered: