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

Analyze and improve relevance ranking #532

Closed
3 of 6 tasks
anarchivist opened this issue Jul 22, 2019 · 2 comments
Closed
3 of 6 tasks

Analyze and improve relevance ranking #532

anarchivist opened this issue Jul 22, 2019 · 2 comments

Comments

@anarchivist
Copy link
Member

anarchivist commented Jul 22, 2019

Users regularly report that they don't know why certain results are being shown first

@mejackreed
Copy link
Collaborator

mejackreed commented Aug 13, 2019

Related to #531 and #369

@seanaery seanaery self-assigned this Dec 8, 2023
seanaery added a commit that referenced this issue Dec 11, 2023
…onfig. Advances #532.

Fixes these problems with the previous config:
 - only 2 terms had to match in a 3-term query, or 3 terms out of 4 (too permissive)
 - any 3-10 term query had to match all but 1 term *except* for 6-term queries, which oddly had to match all but 2.
Now all terms must match for a query of 4 or fewer. Above 4, 90% must match (rounded down).
seanaery added a commit that referenced this issue Dec 11, 2023
- this is the general intent in arclight, see * in config.default_solr_params & config.catalog_controller_group_query_params
- simplifies managing this config as fields change over time.
seanaery added a commit that referenced this issue Dec 11, 2023
…onfig. Advances #532.

Fixes these problems with the previous config:
 - only 2 terms had to match in a 3-term query, or 3 terms out of 4 (too permissive)
 - any 3-10 term query had to match all but 1 term *except* for 6-term queries, which oddly had to match all but 2.
Now all terms must match for a query of 4 or fewer. Above 4, 90% must match (rounded down).
marlo-longley added a commit that referenced this issue Dec 12, 2023
Set the default SearchHandler to just return all fields. Advances #532
seanaery added a commit that referenced this issue Dec 14, 2023
…guage, & ancestor component titles. Closes #894 & Advances #532.

- Adds Container & Identifier to search scope dropdown
- Adds parent component titles, language, containers, & identifiers into the default all-fields search
- TODO: more scoring boost refinement; this PR only gets these elements to be considered at all in queries
seanaery added a commit that referenced this issue Dec 14, 2023
…guage, & ancestor component titles. Closes #894 & Advances #532.

- Adds Container & Identifier to search scope dropdown
- Adds parent component titles, language, containers, & identifiers into the default all-fields search
- TODO: more scoring boost refinement; this PR only gets these elements to be considered at all in queries
marlo-longley pushed a commit that referenced this issue Dec 14, 2023
…guage, & ancestor component titles. Closes #894 & Advances #532. (#1487)

- Adds Container & Identifier to search scope dropdown
- Adds parent component titles, language, containers, & identifiers into the default all-fields search
- TODO: more scoring boost refinement; this PR only gets these elements to be considered at all in queries
@seanaery
Copy link
Contributor

Closing out this ticket as we have implemented several relevance improvements in the Dec 2023 community sprint. We have also updated the wiki doc here: https://github.com/projectblacklight/arclight/wiki/Configuring-Solr-and-Search-Relevancy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants