fix(app): Raise preference for exact matches of accession numbers when searching for keywords above other fields #2991
Conversation
This file contains 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
…n searching for keywords above other fields
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #2991 +/- ##
=======================================
Coverage 65.15% 65.15%
=======================================
Files 380 380
Lines 24487 24487
Branches 878 878
=======================================
Hits 15954 15954
Misses 8533 8533 ☔ View full report in Codecov by Sentry. |
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.
Tested this with a few example queries (such ds000224 which was an obviously bad example) and 20 consistently returns the accession number match as the #1 result.
See #2671