Here is how we would like the check-in process to work in Koha on the SIP connection: 1) a WALKIN item type should never generate a hold slip (currently does) 2) a LOCALHOLD type should only generate a hold slip if there is an unfilled hold for a local patron (currently does for any hold) 3) If a hold slip is generated for any valid circumstances... a) the item processed should be tied to the patron on the slip b) the item should be in the proper status (hold should be confirmed and put in transit if necessary) In summary, when a hold slip is generated we should be able to place the slip in the item and put it in the courier or on our hold shelf.
The SIP code just calls AddReturn, which in turn consults CheckReserves, which does not respect the holds policies configued in the Circulation and Fines Rules area.
Liz, can you tell if this is still valid for master?
I am a bit confused by this: print slip = set a hold waiting/triggering a hold? I suspect this has been fixed since, but it's hard to tell without more information.
There is not enough information here to make it possible to reproduce the problem.