Loans (UXPROD-788)

[UXPROD-2016] Loans: renewal failures and overrides Created: 27/Aug/19  Updated: 03/May/21

Status: Analysis Complete
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Loans

Type: New Feature Priority: P3
Reporter: Emma Boettcher Assignee: Cheryl Malmborg
Resolution: Unresolved Votes: 0
Labels: round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by CIRC-612 Back end: override renewals with hold... Open
is defined by UIU-1785 Fail renewal when it does not extend ... Open
is defined by UIU-1879 Prevent users from selecting a due da... Open
is defined by UIU-1825 Allow override of failed renewal for ... Closed
is defined by UIU-1020 Front-end: Override renewals with hol... Blocked
Relates
relates to UXPROD-1847 Loans: Policy Overrides - override mu... Closed
Epic Link: Loans
Development Team: Vega
Kiwi Planning Points (DO NOT CHANGE): 1
PO Rank: 94.4
PO Ranking Note: Increased rank on this due to behavior when aged to lost - can be problematic if system calculates a due date that is in the past.
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R2
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R2
Rank: GBV (MVP Sum 2020): R4
Rank: Grand Valley (Full Sum 2021): R1
Rank: hbz (TBD): R2
Rank: Lehigh (MVP Summer 2020): R2
Rank: MI State-Lib of MI (Sum 2021): R2
Rank: MO State (MVP June 2020): R2
Rank: U of AL (MVP Oct 2020): R4

 Description   

Current situation or problem:
FOLIO does not allow for override of every renewal failure. Sometimes, it does not show all the reasons why a circ staff member would consider the user has failed (system may quit checking for reasons after it finds reason X, e.g.)

Known failures that do not have overrides:

  • allow override when the renewal fails because of a hold request
  • allow override when renewal fails b/c there is no calendar

Known condition that does not result in failure

  • fail renewals that do not extend the due date into future

In scope

  • Implement logic that will allow the user to tell when multiple characteristics of a loan prevent renewal (see additional information below)
  • Display these reasons in a way that prevents redundancy
  • Allow override for all renewal failures except if the item status claimed returned
  • Fail renewals that do not extend the due date into the future

Out of scope

  • fail renewal/allow override for a loan where the user is inactive- part of UXPROD-2244 Closed

Use case(s)

Proposed solution/stories

Links to additional info

  • Renewal failure reasons: https://docs.google.com/spreadsheets/d/1VURB4XjPl8q6oJFPPI6IO-SCFTHK7afa5GE0wa480uI/edit#gid=71672988
    • Some renewal failure reasons are redundant with each other (i.e., if a loan is not loanable, then it is is also not renewable) or cannot co-occur unless something's very goofy with the loan policy.
      • Spreadsheet is broken up into "failure categories", and each "failure category" has at least one column. You can get multiple things from one column (a renewal could fail for all reasons in that column), but can only select from one column in each category (because the columns are mutually exclusive). You can select from all five categories.
    • Some renewal failure reasons can co-occur. A renewal could fail with reasons from all of the categories listed on the spreadsheet - it would be unusual, but possible
    • Different renewal failures lead to different kinds of overrides. If a renewal fails for multiple reasons that have different kinds of overrides, a reason that does not allow an override (e.g., the item status claimed returned) "wins" over a reason that requires a date picker, and a reason that requires a date picker "wins" over a reason that can calculate the due date.

Questions

  • Does that spreadsheet cover all the renewal failure reasons? Is there a list of checks FOLIO is doing?
    • E.g., FOLIO will fail renewal if there is no calendar timetable, but that was never explicitly stated in JIRA - are there other checks like that?


 Comments   
Comment by Emma Boettcher [ 05/Jun/20 ]

Alexander Kurash since Vega has already pointed one of the stories for this feature, could you add frontend and backend estimates for this feature? Please let me know if you have any questions about it.

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