I had one like that yesterday. I was arbitrating a batch where Iowa was listed in the city box and Cedar Rapids was listed in the state box. An obvious error but I am not allowed to fix it. The rules say to type what you see. The only exceptions you are allowed to correct the spelling of place names, you are allowed to expand abbreviations of place names (LA to Louisiana) and you can correct gender errors but that is it. I don't agree with it but I have to live by the rules. I think that the arbitrators should be able to correct obvious errors like this.
Michele -----Original Message----- From: Robert Runion [mailto:[email protected]] Sent: Tuesday, May 01, 2012 6:48 AM To: [email protected] Subject: Re: [LegacyUG] 1940 census template questions In some of my indexing, I have encountered errors by the Census taker where the county of residence in 1935 was entered int the State column. I debated about how to enter the data but finally erred on the side of the instructions and entered the data as recorded. An example is 'Avery' was entered in the State column and I know from the other data that that should have been entered as Avery Co., North Carolina. Be that as it may, I entered the data as shown and as recommended. Is this compounding an obvious error? I leave it to others to decide. bob On May 1, 2012, at 4:19 AM, Jenny M Benson wrote: > On 30/04/2012 23:46, mbstx wrote: >> To me, it's not so much the quality of the image as the quality of >> the indexing. There are a multitude of errors in the previous census >> databases on Ancestry.com (and some in FamilySearch as well, but not >> as many I believe). FamilySearch is trying to use indexers who >> understand the batches they're working one, particularly re surnames, >> and other things that might be misinterpreted. > > But wherever possible one should record what is actually written on > the Census sheet, not what is obviously a bad transcription. > > This is one reason why it's important to cite the full Source, > including the website. If a person's name is transcribed (wrongly) as > Jane on one site and (correctly) as James on another, someone trying > to follow up your record of Jane, but using a different site to you, > might not find the record. > > Sometimes what is written on the Census sheet is obviously incorrect, > but I still record exactly what is written. > > -- > Jenny M Benson > > > > 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 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
