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

Add Alternative Query Suggestion In No Results Message #1975

Open
thostetler opened this issue Nov 29, 2019 · 5 comments · Fixed by #1979
Open

Add Alternative Query Suggestion In No Results Message #1975

thostetler opened this issue Nov 29, 2019 · 5 comments · Fixed by #1979

Comments

@thostetler
Copy link
Member

When no results are found for a non-fielded query where all the characters are uppercase, we should provide an alternative query to try that is lowercase.

@aaccomazzi are there other cases when this message should show?

@csgrant00
Copy link

@aaccomazzi @thostetler - User group suggested this for an institution search that returns no results (e.g. Harvard - did you mean Harvard U). Maybe an instutution search that is 1 word could suggest - did you mean "blah U" or "blah Coll" ?

@aaccomazzi
Copy link
Member

In the case of the uppercase query, it's easy for the application to detect and provide a suggestion. For the institution query, it's much harder, because I think a suggestion is only useful if it steers the user towards something which produces results. So I think that here we'd need autocomplete.

@thostetler
Copy link
Member Author

@aaccomazzi @csgrant00 how do you guys feel about this?
image

@aaccomazzi
Copy link
Member

Hi Tim, I like it, but why not put it as the first option in the bullet list:

  • Try an alternate query: helio cmr mutation

and we would only do this when the input is all uppercase.

thostetler added a commit to thostetler/bumblebee that referenced this issue Dec 11, 2019
thostetler added a commit to thostetler/bumblebee that referenced this issue Dec 11, 2019
@aaccomazzi
Copy link
Member

We have seen cases where the user enters the query from the classic form with the title in all caps and we end up with a query that looks like this:

title:(FOO BAR XXX)

In which case no warning is issued (presumably because the field title makes the entire string be mixed case). Can we catch these cases as well with a regexp?

@aaccomazzi aaccomazzi reopened this May 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants