Summary: | merge contacts is missing | ||
---|---|---|---|
Product: | [Applications] kaddressbook | Reporter: | Ferdinand Gassauer <gassauer> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | wishlist | CC: | steffen, tokoe |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Ferdinand Gassauer
2011-07-29 13:18:12 UTC
Extremely needed! I own an addressbook with more than thousand entries, most of them double up to five-times (due tu import from several generations of mobile phones), some with few or more different detail entries. Two wishes: First, easiest (?): Mark two or more kontacts, choose "merge", (In reply to comment #1) > Extremely needed! > I own an addressbook with more than thousand entries, most of them > double up to five-times (due tu import from several generations of > mobile phones), some with few or more different detail entries. > > Two wishes: > First, easiest (?): Mark two or more kontacts, choose "merge", Sorry, wrong keys pressed .. I continue: then: - in case the entries are identical, merge silently - in case there are different details: show all details (with field name) and (pre-chosen) radiobuttons to chose, which entries are to be merged. (may be, the text field should be editable for manually changes) grafically, either the "or"-set of different entries should displayed or the two or more verstions side by side (with repeated details grey..) Second, more complex: - search the whole corpus for possible duplicates (narrow or wide searches possible) - for each possible duplicate/set of similar entries show both/all entries for the first decision to be done by the user, if they belong to the same person (contact) i.e. they should be merged - for all contacts to be merged proceed like in the "simple" case. Thanks to all working on addressbook / PIM ! :-) Steffen *** This bug has been marked as a duplicate of bug 242647 *** |