<?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. Content Update: 1880 Census Images, 1935-1945 City Directories, Improved Obituaries Collection &amp; Iowa State Census Fix</title>
	<atom:link href="http://blogs.ancestry.com/ancestry/2009/03/12/us-content-update-1880-1940-obituaries-iowa/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.ancestry.com/ancestry/2009/03/12/us-content-update-1880-1940-obituaries-iowa/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=us-content-update-1880-1940-obituaries-iowa</link>
	<description>The official blog of Ancestry.com</description>
	<lastBuildDate>Sun, 19 May 2013 21:29:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Chris Lydiksen</title>
		<link>http://blogs.ancestry.com/ancestry/2009/03/12/us-content-update-1880-1940-obituaries-iowa/#comment-37151</link>
		<dc:creator>Chris Lydiksen</dc:creator>
		<pubDate>Thu, 26 Mar 2009 21:50:24 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/03/12/us-content-update-1880-1940-obituaries-iowa/#comment-37151</guid>
		<description>Ida, please visit &lt;a href=&quot;http://search.ancestry.com/search/CardCatalog.aspx#ccat=hc%3D25%26dbSort%3D3%26filter%3D1*2%26&quot; rel=&quot;nofollow&quot;&gt;this page&lt;/a&gt; to see the U.S. Content that has been released recently:


Please visit &lt;a href=&quot;http://landing.ancestry.com/comingsoon/?o_iid=37217&amp;o_lid=37217&quot; rel=&quot;nofollow&quot;&gt;this page&lt;/a&gt; to see more of what&#039;s coming: 
</description>
		<content:encoded><![CDATA[<p>Ida, please visit <a href="http://search.ancestry.com/search/CardCatalog.aspx#ccat=hc%3D25%26dbSort%3D3%26filter%3D1*2%26" rel="nofollow">this page</a> to see the U.S. Content that has been released recently:</p>
<p>Please visit <a href="http://landing.ancestry.com/comingsoon/?o_iid=37217&#038;o_lid=37217" rel="nofollow">this page</a> to see more of what&#8217;s coming: </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ida French</title>
		<link>http://blogs.ancestry.com/ancestry/2009/03/12/us-content-update-1880-1940-obituaries-iowa/#comment-37126</link>
		<dc:creator>Ida French</dc:creator>
		<pubDate>Thu, 26 Mar 2009 12:32:21 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/03/12/us-content-update-1880-1940-obituaries-iowa/#comment-37126</guid>
		<description>Chris I hope I see some new U.S. updates soon.  I only have two weeks left on my current subscription and all I see is a ton of updates for other countries and very little new stuff for the U.S. Family search and U.S. Genweb are starting to have more of what we want than Ancestry and those sites are free.</description>
		<content:encoded><![CDATA[<p>Chris I hope I see some new U.S. updates soon.  I only have two weeks left on my current subscription and all I see is a ton of updates for other countries and very little new stuff for the U.S. Family search and U.S. Genweb are starting to have more of what we want than Ancestry and those sites are free.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Lydiksen</title>
		<link>http://blogs.ancestry.com/ancestry/2009/03/12/us-content-update-1880-1940-obituaries-iowa/#comment-37107</link>
		<dc:creator>Chris Lydiksen</dc:creator>
		<pubDate>Wed, 25 Mar 2009 23:19:06 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/03/12/us-content-update-1880-1940-obituaries-iowa/#comment-37107</guid>
		<description>All, the city directory issue where the first image shown is not the first page of the city directory (or where the last image is not the last page), has been mostly fixed (by mostly I mean most of the city directories are displaying as you would expect in the browse now).  This was not an easy or quick fix.  We are aware of some lingering issues that will take longer to sort out.  

Again, these directories were filmed in such a way that some individual directories ran across two rolls of microfilm.  The larger project consists of over 8,000 rolls.  There are thousands more city directories to come and we have adjusted the requirements to catch and fix this issue in subsequent batches.

Thanks for your patience on this.

One more thing.  We extract names, dates and places from free-text (OCR-captured typewritten text as with city directories, newspapers, books, etc.)  When searching free-text databases on Ancestry.com, you can search just for extracted names using the names fields.  However, only names that are included in our name dictionaries are extracted.  Our name dictionary does not include every possible given name or surname in history.  &quot;Lydiksen&quot; is not even included.  This is done to minimize false hits on name searches.  That said, there is a project to augment these dictionaries.

So, and many of you probably already know this, if you are not getting results using the name fields, try entering the name in the keyword field.  That will search ALL captured text, including names, dates and places (this is how I found my grandparents in New Jersey directories).</description>
		<content:encoded><![CDATA[<p>All, the city directory issue where the first image shown is not the first page of the city directory (or where the last image is not the last page), has been mostly fixed (by mostly I mean most of the city directories are displaying as you would expect in the browse now).  This was not an easy or quick fix.  We are aware of some lingering issues that will take longer to sort out.  </p>
<p>Again, these directories were filmed in such a way that some individual directories ran across two rolls of microfilm.  The larger project consists of over 8,000 rolls.  There are thousands more city directories to come and we have adjusted the requirements to catch and fix this issue in subsequent batches.</p>
<p>Thanks for your patience on this.</p>
<p>One more thing.  We extract names, dates and places from free-text (OCR-captured typewritten text as with city directories, newspapers, books, etc.)  When searching free-text databases on Ancestry.com, you can search just for extracted names using the names fields.  However, only names that are included in our name dictionaries are extracted.  Our name dictionary does not include every possible given name or surname in history.  &#8220;Lydiksen&#8221; is not even included.  This is done to minimize false hits on name searches.  That said, there is a project to augment these dictionaries.</p>
<p>So, and many of you probably already know this, if you are not getting results using the name fields, try entering the name in the keyword field.  That will search ALL captured text, including names, dates and places (this is how I found my grandparents in New Jersey directories).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Lydiksen</title>
		<link>http://blogs.ancestry.com/ancestry/2009/03/12/us-content-update-1880-1940-obituaries-iowa/#comment-37101</link>
		<dc:creator>Chris Lydiksen</dc:creator>
		<pubDate>Wed, 25 Mar 2009 23:01:30 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/03/12/us-content-update-1880-1940-obituaries-iowa/#comment-37101</guid>
		<description>Thanks to all of you who&#039;ve said thanks.

Bud, the 1930 census images are going to be replaced under the TGN-FamilySearch project.  1930 will likely be the last census in this project.

Carol, at present, you can correct names on the site, but not other fields.  That functionality is on the roadmap for new features.

John, concerning FTM, you may want to add a comment to the FTM portion of this blog.  I&#039;ll forward your issue to the FTM team.

Caroline, please contact customer service at 1-800-Ancestry.</description>
		<content:encoded><![CDATA[<p>Thanks to all of you who&#8217;ve said thanks.</p>
<p>Bud, the 1930 census images are going to be replaced under the TGN-FamilySearch project.  1930 will likely be the last census in this project.</p>
<p>Carol, at present, you can correct names on the site, but not other fields.  That functionality is on the roadmap for new features.</p>
<p>John, concerning FTM, you may want to add a comment to the FTM portion of this blog.  I&#8217;ll forward your issue to the FTM team.</p>
<p>Caroline, please contact customer service at 1-800-Ancestry.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Caroline M. Burke</title>
		<link>http://blogs.ancestry.com/ancestry/2009/03/12/us-content-update-1880-1940-obituaries-iowa/#comment-37050</link>
		<dc:creator>Caroline M. Burke</dc:creator>
		<pubDate>Mon, 23 Mar 2009 23:23:44 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/03/12/us-content-update-1880-1940-obituaries-iowa/#comment-37050</guid>
		<description>Why is it, when I log into Ancestry 
New home page comes up, 
14 days trial?

I have account with!
Please check and reply.

ccburke2@sbcglobal.net</description>
		<content:encoded><![CDATA[<p>Why is it, when I log into Ancestry<br />
New home page comes up,<br />
14 days trial?</p>
<p>I have account with!<br />
Please check and reply.</p>
<p><a href="mailto:ccburke2@sbcglobal.net">ccburke2@sbcglobal.net</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Covington</title>
		<link>http://blogs.ancestry.com/ancestry/2009/03/12/us-content-update-1880-1940-obituaries-iowa/#comment-37048</link>
		<dc:creator>John Covington</dc:creator>
		<pubDate>Mon, 23 Mar 2009 22:12:22 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/03/12/us-content-update-1880-1940-obituaries-iowa/#comment-37048</guid>
		<description>If almost 99% of the 1880 census images have been replaced, then I must have the 1% that does not update with an image of the census page when I use the merge function in FTM 2009. Any comment as to why there are no images merged?</description>
		<content:encoded><![CDATA[<p>If almost 99% of the 1880 census images have been replaced, then I must have the 1% that does not update with an image of the census page when I use the merge function in FTM 2009. Any comment as to why there are no images merged?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carol Jenkins</title>
		<link>http://blogs.ancestry.com/ancestry/2009/03/12/us-content-update-1880-1940-obituaries-iowa/#comment-36999</link>
		<dc:creator>Carol Jenkins</dc:creator>
		<pubDate>Sat, 21 Mar 2009 19:11:26 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/03/12/us-content-update-1880-1940-obituaries-iowa/#comment-36999</guid>
		<description>I&#039;m glad to see all the additions but please tell me how to make corrections about my mother on the obituary collection.  The obit content is fine, it&#039;s the dates of her birth and death that are totally wrong in the indexing.</description>
		<content:encoded><![CDATA[<p>I&#8217;m glad to see all the additions but please tell me how to make corrections about my mother on the obituary collection.  The obit content is fine, it&#8217;s the dates of her birth and death that are totally wrong in the indexing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sarah</title>
		<link>http://blogs.ancestry.com/ancestry/2009/03/12/us-content-update-1880-1940-obituaries-iowa/#comment-36958</link>
		<dc:creator>Sarah</dc:creator>
		<pubDate>Fri, 20 Mar 2009 11:11:29 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/03/12/us-content-update-1880-1940-obituaries-iowa/#comment-36958</guid>
		<description>I recently came across your blog and have been reading along. I thought I would leave my first comment. I don&#039;t know what to say except that I have enjoyed reading. Nice blog. I will keep visiting this blog very often.

Sarah

http://www.lyricsdigs.com</description>
		<content:encoded><![CDATA[<p>I recently came across your blog and have been reading along. I thought I would leave my first comment. I don&#8217;t know what to say except that I have enjoyed reading. Nice blog. I will keep visiting this blog very often.</p>
<p>Sarah</p>
<p><a href="http://www.lyricsdigs.com" rel="nofollow">http://www.lyricsdigs.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bud Dorr</title>
		<link>http://blogs.ancestry.com/ancestry/2009/03/12/us-content-update-1880-1940-obituaries-iowa/#comment-36922</link>
		<dc:creator>Bud Dorr</dc:creator>
		<pubDate>Thu, 19 Mar 2009 14:29:36 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/03/12/us-content-update-1880-1940-obituaries-iowa/#comment-36922</guid>
		<description>Regarding upgrading the census images, I think the 1930 census images need to be replaced with clear images. The images for 1930 look as if they were photographed under water. I often have to go to Genealogy.com to read an entry. Forgive me if you&#039;ve treated this problem before.

Bud Dorr
Casco, Maine</description>
		<content:encoded><![CDATA[<p>Regarding upgrading the census images, I think the 1930 census images need to be replaced with clear images. The images for 1930 look as if they were photographed under water. I often have to go to Genealogy.com to read an entry. Forgive me if you&#8217;ve treated this problem before.</p>
<p>Bud Dorr<br />
Casco, Maine</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ida French</title>
		<link>http://blogs.ancestry.com/ancestry/2009/03/12/us-content-update-1880-1940-obituaries-iowa/#comment-36877</link>
		<dc:creator>Ida French</dc:creator>
		<pubDate>Wed, 18 Mar 2009 01:21:26 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2009/03/12/us-content-update-1880-1940-obituaries-iowa/#comment-36877</guid>
		<description>Chris,  Thanks for getting back with us on the first and last page issue.</description>
		<content:encoded><![CDATA[<p>Chris,  Thanks for getting back with us on the first and last page issue.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
