Hello,
We are part of a consortium of theaters and so we share patron data. We've recently come across a little issue with our NScan Monitor List attribute. It works fine, but a patron who is on the VIP list that we want to monitor for attendance at one theater in our consortium, is triggering an alert/email of attendance when scanning a ticket at another of our consortium theaters. So the Person receiving the notification email is receiving it when the patron checks in at another theater.
Is there a way to set up the attribute perhaps as a control group for that one theater so that only when the patron scans using the scanners at the appropriate theater will it then send the alert email? or is there another solution?
Thanks!
-Maureen Cotellese
Maureen,
I would be curious to hear what other people have done here, too. We have set up NScan e-mail alerts, and we are also in a consortium environment, so we have experienced the same thing. Thus far, we have just been dealing with it as it has not been THAT irritating (though still somewhat).
For a number of other database procedures and reports, I set up a local table that joins control groups with organizations, and so that seasons can be filtered directly against to which organization they belong. I have been pondering updating the NScan procedures to run performance numbers against that table to try to distinguish between patrons attending performances by each organization, but have not been able to get the logic exactly where I want it to limit it to the specific customer_nos since we would have to resort to those staff numbers, and I was rather hoping to avoid setting up N-Scan attributes for each individual organization, but I suppose I might have to get there eventually.
At any rate, if someone else has a good idea for this, I would be happy to hear it. Either that, or I suppose I should bite the bullet and get updating.
John