Tenth Annual Family Tree DNA Conference Day 3

The internet in the hotel hasn’t gotten any faster, so I’ll just be providing highlights and today’s new announcements.  More info, plus pictures, when I get home.

Sunday always begins with the ISOGG meeting hosted by Director, Katherine Borges.

This year’s meeting was especially touching, because Max Blankfeld and Bennett Greenspan, founders of Family Tree DNA, received plaques for their 10 years of investment and dedication and as a thank you for hosting the conferences for administrators.

DSC_0016

Much of today’s agenda was focused on research, technical updates and new products and features.

This next year, Family Tree DNA’s focus is on three initiatives:

  1. Customer service and feedback
  2. Features – listen to citizen scientists and group administrators
  3. New products and features to make genetic genealogy better for genealogists

Family Tree DNA is actively soliciting your feedback and has set up a special address for suggestions.  This takes you to a google docs file where you enter your name, e-mail and 1000 characters maximum.

http://www.familytreedna.com/suggestions

Free Ancestry and 23andMe Uploads

In order to attract more uploads, which will, of course, give us more matches, Family Tree DNA is announcing free uploads from Ancestry and 23andMe, the v3 chip only, but with a string attached.  The transferee can do the actual transfer for free, but they will only see their top 20 matches, only an initial and a last name, and will not be able to communicate with them unless they decide to pay $39 to join, or perhaps stated more accurately, to active all of the features of a paid transfer.  However, in lieu of the $39 fee, you can also recruit 4 other people to upload their data, whether or not they actually pay the fee or not.

Search Feature

One of the reasons Family Tree DNA implemented the new trees was so that they could implement new search functionality.  Soon, one will be able to search all public trees.  I think this will benefit the community immensely, because it will allow people to see if people from their family lines are present in the data base, which will, hopefully, encourage testing.

Facilitating Communication

DSC_0116

A new social media function called myGroups is being implemented to facilitate contact within groups.  Today, projects and outside mailing lists and groups don’t fully overlap.

The example shown correlated to about 25% of a project group that was subscribed to an outside Yahoo group for discussion.  MyGroups is designed to facilitate discussions that include all project members.

Furthermore, Ancestry’s My Family product became obsolete on September 30th, leaving many people with no place to discuss family lines and groups and share pictures and documents.   The new myGroups is designed to replace some of that functionality within the context of a project.  A project could be defined as an ancestral couple, for example or a surname project, or a haplogroup project.  Of course, the discussions would be quite different for each type of myGroup.  They are ready to launch this in an alpha state and if someone is excited about this and wants to volunteer, and can deal with a few bugs…then please drop Family Tree DNA a note.

News in the Field

We had many wonderful presentations, but my personal favorite was by Michael Hammer.

DSC_0020

I can’t begin to do this topic justice without a real keyboard and a decent internet connection so I can upload lots of pictures.  We now have 18 fully genome sequenced ancient DNA samples, which is, admittedly, just a smattering.  However, if they are representative of the hunter-gatherer (Paleolithic) and early farmer (Neolithic) populations, then what we thought we knew about Y haplogroup R, J and others has just been turned upside down.  And then, there is the teaser, like what is haplogroup C doing in Spain???

Oh, and want to know how much of your European DNA is ancestrally neolithic, hunter-gatherer, ancient northern european or later from the metallic age?  That’s one of the features Family Tree DNA was asked about and I believe they said that was something they could probably do. I’m not positive if that means they will implement that feature, but I do know they’ll evaluate how difficult and accurate this would be to implement.

Join me in a few days, after I get home, when I promise, I’ll do Michael’s presentation justice.  I’m so excited about ancient DNA and the secrets it’s unlocking!!!

Fun times ahead!

______________________________________________________________

Disclosure

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase the price you pay but helps me to keep the lights on and this informational blog free for everyone. Please click on the links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Transfers

Genealogy Services

Genealogy Research

Haplogroup Projects

So far, in our Projects series, we’ve talked about Autosomal Matching within Projects and Surname Projects.

Today, we’re going to talk about Haplogroup Projects, a second type of project sponsored by Family Tree DNA for DNA participants who test at or transfer results to their labs.

You can transfer autosomal results from either 23andMe or Ancestry for $69.  You can transfer Y and mitochondrial DNA results from Ancestry.com to Family Tree DNA for $19 until the end of September when your results, along with the data base, will be destroyed at Ancestry.

If you tested at 23andMe, you receive a Y (if a male) and mitochondrial DNA haplogroup.  To obtain the various markers for either Y or mtDNA, you’ll need to order those tests from Family Tree DNA.  A haplogroup estimate alone won’t do it and your haplogroup may change with additional marker testing.  You can read more about why and how this works here.

While surname projects focus on surname lineage, haplogroups focus on haplogroup or deep clan lineage.  You can read about haplogroups here and the new naming convention that took letter/number names like R1b1a2 to SNP based names like R-M269, here and here.

If you would like to review the difference between STR and SNP markers, click here and if you’d like to understand SNP testing and why someone would want to do that, click here.

Haplogroup projects exist for both Y and mitochondrial DNA.  In general, they are research projects carried out by citizen scientists, sometimes with the aid of professionals in the field.  They are extremely beneficial to both participants and the genetic genealogy community as a whole.   There have been a slew of discoveries at the hands of project administrators, who are all volunteers.

While the projects are discovery focused, for participants, viewing project pages, such as the haplogroup matches page, can be very useful in determining the location and migration path of any particular haplogroup and subgroup.  I recently used haplogroup location information when writing about Elisabetha Mehlheimer and my attempts to figure out if her ancestry is German or Scandinavian.  Your personal haplogroup history extends much further back in time than your individual match history.  If someone from your genealogical line has tested, you can track each of your ancestral lines back in time utilizing haplogroups.  Where were they, what were they doing and which groups of people were they migrating with?  Were they Africans in Africa, hunter- gatherers crossing the Asian plains, the world’s first farmers migrating from the Middle East into Europe or Native Americans crossing Beringia into the New World?  They are in you, and their history is held in the DNA of their descendants.

Projects are established when an individual requests, generally via an e-mail, Family Tree DNA to establish a new project.  Family Tree DNA does not allow duplicate or competing projects, but they are very generous in terms of projects that are in the same haplogroup but focused on different areas.  For example, there is a haplogroup Q project and then a Nordic Q and an Amerindian Q project as well.

haplogroup proj 1

Haplogroup E is a bit different.  There are two primary haplogroup E projects, one for each of the two major E lineages, and then subgroups based on downstream SNPs or other interests, like Scotland.

haplogroup proj 2

Didn’t know that haplogroup E, which is considered African or North African/Mediterranean is found in Scotland and England?  Not only is it found there, we know how it arrived.  That too was a discovery of genetic genealogist, Steven Bird.

As you might have noticed, haplogroup projects are all about sharing.  This is the perfect example of where there is incredible strength in collaboration.  The great news is that sharing doesn’t cost, you, the participant, one penny.  It’s free.

Joining

So, how does one join a haplogroup project?

At the top of your personal page at Family Tree DNA, you have a “My Projects” link.

surname5

Fly over that link and you’ll see the above options.

Click on Join.

The first thing you’ll see are projects where the surname administrator has entered specific surnames of interest to that project.  In my case, my surname is Estes, and these are the projects that include the Estes surname in their surname list.

surname6

Haplogroup projects are not in this list.  Yes, I wish they were, based on the haplogroup involved, but there are many haplogroups that don’t have surname projects, especially subgroups – so technically, it would be very challenging to implement this feature.  I still wish it was offered, because I think the vast majority of testers don’t know about haplogroup projects, which ones to join, or why they would want to.

To view mitochondrial or Y DNA haplogroup projects, scroll down.  At the bottom of the list, you’ll find both, alphabetized, with the total number of projects in that category displayed.

haplogroup proj 3

Looking at mitochondrial haplogroup K, there is only one project, so there are no decisions to make about which project or projects to join.

haplogroup proj 4 crop

Click on the haplogroup letter to view the list of projects, then on the project name to view the project description.  In most cases, the project administrator’s name is displayed with their e-mail in case you have questions.

haplogroup proj 5

I really hate to see projects with only one administrator, although my own fall into that category.  It’s generally not by choice.  If you see a project with only a sole administrator and you have an interest, consider volunteering.  Everyone needs a backup, just in case.

Y DNA projects should only display the Y tab at the top of the page, and mitochondrial DNA projects, the mtDNA Results tab.  Mitochondrial DNA results aren’t relevant to a Y project and vice versa.

To see how participants are grouped within the project, click on the mtDNA Results tab and then “Results.”

haplogroup proj 6Project administrators can group projects in any way they see fit, but generally haplogroup project administrators group participants by subgroup.  In some cases, particularly with mitochondrial DNA, they may go ahead and group people based on a newly defined but not yet published haplogroup or a defining mutation that may become a haplogroup.  That’s what Bill Hurst has done below with haplogroup K1a10.  You’ll notice that some of the participants are not classified as K1a10 by Family Tree DNA – that’s where the experience of the haplogroup administrator comes into play.

Generally, haplogroup administrators know more about a given haplogroup than anyone else in the world…and yes…I do mean that literally.

haplogroup proj 7

Which Haplogroup to Join?

So, how do you know which haplogroup project or projects to join.

On the surface, that’s a very easy question to answer, and then, it gets a bit more complex.

Of course, women can only test for mitochondrial DNA, but men can test for both Y and mitochondrial DNA.

On your main personal page, you have a badge for both your Y and mtDNA haplogroup.

haplogroup proj 8

The haplogroups listed here are your most distinct, meaning the furthest down the tree you can go based on the testing level you’ve taken.  New branches are still being defined for both mitochondrial and Y DNA as people continue to test at higher levels and we, as a community, continue to learn.

If you receive a new branch assignment for Y DNA, your badge will change because your new terminal SNP will be a different SNP name.  So, when this person took the Big Y test, their haplogroup changed from R-M269 to R-L193.  The base haplogroup letter always precedes the SNP name – so we know it’s haplogroup R.

If a new haplogroup branch is defined for mitochondrial haplogroup H63a, it would then simply be added on, so potentially H63a1.  Mitochondrial DNA retains the older letter/number/letter structure.

Finding Your Place on the Tree

In the case of Y DNA haplogroup R, which is by far the most complex of the male haplogroups due to its sheer size and the massive number of downstream SNPs discovered, you’ll have to look at the haplotree on your personal page to determine your path back to the main branch of haplogroup R.  On the My DNA Tab, under Y DNA, click on the Haplogroup and SNPs page link.

haplogroup proj 9

At the top of the page, it tells you a bit about your terminal SNP and which SNPS have been tested positive and negative.  Based on this verbiage, we know the terminal SNP R-L193 is downstream of M343, which just happens to be haplogroup R1b, one of the two major branches of haplogroup R.  You can see the base of haplogroup R at the top of the page, and beneath that, the row with P241 is haplogroup R1.

Haplogroup M343 is highlighted in yellow and you can see where it descends from the P241 row as a brother to the M417 row.

haplogroup proj 10

Scrolling down one more time, we now see our terminal SNP and the branches to reach that SNP.  I find it much easier to work from the terminal SNP back up the tree, following the branches like creeks and rivers.  And just in case you are wondering, yes, I did select the most difficult haplogroup as an example because either you’ll be prepared, or when you look at your own non-R Y haplogroup, you’ll be overjoyed at how simple it is!

haplogroup proj 10b

In this case, this is what our path of descent looks like from haplogroup R.  Some of these subgroups will have projects defined.  Other won’t or will be included in a general haplogroup project.

Old FTDNA Haplogroup Defining SNP Mutation Project Defined
R M207 R-R1b All Subclades
R1 M173 No, not other than R-R1b All Subclades
R1b M343 No, not other than R-R1b All Subclades
R P25 No, not other than R-R1b All Subclades
R1b1a2 M269 No, not other than R-R1b All Subclades
R L23 No, not other than R-R1b All Subclades
R YSC0000072 No, not other than R-R1b All Subclades
R L51 No, not other than R-R1b All Subclades
R L151 No, not other than R-R1b All Subclades
R P311 No, not other than R-R1b All Subclades
R1b1a2a1a1b P312 P312 (R1b-P312)
R1b1a2a1a1b4 L21 R L21 and Subclades
R L513 R L513 and Subclades
R L193 Currently included in L513

To determine which subclades have projects defined, and which ones are appropriate to join, visit the project join page and look at the haplogroup R options.  Only a few of the 55 haplogroup R projects are shown below.

haplogroup proj 11

The first project you see is the “R-R1b and all subclades” project and by looking at the description, we know that this applies to M343, so that project is available for this person to join.

To make my life much easier, I do a screen search (Ctl+F) for the SNP I’m searching for.  I find two instances of M173, but looking at the project definition, I can see that this is not appropriate.  Why?  Because it’s for people who are M173 positive but M343 negative, and this person is M343 positive, so there is nothing appropriate for this person in the M173 project.  Please read project descriptions – each one is structured differently depending on its goals.

haplogroup proj 12

In the case of our participant, he is qualified to join 4 different haplogroup R projects, and I encourage everyone to join the appropriate projects.

When joining a project, be sure to read all of the project pages.  Every project has 4 pages available: Background, Goals, News and Results.  Not every administrator uses every page, but you’ve find extremely valuable information on at least some of the pages, and every project is different.  Many projects will have either a Yahoo group or a Facebook group to discuss research and findings.  These pages are where the administrators will tell you how to interact and obtain information.

I like to use project R-L21 as an example because it is one of the most active and best managed haplogroup projects I’ve encountered.  Kudos to the administrators, and in particular, Mike Walsh.  On the Background page of the L21 project, you will find a current haplotree, not found elsewhere, that details the new haplogroup branch definition beneath L21 based on SNP testing.

haplogroup proj 13 crop

Do understand though that if you join any project, your Y DNA 12-111 marker results are available for anyone on the internet to see, and your SNP results may be too, depending on whether the project administrator has enabled SNP viewing.  Yes, I know this sounds intuitively obvious, and it is, but I have to say this, just like I had to tell my kids over and over not to hit the bee hive with the stick.

So, if you don’t want old stick-in-the-mud auntie Broomhilda to know that your haplogroup is…shall we say…not what the family expected, then don’t join projects – because sure as shooting…someone’s gonna tell her!  Once something is on the internet, consider is gone, released into the wild, and viral, especially if you don’t want it to be!

For mitochondrial DNA, your HVR1 and HVR2 results will be publicly viewable, but your coding region or full sequence results will not be due to possible medical information being in the coding region.

Depending on how the project is set up, your oldest ancestor and/or surname may be visible too.  I encourage all project administrators to enable both the surname and the oldest ancestor field.  We discussed this in the Surname Project article.  There isn’t any reason not to.

Y DNA projects have two options that mtDNA projects don’t have.

haplogroup proj 14

The first option is colorized results, which are both easy and useful.  I find these most useful in surname projects, but in haplogroup projects, they make it easy to spot groupings of people.

haplogroup proj 15

The colorized results of the first few participants are shown above for the haplogroup R-21 project.  You can see that the administrators have included a recommendation for SNP testing in each category name.

When viewing colorized results, the system calculates the minimum, maximum and modal (most common) values for each marker value in each group that the administrator has set up.  In this case, you can see that the most common value is 13 for marker 393 and the first few participants in this grouping have values of 11 and 12.

The second additional option for Y DNA is that the administrator can display confirmed SNPs of participants.  Some administrators display this information and some do not.  There is no harm, that I know of, that has ever come from displaying this information.  However, do be aware that screen scraping of the data does take place.

haplogroup proj 16

Most of the individuals who purchase either individual SNP testing or one of the more comprehensive tests, like the Geno 2.0 or the Big Y do so not only to understand more about their own family deep history, but to contribute to the scientific effort as well.  Without the thousands of testers and the compiled information, we would have made little progress in this field in the last decade.  For example, we have gone from about 800 known, registered SNPs pre-Geno 2.0 to well over 35,000 today and that number grows every single day.

Big Y

As Mike so succinctly put it recently, the Big Y is still in the research arena, for early implementers and adopters, for those who want to be on the leading edge, to help define the frontier.  Yep, sounds like my ancestors.

The Big Y test is one of two avenues to obtain (nearly) full sequencing of the Y chromosome.

From a participants viewpoint, it may be confusing.  From the administrators viewpoint, it someplace between your worst nightmare and a DNA geeks dream come true, and vacillates between the two.  If you want to make and document discoveries, a true genetic explorer, this is the place to be.  This is it, the front line, the cutting edge, the frontier.

From an administrator’s point of view, I wish that everyone who is interested in SNP testing would just take the Big Y and get it over with.  The Big Y combined with STR results is a very powerful tool and we not only test for SNPs that are known, we test for newly discovered SNPs as well.  However, I well know that the cost of the Big Y at $499 is a deterrent for many people and they would prefer for the administrator to recommend a SNP or two to test for $29 or $39 and to arrive at the same end point.  Obviously, that isn’t going to happen.  The only exception would be if someone else within your group has tested and you can use their results as a guide.  Still, if you have new SNPS, you’ll never find them without the Big Y or similar type of next generation sequencing test.

Administrators do recommend the next SNP in a SNP step-by-step progression, but you have to know if you are positive or negative before being assigned the next SNP to test.  Sometimes step by step SNP testing is immediately productive, meaning you have a negative results and you’re done with that line, and sometimes it’s a long, expensive ordeal where the money would have been better spent on at least the Geno 2.0 test which is in-between step-by-step SNP testing and the Big Y.  That applies to most of haplogroup R, for example.  The Geno 2.0 cost has been reduced to $159 as well, so this becomes an attractive option if the participant can’t do the Big Y test.  Genographic results, of course, can be transferred to the participants Family Tree DNA account.

For the administrator, as much as we love the new information flowing from the Big Y tests, trying to manage these tests and make sense of them as a group is a NIGHTMARE.  Individuals have matching results on their individuals web page, but administrators have no tools to manage the entire group.  Everyone has developed their own methodology. Mike, in the haplogroup L21 project, sometimes uploads multiple spreadsheets daily.  However, it’s all this hard work that has defined the new L21 tree branches.

haplogroup proj 17

In fact, this tree is no longer up to date because the administrators can’t fit the branches on the chart above, so they have limited this tree to the major subclades of DF63 and DF13.  That’s the bad news and the good news all rolled into one.  It’s no wonder this has been called the SNP tsunami.  I think this comes in the category of “Be careful what you wish for!”

Grouping and Mapping

Two of the most critical, and useful, components of haplogroup projects are the ability to group individuals and then display maps of those groups.  Enabling mapping is absolutely critical.  Unfortunately, some haplogroup projects are housed at World Families and they do not implement the mapping feature.  I cringe every time I need to utilize one of these projects.  I feel that all projects are significantly handicapped without mapping, but this is especially critical to haplogroup projects because the maps speak to population migration and movement.

Below is the map of the European individuals in the L21 project who are L21, but have no further SNP testing.

haplogroup proj 18My Estes guys are in here, on that brown balloon in Kent.  What, there are too many balloons to see?  Well, maybe we need to take some SNP testing to narrow the field and further define our haplogroup.  I’m positive that Mike would agree!!!

If my Estes guys test positive for DF63, that makes quite a difference.

haplogroup proj 19

This map pretty much confirms that they these men aren’t Irish, while the next group looks to confirm just the opposite.

haplogroup proj 20

And look at this group.  Think that SNP FGC11134 might have evolved in Ireland?

All of the men in these last two maps are in L21, so advanced SNP testing, participant grouping by SNPs and mapping, together, can be a very powerful tool in sorting out the finer points of family ancestry.

This helps not just the person who tested, but all others who descend from that line.  This is quintessential collaboration and sharing.  While my Estes cousin might contribute by takeing a Big Y test, he’ll also benefit from the Big Ys that other men took, and being a genealogist, he’ll be watching his other non-Estes lines to see what they are discovering as well.  Most of us can only contribute on one or two lines, y and mtDNA at most, but we can all be a beneficiary on all of the rest of our ancestral lines.

I hope you’ll not only join haplogroup projects, but that you’ll utilize them to their fullest potential for all of your projects and ancestral lines.  If you’d like some help assembling a DNA pedigree chart, I’ve written an article titled “The DNA Pedigree Chart – Mining for Ancestors.”  It’s the genealogists version of panning for gold.  Enjoy!!!

______________________________________________________________

Disclosure

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase the price you pay but helps me to keep the lights on and this informational blog free for everyone. Please click on the links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Transfers

Genealogy Services

Genealogy Research

Surname Projects

This is the second in a series about DNA projects, how they work and how they can benefit testers and others.  DNA projects aren’t just for those who test.  There are other benefactors too – like those who descend from your paternal line and can’t test because they are females – for example.

Most people don’t utilize all of the project features nor the features they do use, fully.

The first article in this series discussed finding autosomal DNA matches in any project, whether it’s a surname project, a haplogroup project or a geographic project.

Today’s article about surname projects discusses the projects from both the administrator’s perspective as well as that of the participant.  I administer several surname projects and I work with them on behalf of my clients when I’m writing their Personalized DNA Reports every day.  So, I see them routinely from every angle. All of the projects that I’m discussing are found at Family Tree DNA and are for their clients.  Joining projects is free and you can join as many as you want.

Surname projects were the first type of project to be defined by Family Tree DNA.  These are the most straightforward of project types, at least on the surface, because it’s inherently obvious if you are a male, and if you carry a particular surname.  Only males can test their Y DNA, because women don’t carry a Y chromosome – and the Y DNA follows the surname path – so long as that surname path does not include any nonparental events or adoptions.

So, if you’re a Smith male, you would test and join the Smith project, an Estes male joins the Estes project, and so forth.

Finding a Surname Project

If you don’t know whether a project exists for your surname, there are two ways to find out.

If you’re not yet a client of Family Tree DNA, click here, and on their main page scroll all the way to the bottom.  In the Community column, all the way to the right, click on Projects.

surname1

This takes you to the project search page where you can enter the surname you are searching for in the Project Search box in the upper right corner, or you can browse through the various surname and geographic projects using the alphabetic options on the left.

surname2

Entering a surname and searching will take you to the page with relevant information for that surname, in this case, Estes.

surname3

It tells you how many people with the surname of Estes have tested.  The 157 shown will include both males and females.

It shows you if there is an Estes surname project.  There is, and there are 170 members.  We’ll talk about what that means in a minute.

Then, other projects are shown were the project administrators have listed Estes as a surname of interest.  This does not automatically mean that these projects are relevant to your Estes line, but that the surname is of interest to that project for some reason.

To order a kit and join the Estes project, click on the Estes project link.

The next page allows you to join the Estes project and purchase DNA testing of various types.  Purchasing a kit through this page automatically joins you to the project.

surname estes

The project administrator is automatically notified and you will receive a welcome e-mail if the project administrator has implemented that feature.  Many administrators include a request for your genealogy in their welcome e-mail.  After all, a surname project can and does pertain to all instances of that surname, and the administrator has no way of knowing how you are connected to which line without your genealogy info.  This also helps them group your results appropriately.

An Alternative Project List

If you don’t want to look at the projects by category, and you want to simply scroll through a list alphabetically, this link at Worldfamilies.net provides you with exactly that service.  Keep in mind that haplogroup, geographic and surname projects will all be intermingled, but that’s not necessarily a bad thing.  They also provide a surname search.

surname4

The links that show “project site” indicate there is also a WorldFamilies.net project for that surname as well.

Joining Projects After Testing

If you have already tested, and I’m referring to Y DNA testing here, you’ll want to join your surname project, and possibly others, after your results are back.  In some cases, you won’t know what projects you qualify to join until your results are back, such as haplogroup projects.  DNA testing determines your haplogroup.

To join a project, on your personal page, on the top left, you’ll see My Projects.  Click on Join.

surname5

You will see a list of projects where the surname administrator has entered Estes as a surname of interest.

What does this mean to you and how do you decide which projects to join?

Read the project descriptions.

Some of these projects are clearly NOT relevant for you.

Myth – Many people think that the projects they see on these lists are “being recommended” by Family Tree DNA.  Not true.  The fact that the project appears on the list is the sole function of the administrator entering that surname in the project surname list of their project profile.

Let’s take a look at this list for our Estes participant.

surname6

In this case, the Estes ancestor in question is a descendant of Abraham Estes, so the Estes project would be appropriate.  Reading the description of the Estis Jewish Ukraine project, that one doesn’t fit, and neither does the Jester project.  Why are these listed under the surname Estes?  Because the project administrators entered Estes as a surname of interest – because clearly Estis is misspelled Estes and Estes may be a found when looking for Jester as well.

That leaves three other projects to look at.

By clicking on the I-L161 (I2a2b-Isles) Project, you can read the description, as follows:

surname7

It’s rather unusual for a haplogroup project to include surnames, but it’s entirely up to the administrator.  Apparently, at least one of the Estes lines is I-L161 and this project administrator wants to be sure to catch any others.  So, if your Estes haplogroup does not match the project description, then this project is not for you either.

The last two projects are the Cumberland Gap Y and mtDNA projects.  Why is Estes listed here?

surname8

The description tells us that the project is for those families whose ancestors settled in or passed through the Cumberland Gap region that is associated with Claiborne, Hancock and Hawkins Co., in Tn., Lee, Russell or Scott Counties in Virginia, or Bell or Harlan Counties in Kentucky.  If this fits your paternal line, the Estes family line, then this project is a good fit for you.  In this case, it is.  If not, then this isn’t the project for you.

The last project is the Cumberland Gap mitochondrial DNA project.  Since we’re discussing Y DNA testing, a mtDNA project is not relevant to you, so this isn’t the project for you either.

Of the 6 projects listed as possibilities, only 2 are relevant to the Estes line in question.

Myth – All projects listed are relevant to you.

The only projects that appear as a result of a surname search are projects where the administrator knows that the surname is relevant and goes to the effort to enter relevant surnames when they define their project.

surname9

Myth – All projects relevant to you will be listed.  Not true – neither Family Tree DNA nor the other project administrators have the ability to determine what is relevant to your family line.

It may behoove you to browse through the projects in the Y Geographic and Dual Geographic categories.  For example, my Estes family is from Kent in England.  Is there a Kent geographic project?  No, but there is a British Isles by County project.

surname10

Maybe this would be interesting.  Based on their description, the Estes family qualifies because we have a proven geographic connection to Kent.

Dual projects apply to both Y DNA and mtDNA.  We’ll talk about special challenges for these types of projects when we discuss Geographic Projects.

Administrators

Administrators of all projects are volunteers and receive no compensation for their services.  Most are somehow connected to the projects they manage.  For example, I administer the Estes surname project, my maiden name, the Bolton project, my paternal grandmother’s maiden name, and so forth.

The knowledge and dedication of administrators varies as much as individual people do.  Some administrators spend an inordinate amount of time on their projects, and some barely any.  If you have problems contacting a project administrator, notify Family Tree DNA.  Something may have happened and a new administrator may need to be found.  If you have expertise in the specific surname line, consider becoming a co-administrator.  Nearly unanimously administrators are looking for help and for a backup, just in case something does happen.

Unless the administrator does something unethical or outside of the administrator guidelines, they have the freedom to group and run the project in the manner they see fit.  If you would like to see something done differently, make that suggestion, nicely, or volunteer to help.

You might be surprised how much criticism administrators receive from  people who disappear entirely the minute the suggestion is made that they do something besides criticize.

Challenges

There are three main challenges faced by surname projects.

  1. Women
  2. Nonparental Events
  3. Autosomal DNA

Women

One of the challenges every surname administrator faces sooner or later is how to handle women who descend from these lines, or carry the surname, and want to join the project.

Often, this request stems more from a desire to belong than a scientific basis.  Let me explain.

My maiden name is Estes and that is the surname I identify with most strongly.  I would like to join the Estes project because I “belong” there.  As a female, I can test my mitochondrial DNA and my autosomal DNA, neither of which are relevant to a Y DNA project.

Many administrators simply don’t allow females in this situation to join – and that is their prerogative.  I always have included females, and not just because I am one.  Why?  Because it doesn’t hurt the project or cause me as an administrator any problems or extra work.  It makes them feel included, and often, women are the “keepers” of the family history.  With the advent of autosomal testing, I’m glad that I have included females because now I have a group of Estes descended people already gathered.

Each project admin can enable or disable Y DNA results and mtDNA from showing on their public project page.

surname11

A Y DNA project should have mtDNA disabled, so the mtDNA of the women and men who join are not showing in this project, because they are not relevant to the Estes surname project.

Nonparental  or Nonpaternal Events (NPEs)

What do surname administrators do in two awkward instances?

The first is when someone thinks they will match an ancestral name, like the descendants of Abraham Estes, the US immigrant, but they don’t match any Estes line?

I refer to these situations as undocumented adoptions even through they are generally referred to at NonPaternal events, or NPEs.  This means that somewhere, somehow, an “adoption” has occurred.  It could be in the current generation as a legal adoption.  It could be in the 1800s as a step-child taking the surname of his step-father.  It could be in the 1700s as an unwed mother gave her child her surname, but the child carried the Y DNA of his unnamed father.  Or, it could have been due to an infidelity or a relationship that was unwelcome.  Regardless of why, or how, or when, I tell people that they ARE an Estes, that this is their line, and it’s simply a newly documented Estes line.  I go to every effort to make them feel welcome and included and I try very hard to avoid any words that have negative connotations or could be hurtful or make them uncomfortable, like, for example, illegitimate.  Generally, the information alone is quite a shock and I try to position it in the best, most positive, light possible.  Of the undocumented adoptions I’ve been able to identify, most of the time it has to do with a step-father giving a child his surname.  Certainly, an act of love.  Every surname will have these circumstances, given enough time and testers.

Administrators have a variety of ways to deal with this, depending on the cirumstances at hand and how the participant feels about the situation.

surname12

In some cases, I give them their own category based on what is known.  Hershel Estis from the Ukraine is a good example.  So is Moses of Pendleton District, SC.  When I don’t have a lot of information, I may simply group them in the “New Estes Line” category.

And then there’s the opposite situation.  Someone with a non-Estes surname matches an Estes – and I mean exactly including all the rare marker values.  They are obviously genetically an Estes, but they don’t know when that Estes line got genetically inserted into their surname line.  Taking a look at their genealogy and where an Estes might have lived in close proximity might lend an important clue about where the change might have occurred.

I welcome these folks into the project too.  It can’t hurt and it gives them a sense of belonging.  They are clearly related.  I group them with the line they most closely match.

Autosomal DNA

Autosomal DNA testing is wonderful and it has caused so many walls to fall.  However, it’s difficult to work with in a project because there are few good tools.  Part of the problem is that, unlike Y DNA results where you have a few hundred people at most, who match on 111 markers at max – with autosomal you have thousands who match you, but may or may not match each other on millions of locations.  How do you effectively display this kind of information and make it relevant to projects?

Because I want to know more about the Estes autosomal DNA, I encourage people who do not carry the Estes surname, but do descend from an Estes ancestor to join the project.  This applies to all of my surname projects.  Why?

It does cause me more work, which is why many admins don’t encourage or allow it.  And the level of work differs for males and females.  Females won’t show in the Y part of the projects, so if mtDNA display is disabled, they don’t show publicly at all – so no problem.  But males are different.  They will each show in the Y part of the project, even though they aren’t Estes males unless I disable the display for each of them individually, and then they want to know why they aren’t in the project – when they are.

What I do is to create a category called “Autosomal Estes.”

surname autosomal

This means that they descend autosomally from an Estes, even though they are showing on the Y page.  I realize this isn’t the ideal solution, but until Family Tree DNA implements a third tab that says “autosomal” in projects, it’s about the best I can do.  Other suggestions from admins about how they handle this situation are certainly welcome.

Autosomal Matching

In the first Projects article, we talked about autosomal matching from the perspective of the participant.  By utilizing the Advanced Matching feature, any participant can see who they match autosomally within any project they have joined.

My own advanced matching example in the Estes project is shown below.

surname13

However, administrators have a second tool that they can use, but the results are not publicly displayed.  I almost hate to mention this, because I don’t want admins to be overwhelmed with requests.  Keep in mind that you can see your own individual match results utilizing the technique above, for every project you have joined.  Of course, you can always see your matches in all projects from your personal page.

Administrators have a group of genetic reports available to them and among those is the Illumina OnmiExpress Matrix.  It looks and functions like the regular Matrix that we all use to see which of our matches that match us also match each other.

surname14

This matrix gives the administrator the ability to see who, within the project, who matches whom.  However, with a large project, the administrator would have to do these matches in “shifts” or the sheer number overwhelms the size of the screen, etc.

As an administrator, it’s easier to view a members results individually to see who they match.  For example, if I want to see if Tommy Moore, my Moore cousin, matches anyone within the project, it’s much easier just to look at Tommy Moore’s results.  That’s why Tommy is in the Estes project, so that I can do just that since I’m the one responsible for Tommy’s kit.

As an administrator, what I’d really like is the ability to simply generate a file that downloads to a spreadsheet with a match matrix for everyone in the project.

And by way of reminder, just because people match autosomally within a project, it’s not proof positive that their common ancestor is that surname, although it is indeed, a good hint and a good starting point.  The ancestor from which the DNA originated can only be proven through triangulation and the matrix tool.  Now, the good news is that indeed, you have lots of opportunities for triangulation within a surname project.

Other DNA

Sometimes in projects, you’ll find “other DNA.”  In my case, in the Estes project, there are three Moores, a Lentz and two Campbells, etc.  This is because these are tests that I have sponsored and I have them in my project where I can access them easily as an admin.  In the case of the Moore line, they are also “Estes related” autosomally in that John R. Estes married Nancy Ann Moore in 1811, and these Moore folks are from that family line.  The same holds true for the Campbell line.

Does this get a little blurry and a bit messy?  Yes, but that’s also why it’s important, really important, to read the project description and what the admin has to say.  It’s also why each project has a contact for the project administrator.  If in doubt, ask, but AFTER reading, please:)  You would be amazed how may requests admins receive that have been already answered if the person would have read the project information.

About the Group

Each project, at the top of the page, has an “About this Group” tab.

surname15

Those tabs include the project background, goals which will often include information about specific lines being sought, news and results.  I should be a better administrator and keep mine more up to date.

In the Younger project, one of the early goals was to determine if the Halifax County, Virginia group of Youngers was related to the notorious Younger Gang Youngers.  If you take a look at the results section, you will see that the administrators have written about the question and the answers, as well.

As administrators, we collected the genealogy of each participant and before publishing this information, by kit number, we sent each of the participants the document and obtained their approval.  Yes, it was a pain, but it was necessary, as we didn’t want to divulge information that was not acceptable to the participants.  Only one participant declined to participate.  Having gathered and published this information has been a godsend repeatedly.

The corresponding Younger Y DNA project page is color coded to match the results description.

Every project is managed differently.

 WorldFamilies.net

One of the weaknesses of the Family Tree DNA projects is that there is no avenue for the administrators, other than documenting the genealogy/pedigrees in the “About the Group” section like we did in the Younger project, to provide genealogical information about the lines being tested.  Several years ago, WorldFamilies.net stepped up to the plate to work with Family Tree DNA to provide an alternative display for project administrators.

surname16

In some ways, I think the enhanced pedigrees are wonderful because they connect with the kit number from their WorldFamilies Y DNA page.

surname17

However, the down side is that the results are not automatically updated from Family Tree DNA and there is no Match Mapping.  Now you may be thinking to yourself, “how important can match mapping be?”  The answer is that it can actually provide the brick wall breakthrough for some people.  For example, just yesterday, one of my clients found on their match mapping that the oldest ancestor of one of their low level matches was located very close to their own ancestral line.  You can see their white balloon almost on top of a red match balloon underneath.

surname18

While they might not have bothered to contact this person, because there were a low level match, not having tested at a higher level – now they definitely will contact that person.

For someone whose surname is stuck in the US, an ancestral match to someone of the same surname and matching DNA in the old country can be the cannonball that breaks through the brick wall of “where are we from?”  That’s exactly what happened with my McDowell line in Ireland.

Mapping is an extremely important tool, and one that’s often not utilized to its full potential.

Some WorldFamilies projects also maintain their project page at Family Tree DNA as well, so you can have the best of both worlds.

How to Help Yourself

Projects form the framework for DNA matching and solving long-standing problems, but they can only do so much.  There are many things that participants can do that will help projects solve those mysteries.

1. Update the most distant ancestor field. This is important because anyone perusing the project will be able to tell if your line is potentially their line too. Remember, your DNA represents the paternal line DNA for thousands of us who care a great deal about it but can’t test for your surname’s Y chromosome.  You never know what we might have in terms of research that might be useful to you, if we can find you through our common ancestor.

surname19

See all of those blank Paternal Ancestor Names?  That’s because no one entered the most distant ancestor information.  We can’t find you if your oldest ancestor information isn’t there.

Conversely, admins need to enable the “oldest ancestor” field to show.  It helps recruit new members and disabling it has no benefit that I’ve ever been able to discern.  I can’t tell you how disheartening it is to find no oldest ancestors listed and then be unable to contact the administrator to find out if any represent your family line.  In this case, project mapping isn’t enabled either, so the public website project is virtually useless.

2. Upload a GEDCOM file. Every individual’s results have a location for a GEDCOM file. Uploading a file prevents people from writing to you and asking questions that could easily be answered. With autosomal testing, uploading a GEDCOM has become even more important.

Currently, your personal and genealogical information is managed from the “Manage Personal Information” link on the left hand side of your personal page.  I’m hoping Family Tree DNA will put link this back on the top of the page with the other list of links.

surname20

Click on Manage Personal Information.

surname21

Of the above options, Most Distant Ancestors, Surnames and the GEDCOM file need to be addressed.

3. Enter your matching map geographic information. This is done from the Matching Map which can be found on your Y DNA list at the top of your personal page.

surname22

Click on Matches Maps, and then on the bottom of the map of matches, you’ll see “Update Ancestor’s Location.”  Your most distant ancestor’s location will be defaulted to the equator if you don’t enter this information.

surname23

Clicking on “Update Paternal Location” steps you through the process.

surname24

Enter the location, then click on search.

surname25

The location will be returned to you.

surname26

If this is correct, click on “select.”

surname27

Click on next is this is correct.

surname28

Then click on save and exit.

surname29

Now your white balloon shows up where your most distant ancestor in this line is known to have lived.  Hey, who are those other purple people living nearly and who match my ancestor?  Are they Estes folks?  Well, just click on their balloons to see.

See why entering most distant ancestor and their location is so important?

Summary

Surname projects are very powerful tools.  They are most powerful when we, as participants, provide full information, and administrators enable as much information as possible to be displayed which includes the fields for “most distant ancestor” and the mapping function.

For many genealogists, the only way they will ever be able to determine the Y DNA of their 5th great grandfather is through finding their line in a surname project.  If you’re interested in ways to do that, take a look at the article, “The DNA Pedigree Chart – Mining for Ancestors.”  You never know who is waiting for you!!!

Please join me for the next article in this series about Haplogroup Projects.

______________________________________________________________

Disclosure

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase the price you pay but helps me to keep the lights on and this informational blog free for everyone. Please click on the links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Transfers

Genealogy Services

Genealogy Research

Autosomal DNA Matching within Projects

Family Tree DNA was gracious enough to establish projects for genealogists – in fact – that’s one of the first things they did.  However, when they established projects, some 14 or 15 years ago, the first projects that existed were Y DNA projects.  The Y DNA, of course, is passed from father to son, along with the surname, so the projects were called “surname projects.”

Women, of course, are genealogically jinxed because their surnames have historically changed in every generation, with marriage, and sometimes multiple times, with multiple marriages – so which surname project would they join?  The answer is, it varies, and more often than not, the answer is none.  They roam around like homeless nomads.  Mitochondrial DNA tools and data bases lag far behind those of Y or autosomal DNA.

There are four types of projects at Family Tree DNA.

  1. Surname projects
  2. Haplogroup projects
  3. Geographic projects
  4. Mitochondrial DNA lineage projects

Mitochondrial DNA lineage projects have never really caught on, probably because there is no good way to find them, but the other three types of projects are very common and widely used.

In upcoming articles, we’re going to look at each type of project, what it provides, to whom, and any special challenges it might have.

However, there is one universal challenge with projects and that’s how to find and handle autosomal matches.  Autosomal testing didn’t exist when projects were first defined, and now we don’t quite know how to handle autosomal testing and people who descend from specific lines but not through the Y chromosome.  In other words, my paternal grandmother was a Bolton, but it’s not my surname – should I and could I join the Bolton project?  In the past, assuredly, the answer would have been “no,” because the Bolton project is a Y DNA project – but is the answer still no?  That depends on the project and the administrators, and we’ll discuss these types of issues in the upcoming Surname Projects article.

However, regardless of the type of project, there is one question that gets asked a lot, and the answer is always the same.

Can I compare my autosomal DNA to other project members?

And the answer is…..drum roll please….yes.  However, not in the way you might expect.

All projects and types of projects, and all tests, except Big Y, SNP and factoids are included in the advanced matching features available on every participants home page at Family Tree DNA.  This means that you can see who you match, within each project you have joined, on each kind of and combination of kinds of tests.

Sign on to your personal page, and under “My DNA,” under either Y DNA, mtDNA or Family Finder, you have an “Advanced Matching” option.

y dna options

Selecting the Advanced Matching Option will show the following options.

advanced matches

Selecting Family Finder and then the project where you’d like to see who you match, in this case, “Speaks,” and then clicking on “Run Report” gives you the following.

speaks ff match

Within the project, you can see who you match, if they have had their Y or mtDNA tested, and if so, the haplogroup, and their estimated relationship range (to you) utilizing Family Finder.

Now, let me tell you what this DOESN’T mean.

It doesn’t automatically mean that you match these people on this same family line.

I want to say that again, and louder, because this is one of the most common erroneous assumptions I see.

autosomal does not

You have to do more work, chromosome matching and triangulation to determine how you match these people, and on which lines.

And it does not, DOES NOT, mean that if you are both members of a geographic project, like the American Indian project, for example, that you are American Indian because you match someone in the American Indian project.  You might match them on a completely different non-Indian line.

It also DOES NOT mean that these people who match you, match each other.  You can determine that, but you’ll need to utilize the matrix tool to see who matches whom.  In fact, in the example above, Stacy and Lola-Margaret do not match each other.

You simply cannot assume.  You know what assume does….

No jumping to conclusions either, no matter how excited you are or how promising a match within that project looks to be.  Conclusion jumping works functionally the same as assume.

If this seems a bit confusing to you, let me explain.

Autosomal DNA tests test and include your DNA that you received from all of your ancestral lines.  It reaches back in time reliably 5 or 6 generations, and often further, in terms of matching to your genetic cousins.

DNA Pedigree

At 5 generations, you have 32 separate ancestral lines, and at 6 generations, you have 64 different ancestral lines.

Y surname projects typically focus on one line, the blue Estes line above.  Mitochondrial DNA is the same, focusing on the red circle matrilineal line above  But your autosomal DNA match within the Estes project could reflect an Estes line match, or any of your 31 genealogical other lines at 5 generations.  People who join projects typically do so because of their relationship with one particular line, like the Estes line – but autosomal has the capability to and does reach across all lines – so just because you match someone in the same DNA project does not mean that’s where your genetic match comes from.  Of course, it’s a wonderful hint, especially if you’re an Estes and it’s the Estes project, and a great place to start looking – but it’s NOT a given.  And of course, in haplogroup and geographic projects, the connection is even less apparent.  The Y DNA and mtDNA haplogroup fields are also another great hint and can quickly eliminate, or suggest, those possible lines.

Are you curious to see who you match in different projects?  Take a look.  You never know what kind of surprise might be waiting.

______________________________________________________________

Disclosure

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase the price you pay but helps me to keep the lights on and this informational blog free for everyone. Please click on the links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Transfers

Genealogy Services

Genealogy Research

Lazarus Dodson (1760-1826), Revolutionary War Veteran, 52 Ancestors #27

jigsawWhen I first started researching Lazarus Dodson, Sr., he seemed impossibly vague.  He moved from place to place throughout his life, across states and on the frontier of early America in areas not yet states, and never left a forwarding, or return, address.  We don’t know who his wife was, and his life was only reassembled from pieces and tidbits.  We still have more questions than answers, but some of the hints we’ve picked up along the way are incredibly tantalizing.

Was his wife Native?  Why was he encamped with the Indians?  Was his son really an Indian Trader?  Was another son murdered?  Follow along as we piece the clues of Lazarus life together into something resembling a partially completed puzzle.

Lazarus Dodson, son of Raleigh Dodson and his wife, Mary, surname unknown, was probably born about 1760, perhaps slightly earlier, probably in North Farnham Parish in Richmond County, Virginia.  However, there is some evidence that his father, Raleigh was living in Prince William County between 1759-1761, based on a court case, Raleigh Dodson vs John Webb in trespass found in the Prince William order book 1759-61, p 241, so Raleigh could have been born in Prince William County, Virginia.

Notes from the Broad Run Baptist Church in Faquier County, Va., after October 1763 but before May 1764 state that Lazarus Dodson was dismissed to Halifax, but this can’t be our Lazarus, given his age, so it must be the Reverend Lazarus Dodson.  Yes, of course, there had to be multiple men with the name Lazarus Dodson.  That’s just how these southern families work!

Raleigh, Lazarus’s father, is not mentioned beyond his birth which is recorded in North Farnham Parish register on February 16, 1730.

The Farnham Parish church as it stands today is believed to have been built about 1737.  It has been restored, although it was used as a stable during the Civil War.  It is located in Farnham, Virginia, in Richmond County at the intersection of North Farnham Church Road (County Route 692) and Cedar Grove Road (County Route 602) on North Farnham Church Road.  Given that the parish register included dates preceding 1737, this was obviously not the first church at this location, or the church met in private homes before the building was constructed.

North Farnham Church

We do find a Raleigh Dodson in Halifax County, VA, by 1766 when a Raughley Dodson and Lazarus Dodson witnessed a deed of Joseph Terry to Thomas Dodson, Halifax Deed book 6-363.  If this is our Lazarus, the son of Raleigh, he would have to have been born significantly before 1750 to be of age to sign a legal document.  Therefore, this is not our Lazarus and it’s probably not our Raleigh either.  There are two Raleigh/Lazarus pairs in Halifax County about this time, so it’s difficult to tell them apart.

On Feb. 19, 1768, John Roberson and wife Margaret of Orange Co. NC sold to Rolley Dodson of said county for 16# Virginia money 50 acres on the east side of the Country Line Creek.  Witnesses Hugh Kelly, Henry Hicks and Henry Willis.  Caswell Co., NC, was created from Orange in 1777 and Raleigh’s land fell into Caswell.  The Caswell tax list for that year shows him assessed for property in the Richmond District.  He and his wife Mary sold 50 acres of land on the south side of Country Line Creek (shown on the 1833 map below, just below the Dan River) on July 5, 1778 to Clement Gann (being purchased of John Robinson) and evidently moved to Hawkins County, TN about this time.  By this time, Lazarus would have been about 18 and would surely have welcomed the adventure of moving to the frontier of what would, in 1796, become Tennessee.  Lazarus would have been too young to have been married in 1778.

country line creek

We know Raleigh and Lazarus are still in the Virginia/NC area in May of 1777 when they signed the following oath of Allegiance in Pittsylvania County, which borders Halifax Co., Va. and Caswell Co., NC:

“I do swear or affirm that I renounce and refuse all allegiance to George the Third, King of Great Britain, his heirs and successors and that I will be faithful and bear true allegiance to the commonwealth of Virginia as a free and independent state and that I will not at any time do or cause to be done any matter or thing that will be prejudicial or injurious to the freedom and independence thereof as declared by congress and also that I will discover and make known to some one justice of the peace for the said state all treasons or traitorous conspiracies which I now or hereafter shall know to be formed against this or any of the United States of America.”

After Raleigh had left Caswell County, NC, the name of Rawley Dodson shows up there once again in the records in matters pertaining to the estate of John Moore, Jr (1786-1791).  A list of accounts included the name of Rawley Dodson in Caswell Co., Will Book C in June court 1792.

The marriage records of both Halifax County, Virginia and Caswell County, North Carolina, respectively, are intact and neither holds a record for Lazarus Dodson’s marriage to Jane whose surname is unknown.  Lazarus likely married her after his move to the frontier of then North Carolina, now Tennessee.

Arrival in East Tennessee

The next place we find Lazarus is in what would become Eastern Tennessee in the current County of Hawkins.  This 1783 entry gives us a glimpse at what Lazarus was doing in the winter of 1781/1782, based on this land grant:

Page 105, grant 1262 –  Dec. 4 1783 – James Lea enters 317 acres on the North side Holston below the mouth of Richland Creek at a “certain place where Francis Maberry, Major John Reid, and Lazarus Dodson camped with the Indians as they was going down to the Nation last winter and opposite the camp on the other side of the river.”

This record, along with his later involvement with Indian lands in Alabama, his son Jesse being found living on the Indian lands in 1797, near or on the lands later to be settled by Lazarus himself, and Jesse later becoming an Indian trader, has always caused me to wonder if Lazarus Dodson married a Native woman.

Interestingly enough, the Lea family is also found on Country Creek in Caswell Co. NC.  The Dodson family is involved with the Lea family for generations.

The land entry that indicates that Lazarus was with Major John Reid may give us clues as to what Lazarus did during the Revolutionary War.

John Reid, a Major in the Revolutionary War, resided on the Holstein in Washington Co. VA and was appointed ensign in Illinois Regiment commanded by Lt. Col. John Montgomery. He immediately raised his quota of men, joined the regiment at Long Island on Holstein and served there, from January 9, 1779 to January 1781 during which time he acted as Adjutant from April 9 to June 1779 and as Quartermaster from June 1 to December 25, 1779. Reid also carried expresses from Cols. Evan Shelby, Arthur Campbell and David Smith. He was under Col. Campbell in the battle of Kings Mountain in October of 1780, and served as Quartermaster with Col William Campbell in the battle of Guilford Courthouse in March of 1781.

If Lazarus Dodson was with Major Reid in late 1781 or early 1782, this suggests he may have also been with him in the battles of Kings Mountain and Guilford Courthouse.  Lazarus may well have been among the men raised at Long Island of the Holston.

The Revolutionary War

Both Lazarus and his father, Raleigh Dodson served in the Revolutionary War.

Their Revolutionary War service is documented in “North Carolina Revolutionary Army Accounts, Index to Soldiers residing in Washington and Sullivan County, 1781-1783

NC Army Acct

Both Raleigh and Lazarus Dodson are listed.

nc army acct detail

After finding this tantalizing nugget, I contacted the NC Archives and eventually, visited, in order to obtain the original records.

According to pay records found in the NC Archives, in Raleigh, NC, Lazarus Dodson served in the Revolutionary War in August of 1783.  That is likely the date of his discharge, so he may have served earlier in the year.

Laz dodson rev war pay record

In 1783, an Act authorizing the opening of a land office for the redemption of specie and other certificates was passed, and all soldiers holding specie or certificates were enabled to redeem them by taking land in exchange, at a rate fixed by the state of North Carolina.

When I first saw this list of Specie certificates, I also noticed George Eastis, two names above Lazarus Dodson.  George lived in East Tennessee for a time, but ultimately went back to Halifax County, Virginia.  However, his son, John R. Estes settled in Claiborne County, TN and his son, John Y. Estes married Rutha Dodson, daughter of Lazarus Dodson (Jr.) and his wife, Elizabeth Campbell.  Nothing like a little synchronicity in genealogy.

laz dodson rev war auditor record

Believe it or not, there were two holes punched in this document, reflecting how it has been stored.

Raleigh and Lazarus Dodson both served in the Revolution and are both found in the Morgan district which includes the land that would become East Tennessee.

raleigh rev war record

A second Rolley Dotson is found in the Hillsboro district (auditors Mebane and Nichols), which is the area of NC below Halifax/Pittsylvania in VA.  We know that our Raleigh was in East Tennessee prior to this time.

district auditors

The auditors and their corresponding districts found in the archives helped define which Raleigh was which.

nc rev war districts

On April 16, 1784, Lazarus Dotson transferred land to David Rose – 5000 acres on a big creek that runs into Elk River on the south side of said river where a Buffaloe Road crosses the said creek running down said creek for compliment.  Warrant issued Feb 19 1787, #1691.  This may have been the land he claimed in payment for his Revolutionary War service.

Hawkins County, TN

In 1786, Lazarus signed the petition seeking the formation of Hawkins Co. from Sullivan along with his father, Raleigh, and brother, Toliver.

On Feb. 19, 1787, a warrant was issued to Lazarus Dodson for 5000 acres of land on the south side of Elk River which he had entered on April 16, 1784.  This warrant he had previously transferred to David Ross (Elk River runs primarily through the counties of Warren, Franklin and the SE corner of Giles in Tennessee).

Beautiful pool at the bend in Dodson Creek where it leaves the road.

By 1787, if not before, the family had selected the location across the Holston River from Rogersville that would eternally carry the Dodson name in the form of Dodson Creek (above) and later, the Dodson Creek Cemetery and Church (below).

dodson creek cemetery

The following photo shows the landscape from across the Holston river.  The TVA plant today is located on the east bank of Dodson Creek where it empties into the Holston River.  Raleigh and Lazarus owned the land on both sides of the creek into the rolling hills.

OLYMPUS DIGITAL CAMERA

In 1787, the entry book for John and Landon Carter, entry takers for Washington Co., NC, now Tennessee, shows a warrant, 1783, dated May 21, 1779, directing the surveyor of Sullivan Co. to lay off for William Payne 150 acres on the Holston River adjoining a tract of land known as the “burnt cabin”.  This land was surveyed on April 28 1787 for Rawleigh Dodson by Rawl Dodson, deputy surveyor.

The State of NC issued grants to Raleigh Dodson for two tracts of 150 acres, both apparently entered before Hawkins Co. was created from Sullivan in 1786, #1481 for 150 acres on the left fork of Dodson’s creek and #31489 for 150 acres on the south side of Holston River.  Dodson’s Creek, no doubt was named by or for Raleigh Dodson, is a branch of Holston River on the South side of the river and nearly opposite the town of Rogersville.  On this site was Dodson’s Ford where the Great War Path and Trading Path crossed the Holston river at the mouth of Dodson’s Creek.  The spot is marked by a Tennessee Historical marker.

Indian war path

The land around Dodson’s Ford is some of the most beautiful in E. Tennessee.  The photo below shows the area where Dodson’s Ford was located, across this field and behind the trees.  The Great Warrior Path also crossed here and a campsite was located near the river.

In October, 1780, the forces under Col. Arthur Campbell gathered here before going downriver to the attack on the Overhill Cherokee towns of Chota, Talequah, Tallassee, and others.

dodson ford

In 1788 Rolly Dotson enters 300 acres on the South side of Holston River and on both sides of Dotson’s Creek, beginning on Dodson’s line on a branch at a white oak marked D, runs along said Dodson’s line and up the branch, paying 7 pounds, 10 pence.[1] The warrant was issued and a duplicate warrant was issued as well on Sept 28, 1792.  In 1788, this warrant was assigned on August 12th from Raleigh to Lazarus Dodson.[2]

In 1789, Lazarus Dotson applied for his own 300 acres in Sullivan County on the South side of the “Holstein River”, grant #1491.

The photo below is peeking at the river near where Dodson’s Ford was located on the land that Raleigh and Lazarus owned.

holston river at dodson ford

In 1793 a survey for 300 acres was made for Lazarus Dodson assignee of Raleigh Dodson, Raleigh Dodson, Raleigh Dodson Sr. and Alexander Deberty chain carriers.[3]

The Amis Store in Hawkins County kept a ledger book.  Raleigh had a great number of transactions, but we just find this short entry for Lazarus in 1794.

Mr. Lazarus Dodson

1794, March 14 – to balance brought forward from LBF 91 (LB credit leaf missing)

1794, July 30 – by grindstones to balle (same amount as above)

Horse Breeder Too

Based on an article from the book, Making the American Thoroughbred: Especially in Tennessee, 1800-1845 by James Douglas Anderson published in 1916, it appears that Lazarus was involved in a horse-breeding operation with his brother-in-law, James Manasco.  One or the other of them, or maybe both, lived in Greene County at this time.

Chapter IV

HARDY TENNESSEE PIONEERS

The pedigrees of practically all thoroughbreds produced in Tennessee and Kentucky, and the pedigrees of a majority of all the thoroughbreds produced in the United States, between 1 883 and 1 896, trace to some of the horses named in this chapter and the next, as standing in Tennessee prior to 1845.

As early as 1790, according to Killebrew’s “Resources of Tennessee,” the following named thoroughbred stallions were brought to Sullivan County, which joins Virginia: Stately, Milton, Genus (doubtless Genius), Flag of Truce, Don Quixote, Diomed and Peter Quicksilver. The leading men in this movement were Col. John Scott, Col. William Blevins and members of the Snapp, Tipton, Greene and Rutledge families. Killebrew gives no pedigrees, hence I am unable to identify any of the horses. The records show, however, that horses of these names were of this period. The only imported horse named Diomed was the sire of Sir Archy, and he was not imported until 1 799.

Though I can find no authority other than Killebrew for the statement above made, there is still indisputable evidence that the thoroughbred beat the Constitution to Tennessee; or, to state it another way — “the Constitution followed the flag” of the thoroughbred to Tennessee.

Between 1790 and 1795 the following named stallions (pedigrees given here as in advertisements) were advertised in The Knoxville Register and State Gazette to stand in East Tennessee. The words in parentheses are mine.

Young St. George, by imp St. George, dam ” by the old Arabian who was imported and come out of the famous Rosetta.” Season 1792 at James Manasco’s and Lazarus Dodson’s, Greene County; $2 and a bushel of corn. (The imp St. George referred to was most likely the one foaled 1771, by Dragon, out of a mare by Blank.)

White Horn Branch of Bent Creek

Charles Campbell and his sons John and George also lived on Dodson’s Creek.  John and George Campbell would marry Jenny and Elizabeth Dobkins, daughters of Jacob Dobkins, also a Revolutionary War Veteran.  This entire family group, minus Raleigh Dodson and Charles Campbell who remained on their land in Hawkins County, would move to Claiborne County about 1800.

Lazarus maintained his residence on Dodson’s and Honeycutt’s Creeks, Hawkins Co., until he moved about 1797 to the Whitehorn Fork of Bent Creek, then in Hawkins Co., but now in Hamblen Co.

lazarus-dodson-white-horn

Charles Campbell and Lazarus’s brother, Oliver, Dodson witnessed this deed.

Bottom part of Lazarus Dodson's land purchase.

Jacob Dobkins lived there, and it is only about 9 or 10 miles on the main road that crossed the Holston River at Dodson’s Ford to Bull’s Gap where Whitehorn is located.  Lazarus Dodson’s son, Lazarus, who was born about 1795 would eventually marry Elizabeth Campbell, daughter of John Campbell, about 1819 after the entire group had moved to and settled in Claiborne County.

On March 29, 1800, Lazarus Dodson of Claiborne County sold to Johnathan Ling for $900 the 575 acre tract of land on White Horse Fork (also White Run Fork).  This deed is repeated in 1804, for some reason, but includes the words “being the same place whereon said Dodson formerly lived.”

An 1805 deed from Johnathan Long to Mathias Mires references this 111.5 acres as being part of 2 surveys that said Long bought of Lazarus Dodson and the same place that Mires is now living adj Walker and Manasco.  Lazarus’s brother-in-law was James Manasco, which probably explains why he moved to White Horn Branch of Lick Creek.

Claiborne County, Tennessee

By the spring of 1800 Lazarus (Sr.) was in Claiborne Co. where he settled on Gap Creek near Cumberland Gap.  His land lay on the west side of the Kentucky Road that ran from Tazewell to Cumberland Gap and near the “Back Valley Road” (Highway 63) which goes from near Cumberland Gap to Jacksboro in Campbell Co., Tn.[5]  Today this land is located on Tipprell Road between the town of Cumberland Gap and the town of Arthur.

A January 28, 1802 document filed in Hawkins County shows that Lazarus has obtained land or had some interest in the land where he lived.  Richard Mitchell and Rodham Kinner of Hawkins County are bound to Lazarus Dodson for $2700 payment to be made to said Lazarus in 12 months.  Condition is that tract in Powel’s Valley adjoining land of Elisha Wallice [Wallen] below Cumberland Gap being 640 acres.  If money not paid, obligation to remain in effect.  Witnesses A Nelson, John Gore.

Lazarus was a member of Gap Creek Baptist Church in Claiborne Co. and is referenced in the minutes on June 5th, Saturday, 1805.  Another church in the association had asked for their help with determining what to do about “a breach of fellowship with James Kenney and it given into the hands of members from other churches, to wit Absolom Hurst, Lazarus Dodson and Matthew Sims and they report on Sunday morning a matter too hard for them to define on for they had pulled every end of the string and it led them into the mire and so leave us just where they found us.”

This 1809 and 1810 Hawkins County entries confirm that indeed, the Claiborne County Lazarus Dodson is one and the same as the Lazarus Dodson in both Hawkins County and on the White Horse Fork of Bent Creek.

1809, Dec 26 – Mathias Miers of Jefferson Co. Tn to Edward Walker for $350 tract in Hawkins on Bent Creek, part 2 surveys bought of Lazarus Dodson and the same place where on said Walker now lives and adj line of other survey of Dodson’s and Manazius? (probably James Menasco, his brother-in-law).  Wit William Berry, Samuel King, Registered March 16, 1814

1810, Jan 17 – Lazarus Dodson of Claiborne to William Right of Hawkins for $400, 100 acres on the s side Holston River on Honeycutt’s creek, Mooney’s line.  Wit George Mooney, Edmond (Edward) Mooney, Proved Feb 1810 by both Mooney’s

Honeycutt’s Creek is beside Dodson Creek.  This does cause me to wonder why Lazarus owned an interest in land in Hawkins County.  This begs the question of whether Lazarus Sr.’s wife is a Honeycutt.

By 1810, Lazarus had sold all of his land in Hawkins County and subsequently purchased land in Claiborne County from Abner Lea.  The deed thus describes Lazarus’ place of residence, “560 acres in Claiborne where said Dotson now lives, on the Indian Country line, Joseph William’s corner, Gap Creek, a stake near Cumberland Mountain, the top of Poor Valley Ridge adjoining where John Jones formerly lived, Aaron Davis’ line.”  The “Indian Country line” ran from the Cumberland River in Kentucky to the Clinch River in Claiborne Co., Tn. on the west side of the Kentucky Road. It was created by treaty and it encompasses the territory referred to in the list of inhabitants for which the sheriff of Grainger Co was exempted from collecting taxes in 1797.  Jesse Dodson, possibly Lazarus’s son, was noted as living in the Indian area in 1797.  That fact that he was living on the Indian side may be very significant.

You can see, on map titled “A Map of Tennessee, Formerly Part of NC” from Mathew Carey’s American Atlas in 1795 that the Indian Boundary is shown colored pink just to the left of the Kentucky Road where it passes through the Cumberland Gap.

1795 map claiborne co

The court minutes of Claiborne reveal that Lazarus was appointed at the September term 1803 to serve as a juror for the December session.  He failed to appear.

At the March session 1804, Lazarus was appointed overseer of the Kentucky Road (now 25E) from Powell River in place of John Wallen with the following hands to work: “all of Capt. McKinney’s Company from the Kentucky road down to a line dividing between William Jones and Timothy Jennings and so across the valley leaving the house of Archibald McKinney in the said list of hands.”  At the same session, Lazarus was one of those appointed to the jury to view and mark a road the nearest and best way from the intersection of Jurden’s path with the Kentucky road on a direction to Cumberland Gap as far as the state line.

At the September term 1805 Moses Davis replaced Lazarus Dodson as overseer.  Lazarus continued serving as juror off and on through 1816.  At about this time, Lazarus Jr. becomes of age and it is not possible to distinguish between him and his father.  At no time in the records is either referred to as Sr. or Jr., so Lazarus Jr. may already have made his way to the Indian lands in Alabama as soon as he was old enough.

There is a gap in the surviving Claiborne records between Nov. 1808 and May 1812, and another between Aug. 1817 and Nov. 1819.  No reference is made in the surviving minutes to an estate settlement for Lazarus Dodson Sr.  The early Claiborne estate records are also missing.  Therefore we are unable to determine if Lazarus died in Claiborne Co.  It is a possibility that he went early into the Cherokee lands of Northern Alabama where some of his children went, and died there or in one of the Tennessee border counties or in McMinn County where his estate was divided among his heirs.

It’s unclear, but likely that these 1819 transactions involved Lazarus Sr., not Lazarus Jr., given when Lazarus Jr’s children were born in Alabama. The first item in 1819 is the sale of Lazarus land to William Hogan, the second the sale of the same land from Hogan to Lazarus Dodson and Abner Lee just a couple months later.

April 1819 – Indenture in 1819 between Joseph Williams of Surry Co., NC and Thomas Williams by his attorney in fact and William Hogan of Claiborne for $600, tract of land in Claiborne in Powells Valley commonly known by the name of Butcher Springs tract below Cumberland Gap.  Beginning on the Indian boundary line on three post oaks thence north 20 degrees, east 320 poles to 5 post oaks then south 68 degrees east 320 poles to a stake thence south 22 degrees west 320 poles to a stake thence north 68 degrees west 320 poles crossing Gap creek to the beginning containing by estimation 640 acres the same land granted by the state of NC to said Joseph Williams by pat no 485 referenced thereto being had will more fully appear with all and singular rights….Joseph Williams by his atty Thomas L. Williams wit Charles F. Keith, Anderson Barton, April term 1819 ack by Thomas L. Williams in open court, Registered October 16 (or 18) 1819.

On May 4, 1819, Lazarus sells his land to William Hogan – William Hogan of Lee Co., Va. bound into Lazarous Dotson and Abner Lea both of Claiborne in the penal sum of $5000, the condition being that “I this day purchased of Lazarous Dotson and Abner Lea a certain tract of land containing 640 acres.”  Wit Martin Beaty, William Jones, David Dodson.[7]  This may well have been in preparation for going to Alabama.  Some of the children of Lazarus Jr. were born in Alabama.  Lazarus Dobkins Dodson’s Civil War records indicate his birth location is in Alabama about this timeframe.

Oliver Dodson, brother to Lazarus Dodson (son of Raleigh), settled in Anderson County, Tn.  He was alive in 1803 and 1806, but deceased by Oct 16, 1819 when his brother Lazarus conveys land to his 5 children.

Oct. 16, 1819 – Lazarous Dodson of Claiborne Co. to William Dodson, Moses Stout, Willie Mullins, Henry Guttry, and Prudence Dodson, all of Anderson Co., for $1, 100 acres in Anderson Co on Cane creek by entry made by Lazarous Dodson, certificate #31 on Jan. 22, 1812, including the improvements where Oliver Dodson formerly lived.  Wit Elijah Jones, Jesse Dodson, John Cooper, John Lewalen. Proved Jan. session 1820.

In 1822, William Dotson, Lazarus’s nephew, son of his brother Toliver , of Dicature (sic) County, Alabama conveyed his one-fifth share of Oliver’s land to Michael Spesard.  William was in Jackson County by August 1820 when he commissioned Justice of the Peace in Jackson County.

William died in Jackson County, Alabama in 1872 and is buried in the Dodson Cemetery at Lim Rock, Alabama.

In 1826, Lazarus Jr., because Lazarus Sr. is now dead, buys back the same land, but for less money it appears.  Abner Lea, William Hogan, Lazarus Dodson and John Pace may all be related.

1826, Sept 20 – William Hogan to Lazrous Dodson and John Pace, all of Claiborne for $3500, 640 acres in Claiborne adjoining Peter Huffaker’s field, a compromise line between Hogan, Aaron David and William Jones, excepting 4 acres heretofore conveyed to said Huffaker and 2 acres donated by Hogan to the Baptist Church, including the meeting house and also a donation to the trustees of the Washington School, including the schoolhouse.  Wit William McCubbin, Thomas Taylor, Proved April term 1829, Claiborne “the within deed between William Hogan of McMinn Co., Tn to John Pace and Lazerous Dodson for 640 acres by William McCubbin and Thomas Taylor.” Book I-285.

Given these records, we know that Lazarus was living in Claiborne County in 1819 but that in 1812 he had patented land in Anderson County.

Lazarus died sometime between 1819 and 1826.

In 1826 in McMinn County, we fine the following entry: “Abner Lea and Others Obligation to William Dodson: State of Tennessee McMinn County. Know all men by these presents that the Abner Lea and Oliver Dodson and Eligha (sic) Dodson and William Dodson and Jessee Dodson and Lazrus Dodson and held and firmly bound in the penal sum of two thousand dollars which payment will and freely to be maid now(?) and each of us do bind our selves our heirs executor and administrators to the abounded signed sealed and delivered this day and date above written. This is our obligation is as such that has the above abound to appoint Abner Lea and Oliver Dodson to be the gardeans [guardians] of the estate of Lazarous Dodson dc’d also we authorize the said Abner Lea and Oliver Dodson to make to William Dodson a deed of Conveyeance to the part of land granted to the said William Dodson North East Quarter of Section 11 Township 5 Range first east of the meridian. Also that we confirm the sale made on the 13 day of May 1826 we also agree to give unto the heirs of David Dodson a certain piece or parcel of land designated to David Dodson by Lazarus Dodson dec’d be it further understood that this is to be there part and all that they are entitiled to by us, where unto we have set our hand and quill this 11 day of September 1826. Abner Lea, Oliver Dodson, Eligha Dodson, Lazarous Dodson, Jesse Dodson

Witnesses: Landford and Rhodes William Dodson

The land above is roughly the Cochran Cemetery area near Englewood in McMinn Co.  David Dodson who died on August 15, 1826 is buried in this Cemetery.  It appears that David and Lazarus Dodson may have died in very close proximity to each other relative to their death dates.  Poor Jane apparently lost a husband and a son within a very short time.

Abner Lea is certainly an interesting player in this scenario.  He is reported (although unverified) to have been married to a Mary Dodson.  Based on the heirs listed above, it strongly suggests that Mary was the daughter of Lazarus Sr.  His birth date is reported to be about 1770, so too young to be a brother-in-law to Lazarus and about the right age to have married his eldest daughter.  In 1810, Lazarus purchases land from Abner in Claiborne County.  If this is the Abner born in 1770, he was about 40 at this time.

In 1830, Jane Dodson, probably Lazarus widow, born 1760-1770 is living in McMinn County adjacent her son William Dodson and Fannie Dodson, David Dodson’s widow.

It was unclear what had become of the land Lazarus owned on Tipprell Road, but this deed signed in 1861 solves that mystery by referencing a sale in 1833 by Lazarus Dodson [Jr.].

1861, May 6 – Lazrous (sic) Dodson formerly of Claiborne Co, Tn. but now of Pulasky Co., Ky., to David C. Cotterell for $100 “to me the said Lazarous Dodson paid in the year 1833 having then sold to David Cotterell a tract of land on Gap Creek known as the Robert Chumbley land who had entered said land and sold and assigned said entry over to me and when the grant issued it came out in said Chumley’s name and afterwards was assigned by my request to said Cotterell”…beginning at a white oak two poles below Walker’s line, crossing Gap Creek, etc…his mark Lazarus Dodson. Witnesses: Lewis Chumbley, Andrew Chumbley.[8]

This rather odd suit brought in Hawkins County Tn. shows that by 1835 Lazarus Jr. was no longer in Tennessee.

May 7, 1835 – John A. McKinney vs David C. Cotterall, John Pace and Lazarus Dodson – the def John Pace and Lazarus Dodson are not residents of this state…ordered that they make appearance at Rogersville on the first Monday of Nov. next term or complainants bill will be taken pro confesso  and a copy of order to be published in the Abington newspaper and on motion of said complainant leave is given him to take depositions of the def, Dodson subject however to all just exceptions.

Nov. 3, 1835 – they failed to appear.

Sept. 18, 1837 – ordered by court that the clerk and master ascertain the amount of interest due on $87.50 being half the amount of the obligation executed by the def John Pace and Lazarus Dodson to the complainant.

Sept. 1837 – cause came for final hearing by responses made that Cottrell by an agreement made with the complainant pending this suit has assumed to pay the sum of $100 which at that time was half of the obligation and he was bound to do with as the agreement with Pace and further that Dodson is liable to pay the complainant the remaining half of said obligation with interest in the amount of $118.56 with interest from this date until paid.

dodson land poor valley ridge

Above, Lazarus Dodson’s land in Claiborne County, TN, looking towards Poor Valley Ridge.

dodson land tipprell road

Heading North on Tipprell road.  Lazarus’s land is on either side of the road here with Butcher Springs to the right, out of sight.

dodson land rr tracks

Gap Creek runs just over the railroad track and alongside it.  This would be the perfect place for a homestead.  It’s actually flat and farmable here between the ridge and the valley center.

The Cottrell Cemetery was established by David Cottrell, the man who bought the land from Lazarus in 1826.  The earliest marked burial is Moses Cottrell who died in 1857, but there appear to be many older unmarked graves and graves marked with fieldstones.  If Lazarus Sr. died in Claiborne County, he would be buried here, under the oldest trees.  This photo is taken from inside the cemetery, looking back over Lazarus’s land towards Tipprell Road.

cottrell cemetery

Lincoln Memorial University owns most of the adjacent land today.  The photo below overlooks Lazarus’s land towards the Southeast and you can see the “old Kentucky Road” in the photo in the upper left hand corner, which is 25E today.  At one time, Lazarus headed the crew that maintained the old Kentucky Road.

cottrell cem overlook laz land

A Civil War map shows us exactly where the homestead of David Cottrell was located, which of course had previously been the homestead of Lazarus Dodson.  The lane above his house is the road that at one time went to the Cemetery and on to the Kentucky Road.  Today, that lane no longer goes through to the cemetery, which is accessed through LMU.  Tipprell Road was then called Gap Creek Road and the Kentucky Road was labeled Tazewell Road on this map.  Patterson’s Smith shop looks to be the intersection of 25E and Back Valley Road today.

camp cottrell civil war map

The soldiers camped at Butcher Springs which is labeled “Camp Cottrell” on the map.

Children of Lazarus Dodson Sr.

Based on this following 1842 McMinn County court record entry referencing an earlier 1826 entry, we know the names of some of Lazarus’s children, at least those who were living and those who had died and left heirs.

Oct. 5, 1846 – Abner Lea and Oliver Dodson to the heirs of David Dodson decd in compliance with agreement made Sept 1826 – this is from the wills and estate book.

Sept. 11, 1826 – Abner Lea, Oliver, Elijah, William, Jesse and Lazarus Dodson to William Dotson, obligation they appointed Abner Lea and Oliver Dodson the 2 guardians of the estate of Lazarus Dodson decd to make deed to William Dodson, also agree to give land to heirs of David Dodson decd that was assigned to him by Lazarus Dodson decd; Oct. 3, 1842 – the ? of the witnesses Garrett E. Lankford and David Rhodes? is identified as they reside outside the state of Tn.

The children of Lazarus Dodson and Elizabeth, his wife, surname unknown, are:

  1. Lazarus Dodson Jr., born about 1795 in Hawkins Co., Tn. and died in Pulaksi Co., Ky. on October 5, 1861 where he was residing at the time of the 1860 census. He married first Elizabeth Campbell who died probably during the late 1830s, daughter of John and Jane Dobkins Campbell and married second to Rebecca Freeman in 1839.[9]

There is every indication that Lazarus Jr. went to Jackson Co., Alabama soon after his marriage to Elizabeth Campbell, but still held land in Claiborne Co.  In May 1819 Lazarus Dotson and Abner Lea both of Claiborne Co. sold to William Hogan of Lee Co., Va. by $5000 bond a tract of 640 acres.  This appears to be Lazarus Sr. preparing to leave the area, along with most of his children.  This deed was witnessed by Martin Beatty, William Jones and David Dodson.  The witness David Dodson may be the one who moved to McMinn Co. and is likely son David of Lazarus Dodson Sr.

Lazarus Jr. is out of Claiborne Co., during the years 1819 until September 1826.

In Sept. 1829, William Hogan living in McMinn Co., Tn. sold to Lazarus Dodson and John Pace of Claiborne Co., for $3500 a tract of 640 acres adjoining Peter Huffakers field, a compromise line between Hogan, Aaron Davis and William Jones, excepting four acres heretofore conveyed to the said Huffaker and two acres donated by Hogan to the Baptist Church, including the meeting house and also a donation to the Trustees of the Washington School, including the schoolhouse.  This has to be Lazarus Jr. since Lazarus Sr. is dead and appears, based on earlier and later deeds, to be the original land that Lazarus Sr. owned.

In 1827 Lazarus appears in the court minutes for the June session as the security for Andrew Chumbly in the case the State vs Andrew Chumbly.  Thereafter Lazarus appears in the court minutes, serving as juror in Sept 1827, sued for debt by Moses Ball in March 1828 (Ball awarded damages in Sept. 1828), ordered to a road jury in Dec 1829, serving as juror in March 1830, as constable in March 1831, after which his name disappears from court records until March 16, 1835 when John Hunt, sheriff and collector of public taxes lists Lazarus Dodson on his list of “persons being removed out of my county or insolvent so their poll tax cannot be collected for the year 1833 or 1834”.

It was unclear what had become of the land Lazarus owned on Tipprell Road, but this deed signed in 1861 referencing a sale in 1833 by Lazarus Dodson (Jr.) solved the mystery.

1861, May 6 – Lazrous Dodson formerly of Claiborne Co, Tn. but now of Pulasky Co., Ky. to David C. Cotterell for $100 “to me the said Lazarous Dodson paid in the year 1833 having then sold to David Cotterell a tract of land on Gap Creek known as the Robert Chumbley  land who had entered said land and sold and assigned said entry over to me and when the grant issued it came out in said Chumley’s name and afterwards was assigned by my request to said Cotterell”…beginning at a white oak two poles below Walker’s line, crossing Gap Creek, etc…his mark Lazarus Dodson Wit Lewis Chumbley, Andrew Chumbley.[10]

In 1835, we find the Hawkins County record that states he is not a resident of the State of Tennessee.

May 7, 1835 – John A. McKinney vs David C. Cotterall, John Pace and Lazarus Dodson – the def John Pace and Lazarus Dodson are not residents of this state…ord that they make appearance at Rogersville on the first Monday of Nov next term or complaintants bill will be taken pro confesso  and a copy of order to be published in the Abington newspaper and on motion of said complainant leave is given him to take depositions of the def, Dodson subject however to all just exceptions.

Nov. 3, 1835 – they failed to appear.

Sept. 18, 1837 – ord by court that the clerk and master ascertain the amount if interest due on $87.50 being half the amount of the obligation executed by the def John Pace and Lazarus Dodson to the complainant.

Sept. 1837 – cause came for final hearing by responses made that Cottrell by an agreement made with the compl pending this suit has assumed to pay the sum of $100 which at that time was half of the obligation and he was bound to do with as the foot of the agreement with Pace and further that Dodson is liable to pay the complainant the remaining half of said obligation with interest in the amount of $118.56 with interest from this date until paid.

However the name of Lazarus Dodson is on a list of free male inhabitants, 21 and upwards, of Claiborne in 1833.  The foregoing records suggest that Lazarus was living in Claiborne Co., in 1830, though he is not found there on census records for that year.  It is possible he lived in the household of another family, perhaps his in-laws.  These records also suggest that he left the county again for a few years, returning to marry his second wife, Rebecca Freeman, in 1839.

In 1841 Wiley Huffaker was appointed by the court of Claiborne Co. as guardian of the minor heirs of Lazarus Dodson and of Elizabeth Dodson, decd.  This was relative to the settlement of the estate of Elizabeth’s father, John Campbell, who died in 1838.  The children received land, slaves and cash from their grandfather’s estate which was first rented and then sold for their benefit.  The guardianship records continue until Dec. 1845 when the final settlement was made with Lasrus Dotson, the youngest heir, who would be Lazarus the third.

Lazarus and Rebecca Freeman Dodson have not been located on the 1850 census.  They are not on the census of Pulaski Co., KY that year.  The children of Lazarus and Elizabeth Campbell Dodson appear to have been raised after Elizabeth’s death by their Campbell grandparents.  Lazarus, their father, left the area but these children were raised in Claiborne County, married there and established homes.  The children’s names were taken from the records relative to the estate of John Campbell, their grandfather, as a guardian was appointed for them relative to their inheritance.  The children of Lazarus Dodson Jr. and Elizabeth Campbell were Ruthy, born 1820 in Alabama, married John Y. Estes in 1841 in Claiborne County, died in 1903 and buried in the Venable Cemetery in Little Sycamore.  John Campbell Dodson, born 1820-1821 in Alabama, married Barthenia Dobkins in 1839 in Claiborne County, died after 1860.  Nancy Ann Dodson born about 1821, married James S. Bray in 1840 in Claiborne Conty, died between 1852 and 1860.  Lazarus Dobkins Dodson born between 1822-1828 in Alabama, married Elizabeth H. Carpenter in 1845 in Claiborne County, died in 1885 in New Madrid County, Missouri.  Mary Dodson born in 1831 in Tennessee, died after 1860.

  1. Oliver Dodson – born August 31, 1794 in Hawkins Co., Tn. and died Dec. 8, 1875 in McMinn Co., Tn. married Elizabeth, surname unknown, born March 16, 1795 in Va. and died Aug. 7, 1883 in McMinn Co., Tn.  Both are buried in the Mt. Cumberland Cemetery, McMinn Co.

oliver dodson stone

The first record of this Oliver is in the Claiborne court minutes in August 1815 when he proved he killed a wolf in Claiborne Co.  On Jan. 16, 1820 he was relieved as road overseer of the Kentucky road from where Powell’s Valley Road intersects the same at Wallen’s field to the state line at Cumberland Gap.

At the August term 1820 he exhibited the scalp of a wolf he had killed in Claiborne in 1819.

In June 1824 he sued William Hogan for a debt and was awarded damages and costs.

Sometime before or after these events, he spent some time in Jackson Co., Al. where one of his sons Marcellus M. Dodson claimed to be born in 1819.  By 1830 Oliver was settled in McMinn Co, Tn. where he lived the remainder of his life.

A chancery suit filed in McMinn in 1893 involving the estate of Oliver Dodson gives us a list of his children and some of his grandchildren.  The suit, chancery case #1282, Lazarus Dodson vs Mary Jane Reynolds stated that all were nonresidents of McMInn Co. except for Lazarus who files for himself and as administrator of Oliver Dodson and Mary Jane Reynolds.  Some grandchildren lived in Knox Co., Tn. and the others lived in California, Texas, Missouri, Oregon, Montana, Georgia and other states.

  1. Jesse Dodson a son of Lazarus Sr. was born by 1781 or earlier and he was of age in March 1802 when he served as a juror in Claiborne Co., Tn. at the March term and also the June term of 1802, when he was designated as Jesse Dodson Jr.  This was no doubt for the purpose of distinguishing him from Rev. Jesse Dodson, a much older man who was also a resident of Claiborne Co. at this time.  Jesse, the son of Rev. Jesse, was born in 1791, thus being too young to serve as a juror in 1802.  At the June 1805 term of court Jesse Dodson again served as a juror and was designated “Little Jesse Dodson”.

Prior to this, Jesse Dodson Jr. was “assessed for 1 white poll and was included among those living within the Indian Boundary for the year of 1797 which the county court of Grainger released the sheriff from the collection of taxes.”  Apparently these people it had been determined were living beyond the treaty line on Indian land and were not within the jurisdiction of Grainger Co.[11]

Given this information, if this Jesse is the son of Lazarus, then he preceeded his father to Claiborne County by a couple of years and may well have settled on the land where Lazarus eventually lived, which was indeed, just inside the Indian Boundary and was Cherokee land.

Jesse Dodson and Mary Stubblefield Dodson joined the Big Spring Baptist church “by experience”  in March 1802.  They received letters of dismissal from the church in Nov. 1805, but Jesse returned his letter in May 1806.  Apparently in early 1807 Jesse got into a dispute with the church over a theological question which continued on through Sept. 1807 when the question was dismissed.  In Aug. 1808, Jesse was “excluded” from the church for “withholding from the Church”.  He is not again found in the records of Claiborne County.

On June 20, 1811, Jesse Dodson was licensed to trade with Indian tribes in Madison Co., Alabama.  Descendants of this man have the oral tradition that he was an Indian Trader.  He was said to be the oldest son of a large family of boys.  Once when the Indian trader returned from one trip and was preparing to leave on another, the father implored his older son to take along his younger brother.  The trader refused, saying the boy was so inexperienced that he would be killed by Indians.  The father was adamant and insisted, so the trader relented and took the boy along.  He has killed by Indians before the trader’s eyes.  From then on there were hard feelings between the Indian Trader and his father.  This is a tradition which may have grown with the telling over the generations, but there could be some grains of truth in the tale.  If would certainly be interesting to know for sure if Jesse the Indian Trader is the son of Lazarus Sr.

The land that became Jackson Co., Alabama was originally part of the Mississippi Territory and was occupied by the Cherokee until they gave it up by treaty on Feb. 27, 1819.  It is certainly possible that Jesse Dodson, Indian Trader of the Mississippi territory, was a son of Lazarus Dodson, Sr., who, himself was camping with the Indians in the winter of 1781/1782.  Indeed, he did appear to have a family of mostly boys and the name Raleigh is conspicuously absent from a list of descendants, perhaps indicating a death.

1819 is also the years that Lazarus sold his Claiborne County land and when several of his children apparently went to Alabama.

A Jesse Dodson was on the 1830 census of Jackson Co., Al. though the family statistics are puzzling.  The household consisted  of 2 males 5-10, 1 male 10-15, 1 male 20-30, 1 female under 5, 1 female 10-15, 1 female 30-40 and 1 female 50-60.  This would not be Jesse Dodson the Indian Trader unless he were away from home on the date of the census enumeration or unless the census taker made an error in recording the statistics.  We have no record of the children of this Jesse Dodson except for one son, who wound up in Texas. That son may also be the Jesse in Jackson County in 1830.

  1. David Dodson is not in the records of Claiborne Co except for the one time when he witnessed the deed, William Hogan to Lazarus Dotson and Abner Lea, in May 1819.  Apparently David was of age at this time when his father purchased the land for possibly the second time.

If it is the same David Dodson who later appeared in McMinn Co., Tn., then he was probably born between 1790 and 1800.  David Dodson (Dotson) died in McMinn Co. about 1826.  His widow was Fanny Dotson b 1790-1800.  The 1830 census of McMinn Co. with a household consisting of herself, 1 male 5-10, 1 male 10-15, 1 female under , 2 females 5-10.  Living next door was William Dotson whose household was 1 male under 5, 1 male 20-30, 1 female under 5, 1 female 5-10 and 1 female 20-30.  He was the administrator of the estate of David Dotson and seems a little old to be a son of David and Fanny, so was likely his brother instead.  It should also be pointed out that here a Jane Dotson, aged 50-70, born 1760-1770, living alone, also resided next to Fanny Dotson.  She was probably David’s mother, the widow of Lazarus Dodson Sr.

The estate of David Dodson was not settled until April 1846, presumably after all the children had come of age or married.  Apparently all this family left Tennessee before the 1850 census was taken.

  1. As mentioned, William lived adjacent David and Mary Dodson in McMinn County in 1830.  Also, a William L. Dotson was appointed one of the arbitrators between the administrators of the estates of Thomas and William Burch, decd, in June of 1834.  Thomas Burch died circa 1830 and had been the administrator of the estate of his father, William Burch, who died about 1828.  One of the daughters of William Burch was Mrs. Aaron David, apparently a former neighbor of Lazarus Dodson in Claiborne Co.  Mentioned in Thomas Burch’s estate is a note against the estate of William Burch, decd and an unidentified piece of land in Claiborne Co.  Aaron Davis was a member of Gap Creek Church, Claiborne Co. Tn. in 1818.

There were several William Dodsons in McMinn Co and it is not entirely possible to separate them without further records, but one of them was the son of Lazarus Sr.  William L. Dodson, believed to be the son of Lazarus, was born December 11, 1804 and died August 29, 1873.  He is buried in the Cochran Cemetery in McMinn County, shown below, along with Lazarus’s son David.  It’s likely that Mary, Lazarus Sr.’s widow, is buried here as well, given that she was living adjacent to David and William in 1830, and William owned the land on which the cemetery stood.  It’s possible that Lazarus is buried here as well.

cochran cemetery

  1. Elijah Dodson was a son of Lazarus Sr. as well. He is connected in the records of Claiborne with Martin and Jehu who are not listed as Lazarus’s sons.  Elijah was born in 1790 in Hawkins Co. according to information in the Oregon Donation land claims.  He died in Yamhill Co., Oregon in 1859.  His first wife was Mary, surname unknown, whom he married March 12, 1807 in “Clayborn Co, Tn.”.  His second wife was Elizabeth, surname unknown, who died in the Autumn of 1854.  They were married Sept. 1848 in Pilk Co., Oregon.

In the June 1805 term of court, Claiborne Co., Tn. Elijah along with Jehu was appointed as a road hand to work on a road of which Martin Dodson was overseer.  It was a segment of the Kentucky road from the top of Wallen’s Ridge to Blair’s Creek.  In Aug. 1814, Elijah proved a wolf scalp he had killed in 1814 and at the Aug term 1815 he served as a juror.  There are no records of Elijah in Claiborne beyond this date.

It is possible that Elijah eventually went to Henry Co., Ohio and Clay Co., Missouri before moving to Oregon where he made a claim to land in Yamhill Co. on which he lived from Feb. 1848 until his death.  It is believed that two of his sons were with him in Oregon.  The record stated that his first wife left 6 children.

DNA and the Dodson Family

According to the Dodson DNA Project at Family Tree DNA, several people are members who descend from Charles Dodson of Rappahannock Co., VA.  Charles, born in 1649, was the great-great-grandfather of Lazarus Dodson.  Several years ago when I checked, this group was simply labeled as R1b1a2, now R-M269.  Since then, it appears that several people have confirmed SNP tests, among them, R-P25 and R-L2.  How can that be?  Easy.  These are all sub-branches of haplogroup R and the men have tested at different levels.  R-P25 used to be R1b1 before the renaming event and R-L2 used to be R1b1a2a1a1b3c1, which illustrated perfectly one of the reasons why they are only using haplogroup SNP names today.

This confirms that the Dodson male line was European.

However, it can’t address whether or not the wife of Lazarus Sr. was Native or not.  To discover that, we need to test someone descended from Lazarus and his wife, Jane, through all females.  The current generation can be a male, because women pass their mitochondrial DNA to all of their children, but only females pass it on.

If you descend from Lazarus and his wife Jane through all females to the current generation I have a DNA testing scholarship for you!!!

I sent an e-mail to the Dodson DNA Project administrator asking if someone from Lazarus’s line has DNA tested, but I haven’t heard back.  I descend through Lazarus Sr. through Lazarus Jr. and his wife, Elizabeth Campbell, through daughter Ruthy.  Therefore, on the Dodson paternal side, “my paternal line” would have to be represented by one of the descendants of the sons of Lazarus Jr. or Lazarus Sr.  I’m hoping someone from these lines has already tested.  Otherwise, I have a scholarship for a male Dodson from Lazarus Dodson Jr. or Sr., or his father, Raleigh Dodson.

Honoring Lazarus Dodson, Patriot Ancestor

Lazarus Dodson (Sr.) was a patriot.  He served in the Revolutionary War.  He was paid on August 1783 for his service, along with his father, Raleigh Dodson.  Extensive research over the years has helped us to piece the lives of Raleigh and Lazarus together.  Lazarus died between 1819 and 1826, and his heirs sold his land on Tipprell Road, in Claiborne County, Tn. in 1833.  Most of his children were living in McMinn County at that time, and shortly thereafter, along with his widow.  When they moved there is uncertain.  Assuming Lazarus Sr. did not die in Jackson County, Alabama, Lazarus is either buried on his land in Claiborne County or in McMinn County.  Jackson County wills and probate records burned during the Civil War.

Given that Lazarus owned land in Claiborne, it’s most likely that he died on his land and is buried there, perhaps the first grave in the Cottrell Cemetery.  There are many older, unmarked graves in this cemetery.  Lazarus’s heirs sold this land to David C. Cottrell in 1826 and the land, until recently, has remained in the Cottrell family.

laz dodson marker

On June 11th, 2011, at 2 PM, the Dodson family descendants, the Cottrell family, and members of the local Joseph Martin Chapter of the SAR (Sons of the American Revolution), DAR (Daughters of the American Revolution) and staff from LMU gathered to honor Lazarus Dodson and set a long overdue headstone for him.

debbie and george frantz

Debbie Frantz, one of Lazarus descendants through the Estes family, and her husband George (below) were instrumental in arranging this ceremony.  George is an active SAR member as is Debbie in the DAR.  Debbie joined the DAR based on Lazarus’s service, so this was a particularly significant event for her.  Also representing the Dodson family was Roberta Estes, also descended from Lazarus through the Estes family, and Daryl Peters, descended from Lazarus’s father, Raleigh.

It was a beautiful but very hot day, near 100.  Daryl felt faint, and recalled the words of her grandmother, “women don’t sweat in the heat, they swoon”.  She and a few other people were swooning alright.

The Cottrell cemetery is now on Lincoln Memorial University property and LMU has agreed to take over maintenance of the cemetery.  This time in 2010, Daryl and I were there finding out the name of the man to contact about the cemetery.  This year, that gentleman, Keith Cottrell, who cared for the cemetery for years, has passed away, but many of the Cottrell relatives were present to help us celebrate.

debbie at dedication

It’s such a beautiful location.  You can see for 20 miles to the east if it’s not foggy.  The LMU campus is right there as well.  Lazarus’s heirs sold this land to David C. Cottrell in 1826 after Lazarus Dodson died.  It was an honor and a privilege to be able to provide a marker for his grave, overlooking his land.

debbie with laz marker

Debbie Frantz read about his life, his history, and what we have been able to piece together about him.  There were other speakers as well, and two ladies sang.  All in all, a lovely service, even if Lazarus’ death date is 10 years too early on his stone.

Below, Debbie and I have placed the “Descendants” wreath.  His three descendants present were me, Debbie and her grandson.  I wonder if Lazarus knows that nearly 200 years after his death, that his descendants are returning to set a stone and honor him.

debbie and bobbi

Wreaths were lain of honor of Lazarus Dodson by the TNSSAR, General Joseph Martin Chapter, Kentucky Path DAR Chapter, Martin Station SAR chapter VASSAR and the  Dodson Family Descendants.  Flags were flying high.

wreaths and stone

Frank Smith, Dean of Students at LMU  was the main speaker of the event and did a spectacular job.  His topic was about the significance of “the dash“.  That dash – the dash between the birth and death dates – the importance of the lives we live.  It’s the dash that we celebrate, not the beginning or the end.  And it’s the dash of Lazarus life that we have reconstructed to the best of our ability.  May all of our ancestors inspire the days of our dash.

frank smith lmu

The legacy of Lazarus Dodson will live on through his descendants and through the accomplishments of the students that will be given a chance to fulfill their dreams as educators of tomorrow through the Cottrell Endowment fund, which will give LMU a great legacy to be proud of.  Anyone who wishes to contribute may do so by writing a check to LMU and noting that it is a contribution for the Cottrell Endowment Fund.  They have committed to raise $25,000 as an endowed fund so a scholarship can be offered every year.  This was in exchange for LMU agreeing to maintain the cemetery in perpetuity.

laz descendants

After the service ended, we got to meet the Cottrell family with whom we’ve been communicating for months to document the cemetery.  The photo below is of Lazarus’ descendants and the Cottrell family together.

dodson cottrell

Below, the Cottrell family gathers at David Cottrell’s stone.  It seems so long ago, but David Cottrell probably knew Lazarus Dodson (Sr., the Patriot), certainly knew his son, Lazarus (Jr.), and lived in the home that Lazarus (Sr.) built, farmed his land and eventually, was buried alongside Lazarus.

cottrell with stone

Jim Rowland, one of the Cottrell family members mentioned that he knew where the old David Cottrell house had been located.   He’s about 60 or so and said it was torn down when he was a teenager, but it had been abandoned years before.  So off we went caravan style to see the location of the old house. Of course, we went via the roads, but in the old days, they would just have walked over the hill.  Too hot and too many snakes today.

at laz land

Here we are, all gathered in the road in front of the land that once held the cabin of Lazarus Dodson, Sr.  We’re by the bend in the road, by the word Cottrell, on the map inset below from the Civil War map of the 1860s.

laz land on map

After arriving, Jim pointed out the location of the old house and barns.  At the bend in Tipprell Road, the house used to stand where the dead tree is today (photo below), and the barn was in the clearing to the right.  This was rather unusual land, because it’s almost flat here.

The barn had been located to the right of the clump of trees, in the little clearing just as it starts up the little hill.  This location is also shown on the Civil War map and it is the only homestead on Tipprell road at that time.  As the crow flies, the cemetery is just behind the house and over the hill.  There was originally a road that connected the two sites, and the road still exists, but has been abandoned and is blocked at both ends today.

laz house location

Lazarus was also a member of the Gap Creek Church and helped to found it as well.  It was on his 640 acres that he received for his Revolutionary War service, located on Gap Creek.  The Church backs up to Gap Creek has been rebuilt several times, but surely some of the original lurks beneath the surface.

???????????????????????????????

Before we left, we had seen where Lazarus was buried, where he lived, where he worshipped and the creek on his land that quenched the thirst of his family and his animals. We have seen the Indian lands and Butcher Springs where the local story says that long hunters were ambushed by Indians.  Lazarus’ land is steeped in history.

???????????????????????????????

We were glad to get back to the hotel and air conditioning.  We drove back via Tipprell Road, a little one lane road (sometimes stretched to two lanes, but you have to stop to pass).  This would have been the road Lazarus took to the village of Cumberland Gap, “above” his place on the mountain.  Even today, after being paved, it is extremely quiet and peaceful.  We stopped and shut the car off and just listened to the sound of Gap Creek tumbling down the mountain, the birds….and nothing else except for the occasional rustle of the leaves.  How beautiful and peaceful this land is today.

As fate would have it, a Tennessee artist, Tamara Hogshead painted Gap Creek and donated the painting to a nonprofit group for their fundraising auction.  I bid on, and won, that painting which I love dearly and graces my home today.  What are the chances of finding this painting and then discovering that it is of Gap Creek, the creek that ran through Lazarus property?

hogshead gap creek

However, it wasn’t always serene.  We know that this is the place where battles of the Civil War were fought as well as bloody battles between Indians and migrating European settlers.  Today, it is peaceful and stunningly, almost hauntingly, serenely,  beautiful.  This is the Appalachia our ancestors loved, where Lazarus lived, the roads he trod, and the land where we return to honor him and to visit the landscapes of our ancestors.

???????????????????????????????

If no one ever thanked you Lazarus, for your service to your country, or told you they were proud of you, proud to be your descendant, let me do it now.  All of your descendants thank you, those who were able to be present in 2011, and those not.  Those who searched for and documented the meaningful events of your life, those moments between the dash, and those who will, in the future read about them.  We are all here because of you, and we live in a free country.  That freedom is thanks to you, your father, and the other Patriots.  You will never be forgotten, nor will your service to your country.  We have set a memorial stone for you to insure that others can visit you, on your land, in the future.  Hopefully future generations will come, sit a spell in this magical location, ponder the dash, yours and theirs, learn a little about your life, and find a piece of their heritage on the tract known as Butcher Springs, just below Cumberland Gap.

Thank you, from your descendants!

laz wreath

Footnotes:

[1] Page 124 – 798 (681)

[2] [Lazarus Dodson 300 ac and Joseph Beard 400 ac (warrant number mentioned twice) – on warrant list; for grant to L Dodson see file 523 in Sullivan Co; warrant issued Jan 19 1782 by John Adair, warrant assigned Aug 12 1788 by Rawleigh Dodson to Lazarus Dodson (William Smith witness); 300 ac in grant (survey not in shuck, see Sullivan Co file 531); Carter’s entry 1014 in same shuck; grant 539 issued Nov 26 1789.

[3] Page 64 – 427 (311) March 16 (or 15) [RJE – looks to be several surveys under this same number] Grant 534 issued Feb 13 1791

[4] Hawkins deeds 1-94, 2-3184-65, 4-66, 6-196, 6-264. 1800, March 29 – Lazarus Dodson of Claiborne Co and Johnathan Ling of Hawkins $900 for tract in Hawkins on White Horse Fork (also White Run Fork in next deed which is exactly the same except dated March 29 1804.  Actually this is White Thorne Fork) of Bent Creek being same place where said Dodson formerly lived, adj fence of Walker, being 575 acres of land as set out.  Wit William Paine, JP, M_Myres.  Reg Nov 21 1804

[5] See Claiborne deed B-316, D-4, E-366 one of which might refered to Lazarus Jr.  Deeds were also recorded in H-291 and L-23 but these books are missing from the courthouse.

[6] Decatur County was a short lived county crated from territory of Madison and Jackson Counties.

[7] Ack Aug term 1819 by William Hogan  Reg Oct 14, 1819 book E-366.

[8] Ack May 6, 1861 by Lazarus Dodson by appearance before James Allcorn, Clerk of Court in Pulaksi Co., Ky.  Registered Oct. 13, 1870 Claiborne Co.

[9] Claiborne marriages 2-10.

[10] Ack May 6, 1861 by Lazarus Dodson by appearance before James Allcorn, Clerk of Court in Pulaksi Co., Ky.  Registered Oct. 13, 1870 Claiborne Co.

[11] Claiborne was not formed until 1801.

______________________________________________________________

Disclosure

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase the price you pay but helps me to keep the lights on and this informational blog free for everyone. Please click on the links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Transfers

Genealogy Services

Genealogy Research

Haplogroups, SNPs and Family Group Confusion

The transition at Family Tree DNA from the old haplogroup naming convention to the new SNP-only naming convention has generated a great deal of confusion.  It’s like surgery – had to be done – but it has been painful.

I’ve received several questions, many that are similar, so I’d like to attempt to resolve some of the confusing points here.

First, just a little background.

Ancient History

Remember, in 2008, when Michael Hammer et al rewrote the Y tree?  If you do, then count yourself as an old-timer.  Names such as R1b1c became R1b1a2.  E3a became E1b1a and E3b became E1b1b1.  We thought we were all going to die.  But we didn’t – and now, if I hadn’t just told you, you wouldn’t even be able to remember the previous name of R1b1a2.

Why did this happen?  Because when you have a step-wise tree where each step is given a number and letter, like this, you have no room for expansion.

R

R1

R1a

R1a1

Each of these haplogroup names is assigned a SNP, and when a new SNP is discovered between R and R1, for example, the name R1 gets assigned to the new SNP and everyone downstream gets renamed and/or a new SNP assigned.  If you think this is confusing, it is and was – terribly so.  In fact, as testimony to this, the last version of the FTDNA tree, the ISOGG tree and the tree used by 23andMe are entirely out of sync with each other.

With the shift from about 800 SNPs to 12,000 SNPs with the Geno2.0 chip, it was definitely time to redo and rethink how haplogroup names are assigned.  What seemed initially like a great idea turned out not to be when the magnitude of the number of SNPs that actually exist was realized.  In reality, they needed to be obsoleted, but the familiar cadence of the letter number path will forever be gone – with the exception of the fact that the SNP is prefaced with the haplogroup name.  We will no longer have our signposts, sadly, but our signposts were becoming overwhelmingly long.  Here’s one example I copied from the ISOGG tree.  R1b1a2a1a1c2b2a1a1b2a1a – seriously – I can’t remember that.

So, today, and forever more, R1b1a2 will be R-M269.  It will not be shifted or “become” anything else.  Moving a SNP to a new location becomes painless, because it will not affect anything upstream or downstream.

However, as you get use to this new beast, you’re going to want to refer to “what something was” before.  You’ll find that articles, papers and who knows what else will refer to the haplogroup name – and you’ll need a conversion reference.

Here’s a link to that reference.  I don’t know about you, but I copied this and created a .pdf file in case this reference disappears – not that that ever happens in the electronic world.

Why the Confusion?

Within projects, men with the same surname now have different haplogroups assigned, and the SNP names look entirely different.  Before, if most of the surname group was R1b1a2, and one person had SNP tested at a deeper level and showed R1b1a2a1a1b4, it was easy to tell by looking that R1b1a2a1a1b4 fell underneath R1b1a2, and was a subclade.  Today, with the new tree, everyone that was R1b1a2 is now shown as R-M269 and the lone R1b1a2a1a1b4 person is shown as R-L21.  You can’t tell by looking if R-L21 is a subclade of R-M269 or the other way around.  And another few SNP tests at different levels into the mix, and you have one confused administrator.

One thing hasn’t changed.  Notice the haplogroup I-M253 individual in the purple group below.  There is a note that their parentage is uncertain.  Given the completely different haplogroup – this individual does not fit into any groups of Estes males biologically.  So completely different haplogroups are still exclusive, meaning you can tell at a glance that these folks do not share a common ancestor, even though their genealogy says that they should.

estes project cropped

Ok, got that now?  Good, because it gets more confusing.

Family Tree DNA did not do a one to one conversion, meaning they did not create a conversion table where R1b1a2=R-M269.  They did an entirely new prediction routine.  This makes sense, because they don’t hard code the haplogroup – it’s fluid and based on either a hard and fast SNP test or a prediction routine. This also allows for easy future improvements, and they utilize 37 markers for haplogroup predictions now instead of just 12, in most cases.

Unfortunately, or fortunately, the prediction routine produces different results for people within the same family group, based on STR marker results and how many STRs are tested.

What this means is that different people in the same family line will have different haplogroup predictions, as you can see in the groups above of individuals all descended from one male, Abraham Estes.

This isn’t wrong, as in incorrect, but it is confusing, especially when you’re used to seeing everyone who has not been SNP tested have a matching haplogroup within families.

Enter the Terminal SNP

The terminal SNP is your SNP that is furthest down the tree based on the SNPs that you have tested.  That second part is really important – based on the SNPs that you have tested.

When you’re looking at your matches, you can see their terminal SNP in the column below to the right, but what you can’t tell is if they have tested for any downstream SNPs and were found negative.

Estes match cropped

For example, if you are tested positive for R-M269 (formerly R1b1a2) and someone else that you match is R-L21, which is downstream of R-M269 – this does not exclude them as valid matches, UNLESS the first R-M269+ gentleman has actually tested for R-L21 and is negative.  You, of course, have no way of knowing this without asking the other participant.

Also, testing “negative” is a bit subjective, because there are known no-calls in the Geno 2.0 results – so if the Geno 2.0 result did not include the terminal haplogroup you expected, and the outcome is truly important to you, meaning family defining – have that defining SNP, if it’s absent in the Geno 2.0 raw data results, tested individually through regular Sanger sequencing – meaning purchase it separately through Family Tree DNA.  A non-positive result in the Geno 2.0 results is typically interpreted to mean negative, but that is not always the case.  In most situations, if everything else matches, meaning surname, STRs and other SNPs, it’s not necessary to test the SNP separately – but it is available if you need to know, positively.

Secondly, the terminal SNP on the new Family Tree DNA haplotree and in your results, if you have taken the Big Y, the Walk Through the Y or purchased individuals SNPs, may be different.  Why, and how would you know?

The why is because Family Tree DNA has synced to the Geno 2.0 tree at this point, and there have been many new SNPs discovered since the Geno 2.0 tree was developed in 2012.  The ISOGG tree is more current, but keep in mind that it is a provisional tree.  However, you still need to have a way to determine your terminal SNP beyond the Geno 2.0 criteria if you have had advanced testing.

There were originally some tools created by individuals to help with this dilemma, but both tools appear to no longer work.  Kitty Cooper blogged about this, and was apparently recently successful, but I was not.  I downloaded the updated version of the Big Y Chromosome extension that I wrote about and was using the Morley tree but that no longer functions either.  Let’s just say that the word frustrated doesn’t even begin to apply….

My suggestion is to work closely with your haplogroup and surname project administrator(s).  Many of the administrators have put together provisional charts and the haplogroup project pages are grouped by SNP groupings with suggestions for additional relevant testing.

The U106 project is a great example of proactive administrators.  Individual participants are clearly categorized and the categories suggest an appropriate “next step.”  Looking at their home page, the administrators make themselves readily available to project members for consulting about how to proceed.

u106 project

Yes, all of this change is a bit fuzzy right now, but give it a bit of time and the fog will clear.  It did in 2008 and we all survived.

Tree Updates

Family Tree DNA has committed to at least one more tree update this year, and let’s hope that it includes all of the SNPs in the reference data base they are using for the Big Y.

I’ll be talking about Big Y comparisons in a future article.

______________________________________________________________

Disclosure

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase the price you pay but helps me to keep the lights on and this informational blog free for everyone. Please click on the links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Transfers

Genealogy Services

Genealogy Research

Stories about Surname Origins

How many of us have seen stories about the purported origin of our family surname?  Until now, I never thought about DNA perhaps holding the answer to whether these origin stories might be accurate – but in the case of Campbell, it seems DNA might provide a clue if not an answer.Clan Campbell current coat of arms

Ron, on my blog, posted the following query:

“There was a story about Campbells I read in Reader’s Digest probably 40 years ago. They said a Medieval family named Fairfield fell out of favor with English royalty. Many fled the country and translated their name to the native language. Those who went to France became “Beau Champ” while those who fled to Italy became “Campo Bello”, each meaning “Fair Field.”

Some years later they were allowed back home where they Anglicized their names. Beau Champs became “Beachams” and Campo Bellos became Campbells. Now the Fairfields, the Beau Champs, the Campo Bellos, the Beachams, and the Campbells are all related. Hmmm. I wonder if that story is true?”

I had seen these stories myself, years ago, but I had entirely forgotten about them.  Thanks Ron, for jogging my memory.

From this oral history, it looks like Campbell should also match these or similar surnames:

  • Beacham
  • Fairfield
  • Beauchamp
  • Campo Bellos

The first thing I’ll do is to check my own family lines of Y DNA.  My Campbell lines match that of the Campbell clan from Inverary, so if this is a true story, the Inverary line should match at least some of these surnames.

At 12 markers, where the most matches would be found there are no matches to any of these surnames.  There were also none at higher match levels. While this doesn’t entirely disprove the story, it certainly doesn’t lend any credibility to it either.

Do you have any surname stories in your family that DNA could help to prove or disprove?  Even if you don’t have someone to test, you might discover that your line has already been tested by checking the surname projects at Family Tree DNA or by checking by surname at www.ysearch.com.

______________________________________________________________

Disclosure

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase the price you pay but helps me to keep the lights on and this informational blog free for everyone. Please click on the links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Transfers

Genealogy Services

Genealogy Research

Inverary Castle and the Clan Campbell

Scotland sunrise

Please notice that this is a sunrise photo.  Why was I up this early?  Because I fell asleep again right after dinner.  Sunrise is not something I normally experience, but I was certainly glad I was awake for this one.  This is the sunrise over Scotland, the Highlands in the distance.  This is the home of my ancestors, the Campbell and Younger families, and all of the Mc names in my tree.  McDowell, McKee, McMahon, McNeil and McSpaden.

We woke up this morning to rain.  Shortly after that, we were treated to something else.  Bagpipes.  I opened the door to the cabin on the cruise ship and looked outside.  Standing alone, in the rain, on the dock, was a single bagpipe player.  The mournful sound of the bagpipes took me back in time, to another time and place, in the remote Highlands, where another bagpipe player played in the rain.  That sound, like no other, stirred my soul.

Scotland bagpiper

Welcome home.  That’s the same thing my cousin, the Duke of Argyl who is the Campbell heir and carries the Campbell surname, said to me today.  And that is how it felt here in the Scottish Highlands, the lands my ancestors left some nearly 300 years ago.  Their blood in me rejoiced.  I now understand why Mary Herrell said she wanted to be put up on the mountain ledge when she died and her soul taken back to Ireland.  There is a part of you that never leaves your homeland.

Scotland highlands

The Highlands are magnificent in their stark beauty.

Scotland highlands 2

I remember one time Daryl, my cousin, and I were driving through some remote area of Claiborne County, Tennessee trying to figure out where George Campbell lived (below) and she said to me that the terrain reminded her of the highlands of Scotland.

Geo Campbell Land 008 crpped

Now I understand why the Scotch-Irish were so attracted to the Appalachian mountain highlands, the frontiers and why they were not afraid of battles.  Life here was a battle, even when no one was attacking.

Driving up into the Highlands, we stopped at the summit of the gap that is called “Rest and Be Thankful.”  It’s named appropriately, believe me, as shown below.  I suspect it was probably the horses and draft animals that were most thankful for the rest at the top.

OLYMPUS DIGITAL CAMERA

At Rest and Be Thankful, travelers have long welcomed the chance to draw their breath and enjoy the view as they cross the summit at 860 feet on the road that leads from Loch Long to Loch Awe via Glen Croe.

In the beginning, of course there wasn’t a road at all.  There was just a track, a path, made by generations of travelers, and beaten out by herds of black cattle being taken by drovers from Argyll to the Trysts and cattle markets of the Lowlands.  The making of the road, in any sense that we would now recognize it, had to wait until the 18th century. Some work was done in the 1730s on the roads in Argyll by the local government agencies, the Commissioners of Supply.  However, the real impetus for the road building came after the 1715 and 1719 Jacobite Uprisings.  General George Wade was sent to the Highlands to examine the military situation.  His report made a number of recommendations, including the construction of forts at various points and the development of a network of roads to link them.

In 1743 it was decided to construct 44 miles of military road from Dumbarton to Inveraray, via Loch Lomond-side, Tarbet, Arrochar, Glen Croe and thus down to Loch Fyne.  Major Caulfield, Wade’s Inspector of roads and successor as mastermind of the Highland roads network, was ordered to survey the route.  Work started that summer, although the progress was interrupted by the outbreak of the 1745 Jacobite Uprising.

Argyll and Inveraray, its capital was strongly Hanoverian, pro-government, firmly under the control of the Duke of Argyll, a Campbell of course, one of the leading figures in the government of Scotland.  So what military purpose was to be served by this road?  It was hardly likely that a detachment from the garrison at Dumbarton would be marched to Loch Fyne to put down an insurrection in the peaceful glens of Argyll.

Two possible reasons exist for the high priority given to this road.  The first may have been to allow the pro-government forces that could be raised in Argyll – and indeed a regiment of the Argyll Militia fought in the Culloden campaign – to move swiftly from Loch Fyne to wherever they might be needed. The other reason was perhaps less straight forward, but perhaps more plausible – to provide a conveniently smooth road to and from the Lowlands for the Duke of Argyll.  The connection between the road and the Duke was emphasised by Caulfield – when the road was nearly finished, money was running out and there was a danger that a bridge at Inveraray could not be completed,  Caulfield wrote “this will hurt a great man for the bridge is at his door,” as indeed it was, being barely a mile from Inveraray Castle, the Duke’s seat.

After Culloden, work recommenced, and by 1748 troops from the 24th Regiment – later the South Wales Borderers – had made the road over the summit of Glen Croe and erected a stone seat with the legend “Rest And Be Thankful,” shown below.  Completion of the road to Inveraray was achieved by 1749.

Rest and be thankful

On the way to Inverary Castle today, we visited Loch Lomond, the largest inland lake.  The village of Luss sits on the edge of the lake and is quite beautiful.

OLYMPUS DIGITAL CAMERA

This village looks a bit like a storybook.

Inverary is on Loch Fyne, on the other side of “Rest and Be Thankful.”

Lochs are the same things as fjords but are called lochs here.  They are tidal, in some cases, very tidal.  The scenery is incomparable, although I fully understand why my ancestors left.  Land was not available and with the religious and political changes and upheaval, it was leave or perish.  This lands lush, stark beauty must have lived in their souls for the rest of their lives, and their descendants as well as a distant memory. Loch Lomond below.

Loch Lomond

The Castle of Inverary itself was built in the early 1700s, probably just before my ancestors left for America.  They would have known this castle, most likely, but would have thought of it as the “new castle.”  Earlier castles are in ruins and located elsewhere, but this castle was built of the remains of a fort built in the 1400s, so our ancestors probably knew that fort quite well.  This castle is very beautiful however, and it sooths my soul to be someplace my ancestors walked and lived for centuries, maybe millennia.  Just down the loch a ways is Campbeltown too.  Three guesses how it received its name.

Inverary castle

The entrance to the castle spans what is today, a dry mote.

Inverary entrance

Inverary estate

Castle armory room below.  My ancestors likely used these arms.

Inverary armour room

As luck would have it, the Duke himself was in the gift shop signing books.  He’s my cousin, many times removed, and he was most gracious – inviting me back anytime.   Although I’m sure though he didn’t mean to stay in the family area of the castle:)  That’s the two of us in the photo below.  It was so much fun to meet him.  He is very much a gentleman and he personally cut fabric for me – yes – I bought Campbell tartan plaid wool.  I have no idea what I’ll do with it, but certainly something interesting.

For anyone who is interested in the history of the castle, the Duke and Duchess have had the castle interior professionally photographed and have written a book about the history of the Castle and the Campbell Clan.  I highly recommend this book.  You can purchase it online along with other Clan Campbell items.

Me and the Duke

Loch Fyne, below, at Inverary Castle, which is located just on the other side of the bridge.

Loch Fine

This area is tidal….the water comes and goes throughout the day revealing mud flats from time to time.  This is of course the bridge being referenced as at the end of the “Rest and Be Thankful” road which leads to Inverary Castle.

Loch Fine bridge

We ate in a lovely Pub at Loch Fyne where the placemats were slate tiles.

slate placemat

The roofs here are slate too.  When you have this much moisture, you don’t build anything out of wood.

slate roofs

I also understand the woolen industry now too.  Everything here needed to be wool.  Wool was warm, even when wet, which is everyday, all day long, and everyone needed wool breaches.

In one of our stops, we did find a lovely woolen mill where the local wool is made into charming and useful items, all wool, of course.

I so wanted a pair of those warm woolen kilt socks!!!  I had been cold for days.  I bought a pair of heavy knitted woolen socks for myself and my daughter and in the middle of January, she sent me an e-mail with this photo and the title “Best Socks Ever.”  Yep, those Scots knew what they were doing.  I would love to have a few more pairs of these!  Sounds like a good reason to return:)

wool socks

We made our way back through quaint villages to the boat.  We took a ferry across the Frith of Clyde, the estuary of the River Clyde as it enters the sea.  The bus would be driven on to the ferry and the entire bus transported across the frith.  I decided that I needed a Dramamine when I discovered that was the plan.  The bus is bad enough and the boat is bad enough, but a bus on a boat. Dramamine is terrible to chew!!

Bagpipes, now more than one lonely wet person, bade us farewell.  A lovely sendoff and so fitting.

Scotland bagpipers

Our towel guy tonight, Nessie of course, wears a Campbell tartan scarf in front of a Celtic cross ornament and a book about the Clan Campbell.

Nessie towel guy

Clan Campbell

In traditional genealogies of the Clan Campbell, its origins are placed amongst the ancient Britons of Strathclyde.  However the earliest Campbell in written records is Gillespie who is recorded in 1263.  Early grants to Gillespie and his relations were almost all in east-central Scotland.  However the family’s connection with Argyll came some generations before when a Campbell married the heiress of the O’Duines and she brought with her the Lordship of Loch Awe.  Because of this the early clan name was Clan O’Duine and this was later supplanted by the style Clan Diarmid.  This name came from a fancied connection to Diarmid the Boar, a great hero from early Celtic mythology.

The original seat of the Clan Campbell was either Innis Chonnell Castle on Loch Awe or Caisteal na Nigheann Ruaidh on Loch Avich. The clan’s power soon spread throughout Argyll.  However, at first the Campbells were under the domination of the Lords of Lorne, chiefs of Clan MacDougall.  The MacDougalls killed the Campbell chief Cailean Mór (Colin Campbell) in 1296.  All of the subsequent chiefs of Clan Campbell have taken MaCailein Mor as their Gaelic patronymic.

Between 1200 and 1500 the Campbells emerged as one of the most powerful families in Scotland, dominant in Argyll and capable of wielding a wider influence and authority from Edinburgh to the Hebrides and western Highlands.

The Clan Campbell DNA Project at Family Tree DNA has 613 members, including a couple different family members of my Campbell line.  The Duke of Argyl, a Campbell himself, of course, provided a Campbell timeline on the Inverary Castle website.

You know those “two brothers” stories?  Everyone has them.  Well, there really were two brothers, John and George Campbell born in the 1770s and found in Claiborne County, TN in the early 1800s.  We believe their father was Charles Campbell of Hawkins County, Tennessee, but unfortunately, the deed signed by his children to sell his property after his death was never filed in the clerk’s office, so we don’t’ know who signed.  Subsequent deeds only refer to the unfiled deed and the “Campbell heirs.”  Heartbreaking.  Enough to make you want to pull your hair out!

We know from a deed signed during Charles’ lifetime that he did have sons John and George, and we know that the man whose daughters the two Campbell sons married lived not far in Hawkins County from Charles Campbell who died in early 1825.  John and George Campbell married Jane and Elizabeth Dobkins, respectively, about 1800 or just before, daughters of Jacob Dobkins and Dorcas Johnson.

According to the Campbell DNA project and other associated documents, trees and webpages provided by Kevin Campbell, the project administrator, it appears that my line does indeed descend from the Campbell Clan of Argyl.  We are grouped in group 30, which includes the Campbell family of Argyl.

Clan Campbell DNA cropped2

I may never know exactly how I’m related to the Duke of Argyl, but thanks to DNA, my very generous Campbell cousins who tested, and the Campbell DNA project, I know for sure that I am.  And thanks to the generosity of the family of the Duke of Argyl sharing Inverary Castle with the rest of us, I can visit my homelands.  It makes a difference when you know for sure that you are visiting your family ancestral land.  Standing literally where your ancestors stood 500 years ago, and further, back into “time out of mind.”

Colin Campbell

Colin Campbell of Glenorchy who died in 1480.

Archibald Campbell

Archibald Campbell, 1st Marquess of Argyll, who led the Campbell forces in 1645 at the Battle of Inverlochy.

Campbell black watch

The Black Watch, or Campbell Tartan.

If you’d like to hear “The Campbell’s Are Coming” on pipes and drums, click here.  In the historical tidbit category, this was played by the Union as the Iron Brigade marched down the Emmitsburg Road on their way to McPherson’s Ridge at Gettysburg.

“The Campbell’s Are Coming” is the pipe hymn of the Clan Campbell, composed in 1715 by a local piper, inspired by a wedding.  The Gaelic name of the tune is “Baile Ionaraora” or “the town of Inverary.”  For more info and to hear the bagpipe version, click here.

Clan Campbell current coat of arms

Coat of Arms of the current head of the Clan Campbell, the 13th Duke of Argyll.

______________________________________________________________

Disclosure

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase the price you pay but helps me to keep the lights on and this informational blog free for everyone. Please click on the links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Transfers

Genealogy Services

Genealogy Research

2014 Y Tree Released by Family Tree DNA

On April 25th, DNA Day and Arbor Day, Family Tree DNA updated and released their 2014 Y haplotree created in partnership with the Genographic project.  This has been a massive project, expanding the tree from about 850 SNPs to over 6200, of which about 1200 are “terminal,” meaning the end of a branch, and the rest being proven to be duplicates.

If you’re a newbie, this would be a good place perhaps to read about what a haplogroup is and the new Y naming convention which replaces the well-known group names like R1b1a2 with the SNP shorthand version of the same haplogroup name, R-M269.  From this time forward, the haplogroups will be known by their SNP names and the longhand version is obsolete, although you will always see it in older documents, articles and papers.  In fact, this entire tree has been made possible by SNP testing by both academic organizations and consumers.  To understand the difference between regular STR marker testing and SNP testing, click here.

I’ve divided this article into two parts.  The first part is the “what did they do and why” part and the second is the “what does it mean to you” portion.

This tree update has been widely anticipated for some time now.  We knew that Family Tree DNA was calibrating the tree in partnership with the Genographic project, but we didn’t know what else would be included until the tree was released.

What Did Family Tree DNA Do, and Why?

Janine Cloud, the liaison at Family Tree DNA for Project Administrators has provided some information as to the big picture.

“First, we’re committed to the next iteration of the tree and it will be more comprehensive, but we’re going to be really careful about the data we use from other sources. It HAS to be from raw data, not interpreted data. Second, I’ve italicized what I think is really the mission statement for all the work that’s been done on this tree and that will be done in the future.”

Janine interviewed Elliott Greenspan of Family Tree DNA about the new tree, and here are some of the salient points from that discussion.

“This year we’re committing to launching another tree. This tree will be more comprehensive, utilizing data from external sources: known Sanger data, as well as data such as Big Y, and if we have direct access to the raw data to make the proof (from large companies, such as the Chromo2) or a publication, or something of that nature. That is our intention that it be added into the data.

We’re definitely committed to update at least once per year. Our intention is to use data from other sources, as well as any SNPs we can, but it must be well-vetted. NGS and SNP technology inherently has errors. You must curate for those errors otherwise you’re just putting slop out to customers. There are some SNPs that may bind to the X chromosome that you didn’t know. There are some low coverages that you didn’t know.

With technology such as this you’re able to overcome the urge to test only what you’re likely to be positive for, and instead use the shotgun method and test everything. This allows us to make the discovery that SNPs are not nearly as stable as we thought, and they have a larger potential use in that sense.

Not only does the raw data need to be vetted but it needs to make sense.  Using Geno 2.0, I only accepted samples that had the highest call rate, not just because it was the best quality but because it was the most data. I don’t want to be looking at data where I’m missing potential information A, or I may become confused by potential information B.  That is something that will bog us down. When you’re looking at large data sets, I’d much rather throw out 20% of them because they’re going to take 90% of the time than to do my best to get 1 extra SNP on the tree or 1 extra branch modified, that is not worth all of our time and effort. What is, is figuring out what the broader scope of people are, because that is how you break down origins. Figuring one single branch for one group of three people is not truly interesting until it’s 50 people, because 50 people is a population. Three people may be a family unit.  You have to have enough people to determine relevance. That’s why using large datasets and using complete datasets are very, very important.

I want it to be the most accurate tree it can be, but I also want it to be interesting. That’s the key. Historical relevance is what we’re to discover. Anthropological relevance. It’s not just who has the largest tree, it’s who can make the most sense out of what you have is important.”

Thanks to both Janine and Elliott for providing this information.

What is Provided in the Update?

The genetic genealogy community was hopeful that the new 2014 tree would be comprehensive, meaning that it would include not only the Genographic SNPs, but ones from Walk the Y, perhaps some Chromo2, Full Genomes results and the Big Y.  Perhaps we were being overly optimistic, especially given the huge influx of new SNPs, the SNP tsunami as we call it, over the past few months.  Family Tree DNA clearly had to put a stake in the sand and draw the line someplace.  So, what is actually included, how did they select the SNPs for the new tree and how does this integrate with the Genographic information?  This information was provided by Family Tree DNA.

Family Tree DNA created the 2014 Y-DNA Haplotree in partnership with the National Geographic Genographic Project using the proprietary GenoChip. Launched publicly in late 2012, the chip tests approximately 10,000 Y-DNA SNPs that had not, at the time, been phylogenetically classified.

The team used the first 50,000 male samples with the highest quality results to determine SNP positions. Using only tests with the highest possible “call rate” meant more available data, since those samples had the highest percentage of SNPs that produced results, or “calls.”

In some cases, SNPs that were on the 2010 Y-DNA Haplotree didn’t work well on the GenoChip, so the team used Sanger sequencing on anonymous samples to test those SNPs and to confirm ambiguous locations.

For example, if it wasn’t clear if a clade was a brother (parallel) clade, or a downstream clade, they tested for it.

The scope of the project did not include going farther than SNPs currently on the GenoChip in order to base the tree on the most data available at the time, with the cutoff for inclusion being about November of 2013.

Where data were clearly missing or underrepresented, the team curated additional data from the chip where it was available in later samples. For example, there were very few Haplogroup M samples in the original dataset of 50,000, so to ensure coverage, the team went through eligible Geno 2.0 samples submitted after November, 2013, to pull additional Haplogroup M data. That additional research was not necessary on, for example, the robust Haplogroup R dataset, for which they had a significant number of samples.

Family Tree DNA, again in partnership with the Genographic Project, is committed to releasing at least one update to the tree this year. The next iteration will be more comprehensive, including data from external sources such as known Sanger data, Big Y testing, and publications. If the team gets direct access to raw data from other large companies’ tests, then that information will be included as well. We are also committed to at least one update per year in the future.

Known SNPs will not intentionally be renamed. Their original names will be used since they represent the original discoverers of the SNP. If there are two names, one will be chosen to be displayed and the additional name will be available in the additional data, but the team is taking care not to make synonymous SNPs seems as if they are two separate SNPs. Some examples of that may exist initially, but as more SNPs are vetted, and as the team learns more, those examples will be removed.

In addition, positions or markers within STRs, as they are discovered, or large insertion/deletion events inside homopolymers, potentially may also be curated from additional data because the event cannot accurately be proven. A homopolymer is a sequence of identical bases, such as AAAAAAAAA or TTTTTTTTT. In such cases it’s impossible to tell which of the bases the insertion is, or if/where one was deleted. With technology such as Next Generation Sequencing, trying to get SNPs in regions such as STRs or homopolymers doesn’t make sense because we’re discovering non-ambiguous SNPs that define the same branches, so we can use the non-ambiguous SNPs instead.

Some SNPs from the 2010 tree have been intentionally removed. In some cases, those were SNPs for which the team never saw a positive result, so while it may be a legitimate SNP, even haplogroup defining, it was outside of the current scope of the tree. In other cases, the SNP was found in so many locations that it could cause the orientation of the tree to be drawn in more than one way. If the SNP could legitimately be positioned in more than one haplogroup, the team deemed that SNP to not be haplogroup defining, but rather a high polymorphic location.

To that end, SNPs no longer have .1, .2, or .3 designations. For example, J-L147.1 is simply J-L147, and I-147.2 is simply I-147.  Those SNPs are positioned in the same place, but back-end programming will assign the appropriate haplogroup using other available information such as additional SNPs tested or haplogroup origins listed. If other SNPs have been tested and can unambiguously prove the location of the multi-locus SNP for the sample, then that data is used. If not, matching haplogroup origin information is used.

We will also move to shorthand haplogroup designations exclusively. Since we’re committing to at least one iteration of the tree per year, using longhand that could change with each update would be too confusing.  For example, Haplogroup O used to have three branches: O1, O2, and O3. A SNP was discovered that combined O1 and O2, so they became O1a and O1b.

There are over 1200 branches on the 2014 Y Haplogroup tree, as compared to about 400 on the 2010 tree. Those branches contain over 6200 SNPs, so we’ve chosen to display select SNPs as “active” with an adjacent “More” button to show the synonymous SNPs if you choose.

In addition to the Family Tree DNA updates, any sample tested with the Genographic Project’s Geno 2.0 DNA Ancestry Kit, then transferred to FTDNA will automatically be re-synched on the Geno side. The Genographic Project is currently integrating the new data into their system and will announce on their website when the process is complete in the coming weeks.  At that time, all Geno 2.0 participants’ results will be updated accordingly and will be accessible via the Genographic Project website.

In summary:

  • Created in partnership with National Geographic’s Genographic Project
  • Used GenoChip containing ~10,000 previously unclassified Y-SNPs
  • Some of those SNPs came from Walk Through the Y and the 1000 Genome Project
  • Used first 50,000 high-quality male Geno 2.0 samples
  • Verified positions from 2010 YCC by Sanger sequencing additional anonymous samples
  • Filled in data on rare haplogroups using later Geno 2.0 samples

Statistics

  • Expanded from approximately 400 to over 1200 terminal branches
  • Increased from around 850 SNPs to over 6200 SNPs
  • Cut-off date for inclusion for most haplogroups was November 2013

Total number of SNPs broken down by haplogroup

A 406 DE 16 IJ 29 LT 12 P 81
B 69 E 1028 IJK 2 M 17 Q 198
BT 8 F 90 J 707 N 168 R 724
C 371 G 401 K 11 NO 16 S 5
CT 64 H 18 K(xLT) 1 O 936 T 148
D 208 I 455 L 129

myFTDNA Interface

  • Existing customers receive free update to predictions and confirmed branches based on existing SNP test results.
  • Haplogroup badge updated if new terminal branch is available
  • Updated haplotree design displays new SNPs and branches for your haplogroup
  • Branch names now listed in shorthand using terminal SNPs
  • For SNPs with more than one name, in most cases the original name for SNP was used, with synonymous SNPs listed when you click “More…”
  • No longer using SNP names with .1, .2, .3 suffixes. Back-end programming will place SNP in correct haplogroup using available data.
  • SNPs recommended for additional testing are pre-populated in the cart for your convenience. Just click to remove those you don’t want to test.
  • SNPs recommended for additional testing are based on 37-marker haplogroup origins data where possible, 25- or 12-marker data where 37 markers weren’t available.
  • Once you’ve tested additional SNPs, that information will be used to automatically recommend additional SNPs for you if they’re available.
  • If you remove those prepopulated SNPs from the cart, but want to re-add them, just refresh your page or close the page and return.
  • Only one SNP per branch can be ordered at one time – synonymous SNPs can possibly ordered from the Advanced Orders section on the Upgrade Order page.
  • Tests taken have moved to the bottom of the haplogroup page.

Coming attractions

  • Group Administrator Pages will have longhand removed.
  • At least one update to the tree to be released this year.
  • Update will include: data from Big Y, relevant publications, other companies’ tests from raw data.
  • We’ll set up a system for those who have tested with other big data companies to contribute their raw data file to future versions of the tree.
  • We’re committed to releasing at least one update per year.
  • The Genographic Project is currently integrating the new data into their system and will announce on their website when the process is complete in the coming weeks. At that time, all Geno 2.0 participants’ results will be updated accordingly and accessible via the Genographic Project website.

What Does This Mean to You?

Your Badge

On your welcome page, your badges are listed.  Your badge previously would have included the longhand form of the haplogroup, such as R1b1a2, but now it shows R-M269.

2014 y 1

Please note that badges are not yet showing on all participants pages.  If yours aren’t yet showing, clicking on the Haplotree and SNP page under the YDNA option on the blue options bar where your more detailed information is shown, below.

Your Haplogroup Name

Your haplogroup is now noted only as the SNP designation, R-M269, not the older longhand names.

2014 y 2 v2

Haplogroup R is a huge haplogroup, so you’ll need to scroll down to see your confirmed or predicted haplogroup, shown in green below.

2014 y 3

Redesigned Page

The redesigned haplotree page includes an option to order SNPs downstream of your confirmed or predicted haplogroup.  This refines your haplogroup and helps isolate your branch on the tree.  You may or may not want to do this.  In some cases, this does help your genealogy, especially in cases where you’re dealing with haplogroup R.  For the most part, haplogroups are more historical in nature.  For example, they will help you determine whether your ancestors are Native American, African, Anglo Saxon or maybe Viking.  Haplogroups help us reach back before the advent of surnames.

The new page shows which SNPs are available for you to order from the SNPs on the tree today, shown above, in blue to the right of the SNP branch.

SNPs not on the Tree

Not all known SNPs are on the tree.  Like I said, a line in the sand had to be drawn.  There are SNPs, many recently discovered, that are not on the tree.

To put this in perspective, the new tree incorporates 6200 SNPs (up from 850), but the Big Y “pool” of known SNPs against which Family Tree DNA is comparing those results was 36,562 when the first results were initially released at the end of February.

If you have taken advanced SNP testing, such as the Walk the Y, the Big Y, or tested individual SNPs, your terminal SNP may not be on the tree, which means that your terminal SNP shown on your page, such as R-M269 above, MAY NOT BE ACCURATE in light of that testing.  Why?  Because these newly discovered SNPs are not yet on the tree. This only affects people who have done advanced testing which means it does not affect most people.

Ordering SNPs

You can order relevant SNPs for your haplogroup on the tree by clicking on the “Add” button beside the SNP.

You can order SNPs not on the tree by clicking on the “Advanced Order Form” link available at the bottom of the haplotree page.

2014 y 4

If you’re not sure of what you want to do, or why, you might want to touch bases with your project administrators.  Depending on your testing goal, it might be much more advantageous, both scientifically and financially, for you to take either the Geno2 test or the Big Y.

At this point, in light of some of the issues with the new release, I would suggest maybe holding tight for a bit in terms of ordering new SNPs unless you’re positive that your haplogroup is correct and that the SNP selection you want to order would actually be beneficial to you.

Words of Caution

This are some bugs in this massive update.  You might want to check your haplogroup assignment to be sure it is reflected accurately based on any SNP testing you have had done, of course, excepting the very advanced tests mentioned above.

If you discover something that is inaccurate or questionable, please notify Family Tree DNA.  This is especially relevant for project administrators who are familiar with family groups and know that people who are in the same surname group should share a common base haplogroup, although some people who have taken further SNP testing will be shown with a downstream haplogroup, further down that particular branch of the tree.

What kind of result might you find suspicious or questionable?  For example, if in your surname project, your matching surname cousins are all listed at R-M269 and you were too previously, but now you’re suddenly in a different haplogroup, like E, there is clearly an error.

Any suspected or confirmed errors should be reported to Family Tree DNA.

They have made it very easy by providing a “Feedback” button on the top of the page and there is a “Y tree” option in the dropdown box.

2014 y 5

For administrators providing reports that involve more than one participant, please send to Groups@familytreedna.com and include the kit numbers, the participants names and the nature of the issue.

Additional Information

Family Tree DNA provides a free webinar that can be viewed about the 2014 Y Tree release.  You can see all of the webinars that are archived and available for viewing at:  https://www.familytreedna.com/learn/ftdna/webinars/

What’s Next?

The Genographic Project is in the process of updating to the same tree so their results can be synchronized with the 2014 tree.  A date for this has not yet been released.

Family Tree DNA has committed to at least one more update this year.

I know that this update was massive and required extensive reprogramming that affected almost every aspect of their webpage.  If you think about it, nearly every page had to be updated from the main page to the order page.  The tree is the backbone of everything.  I want to thank the Family Tree DNA and Genograpic combined team for their efforts and Bennett Greenspan for making sure this did happen, just as he committed to do in November at the last conference.

Like everyone else, I want everything NOW, not tomorrow.  We’re all passionate about this hobby – although I think it is more of a life mission for many – and surpassed hobby status long ago.

I know there are issues with the tree and they frustrate me, like everyone else.  Those issues will be resolved.  Family Tree DNA is actively working on reported issues and many have already been fixed.

There is some amount of disappointment in the genetic genealogy community about the SNPs not included on the tree, especially the SNPs recently discovered in advanced tests like the Big Y.  Other trees, like the ISOGG tree, do in fact reflect many of these newly discovered SNPs.

There are a couple of major differences.  First, ISOGG has an virtual army of volunteers who are focused on maintaining this tree.  We are all very lucky that they do, and that Alice Fairhurst coordinates this effort and has done so now for many years.  I would be lost without the ISOGG tree.

However, when a change is made to the ISOGG tree, and there have been thousands of changes, adds and moves over the years, nothing else is affected.  No one’s personal page, no one’s personal tree, no projects, no maps, no matches and no order pages.  ISOGG has no “responsibility” to anyone – in other words – it’s widely known and accepted that they are a volunteer organization without clients.

Family Tree DNA, on the other hand has half a million (or so) paying customers.  Tree changes have a huge domino ripple effect there – not only on their customers’ personal pages, but to their entire website, projects, support and orders.  A change at Family Tree DNA is much more significant than on the ISOGG page – not to mention – they don’t have the same army of volunteers and they have to rely on the raw science, not interpretation, as they said in the information they provided.  A tree update at Family Tree DNA is a very different animal than updating a stand-alone tree, especially considering their collaboration with various scientific organizations, including the National Geographic Society.

I commend Family Tree DNA for this update and thank them for the update and the educational materials.  I’m also glad to see that they do indeed rely only on science, not interpretation.  Frustrating to the genetic genealogist in me?  Sure.  But in the long run, it’s worth it to be sure the results are accurate.

Could this release have been smoother and more accurate?  Certainly.  Hopefully this is the big speed bump and future releases will be much more graceful.  It’s easy to see why there aren’t any other companies providing this type of comprehensive testing.  It’s gone from an easy 12 marker “do we match” scenario to the forefront of pioneering population genetics.  And all within a decade.  It’s amazing that any company can keep up.

______________________________________________________________

Disclosure

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase the price you pay but helps me to keep the lights on and this informational blog free for everyone. Please click on the links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Transfers

Genealogy Services

Genealogy Research

 

Wales, Conway Castle and High Winds

One should not go to sleep at 8:30 at night.  Because one wakes up at, let’s say, about 4:30 in the morning.  However, I laid down to read and the Carnival Legend was gently rocking and the next thing I knew, I was sound asleep. No evening entertainment or shows for me that night! Too bad, because the shows are wonderful and the cost is included. This shot below is from the show on the Carnival Splendor. We sailed on her before. I can’t show you the photo from this cruise, because, obviously, I slept through the shows….all of them. Yep, every last one.

Carnival Splendor Show

The other disturbing thing that is happening is that I’m now dreaming in that cockney British accent. I’ve never had this happen before, except when I lived in France. And I’ve only been here for 10 days or so. And the problem is that I don’t understand about half of what they are saying.  You see, after 300 years or so, British and American English are only distant cousins, kind of like we are to them.  And when you take into consideration that English is a second language in most of London, you’re dealing with cockney British English spoken by a non-native speaker – and then you understand about every 4th word.  So I understand only part of what people are saying in my dreams.  But that’s OK, I just make up the rest to be what I want it to be!  It’s my dream, after all.

Yesterday was a “sea day” meaning we didn’t dock in any ports. We won’t discuss this particular sea day because the word of the day was “Dramamine.” High winds forced us to change the schedule as well, and we’re going to miss one of the ports I was very excited to visit, because the tour we had booked was going to go right past the last of the McDowell family whose DNA my McDowell family matches, in Northern Ireland, on King’s Moss Road in Ballyrobert, Newtown. When you’re trying to use DNA to find your family location in the old country, this is indeed the Holy Grail. I’m so close but yet so far.

The problem is that it’s storming and there are extremely high seas, 25-30 foot waves. To put this in perspective, waves are generally no more than 6-8 feet. The port of Belfast has closed and we’ve been rerouted. We’re going, guess where…. back to Liverpool which is adjacent Chester. In fact, Chester is one of the shore excursion options. Instead, Jim and I chose to go to Conway Castle in North Wales.

Try as I might, I could not find any ancestor who was from Wales. There is one rumored to be from Wales, one Peter Johnson supposedly born 1715 in Wales and who died in 1790 in Allegheny Co., PA. He married Mary Polly Philips. I also have a Thomas Rice, which is a Welsh name, rumored to be from Shirenewton, Monmouthshire Wales, born about 1660, but no proof. This probably means I just haven’t hunted deep enough, because someone has to be Welsh.

There is a Wales Cymru DNA project at Family Tree DNA for people who can prove their ancestors back to Wales. This project is for both Yline and mitochondrial DNA. Due to the importance of determining the genetic profile of the indigenous populations of the British Isles, The Wales/Cymru DNA Project collects the DNA haplotypes of as many persons as possible who can trace their Y chromosome and/or mtDNA lines to Wales; the reasoning by many researchers being that there was less genetic replacement from invaders in Wales than elsewhere, excepting small inaccessable islands and similar locales.

Having said that, tradition among historians holds that the Celts retreated as far west into Wales as possible to escape invading populations. The Wales DNA project seeks to determine the validity of that theory. Their long term goal is to identify the haplotypes of the Welsh Princes. They provide a nice list of resources on this page if you have Welsh ancestry.

I decided to dig a bit deeper. In the Rice DNA project, kit number 4086 is reportedly a descendant of Matthew Rice, who is probably the brother of my Joseph Rice (c1700-1766) who was married to Rachel. If this is the case, and if the project grouping is correct in terms of family association, then my Matthew could have been Welsh.

So, I’m going to enjoy Wales assuming that I do indeed have Welsh ancestry and I simply haven’t proven it yet! If nothing else, I’m Welsh for a day because today, we’re visiting Conwy Castle.

Conwy Castle

Conwy Castle (Welsh: Castell Conwy) is a medieval fortification in Conwy, on the north coast of Wales. It was built by Edward I, during his conquest of Wales, between 1283 and 1289. Constructed as part of a wider project to create the walled town of Conwy, the combined defenses cost around £15,000, a huge sum for the period.

Conwy Castle mockup

This rendition shows the town within the walls as it would have appeared in the 1200s when initially build.

Over the next few centuries, the castle played an important part in several wars. It withstood the siege of Madog ap Llywelyn in the winter of 1294–95, acted as a temporary haven for Richard II in 1399 and was held for several months by forces loyal to Owain Glyndŵr in 1401.

Following the outbreak of the English Civil War in 1642, the castle was held by forces loyal to Charles I, holding out until 1646 when it surrendered to the Parliamentary armies. In the aftermath the castle was partially slighted by Parliament to prevent it being used in any further revolt, and was finally completely ruined in 1665 when its remaining iron and lead was stripped and sold off.

UNESCO considers Conwy to be one of “the finest examples of late 13th century and early 14th century military architecture in Europe”, and it is classed as a World Heritage site. The rectangular castle is built from local and imported stone and occupies a coastal ridge, originally overlooking an important crossing point over the River Conwy. Divided into an Inner and an Outer Ward, it is defended by eight large towers and two barbicans, with a postern gate leading down to the river, allowing the castle to be resupplied from the sea.

Conwy Castle exterior

The castle walls are absolutely massive.

OLYMPUS DIGITAL CAMERA

Unfortunately, Conway Castle is so large that I couldn’t get far enough away from it to get a good photo.  The outside of it is at least 2-3 stories below the inside courtyard and castle main area where I was.  The entire city was walled with a total of 21 towers and everything inside was part of the castle complex.  The magnitude of this castle was simply astounding.  It only took 4-5 years to complete.  It was built in the 1200s and is in ruins today.  But they are beautiful ruins.  The 8 castle towers and walls are all still intact.

Conwy paraphet

Conwy view

Conwy arches

When we were in Chester, I wanted to walk the old city walls, but we didn’t get a chance to do that.  Here, I walked the walls, around the castle, but the wall walk at one time extended entirely around the city.

You can see in the photo below that the castle walls seamlessly transition into the city walls.

Conwy City walls

This photo gives you an idea of how large that wall actually is, as compared to the cars.

Conwy walls back

Conwy skyline

In addition, I climbed the very small, very tight circular stone stairs to the top of one of the paraphets, or towers.  The views were utterly stunning.  I’m glad I did it, but I won’t be doing it again.  Between the height, the wind and the motion sickness from the circular stairs, once is enough. The next few photos are from the paraphet walk.

Conwy Jim

And of course, there are sheep. There are more sheep in Wales than people.

Conwy sheep

The city as seen from the towers.

Conwy village

And the countryside.

Conwy countryside

And the harbour.

Conwy harbor

Sometimes rainy days make for stunning photos!

Conwy harbor 2

Can you imagine maneuvering a bus through the city wall? Well, our driver knew that there was only one wall entrance that had a 3 inch clearance, side to side, and that is the only entrance the bus would fit through. And it was not this entrance.

Conwy road

After leaving Conway Castle, we went and had lunch in Betws-y-Ceod, a resort area in North Wales.  We had lunch at the historic Village Inn where they served us lamb.  We had no choice in this matter.  So, I ate lamb.  I still don’t like lamb, but I did try it.  For dessert, we had strawberries and cream, which made up for the lamb.

By then, it was pouring but we had 45 minutes or so of shopping time, so we visited some local shops which is, of course, what tourists do.

There is a very quaint local courting custom.  Young men interested in young women would carve wooden spoons with highly decorated handles and give them as a gift to the object of their desire.  They are called love spoons.  The number of balls on the handle tells her how many children he wants to have, inferring of course, with her.  This custom is excusive only to Wales. You can see many examples in the LoveSpoon store, of course.

love spoons

We also tried Welsh cakes and had a little dessert picnic.  Welsh cakes are a cross between pancakes, cookies and biscuits.  They were different.  We tried three kinds, one berry of some sort, one with sugar and cinnamon – how could that be bad?  But the third was called “savory” and to me it tasted like it had lamb in it.  Not my favorite.

Welsh cakes

Back on our bus and back to our floating home. The great thing about cruises is that you only unpack once and the cruise line worries about logistics. All you have to worry about is getting yourself back on that bus at the appointed time.

Tonight at dinner, we left port just as we were seated.  As we moved out to sea, we saw a wind farm in the sea, followed by an oil rig.

Wind farm at sea

Oil rig

You can see how hard the wind was blowing because the flame at the top is burning sideways, not straight up.  Very rough sea tonight.  I’m ready for bed and I’m wearing my sea bands to bed tonight with my fingers crossed.

Our towel guy tonight was a scorpion and had a tea towel of the flag of Wales, a sweater I bought, the giveaway book about Wales and two love spoons on his fingers.

Towel guy Wales

______________________________________________________________

Disclosure

I receive a small contribution when you click on some of the links to vendors in my articles. This does NOT increase the price you pay but helps me to keep the lights on and this informational blog free for everyone. Please click on the links in the articles or to the vendors below if you are purchasing products or DNA testing.

Thank you so much.

DNA Purchases and Free Transfers

Genealogy Services

Genealogy Research