Bug 28593 - Add ability to charge lost fee when applying new lost status when resolving a claim
Summary: Add ability to charge lost fee when applying new lost status when resolving a...
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: master
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on: 28588
Blocks: 28595
  Show dependency treegraph
 
Reported: 2021-06-18 11:59 UTC by Andrew Fuerste-Henry
Modified: 2021-10-12 19:28 UTC (History)
4 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Fuerste-Henry 2021-06-18 11:59:14 UTC
Bug 28271 added the ability to apply a new lost status when resolving a claim. We should also add the ability to charge a replacement fee.

Many libraries do not charge a replacement fee when a claim is generated. If the item is not found within the time period allowed by library policy, then the item is assumed lost, the claim is resolved, and the item is set to lost. At that point, the library would like to charge the patron. As things stand, there is not a way to generate a lost fee tied to that issue_id. You'd have to either create a manual invoice or return the item, check it back out to the patron, and mark it lost again.
Comment 1 Tomás Cohen Arazi 2021-06-18 18:26:02 UTC
This should be done on top of bug 28588, for sure.
Comment 2 Tomás Cohen Arazi 2021-06-25 11:58:48 UTC
Andrew, how do you think this should work? From the user perspective? Should it be the replacement cost? Should it be added manually in the claim resolution modal?
Comment 3 Andrew Fuerste-Henry 2021-06-25 12:30:41 UTC
It should be the replacement fee (plus processing fee, if any).

We've got ClaimReturnedChargeFee with the options of do charge a fee, don't charge a fee, or give the choice to the user as they claim something. 

I'd like a parallel syspref for ClaimReturnedResolutionChargeFee with the options to charge, don't charge, or give the choice to the user as they resolve something. 

It should not ever create a *second* lost fee if the library is already charging at the point of Claim, and it should only charge at resolution if you're moving the item from Claims Returned to some other non-zero lost status. And the wording of the syspref should make that clear.

"When resolving a claim and setting an item to lost (charge a lost fee / don't charge a lost fee / ask if a lost fee should be charged). If a fee was already generated based on ClaimReturnedChargeFee, this preference will not generate an additional fee."