Collection Page - Sort type as relevance when searching#726
Merged
ofahimIQSS merged 2 commits intodevelopfrom May 29, 2025
Merged
Collection Page - Sort type as relevance when searching#726ofahimIQSS merged 2 commits intodevelopfrom
ofahimIQSS merged 2 commits intodevelopfrom
Conversation
ekraffmiller
previously approved these changes
May 29, 2025
Contributor
ekraffmiller
left a comment
There was a problem hiding this comment.
looks good! approved
Contributor
|
tested it with limited data in local - looks good from my point of view. Will merge after test/component completes. |
Contributor
Author
|
@ekraffmiller I just made a commit to use latest js-dataverse package |
ekraffmiller
approved these changes
May 29, 2025
Contributor
|
All good here - merging PR |
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.
What this PR does / why we need it:
We need to sort by relevance (score) when searching in the collection page.
The Sort By dropdown was showing the "Relevance" option as selected but we were not actually sending that parameter to the Search API.
Which issue(s) this PR closes:
Special notes for your reviewer:
Suggestions on how to test this:
Validate that this fixes the behaviour found in #723
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
Is there a release notes update needed for this change?:
Additional documentation: