Some people eat, sleep and chew gum, I do genealogy and write...

Sunday, August 23, 2015

Some Unexpected Information from

I don't completely know what I expected to learn from's Record Match technology, but I suspect that some of the things I have learned were not planned or foreseen. In fact, some of them are pretty strange. Let me start with a bit of explanation. is one of the partner programs with As part of that partnership, has a link, through its Record Matches, with the Family Tree.

The unexpected information results, in part, from the fact that I uploaded my entire pedigree to some years ago. The program has had a long time to find sources right from the time the Record Match technology was initiated. For this reason, your results may vary. Another contributing factor to the unexpected results is the fairly recent inclusion of the Family Tree data.

Here is what happens. shows that I have 14,420 Record Matches. When I view that huge number of matches by "Person," I can see that one of my ancestors, Nathaniel Potter, has 247 matches. When I look at the list of matches, I see something rather strange and unexpected. There are a huge number of "Nathaniel Potters" listed as coming from the Family Tree. Guess what? has found all the duplicate Nathaniel Potters with unique Personal Identification Numbers. If I click on each of the multiple Nathaniel Potters, I find each of them are duplicates in the Family Tree, each with their own PID.

In short, if finds multiple copies of a person in the Family Tree, then they are very likely to be duplicates. By the way, FamilySearch does not find, nor can it merge all these duplicates until the transition from is completed. The multiple copies also indicate duplicates in and

For Nathaniel Potter, when I look at one of the duplicate Family Tree records, I get 246 additional Record Detective matches. Nearly all of these are in the Family Tree. is showing me, graphically, I might add, each of the real duplicates of my ancestors in the Family Tree; theoretically, I could count the exact number and track down each of the PIDs but FamilySearch can't do anything about it right now.

No comments:

Post a Comment