Bob Spiers
LostCousins Superstar
They say you can't teach an old dog new tricks, but surely an old dog should remember the tricks he learnt as a pup. That is a roundabout way of saying this old dog fell for the most novice of genealogical data entering errors by failing to spot he had added a letter to a surname that completely changed its indexing status, and caused a dilemma far beyond the innocence of the mistake.
Setting the scene I had at long last found a credible spouse for a great grand Aunt by the name of James Haley (from Ireland). They had 5 children. I always enter new data first on my stand-alone PC (non internet) using Family Tree Legends (FTL) so all were duly added. In a later Census her spouse was shown as John Haley (also from Ireland) and 3 new children. (I found out when James died she moved in (no marriage found) with his brother John, but that is not relevant to the story). I duly added the new 'partner' and the 3 new children.
Back to the story: I entered James as Haley and the first child the same. However inadvertently, possibly because I believed the surname was crying out to be Hayley, the subsequent children was recorded as Hayley. I also entered John as Hayley and the 3 children likewise. I was totally unaware of this of course and was now ready to add the information into Ancestry and my Tribal pages. To commence I used the FTL index to locate the Haleys' and found but two, James and the first child. So what had happened to the others?
It is hard to imagine how this mystified me and yet when I reverted to searching on my Great Aunt and opening her page, there was James with the 5 children and I DID NOT SPOT THE ADDITIONAL 'Y'. I clicked on her second spouse/partner and found him with the 3 children. I could not for the life of me work out why 8 names were missing from the index. It took me ages to discover the problem was the spelling of the surname. I am reminded of the old computer saying of 'crap in=crap out' and by golly did this ring true. It was no big thing to correct but there is more than enough work to transfer data into my various data bases -thank goodness FTM syncs with Ancestry (for now at any rate)- without making silly mistakes like that. I am duly penitent.
Setting the scene I had at long last found a credible spouse for a great grand Aunt by the name of James Haley (from Ireland). They had 5 children. I always enter new data first on my stand-alone PC (non internet) using Family Tree Legends (FTL) so all were duly added. In a later Census her spouse was shown as John Haley (also from Ireland) and 3 new children. (I found out when James died she moved in (no marriage found) with his brother John, but that is not relevant to the story). I duly added the new 'partner' and the 3 new children.
Back to the story: I entered James as Haley and the first child the same. However inadvertently, possibly because I believed the surname was crying out to be Hayley, the subsequent children was recorded as Hayley. I also entered John as Hayley and the 3 children likewise. I was totally unaware of this of course and was now ready to add the information into Ancestry and my Tribal pages. To commence I used the FTL index to locate the Haleys' and found but two, James and the first child. So what had happened to the others?
It is hard to imagine how this mystified me and yet when I reverted to searching on my Great Aunt and opening her page, there was James with the 5 children and I DID NOT SPOT THE ADDITIONAL 'Y'. I clicked on her second spouse/partner and found him with the 3 children. I could not for the life of me work out why 8 names were missing from the index. It took me ages to discover the problem was the spelling of the surname. I am reminded of the old computer saying of 'crap in=crap out' and by golly did this ring true. It was no big thing to correct but there is more than enough work to transfer data into my various data bases -thank goodness FTM syncs with Ancestry (for now at any rate)- without making silly mistakes like that. I am duly penitent.