Requests (UXPROD-790)

[UXPROD-1982] Title Level Requests - Light - evaluate request queue on item's check-in Created: 12/Aug/19  Updated: 04/Jan/22  Resolved: 04/Jan/22

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Requests

Type: New Feature Priority: P2
Reporter: Magda Zacharska Assignee: Unassigned
Resolution: Won't Do Votes: 1
Labels: TLR-Light-Phase-1, cf_candidate, requests
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PDF File Title Level Requests.pdf     PDF File UXPROD-1982(2).pdf     PDF File WolfCon_TRL_master.pdf    
Issue links:
Cloners
is cloned by UXPROD-2198 Provide an instance level count of ex... Closed
Defines
is defined by CIRC-641 Re-evaluate request queue on item ret... Closed
is defined by CIRC-675 Re-calculate instance queue position ... Closed
is defined by CIRC-676 Re-calculate request position from i... Closed
is defined by CIRC-673 Implement title-requesting-lite flag Closed
is defined by CIRC-674 Implement Item Level Request flag Closed
is defined by CIRCSTORE-296 Add parameter to enable/disable autom... Closed
is defined by UIREQ-421 Add Item Level Request checkbox to Ne... Closed
is defined by UIREQ-434 Add Item Level Request column to requ... Closed
is defined by UIREQ-435 Hide "Moving requests" and "Reorderin... Closed
Gantt End to Start
has to be done before UXPROD-2311 Title Level Requests-Light - enable m... Closed
Relates
relates to CHAL-191 See total number of requests on Insta... Blocked
relates to UXPROD-1061 Title-Level Requests (Basic) Closed
relates to UXPROD-1796 Title Level Requests Complete (part 1) Closed
Requires
is required by CHAL-129 True title level requests Closed
Epic Link: Requests
Front End Estimate: XL < 15 days
Front-End Confidence factor: Low
Back End Estimate: XXL < 30 days
Development Team: None
PO Rank: 0
Rank: Chalmers (Impl Aut 2019): R1
Rank: Chicago (MVP Sum 2020): R5
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R2
Rank: FLO (MVP Sum 2020): R2
Rank: GBV (MVP Sum 2020): R4
Rank: Grand Valley (Full Sum 2021): R4
Rank: Lehigh (MVP Summer 2020): R2
Rank: Linköping University (TBD): R1
Rank: MO State (MVP June 2020): R4
Rank: Spokane Public Library (Jan 2021): R2
Rank: U of AL (MVP Oct 2020): R4

 Description   

When the item is checked in we should check if there are any unfilled requests associated with other items within the same instance. If they are the existing request should be associated with the newly returned item.
For example, an instance has two copies, both of them are checked out.

  • itemA due 8/19/2019
  • itemB due 8/24/2019

When the title level request is created it is associated with the item that has the earliest due date, so in this scenario it would be associated with itemA
ItemB is returned on 8/17/2019 and the requests is resigned from itemA to itemB The due date for the itemA is restored to its original date if there are no other requests pending.

Implementation of this feature will require tenant level flag that would enable/disable this functionality. Once enabled, manual queue manipulation (reordering and moving requests) will not be available to users. Enabling request reordering and moving requests while Title Level Requests - Light is enabled is a part of UXPROD-2311 Closed



 Comments   
Comment by Theodor Tolstoy (One-Group.se) [ 15/Aug/19 ]

Chalmers are curious about how this relates to the plan for "true" Title level holds/requests and the current solution.

Comment by Magda Zacharska [ 15/Aug/19 ]

If we decide to implement this feature it would resolve the issue of fulfilling requests out of order (if the item with the later due date is returned earlier) but it will still require rebalancing the requests queues (it would happen automatically but is not trivial to implement) and it didn't resolve the issue of requesting the title without items.

Comment by Erin Nettifee [ 06/Sep/19 ]

This doesn't necessarily work for item level requests. There may be specific reasons that a particular item on a holding is wanted, and it shouldn't rebalance automatically.

It seems like you're describing what title-level requesting is meant to do, so maybe this is just in the wrong epic? If an institution hasn't turned on title-level requesting, this may not be desired behavior.

Comment by Magda Zacharska [ 06/Sep/19 ]

I agree Erin Nettifee that it is not desired behavior for the item level requests (thus my comment in the description). However, in FOLIO all requests are saved as an Item Level Request. In order to accommodated discovery layer that allow title level requests we added some logic in edge modules that translates the title level request into the item level request. Once the request is created in FOLIO we don't know anymore if the patron wanted a specific copy or not. If we implement functionality described in this JIRA we would need to add to FOLIO requests a flag that specifies if the request is Item or Title Level Request to prevent fulfilling request by a different copy when a specific copy was requested.

Comment by Cate Boerema (Inactive) [ 26/Mar/20 ]

Just marking blocked, as we are awaiting a technical design from Marc Johnson

Comment by Marie Widigson [ 22/Sep/20 ]

Hi Cate Boerema, Marc Johnson & Magda Zacharska, I wonder how this is proceeding? The lack of title level requests is affecting daily work and relations to end users and we would very much appreciate a way to solve it while waiting for true title level requests.

Comment by Marc Johnson [ 22/Sep/20 ]

Marie Widigson

I wonder how this is proceeding?

I don't know, I haven't recently been involved in this work.

Comment by Cate Boerema (Inactive) [ 09/Oct/20 ]

Hi Marie Widigson. This feature has been backburnered due to other priorities.

On a side note, I'm not sure if you noticed already, but View Item Requests on Instance Record ( UXPROD-1802 Closed ) is now targeted for Honeysuckle release.

Comment by Charlotte Whitt [ 22/Mar/21 ]

Hi Kelly Drake - it this your work too, or is this Magda Zacharska?

Comment by Magda Zacharska [ 04/Jan/22 ]

Full TLR will be implemented in scope of UXPROD-1796 Closed

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