I think what everyone's been telling me her on the list is to include all the other information to get the person to the correct page and even line #, so they wouldn't necessarily be going through the standard "enter first and last name and click 'search' " process.
I have had cases where what was enumerated was wrong (so also indexed incorrectly). In those cases I will add "(incorrectly enumerated as 'James')" in the event notes for Jane's census event, for example. --Paula ________________________________ From:Thomas L. Shaw <tls0...@gmail.com> To:LegacyUserGroup@LegacyUsers.com Sent: Tue, May 1, 2012 5:54:44 AM Subject: Re: [LegacyUG] 1940 census template questions I see your point Jenny...would it make sense to record the obviously correct entry, followed by the incorrect entry in parentheses? On May 1, 2012, at 5:19, Jenny M Benson <ge...@cedarbank.me.uk> 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/legacyusergroup@legacyusers.com/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > 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/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ 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/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ 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
