Database Management - Donor Merges

Hi Robert
We do an auto-merge process.
Basically, the logic is that we run a heavily customised identify potential dupes process; then feed the output into another process that takes sets of identified dupes (not just pairs); makes a decision about which one of each set to Keep based on factors that affect the assumed "well-keptness" of the record, like whether the record is a subscriber or donor, and recency of activity; creates records for each merge-pair from that set; and puts those pairs back into the Tess merge schedule table; where they are picked up by the normal scheduled (nightly, for us) merge.
We currently run that process monthly.
It relies on some local tables that assign merge priority rankings to constituencies and attributes, so there are a few components.
It seemed like a fairly Brave thing to do, but it's worked well so far.
I think all of the components of that are on my TessWeb profile files page - if not I can add them in if you'd like to have a look.

Ken McSwain :: sent from the Blackberry
 

We are doing some clean-up for on our database for constituents duplicates.

 Has anyone written an automated procedure to do a mass merge of constutents? 

 I am thinking of building a local table based on an agreed upon set of rules and call the internal Tessitura procedure with the from and to constituent id's

Bob

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!
Read about the ACO’s Stradivarius violin at aco.com.au/Stradivarius.
Explore the ACO’s 2011 season at aco.com.au/season2011

This email is confidential. If you are not the intended recipient you must not disclose or use the information contained in it. If you have received this email in error please notify us immediately by return email and delete the document. The ACO is not responsible for any changes made to a document other than those made by the ACO or for the effect of the changes on the document's meaning. The ACO accepts no liability for any damage caused by this email or its attachments due to viruses interference, interception, corruption or unauthorised access.

Hello Ken and Simon

We are a 4 member UK consortium TNEM who went live on Tessitura in January this year. Having migrated 4 databases into one, we are also looking to have an auto-merge process to help us reduce a large number of duplicate records.  Having looked at the files and information you have posted we wondered if it would be ok to contact you directly about this to answer a few more questions that we have regarding this process?

Thanks

Annie Scally

 

 

Hi Annie

Always happy to email (or talk)

Direct email is    ken.mcswain@aco.com.au

Ken

 

Hi Annie

Always happy to email (or talk)

Direct email is    ken.mcswain@aco.com.au

Ken