[Koha-bugs] [Bug 11852] New: Scripted processes
bugzilla-daemon at bugs.koha-community.org
bugzilla-daemon at bugs.koha-community.org
Wed Feb 26 18:06:03 CET 2014
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11852
Bug ID: 11852
Summary: Scripted processes
Change sponsored?: ---
Product: Koha
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P5 - low
Component: Circulation
Assignee: koha-bugs at lists.koha-community.org
Reporter: cbrannon at cdalibrary.org
QA Contact: testopia at bugs.koha-community.org
CC: gmcharlt at gmail.com, kyle.m.hall at gmail.com
Here is a lofty wish...
I wish Koha could have the ability to have scripted processes.
For example. We don't have holds waiting automatically expire (meaning it
wasn't picked up, not to be confused with a patron set expiration on the
request), simply for the sake that we don't want available items on the hold
shelf unless it has been processed.
For us, this means, after 7 days waiting without being picked up, we pull the
item, we go into the patron account the item was waiting for and put a message
on the account that the item was not picked up. We then cancel the hold and
check the item in to trigger the next hold or transfer back to the home
library.
It would be a dream to be able to create link to a script that would do all of
this. For example, we would have a link in the Circulation menu to a script
called "Process expired holds". We then scan the item, and the script puts the
"Not picked up" message in the patron account, cancels the existing hold for
that patron, and checks the item in to trigger the next hold or transfer on
that item.
I could see this working if there were a way to pass on these tasks to Koha
like events. Maybe through URLs. I don't know. But, it would be wonderful in
streamlining processes.
Christopher
--
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.
More information about the Koha-bugs
mailing list