[OPEN-ILS-GENERAL] Long overdue items

[Mike Rylander]

Kathy and Elaine,

Elaine, I'd encourage you to send the original docs, and once the tech
specs are complete we'll share those as well.  Kathy, as for the specifics
of when to fine, in what manner and how much, and when and what to void or
unvoid at various events, that will be configurable via a set of YAOUS'.
The intent is for the PINES customization of which Elaine speaks to be
covered by configuration alone.

--miker



On Tue, Mar 5, 2013 at 3:12 PM, Kathy Lussier <klussier at masslnc.org> wrote:

> Hi Elaine,
>
> That's wonderful news!
>
> I would be interested in seeing the requirements doc. From your
> description, it sounds like you'll be covering a bulk of what we want to do
> with the long overdue process. We are looking for an option as to whether
> the long overdue process should bill for the item or not. We have a
> consortium that would like long overdue to generate blocks without
> necessarily billing for the time. But it sounds like you'll be creating a
> good foundation from which we can build.
>
> Thanks for sending along the information!
>
> Kathy
>
>
> Kathy Lussier
> Project Coordinator
> Massachusetts Library Network Cooperative
> (508) 343-0128
> klussier at masslnc.org
> Twitter: http://www.twitter.com/**kmlussier<http://www.twitter.com/kmlussier>
>
> On 3/5/2013 12:41 PM, Hardy, Elaine wrote:
>
>> Kathy,
>>
>> PINES does make a distinction between overdue, longoverdue and lost and
>> has just contracted with ESI for development of a Longoverdue process. In
>> PINES, overdue is anything under 180 days, lost are items patrons report
>> they have lost and Longoverdue is a set by the system when an item is 181
>> days overdue. The Longoverdue process we are developing with ESI is
>> similar to the current lost process. Basically, the system will set the
>> item to Longoverdue, void the overdue fines and add processing fees and
>> replacement costs to the patron record.  While containing some
>> customizations for  PINES policies, it will be developed as an option in
>> Evergreen. If you would like to see our requirements doc, I can send it
>> along
>>
>> Elaine
>>
>> ______________________________**__
>>
>>
>> J. Elaine Hardy
>> PINES Bibliographic Projects & Metadata Manager
>> Georgia Public Library Service
>> 1800 Century Place, Ste 150
>> Atlanta, Ga. 30345-4304
>>
>> 404.235-7128
>> 404.235-7201, fax
>> ehardy at georgialibraries.org
>> www.georgialibraries.org
>> www.georgialibraries.org/pines
>>
>>
>>
>>
>>
>> -----Original Message-----
>> From: open-ils-general-bounces at list.**georgialibraries.org<open-ils-general-bounces at list.georgialibraries.org>
>> [mailto:open-ils-general-**bounces at list.georgialibraries.**org<open-ils-general-bounces at list.georgialibraries.org>]
>> On Behalf Of
>> Kathy Lussier
>> Sent: Tuesday, March 05, 2013 12:07 PM
>> To: Evergreen General Discussion List
>> Subject: [OPEN-ILS-GENERAL] Long overdue items
>>
>> 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
>>
>>
>


-- 
Mike Rylander
 | Director of Research and Development
 | Equinox Software, Inc. / Your Library's Guide to Open Source
 | phone:  1-877-OPEN-ILS (673-6457)
 | email:  miker at esilibrary.com
 | web:  http://www.esilibrary.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-general/attachments/20130305/bea0d709/attachment-0001.htm>