[turba] Address Book Setup Questions

[Jan Schneider]

Zitat von Adam Tauno Williams <adam at morrison-ind.com>:

> On Wed, 2006-10-25 at 19:49 -0400, Chuck Hagenbuch wrote:
>> Quoting Jan Schneider <jan at horde.org>:
>>
>> > Shouldn't composite fields simply search all fields they are used to
>> > build it?
>>
>> Sounds simple, and if there are no obvious catches that's fine with me
>> (I can't think of anything right now, but it seems like it's just
>> hiding in a corner).
>
> It doesn't seem like that would produce the expected results.  If I have
> a composite field "name" comprised of "firstname" and "lastname";  then
> the user enters "adam w' and hits search.... I search for "adam w" in
> firstname and lastname - and find nothing.  I've seen lots of our users
> use expand names search from IMP like this,  I assume they'd do the same
> thing in the address book.  I understand the logic here,  but I don't
> know if it makes sense from a user's perspective.

That's a good point, but the alternative is to not allow that at all,  
because we would have to search on the client (Turba) side if we want  
to allow that. We already have the same problem with composite name  
fields or automatic last name detection and the pager.
This method would at least give some results if the users search for  
"adam", but I agree it's confusing if they don't get a result for  
"adam f" if "Adam Foo" is the only name they usually see in their  
address books.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/