[OPEN-ILS-GENERAL] Notes from Wait Wait Do Tell Me conference session

[Bill Erickson]

Hi Jennifer,

Yes, the Action/Trigger event definitions have an "owner" field that limits
the scope of the generated events.  For overdues/predues, the owner would
limit to circulations that occurred at (or below) the specified owner.

If you wanted to limited by patron home library instead, you could add a
"home_ou":[1,2,3,...] filter next to (or in place of) the "profile" filter
from my example.  These would be org unit ID (actor.org_unit.id) values.

-b


On Mon, Apr 10, 2017 at 3:10 PM, Walz, Jennifer <jlwalz at asbury.edu> wrote:

> Bill,
>
>
>
> Thanks!   That is so very helpful!
>
>
>
>   Can this be done to set certain notice action triggers for different
> OU?
>
>
>
> Jennifer
>
>
>
> *From:* Open-ils-general [mailto:open-ils-general-
> bounces at list.georgialibraries.org] *On Behalf Of *Bill Erickson
> *Sent:* Monday, April 10, 2017 2:44 PM
> *To:* Evergreen Discussion Group
> *Subject:* Re: [OPEN-ILS-GENERAL] Notes from Wait Wait Do Tell Me
> conference session
>
>
>
> Hi,
>
>
>
> As promised at the session, here's a quick rundown of limiting notices to
> specific profile groups.
>
>
>
> 1. Create a custom filter file with a profile limiter.  Here's an example
> overdue notice filter limited to users with profile ID (
> permission.grp_tree.id) values 35, 1002, or 1003.  The "-exists" block is
> where the magic happens.
>
>
>
> {
>
>     "checkout.due" : {
>
>         "context_org" : "circ_lib",
>
>         "filter" : {
>
>             "checkin_time" : null,
>
>             "-or" : [
>
>                 { "stop_fines" : ["MAXFINES"] },
>
>                 { "stop_fines" : null }
>
>             ],
>
>             "-exists" : {
>
>                 "select" : {"au" : ["id"]},
>
>                 "from"   : "au",
>
>                 "where"  : {
>
>                     "profile" : [35, 1002, 1003],
>
>                     "id" : { "=" : {"+circ" : "usr"} }
>
>                 }
>
>             }
>
>         }
>
>     }
>
> }
>
>
>
> 2. Give the notice in question a unique granularity value in the admin
> interface.
>
>
>
> 3. Tell action trigger to use the custom filter file when generating
> notices for the unique granularity:
>
>
>
> perl action_trigger_runner.pl --granularity-only --granularity
> my-unique-granularity --custom-filters /path/to/my-custom-filter.json
>  [...other parameters]
>
>
>
> Hope this helps.
>
>
>
> -b
>
>
>
>
>
>
>
>
>
> On Fri, Apr 7, 2017 at 3:05 PM, Kathy Lussier <klussier at masslnc.org>
> wrote:
>
> Hi all,
>
> I have created a Google doc with the questions and answers at today's Wait
> Wait Do Tell Me Conference sessions.
>
> Questions that are answered in the Doc:
>
> Why does my new item not capture existing holds when I check it in?
>
> When are patron buckets coming?
>
> How can you create different types of notifications for different user
> groups?
>
> Will there be an offline mode in the web client?
>
> Learn the answer to these questions and more in the Google doc at
> https://docs.google.com/document/d/1F_84CHvUcCkdMdXd-
> iTxdHF14bsh1QTPMIwge9IrFrU/edit?usp=sharing
>
> Kathy Lussier
>
>
> --
> Kathy Lussier
> Project Coordinator
> Massachusetts Library Network Cooperative
> (508) 343-0128
> klussier at masslnc.org
> Twitter: http://www.twitter.com/kmlussier
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-general/attachments/20170410/9a36e0c5/attachment.html>