Because I cannot guarantee I will remember the correct format for the comment line each time I just created an MSWord file with the #Comment in the correct format which I copy/paste when I need it, changing the Spouse or MMN accordingly (and the number (in brackets) of names to which it applies if necessary) Kind regards Graham -----Original Message----- From: freebmd-admins-bounces@rootsweb.com [mailto:freebmd-admins-bounces@rootsweb.com]On Behalf Of Allan Raymond Sent: 07 June 2011 10:40 To: freebmd-admins@rootsweb.com Subject: Re: Tip of the Day (No. 6) (last updated 06 June 2011)-AlternativeSpouse Names in Marriage and Birth Records Evan You may lead a horse to the water, but you cannot make him drink springs to mind. I'm aware some individuals are not following the advice in the Tip on how and when to insert the #COMMENT line. I would like to think this is because they are not aware of the requirement rather than a deliberate attempt not to follow the advice. I came across one such transcriber yesterday who was not aware of the requirement which is why I have decided to resurrect the Tips if the Day. Regards Allan Raymond ----- Original Message ----- From: Evan Smith To: freebmd-admins@rootsweb.com Sent: Tuesday, June 07, 2011 6:16 AM Subject: Re: Tip of the Day (No. 6) (last updated 06 June 2011) -AlternativeSpouse Names in Marriage and Birth Records Thanks, Allan, for your "comment". This is indeed a timely reminder of TKB 6u. A substantial minority are omitting to add the bracketted 2 - (2) - after COMMENT and using their own phrasing of the comment. A few do not add any COMMENT. TKB 6(al) is also not being followed in many instances. The example shows Frederick A.M. being transcribed as Frederick A. M. If there is no space in the index, no space should be in the transcription. Evan S ----- Original Message ----- From: "Allan Raymond" <allan_raymond@btinternet.com> To: <freebmd-admins@rootsweb.com> Sent: Tuesday, June 07, 2011 5:31 AM Subject: Tip of the Day (No. 6) (last updated 06 June 2011) - AlternativeSpouse Names in Marriage and Birth Records > This is the sixth in a series of "Tip of the Day" to help volunteers who > are transcribing for the FreeBMD Project. > > This Tip of the Day has been updated to take into account feedback from > volunteers and is reissued for the benefit of our new volunteers plus > existing volunteers who may have missed it when last issued. > > Further feedback is welcomed. > > The Transcribers' Knowledge Base at: > http://freebmd.rootsweb.com/vol_faq.html#6u provides the definitive advice > for dealing with alternative names in records. > > I've been carrying out ongoing checks of recent files uploaded by a number > of transcribers to see how they dealt with records containing alternative > names. In particular, where alternative spouse names are shown against a > marriage entry the advice in http://freebmd.rootsweb.com/vol_faq.html#6u > in a number of instances was not being followed > > The correct way to transcribe a marriage entry such as > > Dunn,Charles,Curphey or Bradley,W.Derby,8b,697 > > using the advice in http://freebmd.rootsweb.com/vol_faq.html#6u is > > Dunn,Charles,Curphey,W.Derby,8b,697 > #COMMENT(2) entry reads Curphey or Bradley for spouse name > Dunn,Charles,Bradley,W.Derby,8b,697 > > Please note, the #COMMENT(2) line is located between the two entries > under consideration. > > By a similar token the correct way to transcribe a birth entry such as > > Dunn,Charles,Curphey or Bradley,W.Derby,8b,697 > > using the advice in http://freebmd.rootsweb.com/vol_faq.html#6u is > > Dunn,Charles,Curphey,W.Derby,8b,697 > #COMMENT(2) entry reads Curphey or Bradley for mother`s name > Dunn,Charles,Bradley,W.Derby,8b,697 > > Please note, the #COMMENT(2) line is located between the two entries > under consideration. > > There should be no space between #COMMENT and (2) although to cater for > the large number of previous instances of a space being inserted it is now > allowed to include a space. > > For standardisation purposes there is no necessity to change the format of > the wording after the #COMMENT(2) shown above and in > http://freebmd.rootsweb.com/vol_faq.html#6u . > > The audit process checks for the alternative spouse name checks and the > list of files identified as being suspect is listed in > http://www.freebmd.org.uk/SuspectFiles.html . > > It would be appreciated if transcribers in conjunction with their > Co-ordinators could check http://www.freebmd.org.uk/SuspectFiles.html to > see if any of their files are listed and where appropriate correct the > files by including the appropriate #COMMENT(2) line. A warning message > will be shown against any suspect files when viewed in File Management. > > As an aside > > A misplaced #COMMENT(2) line can have the wrong outcome. > > In the example below the #COMMENT(2) in the file is placed after the two > entries under consideration rather than between the two entries. > > Barbour,John H.,Stephenson,Skipton,9a,79 > Barbour,John H.,Mitchell,Skipton,9a,79 > #COMMENT(2) - above line has Stephenson or Mitchell as spouse of John H. > Barbour > > The resultant effect from a search is to place a #COMMENT against one > related entry and one unrelated entry as shown below: > > Barbour John H Mitchell Skipton 9a 79 (related #COMMENT - > above line has Stephenson or Mitchell as spouse of John H. Barbour) > Barcinski Philip H Newton Hampstead 1a 1513 (unrelated #COMMENT - > above line has Stephenson or Mitchell as spouse of John H. Barbour) > > Allan Raymond > FreeBMD Co-coordinator of Syndicates > FreeBMD-Admins mailing list - archive > http://archiver.rootsweb.com/th/index/freebmd-admins > FreeBMD http://freebmd.rootsweb.com/ > > ------------------------------- > To unsubscribe from the list, please send an email to > FREEBMD-ADMINS-request@rootsweb.com with the word 'unsubscribe' without > the quotes in the subject and the body of the message > > __________ Information from ESET NOD32 Antivirus, version of virus > signature database 6185 (20110606) __________ > > The message was checked by ESET NOD32 Antivirus. > > http://www.eset.com > > > __________ Information from ESET NOD32 Antivirus, version of virus signature database 6185 (20110606) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 6185 (20110606) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com __________ Information from ESET NOD32 Antivirus, version of virus signature database 6185 (20110606) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com FreeBMD-Admins mailing list - archive http://archiver.rootsweb.com/th/index/freebmd-admins FreeBMD http://freebmd.rootsweb.com/ ------------------------------- To unsubscribe from the list, please send an email to FREEBMD-ADMINS-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message FreeBMD-Admins mailing list - archive http://archiver.rootsweb.com/th/index/freebmd-admins FreeBMD http://freebmd.rootsweb.com/ ------------------------------- To unsubscribe from the list, please send an email to FREEBMD-ADMINS-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message