<?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: 130 Years of London Electoral Registers Released Today!</title>
	<atom:link href="http://blogs.ancestry.com/uk/2012/01/11/130-years-of-london-electoral-registers-released-today/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.ancestry.com/uk/2012/01/11/130-years-of-london-electoral-registers-released-today/</link>
	<description>The official Ancestry.co.uk blog</description>
	<lastBuildDate>Wed, 24 Apr 2013 18:23:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Jim</title>
		<link>http://blogs.ancestry.com/uk/2012/01/11/130-years-of-london-electoral-registers-released-today/#comment-2319</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Tue, 24 Jan 2012 11:43:07 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/uk/?p=3249#comment-2319</guid>
		<description>I totally agree with the coments regarding the errors with The London Electorial Records, especially #51 from Roger, some are very funny.
I have seen some pages with 12 or more entries but only 4 or 5 legitimate names the other names are in fact lines from addresses.

Try searching for MWIK ITIJGWAY for 1874.
There are 9 names listed but only 3 are real names.
Although these errors can be funny what we must realise is that we are paying for a service that we are asked to correct, how many other products do you repair once you have bought them ?</description>
		<content:encoded><![CDATA[<p>I totally agree with the coments regarding the errors with The London Electorial Records, especially #51 from Roger, some are very funny.<br />
I have seen some pages with 12 or more entries but only 4 or 5 legitimate names the other names are in fact lines from addresses.</p>
<p>Try searching for MWIK ITIJGWAY for 1874.<br />
There are 9 names listed but only 3 are real names.<br />
Although these errors can be funny what we must realise is that we are paying for a service that we are asked to correct, how many other products do you repair once you have bought them ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andi</title>
		<link>http://blogs.ancestry.com/uk/2012/01/11/130-years-of-london-electoral-registers-released-today/#comment-2317</link>
		<dc:creator>Andi</dc:creator>
		<pubDate>Mon, 23 Jan 2012 22:33:51 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/uk/?p=3249#comment-2317</guid>
		<description>Roger,

Thanks for your response. I can&#039;t comment about Electoral Rolls because, as I mentioned, I can&#039;t access them. 

But I thought that my comments about Ancestry&#039;s response to errors in census transcriptions might be relevent to the Electoral Rolls as well. 

What blew me away was the fact that Ancestry expected me to correct the error myself by contacting the &quot;creator&quot; of the census data. 

As for Member Solutions being unhelpful unless, as you said, &quot;you can give them chapter and verse on a specific problem so they can verify it&quot;, I don&#039;t know how more specific I could have been when I contacted Ancestry. That is, in addition to the specific census, I also gave full details about the person omitted from the transcription (full name, age, est DOB, birth city and county, name of her school with specific town and county, district, census page number and page line). 

Also, my apologies to everyone for adding comments which are not specifically about Electoral Rolls. It is frustrating that comments on Ancestry blogs are cut off after only two weeks of discussion rather than remaining open for anyone to add further comments as newly-discovered issues and problems arise, eg. recent 1911 census release as well as Electoral Rolls. Or, conversely, to give praise for a &quot;job well done&quot; when things are going well, errors have been corrected or a situation has otherwise improved.  

But to have discussion closed off after such a short time frame, even when there are obvious and serious difficulties, it&#039;s &quot;Out of sight, out of mind. No problems here. Everyone move on.&quot;</description>
		<content:encoded><![CDATA[<p>Roger,</p>
<p>Thanks for your response. I can&#8217;t comment about Electoral Rolls because, as I mentioned, I can&#8217;t access them. </p>
<p>But I thought that my comments about Ancestry&#8217;s response to errors in census transcriptions might be relevent to the Electoral Rolls as well. </p>
<p>What blew me away was the fact that Ancestry expected me to correct the error myself by contacting the &#8220;creator&#8221; of the census data. </p>
<p>As for Member Solutions being unhelpful unless, as you said, &#8220;you can give them chapter and verse on a specific problem so they can verify it&#8221;, I don&#8217;t know how more specific I could have been when I contacted Ancestry. That is, in addition to the specific census, I also gave full details about the person omitted from the transcription (full name, age, est DOB, birth city and county, name of her school with specific town and county, district, census page number and page line). </p>
<p>Also, my apologies to everyone for adding comments which are not specifically about Electoral Rolls. It is frustrating that comments on Ancestry blogs are cut off after only two weeks of discussion rather than remaining open for anyone to add further comments as newly-discovered issues and problems arise, eg. recent 1911 census release as well as Electoral Rolls. Or, conversely, to give praise for a &#8220;job well done&#8221; when things are going well, errors have been corrected or a situation has otherwise improved.  </p>
<p>But to have discussion closed off after such a short time frame, even when there are obvious and serious difficulties, it&#8217;s &#8220;Out of sight, out of mind. No problems here. Everyone move on.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://blogs.ancestry.com/uk/2012/01/11/130-years-of-london-electoral-registers-released-today/#comment-2316</link>
		<dc:creator>David</dc:creator>
		<pubDate>Mon, 23 Jan 2012 14:12:56 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/uk/?p=3249#comment-2316</guid>
		<description>Roger,

It is clear that a number of people have not been transcribed as they are on the same page and it is beyond belief that you ancestry have not listed whole boroughs as this is how the records are arranged by London Metropolitan Achives (LMA). I have confidence that LMA have supplied the whole collection, if not ancestry should have told us that!. Once again it appears that ancestry have transcribed records solely for financial reasons and not to help researchers!.</description>
		<content:encoded><![CDATA[<p>Roger,</p>
<p>It is clear that a number of people have not been transcribed as they are on the same page and it is beyond belief that you ancestry have not listed whole boroughs as this is how the records are arranged by London Metropolitan Achives (LMA). I have confidence that LMA have supplied the whole collection, if not ancestry should have told us that!. Once again it appears that ancestry have transcribed records solely for financial reasons and not to help researchers!.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roger</title>
		<link>http://blogs.ancestry.com/uk/2012/01/11/130-years-of-london-electoral-registers-released-today/#comment-2315</link>
		<dc:creator>Roger</dc:creator>
		<pubDate>Mon, 23 Jan 2012 09:41:51 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/uk/?p=3249#comment-2315</guid>
		<description>Andi,

There is a similar missing persons problem with this collection but it is a little more confused.

I understand that the Electoral Rolls came from the London Metropolitan Archives as Microfilm and have been put through an OCR process to transcribe them by Ancestry. Ancestry have also supplied on screen images of the microfilmed pages.

When viewing a page, occasionally the OCR process appears to have skipped a person as they are not in the Ancestry Indax at the bottom of the view. I guess this problem is down to Ancestry to correct.

Every Elector on a Roll has a number allocated to them and in some cases it looks like whole page of the Roll are missing as numbers start at some odd number instead of 1. Now this could be down to Ancestry just not scanning the missing page or it could be that the LMA have not supplied it or it was never microfilmed in the first place.

I have found that Member Solutions tend to be a little difficult to deal with as unless you can give them chapter and verse on a specific problem so that they can verify it, they brush a complaint off. I have learnt that you need to persist.</description>
		<content:encoded><![CDATA[<p>Andi,</p>
<p>There is a similar missing persons problem with this collection but it is a little more confused.</p>
<p>I understand that the Electoral Rolls came from the London Metropolitan Archives as Microfilm and have been put through an OCR process to transcribe them by Ancestry. Ancestry have also supplied on screen images of the microfilmed pages.</p>
<p>When viewing a page, occasionally the OCR process appears to have skipped a person as they are not in the Ancestry Indax at the bottom of the view. I guess this problem is down to Ancestry to correct.</p>
<p>Every Elector on a Roll has a number allocated to them and in some cases it looks like whole page of the Roll are missing as numbers start at some odd number instead of 1. Now this could be down to Ancestry just not scanning the missing page or it could be that the LMA have not supplied it or it was never microfilmed in the first place.</p>
<p>I have found that Member Solutions tend to be a little difficult to deal with as unless you can give them chapter and verse on a specific problem so that they can verify it, they brush a complaint off. I have learnt that you need to persist.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andi</title>
		<link>http://blogs.ancestry.com/uk/2012/01/11/130-years-of-london-electoral-registers-released-today/#comment-2313</link>
		<dc:creator>Andi</dc:creator>
		<pubDate>Sun, 22 Jan 2012 23:23:33 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/uk/?p=3249#comment-2313</guid>
		<description>I don&#039;t think there should be any expectation that Ancestry will fix these errors. For example, open any random page in any of the censuses and you&#039;ll very soon find various gobbledegook nonsense words and obvious errors that are still uncorrected, years after that census was posted on this site. Many pages have a dozen or more errors on them. It&#039;s the norm rather than unusual. And I&#039;m talking here about pages where writing is clear and legible -- not those pages which are faded or torn or otherwise unreadable for various other reasons. As far as I can see, no errors are ever corrected unless a subscriber does it.  

There are also people missing from the transcriptions in various censuses. I&#039;ve found almost a dozen myself, just stumbling across them in the course of my own research. 
When I contacted Ancestry in October 2009 about one of these omissions in the 1871 census, the reply I got from someone at &quot;Member Solutions&quot; stated the following (and I think it may apply to *any* transcribed info on Ancestry, not just the censuses, which I why I&#039;m mentioning it here) --

&quot;.....Please note that we generally receive data from outside sources and post it as it was provided to us. In order to maintain authenticity in our records, we cannot make changes directly to material not created by Ancestry. To make these types of changes, you will need to contact the original creators of this data, have them correct this in their own records and then send this update to us for posting. We apologize for any frustration or inconvenience this may cause.....&quot;

Note that this says that *I* had to contact the &quot;original creators of this data&quot;, not that Ancestry would do it. So, since I did not follow up on the above advice, the error/omission I told Ancestry about is still there in the 1871 census, ie. a researcher will not be able to find this &quot;missing person&quot; unless they know exactly where she was in 1871 (a pupil at a school in a county which was not her home county). 

The reply from Ancestry also stated --

&quot;....If you wish to consult our corporate policy regarding the content provided on Ancestry.com, please go to the following URL: 

http://www.ancestry.com/legal/terms.htm#Liability

.....&quot;

It also went on to state --

&quot;.....For additional information on the source of the database, select the Database Title link found at the top of each page of search results. The next page provides information on who compiled the database, including a short bibliography and a brief description of the information contained in the database. Here you will be able to locate the source information for the database in question. This should assist you in contacting the source directly on this matter.&quot;

Perhaps someone can see if this applies to the Electoral Rolls as well (which I can&#039;t access because I don&#039;t pay Ancestry enough for my subscription).

Lastly, Ancestry finished off with this very unhelpful bit of advice --

&quot;....You can also typically add a User Comment to any record that you feel may be incorrect. You will find a &quot;add alternate information&quot; or &quot;add comment&quot; link to the right of each database result. If you add a User Comment (once the feature is again available), your comments or corrections will be connected to the database result for others to view.&quot;

But I had not contacted them about something which was *incorrect* -- it was about info that was missing altogether. The above strategy will only work if there is an individual listed in the transcription to add a correction to -- it&#039;s useless if the person isn&#039;t listed in the transcription at all!</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think there should be any expectation that Ancestry will fix these errors. For example, open any random page in any of the censuses and you&#8217;ll very soon find various gobbledegook nonsense words and obvious errors that are still uncorrected, years after that census was posted on this site. Many pages have a dozen or more errors on them. It&#8217;s the norm rather than unusual. And I&#8217;m talking here about pages where writing is clear and legible &#8212; not those pages which are faded or torn or otherwise unreadable for various other reasons. As far as I can see, no errors are ever corrected unless a subscriber does it.  </p>
<p>There are also people missing from the transcriptions in various censuses. I&#8217;ve found almost a dozen myself, just stumbling across them in the course of my own research.<br />
When I contacted Ancestry in October 2009 about one of these omissions in the 1871 census, the reply I got from someone at &#8220;Member Solutions&#8221; stated the following (and I think it may apply to *any* transcribed info on Ancestry, not just the censuses, which I why I&#8217;m mentioning it here) &#8211;</p>
<p>&#8220;&#8230;..Please note that we generally receive data from outside sources and post it as it was provided to us. In order to maintain authenticity in our records, we cannot make changes directly to material not created by Ancestry. To make these types of changes, you will need to contact the original creators of this data, have them correct this in their own records and then send this update to us for posting. We apologize for any frustration or inconvenience this may cause&#8230;..&#8221;</p>
<p>Note that this says that *I* had to contact the &#8220;original creators of this data&#8221;, not that Ancestry would do it. So, since I did not follow up on the above advice, the error/omission I told Ancestry about is still there in the 1871 census, ie. a researcher will not be able to find this &#8220;missing person&#8221; unless they know exactly where she was in 1871 (a pupil at a school in a county which was not her home county). </p>
<p>The reply from Ancestry also stated &#8211;</p>
<p>&#8220;&#8230;.If you wish to consult our corporate policy regarding the content provided on Ancestry.com, please go to the following URL: </p>
<p><a href="http://www.ancestry.com/legal/terms.htm#Liability" rel="nofollow">http://www.ancestry.com/legal/terms.htm#Liability</a></p>
<p>&#8230;..&#8221;</p>
<p>It also went on to state &#8211;</p>
<p>&#8220;&#8230;..For additional information on the source of the database, select the Database Title link found at the top of each page of search results. The next page provides information on who compiled the database, including a short bibliography and a brief description of the information contained in the database. Here you will be able to locate the source information for the database in question. This should assist you in contacting the source directly on this matter.&#8221;</p>
<p>Perhaps someone can see if this applies to the Electoral Rolls as well (which I can&#8217;t access because I don&#8217;t pay Ancestry enough for my subscription).</p>
<p>Lastly, Ancestry finished off with this very unhelpful bit of advice &#8211;</p>
<p>&#8220;&#8230;.You can also typically add a User Comment to any record that you feel may be incorrect. You will find a &#8220;add alternate information&#8221; or &#8220;add comment&#8221; link to the right of each database result. If you add a User Comment (once the feature is again available), your comments or corrections will be connected to the database result for others to view.&#8221;</p>
<p>But I had not contacted them about something which was *incorrect* &#8212; it was about info that was missing altogether. The above strategy will only work if there is an individual listed in the transcription to add a correction to &#8212; it&#8217;s useless if the person isn&#8217;t listed in the transcription at all!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roger</title>
		<link>http://blogs.ancestry.com/uk/2012/01/11/130-years-of-london-electoral-registers-released-today/#comment-2312</link>
		<dc:creator>Roger</dc:creator>
		<pubDate>Sun, 22 Jan 2012 10:03:14 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/uk/?p=3249#comment-2312</guid>
		<description>Rowena,

Good luck correcting names, there are over 139 Million of them to go through in this collection! 

The silliest thing is where the OCR scanner has been run over a header page and has attempted to create names and address from it. Follow this link

http://search.ancestry.co.uk/Browse/view.aspx?dbid=1795&amp;path=Haringey.Hornsey.1937.432&amp;sid=&amp;gskw=

and laugh at the 10 voters listed in the Ancestry Index at the bottom of the screen. This is just one of many examples.

How can Ancestry release this rubbish!</description>
		<content:encoded><![CDATA[<p>Rowena,</p>
<p>Good luck correcting names, there are over 139 Million of them to go through in this collection! </p>
<p>The silliest thing is where the OCR scanner has been run over a header page and has attempted to create names and address from it. Follow this link</p>
<p><a href="http://search.ancestry.co.uk/Browse/view.aspx?dbid=1795&#038;path=Haringey.Hornsey.1937.432&#038;sid=&#038;gskw=" rel="nofollow">http://search.ancestry.co.uk/Browse/view.aspx?dbid=1795&#038;path=Haringey.Hornsey.1937.432&#038;sid=&#038;gskw=</a></p>
<p>and laugh at the 10 voters listed in the Ancestry Index at the bottom of the screen. This is just one of many examples.</p>
<p>How can Ancestry release this rubbish!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roger</title>
		<link>http://blogs.ancestry.com/uk/2012/01/11/130-years-of-london-electoral-registers-released-today/#comment-2311</link>
		<dc:creator>Roger</dc:creator>
		<pubDate>Sun, 22 Jan 2012 08:40:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/uk/?p=3249#comment-2311</guid>
		<description>David,
I have now had further communication with Ancestry and they have accepted that the Borough/County for the Fincley electoral rolls for 1936 and 1937 have been wrongly transcribed. But this is just the tip of the Iceberg!

By browsing the Collection at

http://search.ancestry.co.uk/search/db.aspx?dbid=1795

you can get a dropdown of the Boroughs/Counties, Parliamentary Divisions and Years that have been transcribed.

A quick look shows, for example, numerous records allocated to the borough of Barnet. Everyone that I have so far looked at should have been in Middlesex. Strangly Middlesex appears to have only one year allocated to it.

Random sampling of other Boroughs seems to show that just about every one is wrong! Ancestry is not even consistant with the mistakes allocating records to a name Borough for some years or simply London for other years.

What a mess - and its all caused by using OCR and not checking the output. Or maybe just having someone who has no knowledge of London do the checking.

The interesting thing is that every record I have looked at clearly includes all the information necessary to get the index right in the first few images.

What</description>
		<content:encoded><![CDATA[<p>David,<br />
I have now had further communication with Ancestry and they have accepted that the Borough/County for the Fincley electoral rolls for 1936 and 1937 have been wrongly transcribed. But this is just the tip of the Iceberg!</p>
<p>By browsing the Collection at</p>
<p><a href="http://search.ancestry.co.uk/search/db.aspx?dbid=1795" rel="nofollow">http://search.ancestry.co.uk/search/db.aspx?dbid=1795</a></p>
<p>you can get a dropdown of the Boroughs/Counties, Parliamentary Divisions and Years that have been transcribed.</p>
<p>A quick look shows, for example, numerous records allocated to the borough of Barnet. Everyone that I have so far looked at should have been in Middlesex. Strangly Middlesex appears to have only one year allocated to it.</p>
<p>Random sampling of other Boroughs seems to show that just about every one is wrong! Ancestry is not even consistant with the mistakes allocating records to a name Borough for some years or simply London for other years.</p>
<p>What a mess &#8211; and its all caused by using OCR and not checking the output. Or maybe just having someone who has no knowledge of London do the checking.</p>
<p>The interesting thing is that every record I have looked at clearly includes all the information necessary to get the index right in the first few images.</p>
<p>What</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rowena</title>
		<link>http://blogs.ancestry.com/uk/2012/01/11/130-years-of-london-electoral-registers-released-today/#comment-2310</link>
		<dc:creator>Rowena</dc:creator>
		<pubDate>Sun, 22 Jan 2012 08:10:50 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/uk/?p=3249#comment-2310</guid>
		<description>Previously I have always supported Ancestry with their transcriptions when people have moaned - as I always felt with some wildcard or investigation you could find your ancestor BUT with this latest one the mind boggles - there are pages where the transcription just shows gobbledy gook or indexes the address instead of the name - I am trying to correct all the ones that I can see are wrong as my surname is so rare it is obvious but what about all the others.  I don&#039;t mind correcting mine and the neighbours but there are whole pages where I need to let you know that everything is wrong - I think you need to add a button to the pages so when it is an extremely bad page we can let you know.  Please do not rush these things as you will end up losing the good reputation you have.</description>
		<content:encoded><![CDATA[<p>Previously I have always supported Ancestry with their transcriptions when people have moaned &#8211; as I always felt with some wildcard or investigation you could find your ancestor BUT with this latest one the mind boggles &#8211; there are pages where the transcription just shows gobbledy gook or indexes the address instead of the name &#8211; I am trying to correct all the ones that I can see are wrong as my surname is so rare it is obvious but what about all the others.  I don&#8217;t mind correcting mine and the neighbours but there are whole pages where I need to let you know that everything is wrong &#8211; I think you need to add a button to the pages so when it is an extremely bad page we can let you know.  Please do not rush these things as you will end up losing the good reputation you have.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://blogs.ancestry.com/uk/2012/01/11/130-years-of-london-electoral-registers-released-today/#comment-2309</link>
		<dc:creator>David</dc:creator>
		<pubDate>Sun, 22 Jan 2012 01:37:30 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/uk/?p=3249#comment-2309</guid>
		<description>It is again a question of why ancestry are making claims about releases of 130 years of electoral rolls when they are not complete. On the basis of the response for the missing aprts of the 1911 census it would seem that ancestry are content to release rolls even though thay are incomplete and in the wrong boroughs. Instead of using OCR technology why not allow people to transcribe them,it would be better than having to deal with customer complaints!. 

The basic question is why a list of the boroughs was not prepared before starting and what parishes were included and when, London has had several borough changes over this period. Surely making wide-ranging comments about 130 years that we should be told what rolls have been completed and over what period. I am fed up with receiving ancestry customer satisfaction survey e-mails because the answer is the same in that ancestry have not dealt with the issues.</description>
		<content:encoded><![CDATA[<p>It is again a question of why ancestry are making claims about releases of 130 years of electoral rolls when they are not complete. On the basis of the response for the missing aprts of the 1911 census it would seem that ancestry are content to release rolls even though thay are incomplete and in the wrong boroughs. Instead of using OCR technology why not allow people to transcribe them,it would be better than having to deal with customer complaints!. </p>
<p>The basic question is why a list of the boroughs was not prepared before starting and what parishes were included and when, London has had several borough changes over this period. Surely making wide-ranging comments about 130 years that we should be told what rolls have been completed and over what period. I am fed up with receiving ancestry customer satisfaction survey e-mails because the answer is the same in that ancestry have not dealt with the issues.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roger</title>
		<link>http://blogs.ancestry.com/uk/2012/01/11/130-years-of-london-electoral-registers-released-today/#comment-2308</link>
		<dc:creator>Roger</dc:creator>
		<pubDate>Sat, 21 Jan 2012 14:54:44 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ancestry.com/uk/?p=3249#comment-2308</guid>
		<description>Having been in touch with Customer Services I am no happier with these records. 

Basically, Ancestry used OCR technology to transcribe these records and dispite the numerous obvious errors seem to be proud of the result. What appears to be a standard e-mail I received states -

&quot;Because these Historical Records have far too much text to be indexed manually, indexes are built using advanced Optical Character Recognition (OCR) technology to automatically recognize text within an image. We believe we are using the very best OCR technology available, but it is still less accurate than human eyes and brains. These limitations make it impossible to achieve the same level of accuracy found in other indexes. In cases where the original microfilm text is unclear, the OCR technology tries to guess words intelligently.

There are two important points about searching the Historical Record images:

1. It is likely that there are additional matches for your search that could be found by browsing but which are not in the index or search results list. 

2. The search results may include &quot;matches&quot; on words other than those you searched for because the Optical Character Recognition (OCR) technology we use believes they are optically similar enough that your target word(s) may be in the original image.

I do know that the content team is aware of this issue and will be fixing the records as soon as possible.&quot;

As for the problem with Ancestry using Boroughs that did not exist at the time of the record, well this was ignored.

One other comment in the e-mail indicated that Ancestry hope to double the number of records available. No firm date was given but &quot;Fall&quot; 2012 was mentioned. This tells me two things, we are dealing with Americans which perhaps explains the problem with Boroughs and that this collection is incomplete. I have asked what percentage of the total records is currently available but I have yet to have an answer to this question.

Overall I still feel Ancestry could do a lot better.</description>
		<content:encoded><![CDATA[<p>Having been in touch with Customer Services I am no happier with these records. </p>
<p>Basically, Ancestry used OCR technology to transcribe these records and dispite the numerous obvious errors seem to be proud of the result. What appears to be a standard e-mail I received states -</p>
<p>&#8220;Because these Historical Records have far too much text to be indexed manually, indexes are built using advanced Optical Character Recognition (OCR) technology to automatically recognize text within an image. We believe we are using the very best OCR technology available, but it is still less accurate than human eyes and brains. These limitations make it impossible to achieve the same level of accuracy found in other indexes. In cases where the original microfilm text is unclear, the OCR technology tries to guess words intelligently.</p>
<p>There are two important points about searching the Historical Record images:</p>
<p>1. It is likely that there are additional matches for your search that could be found by browsing but which are not in the index or search results list. </p>
<p>2. The search results may include &#8220;matches&#8221; on words other than those you searched for because the Optical Character Recognition (OCR) technology we use believes they are optically similar enough that your target word(s) may be in the original image.</p>
<p>I do know that the content team is aware of this issue and will be fixing the records as soon as possible.&#8221;</p>
<p>As for the problem with Ancestry using Boroughs that did not exist at the time of the record, well this was ignored.</p>
<p>One other comment in the e-mail indicated that Ancestry hope to double the number of records available. No firm date was given but &#8220;Fall&#8221; 2012 was mentioned. This tells me two things, we are dealing with Americans which perhaps explains the problem with Boroughs and that this collection is incomplete. I have asked what percentage of the total records is currently available but I have yet to have an answer to this question.</p>
<p>Overall I still feel Ancestry could do a lot better.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
