Daily I'm going to create a number of Tessitura Accounts based on information we are gathering at several points around the building.
I have a sense that there are several ways I could automate this:
What are folks having the most success with as an approach for bulk creating accounts? Particularly methods that is robust to Tessitura System Changes over time?
What documentation exists for automating such a process?
Thanks for any help you are able to share.
--Tom
Tom,
When you say that the standard Constituent Import utility isn't going to suit your project, can I ask why? Like Heath I do a LOT of imports using the supplied utility - but I back it up with some SQL scripts afterwards.
Any automation like you're suggestion would need to be VERY robust - if only to deal with the ensuing duplicates!
Martin
Martin Keen (Past Member)
First great point about the duplicates. And thanks for your quick reply.
So, Why I'm consurned about the standard utility. Unlike in the theaters I've worked in, in museum we do a huge amount of "walk up", "day of" orders. There are lots of consurns about the time it takes to create a Tessitura Consituant record. To date we gather very few full customer record because all day long is like the 10-15 minutes before curtian in a theater box office. (People want to get into the Museum as soon as they arrive.) That said we are working on gathering more email addresses and names through a variety of mechinisms. Based on these data sources we will create micro identities with, in some cases, as little information as an email address and name.
For the project, I'm working on we will be doing imports daily, or possibly multiple times daily. Such that we can send a "Glad you were here emailed" each evening based on these micro identities that have come into the museum each day. These glad you were here emails will be inviting feedback and post-visit engagement with the Museum. We don't have staff around at these evening times of the day and am I hoping not to use this amount of manual staff time to walk through the standard account creation process 300 - 600 times a year.
So my consurns include timeless of import, use of staff time, and past problems I've had with the environment of Tessitura changing and the process breaking down and needing a bunch of work to get things working again.
I'd love to learn more about the Post process SQL scripts you are using.
I'm also curious to here more about what you think about this idea, and what other might think as well.