Production and Production Season - 2D & 3D Show Variants

I think the best recommendations are going to depend on two things: how do you want to present the items online and how do you want to report on them.

For online presentation, do you use TNEW?  If so, production season can have significant ramifications because it controls how events are groups in the event listing and also what "additional performances" are displayed when on the item reservation page.  As an example, we sell parking as "performances" on our TNEW site, but it's very limited and access to it is a member privilege, so we do keep the performances separate from the regular calendar.  Initially we lumped all parking into a single Production Season, but when we set up to allow donors to redeem their entitlements online we discovered that this made it the keyword-filtered event listing page for parking look awkward, so we have created production seasons matching the production seasons of the events the parking is for.

For reporting, if you need them separated of course production season would do it if you just needed to see them broken out within a season, but if you wanted to see the difference season over season ("Show me 2d vs 3d sales broken out by fiscal year.") then a separate production would assist with that.  But that might make a mess of your TNEW display.  Alternatively you could use another flag.  Performance Type, for instance, is available in Analytics.

I think the best recommendations are going to depend on two things: how do you want to present the items online and how do you want to report on them.

For online presentation, do you use TNEW?  If so, production season can have significant ramifications because it controls how events are groups in the event listing and also what "additional performances" are displayed when on the item reservation page.  As an example, we sell parking as "performances" on our TNEW site, but it's very limited and access to it is a member privilege, so we do keep the performances separate from the regular calendar.  Initially we lumped all parking into a single Production Season, but when we set up to allow donors to redeem their entitlements online we discovered that this made it the keyword-filtered event listing page for parking look awkward, so we have created production seasons matching the production seasons of the events the parking is for.

For reporting, if you need them separated of course production season would do it if you just needed to see them broken out within a season, but if you wanted to see the difference season over season ("Show me 2d vs 3d sales broken out by fiscal year.") then a separate production would assist with that.  But that might make a mess of your TNEW display.  Alternatively you could use another flag.  Performance Type, for instance, is available in Analytics.

Hi,

Thanks for the response. We are moving to TNEW thou in early stages. We currently develop and build our own inhouse ticketing app for the customers. We have gone through a data structure change to allow for better reporting to get round some issues with report dropdown lists being too large etc.

We have moved to the first row in the table above but we are having some interesting issues pulling the data through the API. We are trying to reduce the amount of calls and data we move between the app and TT for best practise and performance of the app.

We do report the shows as separate entities. i.e. How does the 3D do against the 2D for example.

It appears the first version is what most people are doing especially with TNEW from what I hear along the grapevine but just wanted to see if there was a consensus here.

Thanks

Ed