[dev] IMP and Turba Integration Question

[Nik Chanda]

Hi All--

I would ask for any input on the IMP/Turba integration for a couple 
advanced features.  This question is specific to the "Expand names 
automatically" and "Save recipients automatically" features in the 
Address Book options.

When saving recipients, IMP properly creates a new record in the default 
address book populating the  email address and display name.  When 
composing an e-mail to the newly added address. It also properly 
searches for (and finds) the matching display name.  When the To field 
is auto-populated however, it prints the first and last name instead of 
the display name -- leaving the name blank or similar to:
 "., ." <email at hostname>.

I am willing to implement any solution that makes sense.  Here are a 
couple thoughts -- please let me know if this would bring any value and 
if you have any suggestions:

1. On the auto import of recipients:  Continue to add the name value to 
the displayname field. Then, extend functionality to parse value by 
spaces -- adding the first word to the first name field and all 
remaining words to the last name field.  This is not perfect, but it 
would support last names such as "von Ehrenkrook."  It could cause 
problems if the user entered the To value as "lastname, firstname."

2. Leave the import as is, and extend the Expand Names functionality to 
check for "non whitespace" values in the first and last name fields.  If 
no values are found, insert the displayname value instead.  Should this 
require both a firstname and lastname, or only one value?

2a. Extend the Expand Names functionality to render the field from which 
the match was found.  So if the search string matched the displayname 
field, it would print the display name.  If it was a first name or last 
name that matched -> print the firstname / lastname pair.

3. Enhance the address book functionality throughout to support an 
option to display by first name, last name pairing (already exists) or 
by display name.  This would also require IMP to call the Turba API to 
get the option setting before rendering the value.

Thanks for your input.

Nik