[#1892] Data import doesn't check for duplicate entries
Summary Data import doesn't check for duplicate entries
Queue Turba
Queue Version 2.0.2
Type Enhancement
State Resolved
Priority 1. Low
Owners Horde Developers
Requester kevin_myer (at) iu13 (dot) org
Created 04/30/2005 (1347 days ago)
Due
Updated 05/24/2005 (1323 days ago)
Assigned 04/30/2005 (1347 days ago)
Resolved 05/24/2005 (1323 days ago)
Attachments turba-duplicate-import.patch Download
Milestone
Patch No

History
05/24/2005 Chuck Hagenbuch Comment #2
State ⇒ Resolved
Reply to this comment
Committed along with the enhancement of displaying the name.
04/30/2005 Jan Schneider State ⇒ Assigned
Assigned to Horde DevelopersHorde Developers
 
04/30/2005 kevin_myer (at) iu13 (dot) org Comment #1
State ⇒ New
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ Data import doesn't check for duplicate entries
Queue ⇒ Turba
New Attachment: turba-duplicate-import.patch Download
Reply to this comment
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.