[OPEN-ILS-GENERAL] Expired Patrons Notification

Tim Spindler tjspindler at gmail.com
Mon Apr 11 09:49:38 EDT 2011


I started looking at this and I'm a little confused and not sure if
something has to be coded on the server side.   I created  the following
through the client on the hook tab.


Hook Key: cw.patron_expired
Core Type: au
Description: Passes expiration date of patron record
Passive: True

I used the Core Type of 'au' and Passive at True at Mike Rylander's
suggestion.  Is this all I need to do or does something need to be set up on
server outside of the client.  I'm wondering because this posting (
http://georgialibraries.markmail.org/thread/ojbm5wnl4awlv33h)  states

Next, we need to load the at.environment.sql and at.event_params.sql files
using

the same syntax from above.

Now, add the new json for the expire filter to your existing

action_trigger_filters.json.example.


I was assuming nothing needed to be done on the server to create a new hook.
Is that correct?

Tim Spindler

On Tue, Apr 5, 2011 at 12:23 PM, Ben Shum <bshum at biblio.org> wrote:

> This might be something similar, Mike Peters from Evergreen Indiana had
> this sent out to the mailing lists awhile back:
>
> http://georgialibraries.markmail.org/thread/ojbm5wnl4awlv33h
>
> The mail message indicates that an A/T event to remind patrons about to
> expire was written for 1.6 but should be adaptable to 2.0?
>
> -- Ben
>
> On 04/05/2011 12:15 PM, Mike Rylander wrote:
> > On Tue, Apr 5, 2011 at 11:57 AM, Tim Spindler <tspindler at cwmars.org>
> wrote:
> >> I was looking at setting up a courtesy notification for patrons records
> >>  that are about to expire and thinking that it could be done by
> configuring
> >> an Notification/Action trigger.   I was wondering if someone has done
> this
> >> already and would share what the did?
> >>
> > I don't believe anyone has done it yet, but you certainly could do it.
> >  You'd need a new hook with a core type of 'au', and a passive event
> > def with a delay field of 'expire_date'.  Note, you'll want to prefix
> > your hook with something local to your installation to avoid possible
> > future conflict with a stock hook, if one were added.
> >
>



-- 
Tim Spindler
tjspindler at gmail.com

*P**   Go Green - **Save a tree! Please don't print this e-mail unless it's
really necessary.*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://libmail.georgialibraries.org/pipermail/open-ils-general/attachments/20110411/3530ecb4/attachment.htm 


More information about the Open-ils-general mailing list