Fixed
Details
Assignee
Tim AugerTim AugerReporter
Casey HendersonCasey HendersonSprint
Priority
TBD
Details
Details
Assignee
Tim Auger
Tim AugerReporter
Casey Henderson
Casey HendersonSprint
Priority
Created February 28, 2025 at 5:53 PM
Updated March 28, 2025 at 7:07 PM
Resolved March 28, 2025 at 7:07 PM
Requirements
A library staff user must be authenticated to access the proxy request feature.
A library staff user authenticating against their own library system is not required.
Library staff users should remain authenticated for a session that lasts as long as an existing DCB Admin session.
Library staff users must identify the library of the patron being used to make a request. This is the equivalent to the “Affiliated institution” selector in Locate DCB.
Library staff users, when providing patron authentication credentials, will only authenticate against patron barcode.
Library staff users also want to be presented with the option to manually select an item or allow the system to automatically select an item based on resolution criteria.
Existing eligibility and blocks, circulatability and requestability workflows, behaviors and corresponding downstream functionality continues to be honored.
DCB needs to track proxy requests v. patron requests and available in the full display of a patron request.
Technical Flow
The user inputs a barcode and selects the library they want to make a staff request for ("affiliated institution")
We take the barcode and the agency code from the library and use it to do a patron lookup
The result of that lookup (and bib cluster ID from shared index record) is then used to provide the basis of the request to /place a patron request.
They then select a pickup location and choose either ‘automatic’ or ‘manual’ selection. If manual selection is chosen they must provide criteria (agency, item id etc)
They can also provide a requester note: we add to this note that this is a staff request
A success / error alert is shown, and if successful, we show a link to the request in DCB Admin