Hi Kathy,
I remember talking about long overdue status changing a few years ago
with some folks.
But basically, there exists a script for that action:
Open-ILS/src/support-scripts/long-overdue-status-update.pl
That script takes an argument for a specific period of time (or seems to
default to 180 days) to consider before marking it with a long overdue
status. I imagine it's not very smart about being applied only to a
particular library only or using varying lengths for different libs.
I vaguely recall talking about action/trigger based solutions for this,
but don't remember any of the details at this time. I'll keep digging
at my older communications and see if I can find something, though
someone else may already know more.
-- Ben
On 03/05/2013 12:06 PM, Kathy Lussier wrote:
Hi all,
We've been having some local discussions on issues related to billing,
overdue items, etc. in the hopes of sponsoring some enhancements for
billing in Evergreen. As part of these discussions, we've been talking
about identifying copies that are long overdue (not lost).
I've noticed in the staff client there are several places that refer
to "long overdue" items. It's referenced in the patron summary and in
the bottom pane of the patron's "Items Out" screen. However, as far as
I can tell, there is no built-in way to identify items that are "long
overdue." Since there are references to it in the staff client, I have
to assume that somebody out there is making a distinction among
overdue, long overdue and lost items. If you're using "long overdue,"
can you send along some information on how you're using it on your
system and what you needed to configure?
Thanks!
Kathy
--
Benjamin Shum
Open Source Software Coordinator
Bibliomation, Inc.
32 Crest Road
Middlebury, CT 06762
203-577-4070, ext. 113
