Bug 154411 - Wish: family relationship between contacts
Summary: Wish: family relationship between contacts
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kab3
Classification: Miscellaneous
Component: general (show other bugs)
Version: 3.5
Platform: unspecified All
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-21 03:34 UTC by Dotan Cohen
Modified: 2009-08-05 16:34 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
screenshot of an example of what could solve this problem (159.29 KB, image/jpeg)
2008-08-18 14:08 UTC, Maurizio Pozzobon
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dotan Cohen 2007-12-21 03:34:24 UTC
Version:           1.2.5 (using KDE KDE 3.5.8)
Installed from:    Ubuntu Packages
OS:                Linux

I suggest two new fields for Kontact: "Spouse" and "Children". Each entry could have an optional birthday parameter, with a checkbox to have the birthday show up in Kalander.
Comment 1 FiNeX 2007-12-21 09:53:41 UTC
And if there are more than one child? One birthday parameter for the "children" field is not enough.
It is better to add the "spouse" or "children" as other contact in the addressbook.

Instead it could be implemented a "genealogical" relationship between contacts in the addressbook, but I don't know if this is expected by a addressbook.

What do you think about?
Comment 2 FiNeX 2007-12-21 09:59:54 UTC
*** Bug 154412 has been marked as a duplicate of this bug. ***
Comment 3 Dotan Cohen 2007-12-22 22:21:21 UTC
It could be implemented similar to the way the phone numbers are added, with a dropdown box for Spouse/Child/Mother/ETC. Or in a fashion similar to the way multiple email addresses are handled in Kontact. Shall I mock up what would be in my opinion an ideal solution? I am not a UI designer, but I can give it a shot.

> It is better to add the "spouse" or "children" as other contact
> in the addressbook. 

For many contacts, I need to have their wifes and children's birthdays in my calender. However, I really don't want another contact in my list. Often, I have much information in the Notes box, that would have to be duplicated (not good for data integrity). And simply adding a repeating calendar entry is not ideal, either.
Comment 4 Maurizio Pozzobon 2008-08-18 14:07:00 UTC
I think the best way to implement this would be to add a "Relationship" tab to the contacts information.

This tab should have a list of existing relationships of a contact and a way to add new one, like a textbox where you can write the name of another contact (like in partner's name), and two listboxes where you can choose the role in the relationship of the two contacts (the one you are editing and the related one), like father/son, employee/employer, friend/friend... obviously you should be able to create new relationship categories, like you already can with contacts categories

I'm not native in English so probably I wasn't able to explain in a comprehensible way what I had in mind, but I would like something like what you can do with your contacts in Microsoft CRM (and I imagine in others CRM)

I'll post a screenshot of it. The way MS do it isn't probably the best one but is a good starting point



Comment 5 Maurizio Pozzobon 2008-08-18 14:08:00 UTC
Created attachment 26908 [details]
screenshot of an example of what could solve this problem
Comment 6 Dotan Cohen 2008-08-18 21:57:30 UTC
That is an excellent solution, Maurizio, so long as the Role (or Relationship) can be defined and is not limited only to a default list of Relationship types.

It would be nice if the 'receiving' contact (Party 2 in the screenshot) would have a reverse-link showing the relationship back to the original (Party 1 in the screenshot).
Comment 7 Dotan Cohen 2009-03-19 19:44:55 UTC
Will the move to Akonadi make implementation of this bug possible now?
Comment 8 Tobias Koenig 2009-08-05 16:34:23 UTC
The development of the old KAddressBook will be discontinued for KDE 4.4.
Since the new application has the same name, but a completly new code base we close all bug reports against the old version and ask the submitters to resend there reports against the new product.