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

Breadcrumbs do not lead back to SERP from Finding Aid page #7

Closed
MomoMoses opened this issue Aug 23, 2021 · 3 comments
Closed

Breadcrumbs do not lead back to SERP from Finding Aid page #7

MomoMoses opened this issue Aug 23, 2021 · 3 comments

Comments

@MomoMoses
Copy link
Collaborator

MomoMoses commented Aug 23, 2021

To demonstrate the issue, do an empty search, then select facet term(s). From this SERP, choose a collection to view the finding aid. From here the breadcrumbs lead only to the "Collections Portal" index page or to the BMRC main page.
The browser "back" button does go back to the SERP.

@johnjung
Copy link
Owner

The current behavior is how I understood the spec. Currently, breadcrumbs on the site do not reflect the the path that a user took to get to a specific page, instead they reflect the information architecture of the site in a static, non-interactive way. (So in this case, a user needs to click the back button to get back to a search result page.)

It would be possible to implement a breadcrumb link leading back to the SERP, but this would be a new feature. If we really need this could we save it for a v2.0?

@MomoMoses
Copy link
Collaborator Author

We had discussed this and I understand the user path vs. architecture distinction. What's perhaps surprising is that a SERP is not actually part of the information architecture. Is that correct?
Agreed to see if this is needed through user research, and push it to 2.0 if at all.

@johnjung
Copy link
Owner

The fact that SERPs are dynamic is the issue- so if we need a "back to search results" link, I would need to implement something to save the state of the SERP, which we're not doing right now. I'm going to close the issue out, but if we need to revisit this we can open it again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants