From roots-in@roots-l.rootsweb.com Fri May 19 16:56:56 2006
Received: from mail.rootsweb.com (mail.rootsweb.com [192.168.65.34])
	by admin.rootsweb.com (8.12.8/8.12.8) with ESMTP id k4JMuujb029863;
	Fri, 19 May 2006 16:56:56 -0600
Received: from roots-l.rootsweb.com (roots-l.rootsweb.com [66.43.16.22])
	by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k4JMuts3027343
	for <roots-approved@rootsweb.com>; Fri, 19 May 2006 16:56:55 -0600
Received: from roots-l.rootsweb.com (roots-l [127.0.0.1])
	by roots-l.rootsweb.com (8.12.10/8.12.10) with ESMTP id k4JKMRFI019034
	for <roots-approved@rootsweb.com>; Fri, 19 May 2006 16:22:27 -0400
Received: (from roots-in@localhost)
	by roots-l.rootsweb.com (8.12.10/8.12.8/Submit) id k4JKMRKA019033
	for roots-approved@rootsweb.com; Fri, 19 May 2006 16:22:27 -0400
Received: from lists5.rootsweb.com (lists5.rootsweb.com [66.43.27.41])
	by roots-l.rootsweb.com (8.12.10/8.12.10) with SMTP id k4JIFUFI018791
	for <roots-in@roots-l.rootsweb.com>; Fri, 19 May 2006 14:15:30 -0400
Received: (from slist@localhost)
	by lists5.rootsweb.com (8.12.8/8.12.8) id k4JKnkGV028012
	for roots-in@roots-l.rootsweb.com; Fri, 19 May 2006 14:49:46 -0600
X-Envelope-From: Kith-n-Kin@cox.net Fri May 19 14:49:45 2006
Received: from mail.rootsweb.com (mail.rootsweb.com [192.168.65.34])
	by admin.rootsweb.com (8.12.8/8.12.8) with ESMTP id k4JKnjjb028003
	for <ROOTS-M@lists5.rootsweb.com>; Fri, 19 May 2006 14:49:45 -0600
Received: from fed1rmmtao10.cox.net (fed1rmmtao10.cox.net [68.230.241.29])
	by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k4JKngHT007792
	for <ROOTS-M@rootsweb.com>; Fri, 19 May 2006 14:49:43 -0600
Received: from TOWER ([68.0.155.47]) by fed1rmmtao10.cox.net
          (InterMail vM.6.01.06.01 201-2131-130-101-20060113) with ESMTP
          id <20060519204938.LKEH18458.fed1rmmtao10.cox.net@TOWER>;
          Fri, 19 May 2006 16:49:38 -0400
From: "Kith-n-Kin" <Kith-n-Kin@cox.net>
To: <joe2phil@drizzle.com>, <ROOTS-M@rootsweb.com>
Subject: RE: [ROOTS-L] Vital record index question  
Date: Fri, 19 May 2006 13:49:36 -0700
Message-ID: <002c01c67b85$c085d160$6601a8c0@TOWER>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
Importance: Normal
In-Reply-To: <002d01c67b6e$644b18e0$4b898843@y9w6c2>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-Scanned-By: MIMEDefang 2.52 on 192.168.65.34
X-Scanned-By: MIMEDefang 2.52 on 192.168.65.34
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by admin.rootsweb.com id k4JKnjjb028003
Sender: roots-in@roots-l.rootsweb.com

Well, supposedly, Ask.com is what you seek. I tried it this morning for an "other than genealogy" request
and it was "ok" -- but not *that* much better than Google.

I suggest that the only way the "surname" "lenox" search would be read by any search engine would be if
there were some kind of "hypotext" underneath (not visible) the word designating it as a surname.  In the
meantime, I just try to think of all the "context words" I can to put in the search, (in any engine) so I
can avoid the problem. Of course, with surnames such as Graves, Parks, Gray, and such, I'll never win this
one.

But you could, for example, use <  Lenox genealogy "new york" -town -glassware -"air conditioning" -"air
conditioner" > and so on to get what you want. I'd just like to have much more space for that drilling.

So, you see, it is a bit upside down. The "smart index" needs to be on the part of the document
originator, not the search engine.  

I'll try to remember that when I get around to publishing to the net.

Pat (in Tucson)

|-----Original Message-----
|From: roots-in@roots-l.rootsweb.com 
|[mailto:roots-in@roots-l.rootsweb.com] On Behalf Of 
|joe2phil@drizzle.com
|Sent: Friday, May 19, 2006 11:02
|To: ROOTS-M@rootsweb.com
|Subject: [ROOTS-L] Vital record index question 
|
|
| Hello guys , I am wondering if anyone ' out there ' is 
|working on a ' smart index ' system ,  A system that will 
|actually return the Item requested !! , Not every instances of 
|the item / name / place in the page or pages being searched , 
|????  OR in other words ,  the Surname Lenox only , not the 
|town of Lenox , or the maker of fancy glassware , OR the maker 
|of Air conditioning heating equipment
|   I would think it would be possible to formulate a program 
|that ' reads ' the page and can ' see ' what is being said , 
|Discarding all but those which actually apply to a surname 
|request ,  Try it on Google someday . put in " Lenox " , see 
|the 5 milion hits returned  or J P Stevens !!!!!! ,  Phil , 
|who is named Joseph Philip , granparents Lenox
|
|



