The javascript solution won't work in your situation because you are forcing record level holds, not item level holds. So basically, the first holdable item checked in for a record for that patron is used to fill the patron's hold, but you don't want the patron to be able to select the pickup branch, instead you want the pickup branch to be set to item's holding branch at the time the item is trapped to fill that hold. This could definitely be done with modification to the holds code. Another much less elegent solution would be to add a trigger to your database so that when a hold is created or updated with an itemnumber, the pickup branch is set to the item's holding branch. You could then hide the pickup branch selector with css and/or javascript. I'm not sure how well this would work in practice, but it's certainly a possibility. That being said, getting the feature into the code seems like a far better solutions. Filing a bug report for this enhancement would be a good start. If you add the bug number to this thread and I can find some extra time I'll take a crack at it, but the sure-fire approach would be to hire a developer to add the feature. Kyle http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) Mill Run Technology Solutions ( http://millruntech.com ) On Tue, Oct 13, 2015 at 9:46 AM, Andreas Hedström Mace < Andreas.Hedstrom.Mace@sub.su.se> wrote:
Hi!
Thanks for your response Kyle. Some answers below:
We would like holds to work as follows:
· Holds should be limited to all items of a specific branch, not all items (of several branches) connected to the bibliographic record. Holds can only be placed when all items are checked out on a branch.
Have you ensured that your circulation rules are set to not allow holds for items for patrons from other branches? You write that any patron can place a hold at any library. This seems in conflict with this statement. Can you expand on the behavior you are trying to accomplish?
A patron should be able to place holds on libraries A, B or C. But if a hold is placed on the items connected to library A, it should not affect B and C (see more on that below)
· The pick-up location should always be the same as the books home library.
That is something you can accomplish with some custom Javascript. I can gin up the javascript and post it here if you'd like.
That would be very interesting of course! If you feel like posting it, that would be great thanks!
· A hold placed in one branch should not affect books on other branches.
Can you describe how this is affecting items at other branches?
What I mean is that: (1) returned books on other branches should not be marked as In Transit and sent to fill the hold and (2) checkouts on other branches should not be blocked.
Does anyone know if this set-up is possible with Koha today? Is anyone doing this, or anything similar? Or is some development needed?
It sounds like you need the functionality of this bug perhaps: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10993
That would solve some issues but not all. But it seems like some development is needed to be able to fulfill our needs. Hopefully these changes will make sense to the rest of the community too (and be optional, of course).
Best regards,
Andreas