Requests (UXPROD-790)

[UXPROD-4062] Requests: Special collections mediated requests Created: 10/Feb/23  Updated: 05/Jan/24

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: Sunflower (R3 2024)
Parent: Requests

Type: New Feature Priority: TBD
Reporter: Stephanie Buck Assignee: Stephanie Buck
Resolution: Unresolved Votes: 0
Labels: lc-priority4, loc, requests
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Continues
continues UXPROD-4657 Mediated requests phase 1 (Base app./... In Progress
Gantt End to Start
has to be done after UXPROD-4559 ECS support: Title level requests (pa... In Progress
Relates
relates to UXPROD-4119 Private requests (Congressional loans) In Progress
Release: Not Scheduled
Epic Link: Requests
Front End Estimate: XXL < 30 days
Front End Estimator: Khalilah Gambrell
Front-End Confidence factor: 20%
Back End Estimate: XXL < 30 days
Back End Estimator: Khalilah Gambrell
Development Team: Vega
PO Rank: 0
Rank: Cornell (Full Sum 2021): R3

 Description   

Current situation or problem: Staff in special collections need a way to preview requests before they begin the fulfillment process so they can decide if the patron can handle the requested material

In scope

Out of scope

Use case(s)

  • A patron would like to view a rare map in special collections. They place a request for the map. In the special collections room, the staff person receives the request and is able to decide if the patron can handle the map or not. Sometimes this will include an interview with the patron. 

Proposed solution/stories

Links to additional info

Questions

1. Where in the request workflow does mediation occur? 

  • There are likely use cases for mediation:
    • After request created, before checking for an available item - "Is patron X eligible to use item Y?" (verify patron)
    • After request is created, after item is received at pickup location, but prior to request fulfillment and patron notices - "Is item Y in good enough shape for patron X to use?" (approve item)
    • After request is created, and patron is notified, but prior to item checkout - "Has patron X signed the form to enable them to use item Y?" (verify patron completed X form)

2. Are all requests mediated, or just some?

    • It's likely that some libraries would want all requests to be mediated, but more libraries will have scenarios with special collections where some things are mediated and some aren't. E.g., a collection being used by an undergraduate class probably gets prepped and prepared for the semester and stays onsite and they maybe train the students in the class how to handle materials and at that point the class can just do what they need to do, without librarians interjecting themselves in the process.


 Comments   
Comment by Erin Nettifee [ 14/Feb/23 ]

Stephanie Buck this is an explicit use case for the expansion of "Needed for" and "Process" over in item state. I'm interested in what is being talked about for this feature in terms of requirements. I think there are other use cases for mediation besides "Needed for", especially for libraries with small collections that maybe aren't special but have a need for mediation regardless...

Comment by Stephanie Buck [ 14/Feb/23 ]

Thanks, Erin Nettifee. Is there a specific Jira I should look at for these use cases?

Comment by Mark Canney [ 15/Feb/23 ]

Some of our special collections requests need approval from staff who do not complete the fulfillment of the request. But we need to record the approval and then push to request to the staff who page, ship or provide room use access to the item.

Comment by Erin Nettifee [ 16/Feb/23 ]

Stephanie Buck the use cases for "needed for" are listed on UXPROD-1530 Draft , but there's not a ton of detail there. Glad to talk more after you have a chance to look at it.

Comment by Thomas Trutt [ 09/Mar/23 ]

I'd agree with Erin this does seem a logical extension of "needed for". This IMO is also a case for the workflow engine. We have several rare locations so based on the location being requested different staff would have to review the request. I also feel this would have to be part of the request policy, ie 'Requires Review' or 'Needs Approval'.

Generated at Fri Feb 09 00:36:58 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.