The multiple kit analysis function works beautifully with tag groups. Another benefit of tag groups, is that when I don’t remember the kit number of a cousin whose results I wish to view, I can look it up quickly by displaying the people in that tag group (from the View/Change your profile (password, email, groups) on the top left)
My previous post about tag groups mentioned that tag groups are a quick way to see where a new match fits in by looking at their one to many page for your tag colors. However this is less useful for a distant cousin match (fewer colored tags) or an iffy paper trail match. In those cases I put the new person in my Unknown group (which only ever has the one person being analyzed) and then compare with all the relatives I expect a match to, by using their tag groups.
The main GEDmatch page has a box called Analyze Your Data and towards the bottom of that box you can see Multiple Kit Analysis with a big red NEW next to it. The “new” is because you can now use tag groups for this analysis. When you click Multiple Kit Analysis to get to that function, you will see a page like the one shown below. The old way of doing multiple kit analysis, by typing in each one, is still available from the Manual Kit Selection/Entry tab on this page or by checking boxes in various other functions like one-to-many.
My tag groups: note that I am using shades of aqua and blue for my Etne, Hordaland, Norway descended cousins
You can check the tag groups of interest and compare them to the new person (the Unknowns group for me) in all the wonderful ways the multiple kit analysis gives you (Click here for the slides on that from my most recent GEDmatch presentation).
Recently I have been searching for a “Lee Oleson” who is the grandfather of a third cousin match at Ancestry. He was only in town long enough to get my match’s grandmother with child. This third cousin’s one to many lights up with the colors of my Etne, Hordaland, Norway side relatives. So I set myself a project of tracing forward all the descendants of the eight children of my Etne great-great-grandparents to see if I could find Lee.
The new Tier 1 one-to-many at GEDmatch includes a link to your match’s family tree when that is available. Clicking the word GED next to that kit’s email address takes you to the tree your match has uploaded to GEDmatch. The word WIKI links to the compact tree view at WikiTree.
GEDmatch GEDCOM link
Clicking on the GED for a match takes you to the profile of the individual in the linked tree at GEDmatch.
Here is what you would see if you clicked on the GED next to my Dad’s name. Note the words “GEDmatch Ref: “ followed by a long number. That number is the id of this GEDCOM which you can use to compare to your own GEDCOM in the “2 GEDCOMs “ function on your home page.
Of course, I immediately click on the pedigree button in the little menu at the top of this individual page and then look through the pedigree on the next page for familiar names and places. Here is what the top half of my Dad’s tree looks like at GEDmatch. Note the default number of generations shown is 5. You can change that to a larger number (I often go to 8) and then click submit to see more generations.
Clicking on WIKI next to a match in the Tier 1 One-to-Many listing takes you to that match’s compact pedigree at the collaborative world tree WikiTree. This is automated and the connection to Wikitree happens because a member of that site has added a GEDmatch kit number to a profile there. Here is the top piece of what you see when you click on my WIKI.
Being able to group my cousins from different lines into colored “tag groups” on the GEDmatch site is a wonderful new feature. It makes it easy to quickly see which line a new cousin fits into because the new Tier 1 one-to-many display uses those colors to highlight the kits belonging to a group. See the image below for a colorful example of my own one-to-many.
Tag groups are for everyone, not just tier one members,. They can also be used to select what to look at in the “Multiple kit Analysis” function. However they are not yet included in any of the other functions, like the people who match both kits, triangulation or matching segments and of course not the regular one-to-many.
Here is a quick example of how a new close cousin can be visually assigned to a line when you use the tier 1 one-to-many on their kit. My tag groups use yellow for close family, aqua for paternal first cousins, shades of blue for my Etne lines, green for my Munson line, and purple for my Wold line. Which line is this cousin on?
Right, she is a Munson.
Other New Features
I love that the newest pages at the GEDmatch site include a top menu. and use tabs to make for a more compact display
Also the new Tier 1 version of the one-to-many is outstanding. In addition to showing those colored tag groups. it has search boxes at the top of every column for just that column. The form to invoke the one-to-many is gone, instead the selection is neatly across the top so you can change it dynamically. The long details that used to be at the top of the page now only show up as a pop-up window if you click the tip button.
Yesterday I did a presentation on all of this, click here for the slides which show many of the details of these new features.
Having just received the Etne, Norway local history books (bygdebuker) for Christmas, I have spent countless hours looking at my ancestors in them. Naturally I have been trying to think of even more ways to use these books.
An idea that came to me was to look at my Dad’s one-to-many X matches at GEDmatch.com and see if I could find a match where I could follow the lines and connect them to Dad’s maternal grandad via those books
The largest X match he had with an unfamiliar name and email was to *k for 26.8 centimorgans (cMs) and it included a small autosomal match of 6.3 cMs. This seemed promising so I used the user lookup function on my GEDmatch home page and was delighted to see that she had uploaded a GEDCOM.
The GEDCOM number is clickable from the lookup result and it takes you to a page listing the individual. Of course what you really want is the pedigree to quickly scan for relatives in common and there is a button for that at the top of the page. Better is to use the compare 2 GEDCOMs feature from the home page to compare your match’s GEDCOM to your own. Works great if you both have deep trees but I had no luck with that for *k.
Next I clicked on the pedigree button at the top of her individual listing in the GEDCOM which took me to her pedigree page. Nothing jumped out at me and most of them were from Germany.
Perhaps this post needs the subtitle , “My Perfect Cousin Goes to GEDmatch.”
Most of us can keep track of information in spreadsheets. So how to do that with DNA? Well, the idea is to keep a list of matching DNA segments so that a new match can be compared to your known family members. That way you may be able to see where they fit in.
If you have tested at 23andme or Family Tree DNA, you can download your list of matches with their matching DNA segments either directly from your testing company or by using the tools at DNAgedcom. However AncestryDNA does not provide a list of matching segments.
Extract from my Dad’s Master DNA Segment Spreadsheet (click for a larger version)
Why would you want those? The short answer is to figure out which line a new DNA cousin belongs to. For the long answer, read on. For more posts about DNA spreadsheets click here or in the tag cloud, lower right hand column.
AncestryDNA testers can make a DNA segment spreadsheet by using any of a number of utilities at the GEDmatch web site. Start by uploading your raw DNA data (click here for that “how to” post). Your results will usually be ready for full comparisons the next day. Then buy the tier 1 utilities for at least one month ($10).
My preference for making a first spreadsheet is to use the GEDmatch Matching Segment Search. Then I go through the top matches from the ‘One-to-many’ matches report with that spreadsheet as a reference. I add notes on what I discover to my new spreadsheet.
Here is the step by step of what I did for my perfect cousin J.M. whose AncestryDNA results I blogged about in my previous post.