In our consortium, we are starting the process of figuring out how to get accounts ready for the v11 migration. I have one organization that is very concerned about their associations. They have many accounts in Tessitura that have associations that are not tied to another Tessitura account. They are concerned that they are going to lose those associations. Is this anything they should be concerned with?
Thanks, Teresa
Teresa,
We have started working on this already as well. We are not a consortium but we have found the process to be an opportunity to “Clean” a lot of data including out dated associations and constituents. We have identified some really old stale accounts that will be in-activated in this process. We really wanted to purge them but it has been difficult to find a clean way to do that. We are finding that all of our teams are using this process to get rid of some things that weren’t necessary. Overall the process hasn’t been nearly as painful as we thought it was going to be. I am curious if anyone has figured out a non-gender way to identify Aunt, Uncle, Niece or Nephew?
Thanks,
Dave Alton
CIO
Center Theatre Group
o:213-972-7539 | c:213-973-2834
From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Teresa Dean Sent: Thursday, October 20, 2011 10:00 AM To: Dave Alton Subject: RE: [Tessitura Next Generation Forum] Current Association Question
Anna,
This is exactly what I needed….I needed someone from Tessitura to verify what I’ve been stating, to ease everyone’s minds. As expected, everyone is very nervous about this whole process and I’m trying to make it easier for them by getting my information that I’m giving them verified. Thanks for the help!!
Teresa
From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Anna Wessely Sent: Thursday, October 20, 2011 11:50 AM To: Teresa Dean Subject: Re: [Tessitura Next Generation Forum] Current Association Question
The migration will not remove any data from the system. The soft associations which you describe will be mapped and migrated just as the hard associations are. In the mapping table you should see some associations where there is only data in the Cur Xref Type column and not the Cur Other Xref Type column. These are the soft associations and they are mapped with just the New Assoc Type. If you are not seeing the soft associations listed separately it is possible you have an older version of the toolkit, you may want to download it and run the script again (don't worry you won't lose any mapping doing it that way).
I hope that helps.
Best,
Anna
Anna E. Wessely
Director Special Projects/Senior Application Specialist
Tessitura Network
+1 888 643 5778 x 308
awessely@tessituranetwork.com
From: Teresa Dean <bounce-teresadean9276@tessituranetwork.com> Sent: 10/20/2011 11:36:56 AM
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!
Hi Dave -
We went with the example Tessi gave us of Aunt/Uncle and Niece/Nephew. Not particularly elegant, but it works and you can always change up the names if someone has a brilliant idea.
Speaking of names for affiliations, I brought this question up to a smaller group of alpha testers but now that the migration toolkit is out to the larger world perhaps one of you guys will have a brilliant idea--
I'm wondering if anyone has come up with different terminology for gender neutral associations (Mother/daughter, etc) other than Parent/Child? We're finding that since we don't have a huge education program most of our parent/children associations are actually adult(ish) children - 18 and up. People are having a brain freeze at making them Parent/Child even though that is what they are... This is especially true with the 'in law' category -- 'Child in Law' just sounds wrong. So I've been wracking my brains for something that was a little more age neutral. The closest we've gotten is Parent/Offspring (eek!) which includes such gems as Parent In Law/Offspring In Law. I'm hoping the collective brain trust out there has a better idea. Or maybe we're just the freaky little theatre that makes mountains out of molehills. :P Thanks! HeatherSeattle Rep
I'm wondering if anyone has come up with different terminology for gender neutral associations (Mother/daughter, etc) other than Parent/Child? We're finding that since we don't have a huge education program most of our parent/children associations are actually adult(ish) children - 18 and up. People are having a brain freeze at making them Parent/Child even though that is what they are... This is especially true with the 'in law' category -- 'Child in Law' just sounds wrong.
So I've been wracking my brains for something that was a little more age neutral. The closest we've gotten is Parent/Offspring (eek!) which includes such gems as Parent In Law/Offspring In Law.
I'm hoping the collective brain trust out there has a better idea. Or maybe we're just the freaky little theatre that makes mountains out of molehills. :P
Thanks!
HeatherSeattle Rep
A quick search on Thesaurus.com provides these possibilities: chip off old block, descendant, family, generation, heir, issue, lineage, offshoot, posterity, produce, progeniture, progeny, scion, seed, spawn, succession, successor.
Of course of all these options I would prefer child for my own label! (although Parent/Spawn does have quite the ring to it...)
I think I just want a soft association of Scion.
Regarding soft associations and the "generate household" checkbox, for a soft assoication with a spouse, if an affiliation is specified and "Household" create is checked, will a new constituent be created for the soft association?
Thanks.
Lou Ann,
No. The Create Household check box is ignored for soft association rows in the Mapping table.There is not really enough information in the association to create a new constituent record.
David
Hi all,
I had a quick question about soft associations - is there a way with the v11 Toolkit to turn a soft association into a hard association?
For instance, if there are a whole stack of soft assocations for "Employee", is there a way to add an association to the other record for "Employer"? (Which could then later be examined and turned into an affiliation.)
Cheers,
Matt
Correct me if I'm wrong, but I think the soft association is the instance where there is no other record (there may be a name, but no customer number in the association.) For example we have lots of Employee/Employer hard associations and also a few Employee soft associations.
Hi Matt
You can create a "Soft Affiliation" ( I just checked in the Sandbox). I would assume that soft Employee-type Associations will become soft Employee-type Affiliations, and you will be able to create new constituenti from there by turning the soft Affiliation into a hard Affiliation.
But I don't think the Toolkit can do anything much else with soft associations - not enough detail, even if you have dozens of individuals soft-associated to the same org. In that case, i'd be trying to turn them into hard associations to a real org record before the conversion, I think.
Ken