Summary: | Add ability to charge lost fee when applying new lost status when resolving a claim | ||
---|---|---|---|
Product: | Koha | Reporter: | Andrew Fuerste-Henry <andrew> |
Component: | Circulation | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | azucena.aguayo, gmcharlt, jheltibridle, kyle.m.hall, tomascohen |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Bug Depends on: | 28588 | ||
Bug Blocks: | 28595 |
Description
Andrew Fuerste-Henry
2021-06-18 11:59:14 UTC
This should be done on top of bug 28588, for sure. 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? 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." |