[Koha-bugs] [Bug 28530] Allow configuration of floating limits by item type

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28530

Andrew Fuerste-Henry <andrewfh at dubcolib.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|Needs Signoff               |Failed QA

--- Comment #23 from Andrew Fuerste-Henry <andrewfh at dubcolib.org> ---
Note for testing: I confirmed that AutomaticItemReturn does control whether or
not one can decline the transfers initiated by this feature.

Issues:
 - Library float limits needs to be included in the admin nav sidebar
 - Allow value of zero -- currently, if you enter a zero it gets treated as a
blank and no limit is saved. As described on the screen, a blank should mean
float is not limited while a limit of zero would mean items of that type should
always transfer away
 - rename "limit" field as it causes errors in writing reports unless you refer
to the field with its full name (library_floating_limits.limit). Maybe
"item_limit"?

Transfer triggered for checkin that *meets* limit rather than exceeding it:
- have a float limit set to 1 for Branch A
- have 1 item of that item type at Branch A, giving ratio of 1
- check that item in at Branch A, get notified that this would put the library
over its limit and the item will be transferred

Ratio not correctly calculated for branches with zero items of type:
- Have defined float limits for Branches: A = 1, B = 10, C = 100
- Have 1 item of limited type at Branch A, 1 at Branch B, zero at Branch C
- Check 1 item in at Branch A
- Koha directs the item to transfer to Branch B (ratio of .1) rather than
Branch C (ratio of zero)
Seems like we're only calculating a ratio where there is at least 1 item
already.

-- 
You are receiving this mail because:
You are watching all bug changes.