Segment Updates

Hi there,

I was just wondering whether anyone has discovered or created a way to bulk update the segments to indicate running times across a season of performances after they have been built as yet?

We often do not know the running times for performances ahead of the on sale date - and so have the laborious and time-consuming task of updating this information individually once it becomes available.

Is there any clever people out there who have created a report or similar to do this ?

Any thoughts or suggestions would be greatly appreciated!

regards,

Mardi.

Parents
  • Former Member
    Former Member $organization
    I'm sure Kimly could do you a quick report to update a set of perfs with new segment times.... I'd just do it as a conform task - i e manually adjust one perf, then run a report to conform the other perfs in the same production season to match the selected one. Easy-peasy.
     
    ________________________________
    Ken McSwain

    Systems and Technology Manager

    Australian Chamber Orchestra

    ken.mcswain@aco.com.au

    Ph +61 2 8274 3833 :: Mob +61 418 659 360 :: Fax +61 2 9274 3801

    PO Box R21, Royal Exchange NSW 1225

    2 East Circular Quay, Sydney NSW 2000

     

    From: Tessitura Ticketing Forum [forums-ticketing@tessituranetwork.com] On Behalf Of Sandra Ashby [bounce-sandraashby2064@tessituranetwork.com]
    Sent: Tuesday, 2 August 2011 19:11
    To: Ken McSwain
    Subject: RE: [Tessitura Ticketing Forum] Segment Updates

    Mardi

     

    Segment info is stored for each performance in TX_PERF_SEG and you could import it into there (after a lot of testing of course) for a performance or performances. Of course making sure that you had the correct details for perf_no and the rest of the info, ie segment type id (from tr_perf_seg), duration and the segment order.

     

    Be worth giving it a try in Test at least.

     

    S.

     


    Read about the ACO’s Stradivarius violin at aco.com.au/Stradivarius.
    Explore the ACO’s 2011 season at aco.com.au/season2011

    This email is confidential. If you are not the intended recipient you must not disclose or use the information contained in it. If you have received this email in error please notify us immediately by return email and delete the document. The ACO is not responsible for any changes made to a document other than those made by the ACO or for the effect of the changes on the document's meaning. The ACO accepts no liability for any damage caused by this email or its attachments due to viruses interference, interception, corruption or unauthorised access.
Reply
  • Former Member
    Former Member $organization
    I'm sure Kimly could do you a quick report to update a set of perfs with new segment times.... I'd just do it as a conform task - i e manually adjust one perf, then run a report to conform the other perfs in the same production season to match the selected one. Easy-peasy.
     
    ________________________________
    Ken McSwain

    Systems and Technology Manager

    Australian Chamber Orchestra

    ken.mcswain@aco.com.au

    Ph +61 2 8274 3833 :: Mob +61 418 659 360 :: Fax +61 2 9274 3801

    PO Box R21, Royal Exchange NSW 1225

    2 East Circular Quay, Sydney NSW 2000

     

    From: Tessitura Ticketing Forum [forums-ticketing@tessituranetwork.com] On Behalf Of Sandra Ashby [bounce-sandraashby2064@tessituranetwork.com]
    Sent: Tuesday, 2 August 2011 19:11
    To: Ken McSwain
    Subject: RE: [Tessitura Ticketing Forum] Segment Updates

    Mardi

     

    Segment info is stored for each performance in TX_PERF_SEG and you could import it into there (after a lot of testing of course) for a performance or performances. Of course making sure that you had the correct details for perf_no and the rest of the info, ie segment type id (from tr_perf_seg), duration and the segment order.

     

    Be worth giving it a try in Test at least.

     

    S.

     


    Read about the ACO’s Stradivarius violin at aco.com.au/Stradivarius.
    Explore the ACO’s 2011 season at aco.com.au/season2011

    This email is confidential. If you are not the intended recipient you must not disclose or use the information contained in it. If you have received this email in error please notify us immediately by return email and delete the document. The ACO is not responsible for any changes made to a document other than those made by the ACO or for the effect of the changes on the document's meaning. The ACO accepts no liability for any damage caused by this email or its attachments due to viruses interference, interception, corruption or unauthorised access.
Children
  • Thanks for the suggestions.

    We do currently store this information in the Synopsis for the ones we find out about after the fact. At this point I am looking to use the dedicated field and thus introduce more consistency for the ticketing team.

    Ken and Sandra - I will look at your suggestions and work out which works best for us.

    Thanks again for the ideas to try!