Hi all,
For time immemorial, our FOH managers have issued via email a word doc at the end of each night regarding the performance with all of the typical data - actual house open and perf start times, house temperature checks, weather, concessions/ancillary sales during intermission, customer comments, etc. I want all of that data in Tessitura so it's retrievable and we can analyze it against/between productions.
I was thinking of creating a custom tab that would live on the perf level in Ticketing setup, and then building a report based off of that that could be scheduled and auto-emailed and then also related list criteria, output elements, etc. My concern, though, is making this easy for our FOH managers as well as not really wanting to grant access to ticketing setup to anyone other than show builders (as form data entry would have to be entered at the perf level each night). Has anyone else built this kind of report recently? Where did you set the data to live so that FOH could do their data entry?
Thanks!Kathleen
Ours is in Artifax and I'm thinking of moving it into Tessitura as well. Still planning
Are you on TNEW? If you are going with customization you might consider a TNEW customization that basically creates a form for the FOH to enter information in. You could connect their customer accounts to their user accounts as workers, then use that connection as a security measure to prevent anyone who doesn't log in on the correct worker accounts from accessing it. This way they could enter the data and pull it (via report) without having edit access to the production elements.
We ARE tnew (as well as RAMP/Hosted services). Right now, my budget says "free options are good options", but this might be something for me to ponder and possibly slip into next FY. Good thought!
This is not meant to put any current employees there on the spot, but back when I worked at Chicago Shakespeare Theatre about 10 (!) years ago, I recall they had a house-report-inside-Tessitura up and running. I didn't know all the tech terms back then, but I think it was a custom tab in Performance Setup, probably Infomaker-based given the time frame. Some of us spent time backfilling a few years' worth of old house reports into Tessitura as a summer project...
I'm not sure if they still use a similar system at all or if it was retired or replaced, and the house managers were also highly trained in other areas of Tessitura so some of the security and access issues you note were moot back then...but could be an org to reach out to as you continue to investigate!
Something I thought of this morning - since I'll have to have a local table to store this data anyway, I can always expose it in the system tables area of the client. It would be very easy to limit access to just that table for data entry purposes until I figure out the best place to do something with a friendly UI (maybe a web screen of some sort).
That's a really good idea.
If you wanted to make it super simple you could build it as a GA house with form fields and a secret promo code to shift MOS and open it.
The Stored Procedure capturing the form data can update a number of things as well as saving it to a local table - and if you are like us and save customer sentiment to CSIs you can have an FOH fly on the wall customer feedback CSI updated as well.
The confirmation would have instructions on pulling the report.
Arts Centre Melbourne did a ANZTRUC presentation in 2018 on setting up custom System Tables for Education to record their bookings etc. It was pretty great and served them well. I might have the slides on me.
Ooh, I'd love a peek at them if it's not too much trouble!