Hello Everyone!
At the BSO we currently recording age via date ranges but were thinking about moving towards year-of-birth so that the data will always be accurate. I'm wondering if any other Tessie organizations who define age in terms of year-of-birth XX/XX/XXXX. Is this possible with Tessitura? And if you are using Year-of-birth, how has your success been of collecting the data?
Any guidance you can provide would be much appreciated.
We are also considering a data append to suppliment our current records.
Please share your thoughts,
Jamie Jean
Jamie SchneiderE-Commerce and Digital Marketing ManagerBaltimore Symphony OrchestraPhone: 301.581.5207 | jschneider@BSOmusic.orgJoseph Meyerhoff Symphony Hall | 1212 Cathedral St. Baltimore MD 21201 | www.bsomusic.org The Music Center at Strathmore | 5301 Tuckerman Lane North Bethesda, MD 20852 | One world-class orchestra. Two world-class concert halls.
2009 BSO Gala CelebrationPiano superstar Lang Lang joins Marin Alsop & the BSO to kick off the season in exciting style!
Click here to purchase tickets from $50!
Hi Jamie,
We collect the full birthdate as an attribute. We've named the attribute 'Birthdate YYYYMMDD' so that users know that that's the format that must be used when inputting this data. when this attribute is added by a customer online it automatically is rendered in this format in Tessitura
We've found it very successful as some of our programs are only available to constituents in certain age categories. One in particular only allows online purchases and the sale is validated by the birthdate (which is verified at ticket pick up time). A nightly job runs to apply appropriate constituencies based on this attribute (i.e. minor...so we don't market to them)
We are not using it very often yet but we have two attributes set up for this.One of "Birthdate DOB" (however I like the MM/DD/YYYY idea) which is a data type of Date forcing us to use the full date and another one of "Birthday-Month/Day" in case we don't know the year.