I'm new here, so please excuse me if this has already been discussed. When you have duplicate records and one has only the wife's name (the record to be "kept") and the other has husband and wife's names (the record to be "deleted") and you schedule a merge, why is the husband's name NOT merged into the "kept" record? The logical conclusion for a merge of duplicate records is that all "unique" information will end up in the "kept" record, yet I am not seeing this happen. Can anyone explain if (a) I'm doing something wrong, or (b) if this is a software glitch that needs to be rectified?
Bonny, Colorado Ballet
Good morning Kevin,
Thank you for the link below. After reading pages 10 through 13 three times, I cannot locate what happens to N1 and N2 during the merge process, which is at the core of my question. Perhaps you can help me. As an example:
Record 105 has only Mr. Tim Robbins, and it is the record I want to keep.
Record 2230 has Mr. Tim Robbins in N1 and Mrs. Kathy Robbins in N2, and it is the record to delete.
When the merge has been completed, the kept record does not include Mrs. Kathy Robbins, yet her name is unique and logically in my mind, it should have merged her into N2 in record 105. My executives are questioning why this is not happening. Can you please explain – and will this be address in Version 11?
Thank you for your assistance Kevin!
Bonny Reinmuth
Executive Assistant
Colorado Ballet
1278 Lincoln Street
Denver, CO 80203
bonny.reinmuth@coloradoballet.org
Phone: 303.339.1722
Fax: 303.861.7174
www.coloradoballet.org
From: Tessitura Development Forum [mailto:forums-development@tessituranetwork.com] On Behalf Of Kevin SheehanSent: Monday, June 13, 2011 6:10 AMTo: Bonny ReinmuthSubject: RE: [Tessitura Development Forum] Dups - Name Data Merging?
Here’s the document:
http://www.tessituranetwork.com/network/Learning/Documentation/General/Managing%20Duplicate%20Constituent%20Records.aspx
Kevin Sheehan
Senior Documentation & Learning Resources Specialist
Tessitura Network
+1 888 643 5778 x 329
ksheehan@tessituranetwork.com
Bonny,
If you want to handle the specific circumstance you mention, you will need to alter the local merge procedure. I have done so for our consortium so that the following will happen:
If the kept record has an N2, nothing happens. If the kept record does not have an N2 but the delete record does, I place the delete N2 on the kept record N2 prior to the merge.
We also add aliases in a manner similar to what Amanda describes.