<?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: FREE 1911 Census* – Limited time only!</title>
	<atom:link href="http://blogs.ancestry.com/uk/2012/08/15/free-1911-census-limited-time-only/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.ancestry.com/uk/2012/08/15/free-1911-census-limited-time-only/</link>
	<description>The official Ancestry.co.uk blog</description>
	<lastBuildDate>Sun, 02 Jun 2013 01:35:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Joy Dean</title>
		<link>http://blogs.ancestry.com/uk/2012/08/15/free-1911-census-limited-time-only/#comment-2622</link>
		<dc:creator>Joy Dean</dc:creator>
		<pubDate>Mon, 27 Aug 2012 06:45:41 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/uk/?p=3574#comment-2622</guid>
		<description>Why is the infirmity column still blocked off? When I asked when it would be visible, I was told when the census was complete.
Months ago it was visible in the original 1911 census site.</description>
		<content:encoded><![CDATA[<p>Why is the infirmity column still blocked off? When I asked when it would be visible, I was told when the census was complete.<br />
Months ago it was visible in the original 1911 census site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christopher J. Hewish</title>
		<link>http://blogs.ancestry.com/uk/2012/08/15/free-1911-census-limited-time-only/#comment-2619</link>
		<dc:creator>Christopher J. Hewish</dc:creator>
		<pubDate>Thu, 23 Aug 2012 14:55:16 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/uk/?p=3574#comment-2619</guid>
		<description>A number of early censuses have enumerators being hoodwinked by householders in various ways. Perhaps unwittingly, one line in my family changes spelling of their surname, something very common back in the 17th century. Marrying in the late 1870s one of my ancestors, born as &quot;spelling variant A&quot;, also SVA in 1861 Census, but as SVB in 1871 Census, elopes to London and uses SVA on his marriage lines. In the 1881 Census they are back to SVB, and stayed so thereafter! 

I knew, before starting out on my enquiries, that there are six to ten variant spellings of &quot;Hewish&quot; - from Huyshe to Hewes, notoriously via Hughes. Forewarned is forearmed? 

Overall, I agree with David. Deaths are more definitive, and may be checked with certificates. 
BTW &amp; with respect, David, try sending an &quot;update&quot; on the &quot;Gos?or?&quot; issue. Ancestry.&amp;c DOES review these and incorporate them (provided they are backed by corroborative evidence). Transcription is a human activity and always subject to human error.

If moderation allows, and with respect, I share Mr Dunn&#039;s frustration with certain Public Member Trees especially those who mis-identify the death of my grandmother by some 30 years. They thereby miss out a significant family tragedy and lose her widower&#039;s second marriage completely. (These issues are dealt with in my Public (Cole Family) Tree.) Another PFT has my parents&#039; emigrating and dying overseas. Very creative but NOT History.</description>
		<content:encoded><![CDATA[<p>A number of early censuses have enumerators being hoodwinked by householders in various ways. Perhaps unwittingly, one line in my family changes spelling of their surname, something very common back in the 17th century. Marrying in the late 1870s one of my ancestors, born as &#8220;spelling variant A&#8221;, also SVA in 1861 Census, but as SVB in 1871 Census, elopes to London and uses SVA on his marriage lines. In the 1881 Census they are back to SVB, and stayed so thereafter! </p>
<p>I knew, before starting out on my enquiries, that there are six to ten variant spellings of &#8220;Hewish&#8221; &#8211; from Huyshe to Hewes, notoriously via Hughes. Forewarned is forearmed? </p>
<p>Overall, I agree with David. Deaths are more definitive, and may be checked with certificates.<br />
BTW &amp; with respect, David, try sending an &#8220;update&#8221; on the &#8220;Gos?or?&#8221; issue. Ancestry.&amp;c DOES review these and incorporate them (provided they are backed by corroborative evidence). Transcription is a human activity and always subject to human error.</p>
<p>If moderation allows, and with respect, I share Mr Dunn&#8217;s frustration with certain Public Member Trees especially those who mis-identify the death of my grandmother by some 30 years. They thereby miss out a significant family tragedy and lose her widower&#8217;s second marriage completely. (These issues are dealt with in my Public (Cole Family) Tree.) Another PFT has my parents&#8217; emigrating and dying overseas. Very creative but NOT History.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://blogs.ancestry.com/uk/2012/08/15/free-1911-census-limited-time-only/#comment-2618</link>
		<dc:creator>David</dc:creator>
		<pubDate>Sun, 19 Aug 2012 16:40:50 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/uk/?p=3574#comment-2618</guid>
		<description>Definitely not the 1911 census which has so many errors and omissions from ancesty&#039;s indexes to make research problematic at the very least, London is a mess. The death index is a much better choice. For example my great grandmother is shown on the image in the 1911 census as being born in Gosport (previously Alverstoke) in Hampshire and not Gosford in your index and which is not on the screen!.</description>
		<content:encoded><![CDATA[<p>Definitely not the 1911 census which has so many errors and omissions from ancesty&#8217;s indexes to make research problematic at the very least, London is a mess. The death index is a much better choice. For example my great grandmother is shown on the image in the 1911 census as being born in Gosport (previously Alverstoke) in Hampshire and not Gosford in your index and which is not on the screen!.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Trevor Thacker</title>
		<link>http://blogs.ancestry.com/uk/2012/08/15/free-1911-census-limited-time-only/#comment-2617</link>
		<dc:creator>Trevor Thacker</dc:creator>
		<pubDate>Thu, 16 Aug 2012 23:47:47 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/uk/?p=3574#comment-2617</guid>
		<description>Our apologies, Alfred. Would you mind contacting us on 0800 404 9723 so that we can duplicate the issue with the search? We&#039;d be happy to help!</description>
		<content:encoded><![CDATA[<p>Our apologies, Alfred. Would you mind contacting us on 0800 404 9723 so that we can duplicate the issue with the search? We&#8217;d be happy to help!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alfred Roger Dunn</title>
		<link>http://blogs.ancestry.com/uk/2012/08/15/free-1911-census-limited-time-only/#comment-2616</link>
		<dc:creator>Alfred Roger Dunn</dc:creator>
		<pubDate>Thu, 16 Aug 2012 09:03:23 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/uk/?p=3574#comment-2616</guid>
		<description>The current 1911 search engine consistantly fails to find people whom I have previously found. This is very irritating. It also means, (I guess), I cannot find others for whom I have not previously found.

Also as an aside, some of the published public member trees are quite frankly , a disgrace. Obviously no cross referencing has taken place.


Roger Dunn</description>
		<content:encoded><![CDATA[<p>The current 1911 search engine consistantly fails to find people whom I have previously found. This is very irritating. It also means, (I guess), I cannot find others for whom I have not previously found.</p>
<p>Also as an aside, some of the published public member trees are quite frankly , a disgrace. Obviously no cross referencing has taken place.</p>
<p>Roger Dunn</p>
]]></content:encoded>
	</item>
</channel>
</rss>
