The problem is less if you use Ancestry or other transcriptions instead of findmypast.
Registration Districts often cross county boundaries but are named after a town in one of the counties. Findmypast seem to insist on entering the name of the county which contains the town which is part of the registration district name for all the locations within that RD, regardless of the fact that the actual County for the location concerned is correctly written on the original registration form. Whenever I have asked for a correction to the proper County name they have refused and then added "we aim to provide you with an exact copy of the original census page" When I have pointed out that this is a blatant lie I have received no reply. Not strictly related to Legacy I am afraid, but it is infuriating when one is trying to search for people born in a particular county and they dont appear on a findmypast search (which is usually better than its competitors) not just as a result of human error but of deliberate policy. John Clifford -----Original Message----- From: Ron Ferguson [mailto:[email protected]] Sent: 04 February 2012 11:14 To: [email protected] Subject: Re: [LegacyUG] Event Locations Tony, Which country's censuses are your referring to? For the English/Welsh censuses it may well appear that this is the case, whereas in fact it is not. The reason being that the locations are recorded in Registration Districts which are not the same as the locations, although the detail above the columns is. Ron Ferguson http://www.fergys.co.uk/ -----Original Message----- From: Tony Rolfe Sent: Saturday, February 04, 2012 5:41 AM To: [email protected] Subject: [LegacyUG] Event Locations On Fri, 03 Feb 2012 18:32:15 -0800 Bjørn K Nilssen > I prefer that second school too. What I'm interested in is where that > location is, and who shared it. Adding 10 or more differently spelled > versions isn't really that useful IMO. It would be nice to have an > AKA for locations too though, with date and text fields. What would be really nice would be to have date-linked short names for a given location. Something like Long Name: Sometown, someplace, Somecountry Short name: to 31 mar 1837: An original short name Short Name: to 1 Jan 1951: a different short name here Short Name: to: current short name for the place One problem I have is that Census enumerators described the same location differently on different censuses. It would be nice to record what they actually wrote, without having to make a different location entry for each census. Now the program would pick the short name according to the date for the display. Actually, it might be useful to have both short and long names varying by date with a "Location name" to identify it, but which isn't used in reports. Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
