Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Browse by metadata: If you already selected a value to browse by (value in url) & then search (startsWith) doesn't work #2739

Open
MarieVerdonck opened this issue Jan 11, 2024 · 1 comment · May be fixed by #2734
Assignees
Labels
affects: 7.x Issue impacts 7.x releases affects: 8.x Issue impacts 8.x releases bug claimed: Atmire Atmire team is working on this issue & will contribute back component: Discovery related to discovery search or browse system

Comments

@MarieVerdonck
Copy link
Contributor

Describe the bug
If you select a browse value in a metadata value browse (add value={browse-value} to url), but then want to search for (another) browse value & start to use the search it won't show any results even if there are browse values that start with your search. This is because the previously selected value param is still present in url / request to rest.

To Reproduce
Steps to reproduce the behavior:

  1. Go to a metadata browse, eg https://demo.dspace.org/browse/subject
  2. Select a value & take note of another existing value
  3. Once on selected value page, eg "annuities" => https://demo.dspace.org/browse/subject?value=annuities, then search for the other existing browse value you took note of before, eg "behavior"
  4. Doesn't show result because the url still contains the previously selected value, https://demo.dspace.org/browse/subject?value=annuities&bbm.page=1&startsWith=behavior

Expected behavior
If you're on a selected value page, and then search for a starts with browse, then the search should just reset.
Or we should hide the search in the selected value page so that you have to go back to all browse values first.

@MarieVerdonck MarieVerdonck added bug needs triage New issue needs triage and/or scheduling labels Jan 11, 2024
@github-project-automation github-project-automation bot moved this to 🆕 Triage in DSpace Backlog Jan 11, 2024
@MarieVerdonck
Copy link
Contributor Author

Similar issue as #2729
Atmire would like to claim this issue

@MarieVerdonck MarieVerdonck added the component: Discovery related to discovery search or browse system label Jan 11, 2024
@MarieVerdonck MarieVerdonck self-assigned this Jan 11, 2024
@tdonohue tdonohue added claimed: Atmire Atmire team is working on this issue & will contribute back and removed needs triage New issue needs triage and/or scheduling labels Jan 11, 2024
@tdonohue tdonohue moved this from 📋 To Do to 🏗 In Progress in DSpace 8.x and 7.6.x Maintenance Jan 11, 2024
@tdonohue tdonohue added affects: 8.x Issue impacts 8.x releases affects: 7.x Issue impacts 7.x releases labels Jun 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects: 7.x Issue impacts 7.x releases affects: 8.x Issue impacts 8.x releases bug claimed: Atmire Atmire team is working on this issue & will contribute back component: Discovery related to discovery search or browse system
Projects
Status: 🏗 In Progress
Development

Successfully merging a pull request may close this issue.

2 participants