<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: U.S. City Directories: One Database, a Billion Records, and a Lot of Answers</title>
	<atom:link href="http://blogs.ancestry.com/ancestry/2012/04/19/u-s-city-directories-one-database-a-billion-records-and-a-lot-of-answers/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.ancestry.com/ancestry/2012/04/19/u-s-city-directories-one-database-a-billion-records-and-a-lot-of-answers/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=u-s-city-directories-one-database-a-billion-records-and-a-lot-of-answers</link>
	<description>The official blog of Ancestry.com</description>
	<lastBuildDate>Wed, 19 Jun 2013 12:17:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Genealogy News Corral, Jan. 7-11</title>
		<link>http://blogs.ancestry.com/ancestry/2012/04/19/u-s-city-directories-one-database-a-billion-records-and-a-lot-of-answers/#comment-63135</link>
		<dc:creator>Genealogy News Corral, Jan. 7-11</dc:creator>
		<pubDate>Sun, 13 Jan 2013 07:00:54 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=7383#comment-63135</guid>
		<description>[...] US census collections (correcting some Indiana birth places that were keyed incorrectly) and its City Directories. In addition, Ancestry continues with its indexing of information for the 1940 US census to make it [...]</description>
		<content:encoded><![CDATA[<p>[...] US census collections (correcting some Indiana birth places that were keyed incorrectly) and its City Directories. In addition, Ancestry continues with its indexing of information for the 1940 US census to make it [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Genealogy Path &#8211; Ancestry.com adjusts errors in 1850 census index</title>
		<link>http://blogs.ancestry.com/ancestry/2012/04/19/u-s-city-directories-one-database-a-billion-records-and-a-lot-of-answers/#comment-63004</link>
		<dc:creator>Genealogy Path &#8211; Ancestry.com adjusts errors in 1850 census index</dc:creator>
		<pubDate>Fri, 11 Jan 2013 00:10:43 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=7383#comment-63004</guid>
		<description>[...] our current collections better is important to us. For example, we have recently updated our&#160;City Directories&#160;to include even more information and are still indexing information for the 1940 US Census to [...]</description>
		<content:encoded><![CDATA[<p>[...] our current collections better is important to us. For example, we have recently updated our&nbsp;City Directories&nbsp;to include even more information and are still indexing information for the 1940 US Census to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joan Lottner</title>
		<link>http://blogs.ancestry.com/ancestry/2012/04/19/u-s-city-directories-one-database-a-billion-records-and-a-lot-of-answers/#comment-56385</link>
		<dc:creator>Joan Lottner</dc:creator>
		<pubDate>Wed, 25 Jul 2012 01:51:08 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=7383#comment-56385</guid>
		<description>I have been searching the Grand Rapids and Detroit, Michigan databases and am extremely disappointed with the results.  I have had to browse almost all of them and have made dozens of corrections so far when able.  Dozens more I have not been able to correct as the indexing was so incomplete as to make correction impossible.  Visual transcribing by the computer (as was done in the beta directories here) looks to be extremely inaccurate and in desperate need of major tweeking.  Why Ancestry are you not using World Connect to fix this for now until you find a better solution?  I know there a quite a few things on there now, but I have found the directories a very exciting new addition but they need to be way more accurate to be of any use to anyone.  There are many that are incompletely scanned also and I am wondering if it is because that is all Ancestry had to scan or if the scanning was not completed due to this being simply a beta test version right now.  Will the missing pages be scanned in later once all the bugs are worked out?</description>
		<content:encoded><![CDATA[<p>I have been searching the Grand Rapids and Detroit, Michigan databases and am extremely disappointed with the results.  I have had to browse almost all of them and have made dozens of corrections so far when able.  Dozens more I have not been able to correct as the indexing was so incomplete as to make correction impossible.  Visual transcribing by the computer (as was done in the beta directories here) looks to be extremely inaccurate and in desperate need of major tweeking.  Why Ancestry are you not using World Connect to fix this for now until you find a better solution?  I know there a quite a few things on there now, but I have found the directories a very exciting new addition but they need to be way more accurate to be of any use to anyone.  There are many that are incompletely scanned also and I am wondering if it is because that is all Ancestry had to scan or if the scanning was not completed due to this being simply a beta test version right now.  Will the missing pages be scanned in later once all the bugs are worked out?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sara Savel</title>
		<link>http://blogs.ancestry.com/ancestry/2012/04/19/u-s-city-directories-one-database-a-billion-records-and-a-lot-of-answers/#comment-55538</link>
		<dc:creator>Sara Savel</dc:creator>
		<pubDate>Fri, 25 May 2012 17:03:20 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=7383#comment-55538</guid>
		<description>The Detroit city directories are grossly incomplete, especially the midcentury ones. Many of them only have the first few hundred pages, or just a incomplete street guide index.  Detroit was a major American city up until the 80&#039;S,  with a large population.  The city directories should be complete.  I know they are available, as I have seen the original directories in person at a few genealogical libraries.</description>
		<content:encoded><![CDATA[<p>The Detroit city directories are grossly incomplete, especially the midcentury ones. Many of them only have the first few hundred pages, or just a incomplete street guide index.  Detroit was a major American city up until the 80&#8242;S,  with a large population.  The city directories should be complete.  I know they are available, as I have seen the original directories in person at a few genealogical libraries.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Denise</title>
		<link>http://blogs.ancestry.com/ancestry/2012/04/19/u-s-city-directories-one-database-a-billion-records-and-a-lot-of-answers/#comment-55518</link>
		<dc:creator>Denise</dc:creator>
		<pubDate>Thu, 24 May 2012 13:19:21 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=7383#comment-55518</guid>
		<description>The city directories have been very interesting in finding more about where my family lived in Hartford, CT during the thirties and forties.  However I have had to BROWSE through the files since the indexes are mostly useless for many of the years.  Whoever did the indexing for this town (Hartford, Connecticut) mus thave just hit random keys to page through the names, rendering any search useless.  It be be very worthwhile to pass this information along to whomever handles the review of the index results BEFORE publishing to the web and it would be even better if I could report the problem directly from the image.</description>
		<content:encoded><![CDATA[<p>The city directories have been very interesting in finding more about where my family lived in Hartford, CT during the thirties and forties.  However I have had to BROWSE through the files since the indexes are mostly useless for many of the years.  Whoever did the indexing for this town (Hartford, Connecticut) mus thave just hit random keys to page through the names, rendering any search useless.  It be be very worthwhile to pass this information along to whomever handles the review of the index results BEFORE publishing to the web and it would be even better if I could report the problem directly from the image.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Diane</title>
		<link>http://blogs.ancestry.com/ancestry/2012/04/19/u-s-city-directories-one-database-a-billion-records-and-a-lot-of-answers/#comment-55116</link>
		<dc:creator>Diane</dc:creator>
		<pubDate>Wed, 25 Apr 2012 02:00:59 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=7383#comment-55116</guid>
		<description>The US Directories Beta are a great thing unfortunately the transcriptions for the Detroit Directories are atrocious.  Browsing is the only practical way to search them.  Also, the directories are incomplete. Either missing half the names (from N-Z) or just having random groups of the street indexes. The 1940 Detroit directory has only 255 pages of street indexing (back matter)!!!</description>
		<content:encoded><![CDATA[<p>The US Directories Beta are a great thing unfortunately the transcriptions for the Detroit Directories are atrocious.  Browsing is the only practical way to search them.  Also, the directories are incomplete. Either missing half the names (from N-Z) or just having random groups of the street indexes. The 1940 Detroit directory has only 255 pages of street indexing (back matter)!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michele</title>
		<link>http://blogs.ancestry.com/ancestry/2012/04/19/u-s-city-directories-one-database-a-billion-records-and-a-lot-of-answers/#comment-55108</link>
		<dc:creator>Michele</dc:creator>
		<pubDate>Tue, 24 Apr 2012 15:38:43 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=7383#comment-55108</guid>
		<description>I would suggest using the browse feature in the city directories if you can&#039;t find someone in a search and you know where they lived. This also lets you know which scans are incomplete. I&#039;ve come across several years where there is only the first or second half of the alphabet. So frustrating. However, I am very happy with the additional directories that have been posted!</description>
		<content:encoded><![CDATA[<p>I would suggest using the browse feature in the city directories if you can&#8217;t find someone in a search and you know where they lived. This also lets you know which scans are incomplete. I&#8217;ve come across several years where there is only the first or second half of the alphabet. So frustrating. However, I am very happy with the additional directories that have been posted!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Judy Holzwart</title>
		<link>http://blogs.ancestry.com/ancestry/2012/04/19/u-s-city-directories-one-database-a-billion-records-and-a-lot-of-answers/#comment-55102</link>
		<dc:creator>Judy Holzwart</dc:creator>
		<pubDate>Tue, 24 Apr 2012 02:14:29 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=7383#comment-55102</guid>
		<description>Thanks to the new directories posted, I was able to narrow down, to within a year, when my gggrandfather, Frederick, died. Thanks so much!</description>
		<content:encoded><![CDATA[<p>Thanks to the new directories posted, I was able to narrow down, to within a year, when my gggrandfather, Frederick, died. Thanks so much!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jade</title>
		<link>http://blogs.ancestry.com/ancestry/2012/04/19/u-s-city-directories-one-database-a-billion-records-and-a-lot-of-answers/#comment-55098</link>
		<dc:creator>Jade</dc:creator>
		<pubDate>Mon, 23 Apr 2012 21:29:33 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=7383#comment-55098</guid>
		<description>Most people in USA did not live in cities until at least the 1940s.

This crowing about City Directories is a lot like the foolish blog statement that &quot;most of our ancestors lived in London . . . .&quot; in 1911!!!!  My last London ancestor left there before 1654.

All of us could use more historical understanding.</description>
		<content:encoded><![CDATA[<p>Most people in USA did not live in cities until at least the 1940s.</p>
<p>This crowing about City Directories is a lot like the foolish blog statement that &#8220;most of our ancestors lived in London . . . .&#8221; in 1911!!!!  My last London ancestor left there before 1654.</p>
<p>All of us could use more historical understanding.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shelly</title>
		<link>http://blogs.ancestry.com/ancestry/2012/04/19/u-s-city-directories-one-database-a-billion-records-and-a-lot-of-answers/#comment-55092</link>
		<dc:creator>Shelly</dc:creator>
		<pubDate>Mon, 23 Apr 2012 16:27:33 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=7383#comment-55092</guid>
		<description>I have found the new US City Directories Beta database to be helpful and hope it continues to expand, but I have encountered a problem.  Any time I try to do an exact search with a person&#039;s name &amp; their state, it tells me that there are no results.  If I search for just the name, it gives me lots of results from the same state (in addition to multiple other states).  I hope this will be fixed when it passes the Beta stage.</description>
		<content:encoded><![CDATA[<p>I have found the new US City Directories Beta database to be helpful and hope it continues to expand, but I have encountered a problem.  Any time I try to do an exact search with a person&#8217;s name &amp; their state, it tells me that there are no results.  If I search for just the name, it gives me lots of results from the same state (in addition to multiple other states).  I hope this will be fixed when it passes the Beta stage.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
