Hello all,
I am hoping to get a sense of how different orgs manage their merging of duplicates. I have read on the forums about some great examples from a couple of years ago of people scheduling the Identify Duplicates procedure, and having a daily task of manually putting them into the Merge queue.
Some people appeared to have been confident enough to merge constituents automatically if they meet the criteria.
I would love to hear how many people are automatically merging duplicates, and how many people are doing it manually, which is how I was always taught.
At ACMI, we have thousands of duplicate accounts from importing e-news subscribers over time. The bulk of these accounts only have First Name, Last Name and email. We are working with Tessitura consultants to get our Identify Duplicates logic to pick theses up, and would very much like to merge automatically as many as possible.
Thanks all!
Nicholas
Good day, Nicholas
We’re relatively new to Tessitura (started Aug. 13), and most of our patron accounts migrated from our legacy system.
Data in our legacy system was a mess; thousands of potential duplicates.
When we imported patron accounts from the legacy system into Tessitura, I used SQL script to note these probable duplicates – and simply merged them.
A few merged accounts were wrong, but >99% either were correct or didn’t matter.
As patrons register on our new site (and accounts are created in Tessitura), these accounts pop up as potential duplicates.
At this time I manually run SQL script to identify these potential duplicates, then manually merge them.
Each week I probably merge 20-30 accounts, and will probably continue this manual process for another year or so.
There are too many variables to automate the process, and I still struggle with other users “buying in” to Tessitura usage.
I know Tessitura provides an automatic method to identify and merge potential duplicates, but that process isn’t an option for us right now.
Best Regards
Wendell Baskin
Bass Hall – Fort Worth
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Nicholas Hudson-Ellis Sent: Sunday, April 13, 2014 22:58 To: Wendell Baskin Subject: [Tessitura Technical Forum] Merging Constituents Advice?
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!
Hi All,
There are a lot of potential pit falls when merging records as I have recently found out. Our Box Office were being very efficient in their regular merge process, but they didn't know that a number of records were deliberately being created with spoof addresses. They happily merged these thinking they were not required. I then had a visit from one of our Development ladies in complete melt down about missing records!
I've now had several weeks of painful coding to unmerge the incorrectly merged records. They now have the 'Void Merge' attribute!!
So, just a word of warning.....take care!
Debbie