-
Notifications
You must be signed in to change notification settings - Fork 51
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
Phrase Searching for Blacklight Search Results #6171
Comments
Resolving this may also impact searching on the collections page. Theoretically, it uses the same API, so would also implement phrase searching. |
I searched for “goodman, benny.” Second result has benny goodman, but not goodman, benny. No transcripts are involved. This suggests that at least in MCO, the metadata search is not respecting phrases. It does look like MDPI (which is still running 7.7??) may be respecting phrase searching. |
An OR clause is added to the main query: if there are any "Found in" matches, it will match the record as a whole. We could redefine this main clause; worst case would be having to do a big reimplement, but maybe it wouldn't matter. |
We could look at the search_builder model's search_section_transcripts method to possibly change this behavior. |
@joncameron Was this moved back to Backlog because more examples are needed? |
Description
Phrase searching is possible in Avalon's current configuration by enclosing a search phrase in quote characters, but extra results also appear for things that seem beyond the scope of the phrase.
Phrase searching isn't working as expected for metadata, section data, and transcripts that are searched as part of Blacklight results in MCO: search matched for a substring within a phrase and not the exact phrase string.
"Found in" tokenization is a different case; this ticket only relates to the blacklight search and results, not the "Found In" count/report.
Feedback on search and default "OR":
We'll need to look at the case above—deleting the transcript document for 1544bq372 in mco-staging removed it from returning as a result.
To Reproduce
MCO
First example
Second example
avalon-dev
Done Looks Like
The text was updated successfully, but these errors were encountered: