Comments on: Using Ancestry: Getting Closer to the Data, by Juliana Smith http://blogs.ancestry.com/circle/?p=1817 The Place for Ancestral Connections Sun, 29 Nov 2009 18:27:32 +0000 http://wordpress.org/?v=2.0.1 by: Juliana http://blogs.ancestry.com/circle/?p=1817#comment-212530 Wed, 12 Sep 2007 16:50:26 +0000 http://blogs.ancestry.com/circle/?p=1817#comment-212530 Thanks Bill! I did follow up (as we'll discuss in next week's column) and it turns out that Geo?? is actually Jno. in the images. This complicates things a bit since there is a George in our Tobin family, but I'm not aware of a John. This family just loves to throw me the curve balls! ;) More to come... Juliana Thanks Bill! I did follow up (as we’ll discuss in next week’s column) and it turns out that Geo?? is actually Jno. in the images. This complicates things a bit since there is a George in our Tobin family, but I’m not aware of a John. This family just loves to throw me the curve balls! ;)

More to come…
Juliana

]]> by: Bill Brankowitz http://blogs.ancestry.com/circle/?p=1817#comment-212112 Tue, 11 Sep 2007 21:34:11 +0000 http://blogs.ancestry.com/circle/?p=1817#comment-212112 Juliana Smith, Check to see if "Geo" is not "Tho"...this may explain your Thomas...he may not be missing at all. Just a thought...I've seen this problem before! Bill Juliana Smith,

Check to see if “Geo” is not “Tho”…this may explain your Thomas…he may not be missing at all. Just a thought…I’ve seen this problem before!

Bill

]]> by: mikef http://blogs.ancestry.com/circle/?p=1817#comment-212001 Tue, 11 Sep 2007 06:39:10 +0000 http://blogs.ancestry.com/circle/?p=1817#comment-212001 Hi, A search ability that I think is very needed is one to be able to narrow searches by a customizable time period, and by being able to prioritize search dimensions. At present you can specify up to 20 years one side or other of a birth date or other vital date. But that isn't really sufficient. For example, if on the global search of all databases you enter John Doe and that he died in such a year and such and such a place, you will get the very closest census matches and then less close ones, followed by the closes family tree matches and then less close ones, etc. Whereas I and doubtless others would like to see the results ordered first by a time period, then by locality, etc. With census searches for example, I would like to see the closest time/locality results for the exact spelling input, and then those for variant spellings, *before* seeing any outside the preferred time/locality frames. While I realize you can make a place of residence exact on the global search page, and thus get some of this functionality, it is totally lacking on database specific search pages like ones for a specific federal census year, where again you can only specify a 20 year interval both ways. Mike Hi,

A search ability that I think is very needed is one to be able to narrow searches by a customizable time period, and by being able to prioritize search dimensions. At present you can specify up to 20 years one side or other of a birth date or other vital date. But that isn’t really sufficient. For example, if on the global search of all databases you enter John Doe and that he died in such a year and such and such a place, you will get the very closest census matches and then less close ones, followed by the closes family tree matches and then less close ones, etc. Whereas I and doubtless others would like to see the results ordered first by a time period, then by locality, etc. With census searches for example, I would like to see the closest time/locality results for the exact spelling input, and then those for variant spellings, *before* seeing any outside the preferred time/locality frames. While I realize you can make a place of residence exact on the global search page, and thus get some of this functionality, it is totally lacking on database specific search pages like ones for a specific federal census year, where again you can only specify a 20 year interval both ways.

Mike

]]>