No, Bill is not right. http://www.freebmd.org.uk/vol_faq.html#6u gives an example: #COMMENT(2) entry reads BONUS alias CHAPMAN for surname so <alternative> is the alternative names, in the case given <alternative> is "Curphey or Bradley". However, the item will be updated because as has been pointed out "alias" is very uncommon so the whole item should be biased towards "or". At the same time this misunderstanding can be addressed. Barrie On 19:59, Keith Simpson wrote: > Allan, > I have been asked by BillP a transcriber in my group to post this message on > their behalf. They were unable to post the message themselves , some > technical difficulties. > Keith > GANDALF UK > > Message reads, > > Allan, > > I think that you have given conflicting advice for the #COMMENT line when > completing the transcription for alternative names when referencing the FAQ > concerned. > > The final part of the FAQ concerned says: > So, in general, the comment should read: > > #COMMENT(2) entry reads <alternative> for <field> Where <alternative> is the > alternative from the record and <field> is the field in the record, either > surname, given name, mother's name, spouse name, district, volume of page > number. Note that there is no space between "#COMMENT" and the "(2)". > > > For Birth records and a duplicate mothers name you suggest: > #COMMENT(2) entry reads Curphey or Bradley for mother's name. > > Yet my interpretation of the FAQ is: > #COMMENT(2) entry reads Bradley for mother's name. > > Am I right or missing something? > Bill > > -------Original Message------- > > From: Allan Raymond > Date: 01/04/2012 19:41:33 > To: freebmd-admins@rootsweb.com > Subject: Tip of the Day (No. 6) (last updated 01 April 2012) - > AlternativeSpouse or Mother's Names in Marriage or 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 is being reissued with minor amendments based on recent > feedback from our transcribers and is 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. > > We have also recently enhanced our automatic reporting system so that files > containing possible errors in dealing with alternative names are flagged up. > > 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 # and COMMENT or between #COMMENT and (2). > > 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 wording describes > accurately the reason for the #COMMENT(2) line. > > If there are more than two alternative names, enter one record for each and > put in one comment covering all the names, e.g. #COMMENT(3) after the first > of three entries. > > It may be useful to remember the usual Windows shortcuts CTRL-C for copy, > CTRL-X for cut and CTRL-V for paste, all work in WinBMD. > > So rather than having to retype the complete #COMMENT(2) line each time it > is required just CTRL-C one of the appropriate lines below > > #COMMENT(2) entry reads name1 or name2 Bradley for spouse name > or > #COMMENT(2) entry reads name1 or name2 for mother`s name > > and then CTRL-V to paste in WinBMD not forgetting to change "name1 or name2" > by the actual names. > > The automatic reporting system checks if transcription of alternative name > entries have been transcribed in accordance with the information above and > any files identified as being suspect are listed in > http://www.freebmd.org.uk/SuspectFilesComments.html . > > It would be appreciated if transcribers in conjunction with their > Coordinators could check http://www.freebmd.org.uk/SuspectFilesComments.html > to see if any of their files are listed and where appropriate correct the > files by including the appropriate #COMMENT(2) line. At present there are > over forty four thousand files (i.e. over 44,000) files appearing in the > report creating a huge task for Coordinators and some of their volunteers. > > > > As an aside > > A misplaced #COMMENT(2) line can have the wrong outcome. > > In the example below an invalid #COMMENT(2) line 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 > > > --Certified Virus Free by 4SecureMail.com ICSA-Certified Scanner--
Sorry, at the moment I'm getting these threads in digest form and it's somewhat difficult to ensure that I'm replying at the right point in the chain. I hope this is right. There is now a new version of TKB 6(u) at <http://www.freebmd.org.uk/vol_faq.html#6u> - not mine I wish to add. The middle bit has been rewritten so the example is now all about alternatives "X or Y", i.e. no "X alias Y". I think that it is a great improvement in clarity. Thanks to who ever redrafted it. Regards, Philip -----Original Message----- From: Barrie [mailto:freebmd@myarcher.net] Sent: 05 April 2012 16:18 To: freebmd-admins@rootsweb.com Subject: Re: Message Posted on behalf of BillP No, Bill is not right. http://www.freebmd.org.uk/vol_faq.html#6u gives an example: #COMMENT(2) entry reads BONUS alias CHAPMAN for surname so <alternative> is the alternative names, in the case given <alternative> is "Curphey or Bradley". However, the item will be updated because as has been pointed out "alias" is very uncommon so the whole item should be biased towards "or". At the same time this misunderstanding can be addressed. Barrie On 19:59, Keith Simpson wrote: > Allan, > I have been asked by BillP a transcriber in my group to post this message on > their behalf. They were unable to post the message themselves , some > technical difficulties. > Keith > GANDALF UK > > Message reads, > > Allan, > > I think that you have given conflicting advice for the #COMMENT line when > completing the transcription for alternative names when referencing the FAQ > concerned. > > The final part of the FAQ concerned says: > So, in general, the comment should read: > > #COMMENT(2) entry reads <alternative> for <field> Where <alternative> is the > alternative from the record and <field> is the field in the record, either > surname, given name, mother's name, spouse name, district, volume of page > number. Note that there is no space between "#COMMENT" and the "(2)". > > > For Birth records and a duplicate mothers name you suggest: > #COMMENT(2) entry reads Curphey or Bradley for mother's name. > > Yet my interpretation of the FAQ is: > #COMMENT(2) entry reads Bradley for mother's name. > > Am I right or missing something? > Bill > > -------Original Message------- > > From: Allan Raymond > Date: 01/04/2012 19:41:33 > To: freebmd-admins@rootsweb.com > Subject: Tip of the Day (No. 6) (last updated 01 April 2012) - > AlternativeSpouse or Mother's Names in Marriage or 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 is being reissued with minor amendments based on recent > feedback from our transcribers and is 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. > > We have also recently enhanced our automatic reporting system so that files > containing possible errors in dealing with alternative names are flagged up. > > 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 # and COMMENT or between #COMMENT and (2). > > 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 wording describes > accurately the reason for the #COMMENT(2) line. > > If there are more than two alternative names, enter one record for each and > put in one comment covering all the names, e.g. #COMMENT(3) after the first > of three entries. > > It may be useful to remember the usual Windows shortcuts CTRL-C for copy, > CTRL-X for cut and CTRL-V for paste, all work in WinBMD. > > So rather than having to retype the complete #COMMENT(2) line each time it > is required just CTRL-C one of the appropriate lines below > > #COMMENT(2) entry reads name1 or name2 Bradley for spouse name > or > #COMMENT(2) entry reads name1 or name2 for mother`s name > > and then CTRL-V to paste in WinBMD not forgetting to change "name1 or name2" > by the actual names. > > The automatic reporting system checks if transcription of alternative name > entries have been transcribed in accordance with the information above and > any files identified as being suspect are listed in > http://www.freebmd.org.uk/SuspectFilesComments.html . > > It would be appreciated if transcribers in conjunction with their > Coordinators could check http://www.freebmd.org.uk/SuspectFilesComments.html > to see if any of their files are listed and where appropriate correct the > files by including the appropriate #COMMENT(2) line. At present there are > over forty four thousand files (i.e. over 44,000) files appearing in the > report creating a huge task for Coordinators and some of their volunteers. > > > > As an aside > > A misplaced #COMMENT(2) line can have the wrong outcome. > > In the example below an invalid #COMMENT(2) line 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 > > > --Certified Virus Free by 4SecureMail.com ICSA-Certified Scanner--