Duplicate Constituent Management Tool - Ability to alter the algorithm to improve functionality
The Duplicate Constituent Management Tool (DCMT) returns far too many records that are clearly not duplicates - we have a database of just over 110,000 constituents and are running RE 7.93 - the DCMT will produce over 4,000 potential duplicates (example - Mr A Sebir as duplicate to Ms A Senior) - an ability to change the algorithm so that it would not view different genders as duplicates would be a big step forward.
Also on settings it is possible to exclude Inactive and Deceased constituents, it would be very useful to us as an organisation if it was possible to also exclude Constituents with No Valid Address marker.
I'd welcome the opportunity to have a look at the current algorithm if possible.
-
Guest
- Jan 31 2014
Related ideas
Yes!! This would really help those with larger databases.
Totally agree. Previous business rules were able to be set internally so we could match on first name, surname and postcode, this is a backward step in my opinion to use all this fuzzy data. Our staff add data to the system correctly so there's no need to match Mr J Jack to Mrs Jean Jackson. However, the area where you manage dupes is preferable to the old static report. Being able to dedupe on email address would also be great.
Add a unique identifier for suggestions so we can let you know to merge suggestion 101 with 307 because they are the same or similar. Sort matching search results in order of votes (descending) so we can see which have the most votes. Other posts similar to this one: The duplicate criteria algorithm is too broad and, therefore, brings up too many ' possible duplices when importing large volumes (22 votes); duplicate constituents (13 votes); Have an option to use duplicate constituent 7.92 criteria or specify your own criteria (377 votes); duplicate constituent report does not return true duplicates (26 votes); duplicate (15 votes); A much better duplicate search where you can create various criteria. Right now too many duplicates are not appearing in the report (12 votes); duplicate constituent search does not find true duplicates (4 votes) that over 500 votes to say the duplicate/merge tool is seriously inadequate and should get some serious attention
Yes, and I would like to be able to exclude certain alias types from the match criteria because it is currently suggesting possible duplicates because the alias of ID number from our previous database is similar, even though the names, addresses and phone numbers are quite different.