• Replies 15 replies
  • Subscribers 343 subscribers
  • Views 44 views
  • Users 0 members are here
Related

Ticket History from v11 to v12

Ray Bernard
$organization

Hi,

At the Science Museum, we have legacy ticket data from our previous software, in v11 (and  previous versions)  in Ticket History. In testing the migration to v12 this valuable information is not longer readily available. While we like the greater detail in the v12 History, we don't want to lose ready access to legacy data. Have any other organizations encountered this? How are you handling it? Are there any alternatives for scripted "back filling"of  this data into v12constituent records post migration?

Thanks.

Ray

Parents
  • $organization
    Clean Clean false false false EN-US X-NONE X-NONE

    Thanks, David, Beth and Ken for your thorough replies! You laid out the options and rationales quite well. Anna, thank-you; we’ll let our IT folks decide whether they can tackle this. With the wonderful guidance from all of you, they can make an informed decision.

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Anna Wessely
    Sent: Friday, January 10, 2014 11:52 AM
    To: rbernard@smm.org
    Subject: Re: [Tessitura Technical Forum] Ticket History from v11 to v12

     

    In general if you are planning to adopt the standard ticket history, as we reccomend, then I would plan to convert your legacy data from your old ticket history to the standard history table.  This would be similar to the process that you would use when you installed Tessitura originally.  As long as you are mapping similar columns from your old ticket history to the standard ticket history the conversion should be fairly easy.  If you would like some advice or assistance feel free to contact our consulting department to discuss the options; they are available to give you advice on how you might move your data and/or to take on the project for you.

    Best,

    Anna

    From: Ken McSwain <bounce-kenmcswain5454@tessituranetwork.com>
    Sent: 1/9/2014 4:24:50 PM

    Hi guys

    We haven't looked at it in detail yet, but our first thought is that we would keep our existing, heavily customised, ticket history, and not move to the new standard ticket history at all. I believe that's possible, although strongly un-recommended. We would add the new role-y stuff into our localised version, as per the What's new notes:

    NOTE: If you do not use the new, standard histories, you will need to update your customized histories to include initiator and recipient data if you want that data to be available for lists and extractions. Some instructions and examples for updating custom histories will be included in the v12 upgrade documentation.

    Apart from legacy system data, we also have a lot of imported external venue and agency sales, which we bring in on an ongoing basis, and for them we keep a chunk of specialised data, plus some other very local fields (for example a field which marks a sale record as available to SOH for marketing purposes, a legacy of a complicated contract change that didn't mesh with Tess ways of doing things.) 

    So I don't think we have any option other than to modify our custom tables to work with the new v12 stuff, and continue to use them. We'll see how we go.

    Ken




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Reply
  • $organization
    Clean Clean false false false EN-US X-NONE X-NONE

    Thanks, David, Beth and Ken for your thorough replies! You laid out the options and rationales quite well. Anna, thank-you; we’ll let our IT folks decide whether they can tackle this. With the wonderful guidance from all of you, they can make an informed decision.

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Anna Wessely
    Sent: Friday, January 10, 2014 11:52 AM
    To: rbernard@smm.org
    Subject: Re: [Tessitura Technical Forum] Ticket History from v11 to v12

     

    In general if you are planning to adopt the standard ticket history, as we reccomend, then I would plan to convert your legacy data from your old ticket history to the standard history table.  This would be similar to the process that you would use when you installed Tessitura originally.  As long as you are mapping similar columns from your old ticket history to the standard ticket history the conversion should be fairly easy.  If you would like some advice or assistance feel free to contact our consulting department to discuss the options; they are available to give you advice on how you might move your data and/or to take on the project for you.

    Best,

    Anna

    From: Ken McSwain <bounce-kenmcswain5454@tessituranetwork.com>
    Sent: 1/9/2014 4:24:50 PM

    Hi guys

    We haven't looked at it in detail yet, but our first thought is that we would keep our existing, heavily customised, ticket history, and not move to the new standard ticket history at all. I believe that's possible, although strongly un-recommended. We would add the new role-y stuff into our localised version, as per the What's new notes:

    NOTE: If you do not use the new, standard histories, you will need to update your customized histories to include initiator and recipient data if you want that data to be available for lists and extractions. Some instructions and examples for updating custom histories will be included in the v12 upgrade documentation.

    Apart from legacy system data, we also have a lot of imported external venue and agency sales, which we bring in on an ongoing basis, and for them we keep a chunk of specialised data, plus some other very local fields (for example a field which marks a sale record as available to SOH for marketing purposes, a legacy of a complicated contract change that didn't mesh with Tess ways of doing things.) 

    So I don't think we have any option other than to modify our custom tables to work with the new v12 stuff, and continue to use them. We'll see how we go.

    Ken




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Children
No Data