wonky name-matching policies in autocomplete

[remontoire-pac]

and not reproducible

[sierra-moxon]

following up with @remontoire-pac - this is another instance of:
"autocomplete results change on each addition of a new letter, but suggestions, after the new letter is added, are a completely different set of results."

[remontoire-pac]

important new nuances:

• the "new letter" added might even be a space
• deleting the new letter does not bring back the original results

[dnsmith124]

It sounds like the issue here is twofold:

1. The suggestions returned by the autocomplete are significantly different when a search term changes by only a single letter
2. Suggestions are not consistent when the same input string is searched more than once.

Is that correct? If so I think the former problem should be resolved by the biolink type selection feature planned for the name resolver. The latter sounds like a problem not with the UI but with the Name Resolver or Node Normalizer not consistently returning the same terms for a given input string.

[remontoire-pac]

I have seen both of those behaviors separately and (I think) together. I can try to experiment more carefully if that would be helpful.

…

On Fri, Jun 9, 2023 at 4:03 PM David Smith ***@***.***> wrote: It sounds like the issue here is twofold: 1. The suggestions returned by the autocomplete are significantly different when a search term changes by only a single letter 2. Suggestions are not consistent when the same input string is searched more than once. Is that correct? If so I think the former problem should be resolved by the biolink type selection feature planned for the name resolver. The latter sounds like a problem not with the UI but with the Name Resolver or Node Normalizer not consistently returning the same terms for a given input string. — Reply to this email directly, view it on GitHub <#312 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQFWTWCLQDHHJOGHTWCHLLXKN6RLANCNFSM6AAAAAAY4U3G54> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[gaurav]

Tracking at TranslatorSRI/NameResolution#64

[gaurav]

This should be fixed once UI switches over to the new NameRes (with the possible exception for genes, but we're trying to fix that now). I'll close once we can confirm that this is the case. We now have some testing tools available to make sure this works correctly in NameRes.

[gaurav]

@remontoire-pac could you please retest this at https://ui.ci.transltr.io/? It should be fixed now.

[remontoire-pac]

I was unable to reproduce the earlier behavior, and poking at the auto-complete just now left me with the impression that it is behaving more "naturally". PAC

…

On Fri, Jul 28, 2023 at 11:53 AM Gaurav Vaidya ***@***.***> wrote: @remontoire-pac <https://github.com/remontoire-pac> could you please retest this at https://ui.ci.transltr.io/? It should be fixed now. — Reply to this email directly, view it on GitHub <#312 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQFWTRNI32PKKAVR6JIPTDXSPOBNANCNFSM6AAAAAAY4U3G54> . You are receiving this because you were mentioned.Message ID: ***@***.***>