yalelibrary / YUL-DC

Preliminary issue tracking for Yale University Libraries Digital Collections project
3 stars 0 forks source link

Blacklight OwP - user's request list #2594

Closed mikeapp closed 8 months ago

mikeapp commented 1 year ago

Story

Design is required for the user's management of their requests in Blacklight. Is this part of the /bookmarks page, or a new page? How does the user navigate to it? What does the list of new/approved/expired requests look like?

Acceptance

tmacmath commented 1 year ago

What kind of requests are we talking about, just to clarify? Requests for digitized copies, other copies, etc.?

sshetenhelm commented 1 year ago

Requests for access to 'Open with Permissions' materials.

They can pull files directly from DCS, there's no need to request that.

For objects with aspace or orbis info, users can click through to descriptive records to request physical access. We might want to make that more clear in the future, but I don't want that to hold up this work.

tmacmath commented 1 year ago

"For objects with aspace or orbis info, users can click through to descriptive records to request physical access." Can't they do that for any objects requiring physical access? They certainly wouldn't request within the search results.

tmacmath commented 11 months ago

@sshetenhelm Are we creating a separate Requests page for this (say, like the page with table in Orbis that shows which materials a patron has borrowed)?

sshetenhelm commented 10 months ago

As per Slack, we decided a separate request page would be good. I didn't see anything in the specs that would indicate we would need to think otherwise. I liked the table drawing you did. What specific info did you need -- exact fields for the table from the specs?

We will need to update the Bookmarks list UI to indicate what has been requested and to link to list, but that will be in another ticket. We could have a link back to the bookmarks page from this request list page, and that could just be a button or something that sits at the top of the table.

Please let me know what else you need from me to move forward with this.

tmacmath commented 9 months ago

Here is the mockup - design specs to follow.

Image

tmacmath commented 8 months ago

Design Specs:

A. Digital Access Requests header: 35px; #043669; YaleDisplay-Roman; border-bottom: none;

Table should be similar to the table in the Management App: B. Table font: Mallory Medium, 16pt (default link color) C. Links: object title should link to the object in the DL; regular link color D. Table zebra striping: #ffffff; alternating with #f2f2f2; (same as the table in the management app) E. Table border: 1px solid #dee2e6; F. Table header/field labels: font-size: 18px; font-family: Mallory-Medium; font-color: #043669; G. For table values that are not links: font-family: Mallory-Medium (400); font-size: 14px; font-color: #222529; H. For the sort icon, use Font Awesome or Bootstrap Glyphicons - I will provide a link to it, and if those don’t work well, I’ll find something else.

Image

tmacmath commented 8 months ago

I am currently researching better tools for delivering design specs. XD is not optimal, and others require paid subscriptions.

sshetenhelm commented 8 months ago

Thank you! Created #2724 for engineering work.

Ready to close :)