Introduce scores to API responses - #444
Merged
Merged
Conversation
❌ 6 blocking issues (6 total)
|
jazairi
approved these changes
Jul 31, 2026
Why are these changes being introduced: * Scores will be useful in reranking results in the near future Relevant ticket(s): * https://mitlibraries.atlassian.net/browse/USE-654 How does this address that need: * GraphQL queries now request scores * Scores are now normalized into the records for both TIMDEX and Primo Document any side effects to this change: * Cassettes regeneration for TIMDEX cassettes
JPrevost
force-pushed
the
use-654-add-scores
branch
from
August 3, 2026 17:25
4e14764 to
40dc79a
Compare
Coverage Report for CI Build 30836690009Coverage decreased (-0.06%) to 98.326%Details
Uncovered Changes
Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why are these changes being introduced:
Relevant ticket(s):
How does this address that need:
Document any side effects to this change:
Developer
Accessibility
New ENV
Approval beyond code review
Additional context needed to review
E.g., if the PR includes updated dependencies and/or data
migration, or how to confirm the feature is working.
Code Reviewer
Code
added technical debt.
Documentation
(not just this pull request message).
Testing