RE: Mapping v10 Associations to v11 Affiliations – a l��e�

Hi Marty,

You are on the right track. Affiliations are used to define relationships between unlike constituent types (groups - organizations or households -  to individuals).  Associations are used to define relationships between like constituent types (organization to organization OR individual to individual).  Affiliations are also different from associations in that they do not have reciprocity like associations.  They always describe the relationship from the individual’s point of view to the group.  “I am the Employee to this company”, “I am the Student in this household”.  For that reason, when you are mapping a v10 association to a v11 affiliation, you only need to indicate what the affiliation type would be to describe the individual in the relationship and you indicate that on both sides.  That is why for Employer/Employee you would use Employee on both rows.  You would do a similar thing for relationships like Parent/Child.  Assuming the parent record represents a household (which would become a group) and the child record is an individual, you would use Child Member affiliation type for both rows in your mapping because that describes the relationship of the individual to the group.

All that being said, sometimes there are relationships that imply a directionality like Subscriber/Subscriber Not Of Record, or Attorney/Client, or Doctor/Patient.  In these cases, it is not always consistent which side of the relationship is the provider and which side is the receiver.  For example, the company (or group) side is the Attorney and the individual is the client.  But it could just as easily be the other way where the individual is the attorney and the group the client.  When you map affiliations for these types of relationships, you can specify a different affiliation type for each side.  When the migration is done, whichever mapping row applies to the individual in the relationship, that’s the affiliation type that would be used.  So in the case of the Attorney/Client example, sometimes the affiliation will be Attorney and sometimes it will be Client depending on what the individual is to the group.  This directional mapping of affiliations, incidentally, was added in as part of the latest migration toolkit build which was announced a couple weeks ago.

Remember that you can run the staging as often as you would like and the Staging Results can be filtered so that you can focus on specific pieces of the migration to see what will happen to your data.  So, for instance, you can map your associations, run the staging and then filter the staging results by associations and affiliations to see how these relationships will come over.  That can be a big help in being able to see how certain types of mapping decisions will affect your data.

Hope this helps!

Gregg

From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Marty Jones
Sent: Monday, November 21, 2011 12:27 PM
To: Gregg Stickney
Subject: [Tessitura Next Generation Forum] Mapping v10 Associations to v11 Affiliations – a little lost

Reading through the doc for the section Mapping v10 Associations to v11 Affiliations and getting a little lost here. The example given is for (Employee – Employer) & (Employer – Employee) where both rows are to be marked “Employee” for the New Affiliation type. I guess I don’t understand this in why the (Employer – Employee) row would also be marked “Employee” Taking this a step further, I assume that I could not apply the same logic to a pair of say Adult and Child. I am thinking that the row of Child – Adult is marked as “Child Member” and the row Adult – Child is marked as “Adult Member”. Would this be a correct assumption?

I am thinking the difference between the 2 samples would be that the Employer – Employee is a Group to Individual where the Adult to Child is an Individual to Individual. Just looking for clarification.

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!

--
View this message online at http://www.tessituranetwork.com/COMMUNITY/forums/p/6030/19173.aspx#19173 or reply to this message
--
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!