CiviCRM Community Forums (archive)

I have not tried to include nick_name in the display names. But what you are trying to do sounds totally logic to me? Does that mean we both have a weird mind then?

A few years back I got pretty ambitious for the Woolman website and deployed a bunch of custom hooks to make contact names work the way I thought they should:
- Display name should use nickname if available
- When filling out a profile or webform, nickname should not overwrite first_name if it is entered in the first_name field
- Dedupe matching should query on nick_name OR first_name for all queries
- Nick name token should supply first name if nick_name doesn't exist
- Names should be capitalized automatically for end-users too lazy to use the shift key (and uncapitalized for those with CAPS LOCK on)
- And some other stuff

All that stuff is still in place and still works even on 4.3. You're welcome to browse/borrow any of the code. For example https://github.com/woolman/drupal-modules/blob/master/woolman_website/woolman_website.module#L400

I've been toying with the idea of putting that code into an extension and making the different pieces configurable so site admins can pick & choose which nifty things they do and don't want.
I'd do it if you were up for co-maintaining it

Hi,

I have already an extension for the capitalisation problem (that tries to do it at the UI level as a tool to let the user chose a sane capitalisation)

https://github.com/TechToThePeople/civicrm-normalise