[Koha-bugs] [Bug 8367] How long is a hold waiting for pickup at a more granular level
bugzilla-daemon at bugs.koha-community.org
bugzilla-daemon at bugs.koha-community.org
Tue Jun 18 10:30:05 CEST 2013
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367
Jonathan Druart <jonathan.druart at biblibre.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #15334|0 |1
is obsolete| |
Attachment #15335|0 |1
is obsolete| |
Attachment #15658|0 |1
is obsolete| |
Attachment #15659|0 |1
is obsolete| |
--- Comment #42 from Jonathan Druart <jonathan.druart at biblibre.com> ---
Created attachment 19093
-->
http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=19093&action=edit
Bug 8367: Add more granular level for ReservesMaxPickUpDelay
This patch adds:
- a new column in the issuing rules
- a new field issuingrules.holdspickupdelay
You can now specify a pickup delay for an hold function of a patron
category and/or a item type and/or a library.
To test:
Check there is no regression with a normal reserve workflow.
Add one or more issuingrules.
In 4 templates, you can see the max pickup delay for an hold
(circ/circulation.tt, circ/waitingreserves.tt, members/moremember.tt,
opac-user.tt).
Signed-off-by: Kyle M Hall <kyle at bywatersolutions.com>
Rebased on Feb 15, 2013 (Marcel de Rooy):
CONFLICT (content): Merge conflict in opac/opac-user.pl
CONFLICT (content): Merge conflict in
koha-tmpl/intranet-tmpl/prog/en/modules/circ/circulation.tt
CONFLICT (content): Merge conflict in installer/data/mysql/updatedatabase.pl
CONFLICT (content): Merge conflict in circ/waitingreserves.pl
--
You are receiving this mail because:
You are watching all bug changes.
More information about the Koha-bugs
mailing list