Bug 264023

Summary: add policy option for a default non-empty "Display:" field in contact records
Product: [Applications] kaddressbook Reporter: sphakka <marcoep>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: REPORTED ---    
Severity: wishlist CC: herr_oswald, tokoe
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description sphakka 2011-01-22 23:34:39 UTC 
Version:           unspecified (using KDE 4.4.5) 
OS:                Linux

Hi there,
With kaddressbook v4.4.8 on KDE v4.4.5 (gentoo): importing googledata entries via akonadi results in records with emtpty "Display:" field. That's pretty annoying when exporting to LDIF files, because it results in incomplete records, where the "cn:" line is missing. 
It would be nice to have a policy option to automatically fill the "Display:" field with any available information from the "Name:" field.

Cheers,
  ^s

Reproducible: Always

Steps to Reproduce:
1) add a contact, filling the "Name:" field and leaving empty the "Display:" field;
2) export it to an LDIF file.

Actual Results:  
The resulting LDIF file has entries lacking the "cn:" line, as well as the "cn=" field of the "dn:" line.

Expected Results:  
1) The "Display:" field in the new contact is automatically filled with the "Name:" field's value.
2) The exported LDIF filed has the corresponding "cn:" line.

Not sure if akonadi_googledata is actually buggy, as for the "Display:" field.
Comment 1 Wolf Drechsel 2014-11-08 09:24:38 UTC 
Agreed on the above.

Additionally, I think, there should be a possibility to user set a default behaviour which policy is used.  I, e.g., do prefer the order "surname, first name" -  but other people will like it in a different way.
Comment 2 Justin Zobel 2021-03-09 02:34:06 UTC 
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.