http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12556 Bug ID: 12556 Summary: SelfCheck machine starts the hold instantly with an email sent out Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs@lists.koha-community.org Reporter: jonathan.field@ptfs-europe.com QA Contact: testopia@bugs.koha-community.org CC: colin.campbell@ptfs-europe.com Currently when a reserved book is returned on a SelfCheck machine the hold starts the hold instantly with an email sent out. It would be preferable if the hold started once it had been taken out of the SelfCheck bins and checked in by reservations staff at the counter. Current suggestion: Possible time delay on the message - may help if after 8 at night and 9 the following morning if delayed until following morning still a workaround if looked at account on OPAC they would see a hold e.g. so theoretically it could still be in the bin - it is difficult to find a correct time delay because of the number of variables - a bit more of a task to put in functionality change Possible Ideal Process: Requested item is returned via SelfService machine - for the patron the process remains the same (they are directed to put it in the RED slot) Instead of an email being sent immediately at that point to the patron next in line for the request, the item would have a new circulation status e.g. ‘In SelfService’ this removes the item from the patron’s record but does not trigger the next hold until it is checked-in by a member of the library, at which point the item moves onto the next circulation status that it would have had before going into ‘In SelfService’ (e.g. ‘On hold’ or ‘in transit’ etc.) There could be different variations of this process based on what is easiest to incorporate into Koha e.g. the item could possibly go into a transit status to a new Shelving Location or Branch - again ‘SelfService etc.’ - before returning to the correct next circulation status as described before - once it is checked-in. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.