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 #28

Open
hortongn opened this issue Jun 29, 2020 · 4 comments
Open

Breadcrumbs #28

hortongn opened this issue Jun 29, 2020 · 4 comments

Comments

@hortongn
Copy link
Member

hortongn commented Jun 29, 2020

User story

As a user
I want to see the hierarchy of parent collections and works above the item I'm currently viewing
So that I can clearly see which collections or works the current item is contained within

Acceptance criteria

  • At the top of the page there is a clear listing of the collections and/or parent works that contain the current item.
  • Example: UC DRC Home -> University of Cincinnati Libraries -> Historical Records -> Cincinnati Subway and Street Improvements -> Rapid Transit Construction
  • Breadcrumbs exist on both work show pages and collection show pages

Related Work

Notes

  • An item can only belong to one collection
  • current breadcrumbs aren't appropriate for browsing collections
  • breadcrumbs should reflect collection hierarchy, and should make it easy to navigate back up the collection hierarchy

Resources

@crowesn
Copy link
Contributor

crowesn commented Jul 20, 2020

@jamesvanmil
Copy link

@crowesn this looks more like an implementation of facet filtering - in the case of breadcrumbs we will have a situation where there's only one route to each collection

@crowesn
Copy link
Contributor

crowesn commented Jul 21, 2020

@jamesvanmil Won't we have potential for an item to be contained in multiple collections?

@jamesvanmil
Copy link

jamesvanmil commented Jul 22, 2020

@crowesn a lot of this is informed by the community/collection design in dspace - i think that we'd be able to find cases where folks might want to do this, but committing to a strict hierarchy where each child only has one parent will make a lot of problems easier - e.g. breadcrumbs and recursive collection nesting (the latter is important if we want to be able to search recursively through a collection tree, e.g. as in #46)

i'd also argue that the multiple collection use cases are probably pointing towards the need for an exhibits platform.

ultimately i'm thinking of collections as being roughly analogous to admin sets, but designed for public use, and with the potential for sub-collections.

@hortongn hortongn added this to the Next sprint milestone Dec 11, 2020
@bsp3ars bsp3ars self-assigned this Jan 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants