<?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: Maintenance to U.S. Census, Tennessee Marriages and more</title>
	<atom:link href="http://blogs.ancestry.com/ancestry/2008/07/25/us-content-maintenance-update-us-census-tennessee-marriages-and-more/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.ancestry.com/ancestry/2008/07/25/us-content-maintenance-update-us-census-tennessee-marriages-and-more/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=us-content-maintenance-update-us-census-tennessee-marriages-and-more</link>
	<description>The official blog of Ancestry.com</description>
	<lastBuildDate>Tue, 21 May 2013 21:32:32 +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/2008/07/25/us-content-maintenance-update-us-census-tennessee-marriages-and-more/#comment-18685</link>
		<dc:creator>Chris Lydiksen</dc:creator>
		<pubDate>Tue, 02 Sep 2008 05:08:47 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2008/07/25/us-content-maintenance-update-us-census-tennessee-marriages-and-more/#comment-18685</guid>
		<description>Responding to more comments relevant to the topic at hand:

13) kkandtc, we&#039;re constantly working to improve quality.  That said, there is an optimal level for keying accuracy.  I appreciate feedback like this so that I can use it to research and help improve quality.  

14) Reed, I won&#039;t promise to post an answer back here, but I do promise to look into this.  Thanks.

15) Marjorie, please send me the link to the record.

16) Julia, thanks for reporting this.  It will be prioritized against all other U.S. projects.

19) JMaule, More often than not, such problems are unforeseen and technical, and not the result of a conscious decision by a human to disable databases.  We know how important access to the data on our servers is and we strive to continuously improve.

22) Rich, thanks for your kind remarks and input.

23) Shirley, please send me a link to a specific record in question.  Thanks for your feedback.</description>
		<content:encoded><![CDATA[<p>Responding to more comments relevant to the topic at hand:</p>
<p>13) kkandtc, we&#8217;re constantly working to improve quality.  That said, there is an optimal level for keying accuracy.  I appreciate feedback like this so that I can use it to research and help improve quality.  </p>
<p>14) Reed, I won&#8217;t promise to post an answer back here, but I do promise to look into this.  Thanks.</p>
<p>15) Marjorie, please send me the link to the record.</p>
<p>16) Julia, thanks for reporting this.  It will be prioritized against all other U.S. projects.</p>
<p>19) JMaule, More often than not, such problems are unforeseen and technical, and not the result of a conscious decision by a human to disable databases.  We know how important access to the data on our servers is and we strive to continuously improve.</p>
<p>22) Rich, thanks for your kind remarks and input.</p>
<p>23) Shirley, please send me a link to a specific record in question.  Thanks for your feedback.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Lydiksen</title>
		<link>http://blogs.ancestry.com/ancestry/2008/07/25/us-content-maintenance-update-us-census-tennessee-marriages-and-more/#comment-18678</link>
		<dc:creator>Chris Lydiksen</dc:creator>
		<pubDate>Tue, 02 Sep 2008 04:24:55 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2008/07/25/us-content-maintenance-update-us-census-tennessee-marriages-and-more/#comment-18678</guid>
		<description>6) Don, I&#039;ve done some research on the WWI Draft images.  Some images were produced many years ago with period technology.  These images have been added to the list of those that could benefit from being re-scanned.  Thank you.</description>
		<content:encoded><![CDATA[<p>6) Don, I&#8217;ve done some research on the WWI Draft images.  Some images were produced many years ago with period technology.  These images have been added to the list of those that could benefit from being re-scanned.  Thank you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shirley Starks</title>
		<link>http://blogs.ancestry.com/ancestry/2008/07/25/us-content-maintenance-update-us-census-tennessee-marriages-and-more/#comment-18227</link>
		<dc:creator>Shirley Starks</dc:creator>
		<pubDate>Fri, 29 Aug 2008 13:16:19 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2008/07/25/us-content-maintenance-update-us-census-tennessee-marriages-and-more/#comment-18227</guid>
		<description>Census:
We are so fortunate to have this resource. I use it a lot. 

Please help those of us who know a name is there, but indexing is amiss. 

I am often finding difficulty in a census search.  
Known Profile:
Surname known
State of Residence known.
County known.
................ 
A while back: 
I could fill in certain search blanks for the census, say, 1880. I found one lady with nothing more than a first name, birth year &amp; 
place. 
........ 
Recently, I was looking for a Ridenour surname in 1910.  Known to be living in Clinton Co, MI. Not finding him by name, I sought to look at every Ridenour family in that Clinton Co, MI.  
..........
What was offered by Ancestry... 
I had to begin with all of that name in Arkansas and go through EVERY state in alphabetical order until I came to MICHIGAN. Then I had to wade through every county in that state!  How fortunate that the county began with a &#039;C&#039;!! 

I&#039;ve had to do this procedure with VIRGINIA..! grrr!</description>
		<content:encoded><![CDATA[<p>Census:<br />
We are so fortunate to have this resource. I use it a lot. </p>
<p>Please help those of us who know a name is there, but indexing is amiss. </p>
<p>I am often finding difficulty in a census search.<br />
Known Profile:<br />
Surname known<br />
State of Residence known.<br />
County known.<br />
&#8230;&#8230;&#8230;&#8230;&#8230;.<br />
A while back:<br />
I could fill in certain search blanks for the census, say, 1880. I found one lady with nothing more than a first name, birth year &amp;<br />
place.<br />
&#8230;&#8230;..<br />
Recently, I was looking for a Ridenour surname in 1910.  Known to be living in Clinton Co, MI. Not finding him by name, I sought to look at every Ridenour family in that Clinton Co, MI.<br />
&#8230;&#8230;&#8230;.<br />
What was offered by Ancestry&#8230;<br />
I had to begin with all of that name in Arkansas and go through EVERY state in alphabetical order until I came to MICHIGAN. Then I had to wade through every county in that state!  How fortunate that the county began with a &#8216;C&#8217;!! </p>
<p>I&#8217;ve had to do this procedure with VIRGINIA..! grrr!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich Hrazanek</title>
		<link>http://blogs.ancestry.com/ancestry/2008/07/25/us-content-maintenance-update-us-census-tennessee-marriages-and-more/#comment-17486</link>
		<dc:creator>Rich Hrazanek</dc:creator>
		<pubDate>Thu, 21 Aug 2008 18:13:26 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2008/07/25/us-content-maintenance-update-us-census-tennessee-marriages-and-more/#comment-17486</guid>
		<description>Chris, I enjoyed listening to you on Dear Myrtle. I&#039;m looking forward to the resources you will be adding to supplement the missing 1890 Federal Census. You asked for feedback as to what types of data Ancestry subscribers would like to see added in the future. I would love to see the following New York State Census records, 1892, 1905, 1915 &amp; 1925. Next, I would like to see the Connecticut Military Census of 1917 added. Keep up the great work!</description>
		<content:encoded><![CDATA[<p>Chris, I enjoyed listening to you on Dear Myrtle. I&#8217;m looking forward to the resources you will be adding to supplement the missing 1890 Federal Census. You asked for feedback as to what types of data Ancestry subscribers would like to see added in the future. I would love to see the following New York State Census records, 1892, 1905, 1915 &amp; 1925. Next, I would like to see the Connecticut Military Census of 1917 added. Keep up the great work!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mary Beth Marchant</title>
		<link>http://blogs.ancestry.com/ancestry/2008/07/25/us-content-maintenance-update-us-census-tennessee-marriages-and-more/#comment-16947</link>
		<dc:creator>Mary Beth Marchant</dc:creator>
		<pubDate>Wed, 13 Aug 2008 18:06:32 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2008/07/25/us-content-maintenance-update-us-census-tennessee-marriages-and-more/#comment-16947</guid>
		<description>Same problem here with the census.  We are getting this

Server Error in &#039;/&#039; Application.
--------------------------------------------------------------------------------

Runtime Error 
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. 

Details: To enable the details of this specific error message to be viewable on remote machines, please create a  tag within a &quot;web.config&quot; configuration file located in the root directory of the current web application. This  tag should then have its &quot;mode&quot; attribute set to &quot;Off&quot;.

DONT&#039; YOU THINK WE DESERVE AN EXPLANATION OR AT LEAST A REFUND!!!!</description>
		<content:encoded><![CDATA[<p>Same problem here with the census.  We are getting this</p>
<p>Server Error in &#8216;/&#8217; Application.<br />
&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;</p>
<p>Runtime Error<br />
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. </p>
<p>Details: To enable the details of this specific error message to be viewable on remote machines, please create a  tag within a &#8220;web.config&#8221; configuration file located in the root directory of the current web application. This  tag should then have its &#8220;mode&#8221; attribute set to &#8220;Off&#8221;.</p>
<p>DONT&#8217; YOU THINK WE DESERVE AN EXPLANATION OR AT LEAST A REFUND!!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Derek</title>
		<link>http://blogs.ancestry.com/ancestry/2008/07/25/us-content-maintenance-update-us-census-tennessee-marriages-and-more/#comment-16896</link>
		<dc:creator>Derek</dc:creator>
		<pubDate>Wed, 13 Aug 2008 00:38:06 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2008/07/25/us-content-maintenance-update-us-census-tennessee-marriages-and-more/#comment-16896</guid>
		<description>I look forward to the new 1900 census content and particularly the enhanced index.  Thanks for taking the effort.  I am checking the database daily to see if the change has been implemented...</description>
		<content:encoded><![CDATA[<p>I look forward to the new 1900 census content and particularly the enhanced index.  Thanks for taking the effort.  I am checking the database daily to see if the change has been implemented&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JMaule</title>
		<link>http://blogs.ancestry.com/ancestry/2008/07/25/us-content-maintenance-update-us-census-tennessee-marriages-and-more/#comment-16895</link>
		<dc:creator>JMaule</dc:creator>
		<pubDate>Wed, 13 Aug 2008 00:27:34 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2008/07/25/us-content-maintenance-update-us-census-tennessee-marriages-and-more/#comment-16895</guid>
		<description>A well run operation would leave the current image database in place, put the new one on a new server, and then do a switchover. Instead, they&#039;ve taken down the census records (and other images) and they leave them down. The quality of service on ancestry.com has been going downhill rapidly. Its value to me has been going downhill just as quickly. Customer service shuts down at 5 or 6, and then they close down databases without notice, and there is no one to call. Have they forgotten that when someone is paying them for a service, they need to serve?</description>
		<content:encoded><![CDATA[<p>A well run operation would leave the current image database in place, put the new one on a new server, and then do a switchover. Instead, they&#8217;ve taken down the census records (and other images) and they leave them down. The quality of service on ancestry.com has been going downhill rapidly. Its value to me has been going downhill just as quickly. Customer service shuts down at 5 or 6, and then they close down databases without notice, and there is no one to call. Have they forgotten that when someone is paying them for a service, they need to serve?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mary Beth Marchant</title>
		<link>http://blogs.ancestry.com/ancestry/2008/07/25/us-content-maintenance-update-us-census-tennessee-marriages-and-more/#comment-16870</link>
		<dc:creator>Mary Beth Marchant</dc:creator>
		<pubDate>Tue, 12 Aug 2008 14:43:34 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2008/07/25/us-content-maintenance-update-us-census-tennessee-marriages-and-more/#comment-16870</guid>
		<description>If y&#039;all are updating the census pages, it would be a courtesy to let us know.  At this time this morning census images are out for at least decades 1850 through 1900. All I and others are getting is &quot;error processing image&quot;.  We can be patient if we know ahead of time when and how long but very impatient when things just go offline with no notice or explanation.</description>
		<content:encoded><![CDATA[<p>If y&#8217;all are updating the census pages, it would be a courtesy to let us know.  At this time this morning census images are out for at least decades 1850 through 1900. All I and others are getting is &#8220;error processing image&#8221;.  We can be patient if we know ahead of time when and how long but very impatient when things just go offline with no notice or explanation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julia Mitchel</title>
		<link>http://blogs.ancestry.com/ancestry/2008/07/25/us-content-maintenance-update-us-census-tennessee-marriages-and-more/#comment-16628</link>
		<dc:creator>Julia Mitchel</dc:creator>
		<pubDate>Fri, 08 Aug 2008 05:25:25 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2008/07/25/us-content-maintenance-update-us-census-tennessee-marriages-and-more/#comment-16628</guid>
		<description>Your 1900 census for Kentucky is a mess. The Caldwell County census is reversed with BUTLER County census and vice versa. 
I sent three issue reports and tried to email the error, but all I get is Auto Response.
Guess you guys are gettin too big for us common folk.</description>
		<content:encoded><![CDATA[<p>Your 1900 census for Kentucky is a mess. The Caldwell County census is reversed with BUTLER County census and vice versa.<br />
I sent three issue reports and tried to email the error, but all I get is Auto Response.<br />
Guess you guys are gettin too big for us common folk.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julia Mitchel</title>
		<link>http://blogs.ancestry.com/ancestry/2008/07/25/us-content-maintenance-update-us-census-tennessee-marriages-and-more/#comment-16627</link>
		<dc:creator>Julia Mitchel</dc:creator>
		<pubDate>Fri, 08 Aug 2008 05:24:23 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/ancestry/2008/07/25/us-content-maintenance-update-us-census-tennessee-marriages-and-more/#comment-16627</guid>
		<description>Your 1900 census for Kentucky is a mess. The Caldwell County census is reversed with BUTLER County census and vice versa. 
I sent three issue reports and tried to emain the error, but all I get is Auto Response.
Guess you guys are gettin too big for us common folk.</description>
		<content:encoded><![CDATA[<p>Your 1900 census for Kentucky is a mess. The Caldwell County census is reversed with BUTLER County census and vice versa.<br />
I sent three issue reports and tried to emain the error, but all I get is Auto Response.<br />
Guess you guys are gettin too big for us common folk.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
