• Replies 11 replies
  • Subscribers 360 subscribers
  • Views 57 views
  • Users 0 members are here
Related

Getting ready for Next Gen

Dave Alton
$organization

So Center Theatre Group has undertaken the prereq's for the new Tessitura Next Gen project.  We recently  (today) upgraded our Tessitura Database to Server 2008 x64 along with SQL Server 2008 R2.  It actually went extremely smoothly.  We have also updated most of our component servers such as the Transcend server, WebAPI Server and Seat Server server.  These have all been switched to the latest version of Windows Server 2008.  It took about two months of testing and 2 full overnight operations and about 6 hours of downtime over two nights to get everything back up and operating as we had hoped.

I can honestly say I was pleasantly surprised at how smoothly it went.  Since we are preparing we are also preparing staff for the new changes to the Database.  I had some initial questions about the Constituency model going forward.

  • How will the constituents be imported from our current database? 
  • Will current constituents that have both Name 1 and Name 2 be converted to a family account and the individuals given new personal ids?
  • Or will all current ones be transferred as they are and then moving forward, family accounts can be created?
  • If they are automatically converted, can we pick and choose which ones get the conversion?
  • If we convert to a family account, can they ever be split up again in the future if need be?
  • If account is split, does it divvy up the info according to which “id” was assigned to it? e.g. phone numbers with their personal id, etc.

Our development staff spent a lot of time looking over this and came up with these questions.  I think that some of this might have been addressed in an earlier post but thought we might bring it up again as we are a lot closer now than when we were initially looking at this.

Thanks,

Dave

Parents
  • $organization

    Where will the transaction/order history go? I assume on the household record? If so, seems like this is where we will need to keep the login information so that any web/api functionality that looks at orders, like subscription renewals,  will continue to work.

     

    From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Andrew Recinos
    Sent: Wednesday, March 23, 2011 11:27 AM
    To: Charlotte Hussey
    Subject: Re: [Tessitura Next Generation Forum] Getting ready for Next Gen

     

    Hi Jon,

    Yes, through the front-end you will be able to see in the General Tab and Relationships Tab that an individual is the first affiliate on the household and the second affiliate on the household - essentially mirroring that they were previously Name1 and Name2.  You will see the individuals on the General Tab of the Household and there will be a new navigation tree that will show the affiliates of the household.  From a data perspective, we are expecting to have a table that maps the original customer_nos to the newly created individual constituents (although this table won't be visible through the application).

    On the logins question, the default behavior would be to leave them on the household account unless the N1/N2 flag has been set to Name1 or Name2, in which case they would move to the appropriate new individual.  As mentioned before, we expect to have areas in the upgrade script to add business-specific logic, so for instance, some organizations might make the decision to leave logins on the household regardless of the N1/N2 flag.

    Hope that helps!

    Andrew

    From: Jon Ballinger <bounce-jonballinger5072@tessituranetwork.com>
    Sent: 3/23/2011 9:03:39 AM

    Andrew,

    I forgot to ask how will logins be handled when the account gets split to individuals?

    Thanks




    You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!

  • $organization in reply to Charlotte Hussey

    Hi Charlotte,

    Good questions.  The "where will the transaction go" question is actually an area that the NextGen and Member Advisory Committee have spent a good deal of time discussing over the past six months or so.  While still in analysis and not yet ready for primetime, we have a pretty good idea of how we will accomplish this in a flexible way for Version 11. 

    We are aware of the potential for different organizations wishing to determine where transactions are stored now that there is a new constituent model.  Some will undoubtedly want to keep the transactions on the household, as you note, in keeping with how things are done today.  Others may wish to start storing transactions on the individual affiliates of a household.  We are in the process of finalizing methods to allow organizations to determine this individually, so that you can determine, by organization, where the transactions should "live" and then enforce this both through the Tessitura application and via the existing API.

    Stay tuned for more information about specifics of this new functionality in the coming months.

    Thanks!

    Andrew

Reply
  • $organization in reply to Charlotte Hussey

    Hi Charlotte,

    Good questions.  The "where will the transaction go" question is actually an area that the NextGen and Member Advisory Committee have spent a good deal of time discussing over the past six months or so.  While still in analysis and not yet ready for primetime, we have a pretty good idea of how we will accomplish this in a flexible way for Version 11. 

    We are aware of the potential for different organizations wishing to determine where transactions are stored now that there is a new constituent model.  Some will undoubtedly want to keep the transactions on the household, as you note, in keeping with how things are done today.  Others may wish to start storing transactions on the individual affiliates of a household.  We are in the process of finalizing methods to allow organizations to determine this individually, so that you can determine, by organization, where the transactions should "live" and then enforce this both through the Tessitura application and via the existing API.

    Stay tuned for more information about specifics of this new functionality in the coming months.

    Thanks!

    Andrew

Children