[OPEN-ILS-DEV] Lost item handling

[Mike Rylander]

On Fri, Dec 19, 2008 at 11:01 AM, Bill Ott <bott at grpl.org> wrote:
>
>>> Less-short story:
>>> "Void lost on checkin" can mean a few different things.  There are
>>> normally two different generated charges, lost processing fee and lost
>>> replacement charge, and either one or both might need to stick around
>>> depending on circumstances.  So, that's part of what is being taken
>>> into account with the "in the works" support, based on a (relatively
>>> speaking) wide range of input from production sites (including, in
>>> fact, one of your MLC compatriots ;) ).
>>>
>>
>> I realized that.  In the code I've been playing with, I added pieces for
>> both.  Actually a 3rd, as we (GRPL) go as far as removing the lost charge,
>> but reinstate the original overdue fines.  So I've got a piece that
>> reinstates the original overdue charges, un-voids them essentially.
>
> Oh, and a final note.  I don't have it worked in here yet, but originally I
> mentioned the voided charge by date.  For us, we only accept the item back
> for 1 year post due-date.  After that, you can give it back, but we still
> charge for it.  So, while anything but a zero will trigger these now, a
> duration is what's really needed (e.g. "1 year").
>

Right.  That would be another (optional) org setting, I think.  There
are functions for turning dates and intervals into integers (see:
interval_to_seconds in OpenSRF::Utils) to facilitate age comparisons.

-- 
Mike Rylander
 | VP, Research and Design
 | Equinox Software, Inc. / The Evergreen Experts
 | phone:  1-877-OPEN-ILS (673-6457)
 | email:  miker at esilibrary.com
 | web:  http://www.esilibrary.com