[Tickets #1892] NEW: Data import doesn't check for duplicate entries
bugs@bugs.horde.org
bugs at bugs.horde.org
Fri Apr 29 21:22:22 PDT 2005
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/?id=1892
-----------------------------------------------------------------------
Ticket | 1892
Created By | kevin_myer at iu13.org
Summary | Data import doesn't check for duplicate entries
Queue | Turba
Version | 2.0.2
State | New
Priority | 1. Low
Type | Enhancement
Owners |
+New Attachment | turba-duplicate-import.patch
-----------------------------------------------------------------------
kevin_myer at iu13.org (2005-04-29 21:22) wrote:
When importing data, no duplicate check occurs. As a result, if importing
from multiple disparate data sources, its possible to quickly obtain many
identical entires in your addressbook. Contact lists have the potential to
get really messed up, because only one entry exists in the contact list but
you have no way of knowing which addressbook entry it corresponds to and you
may inadvertently delete the wrong one, if you decided to clean up your
addressbook and remove duplicates.
The contacts API call from IMP, for adding an entry to the addressbook from
the headers of a message, does this check (single entry only). This patch
attempts to mimic that same behavior by checking for the existence of the
value in the addressbook.
Room for improvement - pluck the entry that is a duplicate out of the import
file and display the email address or name to the person importing the
entry, instead of "Already exists". Its too late for me to figure out how
to do that.
More information about the bugs
mailing list