How that I hooked you with the catchy title...
How do you handle two constituents that marry.
-Do you merge the records?
-Do you keep them seperate and make associations to each spouses record?
The question I would ask is what happens in the future if the couple splits? Yes, we are going through this right now. We merged the accounts when the couple married. Now they are divorced.
In hindsight, I would have created a third account for the couple. Associated the individual accounts to the 3rd account and inactivated the individual accounts. If I had done that, I could now just reactivate the old individual accounts.
It’s just something to think about before you merge.
Dee Dee
Dee Dee Fite |dfite@IndianapolisSymphony.org Director of Patron Systems Indianapolis Symphony Orchestra *: 32 E. Washington St. Suite 600 | Indianapolis, IN 46204-2919 (: 317.229.7080 | (f) 317.262.1159
The Beethoven just keeps on coming! Mario Venzago leads Beethoven’s Fifth Symphony, featuring the four most famous notes in music, on May 8-9. Visit IndianapolisSymphony.org for tickets.
P Please don't print this e-mail unless you really need to.
From: Tessitura Development Forum [mailto:forums-development@tessituranetwork.com] On Behalf Of Parnell E. LaLonde IV Sent: Thursday, May 07, 2009 2:08 PM To: Dee Dee Fite Subject: [Tessitura Development Forum] Conjoin or NOT to Conjoin, THAT is the question
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Development Forum. You may reply to this message to post to the Development 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!
We recently dealt with this issue, but our relationship was primarily with the wife, so we removed the husband from their account and created a new account for him. Then we associated the two records as ex-spouses.
If we had had to split the history, it would have been a lot messier for us, but we probably would have handled it with a some carefully tested updates on the back-end.