Login to participate
  
Register   Lost ID/password?

Louis Kessler’s Behold Blog

Using a GEDCOM file to add to FamilySearch - Tue, 23 Feb 2021

Today I got a newsletter from Elizabeth O’Neal, who runs the Heart of the Family site.  The newsletter was about “Getting the Most Out of RootsTech”. What caught my attention was her point 5: “Check your growing list of cousins.”

Elizabeth was talking about Relatives at RootsTech, which looks at your FamilySearch tree and sees if there are any of the over 320,000 attendees that you are connected to. Some people like Randy Seaver are connected to tens of thousands of people. Me: zero, zilch, nil, none.

I had already added all of my direct ancestors to FamilySearch, which amounted to about 31 people, and I connected them to anyone I could find at FamilySearch who was related, putting in the necessary intermediaries to connect us.

But what Elizabeth said that I did not know was that you can upload a GEDCOM file to FamilySearch. She gave this link to the FamilySearch article: How do I upload my GEDCOM file.

This does not upload your information to FamilySearch’s FamilyTree, but uploads it to their Pedigree Resource File (PRF) which “allows you to share your family history on FamilySearch without letting other people change it.”

One you’ve done that, then you can copy that information into FamilyTree. See the article: How do I copy information from my GEDCOM into Family Tree?

So I had to try that. Other than this possibly being a very good way to get my information into the tree, it might allow me to fairly quickly connect more of my branches to the main tree. And maybe I’ll result in finding some relatives who are also registered for RootsTech.

So let’s try it and see how it goes.


Initial Step:  Create GEDCOM

I have my main tree at MyHeritage. I use their free desktop program Family Tree Builder which keeps the two synced together. I’ll open Family Tree Builder and export my GEDCOM.

image

I’ll select all people and omit all living people and all people and data that I’ve marked private. I’m not sure if the photos I have of my relatives will transfer to FamilySearch, but I’ll export them in the hope that they will.

Checking the GEDCOM file with Behold, I can see I have 6413 people in the file. The GEDCOM includes all the living people in the file, so all the father/mother/child connections are there, but none of them have any information included, not even the NAME tag. I do want the tree to connect to me, so I find my INDI record in the file and add to it a new line:
     1 NAME Louis /Kessler/


Step 1: Upload my GEDCOM to FamilySearch

1. I sign into FamilySearch and click Search.
2. I click Genealogies.
3. I scroll past the search fields to the section titled What are Genealogies?
4. At the end of the section, I click Submit Your Tree.
5. I click Upload GEDCOM File.

image

I chose my file, entered a tree name and description and clicked Upload.

In very little time (less than a minute), my tree was uploaded and ready to compare.

image


Step 2: Compare My File to FamilySearch Family Tree

So now I press the Compare button in the screenshot above. The word “Comparing…” appears as the Status while this takes place. After about 15 minutes, the Status changes to “Ready”.

I press the View link that now appear where Compare used to be. The results flash for a second and then I get taken to this:

image

I go back and try again but this keeps happening. I try it in Edge, Google Chrome and Firefox. It’s a problem in all browsers. The page before does stick around long enough that I can do a screen capture:

image

So there’s a glitch here that FamilySearch should fix, but it looks like the processing worked. I had 2128 non-living people in my GEDCOM of which 680 are already in Family Tree, 42 are potential matches and 1406 that I can add to Family Tree.


Step 3: Review the Potential Matches List

(*** NOTE:  I learned after the fact that it might be better to do Step 5 before doing steps 3 and 4.  See Step 5, below)

Aha! If I go back and click on “Potential Matches” before it transforms to the “Oops, I did it again” page, the Potential Matches page does appear. Glitch workaround success!!  I get this:

image

Below the summary, on the left are my 42 potential matches. The first potential match is shown on the right comparing my GEDCOM to what’s on Family Tree. Now I can select in the top right either “Not a Match” or “Yes”. This one is a “Yes”.

After clicking “Yes”, I get this screen:

image

I can now decide to replace some of the information for this person in the tree with the information from my GEDCOM. I’m going to be very conservative here, and not transfer anything that is different or suspect. If I don’t click on any of the “Replace” links, then the “Save” button doesn’t activate. 

If I do click on at least one replace link, and then click on “Save”, then the following Reason for Update box appears:

image

They do not, however, force you to enter a reason. You can just click “Continue” and it will be saved.

They gave me two potential matches for the following person, but neither was the correct one, so I clicked “Not a Match” for each one. That took me to this screen:

image

I now clicked “Add” to add this person to Family Tree.

The name of each potential match links to the Family Tree entry for the person, so when I’m in doubt, I can check in more detail what Family Tree shows.

Of the 42 potential matches, about half were the correct person so I merged them. And the other half were not the correct person, so I added them. 

I found some new information that I didn’t have before, as well as a few corrections which I then added to my MyHeritage tree.

It took a couple of hours to go through the 42 potential matches:  a very worthwhile effort.

I liked the way this procedure worked. It was nicely implemented by the FamilySearch people.


Step 4: Review the Add to Family Tree List

Here I have 1407 people. It appears they have to be added one at a time. It takes two clicks per person, one to add them, and one to navigate to the next person.

Looks like this will be grunt-work that I’ll save to do while I’m watching some RootsTech sessions.


Step 5: Review the Already in Family Tree List

This list now included the 680 people that were already in Family Tree, plus the people I added from Steps 3 and 4. If I were doing this, I’d review this list first before the others get added. 

It is nice to review the information that I have for each of these people versus what FamilySearch has. It is presented in the same format as shown in the “Already in Family Tree” graphic (above). You get the opportunity to replace information in Family Search if you’re sure (with evidence hopefully) that yours is correct.


Final Thoughts

I never realized that FamilySearch Family Tree had this capability to load a GEDCOM, compare it to the tree, and merge your information into it.

I was very impressed by how it worked. Family Tree already had 680 of my people in my tree, and this will allow me (after I do the grunt-work) to add 1448 more people, which is all the other people in my Family Tree Builder tree who are not living or private.

I don’t know when FamilySearch added this capability, but thank you Elizabeth O’Neal, for making me aware of it.

Hopefully the addition of so many new people will allow Relatives at RootsTech to find me a relative before the end of RootsTech.




Followup Feb 24:  I went through the 1407 people to be added and added them one at a time. About 10 of them ended up being duplicates because the name or a date was different than the person it should have matched. So I used FamilySearch tools to combine them. I’m sure there are a few others that I’ll have to find over time. Also, for some reason, FamilySearch gave me an error when trying to add 3 people, so I couldn’t add those three.

A few glitches, but I got the job done. I do see why they don’t want to blindly add people’s GEDCOMs en masse, as that would cause a mess.

Double Match Triangulator 4.0 - Tue, 23 Feb 2021

Yesterday, I released  new version of Double Match Triangulator. This took longer than I hoped, but finally it’s out.

In late November, GEDmatch changed the format of their segment match file and also made a change to their one-to-one report, so DMT needed to be updated to handle those.

Also in May 2019, MyHeritage changed their segment match files to include a unique ID for each person. DMT now uses the name plus part of that ID so that like GEDmatch, two people with the same name will be differentiated.

But the biggest changes are under the hood.  I reviewed most of DMTs internals and geared it to give you as much of the information and assumptions that you can make from your data.

DMT’s interface now looks like this:

The only change to the interface is the addition of a Male (1 X) / Female (2 X) selector. The selection will be reflected in the number of X chromosomes DMT includes in the results. DMT now knows that for males, ancestral paths on the mother’s side are the only one allowed. And it understands that no ancestral path on the X can go through two F (fathers) in a row.

I also found and fixed a bug that was causing the Map page to take 10 times longer to generate than it needed to.


DMT, Painting and Clustering

Double Match Triangulator works differently than all the other autosomal DNA tools. By comparing all the segment matches of two or more people, DMT determines every single triangulation between the people whose files you have.

The addition of user-entered Most Recent Common Ancestors (MRCAs) in DMT version 3 allowed DMT to take the next step and allow painting of ancestral paths to segments.  This is exactly what you do manually with DNA Painter, except that with DNA Painter, you are only adding single matches.  DMT used triangulations and makes use of the fact that segments that don’t triangulate likely are on the opposite parent as those that do triangulate.

DMT also calculates all possible inferred matches, where Person B matches Person C but Person A does not. Basically, these refute the ancestral line towards the more distant MRCA of Persons B and C. .

Put those together, and you can get most of your genome painted fairly easily.  DMT will create a file for you that you can input into DNA painter. For example, if you know 11 MRCAs and have their segment match files, this is what the results might look like when uploaded to DNA Painter:

Other autosomal analysis tools that do clustering have become available in the past few years. DMT does clustering as well. It does so by using the most common ancestral path of a person’s segments to be the cluster for the person.

With those 11 MRCAs in the above example, DMT places people into the following clusters:

image

In this example, almost half the people got assigned to a cluster on either the father (F) or mother (M)’s side. For people who you don’t know your relationship to, this will be a great clue as to which ancestral line you should look at first.


DMT is Available at:

The new version 4 of DMT can be found on the DMT website:  www.doublematchtriangulator.com

For those of you who have already purchased DMT ($40 USD) it is as it always will be a free upgrade. Simply download and install it.

For those who haven’t, please feel free to try the program. The download is fully functional but only shows you results for chromosome 1. That should be enough to give you a good feeling for what it can do.

GEDCOM 7.0 - Fri, 19 Feb 2021

**UPDATE** June 8: 
FamilySearch has released the official version of GEDCOM 7.0.
See my blog post: GEDCOM 7.0, Official.

It appears that a GEDCOM Version 7.0 Release Candidate will be announced at RootsTech Connect on February 25.

This will likely take place in the session by Gordon Clarke titled:
”GEDCOM is Alive and getting Smarter” –> See Feb 24, 2021, below.

The home for GEDCOM 7.0 appears to be:  https://gedcom.io

image

The current Release Candidate 7.0.0-rc1 appears to be available:

As a web page:  https://gedcom.io/specifications/GEDCOM7rc.html

As a PDF:  https://gedcom.io/specifications/gedcom7-rc.pdf


   

I’m going to keep track on this blog post of anyone writing about GEDCOM 7.0. Please let me know of any new articles you find and I’ll post them here:

Feb 19, 2021:

Feb 20, 2021:

Feb 21, 2021:

Feb 22, 2021:

Feb 23, 2021:

Feb 24, 2021

Feb 25, 2021

  • Gordon Clarke’s two presentations inexplicably no longer are available from RootsTech Connect.  The YouTube videos at the links above (Feb 24) are unavailable as well.
  • The gedcom.io site also became inaccessible.
  • The three blog posts on James Tanner’s Genealogy’s Star personal blog have been removed. (see above, Feb 19, 20, 23)
  • The GEDCOM Standard page at familysearch.org has removed the “What can we expect in the future?” and “What is GEDZip?” paragraphs that referenced GEDCOM 7.0 and GEDZip. (See Feb 19)

Feb 27, 2021

  • Markus Henn tweeted:  Answer from @RootsTechConf staff: @FamilySearch has determined to not publish information regarding #GEDCOM standards at this time. This includes some content intended for #RootsTechConnect 2021. We apologize for any inconvenience. Thank you for your patience and support.”

Feb 28, 2021