Details
-
New Feature
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
None
-
Jumbo: > 45 days
-
Low
-
XXXL: 30-45 days
-
Vega
-
-
95
-
32
-
-
R1
-
R5
-
R4
-
R2
-
R4
-
R3
-
R4
-
R3
-
R2
-
R1
-
R3
-
R2
-
R2
-
R2
Description
When a patron is making a request, they often don't care what copy they get - they just want a copy of a given title. With FOLIO's basic title level requesting (TLR) functionality (see UXPROD-1061) patrons can request a title in discovery and business logic will convert the title request into a request on the item which is most likely to become available first.
Often, the item predicted to be returned first is not returned on time. When this happens, requests could be fulfilled out of order (a patron that requested later can receive their copy earlier). In institutions where course materials are requestable, this could become a customer service issue, as student could be made aware of this situation through discussions with classmates.
Title Level Requests (Complete) functionality would associate a request with an instance at the time the request is placed, and then only with an item at the time of fulfillment. This would solve the following problems:
1. Risk of fulfilling out of order (per above)
2. Need to rebalance item request queues when item goes missing or new copy becomes available*
3. Ability to request titles without items (using the note field)
Generally, TLRC will add:
- Tenant level configuration option to allow Title level requesting
- Title level requests via discovery and via the FOLIO UI
- Patron ability to see their place in a title level request queue
- A unified request queue (using existing item level basic logic)
- Ability to balance title level vs item level requests
- Ability to filter for and manage requests with the Open-Title level status
Non-functional Requirements
- Adequate logging to indicate success or failure of any TLR activities
- Schema migration scripts are created and tested
- Performance of all affected actions does not degrade by more than 1%
How Title Level Requests Should Work
- Provides a tenant level setting that allows a tenant to enable, or disable title level requesting
- Title Level Request Creation: patron places a request via discovery by selecting “the first available copy” option, or a FOLIO user places a title request from the Instance record, or other avenues
- FOLIO processes work to create an item level request
- Using established tlr - lite functionality FOLIO determines if it is able to place an item level request right away
- If not Creates a title level request queue
- Creates a title level request, request status = “Open - title level”
- When an item is returned - using the existing request functionality, along with the priority of the request in the request queue- system determines if the item should fulfill a title level or item level request
- Move title level request to an item request
- FOLIO fulfills requests from the queue using a first in, first out logic. If two requests are placed at the same time FOLIO will randomly select the request that gets fulfilled first
- FOLIO users manage title level requests via the existing Request interface with the addition of a new “Title-level” Request status.
- Track and manage the request queue
- Follow the title level request process - until the request is resolved to an item level request (at which point it then continues on as any other request.
Important links
Mockups folder: https://drive.google.com/drive/u/1/folders/1ndvI2IIzp6avYbCu1B_YueoZVlGfeuOB
GDrive folder: https://drive.google.com/drive/u/1/folders/1ao5l4aKi-aNLlXwzT5CJ-UCXaba5tEKE
Vega documentation folder: https://drive.google.com/drive/u/0/folders/1R8mESODVM_Yt-Od8w6YCv2fe3YbI90R2
Groomings:
Notes:
- As of 9/10/21, title look-up (on the new Request form) is out of scope for the first implementation of this feature.
- As of 9/14/21 it is confirmed that Vega will integrate this work with Inventory only, NOT Inventory ES.
- All patrons can place title level requests regardless of whether they can be filled or not in the first implementation. Ideally in the second implementation we will find a way of controlling who can place TLR request, is excluding patron groups, working with existing circulation rules, extending circulation rules to work with instance data (patron, loan type, material type and location IDs in a list - see if a request can occur)
- Multivolume series requests will be investigated in the next implementation
TestRail: Results
Attachments
Issue Links
- is defined by
-
CIRC-1164
Spike: Title Level Requests - analyze existing implementation
-
- Closed
-
-
CIRC-1212
Spike: Title Level Requests - feature review and approach design
-
- Closed
-
-
CIRC-1290
Handling title level request notices (scheduled notices)
-
- Closed
-
-
CIRC-1295 SPIKE - Create BE tickets for TLR feature
-
- Closed
-
-
CIRC-1296
Consider title-level requests during checkin
-
- Closed
-
-
CIRC-1297
Consider title-level requests during checkout
-
- Closed
-
-
CIRC-1298
Consider title-level requests during request queue management
-
- Closed
-
-
CIRC-1337
Handling title level request notices (immediate notices)
-
- Closed
-
-
CIRC-1358
Link page TLR to the item on creation
-
- Closed
-
-
CIRC-1359
Link item to hold TLR when checked in
-
- Closed
-
-
CIRC-1360
Consider TLR when creating recall requests
-
- Closed
-
-
CIRC-1361
Consider TLR when validating new request against existing loans
-
- Closed
-
-
CIRC-1362
Consider TLR when changing loan due date
-
- Closed
-
-
CIRC-1375
TLR response does not contain instance data
-
- Closed
-
-
CIRC-1394 Publication data missing in Instance when call API circulation/requests?query=id
-
- Closed
-
-
CIRC-1395
TLR should be refused when instance/item already requested
-
- Closed
-
-
CIRC-1402
Extend requests returned by queue API with additional fields
-
- Closed
-
-
CIRC-1403
On check-in page TLR linked to an item should be updated, not first TLR in the queue
-
- Closed
-
-
CIRC-1411
Add positionOpenNotYetFilled field to the request JSON
-
- Closed
-
-
CIRC-1412
Requests should change position when they go in fulfilment on check-in
-
- Closed
-
-
CIRC-1421
During check-in only update fulfillable request if it's for the same item
-
- Closed
-
-
EDGPATRON-79
Support circulation interface v13
-
- Closed
-
-
MODINREACH-212
Support circulation interface v13
-
- Closed
-
-
MODINV-617
Support circulation interface v13
-
- Closed
-
-
MODNCIP-37
Support circulation interface v13
-
- Closed
-
-
MODORDERS-634
Support circulation interface v13
-
- Closed
-
-
MODPATRON-101
Support circulation interface v13
-
- Closed
-
-
MODRS-115
Support circulation interface v13
-
- Closed
-
-
SIP2-107
Support circulation interface v13
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
UICIRC-698
Create new setting for title level requests
-
- Closed
-
-
UICIRC-699
Title level request permission
-
- Closed
-
-
UICIRC-708
Title level request setting cannot be disabled when there is an active title level request in the system
-
- Closed
-
-
-
- Closed
-
-
UIIN-1619
Create request from Item record
-
- Closed
-
-
UIIN-1620
Create title level request from Instance record
-
- Closed
-
-
-
- Closed
-
-
UIIN-1881
Inventory action menu link View & reorder queue
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
UIREQ-612
Create new request filter
-
- Closed
-
-
UIREQ-613
Create updated request details pane
-
- Closed
-
-
UIREQ-614
Create updated request results page
-
- Closed
-
-
UIREQ-615
Action dropdown for title level request detail pane
-
- Closed
-
-
UIREQ-619
Create item level request from item record
-
- Closed
-
-
UIREQ-620
Update (new) request form
-
- Closed
-
-
UIREQ-630
View & reorder requests (first accordion)
-
- Closed
-
-
UIREQ-633
Unchecking the Title level request box when it is automatically checked
-
- Closed
-
-
UIREQ-635
Turn an item level request into a title level request
-
- Closed
-
-
-
- Closed
-
-
UIREQ-644
View & reorder requests (second accordion)
-
- Closed
-
-
UIREQ-647
SPIKE: investigate the way to create new setting for title level requests
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
UIREQ-655
Create a title level request checkbox
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
UIREQ-691
Hide "Actions dropdown" for "Request Detail" when all options disabled
-
- Closed
-
-
UIREQ-695
Migrate requests queue/reorder page on new end-points
-
- Closed
-
-
UIREQ-700
"Select item" modal should display all items in the Instance when user uncheck box
-
- Closed
-
-
UIREQ-701
Update "Request not allowed" modal for TLR
-
- Closed
-
-
UIREQ-702
Incorrect operation of the "Position in the queue" hyperlink
-
- Closed
-
-
UIREQ-704
User should see item barcode link when title request is in "Fulfillment in progress" or "Open - Not yet filled" accordions
-
- Closed
-
-
UIREQ-706
Disable validation on reordering for `Page` requests on UI side
-
- Closed
-
-
UIREQ-707
The text in the "Position in the queue" must be of the form (# (# of items) view requests in the queue "link")
-
- Closed
-
-
UIREQ-709
The user is redirected to the 'Request queue' where the request queue is not displayed
-
- Closed
-
-
UIREQ-713
Header and Subhead do not match the given form in Request queue page
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
UIU-2432
Create title level request from Users
-
- Closed
-
-
-
- Closed
-
-
UX-429
Title level requests: Title level request Detail display
-
- Closed
-
-
UX-430
Title level request: "Open - Title level" request status filter
-
- Closed
-
- is required by
-
CHAL-129
True title level requests
-
- Closed
-
- relates to
-
CIRC-1397
Disable request queue validation for page requests always being at the top
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Draft
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- requires
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-