On Advanced Search page, when choosing the "No" option of metadata field that has "Yes"/"No" options, expected search results aren't shown
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?
- We have added a customized metadata block "CityUHK" with a metadata field "RGCFunded". The metadata field is a controlled vocabulary with allowed values "Yes" or "No".
- There are four datasets with RGCFunded = "Yes" and two datasets = "No"
- We tried Advanced Search for RGCFunded = "Yes" and the result is correct (4 datasets).
- However, when we tried Advanced Search for RGCFunded = "No", no results were shown (should be 2 datasets).
Which page(s) does it occurs on?
Advanced Search page
What happens?
No datasets were shown when searching with RGCFunded = "No" (a customized metadata field)
To whom does it occur (all users, curators, superusers)?
all users
What did you expect to happen?
Two datasets with RGCFunded = "No" should be shown
Which version of Dataverse are you using?
6.0 (build no. 1512-366fd41)
Any related open or closed issues to this bug report?
No
Are you thinking about creating a pull request for this issue?
Help is always welcome, is this bug something you or your organization plan to fix?
Yes
Related discussion: https://groups.google.com/g/dataverse-community/c/t9zMmbk7Ou4/m/qMlcaeXVBQAJ
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 on the Advanced Search page and reproduce the issue with a controlled-vocabulary metadata field containing “Yes” and “No,” as described in the report. Trace the search handling for the “No” value and verify that the expected datasets are returned while the existing “Yes” behavior remains correct.
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
- 35/100