Embracing 3rd and 4th cousin DNA matches!

I’ve often heard people who are interested in their family history say they won’t take a DNA test because they’re not interested in connecting with 3rd or 4th cousins: they just want to know about their own ancestors. This is a misunderstanding of how DNA matching works. The point is that we share 2x great grandparents with our 3rd cousins, and we share 3x great grandparents with our 4th cousins. Unless our ancestors have lived extraordinarily long lives and reproduced the following generation at scandalously early ages, none of those ancestors of ours will still be living. However, if we can connect with other people who are descended from them via siblings of our direct line, we might learn new stories about them that were passed down their line but not ours. We might even find new photographs or documents, or a family bible. If we’re not absolutely sure that we have the correct parentage assigned to one of our forbears, the DNA will prove that and help us to work out who the correct person is. If all this seems like an impossible puzzle – well, yes, there is a lot to learn. Sometimes the connection is very clear; other times we have to work hard to find it. But it’s worth it.

In my own family research I’ve used DNA to home in on birthplaces in Ireland (from where my ancestors migrated before the advent of civil registration and before the big fire in Dublin); to verify a hypothesis I had about a mysterious ancestor; to help several other people to find missing grandfathers; and to connect with people who had photos. However, this post is not about my own ancestry.

Today I’m going to share with you how I used three unknown DNA matches of a person whose DNA I manage:

  • to identify beyond doubt the birthplace in modern-day Belarus of certain named individuals;
  • to identify beyond doubt two family members, brothers of direct ancestors, about whom very little was known.

All this is published here with that person’s permission. 

The case is complicated because it involves several countries, constantly changing national boundaries, two continents, several languages and two types of script: the Latin script we use in English, and the Cyrillic script used in Russia and Belarus. It involves people of Jewish heritage, where the high incidence of endogamy can skew estimates of cousin matches, making them appear closer than they really are. At no time did I make contact with any of the DNA matches. All research was carried out using only the sparse information they each had on the trees linked to their DNA results as my starting point.

The research relates to Marks Chirklin, his wife Fanny Chirklin née Rudow and one of their daughters, who I will not name here. 

The Chirklins immigrated to the UK early in the twentieth century, and were believed by their living descendants to have come from Poland or Lithuania.  In the 1911 census their country of birth is recorded as ‘Russia’.  None of this is incompatible, since boundaries changed regularly.  However, the Russian Empire was huge, so this documentary evidence did nothing to permit a homing in on the actual birthplace of the family.

In all UK records the name of this family is written as Chirklin or Cherklin.  This too is not without complications.  For any of our ancestors originating in a non-English speaking country, names may have been anglicised.  If they have come from a place where an alphabet other than our Latin script is used, the complications are even greater.  Often in such cases we lack a letter to write the sounds required to pronounce the original word.  In the case of immigrants this will impact on names of people and also place-names.  As we shall see, both of these were an issue in this research.

Using records and DNA matches to locate a birthplace for the Chirklins

In the 1921 UK census Marks and Fanny gave their birthplaces as Vilna.  Vilnius is the capital of Lithuania, but ‘Vilna’ is a government district, or ‘Oblast’. Although it did include Vilnius, it was much larger, including territories in present-day Belarus as well as Lithuania.  At the time the family came to the UK it was part of the Russian Empire. 

However, in the same census, the now-married daughter of Marks and Fanny gave her birthplace as ‘Dishna, Russia’.  This was problematic for the linguistic reasons outlined above.  Just writing this down involved transforming the sounds of her homeland and somehow finding a way to make sense of these sounds in English language and script.  So ‘Dishna’ was unlikely to be entirely correct, but it was a starting point; and since the rest of the family were born in the Vilna Oblast, this narrowed down the search for a town within Vilna with a name that sounded like ‘Dishna’.

I had already noticed that the Chirklin descendant whose DNA I manage had two reasonably close DNA matches with names in their trees similar to Chirklin.  Specifically, those names were Tsirklin and Tzerklin.  One was in the US; the other location not known. Both were showing with a probability of a 2nd-3rd cousin match.  For reasons outlined above, this estimated match level needed to be taken with a pinch of salt to some extent.  Even so, a DNA match stretching back far enough to be just out of reach as far as our UK and US records are concerned seemed likely – perhaps a 3rd-4th cousin match.

Should my linking of Chirklin, Cherklin, Tsirklin and Tzerklin require any explanation, it’s easily explained by the linguistic conversion of the sounds of one language family to another.  There is often even a difference between the way surnames were recorded upon immigration into the US and immigration into the UK.  (For example the name pronounced phonetically in the US as Pet-Raow-Skee is both spelled and pronounced differently in the UK: Piotrowski and Pee-Ot-Roff-Skee.) In a new language which doesn’t have an equivalent sound, ‘Tz’ could easily be the same sound as ‘Ch’. 

I had no way of knowing how these Tsirklins and Tzerklins were connected to the Chirklins.  The family trees linked to the DNA results were sparse, and it seemed clear that any connection would be back in the old homeland.  What I could see, however, was that the earliest known Tsirklin was from ‘Volintsi’ in Belarus, and the earliest known Tzerklin from Polatsk in Belarus.  These towns are about 35 km apart – but Polatsk is a much larger town and could easily have been a ‘shorthand’ for “I come from a tiny settlement called XXX about 10 miles from Polatsk”.

Locating these on the map I then searched for ‘Dishna, Belarus’ and found it: Dzisna – just a short distance south of Volyntsy.  By combining the documentary evidence of the placename given on the 1921 census with the location of these reasonably close DNA matches with the same family name, we finally had a definite birthplace for this Chirklin daughter and possibly for her siblings and parents too.

Google map showing the locations of three towns in Belarus.  The towns are Volyntsy, Dzisna and Polatsk.  The place names are recorded on the map with Latin script and Cyrillic script.
Location of Volyntsy, Dzisna and Polatsk in Belarus. Google Maps.

There are various spellings of this town’s name.  I have come across Disna, Dysna, Dzisna (Polish), but also in the Russian Cyrillic script Дзісна in Belarusian (which is pronounced Dzisna, as in the Polish pronunciation), and Дисна in Russian, which would be pronounced as Disna. Today, the boundaries of the Oblasts have also changed.  Dzisna is now within the Molodechno Oblast of Belarus. 

Using records and a third DNA match to identify and locate two missing family members

In addition to the known siblings living with the family at the time of the censuses, the Chirklins were thought to have another son: Nathan.  The descendants of the family knew of him only from a reference on a memorial headstone.  He was generally assumed to have gone to America, but no one knew for sure.  One of the descendants found a new document via Ancestry.com, and thought this could be him.

The new document was a ship’s manifest, dated 1907, including the passenger Nachman Zirklin.  Could ‘Zirklin’ be yet another anglicisation of Chirklin/ Cherklin/ Tzerklin/ Tsirklin?  And could ‘Nachman’ be the missing person thought to be Nathan?

Entry for Nachman Zirklin on the Shop's manifest for his ship from Liverpool to Philadelphia, PA, arriving March 1907. The entry gives name, occupation of watchmaker, last residence of London and the name and address of an uncle with whom Nachman will be starying upon arrival.
Nachman Zirklin, Ship’s Manifest entry, March 1907, Liverpool to Philadelpia PA.
CLICK FOR BIGGER

According to the ship’s manifest, Nachman Zirklin was 21 years old in 1907 – the right sort of age to be the missing brother.  He was departing from Liverpool, bound for Philadelphia, PA, and his last place of residence was London, where he had lived for eight months.  The immigration date of the Chirklins into the UK was not known but was likely to be around this time.  Therefore if this Nachman was the correct person, this record would also give us a likely immigration date for the whole family of around July 1906.  Nachman’s birthplace is noted as ‘Lisna’, which is very similar to Disna and an easy mistake to make if the clerk has never heard of the place and has noted down what they thought the person with very little English has said, or indeed if that information is being copied from another document where the upper round stroke of the ‘D’ was very faint.

There was one other very interesting piece of information.  Nachman was heading for New York City, where he would be staying with his uncle, a Mr Rudoff.  Rudoff, of course, is a phonetic spelling of Rudow, which is, as we knew, the maiden name of Fanny, the mother of the Chirklin family in England.  It looked very much like Fanny had a brother in New York, and that her son Nathan/ Nachman was going to stay with him.

As luck would have it, there was another DNA match, estimated 2nd-3rd cousin, to a US-based person with Rudow ancestry.  Again the linked tree was very sparse, and while acknowledging the obvious surname link between that family and Fanny back in London, there were no clues at all as to how they might fit in.  The earliest known Rudow ancestor on that tree was a Solomon, with an estimated birth year of 1866 and a birthplace of ‘Russia’.  However, when I went now to look at this DNA match again I saw that the Ancestry algorithms had been hard at work, and had found a link between ancestors that this match didn’t even have on her tree and two people on the one I had created for the person whose DNA I manage.  The two people were Fanny’s parents.  I had been given their names by family members and knew nothing more about them.  However, Ancestry was suggesting these people were also the parents of Solomon Rudow in New York.  If correct, this would make Solomon Fanny’s brother, and therefore the uncle of Nathan/ Nachman. 

We should never simply accept hints on Ancestry or any other genealogy website.  Hints are suggestions, nothing more.  It’s up to us to prove or disprove them.  So I now set about researching Solomon Rudow of New York.  Through a series of US Federal and NY State censuses I tracked him from his arrival circa 1902 to his death in 1956.  On the 1906 US directory I found his address: right next door to that given the following year by Nathan/ Nachman as the address of his uncle Mr Rudoff, on the ship’s manifest.  We have our man!  This Solomon Rudow is indeed the uncle of Nathan Zirklin/ Chirklin, younger brother of Fanny née Rudow; and Nathan is the son of Marks and Fanny.

Extract from the family tree chart, showing all the people who have been named in the text of this blogpost.

This post has looked at how DNA was used to confirm birthplaces, plus connections to two missing people who had emigrated to the USA. In view of the lack of information amongst the living descendants of the Chirklin family, I couldn’t have proven any of this without the DNA.

While in this post we have been looking from England to find out more about people who went to America, in my next post I’ll be staying with Solomon Rudow and Nachman/ Nathan Zirklin/ Chirklin, and investigating what might be learned about the family back in England and their origins in Dzisna/ modern day Belarus by looking at the US records about the two of them.

So your DNA results are in! What now?

I first took a DNA test to help with my family research about eight years ago.  Although I’d done a little reading and understood the basics, I had no idea how to make practical use of the DNA.  In the absence of knowledge, tools and even significant tester databases my modus operandi was to contact my matches and ask if they would be prepared to work with me at trying to locate where, on our trees, we matched.  Some never replied but even with the ones who did it wasn’t a success, resulting in zero confirmed matches.  None of us really had any idea how to actually use the new information the DNA itself provided.  Now, when I look back at the people I contacted I can ‘read’ the DNA info regarding our match better and I can see why we never found / in some cases never will find our common ancestors.

Since then, there have been lots of developments:

  • Many more people have tested
  • People have emerged as ‘authorities’, writing books, blogs, and producing helpful videos
  • Facebook groups have formed where people help each other and again, some have emerged as leaders and experts
  • Ancestry and MyHeritage have developed their own tests aimed specifically at genealogists, and working increasingly seamlessly with the tree-building functions of their websites
  • Other people and companies have created tools for us to use alongside our DNA results to help us get the most from them

Eventually I decided to get on top of this DNA thing, challenging myself to see how far I could progress within one year.  I tested again, this time with Ancestry (so I could access their large database), I read books, watched videos, learned how to use some of the new tools, and I joined Facebook groups, asking questions when stuck.  More than two years have passed and I’m still learning, but these days I can usually work on a match without ever needing to contact the other person, just using information on the database.  Of course there remains much to learn.  I still read, seek out videos on specific learning points, and if I’m stuck on something specific there is always someone on the Facebook groups with apparently encyclopaedic knowledge on matters DNA.

Earlier this year I published five blogposts (starting here) about how we can use DNA to develop our trees.  They were aimed at the complete beginner with no knowledge, and in particular at readers who hadn’t tested and didn’t trust or understand that DNA can provide a very useful additional string to your bow.  I tried to cover a number of common objections and misunderstandings I see regularly in online discussions

I’ve now put together another little series of posts.  This time the focus is more practical: how can we put the theory covered in those earlier posts into practice?  These posts have grown out of many email exchanges with some of my own DNA matches in which I’ve tried to answer their questions or explain to them how we might be able to progress together.  Again, this series focuses on known sticking points – often discovered in working with my own DNA matches.  So if you’re reading this because we’re DNA cousins (Hello!) then this post, the next two, and others that will follow in spring 2021 are dedicated to you.  My hope is that by writing it here instead of (repeatedly!) in emails, it will help other new – or even not-so-new – testers, who are still finding out how to make the DNA work.

*****

Getting started: Looking at your results
I’m going to concentrate here on the two DNA testing providers mostly used by amateur genealogists: Ancestry and MyHeritage.  These companies are increasingly integrating their DNA service with their online tree function.  However, other testing companies will present the essential information in a similar way.

When you open up the DNA page on Ancestry or MyHeritage the options you’re presented with are pretty similar.

On Ancestry you’ll see:

  • Your DNA Story, including ethnicities, and breaking these down further into regions, counties and smaller areas.
  • DNA Matches
  • Thrulines

On MyHeritage you’ll see:

  • An Overview, where you can scroll down to access all the other options but where you can also see your ethnicities at a glance
  • Ethnicity estimate – the areas are broader (less focused) than Ancestry’s
  • DNA Matches
  • Tools

EVERYONE looks at the ethnicities first!
Many people take a DNA test purely out of curiosity for the ethnicities.  They have no knowledge of and no interest in their family tree.  Often, the people listed as your DNA matches who have no tree attached will fall into this category.  (The other possibility is that they have no tree because they don’t know who their parents are and have taken the test to try to find out.)  Whatever your reason for taking the test, this is almost sure to be the place you look first, and on the surface it’s the easiest part to understand.

Ethnicities are, however, the least ‘accurate’ part of the whole DNA testing journey.  They are based on a comparison of your DNA to that of selected people with deep regional roots and well-documented family trees from around the world.  These people are referred to as the ‘reference panel’.  Different testing companies arrange their panels in different geographical groupings.  They also use different algorithms.  What this means is that your ethnicities are only an estimate; and although of course your DNA doesn’t change, from time to time, based on all of the above, the testing companies will update their estimate of your ethnicities.  It also means that the estimate of your ethnicity will differ according to which company provides it.  Hence at the time of writing this my own ethnicity is estimated as follows (the largest area is first in each case):

Ancestry: England & NW Europe, Scotland, Ireland, Sweden, Germanic Europe, Wales
FTDNA: Scandinavia, West and Central Europe, British Isles and a dash of Siberia
MyHeritage: (The DNA data I put on here was uploaded from my original FTDNA test): Mostly North and West Europe with some East Europe and a little South Europe

That’s quite a range, although taken as a whole they are all European and all centre on the north and north-west of Europe if not actually the British Isles.  (And of course like many people I cling to the hope of deep down, being a Viking. 🙂 )  It’s advised that tiny percentages (like my Siberia) be taken with a pinch of salt, but certainly as more people test, ethnicities are becoming more accurate.  If something unexpected shows up at a high percentage it’s likely to be a reasonable guide.

Ancestry have taken ethnicities a step further with the integration of ‘Genetic Communities’ into their ‘DNA Story’.  The smaller (regional, county, locality) groupings referred to above are in fact a combination of genetics and genealogy: they draw upon the family trees of your DNA matches.  These are generally found to be very accurate and in my case have homed in on two very important areas of my ancestry.

*****

The important bit: DNA matches
For genealogy and family history enthusiasts, this is the most important information.  Whichever company you tested with, your DNA matches will be listed in descending order starting with those with whom you share the highest amount of DNA at the top, right down to the tiniest matches.  You will have a LOT of matches but you should start at the top.

Your matches will be placed into categories.  At MyHeritage matches are placed into ‘Close Family’, ‘Extended Family’ and ‘Distant Relatives’ with an ‘estimated relationship’ for each person.  At Ancestry the divide is at ‘4th cousins or Closer’ and ‘All Matches’, with matches arranged as e.g. ‘Full Siblings’, ‘3rd cousins’, ‘4th cousins’, and a more specific estimate for each person.

For each individual match you’re given additional information.

Ancestry provide:

  • the person’s name (or pseudonym) and maybe a photo
  • the amount of shared DNA, expressed as centiMorgans (cM)
  • the number of individual segments these cM are arranged in, and the largest segment
  • whether they have a tree, and whether it’s public or private
  • whether you have already added any notes

Click on the person’s name for more information:

  • links to your match’s tree(s) – there may be more than one tree, but only one can be linked to their DNA
  • whether Ancestry’s algorithms have identified any common ancestors in your trees
  • a link where you can compare your own ethnicity with your match’s
  • a link to a list of shared matches – people who match both of you
  • You will also see where you can add the notes mentioned above and where you can add the person to a group, using a coloured dot of your choice

MyHeritage provide:

  • the person’s name (or pseudonym) and maybe a photo
  • the amount of shared DNA, expressed as cM and also as a percentage of your total DNA
  • the number of individual segments and the largest segment
  • whether they have a tree and how many people are on it
  • A ‘notepad’ icon where you can make notes (icon is red if you have already made notes for this match)

Click on ‘Review DNA Match’ for more information:

  • lists of ancestral surnames in your trees, with any shared surnames highlighted
  • lists of people who match both of you (shared matches)
  • a comparison of your ethnicities
  • and right at the bottom something called a chromosome browser, in which you can see exactly where, on your 22 chromosomes, you and this person match.  (I’ll be looking at this in detail in a mini-series of posts about chromosome mapping early in 2021.)

For an explanation of centiMorgans see my earlier post on Using DNA to develop your family research.  See also the Shared centiMorgan Project chart that sets out the possible relationships for any specific cM range.  As a general rule, don’t spend too much time working on matches below 30 centiMorgans.

*****

This is what you can do straight away
My advice is to take a while getting to know how the information is laid out, and to take note of anything that leaps out at you. I say this for two reasons.  Firstly, there’s a huge amount of information there and it’s easy to become overwhelmed.  But secondly, it takes a while for the powerful computers to find all your matches and include them on your match list, along with their trees and lists of shared matches.  The following action plan focuses on what you can do straight away while you find your way around the system.

  • Look at your list of matches.
  • For the closer matches (at the top of your list) do you already recognise them? Are they known cousins, second cousins, etc?
  • For any closer matches (such as 2nd or 3rd cousin) that you don’t recognise but who have trees, can you compare your trees and find a common ancestor?  Bear in mind that second cousins are descended from the same great grandparents; third cousins from the same great great grandparents.  But be prepared to look a generation or so either side.
  • When you can confirm your first match and have worked out your Most Recent Common Ancestors (MRCA) you can assign this match to a specific part of your tree.  You now know your documentary research to this point is correct and there were no adoptions or unexpected paternity events along the way.  Making immediate use of the notes box means you won’t waste time looking again for your match.
  • If you’re using Ancestry you can assign this reasonably close match a coloured dot.  How you organise your coloured dots is up to you.  I have eight colours – one for each great grandparent.  Whenever I can confirm a new match I give them the appropriate colour dot for the part of my tree they slot into.
  • You now have the beginning of a guide for other matches for this part of your tree.  For example, a first cousin match may help you to place any shared matches to your maternal or your paternal side; a second cousin may help you to home in on a specific grandparent.  See my previous post on Asking other family members to test for more guidance on this.
  • With this in mind, look now at the shared matches for you and your confirmed cousin match.  Again, perhaps you already know some of these people.  Perhaps you recognise their surname from your tree.  If not, perhaps their own tree will guide you to the place where your trees merge: your MRCA.
  • Join an online group.  There are several groups on Facebook, but DNA Help for Genealogy run by Donna Rutherford is a good place to start. Gradually you’ll understand more and be able to make better use of more of this information.

*****

My next DNA post, on 15th November, will look at Ancestry’s Thrulines and MyHeritage’s Theory of Family Relativity.

I’m deliberately releasing this information in manageable, bite-size chunks.  However, if I’m going too slow for you, have a look at Donna Rutherford’s blogpost on Frequently Asked Questions about DNA.

*****

Note
My posts about DNA are aimed at complete beginners and aim to provide information in manageable chunks, each post building on previous ones. Click [here] to read all of them in order, or to dip in and out as you wish. You’ll also find lots of resources and useful links.