Fees/Fines (UXPROD-792)

[UXPROD-3377] Loan: (FE) Lost Item Fees processing page for ACTUAL COST phase 1 Created: 20/Oct/21  Updated: 27/Mar/23  Resolved: 06/Oct/22

Status: Closed
Project: UX Product
Components: Fees/Fines
Affects versions: None
Fix versions: Nolana (R3 2022)
Parent: Fees/Fines

Type: New Feature Priority: TBD
Reporter: Holly Mistlebauer Assignee: Holly Mistlebauer
Resolution: Done Votes: 0
Labels: cap-mvp-split, feesfines, loans, needs-testrail, resourceaccess
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PDF File Lost items - Close loan (1).pdf    
Issue links:
Blocks
blocks UXPROD-2554 Loan: Declared lost - work for actual... Closed
Cloners
is cloned by UXPROD-3565 Loan: (BE) Lost Item Fees processing ... Closed
is cloned by UXPROD-3744 Loan: (FE) Lost Item Fees processing ... Closed
is cloned by UXPROD-3554 Loan: Lost Item Fees processing page ... In Refinement
Continues
is continued by UXPROD-3955 Update CIRC LOG to include LOST ITEMS... Draft
Defines
defines UXPROD-3079 Implement actual cost for lost items In Progress
is defined by UIU-1382 Lost items requiring ACTUAL COST: Gen... Closed
is defined by UIU-2491 Create permission for "Lost items req... Closed
is defined by UIU-2667 Implement 3 dot component Closed
is defined by UIU-1867 Lost items requiring ACTUAL COST: Imp... Closed
is defined by FAT-1483 Сheck test cases for validity and rel... Closed
is defined by FAT-1501 Refinement UXPROD-3377 Closed
is defined by UIU-2519 Spike: Investigate pagination problem... Closed
Duplicate
is duplicated by UXPROD-846 Fees/Fines in-app report: Lost items ... Closed
Gantt End to Start
has to be done before UXPROD-3573 Notify user when item(s) are charged ... Closed
has to be done before UXPROD-3554 Loan: Lost Item Fees processing page ... In Refinement
Relates
relates to UXPROD-501 Loan: Declared Lost Closed
relates to UXPROD-2246 Loan: Declared Lost - Fee/Fine work f... Closed
relates to UXPROD-2260 Loan: Declared Lost (Stories dependen... Closed
relates to UXPROD-2391 Loan: (BE) Declared Lost/Aged to Lost... Closed
relates to UXPROD-3564 Loan: (FE) Declared Lost/Aged to Lost... Closed
relates to UXPROD-2554 Loan: Declared lost - work for actual... Closed
relates to UXPROD-2572 Loan: Aged to Lost using ACTUAL COST Closed
Requires
requires UXPROD-2554 Loan: Declared lost - work for actual... Closed
Release: Nolana (R3 2022)
Epic Link: Fees/Fines
Front End Estimate: XL < 15 days
Front-End Confidence factor: 80%
Back End Estimate: Out of scope
Estimation Notes and Assumptions: Re-estimated by Vega 12/14/21

New back end developers are still getting used to working in the team (and FOLIO) and are all unfamiliar with this area. It could easily take much longer than 45 days.

If this work includes new APIs, then this estimate will likely need to grow in order to accommodate the expectation for API integration testing with Karate.
Development Team: Vega
Kiwi Planning Points (DO NOT CHANGE): 71
PO Rank: 96
Rank: Chicago (MVP Sum 2020): R5
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R2
Rank: 5Colleges (Full Jul 2021): R4
Rank: GBV (MVP Sum 2020): R5
Rank: Grand Valley (Full Sum 2021): R1
Rank: Lehigh (MVP Summer 2020): R3
Rank: MTSU: R2
Rank: MI State-Lib of MI (Sum 2021): R2
Rank: MO State (MVP June 2020): R1
Rank: U of AL (MVP Oct 2020): R4

 Description   

Split July 6, 2022 to enable inclusion in Nolana development.
Split February 15, 2022 to create FE and BE separate features

 

Split on October 20, 2021

Formerly  UXPROD-2391 Closed  included both the ACTUAL COST fee/fine work for items that are Declared Lost and the report that will be used to process the ACTUAL COST for both Declared Lost and Aged to Lost items. Holly split the processing report since it is for both Declared Lost and Aged to Lost items.  UXPROD-2391 Closed  now covers only the ACTUAL COST fee/fine work for items that are Declared Lost. UXPROD-3377 covers the processing report.

Redesigned on September 23, 2020

The redesign of the ACTUAL COST process has resulted in no longer needing the following user stories...
 * UIU-1593 (Declared lost item: Manual fee setting for ACTUAL COST fee/fine type)
 * MODFEE-51 (BE - Declared lost item: Manual fee setting for ACTUAL COST fee/fine type)
 * CIRC-727 BE - (Declared lost: renewal (effect on lost item fees) - SHARED ACTUAL COST)
 * CIRC-729 BE - (Declared lost item: check in (effect on fines/fees) - SHARED ACTUAL COST)
 
The following user stories will be kept, but have been renamed...
 * CIRC-728
 ** OLD: BE - Declared lost: renewal (effect on lost item fees) - FF OWNER ACTUAL COST
 ** NEW: BE - Declared lost: renewal (effect on lost item fees) - ACTUAL COST
 * CIRC-730
 ** OLD: BE - Declared lost item: check in (effect on fines/fees) - FF OWNER ACTUAL COST
 ** NEW: BE - Declared lost item: check in (effect on fines/fees) - ACTUAL COST\

Merged on July 20, 2020

UXPROD-846 Closed  (Fees/Fines in-app report: Lost items requiring actual cost) was merged with  UXPROD-2391 Closed  (Lost: Declared Lost - Fee/Fine work for ACTUAL COST) to create UXPROD-2046 ( UXPROD-2391 Closed  (Lost: Declared Lost - Fee/Fine work for ACTUAL COST). Note: This was done because of the constant misunderstanding that the report wasn't a high priority although it was part of the thin-thread workflow.

Split on April 22, 2020

UXPROD-2246 Loan: Declared Lost - Fee/Fine work was split into two features:
 # UXPROD-2246 Loan: Declared Lost - Fee/Fine work for SET COST (for Q2 2020)
 # UXPROD-2391 Loan: Declared Lost - Fee/Fine work for ACTUAL COST (for later in 2020 or Q1 2021){panel}
 
Update 2/11/22, clarifying questions:
 
UIU-1382 Closed
1. Could you please confirm that button "Lost items requiring actual costs" should be at the bottom of "Actions drop-down"?
 A: Yes, confirmed {color:#DE350B}Holly has updated Scenario 1 to indicate that the new option should be at the bottom and has attached a new mock-up to UIU-1382.{color}
2. Could you please confirm that we have "Lost Item Fees processing page for ACTUAL COST" and we don't have any report?
A: There is no report - it is a processing page {color:#DE350B}Holly has removed all references to "report" from the scenarios.{color}
 3. Could you please confirm that "2. Scenario" this is search rules for BE?
A: Already in the backend story, so it can be removed from FE story, BE story must be done first. {color:#DE350B}Holly has removed the scenario from the front-end story and has added a link to CIRC-940.{color}
 4. Can we move Scenario 6-7 to a separate story and discuss them separately (just for example: we have a patron name and a patron barcode and we need to know what field we need to use for sorting)?
A: Holly will move to separate story. Translate to other languages. Make sure scope is clear that sorted by database name, but not by local alphabetization {color:#DE350B}Holly has created a brief story ( CIRC-1440 Draft ) for this and will clarify it when it is scheduled to be worked on (in Nolana).{color}
 5. Could you please confirm that data selected red cannot be localized and all other data should be localized (localization.jpg)?
A: Yes, confirmed, though dates should be confirmed. Holly will add to this story. {color:#DE350B}Holly has added a note to this user story.{color}
 
UIU-1863 Closed
Holly will describe images within story scenarios.
 
1. Could you please confirm that "Actual cost to bill patron" greater or equal 0.00 and less or equal 9999.99 (3-charge-fee-modal.png)?
A: Confirmed, Holly will add to story {color:#DE350B}Holly has updated scenario 3 to reflect this requirement.{color}
2. Could you please confirm that we always should show 2 decimal places for "Actual cost to bill patron" (3-charge-fee-modal.png)?
Confirmed, Holly will add to story {color:#DE350B}Holly has updated scenario 1 to reflect this requirement.{color}
3. Could you please confirm that input "Actual cost to bill patron" should use full column width (3-charge-fee-modal.png)?
Confirmed, Holly will add to story {color:#DE350B}Holly has updated 3-charge-fee-modal.png to reflect the column width. {color}
4. Could you please describe what we need to show in "Error toast" (just for example 2 people can try "Charge" one item) (5-charge-fee-success.png)?
Holly will add to story {color:#DE350B}Holly has added a scenario for this situation to the user story.{color}
5. Could you please confirm that "Billed: <billed amount>" should be black and bold (5-charge-fee-success.png)?
Confirmed, Holly will add to story {color:#DE350B}Holly has updated 5-charge-fee-success.png to show Billed: 0.00 in bold black instead of bold blue.{color}
6. Could you please confirm that for modal 4-confirm-modal.png we should change text for button from "Charge fee" to "Billed" (4-confirm-modal.png)?
Holly will clarify and add to story {color:#DE350B}No, that isn't the change Holly made in the end. Holly changed the "Charge fee" button on 2-lost-items-requiring-actual-costs.png to "Process" and the "Charge fee" button on 4-confirm-modal.png to "Confirm & save". The "Charge fee" button on 3-charge-fee-modal.png will remain as "Charge fee". The updated mock-ups have been attached to the user story.{color}
 
UIU-2491 Closed
1. Could you please confirm that button "Lost items requiring actual costs" ( https://folio-org.atlassian.net/browse/UIU-1382 ) not visible when user don't have this permission?
A: Holly will add to story {color:#DE350B}Holly has added this note to the user story.{color}
2. Could you please confirm that we have "Lost Item Fees processing page for ACTUAL COST" and we don't have any report?
A: Holly will add to story {color:#DE350B}Holly has changed all references to "report" to "processing page".{color}
 
Pagination issue/story is missing. Pavel is working on a PoC. UIU-2519. Pavel recommends option 2, but is unsure of the time required to implement. Further investigation needed. This can be done for Nolana.
Solution 3, Load more...approach will be acceptable for Morning Glory. How many items should load at one time? 100. {color:#DE350B}Holly has created user story CIRC-1441 for pagination. It is in draft form until the approach is defined. {color}
 
Holly will come up with scenarios for karate tests - happy path scenarios. Performance needs to be defined as well. Holly will ask Users. Holly will also write test cases in test rails. {color:#DE350B}Holly has Karate tests, performance and Test Rail test cases on her list of things to do. {color}
 
Additional update 2/11/22, from Holly:
  * Holly was also asked to add one filter to the first release of this so that there is something in the left-hand column. {color:#DE350B}Holly will add "Loss type". Holly has added CIRC-942 and UIU-1867 to this story. {color}

  • Holly has realized that she needs to add a story for when aged to lost/declared lost items are returned or renewed. They should be removed from the list of items needing actual cost. {color:#DE350B}Holly has created one story for returned items and one story for renewed items. They are CIRC-1444 and CIRC-1445.{color}
Current situation or problem:
 
In scope
 
Out of scope
 
Use case(s)
 
Proposed solution/stories
 
Links to additional info
 
Questions


 Comments   
Comment by julie.bickle [ 01/Feb/22 ]

Hey Holly Mistlebauer, I’m wondering if there is any work to do, to make sure that notices continue being sent for actual cost
Will the feeCharge.type still be “Lost item fee”? Or will it be a different one? (I see from the mock-up on CIRC-942 "Lost item fee (actual cost)")

If it’s the same, then I assume there is no extra work to be done and will test the notices once this feature is ready to test.

If it’s different, then I will add a feature and stories to make sure that this new f/f type is considered for the notice policy trigger “Lost item fee(s) charged”.

Comment by Holly Mistlebauer [ 07/Feb/22 ]

julie.bickle: The fee/fine type will be “Lost item fee (actual cost)”, which is NOT the same as that for SET COST (“Lost item fee”). I know nothing about notices so I am not sure what work needs to be done. Sorry…

Comment by julie.bickle [ 08/Feb/22 ]

Holly Mistlebauer No worries - that's for me to figure out

Next question: Aged to lost set fee is automatically waived if the item is checked back in.
--> Will this be the same for the actual fee?

Comment by Holly Mistlebauer [ 14/Feb/22 ]

Stephanie Buck: I have added two new stories to this feature. They are CIRC-1444 Closed and CIRC-1445 Closed . Please let me know when I should meet with Vega for grooming. Thanks much...

Comment by Holly Mistlebauer [ 14/Feb/22 ]

julie.bickle: Just noticed that you asked about automatically waiving the fee when a lost item requiring ACTUAL COST is checked in. I had the same thought over the weekend, so I created CIRC-1444 Closed (for returned items) and CIRC-1445 Closed (for renewed items) this morning. Thanks much...

Comment by Holly Mistlebauer [ 14/Feb/22 ]

julie.bickle: Yes, "Lost item fee (actual cost)" will be cancelled/refunded if the lost item is returned/renewed, just like it is for "Lost item fee" (which is the Fee/Fine Type used for set cost). Please note that In both cases, if the date the item is returned/renewed is after the "No fees/fines shall be refunded if a lost item is returned more than <interval> late" (from the "Lost item fee policy", the "Lost item fee" and "Lost item fee (actual cost)" will NOT be cancelled/refunded.

Comment by Stephanie Buck [ 26/May/22 ]

This feature will begin in Nolana, but will not be complete until the BE work in https://folio-org.atlassian.net/browse/UXPROD-3565 is done. 

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