A well known phonetic matching algorithm is Soundex, I think it is
built-in in Oracle, it is definitely ok to start with... it is very
important for names, not only people names but also companies, that
people many times fail to spell or has a few variations. Specially if
users come from different
Steve, Joan, Erin, Jim, Josh, Phillip, Petter, Sarah, and Santiago,
Thank you- I stand enlightened and inspired!
Vincent
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=41113
___
On 09/04/2009, at 08:59, Vincent wrote:
Type ahead by last name is a wonderful solution. Though, it seems
contextual to last name?
In the proof of concept ( http://icograma.com/raf08/ ), clients can be
found by any field(s).
All this queries give [Jorge Gonzalez, phone 4946-2493, address
Also, testing search functionality is *not* possible until the very end
of release which naturally limits any actions to be taken based on
results of user testing.
...Just to play devil's advocate, why not? You could create some working
prototypes to test this before development. Prototypes may t
A single incremental search field coupled with a decent search engine,
allows to search by name, surname, address, and/or phone number (w/o
dashes), in any order, with maximum efficiency.
Proof of concept: http://icograma.com/raf08/
This mockup, in spanish, is part of a 45' presentation we gave i
I can't thank everyone enough for the generous feedback here.
Scenarios are quite broad with primary emphasis on first and last
names (Steve, your point to phonetic matching is right on track for
when looking for a name you only heard ... especially with Google
appliance).
A close second are nam
Google Search does have the "Did You Mean" feature - perhaps that
would help in the Louise/Louisa arena?
Also look to the predictive search on Facebook as a best-in-class
example of finding people. It might be outside of your scope but is
very easy to use.
Jakob Neilsen's studies about search in
I agree with Philip Hunter: the type of searches normally conducted
should (or could) play a strong role in deciding which method to
apply.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=41113
__
I've had a similar experience as Jim...if you can implement type-ahead
you solve 80-90% of queries.
Also, people really *like* type-ahead.
On Apr 9, 2009, at 5:56 AM, Jim Kauffman wrote:
Here at Vanguard we use a simple type-ahead search box based on a last
name list. The person's phone ex
Here at Vanguard we use a simple type-ahead search box based on a last
name list. The person's phone extension is listed with their name.
Advanced search is available, but most people get by with just the
type-ahead box.
Jim K.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Many genealogical sites offer this sort of solution for people
search. Because literacy rates were not high in the western world
until the 20th century, spelling of names in public records was often
approximate at best, and so this is a necessary feature for people
trying to find records o
Vincent,
Both options have plenty to recommend them. The one thing Google lacks which
I think is particularly useful when searching for people is a phonetic
matching algorithm. This can help overcome issues with names like Louise,
Louisa, Louissa, etc; when looking for a person who's name you've o
Hi All,
Currently have some questions about searching an internal directory
of 20,000+ people.
There's some thinking that a Google appliance utilizing a white bar
with rich search capability (parameters / facets on particular
attributes) would be enough to narrow down to who you're looking
for.
13 matches
Mail list logo
