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 <kluss...@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-iTxdHF1
> 4bsh1QTPMIwge9IrFrU/edit?usp=sharing
>
> Kathy Lussier
>
>
> --
> Kathy Lussier
> Project Coordinator
> Massachusetts Library Network Cooperative
> (508) 343-0128
> kluss...@masslnc.org
> Twitter: http://www.twitter.com/kmlussier
>
>

Reply via email to