http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5872 --- Comment #1 from Chris Cormack <chris@bigballofwax.co.nz> 2011-03-16 00:09:43 UTC --- Circulation rules management : everything (issues, holds, fines) now at granular level All scripts = there are some (a few) reindenting changes. * C4/IssuintRules.pm script created : contains all circ rules related functions * C4/Circulation.pm - rewrite issuing rules according to new behaviour : default values applies as default, not as total. There is also an inheritance, meaning you don't have to define all rules - debarment management : debarred patrons now can have a limit date of debarment (for fine in days, but also for a limited debarrment) - lot of lines removes (now in IssuinRules.pm) - modifys the offline circ : works in conjunction with the Firefox plugin. All offline circ code is in another patch * C4/Overdues.pm - use IssuingRules.pm functions - deal with debarment up to a givendate * C4/Reserves.pm - deal with HoldRules at granular level. The library can now define rules for hold at ccode(itype) / branch / patron category level - added a pickupDelay * admin/smart-rules.pl - script rewritten - added ajax (smart-rules-service) to modify a cell directly * admin/branch_transfer_limits.pl - some variable renamed for more readability * circ/branchtransfers.pl - ModReserveAffect now deals with branches to check hold rules * circ/circulation.pl and circ/returns.pl - deals with debardate where applicable - deals with possible holds on a given item adapted to fit new hold rules - display borrower relatives issues (on circulation.pl only) * reserve/modrequest.pl, placerequest.pl, renewscript.pl and request.pl - deals with new granular-level hold rules * unit tests for Circulation.pm, GetMemberDetails.pm and Overdues.pm - deals with IssuingRules.pm package & API changes * opac-reserve.pl and opac-modrequest: - deals with holds at granular level -- 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.