Requests (UXPROD-790)

[UXPROD-4119] Private requests (Congressional loans) Created: 10/Mar/23  Updated: 07/Feb/24

Status: In Progress
Project: UX Product
Components: None
Affects versions: None
Fix versions: Ramsons (R2 2024)
Parent: Requests

Type: New Feature Priority: P2
Reporter: Stephanie Buck Assignee: Stephanie Buck
Resolution: Unresolved Votes: 0
Labels: IC_review, LC-priority2, SolutionArchitecture, acs, at-risk, ecs, loc, requests, requires-discussion
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PDF File Attachment A - CL Workflowb234ebbd86f33a3fb1e473b31f94f484b89b689f642fe07318936ce31fc72433.pdf     Microsoft Word Life Cycle of a Congressional Requestcf625310bce8252cc87d44861bb4a802a695d3f491d56b6d7a99673a9cb102cd.docx    
Issue links:
Blocks
blocks UX-525 UX: Mediated requests app icon Closed
Continues
is continued by UXPROD-4595 Private requests (Congressional loans... Draft
Defines
is defined by CIRC-2000 Secure loan: Viewing secure patron da... Closed
is defined by MODAUD-179 Secure loan: Viewing secure patron da... Closed
is defined by UIU-3006 Secure loan: Viewing secure patron da... Closed
is defined by UICIRC-1030 New Circulation > Mediated requests s... Draft
is defined by UICHKIN-410 Secure loan: Viewing secure patron da... Draft
is defined by UIREQMED-13 Secure mediated requests: Indefinite ... Draft
Gantt End to End
has to be finished together with UXPROD-4559 ECS support: Title level requests (pa... In Progress
has to be finished together with UXPROD-4657 Mediated requests phase 1 (Base app./... In Progress
Relates
relates to UXPROD-4056 Requests: Rush requests Draft
relates to UXPROD-4062 Requests: Special collections mediate... Draft
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
Back-End Confidence factor: 20%
Development Team: Vega
PO Rank: 0
Rank: Cornell (Full Sum 2021): R4

 Description   

Current situation or problem:

The library needs a way to allow authorized library staff to request items as proxy for patrons who are members of designated groups (congressional loan patrons) that require anonymity and privacy with requests and loans. Only authorized staff should be able to access and view the patron's account information regarding requests and subsequent loans. Congressional loan patrons can place requests directly with authorized staff via phone, email, fax, etc., and they can also place requests via discovery or OPAC. This is mediated requests with extra security.

Congressional user data must only be visible to authorized library staff (web interface, apis, exports and all printed slips). Restriction of user data  must not impair  un-authorized library staff members ability to process and fulfill requests.

The original requester name and barcode should not appear in Requests, Loans, Users, Circulation log and any other circulation data. Only select staff can access original requester data.

A "waitlist" of requested items that are unavailable (item not on shelf, item on order, etc.) is required, which can be handled by current Requests functionality.

Library staff need to know when a secure patron has placed a request in the OPAC.

In scope

  • Maintain borrower/requester anonymity and privacy
  • Only authorized library staff must be able to create, edit, and view the patron's account information on requests, loans, user record and circulation data
  • Authorized staff determine which item should fulfill a request from a congressperson
  • Authorized staff can request items as proxy for patrons
  • Congressional loan patrons can place requests directly via discovery and OPAC, or by email, fax, phone to congressional loan staff
  • Retrieval staff cannot not see who gets the item (patron data); authorized staff/ Congressional loan staff can see patron data
  • Staff are able to respond to the request within one hour

Out of scope

  • A "waitlist" of requested items that are unavailable (see Use Case below) (covered by current Request functionality)
  • Ability to designate requests as a Rush (defined by UXPROD-4056 Draft )
  • Ability to mediate any type of request by item security level (gold, bronze, etc.), location, patron category (Congressional  patrons), condition, access restrictions, and preservation state (brittle, deacidified).  UXPROD-4062 Draft
  • Alternative check outs UXPROD-4398 
  • Ability to place requests for items not yet in inventory - this is currently possible by creating a stub item record and placing a request on that item record

Use case(s)

A Congressperson requests materials to aid research for a bill they are writing. What they request must be as secure and confidential as possible. 

A staff member from the White House requests materials on behalf of the Administration. What they request must be as secure and confidential as possible.

As a librarian filling secure requests, I want to make sure there are patron group(s) that will include the requesters in the secure request process. 

Waitlist Use Case

  • Congressional borrower requests via the OPAC an item not yet/never acquired by LC using the Cataloging in Process (CIP) record (for example: https://lccn.loc.gov/2023935453), which will be acquired in order to eventually fill the request, if possible.

Proposed solution/stories

Functionality within the new Mediated requests app that will support private requests and allow for the following:

  • Place secure, obfuscated requests
  • Fulfill secure requests
  • Approve or decline item for request fulfillment
  • Unmask requester for CMD charge desk staff
  • Barcode actions - trigger actions to move items through mediated request workflow 
  • Which actions trigger patron notices, pop up notices, and staff slips?
  • Appropriate permissions 
  • Congressional loan team
  • Approved CMD staff that charge and route item for final delivery
  • Retrieval staff requirements around privacy of patrons
  • Performance considerations

 

Links to additional info

https://ebscoinddev.atlassian.net/l/cp/Erc3U0Xh (This is an internal ebsco link; contact Steph Buck for more info)

Questions

 

 



 Comments   
Comment by Stephanie Buck [ 09/Oct/23 ]

Blocked as we work through workflows, architectural design, and timelines. 

Comment by Kimie Kester [ 15/Nov/23 ]

Hi Stephanie Buck I've started to add some very rough mocks here:
https://drive.google.com/drive/folders/1Jfx6fj2dl1EI7xqFcaVI766VLStm508E?usp=drive_link

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