Bug 13550 - Automatic processing status
Summary: Automatic processing status
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: 2015-01-09 21:43 UTC by Christopher Brannon
Modified: 2022-07-22 13:01 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 2015-01-09 21:43:20 UTC
It would be great if Koha had the ability to flag items based on criteria for automatic processing.  For example, lets say you have a collection that rotates libraries.  It would be great to have some way to flag that collection, and when criteria is met, and the item is checked in, it is put into a predetermined processing status and handed off rather than going back out on the shelves.

Perhaps new items have a short loan period, and after a certain length of time in the collection, it needs to be changed.  It could be flagged to either automatically change to a new loan period, or if it needs to be handled for processing (labels and such), it could be flagged for processing.

Perhaps you have items that need to be reset, or batteries to be replaced, either every time it comes in or on a set interval.  It could be flagged for processing.

It would also be beneficial to have reports on flagged items past due, for items that have not necessarily circed.

Christopher
Comment 1 Katrin Fischer 2020-01-06 13:58:35 UTC
(In reply to Christopher Brannon from comment #0)
> It would be great if Koha had the ability to flag items based on criteria
> for automatic processing.  For example, lets say you have a collection that
> rotates libraries.  It would be great to have some way to flag that
> collection, and when criteria is met, and the item is checked in, it is put
> into a predetermined processing status and handed off rather than going back
> out on the shelves.
> 
> Perhaps new items have a short loan period, and after a certain length of
> time in the collection, it needs to be changed.  It could be flagged to
> either automatically change to a new loan period, or if it needs to be
> handled for processing (labels and such), it could be flagged for processing.
> 
> Perhaps you have items that need to be reset, or batteries to be replaced,
> either every time it comes in or on a set interval.  It could be flagged for
> processing.
> 
> It would also be beneficial to have reports on flagged items past due, for
> items that have not necessarily circed.
> 
> Christopher

I think some of this can be solved using the Automatic item modifications by age tool and the UpdateItemLocationOnCheckin and UpdateNotForLoanStatusOnCheckin systempreferences. But as a whole it's a lot of different requirements that I think would be hard to put into one tool. What I got from the descriptions:

- flag new items after certain time (Automatic item modifications by age)
- flag items after a certain time period
- flag items on every return 

Some of that could maybe be achieved with reports. But I think the idea is more to have a flag that can be removed once processed?
Comment 2 Christopher Brannon 2020-06-26 20:55:42 UTC
I think, ultimately, what is needed is a way to make a list of items, where you can schedule a one time or reoccurring task.  Maybe even make use of the lists option (but you would need to be able to list a specific item).  The automatic item modifications is good, but to try and set a rule for every item you want to fall into this behavior would be an onerous task.  If there were a way to link a list of items (again items, not bibs) to one of these rules, that would be a HUGE improvement.

But it would also help if this tool could be triggered not just by age, but other counts, like number of issues, or by a certain date.

Does that make sense?
Comment 3 Katrin Fischer 2020-06-27 13:22:29 UTC
Yes, but not totally sure yet how it would be realized best. 

Maybe changing an enhancing the 'modifications by age' would be a way to go. There is already a bug that it should look for other critiera. Looking at a certain defined list of items, could be another thing.

Maybe we need a way to define lists of items like we can define lists for patrons and bibs first? That could also be used with batch tools.