Requests (UXPROD-790)

[UXPROD-3981] TLR: Circulation rules on items to be followed by title level request holds Created: 24/Jan/23  Updated: 08/Feb/24  Resolved: 09/Oct/23

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Poppy (R2 2023)
Parent: Requests

Type: New Feature Priority: P2
Reporter: Stephanie Buck Assignee: Stephanie Buck
Resolution: Done Votes: 1
Labels: LC-priority2, loc, resourceaccess, was-quesnelia-now-poppy
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by CIRC-1883 Allow title level holds on instances ... Closed
is defined by CIRC-1819 TLR Hold should follow circulation rules Closed
is defined by FAT-6946 Karate tests for CIRC-1819 Closed
is defined by FAT-6950 Karate tests for CIRC-1831 Closed
is defined by UICIRC-949 TLR: New setting to enable hold reque... Closed
is defined by UIREQ-960 TLRs check circulation rules before r... Closed
Relates
relates to UXPROD-3980 TLR: disallow requesting for titles/i... Closed
relates to CIRC-1693 Item level circulation policies not b... Closed
Epic Link: Requests
Front End Estimate: Medium < 5 days
Front End Estimator: Stephanie Buck
Front-End Confidence factor: 90%
Back End Estimate: Large < 10 days
Back End Estimator: Alexander Kurash
Back-End Confidence factor: 90%
Development Team: Vega
PO Rank: 0
Rank: Cornell (Full Sum 2021): R1

 Description   

Current situation or problem: Title level (hold) requests do not always follow circulation rules set on items. (Page and recalls do check request policies because an item is immediately associated with those request types.)

In scope

Implementation of circ rules (either existing or new) to allow for prevention of title level requests if patron / material type / loan type / location is not eligible

Setting to make this option configurable

Out of scope

  • Policies already checked when an item is returned (bug linked below)

Use case(s) 

As a staff member I want to restrict what items can have a TLR placed on them. Examples:

  • We want to allow requests on monographs but not serials or thesis.
  • We do not want to allow TLR on items in specific locations; such as new book shelf or new and note worth, but still allow TLR on copies in the regular stacks.
  • We may not want to allow undergraduates, or resident cards to place TLR requests but allow all other User groups.
  • If an instance record has a mix of item types, some allowing TLR and some ILR, this should be recognized by the system. If a patron is allowed via the policy to place a TLR it should be allowed, but only include those items that are TLR eligible. 
  • If an item changes so that it is TLR eligible this should be recognized by outstanding TLRs for that instance record. 
  • A single FOLIO institution has several general collection libraries and one library that has special collections. The general collection libraries want to have title-level requesting; the library with special collections does not.

Proposed solution/stories

Items associated with a title (instance) should be checked each time a title level request is placed to make sure the patron and item combination are allowed. When they are not, the TLR will default to placing a hold, as they are always allowed.

Enabling an option to allow libraries to choose to either allow the default hold to be placed, or to send an error, when circulation rules prevent the request. 

Links to additional info

Questions{}

  1. Will this affect how requests are placed through discovery? Will those requests also follow circulation rules?

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