Hello Tessitura Community,
I am inquiring as to whether anyone would be able to share their organizations policy on merging constituents. My team would like to document a clear and concise policy on when to merge records, what to look for prior to merging and the process of cleaning up a record following a merge.
It would also be helpful to know how folks have their merge utility set up and what types of reports you run to track duplicates.
Thanks!
JeffVisitor Experience ManagerYBCA
Hi Jeff, I'm happy to share a merge document I worked on. We wrote it as a combination of standards and instructions for staff, so it explains the process of manually merging constituents, but there are some policy elements throughout. As far as the set up of utilities, we had just transitioned to Tessitura and had an enormous amount of duplicate. The more high level methods of duplicate identification gave us more than enough merging to do at the time. All our merging was done manually. We ran the AP_Identify_Duplicates procedure monthly according to the default values to populate the merge constituents screen, and then our staff would go through them according to the instructions in the document. Scheduled merges were done nightly. Let me know your email if you want to peruse the document
Juliane,
I'd be interested in seeing your doc as well. Is it something you'd be willing to share here on the forum?Thanks!
Hello Jennifer,
I've saved it here as a Google Doc (hopefully this link works). Let me know if you have any questions!
Fantastic! Thank you