One of the big tasks ahead in the Next Generation project is redefining all the ways in which a constituent relates to other constituents. Today we call this Associations and we know that it doesn’t begin to cover all the bases. So just as we have in the past, we need you to help us out with your thoughts on any or all of the following questions:
1. What are the ways that constituents relate to one another, particularly ways that aren't so easy to track in Tessitura today? 2. What are some scenarios that describe ways that your business needs to communicate with different segments of related constituents? (A simple example: “Sometimes I need to send a mailing out with only one piece per household. But if I’m doing the same promotion in an email I need to send it to all the members of the household.”)3. One of the things we struggled with in designing Tessitura the first time was the whole name1/name2 construct. Is there a reason to treat spousal relationships differently than any other type of family/household relationship? 4. What other questions need to be asked about this topic?
Hi Chuck - i have a few thoughts to add on assocations:
1. The way are displayed is makes it difficult to read and they are not easily searchable (i would suggest a list of names and relationship types that you can click into)
2. They should be listed alphabetically by organization/surname
3. Contact information needs to be stored in an organized way especially for corp/trust contacts who don’t have their own records
4. They don’t necessarily need to be divided into employment/family/other as this can be defined in the exact nature of the relationship
5. You should be able to invite associations to activities
All the best,
Ruth
A relationships issue I’ve been thinking about is when one person buys tickets for another person. I think ideally the record of the financial transactions would be tied to the person actually purchasing the tickets, but we’d want the ticket itself to be tied to the person who’ll be using the tickets.
This same challenge also applies to people who subscribe together – a subscription for 4 that is paid for by one couple, on the account of one couple, but two couples attend. They don’t want to split the subscription because it’s the simplest way of making sure they continue to be seated together year after year, but both couples want us to treat them like subscribers (i.e. not mail to the couple without the subscription record asking them to subscribe).
Kirk Mortensen Database Administrator
tel: 650-463-7122 fax: 650-463-1963 kirk@theatreworks.org
“SPELLBINDING… PURE MAGIC” - Chicago Sun Times
THE CHOSEN by Aaron Posner and Chaim Potok October 7 - November 1 Mountain View Center for the Performing Arts
From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Ruth Forrester Sent: Monday, October 19, 2009 3:40 AM To: Kirk Mortensen Subject: Re: [Tessitura Next Generation Forum] Relationships, anyone?
From: Chuck Reif <bounce-chuckreif3941@tessituranetwork.com> Sent: 10/16/2009 8:30:12 PM
1. What are the ways that constituents relate to one another, particularly ways that aren't so easy to track in Tessitura today? 2. What are some scenarios that describe ways that your business needs to communicate with different segments of related constituents? (A simple example: “Sometimes I need to send a mailing out with only one piece per household. But if I’m doing the same promotion in an email I need to send it to all the members of the household.”) 3. One of the things we struggled with in designing Tessitura the first time was the whole name1/name2 construct. Is there a reason to treat spousal relationships differently than any other type of family/household relationship? 4. What other questions need to be asked about this topic?
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!