exact search sometimes returns inexact results
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
What steps does it take to reproduce the issue?
Create three datasets, with titles:
- Alphafold structure of mutation type Q8TDZ2/A758E protein
- Alphafold structure of mutation type Q8TDZ2/A758S protein
- Alphafold structure of mutation type Q8TDZ2/A758T protein
When does this issue occur?
Searching for "Alphafold structure of mutation type Q8TDZ2/A758E protein" (with quotes!)
search API equivalent: curl $SERVER_URL'/api/search?type=dataset&q=title:"Alphafold+structure+of+mutation+type+Q8TDZ2/A758E+protein"'
(You can search for Q8TDZ2/A758S too, the result is the same).
Which page(s) does it occurs on?
search result page, API
What happens?
It displays two results:
- Alphafold structure of mutation type Q8TDZ2/A758E protein
- Alphafold structure of mutation type Q8TDZ2/A758S protein
To whom does it occur (all users, curators, superusers)?
all users
What did you expect to happen?
Only display one result.
If I search for "Alphafold structure of mutation type Q8TDZ2/A758T protein", there is only one result.
Which version of Dataverse are you using?
6.1
Any related open or closed issues to this bug report?
I could not find any.
Screenshots:
Are you thinking about creating a pull request for this issue?
Maybe...
Other notes
This may very well be a solr issue
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the quoted dataset search with the provided curl command and compare it with the search result page. Trace the search API and result handling to identify why the A758E query includes A758S; done means both interfaces return only the exact matching dataset.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100