Describe the bug
We are working on DSpace 9.2. When I go to an item and click one of the listed keywords, it does NOT show a list of all items associated with that keyword. Instead, it bounces to the Subject Category browse page. The keyword should correspond to Subjects rather than Subject Categories. How can I deal with this issue?
Dspace-tech thread: https://groups.google.com/g/dspace-tech/c/vFYHd7dJHdM/m/_ZJ-11OyAQAJ
To Reproduce
Steps to reproduce the behavior:
- Click on one of the keywords on an item page.
- First directed to
browse/srsc?startsWith=[keyword]
- If you click Browse, directed to
/search?startsWith=[keyword]. If a subject category was selected on browse, directed to `/search?startsWith=[keyword]&f.subject=[subject category]
- End result is user does not retrieve a set of items with the same keyword(subject) as the one clicked
Expected behavior
Expect to go to a search or browse page containing items with the same keyword, which corresponds to Subjects rather than subject categories.
One solution could be simply directing the links to "/search?f.subject=[keyword]", but other possibilities might address the issue.
Related work
N/A
Describe the bug
We are working on DSpace 9.2. When I go to an item and click one of the listed keywords, it does NOT show a list of all items associated with that keyword. Instead, it bounces to the Subject Category browse page. The keyword should correspond to Subjects rather than Subject Categories. How can I deal with this issue?
Dspace-tech thread: https://groups.google.com/g/dspace-tech/c/vFYHd7dJHdM/m/_ZJ-11OyAQAJ
To Reproduce
Steps to reproduce the behavior:
browse/srsc?startsWith=[keyword]/search?startsWith=[keyword]. If a subject category was selected on browse, directed to `/search?startsWith=[keyword]&f.subject=[subject category]Expected behavior
Expect to go to a search or browse page containing items with the same keyword, which corresponds to Subjects rather than subject categories.
One solution could be simply directing the links to "/search?f.subject=[keyword]", but other possibilities might address the issue.
Related work
N/A