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

Relevance: analyze stemming behavior #725

Closed
anarchivist opened this issue Sep 5, 2019 · 1 comment · Fixed by #855
Closed

Relevance: analyze stemming behavior #725

anarchivist opened this issue Sep 5, 2019 · 1 comment · Fixed by #855
Assignees

Comments

@anarchivist
Copy link
Member

On the 2019-09-04 PO call, we talked about matches (involving names) where names that appeared in e.g. a title were ranked lower than than those containing a stemmed form of the query. For example, the name Eugene is presumably getting stemmed to eugen, which also matches eugenics.

  • What are our options for adjusting this?
  • Are there specific fields that do not benefit from stemming?
@cbeer
Copy link
Member

cbeer commented Sep 19, 2019

KeywordRepeatFilterFactory may be sufficient in many cases to address stemmed vs unstemmed relevancy.

cbeer added a commit that referenced this issue Sep 19, 2019
… preserving incoming keywords for better exact matching, etc; fixes #725
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants