<?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: Obituaries, Naturalizations, City Directories, New Census Images and More</title>
	<atom:link href="http://blogs.ancestry.com/ancestry/2009/08/13/u-s-content-update-catching-up/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.ancestry.com/ancestry/2009/08/13/u-s-content-update-catching-up/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=u-s-content-update-catching-up</link>
	<description>The official blog of Ancestry.com</description>
	<lastBuildDate>Sat, 25 May 2013 04:38:25 +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/08/13/u-s-content-update-catching-up/#comment-40264</link>
		<dc:creator>Chris Lydiksen</dc:creator>
		<pubDate>Thu, 27 Aug 2009 16:28:05 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1896#comment-40264</guid>
		<description>#78 - Yes, Charles, there are more Native American collections in the works.  Here are some of the collections we have live now:

U.S. Indian Census Schedules, 1885-1940

U.S. Native American Enrollment Cards for the Five Civilized Tribes, 1898-1914

U.S. Native American Applications for Enrollment in Five Civilized Tribes, 1896</description>
		<content:encoded><![CDATA[<p>#78 &#8211; Yes, Charles, there are more Native American collections in the works.  Here are some of the collections we have live now:</p>
<p>U.S. Indian Census Schedules, 1885-1940</p>
<p>U.S. Native American Enrollment Cards for the Five Civilized Tribes, 1898-1914</p>
<p>U.S. Native American Applications for Enrollment in Five Civilized Tribes, 1896</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charles Hayward</title>
		<link>http://blogs.ancestry.com/ancestry/2009/08/13/u-s-content-update-catching-up/#comment-40202</link>
		<dc:creator>Charles Hayward</dc:creator>
		<pubDate>Wed, 26 Aug 2009 04:49:44 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1896#comment-40202</guid>
		<description>My question concerns the Native American Community.  I know there are tribal census available, but I have yet to find one on Ancestry.com.  In my family history background there are Native Americans and that right now is my big roadblock.  Can you comment on this as to whether or not any of these /
documents may become available.
Thank you,
Charles H.</description>
		<content:encoded><![CDATA[<p>My question concerns the Native American Community.  I know there are tribal census available, but I have yet to find one on Ancestry.com.  In my family history background there are Native Americans and that right now is my big roadblock.  Can you comment on this as to whether or not any of these /<br />
documents may become available.<br />
Thank you,<br />
Charles H.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Lydiksen</title>
		<link>http://blogs.ancestry.com/ancestry/2009/08/13/u-s-content-update-catching-up/#comment-40186</link>
		<dc:creator>Chris Lydiksen</dc:creator>
		<pubDate>Tue, 25 Aug 2009 21:50:13 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1896#comment-40186</guid>
		<description>#76 - If the problem is with the transcribed index, then the U.S. content product manager is the right person to address this.  If the problem is with the search tool, then the search product manager is the right person to address this.  As stated already today, the issue is currently under review.</description>
		<content:encoded><![CDATA[<p>#76 &#8211; If the problem is with the transcribed index, then the U.S. content product manager is the right person to address this.  If the problem is with the search tool, then the search product manager is the right person to address this.  As stated already today, the issue is currently under review.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BobNY</title>
		<link>http://blogs.ancestry.com/ancestry/2009/08/13/u-s-content-update-catching-up/#comment-40184</link>
		<dc:creator>BobNY</dc:creator>
		<pubDate>Tue, 25 Aug 2009 21:26:16 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1896#comment-40184</guid>
		<description>Chris,

Your responses to date on the simple question of your returning the ED descriptions for New York, New York County for the 1900 census that were there before you &quot;improved&quot;the index (since it was search index-related I mistakenly assumed this belonged to Anne) have been:

August 13, 2009 at 3:13 pm 
Bob, One of our genealogists is assessing the severity of the issue you’ve noted. More to come on this.
=========================
August 21, 2009 at 9:59 am 
#10 – Bob, The ED issue is being looked at.
=========================
August 21, 2009 at 10:45 am 
On the issue of missing EDs, below is the the I received from an internal source. If this is not accurate, please be patient with us as we need to better understand your question.

- Are you certain the ED descriptions were there previously for the cities you mention?

- Is it possible that you could be mistakenly confusing the A.com 1900 US Federal Census with either (1) the A.com 1920 US Federal Census, or (2) an unrelated Web site?
=========================
August 25, 2009 at 11:46 am 
#62 and #63 – I’ve forwarded your feedback to the expert on the case. We’ll get back to you again on this.
=========================
I originally asked this question on the ancestry comments board at Rootsweb in response to Anne&#039;s boast that &quot;Censuses that have been improved already are 1900 (index and images) and 1880 (images). We are currently working on the 1880 index . . .&quot;

As I wrote on 4/22:
This is a perfect example of ancestry not thinking through an issue. You may have improved the 1900 index, but you have made it absolutely useless to browsers. Prior to your improvements, if one were to browse a large city, e.g. New York or Chicago, there would be a description of the ED within the appropriate county.

Now there is nothing but a series of meaningless ED numbers with no description. Chicago is not as bad as New York. At least for Cook County - Chicago you maintained the Wards so there are only 20 or 30 meaningless ED numbers at a time. For New York, there are over 1,000 meaningless numbers in a virtually endless stream. And since you don&#039;t believe in leading zeros, they are not even in numerical order.

You have the information for each ED boundary since it was there before your &quot;improvement.&quot; Could you please put the data back?
===========================
Anne did not see fit to respond. So, I have another simple question:

Assuming a subscriber has an issue with the index used to search for U.S. content, who is responsible 

a) the Sr. Manager, Customer Experience
b) the Product Manager, Search
c) the Product Manager, U.S. Content
d) the Vice President of Content
e) the VP of Product for Ancestry
f) the generic product managers, (Freestone, Graham, et. al.)
g) none of the above

==========================</description>
		<content:encoded><![CDATA[<p>Chris,</p>
<p>Your responses to date on the simple question of your returning the ED descriptions for New York, New York County for the 1900 census that were there before you &#8220;improved&#8221;the index (since it was search index-related I mistakenly assumed this belonged to Anne) have been:</p>
<p>August 13, 2009 at 3:13 pm<br />
Bob, One of our genealogists is assessing the severity of the issue you’ve noted. More to come on this.<br />
=========================<br />
August 21, 2009 at 9:59 am<br />
#10 – Bob, The ED issue is being looked at.<br />
=========================<br />
August 21, 2009 at 10:45 am<br />
On the issue of missing EDs, below is the the I received from an internal source. If this is not accurate, please be patient with us as we need to better understand your question.</p>
<p>- Are you certain the ED descriptions were there previously for the cities you mention?</p>
<p>- Is it possible that you could be mistakenly confusing the A.com 1900 US Federal Census with either (1) the A.com 1920 US Federal Census, or (2) an unrelated Web site?<br />
=========================<br />
August 25, 2009 at 11:46 am<br />
#62 and #63 – I’ve forwarded your feedback to the expert on the case. We’ll get back to you again on this.<br />
=========================<br />
I originally asked this question on the ancestry comments board at Rootsweb in response to Anne&#8217;s boast that &#8220;Censuses that have been improved already are 1900 (index and images) and 1880 (images). We are currently working on the 1880 index . . .&#8221;</p>
<p>As I wrote on 4/22:<br />
This is a perfect example of ancestry not thinking through an issue. You may have improved the 1900 index, but you have made it absolutely useless to browsers. Prior to your improvements, if one were to browse a large city, e.g. New York or Chicago, there would be a description of the ED within the appropriate county.</p>
<p>Now there is nothing but a series of meaningless ED numbers with no description. Chicago is not as bad as New York. At least for Cook County &#8211; Chicago you maintained the Wards so there are only 20 or 30 meaningless ED numbers at a time. For New York, there are over 1,000 meaningless numbers in a virtually endless stream. And since you don&#8217;t believe in leading zeros, they are not even in numerical order.</p>
<p>You have the information for each ED boundary since it was there before your &#8220;improvement.&#8221; Could you please put the data back?<br />
===========================<br />
Anne did not see fit to respond. So, I have another simple question:</p>
<p>Assuming a subscriber has an issue with the index used to search for U.S. content, who is responsible </p>
<p>a) the Sr. Manager, Customer Experience<br />
b) the Product Manager, Search<br />
c) the Product Manager, U.S. Content<br />
d) the Vice President of Content<br />
e) the VP of Product for Ancestry<br />
f) the generic product managers, (Freestone, Graham, et. al.)<br />
g) none of the above</p>
<p>==========================</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Lydiksen</title>
		<link>http://blogs.ancestry.com/ancestry/2009/08/13/u-s-content-update-catching-up/#comment-40179</link>
		<dc:creator>Chris Lydiksen</dc:creator>
		<pubDate>Tue, 25 Aug 2009 20:18:45 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1896#comment-40179</guid>
		<description>#73 - Thanks Connie.  The 1860 census is being worked on as we speak and will be released with improved images and an improved index in coming months.</description>
		<content:encoded><![CDATA[<p>#73 &#8211; Thanks Connie.  The 1860 census is being worked on as we speak and will be released with improved images and an improved index in coming months.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MikeF</title>
		<link>http://blogs.ancestry.com/ancestry/2009/08/13/u-s-content-update-catching-up/#comment-40178</link>
		<dc:creator>MikeF</dc:creator>
		<pubDate>Tue, 25 Aug 2009 20:13:09 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1896#comment-40178</guid>
		<description>Chris,

On your #68, thanks for the further reply.  You said:

--

&quot;#58 – Mike, I cannot reveal the organizations, states, counties, etc. that we are working with to digitize records. It will need to suffice to say that we are working with many, many organizations.&quot;

--

Why can you not reveal the repositories you are working with?  Is it because your marketing dept. does not wish you to?  Surely there is no need for secrecy on the repository side is there?  Since most of those are publicly funded agencies and subject to open records laws most likely, then if I were to inquire of a repository I cannot see them refusing to tell me if they currently had a project with Ancestry.  Or are you in fact saying these state repositories do want confidentiality until your marketing dept. hypes the release of a new database?

Also again, if there are repositories who are *totally* uncooperative, then I think not only does Ancestry not lose anything by naming them as such, but also that it helps by customers then knowing where to apply political pressure to induce future cooperation.

MikeF</description>
		<content:encoded><![CDATA[<p>Chris,</p>
<p>On your #68, thanks for the further reply.  You said:</p>
<p>&#8211;</p>
<p>&#8220;#58 – Mike, I cannot reveal the organizations, states, counties, etc. that we are working with to digitize records. It will need to suffice to say that we are working with many, many organizations.&#8221;</p>
<p>&#8211;</p>
<p>Why can you not reveal the repositories you are working with?  Is it because your marketing dept. does not wish you to?  Surely there is no need for secrecy on the repository side is there?  Since most of those are publicly funded agencies and subject to open records laws most likely, then if I were to inquire of a repository I cannot see them refusing to tell me if they currently had a project with Ancestry.  Or are you in fact saying these state repositories do want confidentiality until your marketing dept. hypes the release of a new database?</p>
<p>Also again, if there are repositories who are *totally* uncooperative, then I think not only does Ancestry not lose anything by naming them as such, but also that it helps by customers then knowing where to apply political pressure to induce future cooperation.</p>
<p>MikeF</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Connie</title>
		<link>http://blogs.ancestry.com/ancestry/2009/08/13/u-s-content-update-catching-up/#comment-40177</link>
		<dc:creator>Connie</dc:creator>
		<pubDate>Tue, 25 Aug 2009 19:18:40 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1896#comment-40177</guid>
		<description>While you&#039;re improving census records, you might want to correct a significant error in 1860 Washington State.  You have the people who were living in Sawamish Co. listed as living in Snohomish Co.  Not the same place (now or then); someone needs to check some of your own publications like Red Book!  Sawamish Co. was renamed Mason Co. in 1864.</description>
		<content:encoded><![CDATA[<p>While you&#8217;re improving census records, you might want to correct a significant error in 1860 Washington State.  You have the people who were living in Sawamish Co. listed as living in Snohomish Co.  Not the same place (now or then); someone needs to check some of your own publications like Red Book!  Sawamish Co. was renamed Mason Co. in 1864.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Lydiksen</title>
		<link>http://blogs.ancestry.com/ancestry/2009/08/13/u-s-content-update-catching-up/#comment-40174</link>
		<dc:creator>Chris Lydiksen</dc:creator>
		<pubDate>Tue, 25 Aug 2009 17:49:50 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1896#comment-40174</guid>
		<description>#67 - I&#039;ve forwarded this issue to the appropriate person.  Thank you for providing a specific link.</description>
		<content:encoded><![CDATA[<p>#67 &#8211; I&#8217;ve forwarded this issue to the appropriate person.  Thank you for providing a specific link.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Lydiksen</title>
		<link>http://blogs.ancestry.com/ancestry/2009/08/13/u-s-content-update-catching-up/#comment-40173</link>
		<dc:creator>Chris Lydiksen</dc:creator>
		<pubDate>Tue, 25 Aug 2009 17:46:05 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1896#comment-40173</guid>
		<description>#62 and #63 - I&#039;ve forwarded your feedback to the expert on the case.  We&#039;ll get back to you again on this.</description>
		<content:encoded><![CDATA[<p>#62 and #63 &#8211; I&#8217;ve forwarded your feedback to the expert on the case.  We&#8217;ll get back to you again on this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Lydiksen</title>
		<link>http://blogs.ancestry.com/ancestry/2009/08/13/u-s-content-update-catching-up/#comment-40172</link>
		<dc:creator>Chris Lydiksen</dc:creator>
		<pubDate>Tue, 25 Aug 2009 17:44:19 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/?p=1896#comment-40172</guid>
		<description>#61 - The 1850 U.S. Census is currently being worked on and will release with improved images and indexes in the near future.</description>
		<content:encoded><![CDATA[<p>#61 &#8211; The 1850 U.S. Census is currently being worked on and will release with improved images and indexes in the near future.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
