http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5533
--- Comment #9 from Ian Walls <[email protected]> 2011-09-13 13:08:25 UTC --- Srdjan, It seems to me that what needs to happen here is what Jared suggests: we need a single subroutine to handle all the logic of marking an item Lost. Input params: * lost value: which LOST auth values to use * charge: charge the patron the replacement cost? * markreturned: check in the material? The behaviour on the item tab and the behaviour in longoverdue.pl can then be synchronized. I'm still not convinced that the edit items screen needs to include this additional logic; it's the manual way to edit an item record, and should only be done by people who know what they're doing. Hiding 'Lost' in the MARC Framework would be an easy way to prevent folks from inadvertently making the changes without properly handling all the other logic. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
