Circ Rules and Loan Policies (UXPROD-789)

[UXPROD-1217] Extending Loan Rules Editor to target additional policy types Created: 28/Sep/18  Updated: 16/Sep/20  Resolved: 11/Mar/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q1 2019
Parent: Circ Rules and Loan Policies

Type: New Feature Priority: P2
Reporter: sthomas (Inactive) Assignee: Owen Stephens
Resolution: Done Votes: 0
Labels: Q42018-at-risk, feesfines, loan_rules_policies, loans, notices, requests
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks UXPROD-69 Request policies (CRUD and Impact on ... Closed
Defines
is defined by CIRC-187 Back end work for UICIRC-164 and UICI... Closed
is defined by CIRC-196 Back end work for UICIRC-164 and UICI... Closed
is defined by CIRC-197 Back end work for UICIRC-164 and UICI... Closed
is defined by UICIRC-164 Circ Rules Editor - Add new policy ty... Closed
is defined by UICIRC-165 Circ Rules Editor - Add new policy ty... Closed
is defined by UICIRC-341 Circ Rules Editor - Add lost item fee... Closed
Relates
relates to UXPROD-1857 Fee/fine Policies for Lost Item Fees Closed
relates to UXPROD-69 Request policies (CRUD and Impact on ... Closed
relates to UXPROD-676 CRUD Patron Notice Policies - Loan-re... Closed
relates to UXPROD-96 Fee/fine Policies for Overdue Items Closed
relates to UXPROD-1061 Title-Level Requests (Basic) Closed
relates to CIRC-495 Backend for circ rules editor: add ov... Closed
relates to UXPROD-1809 Title-Level Requests (Basic) - bug fi... Closed
relates to UICIRC-353 Circ rules editor: add overdue fine p... Closed
relates to UICIRC-352 Circ Rules Editor - Add new loan limi... Draft
Epic Link: Circ Rules and Loan Policies
Front End Estimate: Large < 10 days
Front End Estimator: Kostyantyn Khodarev
Front-End Confidence factor: Medium
Back End Estimate: XL < 15 days
Back End Estimator: Kostyantyn Khodarev
Estimation Notes and Assumptions: Assuming the simple way: A rule in the rules editor has a policy that consists of subpoliciess for loan, fee/fines, requests and notices.

Old estimates from Core: 5/5 (Julian and Michal)
Development Team: Prokopovych
Rank: Chalmers (Impl Aut 2019): R1
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R1
Rank: GBV (MVP Sum 2020): R1
Rank: Lehigh (MVP Summer 2020): R1
Rank: MO State (MVP June 2020): R1
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R1

 Description   

Description: While support for Loan Policies exists in the Loan Rules Editor, staff users need support for additional policy types to fulfill requirements for circulation of resources to patrons. The Loan Rules Editor should be functionally extended to fully support the inclusion of additional policy types.

Example policies include:
Fee/fine policies ( UXPROD-96 Closed ) (ST: Note, fee/fine policies were out of scope for Q1-2019 development)
Request policies ( UXPROD-69 Closed )
Patron Notice policies ( UXPROD-676 Closed )



 Comments   
Comment by sthomas (Inactive) [ 28/Sep/18 ]

Marc Johnson and Julian Ladisch - can you provide a back-end estimate for this for Q4 planning?
Michal Kuklis - can you provide a front-end estimate for this for Q4 planning?

Comment by Julian Ladisch [ 29/Sep/18 ]

The most simple way to implement this is renaming the "loan rules editor" to a "rules editor" (or "circulation rules editor"?) where you can define a "policy" (or "circulation policy"?). Such a "policy" consists of four sections (= four subpolicies): The loan policy (for how long can I loan the item?), the fee/fine policy, the request policy, and the patron notice policy.

On ux.folio.org there is a policy editor with two sections: loan policy section and (empty) request policy section.

This simple way does not require any change in the rules editor (only renaming).
Some work is needed for extending the policy editor and CRUD for the data of the new sections.

A more complicated way is a rules editor where each rule picks a loan policy, a fee/fine policy, a request policy, and a patron notice policy. I doubt that this complicated way is needed.

Comment by Cate Boerema (Inactive) [ 08/Oct/18 ]

I'm marking this as needed by Chalmers to go live, as it's needed to make Patron notices and Requests function

Comment by Cate Boerema (Inactive) [ 08/Oct/18 ]

In fact, I am marking this as needed for go-live by all early implementers because all early implementers said they needed UXPROD-676 Closed (Setup/configure patron notice logic) for go live.

Comment by Cate Boerema (Inactive) [ 10/Oct/18 ]

Hey sthomas. Did you intentionally remove the Q4 2018 fix version from this one?

Comment by Cate Boerema (Inactive) [ 05/Dec/18 ]

Hi sthomas. Moved this from Q4 2018 to Q1 2019 per our convo. Can you please add a comment on this to the Weekly Status Report? Thanks much!

Comment by Cate Boerema (Inactive) [ 04/Jan/19 ]

Per meeting on January 4th with Jakub, Kostya etc, we would like to reassign this to the Core team. I am making the change here, but we will need to run this through the capacity plan again to ensure there is bandwidth.

Comment by sthomas (Inactive) [ 11/Mar/19 ]

All stories as part of this feature for Q1 are complete. Moving to done.

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