Hello Everyone!
Here at the TSA we would like to better engage with our patrons. For example: flagging patrons as disabled or donors or "frequent flyers", then being able to pull the rooster and see that someone with these flags are coming to the event.
But I don't know whether this would be best/easiest/most useful to do this as a CSI/attribute/etc.
Or how to do it for that matter?
Please share what you do and let me know if you have any advice!
Many thanks,
Jamie Jean
We use mostly a combination of attributes and constituencies. For the disability example, we use an attribute of "disability" and the attribute value is specifically what: wheelchair, hearing impaired, etc. The presence of the attribute triggers a constituency. So users can always see from the constituency that there is some kind of disability, and know to look at the attribute to see what it is.
For us, a large part of the decision making for attribute vs constituency was based on whether we'd want anyone who looks at the account to know that info about the patron as soon as they look at it, or if we really only need to know in the context of lists/reporting. So things that are immediate needs-to-know were usually constituencies, and things that were more we want to be able to find out if we ask were usually attributes.
Hope some of that helps.