When we originally designed and wrote Tessitura, there were some pieces of functionality that made their way into the system that I never really thought were fully formed or thought out. As a result these features tend to get very little use or confuse many users.
One such feature is constituency-based security. This feature allows you to define rights to one or more constituent functions (i.e. editing addresses) based on the highest ranking constituency of that constituent.
Development stories concerning constituencies are starting to come into view and we need to explore whether this security paradigm is worth continuing.
In my opinion, the whole idea of constituency-based security loses a bit of its shine as soon as you realize that it's all based on the highest ranking constituency only. In addition, the concept was put in place well before Control Groups was ever thought of and we might have thought twice about it if Control Groups were in the original plan. It's not that Control Group functionality replaces constituency-based security, but rather that sometimes you have to step back and wonder whether there aren't too many layers of complexity. Especially if one of those layers is not often used--a survey of Network implementation consultants seemed to show that very few sites ever implement this functionality, at least initially.
Another factor prompting this thread is that several times our internal discussion on on how we might better use constituencies going forward has been hampered when someone says "yeah, but don't forget about constituencies and security".
We've tried to model out what would happen if we changed the model so that security could be based on "any" constituency instead of "highest ranking" constituency. But that always creates problems. What if a constituent has both constituency 1 and constituency 2. Constituency 1 says they're allowed to edit addresses and constituency 2 says that they are not. What to do then?
So some help here, please. How many sites use this functionality now and how passionate about it are you?
As always, thanks in advance for the feedback!
I'm not familiar with how constituency-based security works, and it sounds like that may be the case for others as well. Could you give an overview of what exactly it does? It sounds like it's meant to limit what a member of the public can do with their own record based on the constituencies they've been assigned. Is that correct? And how does that interface with control groups?
-Morgan
Hi-
We actually use this for a very specific business use. Because we sell youth classes, and we create a child record type which is tied to a parent who might have the same name, we added in a “KID” constituency to those child records and set-up security so that different user groups can’t sell tickets/membership to that record, but still allows them to update address information or do other management of the record.
Thanks
Jeanette Boudjouk
Database Analyst
Science Museum of Minnesota
651-265-9846
jboudjouk@smm.org
Omnifest 2010 brings five giant screen films to the Omnitheater for six short weeks from January 29 through March 11. Members see it free! View this year's films and trailers at www.smm.org/omnifest. The Dead Sea Scrolls: Words That Changed the World exhibition opens March 12. Witness authentic 2,000-year-old manuscripts, including the earliest biblical writings. Spiritually significant. Scientifically stunning. Visit www.smm.org/scrolls.
From: Chuck Reif <bounce-chuckreif3941@tessituranetwork.com> Sent: 2/18/2010 1:37:18 PM
You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!
Spam Not spam Forget previous vote