Skip to content
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

Closed
AmalieT opened this issue Oct 1, 2019 · 13 comments
Closed

Autocomplete should only suggest normalized entities #112

AmalieT opened this issue Oct 1, 2019 · 13 comments
Labels
backend Requires changes on the backend directly solved by unibox Issue is superceded or made obsolete once unibox is implemented. frontend Requires changes on the frontend

Comments

@AmalieT
Copy link
Contributor

AmalieT commented Oct 1, 2019

No description provided.

@AmalieT AmalieT added backend Requires changes on the backend directly solved by unibox Issue is superceded or made obsolete once unibox is implemented. labels Oct 1, 2019
@jdagdelen
Copy link
Contributor

The way autocomplete works is it completes whatever you were typing but fills in the normalized version.

@AmalieT
Copy link
Contributor Author

AmalieT commented Oct 1, 2019

That doesn't seem to be what's happening on the front end right now? Try typing in Descriptor: Nanoparticle(s) for example.

@AmalieT AmalieT added the frontend Requires changes on the frontend label Oct 1, 2019
@AmalieT
Copy link
Contributor Author

AmalieT commented Oct 1, 2019

Tagging this frontend since it seems that may be the issue here

@AmalieT
Copy link
Contributor Author

AmalieT commented Oct 1, 2019

@ardunn is this because of the way text is transferred from the entities boxes to the main search box?

@jdagdelen
Copy link
Contributor

Maybe we switched this. However, shouldn't entity normalization happen on the back-end once a query comes in?

@AmalieT
Copy link
Contributor Author

AmalieT commented Oct 1, 2019

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.

@ardunn
Copy link
Contributor

ardunn commented Oct 1, 2019

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

@jdagdelen
Copy link
Contributor

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'.

https://github.com/materialsintelligence/matscholar-web/blob/1eb2ecb9cd8ea7bb77b70f8bb31657eeeeb498a1/matscholar_web/search/view.py

@jdagdelen
Copy link
Contributor

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.

@AmalieT
Copy link
Contributor Author

AmalieT commented Oct 1, 2019

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?

@jdagdelen
Copy link
Contributor

jdagdelen commented Oct 1, 2019 via email

@AmalieT
Copy link
Contributor Author

AmalieT commented Oct 1, 2019

Let's revert the normalization change on ESAutoSuggest then?

@computron
Copy link

I think this is superceded by #124 - reopen if needed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Requires changes on the backend directly solved by unibox Issue is superceded or made obsolete once unibox is implemented. frontend Requires changes on the frontend
Projects
None yet
Development

No branches or pull requests

4 participants