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

Access restriction badge should appear on search results page #1447

Closed
1 task done
faithc opened this issue Oct 8, 2024 · 0 comments
Closed
1 task done

Access restriction badge should appear on search results page #1447

faithc opened this issue Oct 8, 2024 · 0 comments
Assignees
Labels
dls-work-cycle Tickets designated for the next work cycle (limit 16) feature user experience

Comments

@faithc
Copy link
Collaborator

faithc commented Oct 8, 2024

User story

As a user, it is important for me to see that materials are restricted from the search results page. The visibility of access restrictions should be robust.

Acceptance criteria

  • When viewing a restricted item in search results there should be a badge next to restricted items.

Concrete example

A researcher does not know that any of these materials are restricted unless they click on the component. See for example, the search results listed here. All of these materials are restricted.

An example that isn't a component, but should have a badge: https://findingaids.princeton.edu/catalog/C1491_c84, search result: https://findingaids.princeton.edu/?f%5Bcollection_sim%5D%5B%5D=Toni+Morrison+Papers%2C+1908-2017+%28mostly+1970-2015%29&group=true&search_field=all_fields

Implementation notes, if any

Adding "Restricted" badges to the search results page would likely be akin to current functionality that adds the "Has Online Content" badge to the search results page.

This should use the same logic as we use in the show page for the components.

These probably shouldn't be a link, because it would send them to the collection page and not the component page.

First Step

Write a test. The Toni Morrison items in the test fixtures should include restricted items that can be used here.

@faithc faithc added user experience feature On Deck Next issues marked by product owners for working on. labels Oct 8, 2024
@tpendragon tpendragon added dls-work-cycle Tickets designated for the next work cycle (limit 16) and removed On Deck Next issues marked by product owners for working on. labels Nov 18, 2024
@Seanwarren77 Seanwarren77 self-assigned this Nov 19, 2024
hackartisan added a commit to pulibrary/pul_solr that referenced this issue Nov 26, 2024
hackartisan added a commit to pulibrary/pul_solr that referenced this issue Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dls-work-cycle Tickets designated for the next work cycle (limit 16) feature user experience
Projects
None yet
Development

No branches or pull requests

3 participants