-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Autocomplete should only suggest normalized entities #112
Comments
The way autocomplete works is it completes whatever you were typing but fills in the normalized version. |
That doesn't seem to be what's happening on the front end right now? Try typing in Descriptor: Nanoparticle(s) for example. |
Tagging this frontend since it seems that may be the issue here |
@ardunn is this because of the way text is transferred from the entities boxes to the main search box? |
Maybe we switched this. However, shouldn't entity normalization happen on the back-end once a query comes in? |
It does, but I thought from a user perspective it should be clear that searcing nanoparticle vs nanoparticles or SiO2 vs O2Si are equivalent. It helps highlight the added value that we have vs plain text search engines. |
The current frontend just uses ESAutosuggest like the old one did. I haven't goofed around with exactly what it is doing yet. I'll fix soon |
The ESAutosuggest has two fields available in its results list, 'original' and 'normalized'. Right now as we have it defined we're using the default filed of 'original'. |
Ok, I just switched it to display and fill normalized entities on the staging site. Let's try it out and see how we feel about that. |
Feels ok, but I wonder if there's an intuitive way to have the normalization happen between transferring from the entity box to the main search box? |
There is a way to do that. Just have to modify how ESAutosuggest works on the React side.
However, this might be confusing to the user. I think the best solution is to normalize on the backend and indicate to the user that it’s also searching on equivalent terms.
On Tue, Oct 1, 2019 at 1:45 PM, AmalieT <[email protected]> wrote:
Feels ok, but I wonder if there's an intuitive way to have the normalization happen between transferring from the entity box to the main search box?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub [#112?email_source=notifications&email_token=ACFODYIZWAXGKLYQT2TYN3DQMOZHJA5CNFSM4I4OFUW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEACV3TQ#issuecomment-537222606] , or mute the thread [https://github.com/notifications/unsubscribe-auth/ACFODYKANZUTH3P6XSUL3TLQMOZHJANCNFSM4I4OFUWQ] .
|
Let's revert the normalization change on ESAutoSuggest then? |
I think this is superceded by #124 - reopen if needed |
No description provided.
The text was updated successfully, but these errors were encountered: