Bug 222684

Summary: New field type: working hours
Product: [Applications] kaddressbook Reporter: Dotan Cohen <kde-2011.08>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED INTENTIONAL    
Severity: wishlist CC: tokoe, wstephenson
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Unspecified   
Latest Commit: Version Fixed In:

Description Dotan Cohen 2010-01-14 11:58:35 UTC 
Version:            (using KDE 4.3.4)
Installed from:    Unspecified Linux

Now that Kaddressbook is Akonadi based and not Vcard dependant, it would be great if a new field type for working hours could be added. Right now I am using the Notes field for this, but having a separate field would let one query for this information, and find it quickly. This field is relevant for over half of my 400+ contacts, so it is not some corner case.

Thanks!
Comment 1 Tobias Koenig 2010-01-14 12:54:01 UTC 
Hej Dotan,

having KAddressBook based on Akonadi doesn't mean we don't depend
on vCard anymore... Akonadi is only an access layer, the storage
is still done in vCard/Groupware Server/etc...
So we should try to keep as compatible as possible. You can use
a custom field for that as soon as they are back in 4.5 or later

Ciao,
Tobias
Comment 2 Will Stephenson 2010-03-04 10:17:41 UTC 
Agreed - the more fields in the base Addressee, the harder it is to synchronise or to write groupware backends for.   Extensions like this will be possible with Nepomuk ontologies, but how this will be represented in the UI is a completely open question.
Comment 3 Dotan Cohen 2010-03-16 13:56:48 UTC 
> You can use a custom field for that as soon as
> they are back in 4.5 or later

Custom fields are not flexible enough to let one query for information such as:
1) See which pizza restaurant is open on Friday at 02:30 in the morning.
2) See which museums will be open when your old friend comes to visit.
3) Which pharmacy is open on Saturday when your child is sick.

If you are concerned about vCard compatibility, then the information could be stored in custom vCard fields. Or the information could be stored in a human-readable format as an amendment to the Notes field, that won't show in Kaddressbook but will show in other apps. Shall I suggest just such a format?


> but how this will be represented in the UI is a
> completely open question.

Would you like me to write up a mockup?