Requests (UXPROD-790)

[UXPROD-1796] Title Level Requests Complete (part 1) Created: 24/Jun/19  Updated: 03/Apr/23  Resolved: 31/Jan/22

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Lotus (R1 2022)
Parent: Requests

Type: New Feature Priority: P2
Reporter: Cate Boerema (Inactive) Assignee: Stephanie Buck
Resolution: Done Votes: 1
Labels: TLR-Complete, resourceaccess
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File screenshot-1.png    
Issue links:
Defines
is defined by UIREQ-700 "Select item" modal should display al... Closed
is defined by UIREQ-702 Incorrect operation of the "Position ... Closed
is defined by UIREQ-704 User should see item barcode link w... Closed
is defined by UIREQ-730 Should to add link for "Requests on i... Closed
is defined by CIRC-1164 Spike: Title Level Requests - analyze... Closed
is defined by CIRC-1212 Spike: Title Level Requests - feature... Closed
is defined by UICIRC-708 Title level request setting cannot be... Closed
is defined by CIRC-1290 Handling title level request notices ... Closed
is defined by CIRC-1295 SPIKE - Create BE tickets for TLR fea... Closed
is defined by CIRC-1296 Consider title-level requests during ... Closed
is defined by CIRC-1297 Consider title-level requests during ... Closed
is defined by CIRC-1298 Consider title-level requests during ... Closed
is defined by CIRC-1337 Handling title level request notices ... Closed
is defined by CIRC-1358 Link page TLR to the item on creation Closed
is defined by CIRC-1359 Link item to hold TLR when checked in Closed
is defined by CIRC-1360 Consider TLR when creating recall req... Closed
is defined by CIRC-1361 Consider TLR when validating new requ... Closed
is defined by CIRC-1362 Consider TLR when changing loan due date Closed
is defined by CIRC-1375 TLR response does not contain instanc... Closed
is defined by CIRC-1394 Publication data missing in Instance ... Closed
is defined by CIRC-1395 TLR should be refused when instance/i... Closed
is defined by CIRC-1402 Extend requests returned by queue API... Closed
is defined by CIRC-1403 On check-in page TLR linked to an ite... Closed
is defined by CIRC-1411 Add positionOpenNotYetFilled field to... Closed
is defined by CIRC-1412 Requests should change position when ... Closed
is defined by CIRC-1421 During check-in only update fulfillab... Closed
is defined by EDGPATRON-79 Support circulation interface v13 Closed
is defined by MODINREACH-212 Support circulation interface v13 Closed
is defined by MODINV-617 Support circulation interface v13 Closed
is defined by MODNCIP-37 Support circulation interface v13 Closed
is defined by MODORDERS-634 Support circulation interface v13 Closed
is defined by MODPATRON-101 Support circulation interface v13 Closed
is defined by MODRS-115 Support circulation interface v13 Closed
is defined by SIP2-107 Support circulation interface v13 Closed
is defined by UICHKIN-319 TLR. Update okapiInterfaces to versi... Closed
is defined by UICHKOUT-760 TLR. Update okapiInterfaces to versio... Closed
is defined by UICIRC-698 Create new setting for title level re... Closed
is defined by UICIRC-699 Title level request permission Closed
is defined by UICIRC-732 TLR. Update okapiInterfaces to versio... Closed
is defined by UIIN-1619 Create request from Item record Closed
is defined by UIIN-1620 Create title level request from Insta... Closed
is defined by UIIN-1871 TLR. Update okapiInterfaces to versio... Closed
is defined by UIIN-1881 Inventory action menu link View & reo... Closed
is defined by UIIN-1901 TLR. Merge feature branch for TLR Closed
is defined by UIPCIR-31 TLR. Update okapiInterfaces to versio... Closed
is defined by UIREC-195 TLR. Update okapiInterfaces to versio... Closed
is defined by UIREQ-612 Create new request filter Closed
is defined by UIREQ-613 Create updated request details pane Closed
is defined by UIREQ-614 Create updated request results page Closed
is defined by UIREQ-615 Action dropdown for title level requ... Closed
is defined by UIREQ-619 Create item level request from item r... Closed
is defined by UIREQ-620 Update (new) request form Closed
is defined by UIREQ-630 View & reorder requests (first accord... Closed
is defined by UIREQ-633 Unchecking the Title level request bo... Closed
is defined by UIREQ-635 Turn an item level request into a tit... Closed
is defined by UIREQ-636 Spike: Title Level Requests - feature... Closed
is defined by UIREQ-644 View & reorder requests (second acco... Closed
is defined by UIREQ-647 SPIKE: investigate the way to create ... Closed
is defined by UIREQ-651 Spike: investigate possible for reuse... Closed
is defined by UIREQ-654 Create reusable component Closed
is defined by UIREQ-655 Create a title level request checkbox Closed
is defined by UIREQ-656 Spike: Create a title level request c... Closed
is defined by UIREQ-657 Spike: Create a title level request c... Closed
is defined by UIREQ-660 Move reusable part of "move request d... Closed
is defined by UIREQ-667 Spike: Investigate what TLR functiona... Closed
is defined by UIREQ-689 TLR. Merge feature branch for TLR Closed
is defined by UIREQ-691 Hide "Actions dropdown" for "Request ... Closed
is defined by UIREQ-695 Migrate requests queue/reorder page o... Closed
is defined by UIREQ-701 Update "Request not allowed" modal ... Closed
is defined by UIREQ-706 Disable validation on reordering for ... Closed
is defined by UIREQ-707 The text in the "Position in the queu... Closed
is defined by UIREQ-709 The user is redirected to the 'Reques... Closed
is defined by UIREQ-713 Header and Subhead do not match the g... Closed
is defined by UIREQ-715 Make translation keys more specific Closed
is defined by UIREQ-717 TLR. Update okapiInterfaces to versio... Closed
is defined by UIU-2432 Create title level request from Users Closed
is defined by UIU-2483 TLR. Update okapiInterfaces to versio... Closed
is defined by UX-429 Title level requests: Title level req... Closed
is defined by UX-430 Title level request: "Open - Title le... Closed
Relates
relates to MODPATRON-104 Requests placed via mod-patron using ... Closed
relates to UXPROD-1982 Title Level Requests - Light - evalua... Closed
relates to UXPROD-3402 Title look-up for Requests (title lev... Closed
relates to UXPROD-2198 Provide an instance level count of ex... Closed
relates to UXPROD-2311 Title Level Requests-Light - enable m... Closed
relates to CIRC-1397 Disable request queue validation for ... Closed
relates to UXPROD-3528 Requests: expanded permissioning Draft
relates to UXPROD-1061 Title-Level Requests (Basic) Closed
relates to UXPROD-1809 Title-Level Requests (Basic) - bug fi... Closed
relates to UXPROD-1810 Item-Level Requests - discovery servi... Closed
Requires
requires UXPROD-3305 Requests drag & drop keyboard functio... Closed
requires UXPROD-3330 Data migration required by title leve... Closed
requires UXPROD-3392 Title Level Requests Complete (part 2) Closed
is required by CHAL-129 True title level requests Closed
Epic Link: Requests
Front End Estimate: Jumbo: > 45 days
Front-End Confidence factor: Low
Back End Estimate: XXXL: 30-45 days
Development Team: Vega
Kiwi Planning Points (DO NOT CHANGE): 95
PO Rank: 32
PO Ranking Note: 2020-10-04 - CB: Making my PO rank same as the calculated total rank for now.
2019-07-12: Keeping PO rank same as calculated rank (with potential minor adjustments to avoid having two features with same rank)
Rank: Chalmers (Impl Aut 2019): R1
Rank: Chicago (MVP Sum 2020): R5
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R2
Rank: 5Colleges (Full Jul 2021): R4
Rank: FLO (MVP Sum 2020): R3
Rank: GBV (MVP Sum 2020): R4
Rank: Grand Valley (Full Sum 2021): R3
Rank: Lehigh (MVP Summer 2020): R2
Rank: Linköping University (TBD): R1
Rank: MO State (MVP June 2020): R3
Rank: Spokane Public Library (Jan 2021): R2
Rank: TAMU (MVP Jan 2021): R2
Rank: U of AL (MVP Oct 2020): 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 Closed ) 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 


 Comments   
Comment by Siska [ 31/Oct/19 ]

What is happening with this issue?

Comment by Eva Sejmyr [ 26/Apr/21 ]

This is crucial for us. Most of our loans are done via requests. We have several copies of the titles that are popular and if a patron wants to loan them, they usually have no other option than to make a request. We want things to be as easy and fair as possible for our patrons and without title level requests, there will be an added layer of difficulty for our patrons since they must learn which copy is best to request and “their” copy might not get returned by another patron. When all copies are checked out, the first returned copy should go to the patron who made a request first. The same applies when a newly ordered copy becomes available, we want it to go to the patron who is first in line, not whoever makes a request for that specific copy.

Requests are integral to our library and with the quantities we handle having to adjust reservation queues manually is not doable. As we understand it some libraries have different solutions (scripts, manual adjusting, etc.) to issues that occurs due to the lack of title level requests, but they seem like band aids instead of a solution to the core issue.

Comment by Tim Darlington [ 22/Oct/21 ]

Also crucial for Massey University (New Zealand). We have multiple campuses and are a distance education provider, which means a lot of multiple copies and a lot of requesting. Distance students can only use our collection by requesting and having us deliver the books to them. As part of our Covid-19 response, we've extended that courier delivery service to any patron who requests delivery. 

These things mean that title-level requesting with automated queuing is important to us, and that inclusion of the ability for patrons to request delivery is also important to us. Please make sure that patron-selected fulfillment preference is included in any functionality for requesting by instance.

Comment by Erin Nettifee [ 22/Oct/21 ]

Hi Tim Darlington. Not sure if you have anyone who is planning to engage in Slack - there is an active RA SIG (#resource-access) as well as a separate group discussing title-level requesting in its own channel. Given the timezone difference, Slack might be the easiest way to engage, and so I'd encourage you to think about having someone join the discussions to learn more and to represent your institution's development needs. Please feel free to reach out to me or to Stephanie Buck to learn more.

Comment by Tim Darlington [ 25/Oct/21 ]

Thanks Erin Nettifee, have joined Slack and found the channels.

Comment by Lisa Sjögren [ 12/Jan/22 ]

Hi! I was trying to understand the status of this and noticed that this ticket is "In Progress" but also has resolution "Won't Do". What does this mean?

Comment by Stephanie Buck [ 12/Jan/22 ]

Hi Lisa Sjögren. The "won't do" is a mistake. I accidentally closed this out rather than the feature created for spillover stories. This is still in progress and on track. 

Comment by Stephanie Buck [ 31/Jan/22 ]

Completed as defined.

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