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

Make Collection Level Access restrictions badges clickable; and open the Access and Use Tab #1368

Open
1 task done
ccleeton opened this issue Jan 11, 2024 · 6 comments
Open
1 task done
Labels
dls-work-cycle Tickets designated for the next work cycle (limit 16) sudden-priority user experience

Comments

@ccleeton
Copy link
Collaborator

ccleeton commented Jan 11, 2024

Users consistently try to click on badges thinking they are buttons.
For example when it shows Access Restrictions,, jump to the access page or the conditions governing access

Acceptance Criteria

First Step

Write a test.

@ccleeton ccleeton changed the title Access restrictions badges: make these clickable/interactive Collection Level Access restrictions badges: make these clickable/interactive and open the Access and Use Tab May 17, 2024
@ccleeton
Copy link
Collaborator Author

Example: https://findingaids.princeton.edu/catalog/MC247
At the top of the finding aid under the title and the online access green bar, make the "Restrictions may apply. See Access Note" clickable and open the Access & Use tab.

@ccleeton
Copy link
Collaborator Author

ccleeton commented May 17, 2024

Justification for Sudden prioirty - Users consistently try to click the badge at the top of the finding aid. Users also consistently do not understand if they can actually view the material in person.

@ccleeton ccleeton changed the title Collection Level Access restrictions badges: make these clickable/interactive and open the Access and Use Tab Make Collection Level Access restrictions badges clickable/interactive; and open the Access and Use Tab May 17, 2024
@ccleeton ccleeton changed the title Make Collection Level Access restrictions badges clickable/interactive; and open the Access and Use Tab Make Collection Level Access restrictions badges clickable; and open the Access and Use Tab May 17, 2024
@tpendragon tpendragon added the dls-work-cycle Tickets designated for the next work cycle (limit 16) label Nov 12, 2024
@Seanwarren77 Seanwarren77 self-assigned this Nov 13, 2024
@ccleeton
Copy link
Collaborator Author

I saw the ticket was closed but I am not seeing it active in the finding aid. Am I missing something?

@hackartisan
Copy link
Member

@ccleeton I've just deployed; it should be in place now!

@faithc
Copy link
Collaborator

faithc commented Nov 21, 2024

Hi @hackartisan and @Seanwarren77 -

I noticed that badges at lower levels of description are linking to the collection-level Conditions Governing Access note in the Access + Use tab. If it's possible to implement, badges associated with components should link to the Conditions Governing Access note applied at that component level.

For example, the badge at the series level here shouldn't link to the collection-level note, but rather to the note associated with that component.

The badge here should link to the Conditions Governing Access note associated with the component, i.e., "Restricted for 75 years (until 2094)." This one doesn't seem to link out at all at the moment.

Please let me or Christa know if you have any questions. Thanks!

@Seanwarren77
Copy link
Contributor

@faithc good catch thank you for noticing this. We are looking at this now and realizing that this ticket only asked for the Collection level badge to be a link. We are thinking a good next step would be to make the badge not a link at the series and component levels, The same way we just did for the search results. Then we can move on to #1370 and see how it is all coming together. Does that sound good?

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) sudden-priority user experience
Projects
None yet
Development

No branches or pull requests

5 participants