The redhen_dedupe module provides the ability to find and merge duplicate RedHen Contact records.
User Interface:redhen/dedupe
Configuration:admin/people/permissions#module-redhen_contact
Configuration
The only configuration necessary is to assign the "Administer RedHen Contacts" permission to any users you wish to give access to the Dedupe interface.
Usage
Users with permission will see a menu item on the RedHen menu named "Find Duplicate Contacts". This item leads to the path redhen/dedupe. This page provides a list of checkboxes for the basic RedHen Contact properties.
To merge, select the properties you wish to compare contacts with in order to isolate duplicates, and click Submit. At the bottom of the page, a list of duplicate "sets" will be displayed, showing the properties you selected, the number of duplicates matching those properties, and a button to merge.
Click a "merge" button to merge the Contacts with the corresponding properties. The merge interface walks you through selecting a Master record and choosing which field and property values from the various Contacts to keep on the merged record. All related items from the various Contacts, like those generated by RedHen Relation, will be attached to the Master Contact you selected. Which Contact is selected as Master shouldn't matter for a basic RedHen installation, but you may need to be more deliberate if you have made customizations to your setup that make use of RedHen Contact Entity IDs, as those of the Master record are the only ones that will be preserved. The other case where the Master record is significant is if you are merging records across different Contact Record Types: the Record Type of the Master will be preserved, and is hard to change later.
The field and property selection interface actually renders all of the fields, so the page can become quite large depending on what types of fields your contact records have and how many records match.
RedHen Dedupe was introduced in RedHen 1.5
