RootsWeb.com Mailing Lists
Total: 3/3
    1. Re: Matching entries
    2. Ben Laurie
    3. Dave Mayall wrote: >>Thanks Dave - I wondered if James Fox was a "onenamer" and if this would >>prove to be the answer. And I did read to the end of your reply and, I >>think, understood the principle. >>Now another question - what happens when the second keying is done and > > there > >>are now three entries for some of this particular batch of "Friends"? > > > As the software stands at present, the double keying would align onto > Steve's keying, and we would see one single keyed and one double keyed in > the results For the Manchester James. > > All the others would simply appear as double keyed (the system makes no > distinction between double or triple or 21-fold keying of a record) > > The challenge that faces us is to tweak the software to cope with this, and > it will be a challenging bit of software to write, for there are no easy > fixes here. I'd note that one-name submissions treat each line as a separate accession. If a one-name is submitted as something else, it breaks the system. The easy fix is to fix the type. Anything presorted should be classed as one-name. Cheers, Ben. -- http://www.apache-ssl.org/ben.html http://www.thebunker.net/ "There is no limit to what a man can do or how far he can go if he doesn't mind who gets the credit." - Robert Woodruff

    12/23/2003 05:58:36
    1. Re: Matching entries
    2. Dave Mayall
    3. On Wed, 24 Dec 2003 00:58:36 +0000, you wrote: >Dave Mayall wrote: >>>Thanks Dave - I wondered if James Fox was a "onenamer" and if this would >>>prove to be the answer. And I did read to the end of your reply and, I >>>think, understood the principle. >>>Now another question - what happens when the second keying is done and >> >> there >> >>>are now three entries for some of this particular batch of "Friends"? >> >> >> As the software stands at present, the double keying would align onto >> Steve's keying, and we would see one single keyed and one double keyed in >> the results For the Manchester James. >> >> All the others would simply appear as double keyed (the system makes no >> distinction between double or triple or 21-fold keying of a record) >> >> The challenge that faces us is to tweak the software to cope with this, and >> it will be a challenging bit of software to write, for there are no easy >> fixes here. > >I'd note that one-name submissions treat each line as a separate >accession. If a one-name is submitted as something else, it breaks the >system. The easy fix is to fix the type. No, RANDOM treats each line as a separate Accession. ONENAME is a halfway house which behaves like SEQUENCED except that it includes an implicit +BREAK (and hence a new Accession) on change of surname. -- Dave Mayall

    12/24/2003 12:32:16
    1. Re: Matching entries
    2. Ben Laurie
    3. Dave Mayall wrote: > On Wed, 24 Dec 2003 00:58:36 +0000, you wrote: > > >>Dave Mayall wrote: >> >>>>Thanks Dave - I wondered if James Fox was a "onenamer" and if this would >>>>prove to be the answer. And I did read to the end of your reply and, I >>>>think, understood the principle. >>>>Now another question - what happens when the second keying is done and >>> >>>there >>> >>> >>>>are now three entries for some of this particular batch of "Friends"? >>> >>> >>>As the software stands at present, the double keying would align onto >>>Steve's keying, and we would see one single keyed and one double keyed in >>>the results For the Manchester James. >>> >>>All the others would simply appear as double keyed (the system makes no >>>distinction between double or triple or 21-fold keying of a record) >>> >>>The challenge that faces us is to tweak the software to cope with this, and >>>it will be a challenging bit of software to write, for there are no easy >>>fixes here. >> >>I'd note that one-name submissions treat each line as a separate >>accession. If a one-name is submitted as something else, it breaks the >>system. The easy fix is to fix the type. > > > No, RANDOM treats each line as a separate Accession. ONENAME is a > halfway house which behaves like SEQUENCED except that it includes an > implicit +BREAK (and hence a new Accession) on change of surname. I guess that strictly ONENAME is wrong then, sadly. Cheers, Ben. -- http://www.apache-ssl.org/ben.html http://www.thebunker.net/ "There is no limit to what a man can do or how far he can go if he doesn't mind who gets the credit." - Robert Woodruff

    12/24/2003 09:15:00