Bug 11852 - Allow staff to create pipelines of actions for items
Summary: Allow staff to create pipelines of actions for items
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-26 17:06 UTC by Christopher Brannon
Modified: 2022-12-06 02:32 UTC (History)
4 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Brannon 2014-02-26 17:06:03 UTC
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
Comment 1 David Cook 2022-12-06 02:30:13 UTC
I'm not sure I understand this 100% but it sounds like you'd want the ability to create your own pipeline.

Sample Pipeline:
1. Prompt user for input X
2. Perform Action A on input X
3. Perform Action B on input X
4. Perform Action C on input X

It's certainly an interesting idea...
Comment 2 David Cook 2022-12-06 02:30:52 UTC
Changing name from "Scripted processes" to "Allow staff to create pipelines of actions for items"
Comment 3 David Cook 2022-12-06 02:32:39 UTC
The background jobs functionality could be used for executing the pipeline. 

Alternatively someone could implement this as a plugin.

Regardless of implementation, I think you'd probably need to sponsor this development, as it would probably be too big for anyone to take on independently.