Loans (UXPROD-788)

[UXPROD-2244] Truncate due date based on patron expiration at CHECK OUT Created: 27/Jan/20  Updated: 15/Dec/21  Resolved: 08/Jun/21

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: R2 2021
Parent: Loans

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

Issue links:
Cloners
is cloned by UXPROD-3065 Truncate due date based on patron exp... Closed
Defines
is defined by CIRC-1030 Truncate due date based on patron exp... Closed
is defined by CIRC-886 Truncate due date based on patron exp... Closed
Relates
relates to UXPROD-2746 Check Out: override patron blocks, ex... Closed
Epic Link: Loans
Front-End Confidence factor: High
Back End Estimate: Large < 10 days
Back End Estimator: Alexander Kurash
Development Team: Vega
PO Rank: 130
PO Ranking Note: Was ranked go-live by round II implementers. Wanted by summer 2021 implementers, Increased rank from 107
Cap Plan Fix Version (DO NOT CHANGE): R2 2021
Rank: Chicago (MVP Sum 2020): R2
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R1
Rank: FLO (MVP Sum 2020): R1
Rank: GBV (MVP Sum 2020): R2
Rank: Grand Valley (Full Sum 2021): R1
Rank: hbz (TBD): R2
Rank: MI State-Lib of MI (Sum 2021): R2
Rank: MO State (MVP June 2020): R2
Rank: U of AL (MVP Oct 2020): R2

 Description   

SPLIT - see UXPROD-3065 Closed .

Current situation or problem:

  • Loans and renewals do not respect patron expiration date - items can be due after a patron expires
  • Renewals will succeed for inactive/expired users

In scope

  • If a user's expiration date is before the calculated due date for the loan, truncate the loan due date to the patron expiration date, while respecting closed library due date management
  • a renewal that would extend the due date past the patron's expiration date should be truncated to the patron's expiration date
  • fail renewals for inactive users (checking out items already fails for inactive users)
  • Allow for overrides if renewal or check out fails because of inactive/expired user

Out of scope

Use case(s)

Proposed solution/stories

Links to additional info

Questions



 Comments   
Comment by Brooks Travis [ 29/Jan/20 ]

What are the odds this might be resolved in Q1 or Q2 2020?

Comment by Kelly Drake [ 13/Feb/20 ]

Brooks Travis There doesn't seem to be much chance of this getting into q1 or q2 as there aren't any assigned resources. We're looking into a possible workaround using the calendar? (but since we currently can't save additional calendars....)

Comment by Cate Boerema (Inactive) [ 05/May/20 ]

Emma Boettcher can you please have this feature estimated? It might make sense to ping some folks from Vega as I think they would likely do the development.

FYI Darcy Branchini

Comment by Emma Boettcher [ 07/May/20 ]

Alexander Kurash would you be able to estimate this feature? Let me know if you have any questions.

cc: Darcy Branchini

Comment by Charlotte Whitt [ 27/May/20 ]

Hi Emma Boettcher and Darcy Branchini - this is a Go live feature for both FLO and for MSU.
Do we know when we might be able to have this feature in. I see it has been BE estimated as: Large < 10 days, but no Fix Version yet.

CC: Kelly Drake

Comment by Darcy Branchini [ 04/Jun/20 ]

Charlotte Whitt, unfortunately, this doesn't have a fix version on it and it was not pulled into Q2. We're hard at work finishing features that were Q2 now so we wouldn't be able to pull this in now. I'll have to lean on Emma Boettcher regarding whether or not this gets prioritized for Q3 and Vega assigned the development work as part of capacity planning for Q3.

Comment by Brooks Travis [ 12/Jun/20 ]

As we're already live, and we don't yet have this, I feel comfortable updating it to be "can wait up to a quarter". If I had an option for 2qtrs, I'd choose that, but 1yr is too long. I have ideas for workarounds, but they're not pleasant from a UX perspective.

Comment by Darcy Branchini [ 27/Aug/20 ]

Emma groomed this with Vega on 8/25. Vega will point the stories and decide if FE stories are needed to support a failed renewal for an expired/inactive user ( CIRC-887 Closed ). Emma Boettcher will add closed library management handling to stories for truncated due date ( CIRC-888 Closed and CIRC-886 Closed ). Also, Emma Boettcher, do we need a similar story and set of scenarios to CIRC-887 Closed for a failed check out? Is that what UICHKOUT-645 Open is?

cc: Alexander Kurash Tetyana Afanasyeva

Comment by Emma Boettcher [ 27/Aug/20 ]

Darcy Branchini No, check out already fails if you check out to an inactive user. But the SIG did say today that they wanted to be able to override failed check outs/renewals that are failing because renewal was inactive, so I'll fill out those stories as well.

Comment by Darcy Branchini [ 27/Aug/20 ]

That's right re: check out! Thanks for the clarification Emma Boettcher and I did see the two stories you created for override. fyi, not sure if it'll be helpful, but for another feature, Holly has overrides broken out as an override where the current FOLIO user logged in has permission to override and an override where the current FOLIO user logged in does not have permission. See UXPROD-2127 Closed . We are looking at three possible solutions for a user without permission, defined in this spike - CIRC-882 Closed .

Comment by Holly Mistlebauer [ 26/Feb/21 ]

Darcy Branchini: Is this feature going to be a part of R2 2021 for Vega.  If not, should the CF take the feature back?

Comment by Darcy Branchini [ 30/Apr/21 ]

Cheryl Malmborg, this is at-risk for completing in R2. Also, there are stories that, in my opinion, should be split into a separate feature - mainly UICHKOUT-645 Open and UIU-1816 Open which are about override abilities. Also CIRC-887 Closed seems to either be a bug or could possibly be included in the feature above which could be more broadly titled, "Failure and overrides for..." or something to that effect. Even with that, there's still a chance that we won't complete CIRC-888 Closed .

Comment by Cheryl Malmborg [ 03/May/21 ]

Darcy Branchini I think CIRC-887 Closed should be separate from this feature. It seems like a bug. To me it has a higher priority than truncating the due date. Renewals are often done self-service through a discovery tool.

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