Duplicate Contacts Manager for Thunderbird

This Thunderbird extension facilitates handling of redundant entries in address books.
After installation it can be invoked via the Tools->Duplicate Contacts Manager... menu entry. One can also customize the Toolbar of the Address Book window with a Find Duplicates button.

[Screenshot of start window with the options available]

The Duplicate Contacts Manager searches address books for matching contact entries, also known as cards. It can automatically delete all cards that match and have equivalent or less information than some other one. Any remaining pairs of matching cards are as potential duplicates for manual treatment. Each two cards are shown side-by-side with a comparison of all fields containing data, including any photo. Some important fields are always shown such that they can be filled in when they have been empty so far. When pairs of candidate duplicates are presented, the reason why they are considered matching is given in the status line.

During manual treatment of a pair of matching cards the user can skip them, can modify one or both of them, and can decide to delete one of them. When a card is deleted and it has a primary email address that is contained in one or more mailing lists and the other card does not have the same primary email address, the address is also deleted from the respective mailing lists.

Matching contact entries

There are two search modes for finding matching cards:

Two cards are considered matching if any of the following conditions hold, where the details are explained below.

Yet cards with non-equivalent AIMScreenName are never considered matching, which is convenient for preventing cards from being repeatedly presented for manual treatment.

The matching relation is designed to be rather weak, such that it tends to yield more pairs of candidate duplicates.

Matching of names, email addresses, and phone numbers is based upon equivalence of fields modulo abstraction, described below. As a result, for example, names differing only in letter case are considered to match. For the matching process, names are completed and their order is normalized — for example, if two name parts are detected in the DisplayName (e.g., "John Doe") r in an email address (e.g., "John.Doe@company.com"), they are taken as first and last name. Both multiple email addresses within a card and multiple phone numbers within a card are treated as sets, i.e., their order is ignored as well as their types.

Abstraction of field values

Before card fields are compared their values are abstracted using the following steps.
  1. Pruning, which removes stray contents irrelevant for comparison:
    1. ignore values of certain field types — the set of ignored fields is configurable with the default being UID, UUID, CardUID, groupDavKey, groupDavVersion, groupDavVersionPrev, RecordKey, DbRowID, PhotoType, PhotoName, LowercasePrimaryEmail, LowercaseSecondEmail, unprocessed:rev, unprocessed:x-ablabel,
    2. remove leading/trailing/multiple whitespace and strip non-digit characters from phone numbers,
    3. strip any stray email address duplicates from names, which get inserted by some email clients as default names, and
    4. replace @googlemail.com by @gmail.com in email addresses.
  2. Transformation, which re-arranges information for better comparison:
    1. correct the order of first and last name (for instance, re-order "Doe, John"),
    2. move middle initials such as "M" from last name to first name, and
    3. move name prefixes such as "von" to the last name.
  3. Normalization, which equalizes representation variants:
    1. convert to lowercase (except for name part of AOL email addresses),
    2. convert texts by transcribing umlauts and ligatures, and
    3. if configured, replace in phone numbers the national trunk prefix (such as '0') with the default country calling code (such as '+49').
  4. Simplification, which strips less relevant information from texts:
    1. remove accents and punctuation, and
    2. remove singleton digits and letters (such as initials).
Corresponding fields in two cards are considered equivalent if their abstracted values are equal.
Note that the value adaptations mentioned above are computed only for the comparison, i.e., they do not change the actual card fields.

If automatic removal is chosen, only cards preferred for deletion (which implies equivalent or less information than some other card; for details see below) are removed.
When a pair of matching cards is presented for manual inspection, the card flagged by default with red color for removal is

Equivalence of information

A card is considered to have equivalent or less information than another if for each non-ignored field: For the above field-wise comparison, the email addresses of a card are treated as a set, the phone numbers of a card are also treated as a set, and the set of names of mailing lists a card belongs to is taken as an additional field.

A card with equivalent or less information than another is preferred for deletion if:

Here is an example.

[Screenshot of comparison window showing two matching cards]

The card on the right will be preferred for deletion because it contains less information.

NickName: "Péte" "  pete ! " accent, punctuation, letter case, and whitespace ignored
FirstName: "Peter" "Peter Y van" name prefix "van" moved to last name, middle initial "Y" ignored
LastName: "van Müller" "Mueller" name prefix "van" moved to last name, umlauts transcribed
DisplayName: "Hans Peter van Müller" "van Müller, Peter" first name moved to the front, name is substring
PreferDisplayName: 'yes' 'yes' same truth value
AimScreenName: "" "" same AIM name
PreferMailFormat: 'HTML' 'unknown' default ('unknown') considered less information
PrimaryEmail: "Peter.vanMueller@company.com" "P.van.Mueller@gmx.de" emails treated as sets, letter case ignored
SecondaryEmail: "p.van.mueller@gmx.de" "" emails treated as sets, letter case ignored
WorkPhone: "089/1234-5678" "+49 89 12345678" national prefix normalized and non-digits ignored
PopularityIndex: 5 3 field ignored for infomation comparison
LastModifiedDate: 2018-02-25 07:51:28 2018-02-25 08:30:37 field ignored for information comparison
UUID: "" "903a61be-64d5-4844-802a" field ignored

[Screenshot of final window showing a statistics on the last run]

Configuration variables

The options/configuration/preferences used by this Thunderbird extension are are saved in configuration keys starting with extensions.DuplicateContactsManager. — for instance, the list of ignored fields is stored in the variable ignoreFields.

Update of 2017-02-27, introducing version 1.0

This is a major update, which I call Version 1.0, of the Duplicate Contact Manager.

Work on this extension apparently has been stopped by end of 2012. Meanwhile, mixed user experience piled up on the official Thunderbird add-on feedback page.

Recently I faced a major challenge: my address book with some 1.200 entries got inflated by a buggy CardDAV online sync tool to more than 17.000 cards. The new copies contained new types of automatically generated identification meta fields. When I tried to clean the mess automatically using Duplicate Contact Manager, this did not work because it considered the copies different due to the new identifiers. So I added to the extension a configurable list of field types ignored during comparison. Doing so, I started fixing several issues and adding further features:

Part of the original post of 2012-04-07, introducing version 0.9:

The so far available Version 0.8.2 was a good starting point, but since I urgently needed a more sophisticated tool, I started improving it myself. My changes have been motivated — and validated — using my personal address book with some pretty diligently manually managed 1.000 entries and using the automatically generated collected address book with some 2.500 entries including many duplicates and weird variants of names etc.
The change log is:

Questions and comments are welcome.

[Valid HTML5] URL: http://ddvo.net/DuplicateContactsManager/index.html Last modified: Mon Jun 4 00:05:55 CEST 2018