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

Bound with UI on search results #4116

Open
dbranchini opened this issue Mar 8, 2024 · 0 comments
Open

Bound with UI on search results #4116

dbranchini opened this issue Mar 8, 2024 · 0 comments

Comments

@dbranchini
Copy link

After discussion with stakeholders, we decided to present bound-withs in a minimal/lean fashion for the search results page and link to the record view for detailed information. However, the request button will be available on the child record as well as the parent record. If the user decides to request the item, they'll see additional bound with information on that screen too. To that end, here are the visuals for bound withs on the search results page:

Child item - To fear a painted devil

Parent item - The bridesmaid

Mix of both child and parent items - The gases of swamp rice soils:


Design notes:
Regardless of whether it's a child or parent record, there is s separate note in a gray box above the location info:

  • Copy: "Some items are bound together - see record for full details."
  • "see record for full details" is a link to the record view
  • Gray box background is Accent-Fog-Light or #F4F4F4
  • Gray box has 8px padding on the left and right and 4px padding on the top and bottom.
  • Availability status is presented with a request button (if it's requestable - same logic as record view)
  • And for The gases of swamp rice soils (or other complex bound withs where there are items bound together on the same instance, then we'll group those into one row and provide one mention of availability. If it's an item-level request, the request button would also appear here (and just once).

There are also prototypes you can follow instead of the screenshots if you prefer:

Child item: https://www.figma.com/proto/sqzYVhfRgn3nMArUAdrs0n/SearchWorks?page-id=453%3A2788&type=design&node-id=576-1498&viewport=9%2C1638%2C1&t=t8GqaXmNnp8pR08v-9&scaling=min-zoom&starting-point-node-id=576%3A1498&show-proto-sidebar=1

Parent item: https://www.figma.com/proto/sqzYVhfRgn3nMArUAdrs0n/SearchWorks?page-id=453%3A2788&type=design&node-id=576-1933&viewport=9%2C1638%2C1&t=t8GqaXmNnp8pR08v-9&scaling=min-zoom&starting-point-node-id=576%3A1933&show-proto-sidebar=1

Mixed complex item: https://www.figma.com/proto/sqzYVhfRgn3nMArUAdrs0n/SearchWorks?page-id=453%3A2788&type=design&node-id=571-960&viewport=9%2C1638%2C1&t=t8GqaXmNnp8pR08v-9&scaling=min-zoom&starting-point-node-id=571%3A960&show-proto-sidebar=1

@dnoneill dnoneill self-assigned this Mar 18, 2024
@dnoneill dnoneill removed their assignment Jun 20, 2024
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