Pull non-ticketed events into Tessitura website via API?

Hello Tessitura Web API gurus,

My org is redeveloping our website at the moment, and one of our goals is to pull in dates and times of Performances, even if there are no tickets available, and present them in a calendar.

An example of this would be a free exhibition. We still want the exhibition to show up in a calendar with Performances that do have tickets. 

Another example of this would be an event that we do not provide ticketing for. We would still create Performances, but would use the TNEW Buy Tickets override Content field (or something similar) to provide the external link for customers.

The rationale behind this is to keep Tessitura as the single source of event information that is exposed to the public at some point.

Do any organisations operate like this? Or have you considered this and went down another path?

Cheers,

Nicholas Hudson-Ellis

 

 



[edited by: Nicholas Hudson-Ellis at 6:16 AM (GMT -6) on 8 Feb 2014] added 'to API' to title.
Parents
  • Former Member
    Former Member $organization

    Hi Nicholas

    ACO put a variety of non-ticketed events up on the website through Tess - from education workshops to ABC-FM broadcasts of our concerts.

    Eg on our Calendar page. 

    We use a mixture of perf keywords ( eg "Show in Event Lists"), content fields (eg  venue details that substitute for the dummy-faclity details that we use for the perfs in tess), and config data on the website itself ( eg a switch to turn the 'Buy Tix" links off)

    That's all with a bespoke website, of course - I don't know how easy that kind of customisation is in TNEW - but Steve G will be here for ANZTRUC this week, so that should be a good opportunity to  chew his ear about it. ¿Si?

    Ken

     

     

Reply
  • Former Member
    Former Member $organization

    Hi Nicholas

    ACO put a variety of non-ticketed events up on the website through Tess - from education workshops to ABC-FM broadcasts of our concerts.

    Eg on our Calendar page. 

    We use a mixture of perf keywords ( eg "Show in Event Lists"), content fields (eg  venue details that substitute for the dummy-faclity details that we use for the perfs in tess), and config data on the website itself ( eg a switch to turn the 'Buy Tix" links off)

    That's all with a bespoke website, of course - I don't know how easy that kind of customisation is in TNEW - but Steve G will be here for ANZTRUC this week, so that should be a good opportunity to  chew his ear about it. ¿Si?

    Ken

     

     

Children