• Replies 6 replies
  • Subscribers 362 subscribers
  • Views 38 views
  • Users 0 members are here
Related

Tessitura Teacher Tribulations

Matt Gonzales
$organization

We have a situation with our teacher records in Tessitura.  It has come to our attention that (for whatever reason) they are set up in OI format with both N1 and N2 being used for the teacher's name under our HCO constituency.  That's right, instead of the school name being N1 and N2 being the teacher's name, it's in both.

Our concern is how to prepare these records for the migration with minimal consternation.  Any suggestions?

Anyone?

Thanks, Tessiturians.

  • $organization

    We've also found a number of irregularities in our account data. This seems like a great time to attack these systematically.

    I wonder what the best end result would be - keep the same constituent type and update the N1 to the school name? Or make the accounts individual types? I guess that would depend on how you want them to look after the v11 migration. Is the school connected to the teacher in some other way, like an association? If you've got an association, changing the accounts to indiv's and making the n2 the n1 might be the right way to go. You could do that easily enough with a sql update. 

  • $organization

    We have a similar problem except we have a school account and each teacher who orders for the school has an account with the school mailing address that get’s associated to the school account. We are rather scared about V11 because of the nature of our business. Hopefully it will be a smooth transition.

     

    Christopher Cuhel, Patron Services Manager

    First Stage

    Transforming Lives Through Theater

     

    From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Brian Graham
    Sent: Monday, November 14, 2011 3:21 PM
    To: Christopher Cuhel
    Subject: Re: [Tessitura Next Generation Forum] Tessitura Teacher Tribulations

     

    We've also found a number of irregularities in our account data. This seems like a great time to attack these systematically.

    I wonder what the best end result would be - keep the same constituent type and update the N1 to the school name? Or make the accounts individual types? I guess that would depend on how you want them to look after the v11 migration. Is the school connected to the teacher in some other way, like an association? If you've got an association, changing the accounts to indiv's and making the n2 the n1 might be the right way to go. You could do that easily enough with a sql update. 

    From: Matt Gonzales <bounce-mattgonzales9808@tessituranetwork.com>
    Sent: 11/14/2011 11:06:06 AM

    We have a situation with our teacher records in Tessitura.  It has come to our attention that (for whatever reason) they are set up in OI format with both N1 and N2 being used for the teacher's name under our HCO constituency.  That's right, instead of the school name being N1 and N2 being the teacher's name, it's in both.

    Our concern is how to prepare these records for the migration with minimal consternation.  Any suggestions?

    Anyone?

    Thanks, Tessiturians.




    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 Christopher Cuhel

    Chris - sounds like you're already a step ahead of many of us for the v11, what with already having a school account and many associated teacher accounts! Now just get their personal addresses and start selling them tickets for their own families as well! :)

  • $organization

    Oh Brian, I’m sure many of our teachers have personal accounts that is where the conundrum  exists. How do we figure out that mess? We never thought to associate the teachers private account with their school account.

     

    Christopher Cuhel, Patron Services Manager

    First Stage

    Transforming Lives Through Theater

     

    From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Brian Graham
    Sent: Monday, November 14, 2011 6:07 PM
    To: Christopher Cuhel
    Subject: RE: [Tessitura Next Generation Forum] Tessitura Teacher Tribulations

     

    Chris - sounds like you're already a step ahead of many of us for the v11, what with already having a school account and many associated teacher accounts! Now just get their personal addresses and start selling them tickets for their own families as well! :)

    From: Christopher Cuhel <bounce-christophercuhel9903@tessituranetwork.com>
    Sent: 11/14/2011 3:29:30 PM

    We have a similar problem except we have a school account and each teacher who orders for the school has an account with the school mailing address that get’s associated to the school account. We are rather scared about V11 because of the nature of our business. Hopefully it will be a smooth transition.

     

    Christopher Cuhel, Patron Services Manager

    First Stage

    Transforming Lives Through Theater

     

    From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Brian Graham
    Sent: Monday, November 14, 2011 3:21 PM
    To: Christopher Cuhel
    Subject: Re: [Tessitura Next Generation Forum] Tessitura Teacher Tribulations

     

    We've also found a number of irregularities in our account data. This seems like a great time to attack these systematically.

    I wonder what the best end result would be - keep the same constituent type and update the N1 to the school name? Or make the accounts individual types? I guess that would depend on how you want them to look after the v11 migration. Is the school connected to the teacher in some other way, like an association? If you've got an association, changing the accounts to indiv's and making the n2 the n1 might be the right way to go. You could do that easily enough with a sql update. 

    From: Matt Gonzales <bounce-mattgonzales9808@tessituranetwork.com>
    Sent: 11/14/2011 11:06:06 AM

    We have a situation with our teacher records in Tessitura.  It has come to our attention that (for whatever reason) they are set up in OI format with both N1 and N2 being used for the teacher's name under our HCO constituency.  That's right, instead of the school name being N1 and N2 being the teacher's name, it's in both.

    Our concern is how to prepare these records for the migration with minimal consternation.  Any suggestions?

    Anyone?

    Thanks, Tessiturians.




    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!




    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 Christopher Cuhel

    Unknown said:
    [...] I’m sure many of our teachers have personal accounts that is where the conundrum  exists. How do we figure out that mess?

    We, too, will have many such records created out of the N2 currently residing on various corporate and other organizational records. A few thousand, perhaps. We will treat them as potential dupes, to be found by the usual methods, i.e. some combination of matching whole or partial name/phone/e-mail/street1/zip, etc.

  • $organization in reply to Chris Jensen

    We wondered about the possibility of marking the N1 (in our case, the organization name) as INACTIVE, so that in the migration, the individual name would be generated, and the inactive name would be ignored (if appropriately expressed in the migration table rules.  Could that work?