From roots-in@roots-l.rootsweb.com Mon Jul 31 15:41:15 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 k6VLfFjb023961;
	Mon, 31 Jul 2006 15:41:15 -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 k6VLfCCT003518
	for <roots-approved@rootsweb.com>; Mon, 31 Jul 2006 15:41:12 -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 k6VJ2RFI030324
	for <roots-approved@rootsweb.com>; Mon, 31 Jul 2006 15:02:27 -0400
Received: (from roots-in@localhost)
	by roots-l.rootsweb.com (8.12.10/8.12.8/Submit) id k6VJ2R9U030323
	for roots-approved@rootsweb.com; Mon, 31 Jul 2006 15:02: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 k6VGH3FI029821
	for <roots-in@roots-l.rootsweb.com>; Mon, 31 Jul 2006 12:17:03 -0400
Received: (from slist@localhost)
	by lists5.rootsweb.com (8.12.8/8.12.8) id k6VIte9p011871
	for roots-in@roots-l.rootsweb.com; Mon, 31 Jul 2006 12:55:40 -0600
X-Envelope-From: joanparker@intergate.com Mon Jul 31 12:55:40 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 k6VItejb011860
	for <ROOTS-M@lists5.rootsweb.com>; Mon, 31 Jul 2006 12:55:40 -0600
Received: from smtp9.trip.net (smtp9.trip.net [216.139.64.9])
	by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k6VItWmX004679
	for <ROOTS-M@rootsweb.com>; Mon, 31 Jul 2006 12:55:36 -0600
Received: from acer2e68c49b20 (2-pool1.ras02.mia01.dial.cogentco.com [206.148.140.2])
	by smtp9.trip.net (8.13.7/8.13.7) with SMTP id k6VItL9Y058513;
	Mon, 31 Jul 2006 13:55:24 -0500 (CDT)
Message-ID: <031001c6b4d2$c8f418d0$2f8c94ce@acer2e68c49b20>
From: "Joan Parker" <joanparker@intergate.com>
To: <ROOTS-M@rootsweb.com>
References: <412.4bd3a20.31feb252@aol.com>
Subject: Re: [ROOTS-L] Re: more on ancestry : incorrect ssdi listing
Date: Mon, 31 Jul 2006 14:42:42 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2869
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
X-Scanned-By: MIMEDefang 2.56 on 216.139.64.8
Sender: roots-in@roots-l.rootsweb.com

That has happened to me, person deceased in 1913 but that name showed up in 
SSDI anyway. Yes, the death date year was entered correctly, right from the tombstone.

Go figure.

Joanie
  ----- Original Message ----- 
  From: JYoung6180@aol.com 
  To: ROOTS-M@rootsweb.com 
  Sent: Sunday, July 30, 2006 9:09 PM
  Subject: [ROOTS-L] Re: more on ancestry 


  From: "Vicky Drake" dvicky@cox.net

  In all the changes to their home page I wonder if Ancestry's search engines  
  have been changed significantly.

  They certainly seem to less selective or  specific.

  Yesterday I put in Mary Hill  b. 1659  d   1712
  and among other choices that came back were about 75 hits in the  SSDI!

  I would expect SSDI hits if I didn't have a definite death  date
  but a 1712 death date seems a little out the realm of SSD
  ----
  Vicky-
   
  I just tried to duplicate/reproduce your results with May Hill born 1659  and 
  died 1712 on Ancestry's SSDI and got zero hits.  So Ancestry's SSDI is  not 
  returning about 75 hits based on the parameters you list above.
   
  Joan



