So we are finally ready to start tackling merging duplicate records! Sadly we have quite a large amount to tackle first. About 12,000. Gulp. What I'm thinking of doing is running the identify dupes procedure once and then scheduling the merge procedure to run nightly so that any dupes that were scheduled that day get merged and off the list.
After we tackle those then we had decided to schedule the procedures to run weekly, but I'm interested to hear how often other organizations schedule these procedures to run. Do you find it's better to do it daily or weekly?
Any advice on how to get our massive amount of duplicates down quickly? I think we're going to divide the alphabet up so we can have several people working on scheduling them at once.
Thanks!
We run the merge process and the potential duplicate procedure nightly.
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
From Classic Rock to Classical, the ISO celebrates your favorite music idols this January! Rock to The Music of Paul McCartney featuring Tony Kishman, Jan. 14-16 and delight in the "Emperor" Concerto when piano powerhouse Andre Watts Plays Beethoven, Jan. 21 & 22. Tickets at IndianapolisSymphony.org. Music of Paul McCartney link - http://www.indianapolissymphony.org/tickets/learnmore.aspx?id=3520 Watts Plays Beethoven link - http://www.indianapolissymphony.org/tickets/learnmore.aspx?id=3567
P Please don't print this e-mail unless you really need to.
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Christina Bledsoe Sent: Wednesday, December 29, 2010 1:42 PM To: Dee Dee Fite Subject: [Tessitura Technical Forum] How Often to Merge Duplicate Records
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical 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!
Thanks for the advice! On a related topic we had decided we would keep the account that has a membership or subscription because members get an id card with their account number on it and subscribers generally know their account number. We have come across some duplicate records where one account has an active membership and the other has a subscription package. I'm very hesitant to merge these accounts and we're trying to figure out a way to handle them. I know that when you search for an account that was merged the kept account will get returned in the search. So should I not worry about it? Any advice?
Unknown said: Thanks for the advice! On a related topic we had decided we would keep the account that has a membership or subscription because members get an id card with their account number on it and subscribers generally know their account number. We have come across some duplicate records where one account has an active membership and the other has a subscription package. I'm very hesitant to merge these accounts and we're trying to figure out a way to handle them. I know that when you search for an account that was merged the kept account will get returned in the search. So should I not worry about it? Any advice?
With a few exceptions (such as >1 sub pkg) we merge and keep the oldest record regardless of subscriptions and/or memberships. Memberships in particular need to be checked the next day, but I'd recommend checking merges the next day in general to make sure all is as expected.