Family Tree DNA’s PUBLIC Y DNA Haplotree

It’s well known that as a result of Big Y testing that Family Tree DNA has amassed a huge library of Y DNA full sequence results that have revealed new SNPs, meaning new haplotree branches, for testers. That’s how the Y haplotree is built. I wrote about this in the article, Family Tree DNA Names 100,000 New Y DNA SNPs.

Up until now, the tree was only available on each tester’s personal pages, but that’s not the case anymore.

Share the Wealth

Today, Family Tree DNA has made the tree public. Thank you, thank you, THANK YOU Family Tree DNA.

To access the tree, click here, but DON’T sign in. Scroll to the bottom of the page. Keep scrolling, and scrolling…until you see the link under Community that says “Y-DNA Haplotree.” Click there.

The New Public Haplotree

The new public haplotree is amazing.

This tree isn’t just for people who took the Big Y test, but includes anyone who has a haplogroup confirming SNP OR took the Big Y test. Predicted haplogroups, of course, aren’t included.

Each branch includes the location of the most recent known ancestor of individuals who carry that terminal SNP, shown with a flag.

The branches are color coded by the following:

  • Light blue = haplogroup root branches
  • Teal or blue/green = branches with no descendants
  • Dark blue = branches that aren’t roots and that do have at least one descendant branch

The flag location is determined by the most distant known ancestor, so if you don’t have a “Most Distant Known Ancestor” completed, with a location, please, please, complete that field by clicking on “Manage Personal Information” beneath your profile picture on your personal page, then on Genealogy, shown below. Be sure to click on Save when you’re finished!

View Haplotree By

Viewing the haplotree is not the same as searching. “View by” is how the tree is displayed.

Click on the “View By” link to display the options: country, surnames or variant.

You can view by the country (flags), which is the default, the surname or the variants.

Country view, with the flags, is the default. Surname view is shown below.

The third view is variant view. By the way, a variant is another word for SNP. For haplogroup R-M207, there are 8,202 variants, meaning SNPs occurring beneath, or branches.

Reports

On any of the branch links, you’ll see three dots at the far right.

To view reports by country or surname, click on the dots to view the menu, then click on the option you desire.

Country statistics above, surname below. How cool is this!

Searching

The search function is dependent on the view currently selected. If you are in the surname view, then the search function says “Search by Surname” which allows you to enter a surname. I entered Estes.

If I’m not currently on the haplogroup R link, the system tells me that there are 2 Estes results on R. If I’m on the R link, the system just tells me how many results it found for that surname on this branch and if there are others on other branches.

The tree then displays the direct path between R-M207 (haplogroup R root) and the Estes branch.

…lots of branches in-between…

The great thing about this is that I can now see the surnames directly above my ancestral surname, if they meet the criteria to be displayed.

Display criteria is that two people match on the same branch AND that they both have selected public sharing. Requiring two surnames per branch confirms that result.

If you want to look at a specific variant, you can enter that variant name (BY490) in the search box and see the surnames associated with the variant. The click on “View by” to change the view from country (maps) to surnames to variants.

Change from country to surname.

And from surname to variants.

What geeky fun!!!

Go to Branch Name

If you want to research a specific branch, you can go there directly by utilizing the “Go to Branch Name” function, but you must enter the haplogroup in front of the branch name. R-BY490 for example.

When you’re finished with this search, REMOVE THE BRANCH NAME from the search box, if you’re going to do any other searches, or the system thinks you’re searching within that branch name.

My Result Isn’t Showing

In order for your results to be included on the tree, you must have fulfilled all 3 of these criteria:

  • Taken either a SNP or Big Y test
  • Opted in for public sharing
  • More than one result for that branch with the same exact surname

If you think your results should be showing and they aren’t, check your privacy settings by clicking the orange “Manage Personal Information” under your profile picture on your main page, then on the Privacy and Sharing tab.

Still not showing? See if you match another male of the same surname on the Big Y or SNP test at the same level.

If your surname isn’t included, you can recruit testers from that branch of your family.

How Can I Use This?

I’m like a kid with a new toy.

If any of your family surnames are rather unique, search to see if they are on the tree.

Hey look, my Vannoy line is on haplogroup I! Hmmm, clear the schedule, I’m going to be busy all day!

Every haplogroup has a story – and that story belongs to the men, and their families, who carry that haplogroup! I gather the haplogroups for each of my family surnames and this public tree just made this task much, MUCH easier.

Discovering More

If the testers have joined the appropriate surname project, you may also be able to find them in that project to see if they descend from a common line with you. To check and see, click here and then scroll down to the “Search Surname” section of the main Family Tree DNA webpage and enter the surname.

You can see if there is a project for your surname, and if not, your surname may be included in other projects.

Click on any of those links to view the project or contact the (volunteer) project administrators.

Want to search for another surname, the project search box is shown at the right in this view.

What gems can you find?

Want to Test?

If you are a male and you want to take the Big Y test or order a haplogroup confirming SNP, or you are a female who would like to sponsor a test for a male with a surname you’re interested in, you can purchase the Big Y test, here. As a bonus, you will also receive all of the STR markers for genealogical comparison as well.

Wonder what you can learn? You will be searching for matches to other males with the same surname. You can learn about your history. Confirm your ancestral line. Learn where they came from. You can help the scientific effort and contribute to the tree. For more information, read the article, Working with Y DNA – Your Dad’s Story.

Have fun!!!

_____________________________________________________________________

Standard Disclosure

This standard disclosure appears at the bottom of every article in compliance with the FTC Guidelines.

I provide Personalized DNA Reports for Y and mitochondrial DNA results for people who have tested through Family Tree DNA. I provide Quick Consults for DNA questions for people who have tested with any vendor. I would welcome the opportunity to provide one of these services for you.

Hot links are provided to Family Tree DNA, where appropriate. If you wish to purchase one of their products, and you click through one of the links in an article to Family Tree DNA, or on the sidebar of this blog, I receive a small contribution if you make a purchase. Clicking through the link does not affect the price you pay. This affiliate relationship helps to keep this publication, with more than 900 articles about all aspects of genetic genealogy, free for everyone.

I do not accept sponsorship for this blog, nor do I write paid articles, nor do I accept contributions of any type from any vendor in order to review any product, etc. In fact, I pay a premium price to prevent ads from appearing on this blog.

When reviewing products, in most cases, I pay the same price and order in the same way as any other consumer. If not, I state very clearly in the article any special consideration received. In other words, you are reading my opinions as a long-time consumer and consultant in the genetic genealogy field.

I will never link to a product about which I have reservations or qualms, either about the product or about the company offering the product. I only recommend products that I use myself and bring value to the genetic genealogy community. If you wonder why there aren’t more links, that’s why and that’s my commitment to you.

Thank you for your readership, your ongoing support and for purchasing through the affiliate link if you are interested in making a purchase at Family Tree DNA, or one of the affiliate links below:

Affiliate links are limited to:

 

 

 

 

Ancestor Birthdays Mean Presents for YOU!

I’ve been wanting to celebrate my ancestors’ birthdays for some time now, and I’ve finally figured out exactly how to accomplish this goal in a really fun way.

Being reminded once a year about their birthday and the anniversary of their death reminds me to work on their genealogy, and in particular, genetic genealogy. With more people testing every single day, meaning different people at every vendor, we need to check often with specific ancestors in mind. You never know who’s going to be the person who puts the chink in that brick wall.

With this in mind, I’ve put together a spreadsheet to track what I know about each ancestor. This makes it easy to schedule those dates in my calendar, with a reminder of course, and then to check my spreadsheet to see what information might have been previously missing that might be able to be found today.

It’s like a birthday present for them, but now for me. I am, after all, their heir, along with the rest of their descendants of course! If I’m lucky, I inherited part of their DNA, and if not, their DNA is still relevant to me.

Checking the List

Here’s my spreadsheet checklist for each ancestor:

  • Birth date
  • Birth place
  • Death date
  • Death place
  • Spouse
  • Y DNA haplogroup (if male)
  • Mitochondrial DNA haplogroup
  • Autosomal confirmed
  • Ancestry Circle

New information becomes digitized every year making new information available.

Additionally, some items may change. For example, if a base haplogroup was previous known, a deeper haplogroup might be available a year later if someone has taken a more detailed test or the haplogroup name might have been updated. Yes, that happens too.

I originally had a triangulation column on the spreadsheet too, but I pretty quickly discovered that column was subject to lots of questions about interpretation. Is the actual ancestor triangulated, or the line? I decided that “autosomal confirmed” would suffice to cover whatever I decide constitutes confirmation and a comment column could hold the description. For example, my grandparents are autosomal confirmed because I match (and triangulate) with cousins who are descended from ancestors upstream of my grandparents. If my grandparent wasn’t my grandparent, I wouldn’t be related to those people either. In particular, first cousins.

I also added an “Article Link” column to paste the link to that ancestor’s 52 Ancestors article so I can quickly check or maybe even provide this spreadsheet to a family member.

Here’s an example of what the first several entries of my Ancestor Birthday Spreadsheet look like.

Ancestor Birthday Presents for You

In order to remind myself to check on my ancestors’ status, on their birth and death days, I schedule reminders in my phone calendar. Every morning when I wake, I’m greeted by my ancestor – well – at least this much of them.

  • First, I check at Family Tree DNA for new matches, haplogroups and the presence of my family lines in surname projects.
  • Then it’s off to Ancestry to see if I have any new green leaf DNA or record hints, to add or update the circle for this particular ancestor, and to see if any of my matches would be a candidate for either Y or mitochondrial DNA testing, assuming they reply to messages and agree to test at Family Tree DNA. I keep a separate spreadsheet of each person that I’ve identified as a match with an identified ancestor. I know it’s extra work, but that spreadsheet is invaluable for determining if the ancestor is autosomal proven and if the match is a candidate for Y or mtDNA testing.
  • Then I get another cup of coffee and check at MyHeritage for new record matches for that ancestor, along with new DNA SmartMatches.
  • GedMatch and 23andMe aren’t as easy to check for matches specific to ancestors, but I still check both places to see if I can find matches that I can identify as descending from that ancestor.
  • While I’m at it, sometimes I run over to FamilySearch to see if there’s anything new over there, although they don’t deal with DNA. They do, however, have many traditional genealogical records. I may add another column to track if I’m waiting for something specific to be digitized – like court minutes, for example. FamilySearch has been on a digitization binge!
  • As I go along, I add any new discovery to my genealogy software and my Ancestor Birthday Spreadsheet as well.
  • Last, I paint new segment information from Family Tree DNA, MyHeritage, GedMatch or 23andMe at DNAPainter. My three articles about how I use DNAPainter are here, here and here.

I just love ancestor birthdays.

Any day that I get to find something new is a wonderful day indeed – fleshing out the lives, history and DNA of my ancestors. With this many places to look, there’s seldom a day that goes by that I don’t discover at least something in my ancestor scavenger hunt!

Ancestor birthday presents for me😊

_____________________________________________________________________

Standard Disclosure

This standard disclosure appears at the bottom of every article in compliance with the FTC Guidelines.

I provide Personalized DNA Reports for Y and mitochondrial DNA results for people who have tested through Family Tree DNA. I provide Quick Consults for DNA questions for people who have tested with any vendor. I would welcome the opportunity to provide one of these services for you.

Hot links are provided to Family Tree DNA, where appropriate. If you wish to purchase one of their products, and you click through one of the links in an article to Family Tree DNA, or on the sidebar of this blog, I receive a small contribution if you make a purchase. Clicking through the link does not affect the price you pay. This affiliate relationship helps to keep this publication, with more than 900 articles about all aspects of genetic genealogy, free for everyone.

I do not accept sponsorship for this blog, nor do I write paid articles, nor do I accept contributions of any type from any vendor in order to review any product, etc. In fact, I pay a premium price to prevent ads from appearing on this blog.

When reviewing products, in most cases, I pay the same price and order in the same way as any other consumer. If not, I state very clearly in the article any special consideration received. In other words, you are reading my opinions as a long-time consumer and consultant in the genetic genealogy field.

I will never link to a product about which I have reservations or qualms, either about the product or about the company offering the product. I only recommend products that I use myself and bring value to the genetic genealogy community. If you wonder why there aren’t more links, that’s why and that’s my commitment to you.

Thank you for your readership, your ongoing support and for purchasing through the affiliate link if you are interested in making a purchase at Family Tree DNA, or one of the affiliate links below:

Affiliate links are limited to:

Family Tree DNA Group Project Privacy Levels

Recently, Family Tree DNA sent two emails about the new Group Project privacy settings and policies that are now in effect. The first email was to project members, and the second was to administrators.

I’m combining information from both in this article, along with step-by-step instructions for what you need to do, whether you’re a project member or a project administrator.

Before GDPR came into force in May 2018, group project administrators had more latitude to help project members by viewing all fields and being able to change some that weren’t deemed critical to privacy. For example, administrators could add the member’s most distant ancestor, help them with a tree or enter the mapped location of their direct maternal or paternal ancestor. Administrators could not change personal things like name, e-mail, contact information or passwords.

With the arrival of GDPR, Family Tree DNA implemented changes in order to achieve compliance which had the unfortunate effect of restricting administrators’ ability drastically. With the pressure of the GDPR deadline past, Family Tree DNA has rethought some of the restrictions and made welcome modifications.

Who is Affected and What Changed?

Anyone who has tested at Family Tree DNA and is a member of any project is affected, even if you may not realize that you are.

Before we go any further, let’s discuss the privacy settings which fall into basically three categories:

  • very low
  • medium (normal)
  • high

In the chart below, we see the names assigned to the levels as of the GDPR rollout, and now. The names have changed.

The May 2018 names were problematic because some project members became confused, thinking that Project Only was giving full access for this project. Additionally, Full access wasn’t full, but did allow some modifications. Therefore, in an effort to minimize confusion, Family Tree DNA has now renamed the access levels. The () are my descriptions.

The GDPR Transition

In May, the pre-GDPR privacy settings for project members were programmatically converted to the new settings, the result being that many project members were converted over with new settings that were much more restrictive than they were previously. I am still hopeful that this issue will be addressed, because the expectation of individuals who joined projects in the 19 years before GDPR was that the administrators had access to work with their results – and always would have. Many of those individuals have been project members for years and have now passed away, eliminating any possibility of the project administrator obtaining even limited (partial view only) access from the member.

For example, with Minimal access, administrators can’t see either members results or trees. With Limited Access, project administrators can’t see the member’s personal profile or privacy selections, but at least can view their tree and results.

Furthermore, anyone who joined a project after May 25th was joined at the minimal level, requiring the new member to change their settings to Limited, providing the administrators a reasonable level of access. Most people didn’t realize that, and therefore the majority of people who have recently joined projects remain at the minimal level.

New Joins No Longer Default to Minimal

When joining a project, new members are currently given the option of assigning an administrator a level – meaning the minimum privacy level is no longer assigned as a default. This is a HUGE improvement.

Due to the transition as well as the “join” policy between May and August leaving many people with Miminum settings, project administrators may want to contact individuals who currently have the Minimum level and ask them to change their settings.

Moving Forward

What matters currently is that you, or kits you manage, may now be at the MOST restrictive level which was originally called “Project Only” after conversion, but has now been renamed as “Minimal Required.”

From my perspective, if a group member does not want the administrators working with their results, they shouldn’t join the project. The purpose and focus of projects is collaboration.

New Settings and Permissions

The chart below, now shown to people when they join projects, summarizes the various abilities that administrators have under Minimal, Limited and Advanced.

With the most restrictive “Minimal Required” setting, administrators cannot see critical items such as a member’s tree or who they match. Minimal Required is extremely restrictive, which means that administrators can’t group the individual within the project appropriately.

With the original GDPR privacy rollout, many people were automatically converted to what is now “Minimal Required” and are unaware that their privacy selection has been downgraded.

Access Now Granted To Individual Administrators

Another change is that members now grant each individual project administrator a specific and different level of access unique to that administrator.

This change is quite beneficial, because you may want to grant one project administrator Advanced access which allows them to change some fields, while granting the rest Limited.

New Administrators

In this latest update, you can now grant all future project administrators an access level too, creating a legacy for future project administrators to have access to your results at the level you select.

After GDPR, new project administrators were only granted “minimal” access to every project member, meaning that in essence, new administrators were entirely hamstrung if every project member didn’t individually change their access for that administrator.

Needless to say, project members who joined projects before GDPR did not expect this would ever happen. Many have died or become disinterested and that meant that their results would forever be unavailable to new administrators.

Granting at least minimal access to future administrators assures that your DNA within a project will never be dead.

Another change last week was that new administrators are now granted Limited access, unless you specifically select either Minimal or Advanced access for new administrators.

Advanced Versus True Full Access

Advanced access is not the same as full access.

If you want an individual, project administrator or otherwise, to truly have full access to your account, you need to personally give them your kit number and password, realizing that allows them to function entirely “as you.” I have done this, because when I die, I want my DNA legacy to live vibrantly into the future.

Beneficiary

Speaking of legacy, please take this opportunity to complete your beneficiary form so that Family Tree DNA knows who to allow access to your account after your death.

Access Levels

Bottom line – you need to check BOTH your “Privacy and Sharing” setting along with “Project Preferences” for each project that you belong to because your settings may be much more restrictive than you think they are.

Privacy and Sharing

The Privacy and Sharing tab allows your results to be shown in the public project.

You MUST OPT IN to project sharing, or your results won’t be included in the public project display.

Most people don’t realize that the default is to NOT SHOW in a project, believing that if they join a project, their results will automatically be anonymously displayed in the public portion of the project. You must opt-in, so be sure that little box at the right side of the Group Project Profile is checked.

Project Preferences

The Project Preferences tab is where you grant project administrator rights.

Let’s look at the various group project preference privacy levels; Minimal, Limited and Advanced, and what they provide.

Level: Minimal Required

From the Family Tree DNA Learning Center:

Minimal Required is the most limited access level. This access level permits the Group Administrator or co-administrator to access project administration tools that allow him or her to view certain results in relation to how you match other project members; however, this access level does not allow the administrator to visit your myFTDNA pages.

The following table lists the Group Administration Pages and the corresponding group member information viewable by administrators assigned the Minimal Required level:

Minimal Required
Group Administration Report Page* Viewable Information
Profile Information
(viewable by Group Administrators, co-administrators, and other project members in multiple locations)
  • Name
  • Email
Maternal and Paternal Ancestry
  • Maternal and Paternal
    Country of Origin
    (from release form only)
  • Most distant ancestor and location
  • Family tree (if public)
Order Summary
  • Y-STR
  • Big Y-500
  • mtDNA
  • Deep Clade
  • Family Finder
  • Geno 2.0
Pending and Received Lab Results
  • Pending lab results
  • Completed lab results
Received and Unreceived Kits
  • Kit status
FF Illumina OmniExpress Matrix
  • Matrix of in-project members and who they match
FF Illumina OmniExpress Results
  • Comparison and download of in-project matches and their chromosome information
mtDNA Results Classic
  • Haplogroup
  • HVR1/2 mutations
  • Coding region mutations
    (only if authorized)
Y-DNA Genetic Distance
  • Subgroup
Y-DNA TiP Report
  • Genetic distance to other project members
Y-DNA Results
  • Haplogroup
  • STR marker values
Y-DNA Results Classic
  • Haplogroup
  • STR marker values
Y-DNA Results Colorized
  • Haplogroup
  • STR marker values
Y-DNA SNP
  • SNPs
Member Subgrouping
  • SNPs
Activity Feed
  • Postings

*These pages are only accessible by Group Administrators and co-administrators unless otherwise noted.

Level: Limited and Advanced

Limited is the recommended access level. This level of access permits the Group Administrator or co-administrator to visit and view certain information on your myFTDNA pages in order to assist with kit management and to better facilitate project research. Additionally, this access level includes all of the permissions granted with the Minimal Required level.

For more information on the permissions granted with this level, see the below Limited and Advanced Access table.

Advanced access permits the Group Administrator or co-administrator to visit, view, and modify certain information on your myFTDNA pages in order to assist with kit management and better facilitate project research. Additionally, this access level includes all of the permissions granted with the Limited access level.

The Advanced access level is designed to allow an individual administrator to fully manage a project member’s kit and function on their behalf. This includes ordering products and modifying information with the exceptions of the primary email address and project preferences for other Group Projects.

The following table lists your myFTDNA pages and the corresponding limitations and permissions granted to the administrator with the Limited and Advanced access levels.

Note: In addition to the personal information mentioned below, administrators for Group Projects of which you are a member and whom you have assigned Limited or Advanced access and administrators to whom your matches have granted Limited or Advanced access, will be able to view your profile, match information (e.g., Common Matches, Genetic Distances, and Shared Segments) and some Genetic Information (e.g., genetic markers and ethnicity information).

Limited and Advanced
Group Member myFTDNA Page Limited (Recommended)
(read only)
Advanced
(modify capability)
myFamilyTree Yes Yes
Complete Order History Yes Yes
Personal Surveys No Yes
Products and Upgrades
(Ability to purchase tests or upgrades
for group member)
No Yes
Family Finder
Family Finder Raw Data Download No Yes
Family Finder Matches Yes Yes
Download Family Finder Matches Yes Yes
Family Finder Linked Relationship Yes Yes
Family Finder Chromosome Browser Yes Yes
Download Family Finder Chromosome Browser Yes Yes
Family Finder myOrigins Yes Yes
Family Finder Shared Origins Yes Yes
Family Finder ancientOrigins Yes Yes
Family Finder Matrix Yes Yes
Population Finder Survey No Yes
Family Finder Advanced Matches Yes Yes
mtDNA
mtDNA Download Matches Yes Yes
mtDNA View Matches Yes Yes
mtDNA Ancestral Origins Yes Yes
mtDNA Matches Maps Yes Yes
mtDNA Migration Maps Yes Yes
mtDNA Haplogroup Origins Yes Yes
mtDNA Print Certificates No Yes
mtDNA Download FASTA No Yes
mtDNA View Results Yes Yes
mtDNA Advanced Matches Yes Yes
Y-DNA and Big Y-500
Y-DNA Download Matches Yes Yes
Y-DNA View Matches Yes Yes
Y-DNA Ancestral Origins Yes Yes
Y-DNA Haplotree & SNPs Yes Yes
Y-DNA SNPs Download Yes Yes
Y-DNA Matches Maps Yes Yes
Y-DNA Migration Maps Yes Yes
Y-DNA SNP Map Yes Yes
Y-DNA Haplogroup Origins Yes Yes
Y-DNA Print Certificates No Yes
Y-DNA Download Y-STR Results Yes Yes
Y-DNA View Y-STR Results Yes Yes
Y-DNA Advanced Yes Yes
Big Y-500 Results Yes Yes
Big Y-500 Matches Yes Yes
Big Y-500 BAM File Download No Yes
Big Y-500 Download VCF No Yes
Y-DNA Advanced Matches Yes Yes
Other Results
All Factoids Results No Yes
X-STR Yes Yes
Individual Y-STR Yes Yes
Individual Autosomal Markers Yes Yes
Applications
Partner Applications No Yes
Vitagene Wellness No No
Account Settings
Contact Information No Yes (except primary email)
Change Password No Yes (must know the current password to change it)
Beneficiary Information No Yes
Earliest Known Ancestors Yes Yes
Surnames Yes Yes
Privacy & Sharing Yes Yes
Project Preferences Yes Yes*
Notification Preferences Yes Yes
Projects
Join a Project Yes Yes

* An administrator granted Advanced access has the ability to modify permissions for administrators in other projects who have Limited or Minimal Required access; however, they cannot grant Advanced access to or remove Advanced access from any other administrator or co-administrator. Additionally, administrators granted Advanced access by a member can, on the member’s behalf, leave other projects with the exception of those having administrators who also have Advanced access.

Checking Your Settings – Step by Step Instructions

Step 1

Sign on to your account at Family Tree DNA and select the orange “Manage Personal Information,” right under your Profile photo, or the location reserved for the photo.

Then click on the Project Preferences tab:

Click on the Edit function which shows you the current level for each administrator in a specific project, allowing you to select a new level, and then allowing you to pre-select a new level for all new future administrators of this project.

I strongly recommend that you pre-select (at least) the Limited Access level.

Then, click on Accept which shows you a summary of your new selections.

Click “Confirm” and you’re all set.

You’ll need to repeat this step to check administrator rights for all projects that you have joined.

Step 2

Next, click on the privacy and sharing tab to opt in to Project Sharing. You only have to do this one time, but if you don’t – your results will NOT BE INCLUDED in any public projects.

Why is that important?

Public project displays encourage people to participate in DNA testing and join projects, especially Y and mitochondrial. If they see several lines tested, they are much more likely to purchase a test to see if they match a line they think might be theirs. Projects serve as advertising which helps all genealogists.

So please, opt in!

Project Administrators

If you’re a Family Tree DNA project administrator, you’ll need to do the following:

  • Review your Member Information List for members who have the minimal setting AND those who are not publicly sharing their DNA results.

In my Estes project of 327 individuals, 32 converted with Minimal access, including my immediate family members whose kits I manage. I don’t know if this 10% number holds true across all projects, but that’s a nontrivial number of people whose results you can’t access, and who you can’t help.

You’ll need to do the following:

  • Educate your members about why you need either Limited or Full Access as well as why they want to consider allowing their results to be publicly displayed.
  • If as an administrator, you’ve elected to prevent your project from publicly displaying, please consider making your project public. Family Tree DNA does not display the results of any individual in a project who does not opt-in to having their results shown publicly – so you don’t have to worry about that.
  • Using the administrator’s Bulk Email function, send a project e-mail with instructions for how to check and select new Project Preference administrator settings as well as where to find the Project Sharing opt-in. (Feel free to link to this article.)
  • Follow-up by sending individual e-mails to members who don’t change their settings.
  • If you have a number of people in your project who are not grouped, you can group people with “Minimal” access into one group, and send a group e-mail to only them. I think that would be easier than e-mailing everyone individually, but as a project administrator, I’m committed to doing whatever needs to be done to preserve the integrity of my projects.

Getting Help

  • If you run into problems and need help, you can call Family Tree DNA at 713-868-1438 M-F 9-5 CST and select the customer support option or initiate a support request by clicking on help at the very bottom of every page.
  • If you’re a project administrator and run into problems, don’t forget that Family Tree DNA has a Group Support Department to help administrators. You can call the same number and select the option for groups or e-mail groups@ftdna.com.

_____________________________________________________________________

Standard Disclosure

This standard disclosure appears at the bottom of every article in compliance with the FTC Guidelines.

I provide Personalized DNA Reports for Y and mitochondrial DNA results for people who have tested through Family Tree DNA. I provide Quick Consults for DNA questions for people who have tested with any vendor. I would welcome the opportunity to provide one of these services for you.

Hot links are provided to Family Tree DNA, where appropriate. If you wish to purchase one of their products, and you click through one of the links in an article to Family Tree DNA, or on the sidebar of this blog, I receive a small contribution if you make a purchase. Clicking through the link does not affect the price you pay. This affiliate relationship helps to keep this publication, with more than 900 articles about all aspects of genetic genealogy, free for everyone.

I do not accept sponsorship for this blog, nor do I write paid articles, nor do I accept contributions of any type from any vendor in order to review any product, etc. In fact, I pay a premium price to prevent ads from appearing on this blog.

When reviewing products, in most cases, I pay the same price and order in the same way as any other consumer. If not, I state very clearly in the article any special consideration received. In other words, you are reading my opinions as a long-time consumer and consultant in the genetic genealogy field.

I will never link to a product about which I have reservations or qualms, either about the product or about the company offering the product. I only recommend products that I use myself and bring value to the genetic genealogy community. If you wonder why there aren’t more links, that’s why and that’s my commitment to you.

Thank you for your readership, your ongoing support and for purchasing through the affiliate link if you are interested in making a purchase at Family Tree DNA, or one of the affiliate links below:

Affiliate links are limited to:

Family Tree DNA – Summer Sale and Project Changes (Thank Goodness)

In late breaking news, this morning two things happened at Family Tree DNA:

  • The Summer Sale has started with great prices
  • The project defaults are now “Limited Access” when new people join projects

Group Project Changes

I am jumping for joy!!!

Thank you Family Tree DNA for listening to your customers and project administrators!

The project restrictions imposed due to GDPR privacy concerns were strangling administrators’ ability to work with project members and their results. Post-GDPR, when people joined projects, the administrators couldn’t even see who new members matched or their trees, making grouping impossible. I understand the concept behind this restriction, but it also made it impossible, from a project administrator’s position, to work with members.

Furthermore, new administrators will now be granted Limited Access to group participants information as well.

There are still post-GDPR challenges that remain, but for now, this is a HUGE step forward.

The Summer Sale

Everything is on sale – literally everything. New purchases and upgrades too.

Product bundles, already discounted, are now discounted even further during the sale.

The sale ends on August 31st. Now is a great time to buy those kits for your relatives and take them along to family reunions.

Click here to order now!

_____________________________________________________________________

Standard Disclosure

This standard disclosure appears at the bottom of every article in compliance with the FTC Guidelines.

I provide Personalized DNA Reports for Y and mitochondrial DNA results for people who have tested through Family Tree DNA. I provide Quick Consults for DNA questions for people who have tested with any vendor. I would welcome the opportunity to provide one of these services for you.

Hot links are provided to Family Tree DNA, where appropriate. If you wish to purchase one of their products, and you click through one of the links in an article to Family Tree DNA, or on the sidebar of this blog, I receive a small contribution if you make a purchase. Clicking through the link does not affect the price you pay. This affiliate relationship helps to keep this publication, with more than 900 articles about all aspects of genetic genealogy, free for everyone.

I do not accept sponsorship for this blog, nor do I write paid articles, nor do I accept contributions of any type from any vendor in order to review any product, etc. In fact, I pay a premium price to prevent ads from appearing on this blog.

When reviewing products, in most cases, I pay the same price and order in the same way as any other consumer. If not, I state very clearly in the article any special consideration received. In other words, you are reading my opinions as a long-time consumer and consultant in the genetic genealogy field.

I will never link to a product about which I have reservations or qualms, either about the product or about the company offering the product. I only recommend products that I use myself and bring value to the genetic genealogy community. If you wonder why there aren’t more links, that’s why and that’s my commitment to you.

Thank you for your readership, your ongoing support and for purchasing through the affiliate link if you are interested in making a purchase at Family Tree DNA, or one of the affiliate links below:

Affiliate links are limited to:

Project Groupings and How to Get the Most Out of Projects at Family Tree DNA

Family Tree DNA is the only DNA testing company that offers and supports projects – a structure that allows participants to join groups of common interest with the goal of providing information about their ancestors. Family Tree DNA provides a project structure and even a special administrator support group and hotline at Family Tree DNA to assist project administrators with the over 8000 projects that exist today.

Projects do more than just help the members – they have the potential to help others who descend from these same lines. Not to mention that they are a wonderful recuiting tool.

You can see what projects might be available for a surname of interest at this link by typing the surname or topic (like Indian) into the “Search your Surname” box:

For the past several years, World Families Network has hosted some Family Tree DNA projects utilizing a different format, as well as orphan projects, meaning those with no administrator.

With the recent World Families Network announcement that they are retiring as of May 23th and will no longer be hosting projects, several people have been inspired to adopt orphan projects, literally preserving what exists at World Families Network already in place for that project. That’s great news, but what’s next and how does a project administrator manage a project?

Or maybe you’re on the other side of the fence and you’d like to understand why projects are grouped so differently and how to use, or group, them effectively.

This article is written for surname project administrators, but is a learning tool for anyone interested in surnames. Isn’t that all genealogists?

Projects Are Your Surname Billboard

Project pages are your project’s front door, the marketing department, and a great way to put your best foot forward to recruit new members.

I’ve provided some resources for administrators at the end of this article, but before you start the nitty-gritty of how to group project members, I’d like to provide a few thoughts, observations and recommendations for grouping specific types of projects.

No need to roll through the same mud puddles I’ve already stomped in just to discover that they’re cold, wet and dirty.

Project Types

I administer or co-administer a number of projects at Family Tree DNA, such as:

  • Regional projects, such as the Cumberland Gap Y and mitochondrial DNA
  • Family or special interest projects, such as the American Indian project and the Acadian AmerIndian Ancestry project.
  • Haplogroup projects
  • Surname projects
  • Autosomal projects

How projects are grouped varies by the type of project, combined with the project’s specific goal. Not every project falls neatly into one of these categories, but most do.

Let’s take a look at the differences.

Regional Projects

Regional projects often reflect an interest in a particular region of the world. This includes projects based on geographic regions, like the Cumberland Gap projects, or sometimes countries like the French Heritage Project.

Regional projects sometimes show both Y and mitochondrial DNA results, although this is sometimes problematic. Unless the administrator checks to be sure both the Y and mitochondrial lineages belong in that specific project for every member who joins, the member’s results will be shown in both categories if they have taken both tests. For example, a man’s direct paternal line might be from the Cumberland Gap region, but his mother, or mitochondrial line might be from Italy. Clearly both lines don’t belong in this project.

The administrator can individually disable one display or the other (Y or mt) for each project participant – but that requires that the participant communicate with the administrator and frankly, it’s a huge pain. Been there, tried that, didn’t work.

For that very reason, several years ago, I split the Cumberland Gap project into two projects, one being for Y DNA results and one for mitochondrial results. That way, I can simply disable the entire mitochondrial page display for the Cumberland Gap Y DNA project, and disable the Y page display for the Cumberland Gap Mitochondrial DNA project. No need to do something with each person who joins. The member joins the appropriate project for their heritage – Y or mitochondrial DNA, or maybe both.

Deciding how to group a regional project can be challenging. The French Heritage project groups their Y DNA members and mitochondrial by surname and ancestor.

Please click to expand any image.

In this case, the administrator of the French Heritage project has chosen NOT to include the surname column, but instead created a subgroup banner with the surname included – so the surname column was not necessary unless a member is ungrouped.

The Cumberland Gap literally at the intersection of Virginia, Kentucky and Tennessee, was a waystation on the westward migration and the projects were originally intended to help reassemble families whose ancestors migrated through the mountain ranges to new frontiers. Some stayed and settled, but many left behind a family member of two and then moved on. Truthfully, I’m not sure that this project hasn’t outlived its original purpose with the advances in DNA testing since it was established about 15 years ago.

The Cumberland Gap Mitochondrial project results are “ungrouped,” because based on how Family Tree DNA groups Mitochondrial results, similar results and haplogroups appear together – so mitochondrial projects are in essence self-grouping in most instances.

For mitochondrial DNA, the current surname is largely irrelevant because women’s surnames tend to change with every generation, unlike patrilineal surnames which are relevant to Y DNA results.

The administrators also maintain a separate Yahoo group to exchange genealogical, regional and cultural information.

If you are administering a Y haplogroup only project, disable the mitochondrial page display, and vice versa.

World Families Network didn’t host regional, special interest or haplogroup projects, so these projects aren’t as likely to be orphaned as surname projects.

Special Interest Projects

Special interest projects are focused specifically on one type or group of people. Grouping varies widely depending on the project type. I co-administer both the American Indian project and the Acadian Amerindian Ancestry projects, and they are grouped differently.

The American Indian project is grouped according to haplogroup, since specific haplogroups are known to be Native; subsets of C and Q for Y DNA and subsets of A, B, C, D, X and possibly M for mitochondrial DNA.

Note that we show the surname and the “Paternal Ancestor Name” columns, both, because the surname and the paternal ancestor’s name may not be the same for a variety of reasons.

The Acadian AmerIndian Ancestry project includes both Y and mitochondrial DNA of our Acadian ancestors. Acadians were a mixture of French, a few English soldiers, and Mi’kmaq Indians. The Acadian AmerIndian Y DNA project is grouped both by haplogroup and by surname.

Some surnames, such as Doucet, have both a Native lineage (C-P39) and a European lineage (R-M269), so their separate lineages are shown grouped with their respective haplogroups.

If members were grouped primarily by surname, then both lineages would have been shown adjacent to each other under the Doucet surname.

There is no one right way to group projects.

In this project, as well as others, I sometimes wish we had implemented the “apply to join” methodology, because I suspect that some people (in the ungrouped section) have joined in error.

Some ungrouped people have joined because their lineage is Acadian, but not their direct Y or mitochondrial lines.

The administrators chose to embrace the open join policy, even though it’s more difficult and time-consuming to administer, because we want to be inclusive and help everyone with either Acadian or AmerIndian ancestors from France, Eastern Canada and the Acadian diaspora regions connect with their ancestors. Acadians were admixed in Canada for 150 years, then dispersed to the winds in 1755 when they were forcibly evicted from Nova Scotia, so we find their roughly 2 million descendants in many parts of the world today.

Haplogroup Projects

By comparison, haplogroup projects are easier to group, because their focus is clear. Haplogroup projects, be they Y or mitochondrial are focused on that haplogroup and it’s sub-haplogroups.

The Haplogroup C-P39 project is a relatively small Native American project, so it’s grouped by surname and matching group within that haplogroup.

Another popular way to group larger haplogroup projects is by haplogroup subgroups for both Y and mitochondrial DNA. The popular R-L21 and Subclades project where my Estes men are members, but I don’t administer, is grouped in this manner.

One of the great features of all projects at Family Tree DNA is mapping. Based on how the administrator subdivides the project, if they enable project mapping (please do), you can select groups to display to view subgroup clusters.

I just love this feature. You know there’s a story behind this grouping that is relevant to the men who carry this haplogroup.

The A2 mtDNA Haplogroup project is grouped by subgroup. Some administrators go further and group by specific mutations within subgroup as well, hoping they will someday form a new subclade.

Maps provide so much information. In this case, the map of the A2 group, with no A2+ (downstream) subgroups shows a dispersal throughout the Americas, plus one person in Denmark.

Wait, what?

Denmark?

Of course, Denmark immediately raises a plethora of questions including whether the Denmark person has taken the full sequence test or has perhaps misidentified their ancestor’s original location.

Some people don’t understand that the matrilineal line is your direct mother’s mother’s mother’s line on up until you run out of direct line mothers. They hear or understand maternal instead and select their most distant MATERNAL ancestor which may be anyone from their mother’s side of the tree – and someone entirely different than their direct line MATRILINEAL ancestor.

Surname Projects

Surname projects play a different role than the projects mentioned above. Specifically, surname projects not only attract males with that surname who are candidates to test, they also attract anyone who has that surname in their genealogy who is looking to see if someone from their line has tested – because they can’t.

All of us have a lot more surnames that aren’t our direct paternal surname, which only males can test via Y DNA.

In the graphic above, the surname lineage is blue, the mitochondrial is red, and the colorless boxes represent all of our other lines.

Therefore, most people are looking at a surname project to find lineages they can’t directly test for. Surname projects need to make it easy to find and locate lineages based on ancestors and location.

I don’t know how many surname projects exist, as opposed to other project types, but I’d say surname projects outnumber the other types of projects significantly – meaning there is a huge potential to find your surnames and ancestors in those projects.

I love surname projects, because even if you are a female or a male that doesn’t carry that surname today, you can still benefit from the tests of people with that surname.

In the Estes project, which was formed for Y DNA, we also welcome autosomal joiners as long as they have Estes lineage someplace in their tree.

In the project, I group Estes men by lineage from the immigrant Estes ancestor.

In order to do this, I utilized the descendants of Abraham Estes to recreate his haplotype, and I compare everyone to those values, which represent the values that Abraham himself carried.

The good news is that by looking at the matches of each person in the project, you know who does and does not match each other. Family Tree DNA tells you that. They do the hard lifting and you arrange the furniture.

I didn’t know quite what to do with people whose genealogy and surname go back to Abraham Estes, or one of his cousins who all descend from the Deal, England line – but their Y DNA unquestionably doesn’t.

I created a “New Estes Line – Genetically Speaking” category. We can’t say that these people “aren’t Estes” because their mother may have been an Estes and gave her male child her surname, just not her Y DNA (which she doesn’t have,) of course. That was contributed by the father. So the surname is Estes, but the Y DNA doesn’t match any of the Estes descendants of the Deal line. However, these people may match Estes descendants autosomally.

There is also an “Estes Ungrouped” group, because even though their Y DNA is clearly Estes, I can’t connect these men back to a specific line yet either through paper or DNA.

Assigning a member to the “Estes Ungrouped” group is different than leaving them in the default “ungrouped” catchall group provided by Family Tree DNA which is located at the bottom of the page. The default ungrouped group is where everyone lives until the administrator assigns them to a group.

Autosomal Joiners

There’s been recent discussion about why administrators would want to allow people to join Y DNA surname projects who’ve tested autosomally and descend from the surname line, but aren’t males who carry the surname.

I am very much IN FAVOR of allowing autosomal joiners. Some other administrators, not so much. Someone recently said that they don’t understand why anyone who is not a male with the same surname as the project would want to join – what benefit there could possibly be. As a female Estes, I can explain exactly why, in one simple graphic. OK, 3 graphics.

On your personal account myFTDNA tab, there’s an Advanced Setting under “Tools and Apps.” Click there.

Then select the Family Finder test, then “yes” to “Show only people I match in all selected tests,” then select the project. The project selected (Estes in this example) must be one you have joined – that’s why it’s important to allow people from that lineage that don’t carry the Y chromosome to join.

Want to guess how many people I match, meaning Estes males AND all other Estes descendants who have joined the project? Click on the orange “Run Report” to see.

The answer is 23 people, although I’ve truncated the graphic. Some are cousins that I tested, but a dozen aren’t AND there are a few that I’ve never heard of before. Hello cousins! Does anyone have the family Bible or know where it is???

Clearly, I could match some of these people through other lines, BUT, now I know where to start looking. Using the advanced tools like Paternal Phasing (bucketing), the In Common With (ICW) tool and the Matrix, available to everyone, will quickly tell me how I match these people. You can read about how to utilize these tools here.

Project administrators have an even more powerful matrix tool at their disposal.

This is exactly why I’ve elected to welcome autosomal testers into my Y DNA surname projects. The power of DNA is not just in a single set of results, but in collaboration and combined tools.

Autosomal Projects

Autosomal projects, typically referred to as “private family projects” do exist, but you can’t see them when you search by surname because they don’t show up in searches, according to the Family Tree DNA policy.

I hope this policy changes in the near future, allowing the option of searching for autosomal-only projects. Admittedly, autosomal projects are challenging without any results to “show” in a display.

Therefore, in an autosomal project today, in order to group people, you must allow either the Y or mtDNA to “show” because members can’t be grouped otherwise, and even then, they must be grouped on two independent pages – Y and mitochondrial.

The current project structure does not support creating an autosomal group, perhaps by ancestor, and allowing project members’ ancestor from the Estes line to show, for example, given that it’s not the direct Y or mitochondrial DNA line.

For that reason, autosomal projects are private, but I would like for the administrator to be able to select public or private for autosomal projects and to have a separate autosomal tab in the administrator’s toolbox where all members can be grouped according to autosomal lines, independent of and in addition to Y or mitochondrial DNA if relevant.

This would also allow the creation of “ancestor projects,” meaning everyone descended from Robert Eastye (that becomes Eastes and Estes) born 1555 in Deal or Ringwould, Kent, England. Thinking ahead, we could then proceed to recreate his autosomal DNA from project members, just like we recreated Abraham Estes’s Y STR haplotype.

Here’s an example of how autosomal results could be grouped, without showing any additional results information, in projects. I’ll be submitting this as a request to Family Tree DNA!

This autosomal grouping challenge is present as well for Y DNA surname projects that allow autosomal joiners.

Some Grouping Don’ts, With a Dash of Humor

One of the things I do roughly yearly is to peruse the public projects to see if any of my ancestral lines are represented or their haplogroup has been expanded. I recently finished this activity once again, so, here are a few of the frustrations I encountered that are entirely avoidable.

  • Please Don’t Make Projects Private

There is nothing more discouraging than seeing this:

Projects are a wonderful way to recruit new members and if the project is private, you’ve disabled your best recruiting tool.

I’m not feeling warm and fuzzy about this project, and that’s no joke. The first thing this project administrator did was to hang a big “Go Away” sign out for me to see. Ok, I’m going! No need to ask twice!

Individuals select for their results to “show” or “not show” publicly in projects. You don’t have to do this for them. Really.

So please, be inclusive and roll out the red carpet!

  • Please Don’t Group Surname Projects by Haplogroup Only

Please don’t group surname projects by haplogroup, at least not if you have any other choice. Let’s call this the last choice or desperation grouping methodology.

Remember, the most common reason people are looking at the project is to be able to find their ancestors, or ancestral group, which may be predicated on location. No one, but no one, already knows the surname haplogroup or they wouldn’t be searching for their ancestors in this way.

Family Tree DNA automatically groups by marker/color within subgroup, but if you’re trying to see if your ancestor or line is represented in a project, it’s almost impossible to find using the “group by haplogroup” methodology – especially with small subgroups. Y haplogroups can vary in their naming, depending on how deeply people have tested. For example, haplogroup R has thousands of branches. Some administrators group at the highest haplogroup level, and some group by the smallest branch level, which separate groups of men in the same family line – because not everyone has tested to the same level.

Of course, if you really don’t know how these men connect, or don’t have any idea about who descends from which ancestor, haplogrouping at the base haplogroup level (like R or J) may be the best you can do. Family Tree DNA will attempt to automatically group within your haplogroup subgroups.

If this is the case, you might want to attempt to recruit a genealogist with some specialty in this surname as a co-administrator. Hey, maybe someone from within that surname project!

  • Please Don’t Group by Number of Markers Tested

OMG, please no. Just no.

Grouping by number of markers tested makes it impossible to find line marker mutations that should be grouped together. For example, the men with a value of 13 at marker DYS439, above, should be displayed together because that is likely a line marker mutation – signifying descent from a specific descendant line of Charles Dodson in the red rows. However, since participant results are grouped by the number of markers tested, these men are displayed in different groups.

To figure out which ancestral line that value of 13 descends from, you need a subscription to the Physic Friends Network.

  • Please, PLEASE, Don’t Show Only Surnames and not “Paternal Ancestor Name”

How on earth would I ever know if my Luttrell or Littrell line is represented here. And why would an administrator choose to NOT INCLUDE the Paternal Ancestor Column?

This one makes me just want to pull my hair out. Yes, seriously! Going bald.

  • Please, Name the Line

Give the lineage a name or description, not just “Lineage 1.” It helps researchers determine if THAT John Jones is THEIR John Jones and it helps a lot to know who John Jones married, and when, if you know.

For example, for Lineage 1, put as much information as you can discover, or at least enough to unquestionably identify the line. For example, “John Doe born 1612 Sussex, England died 1683 Tukesbury, MA m Jane Smith.”

This helps identify specific lines. This is not Wheel of Fortune for ancestors. Don’t make me guess, because I may guess incorrectly – and there is no need for that when the information is (could be, might be, please let it be) readily available.

Another hint is to use color effectively. Perhaps lines that have different known progenitors but still match genetically having the same surname, meaning the earliest common ancestor has not yet been identified, could be the same color.

Think this through ahead of time and come up with a naming and color scheme that works well for your project circumstances and goals.

Sometimes after you’ve worked with a project for some time, you realize that perhaps things could be organized better. Been there, done that – no t-shirt. Just re-do it.

  • Or Worse Yet…

No surname AND no ancestor AND the lines aren’t named. Yes, really. This project might as well be called “why bother” or “shoot me now.”

You can’t even tell which surname this project might be, let alone identify an ancestral line.

You know that old saying about serving as a bad example? Well, this is it!

  • A Good Example

And because I don’t want to leave on a negative note – a really good example of a surname project.

You can tell that this administrator has spent a significant amount of time working on this project – and also encouraging members to enter their most distant ancestor information which is extremely useful.

Now this project looks inviting and welcoming. And no, in case you were wondering, I do not administer this project, but since imitation is the sincerest form of flattery, I’m going to review my own surname projects with this one in mind.

Great job Hill project administrator(s).

Resources

Maurice Gleeson has produced two wonderful YouTube videos about project administration and in particular, member grouping.

How to Group your Project Members using MPRs (by the way, an MPR is a “marker of potential relatedness,” according to Maurice.

https://www.youtube.com/watch?v=A9JcvbFcgUI

How Y-DNA can help your One Name Study

https://www.youtube.com/watch?v=vOx971zy6LI&t=3s

In addition, Family Tree DNA just updated the Quick Start Guide for administrators which walks you through setting up a project. https://www.familytreedna.com/learn/project-administration/quick-start-guide/.

Now, enjoy Maurice’s videos and create the most friendly welcome mat possible.

_____________________________________________________________________

Standard Disclosure

This standard disclosure appears at the bottom of every article in compliance with the FTC Guidelines.

Hot links are provided to Family Tree DNA, where appropriate. If you wish to purchase one of their products, and you click through one of the links in an article to Family Tree DNA, or on the sidebar of this blog, I receive a small contribution if you make a purchase. Clicking through the link does not affect the price you pay. This affiliate relationship helps to keep this publication, with more than 900 articles about all aspects of genetic genealogy, free for everyone.

I do not accept sponsorship for this blog, nor do I write paid articles, nor do I accept contributions of any type from any vendor in order to review any product, etc. In fact, I pay a premium price to prevent ads from appearing on this blog.

When reviewing products, in most cases, I pay the same price and order in the same way as any other consumer. If not, I state very clearly in the article any special consideration received. In other words, you are reading my opinions as a long-time consumer and consultant in the genetic genealogy field.

I will never link to a product about which I have reservations or qualms, either about the product or about the company offering the product. I only recommend products that I use myself and bring value to the genetic genealogy community. If you wonder why there aren’t more links, that’s why and that’s my commitment to you.

Thank you for your readership, your ongoing support and for purchasing through the affiliate link if you are interested in making a purchase at Family Tree DNA, or one of the affiliate links below:

Affiliate links are limited to:

World Families Network, Ysearch and Mitosearch Bite the Dust – Thanks So Much GDPR

It’s a sad month.

The core foundation of genetic genealogy is sharing.

GDPR is NOT about sharing easily, and the GDPR hoops are onerous, to be charitable. I wrote about GDPR in the articles GDPR – It’s a Train and It’s a Comin’ and Common Sense and GDPR.

One might say GDPR is at cross purposes with genealogy. It probably wasn’t intended that way, but so far, we’ve lost several resources due to GDPR, and it’s still not here yet.

Add to the death list World Families Network, Ysearch and Mitosearch.

The cost of GDPR compliance, necessary attorney fees along with with the risk of the horrific fines of up to 4 million Euro is just too much for a small business or a non-profit. Additionally, non-EU businesses are required to retain a European Representative company that agrees to absorb some level of the risk for non-compliance. Try finding a company to do that. Not to mention the pain-in-the-butt-factor of the hoops that they would have to jump through if so much as one person complained. Bottom line – not worth it.

Thanks so much GDPR.

World Families Network

Terry Barton, founder of World Families Network, a Y DNA project management company that consists primarily of Terry and his wife, sent an e-mail to the administrators of the projects they host saying that WFN is retiring and shutting down on May 23rd, two days before the GDPR date.

Here’s part of the e-mail to WFN administrators from Terry:

We will delete the project sections of the WorldFamilies site on May 23, 2018, so please copy any information that you wish to save. You may wish to make a copy of your Home, Results, Patriarch, Discussion or other project pages. We can provide an empty excel spread sheet with columns preset to copy/paste your results page on request. For the other pages, you may want to copy/paste your info into a Word document. (Note: we won’t be able to “rescue” you if you miss the deadline, so please don’t wait too long.)

The projects hosted at World Families Network (WFN) will revert to their project pages at Family Tree DNA, so all is not lost, BUT, the information on the Patriarch’s pages as well as some of the information on the actual DNA results pages at WFN does not come directly from Family Tree DNA. Some WFN sites are not fed from the Family Tree DNA project pages at all, so fields like “Earliest Ancestor” at WFN may be blank at Family Tree DNA. That, of course, can be remedied, but won’t happen automatically.

Many of the projects managed by WFN were abandoned, meaning they have no administrator. Some have administrators that preferred the WFN format to the Family Tree DNA format. One of the most popular features was the Patriarchs page where lineages of men with the project surname were listed. This feature was put in place before trees were available at Family Tree DNA – but the Patriarchs format serves as a one-glance resource and can be connected to the kit numbers on the DNA pages.

Please, please, please do two things:

  • Visit the WFN surname links here for projects and scan the projects shown with “project site,” meaning they are WFN hosted, to see if any include your ancestral surnames. If SO, visit that WFN project site by clicking the link and record any information relevant to your family.

  • Consider adopting projects relevant to your surname. Most of these projects will need to be spruced up at Family Tree DNA, meaning they will need to be grouped and the Patriarch’s page will need to be copied onto one of the several available project pages at Family Tree DNA. Many of these projects are small and you can easily preserve information. Terry provides a list of orphaned projects here, but I don’t know if it’s current. I would reach out to Family Tree DNA at groups@familytreedna.com about any project listed as having a project site at WFN. Some projects have an administrator listed, but they are no longer active.

For project administrators considering a private website, be aware per the GDPR requirements that you will constantly have to monitor the privacy settings at Family Tree DNA and assure that you are not displaying information for anyone who has selected, or changed their project setting from public to “project only.” Family Tree DNA automatically removes the project members data from a public display when they change settings or leave projects.

Ysearch and Mitosearch

On May 10th, on their Forum, a Family Tree DNA representative announced that Ysearch and Mitosearch will be shut down by month end. These databases were established in 2003 by Family Tree DNA for free, open sharing.

While this announcement doesn’t state that it’s because of GDPR, that correlation probably isn’t coincidence.

These two data bases have been on life support for some time now. They have been less immediately useful since other testing companies stopped Y and mitochondrial DNA testing, meaning that you could see all of your new matches at Family Tree DNA.

One of their biggest benefits, even for Family Tree DNA customers, was that these were the two databases where everyone could compare actual marker values, not just see if they matched and genetic distance.

Unfortunately, Ysearch and Mitosearch were the only locations left for people who uploaded from those now-defunct databases. Of the 219,410 records in the Ysearch database, 25,521 are from sources other than Family Tree DNA.

Originally, there were four public databases. The other two have been gone for some time, with these being the last two resources to go. This is truly a tragedy for the genetic genealogy community, because unlike the WFN departure where the projects are still available at Family Tree DNA – there is no alternative resource to Ysearch and Mitosearch. Gone is gone – especially for the 25,000+ results archived there from companies that are also gone meaning Relative Genetics, Oxford Ancestors, Ancestry’s now defunct Y DNA, Sorenson and others.

Recently, Family Tree DNA fixed the captcha issue, but the sites are still not fully functional. I tried to retrieve information by searching by surname at Ysearch, and the search failed with an error. I don’t know if the problem now is the actual data base or the fact that the site is overwhelmed by people trying to do exactly what I was trying to do.

As someone in the Family Tree DNA forum thread said:
GDPR: The gift from Europe that just keeps on giving.

Thank You

As sad as I am to see both of these resources go, I want to publicly thank Terry and Marilyn Barton for their 14 years of service to the genetic genealogy community and wish them well in their retirement. Hopefully they will have time to solve their own genealogy mysteries now.

I also want to thank Family Tree DNA for establishing both Ysearch and Mitosearch, and maintaining these sites as long as they have. Few companies would have established a platform for their customers to compare results with their competitors’ products which speaks to their early and ongoing commitment to genealogy.

_____________________________________________________________________

Standard Disclosure

This standard disclosure appears at the bottom of every article in compliance with the FTC Guidelines.

Hot links are provided to Family Tree DNA, where appropriate. If you wish to purchase one of their products, and you click through one of the links in an article to Family Tree DNA, or on the sidebar of this blog, I receive a small contribution if you make a purchase. Clicking through the link does not affect the price you pay. This affiliate relationship helps to keep this publication, with more than 900 articles about all aspects of genetic genealogy, free for everyone.

I do not accept sponsorship for this blog, nor do I write paid articles, nor do I accept contributions of any type from any vendor in order to review any product, etc. In fact, I pay a premium price to prevent ads from appearing on this blog.

When reviewing products, in most cases, I pay the same price and order in the same way as any other consumer. If not, I state very clearly in the article any special consideration received. In other words, you are reading my opinions as a long-time consumer and consultant in the genetic genealogy field.

I will never link to a product about which I have reservations or qualms, either about the product or about the company offering the product. I only recommend products that I use myself and bring value to the genetic genealogy community. If you wonder why there aren’t more links, that’s why and that’s my commitment to you.

Thank you for your readership, your ongoing support and for purchasing through the affiliate link if you are interested in making a purchase at Family Tree DNA, or one of the affiliate links below:

Affiliate links are limited to:

2018 Resolution – Unveiling Hidden Evidence

I spent New Year’s Eve, doing what I’ve done for years on New Year’s Eve – celebrating by researching. In fact, it was at the stroke of midnight in 2005 that I ordered kit number 50,000 from Family Tree DNA.  Yes, I’m just that geeky and yes, I had to purchase several kits in a row to get number 50,000.

That kit went on to help immensely, as I used it to test an elderly cousin of my great-grandmother’s generation who took both the Y DNA test, and then, eventually, autosomal.

This year I made a wonderful discovery to mark the new year.  But first, let’s see how I did with last year’s resolution.

Last Year’s Resolution

Last year, I made 1 resolution. Just one – to complete another year’s worth of 52 Ancestor stories.

Now, that didn’t mean I had to do 52 in total.  It meant I had to be committed to this project throughout the year.  You know, unlike cleaning out that closet…or losing weight…or exercising more. Commitments that are abandoned almost as soon as they are made.

So, how did I do?

I published 37 stories.  I shudder to think how many words or even pages that was.  I’m ashamed to say that I plucked much of the “low hanging fruit” early on, so these were tough ancestors for an entire variety of reasons.

That’s not one article each week, but at least I’m making steady progress. And I must say that I couldn’t do it without a raft of helpers – all of whom I’m exceedingly grateful to.  Friends, professionals, cousins, DNA testers, blog subscribers and commenters – an unbelievable array of very kind souls who are willing to give of their time and share their results. Thank you each and every one!

Now, I’m thrilled to tell you that Amy Johnson Crow has revitalized the 52 Ancestor’s project.  It’s free and you can sign up here.  There’s no obligation, but Amy provides suggestions and a “gathering place” of sorts. Think of her as your genealogy cheerleader or coach. It’s so much easier with friends and teammates! I miss reading other people’s stories, but I won’t have to miss that much longer!

Randy Seaver (of Genea-Musings) and I will have company once again.  He’s the only other person that I’m aware of that has continued the 52 Ancestors project – and he has put me way to shame.  I do believe he published number 286 this week.  I keep hoping that some of his ancestors and some of mine are the same so I can piggyback on Randy’s research! I need an index! Randy, are you listening?

You might wonder why I enjoy this self-imposed deadline ancestor-writing so much.

It’s really quite simple.  It’s an incredible way to organize and sort through all of your accumulated research “stuff.”  I cherish the end product – documenting my ancestors lives with dates, compassion and history.  BUT, I absolutely hate parts of the research process – and the deadline (of sorts) gets me through those knotholes.

I absolutely love the DNA, and I really, REALLY like the feeling of breaking through brick walls.  It’s like I’m vindicating my ancestors and saving them from the eternal cutting room floor. DNA is an incredible tool to do just that and there are very few ancestors that I can’t learn something from their DNA, one way or another – Y, mtDNA,  autosomal and sometimes, all three.  And yes, DNA is in every one of my articles, one way or another. I want everyone to learn how to utilize DNA in the stories of their ancestor’s lives.  In many cases the DNA of theirs that we (and our cousins) carry is the only tangible thing left of them. We are wakling historical museums of our ancestral lines!

How Did You Do?

Not to bring up an awkward subject, but if you recall, I asked you if you had any genealogy resolutions for 2017?  How did you do?

Congratulations if you succeeded or made progress.

It’s OK if you didn’t quite make it. Don’t sweat last year.  It’s over and 2018 is a brand spanking new year.

New Year Equals New Opportunities

2018 is stacking up to be a wonderful year. There are already new matches arriving daily due to the Black Friday sales and that’s only going to get better in the next month or two.  Of course, that’s something wonderful to look forward to in the dead of winter.  We’ll just call this my own personal form of hibernating. Could I really get away with not leaving my house for an entire month? Hmmm….

I want to give you three ideas for having some quick wins that will help you feel really great about your genealogy this year.

Idea 1 – Finding Hidden Mitochondrial DNA

This happened to me just last night and distracted me so badly that I actually was late to wish everyone a Happy New Year.  Yes, seriously.  One of my friends told me this is the best excuse ever!

I was working on making a combined tree for the descendants of an ancestor who have tested and I suddenly noticed that one of the female autosomal matches descended from the female of the ancestral couple through all females – which means my match carries my ancestor’s mitochondrial DNA!

Woohooooooo – it’s a wonderful day.

Better yet, my match tested at Family Tree DNA AND had already taken the mitochondrial DNA test.

Within about 60 seconds of noticing her pattern of descent, I had the haplogroup of our common ancestor. That’s the BEST New Year’s gift EVER.  I couldn’t sleep last night.

So, know what I did instead of sleeping? I bet you can guess!

Yes indeed, I started searching through my matches at Family Tree DNA for other people descended from female ancestors whose mtDNA I don’t have!

So, my first challenge to you is to do the same.

Utilizing Family Finder, enter the surname you’re searching for into the search box in the upper right hand corner of your matches page.

That search will produce individuals who have that surname included in their list of ancestral surnames or who carry that surname themselves.

Your tree feeds the ancestral surname list with all of the surnames in your tree.  I understand this will be changing in the future to reflect only your direct line ancestral surnames.

Some people include locations with their surnames – so you may recognize your line that way. Click on your match’s surname list (at far right) to show their entire list of surnames in a popup box. Some lists are very long.  I selected the example below because it’s short.

Your common surnames are bolded and float to the top.  The name you are searching for will be blue, so it’s easy to see, especially in long lists of surnames. 

About half of my matches at Family Tree DNA have trees.  Click on the pedigree icon and then search for your surname of interest in your match’s tree.

Hey, there’s our common ancestral couple – William George Estes and Ollie Bolton!!!

Idea 2 – Finding Hidden Y DNA

Now that I’ve shown you how to find hidden mitochondrial DNA, finding hidden Y DNA is easy.  Right?

You know what to do.

I this case, you’ll be looking for a male candidate who carries the surname of the line you are seeking, which is very easy to spot on the match list.

Now, word of warning.

As bizarre as this sounds, not all men who carry that surname and match autosomally are from the same genetic surname line.

As I was working with building a community tree for my matches last night, I was excited to see that one of my cousins (whose kit I manage) matches a man with the Herrell surname.

I quickly clicked on the match’s tree to see which Herrell male the match descends from, only to discover that he didn’t descend from my Herrell line.

Whoa – you’re saying – hold on, because maybe my line is misidentified.  And I’d agree with you – except in this case, I have the Y DNA signature of both lines – because at one time I thought they were one and the same. You can view the Herrell Y DNA project here.  My family line is Harrold Line 7.

Sure enough, through the Family Finder match, I checked my Harrell match’s profile and his haplogroup is NOT the same as my Herrell haplogroup (I-P37.)

I could have easily been led astray by the same surname. I really don’t need to know any more about his Y DNA at this point, because the completely different haplogroup is enough to rule out a common paternal line.

Don’t let yourself get so excited that you forget to be a skeptical genealogist😊

My second challenge to you is to hunt for hidden Y DNA.

You can  increase your chances of finding your particular lineage by visiting the relevant Y DNA projects for your surname.

Click on Projects, then “Join a project,” then search for the DNA project that you’re interested in viewing and click on that link.

Within the project, look for oldest ancestors that are your ancestors, or potentially from a common location.  It’s someplace to start.

You can read more about how to construct a DNA pedigree chart in the article, “The DNA Pedigree Chart – Mining for Ancestors.”

Idea 3 – Pick A Puzzle Piece

Sometimes we get overwhelmed with the magnitude and size of the genealogy puzzle we’d like to solve. Then, we don’t solve anything.

This is exactly WHY I like the 52 Ancestor stories.  They make me focus on JUST ONE ancestor at a time.

So, for 2018, pick one genealogy puzzle you’d really like to solve. One person or one thing.  Not an entire line.

Write down your goal.

“I’d like to figure out whether John Doe was the son of William Doe or his son, Alexander Doe.”

Now admittedly, this is a tough one, because right off the bat, Y DNA isn’t going to help you unless you’re incredibly lucky and there is a mutation between Alexander Doe and his father, William.  If indeed that was the case, and you can prove it by the DNA of two of Alexander’s sons who carry the mutation, compared to the DNA of one of William’s other sons who does not, then you may be cooking with gas, presuming you can find a male Doe descended from John to test as well.

This is the type of thought process you’ll need to step through when considering all of the various options for how to prove, or disprove, a particular theory.

Make a list of the different kinds of evidence, both paper trail and genetic, that you could use to shed light on the problem. Your answer may not come from one piece of evidence alone, but a combination of several.

Evidence Available/Source Result
William’s will No, burned courthouse Verified
Alexander’s will No, burned courthouse Verified
Deeds with William as conveyor No, burned courthouse Verified
Family Bible Nope, no Bible
Deeds with Alexander as conveyor, naming John Possible, some deed books escaped fire Check through county, Family search does not list
Deeds with John as conveyor Yes, check to see if they indicate the source of John’s land John is listed in index, need to obtain original deeds from county
Y DNA of John’s line Yes, has been tested Matches DNA of William’s line as proven through William’s two brothers
Y DNA of Alexander Not tested (to the best of my knowledge), find descendant to see if they will test Search vendor DNA testing sites for male with this surname to see if they have/will Y DNA test
Closeness (in total cM and longest segment) of individuals autosomal matching through any of William’s descendants Mine both Ancestry and FTDNA for surname and ancestor matches This step may produce compelling or suggestive evidence, and it may not.  Make a McGuire chart of results.
Does John match any relatives of the wife of Alexander Doe? Search FTDNA and Ancestry for matches.  Triangulate to determine if match is valid and through that line. This is one of the best approaches to solve this type of problem when paper records aren’t available. Fingers crossed that Alexander and his wife and not related.

You can add pieces of evidence to your list as you think of them.

Making a list gives you something to work towards.

Your Turn!

Select one thing that you’d like to accomplish and either set about to do it, like mining for mitochondrial or Y DNA evidence, or put together a plan to gather evidence, both traditional and genetic.

In the comments, share what it is you’ll be searching for or working on.  You just never know if another subscriber may hold the answer you seek.

I can’t wait to hear what you’ll be doing this year!

Have a wonderful and productive New Year searching for those hidden ancestors!

_____________________________________________________________________

Standard Disclosure

This standard disclosure appears at the bottom of every article in compliance with the FTC Guidelines.

Hot links are provided to Family Tree DNA, where appropriate.  If you wish to purchase one of their products, and you click through one of the links in an article to Family Tree DNA, or on the sidebar of this blog, I receive a small contribution if you make a purchase.  Clicking through the link does not affect the price you pay.  This affiliate relationship helps to keep this publication, with more than 900 articles about all aspects of genetic genealogy, free for everyone.

I do not accept sponsorship for this blog, nor do I write paid articles, nor do I accept contributions of any type from any vendor in order to review any product, etc.  In fact, I pay a premium price to prevent ads from appearing on this blog.

When reviewing products, in most cases, I pay the same price and order in the same way as any other consumer. If not, I state very clearly in the article any special consideration received.  In other words, you are reading my opinions as a long-time consumer and consultant in the genetic genealogy field.

I will never link to a product about which I have reservations or qualms, either about the product or about the company offering the product.  I only recommend products that I use myself and bring value to the genetic genealogy community.  If you wonder why there aren’t more links, that’s why and that’s my commitment to you.

Thank you for your readership, your ongoing support and for purchasing through the affiliate link if you are interested in making a purchase at Family Tree DNA, or one of the affiliate links below:

Affiliate links are limited to: