Hello there,
We are considering adding an education season in TR_SEASON in order to segment our educational programs from the mainstage productions. Currently we only have a single season per fiscal year.
The idea is to better be able to pull lists, use the season criteria to run certain reports with more detail and separate data by season in T-stats. I'm concerned though that there will be some yet unforeseen consequences of adding a new season in this way. Can anyone who has multiple TR_Seasons per fiscal year share their experience? Are there key reports that will implode? Anything tricky we can expect to happen?
Thanks for the help,
Kyle Y.
San Jose Repertory Theatre
We started on Tessitura in 2008 and have always had multiple seasons per FY for just the reason you mention. Not only does it help with reporting; it also helps segregate what each user group sees and doesn't see since you can Control Group seasons. There are really no consequences I can think of other than perhaps a bit extra administrative work to keep everything up to date.