Circ Rules and Loan Policies
(UXPROD-789)
|
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Circ Rules and Loan Policies |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Cate Boerema (Inactive) | Assignee: | Cheryl Malmborg |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | round_iv | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
| Epic Link: | Circ Rules and Loan Policies |
| Front End Estimate: | XL < 15 days |
| Front End Estimator: | Michal Kuklis |
| Front-End Confidence factor: | High |
| Back End Estimate: | Large < 10 days |
| Back End Estimator: | Julian Ladisch |
| Estimation Notes and Assumptions: | This story will require both front end and back end work. The backend will require a new validation endpoint which would return the applied/matched loan rule. From the front end perspective this looks like a sprint or two for the first raw version. |
| Development Team: | Vega |
| Kiwi Planning Points (DO NOT CHANGE): | 2 |
| PO Rank: | 75 |
| PO Ranking Note: | Increasing the ranking for this as I think it will be of greater benefit than many of the other features being reviewed. |
| Rank: Chalmers (Impl Aut 2019): | R4 |
| 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: FLO (MVP Sum 2020): | R4 |
| Rank: GBV (MVP Sum 2020): | R4 |
| Rank: Grand Valley (Full Sum 2021): | R3 |
| Rank: hbz (TBD): | R4 |
| Rank: Hungary (MVP End 2020): | R1 |
| Rank: Lehigh (MVP Summer 2020): | R2 |
| Rank: Leipzig (Full TBD): | R1 |
| Rank: MO State (MVP June 2020): | R1 |
| Rank: TAMU (MVP Jan 2021): | R1 |
| Rank: U of AL (MVP Oct 2020): | R2 |
| Description |
|
Ability to test loan rules by simulating checkout of an item to a patron and viewing which rule would apply, which were overwritten etc. https://discuss.folio.org/t/loan-rules-ux-iteration-4/834 |
| Comments |
| Comment by Michal Kuklis [ 18/Jun/18 ] |
|
Cate Boerema I think this will require both front end and back end work. The backend will require a new validation endpoint which would return the applied/matched loan rule. From the front end perspective this looks like a sprint or two for the first raw version. |
| Comment by Cate Boerema (Inactive) [ 19/Jun/18 ] |
|
Thanks Michal Kuklis! Can you please add your estimate in the Front End Estimate field (visible when you edit this feature) and also add your name as the Front End Estimator? You can also add any notes (such as the comment above) in the Estimation Assumptions field. |
| Comment by Michal Kuklis [ 19/Jun/18 ] |
|
Cate Boerema I just updated the Front End Estimate field. |
| Comment by Julian Ladisch [ 21/Jun/18 ] |
|
I increased the front-end estimate because "a sprint or two" is at least 14 days. The back-end api already exists: https://s3.amazonaws.com/foliodocs/api/mod-circulation/circulation.html#circulation_loan_rules_apply_all_get |
| Comment by md331 (Inactive) [ 15/Jan/21 ] |
|
Just to keep this current for anyone browsing, the refactoring process of mod-circulation split its API across interfaces so the backend API linked by Julian above is actually now at https://s3.amazonaws.com/foliodocs/api/mod-circulation/p/circulation-rules.html#circulation_rules_loan_policy_all_get |
| Comment by Erin Nettifee [ 22/Jun/22 ] |
|
I have a basic python script that uses the APIs Julian and Mark referenced to generate a test run of circ rules, that can be a workaround for this feature. It takes a CSV file with patron id, loan type id, material type id, and location id, and returns a new csv file that includes the applicable policies that would apply. It works on Lotus or above - there's a permission issue in Kiwi that prevents you from fetching the overdue and lost item policies. https://github.com/enettifee/folio-scripts/blob/main/resource-access/loan-tester.py |