DNA: Exploring AncestryDNA Thrulines

ThruLines® is a tool from AncestryDNA that shows you how you might be related to people with whom you share DNA.

A ThruLine is a hypothetical connection based on information from your family tree that supports a link between your tree and the family tree of the person you match (a match is someone who shares some DNA with you).

For a ThruLine to exist both you and your match need to have a family tree linked to your DNA test. AncestryDNA uses the family tree linked to your test to find people who are in your tree and also in the
trees of your matches.

You can find ThruLines from any page on Ancestry®. Click the DNA tab to start. ThruLines are available for ancestors through to 5th great-grandparents.

Here is a screenshot of my husband Greg’s ThruLines.

We know all of Greg’s great great grandparents, but when it comes to earlier generations there are gaps. ThruLines, using a combination of DNA and family trees, has the potential to help identify some of the ancestors whose name we don’t know. These suggestions are identified in green.

Thomas Harvey, born 1739, has been identified as possibly one of Greg’s fifth great grandfathers.

I select Thomas from the grid on ThruLines. While hovering it shows me there are two DNA matches who are also descended from Thomas. I am invited to evaluate the relationship paths.

One of the matches is a second cousin descended from Greg’s great grandmother Edith Caroline Edwards. The other match is identified as possibly a sixth cousin.

If I click on the green ‘Evaluate’ button beside the name of Thomas Harvey, I see two different sorts of trees to review. One tree is created by the DNA match, but it is a private tree with apparently no records. However, clicking on the private tree I can see that there are in fact 13 records attached. So I can evaluate the possible shared ancestry I have written to the match requesting access to the tree.

There are also 3 other trees with Thomas Harvey, with up to 3 records attached. The researchers have no DNA connection but are researching the same ancestors. Selecting one of the other trees I can see the three attached records and I can review these further. I am also invited to add Thomas to my tree on the basis of the research done by the Ancestry member. I prefer to progress more slowly and to evaluate the records to see if Thomas Harvey is indeed the father of Jane.

ThruLines has given me some hints to work on to go further back on the Harvey line and review the records to see if I can link Greg’s 4th great grandmother Jane Harvey to Thomas and Patience Harvey. The difficulty is that Harvey is not an uncommon surname and Jane is a common forename. It is hard to be certain that Jane Harvey is linked to this family. Parish records in the late eighteenth and early nineteenth centuries are less useful in making connections between the generations. I do not think there are wills available for this family which would help to link the generations.

ThruLines® is a useful tool for suggesting connections between DNA matches and providing hints about possible relationships. However, as with all such hints and clues, the written records must also be assessed to determine if the relationship suggested by the DNA evidence actually holds

WikiTree link for Jane Harvey: Jane (Harvey) Edwards (abt. 1766 – 1842)

Wikitree – what is it and should I use it?

Front page of Wikitree.com as at 16 September 2022

Recently a user on a Reddit genealogy forum asked, Wikitree-what is it and should I use it?

He received some interesting answers.

One user replied:

WikiTree is a free global tree, where one profile is created per ancestor that users collaborate on. The most popular global trees are FamilySearch, Geni, and WikiTree.

Advantages of working on a global tree are:
. you have other people to share the work with and learn from
. all the best sources and info and are combined into one place
. gives the opportunity to see conflated information you probably wouldn’t notice outside a global tree (for example, two profiles have the same date of birth and parents but aren’t the same person, meaning further research is needed)
. view relationships to other people in the global tree
. other people are more likely to see your research vs. just having it in your own tree

While smaller than the other global trees, WikiTree focuses the most on accuracy and tries to enforce a standard of having at least one source per profile , and only using reliable sources for pre-1700 profiles. It is probably the most “serious” genealogy site of the three. It is not a records repository site like Ancestry or FamilySearch though.

Another user wrote:

I am a big fan of the Wiki collaborative editing concept, but I found the WikiTree UI clunky to use and got discouraged after a few days.

Another pointed out that:

Wikitree is not a records repository. It's aim is to be the most accurate "one world tree" there is, where users are supposed to collaborate on profiles of people, and list sources to support the facts.

While it sometimes falls short of 100% accuracy and profiles without enough good sources, I generally find it a good place to collaborate. There are a lot of experienced genealogists contributing, and it's a bit harder for a newbie to cause too much erroneous damage than it would be on the FamilySearch shared tree. It's also good in that you can write (or edit or contribute too) a biography for your ancestors - describe the facts, anecdotes if any, and research notes if there are complicated interpretations of sources.

I find it a useful place to share my research - I think of it more of a site to "give to" rather than one to "take from" -- my family members and distant cousins can make use of what I've found, and review sources to make sure that I (and others) didn't get any of it wrong. I like to think of genealogy as a perpetual work in progress, and we should all share what we know. It saves a lot of hours not having to blindly replicate some complicated research that someone else has already done.

It also has neat things like seeing how you are connected to famous people. I also like how users can enter DNA info on their profiles (not DNA data itself, but that they took a test and where), and that info is propogated in a useful way through their relations in the tree. It has lots of useful and fun apps for various purposes.

If you're interested in it, one warning -- it's a bit of a learning curve to learn the ins and outs, but there are good help pages and videos. Also it is time-consuming to create good profiles, so it is for the patient and careful type. You have to search to see if a profile exists or not to determine of you should create a new profile or edit an existing one, because one person should only have one profile. And the features won't be useful unless you build out your tree enough to connect in to the rest of the world.

Other people on the Reddit forum complained that the collaborative process sometime allowed incorrect information to be added.

Another user noted that “Adding sources is a lot of work and if you’re not familiar with wiki formatting it is slow.”

A user added a few pointers:

You’ve gotten a lot of good explanations on what wikitree is so here’s a few tips on using it.

1. It’s a great way to share your research with others. A cousin is curious and all you have to do is send a link. No long email with info. It’s all there in a free, easy to understand way.
2. Is that it’s a great way to keep your research online. Since they encourage putting in all your sources, you know have access to it all online and can work on your tree anywhere. Sure you can do that on other sites, but I personally find wikitree to be an easier way to do it. And it’s free.
3. Rootstech. [I think the author means Rootsearch found on the right of the data entry screen] It puts your info in the search boxes. Click the site you want to search and voila. No more jumping back and forth having to put in the info on each site you use.
4. The community is actually active and you can get help and actual support.
5. Join a project. Sometimes we burn out on our own trees. Those brick walls just get us. Maybe there’s a project you can join. A challenge that you can find. Some project generate a list of profile with errors so you can quickly help others.

Things you may not like 
1. It’s meant as a genetic tree, so adoptive parents/children may find that off putting.
2. It’s a lot of work putting in all the data.
3. As with all shared trees you have to trust the other users.

A review of Wikitree published at https://www.dnaweekly.com/reviews/wikitree/ was unfavourable. The reviewer found the interface clunky and unintuitive. She wanted to explore uploading a GEDCOM file, a file which contains genealogical information about individuals such as names, events, and relationships; the records are linked together by metadata. However, she found it best to start building her tree. It is apparent from her efforts that she is not an experienced genealogist, for she entered her maternal grandmother with her married name, not her maiden name. She could not

 “locate any birth, death, or marriage certificates for any of my family members, even though I’d found them on other sites. If you’re after historical records specifically, you’d be better with Ancestry. It has a huge bank of records with an easy-to-use searching tool.”

Of course—and some people miss the point—this is because WikiTree is not a records repository.

The reviewer misunderstood Wikitree and was disappointed.

A response on the Reddit forum about sourcing points to a useful browser extension:

Entering sources is really easy using the WikiTree Sourcer browser extension (https://www.wikitree.com/wiki/Space:WikiTree_Sourcer). It came out in October. Easily cite Ancestry, FamilySearch, FindMyPast, ScotlandsPeople, Find A Grave, UK BMD, with more sites to be added in the future. It even automatically adds a free sharing link for Ancestry sources.

For sources from other sites, most of the WikiTree projects have pages dedicated to source citation templates you can copy and fill in, or source citation examples for specific sites.

I have been using this extension recently and I found it very effective for adding information to profiles. I recommend it. There is a YouTube video which explains how to use it, at WikiTree Sourcer Extension Intro and Overview.

I agree that the interface of WikiTree is clunky but it is effective. It takes a little while to get used to and some knowledge of genealogical conventions such as the use of maiden names for women is required. It is expected that sources are cited according to conventions but as the Help page says: “the important thing is citing the source, not how it’s done.” “Genealogy without sources is mythology!” (According to a 2011 post by Tamura Jones the source of this aphorism is possibly Mary L. Henke.)

Family Tree Magazine has an introduction to Wikitree at https://familytreemagazine.com/websites/wikitree-tutorial/ The presentation notes “This is a collaboration—it’s meant to be accurate. Mistakes will happen, but the group assumes the best intentions of others and pledges to be courteous as they hammer out their differences in research findings.”

In a post of 26 April 2019, the genealogist Kitty Cooper discusses why you should add your research to WikiTree. She starts her post “A heartbreaking moment for any family historian is when you discover that your late genealogist cousin’s wife has shredded all his papers. This actually happened in my family.”  Sadly, this has happened in my family too. However, with Wikitree I believe my research will be there as a resource for my descendants and my cousins to use now and indefinitely into the future, safe, I hope, from accidental or malicious damage.

To sum up: Wikitree is not a records repository but a global family tree with a profile for each person. Wikitree users collaborate in their research. Wikitree is a site to give to rather than take from. My family members and distant cousins can make use of what I’ve found and review sources to make sure that I didn’t get any of it wrong. I agree with the idea of “genealogy as a perpetual work in progress”, and that we should share what we know. Not having to replicate complicated research that someone else has already done can save a lot of time. The Wikitree interface is a little rough and ready, and it takes time to learn, but there are tools to help.

Related posts

• Tree progress September 2022

Tree progress September 2022

In May 2018 I wrote in this journal about progress I was making on my family tree. The previous ten generations of my children’s ancestors have a maximum total of 1,023 people. How many of these, I wondered, could I name.

I found that I knew the names of only 319 (31%). Today, four and a half years later, I can name 384 (38%). This is 65 more, an increase of 26 on what I knew a year ago. I have yet to discover the names and other information about the remaining 639.

Ten generations takes you to your 7th great grandparents. Where I know their date of birth, most of my children’s 7th great grandparents were born in the late 1600s and 1700s. I know the names of 99 of the 512 ancestors of this generation. I don’t know very much more than the names of 44.

In recent years I have transferred the outcome of much of my research to WikiTree, a collaborative project intended to produce a single worldwide family tree.

In a post of 26 April 2019, the genealogist Kitty Cooper discusses why you should add your research to WikiTree. My research will be there as a resource for my cousins to use now and indefinitely into the future, safe, I hope, from accidental or malicious damage.

There are discrepancies between my personal research tree and WikiTree. For one thing, I have names of ancestors on my personal tree about whom I know nothing more. These people cannot be added to WikiTree until I have more information about them. When I add a person to WikiTree I provide source citations: I state how I know the facts being added and about the relationship of the newly-added profile to other people on the tree. Adding my family tree to WikiTree is an excellent way to review and verify my family history research.

When looking at the 1,023 individuals of the previous ten generations of our ancestors, I now have 313 recorded on WikiTree, 31% of the possible maximum. This is 55 more than the 258 recorded on WikiTree a year ago. I need to find more details for the 70 ancestors where I know not much more than the name and add them to WikiTree. The challenge remains to try to learn about the 639 ancestors missing from our tree.

Chart generated from Wikitree of my daughter’s ancestors

Related posts

• Progress on my tree from May 2018
• Tree progress September 2021

AncestryDNA: latest updates to ethnicity estimates

AncestryDNA has launched a new feature, a chromosome painter, which ‘paints’ your DNA with your ethnicities, showing the DNA regions that make up your ethnicity estimate.

Overnight my kits updated to show the new information. It’s found under the ‘DNA Story’ tab.

Five years ago when I looked at my ethnicity AncestryDNA reported it as 100% European:

• 59% from Great Britain, which includes England, Scotland, Wales and the Isle of Man
• 20% Europe East
• 12% from Ireland
• 4% from Finland / North-west Russia
• 2% from Europe-West
• 2% from Italy/Greece
• <1% from the Iberian peninsula

At the time, the results seemed to underestimate my German heritage. My mother and her ancestors are from Germany.

It has now refined the results:

• Scotland 41%
• Germanic Europe 33%
• England and Northwestern Europe 13%
• Sweden and Denmark 6%
• Wales 3%
• Ireland 3%
• Baltics 1%

At https://support.ancestry.com/s/article/AncestryDNA-Ethnicity AncestryDNA explains it calculates its ethnicity estimate:

To discover where you come from, we compare your DNA to the DNA of people with known origins from around the world. These people are our reference panel. Our reference panel has over 56,580 DNA samples from people with deep regional roots and documented family trees. We survey your DNA at over 700,000 locations and look at how much DNA you share with people from the reference panel in each ethnicity region.

Recently AncestryDNA provides estimates of ethnicity inheritance from each parent. They use your DNA matches to split your DNA into the halves that came from each parent. First, they find the segments that connect only to one parent or the other. Then, they separate out the DNA you got from each parent by piecing together the segments that overlap. After they have separated your DNA into the parts that correspond with each parent, they calculate an ethnicity estimate on the two halves. From this, they can show your “ethnicity inheritance”—the ethnicity percentages passed down to you from each parent.

These are my results.

Both of my parents have tested with AncestryDNA, so I can compare the estimate with its results. The differences are partly because I inherited only part of their DNA.

Column 1 has the ethnicity percentage I am estimated to have inherited from my parent and column 2 has their ethnicity estimate from their own test with AncestryDNA.

	% I inherited from parent 1	My father’s ethnicity estimate
Scotland	41%	43%
Germanic Europe	0%	3%
England and Northwestern Europe	6%	8%
Sweden and Denmark	0%	0%
Wales	3%	14%
Ireland	0%	31%
Basque		1%

	% I inherited from parent 2	My mother’s ethnicity estimate
Scotland	0%	2%
Germanic Europe	33%	79%
England and Northwestern Europe	7%	10%
Sweden and Denmark	6%	3%
Wales	0%	0%
Ireland	3%	0%
Eastern Europe and Russia	0%	6%
Baltics	1%	0%

It seems doubtful to me that I inherited Irish ethnicity from my mother. She herself shows no Irish ethnicity in her results and my documented family tree has an Irish connection on my father’s side, reflected in his ethnicity results, with no Irish connections for my mother.

AncestryDNA’s Chromosome Painter displays these results:

My Chromosome map at AncestryDNA as at July 2022

My chromosome map divided between my two parents

When I look at the results by different regions I see that Ireland has been assigned solely to chromosome 7, as has Wales. AncestryDNA has allocated Wales to one of my parents and Ireland to the other.

I suspect the breakdown by chromosome needs to be refined.

By way of comparison this is my father’s AncestryDNA chromosome painter picture. It can be compared with the map I have developed using DNAPainter.

My father’s Chromosome Painter results from AncestryDNA July 2022

My father’s chromosome map at DNAPainter where I have been able to assign shared DNA according to ancestors shared with DNA matches

For the most part AncestryDNA has allocated regions to whole chromosomes.

So far at DNAPainter I have only managed to paint just over a quarter of my father’s DNA profile. I can make some comparison between the two diagrams.

The Basque inheritance AncestryDNA shows on the paternal chromosome 1 appears to be inherited from Philip Chauncy and Susan Mitchell, my father’s great great grandparents.

My father has inherited Scottish and Irish ancestry from both his mother and his father. His Welsh ancestry was inherited only from his father. This does correspond with my known tree.

English ancestry has only been inherited from his mother; English ancestry is not so well defined for me – many forebears were born in England but had come from elsewhere, the issue becomes from what generation ethnicity is determined.

My father has inherited his Germanic Europe ancestry from his father on chromosome 6. It is not clear which ancestors might be responsible for this inheritance.

To be useful AncestryDNA’s Chromosome Painter diagrams clearly need more work.

I remain more interested in ancestral contributions to DNA rather than the vague attributions of ethnicity.

Unfortunately, for privacy reasons (or so it is said), AncestryDNA chooses not share detailed information about DNA matches. To obtain the details and be able to derive the information about which DNA you inherited from which ancestors you need to use other companies, such as MyHeritage, Family Tree DNA, or GedMatch.

RELATED POSTS AND FURTHER READING:

• Looking at my ethnicity as determined by DNA testing
• ‘ethnicity’ DNA: beware of inheritance from daughter to mother
• Update to AncestryDNA communities: Vinnie has views
• DNA Painter – a new tool

• AncestryDNA articles
  • Chromosome Painter
  • AncestryDNA® Ethnicity Estimate
  • Ethnicity Inheritance
  • How SideView™ Technology Splits Your DNA Results by Parent
  • Ethnicity Estimate 2021 White Paper

Wikitree:

• Anne (Champion de Crespigny) Young

Y not Y?

My fourth great-grandparents Edward Hughes and his wife Elizabeth Jones were Welsh; Edward was from Newmarket, Flintshire, and Elizabeth from Cardiganshire. Hughes, however, is not an unusual surname in Wales, nor is Jones, and for a while I’ve been muddling them with another Welsh couple from Flintshire with the same names.

• 

• 

  Photographs of Edward and Elizabeth Hughes from pages 67 and 72 of Cherry Stones by Helen Hudson

When three years ago I wrote about Edward and Elizabeth I believed, mistakenly, that they had married at Ysgeifiog (also written Ysceifiog) in 1821 and that this was Elizabeth’s birthplace. Edward was from Holywell, a couple of miles north.

I have since ordered Elizabeth’s Victorian death certificate. She died on 4 July 1865 in Brighton, a suburb of Melbourne, Australia.

Australian death certificates include much information useful to the genealogist, though the reliability of this depends on the knowledge and good will of the informant. In Elizabeth’s case the informant was her husband Edward Hughes.

The 1865 death certificate of Elizabeth Hughes

From Elizabeth’s death certificate I learnt that she was born in Cardiganshire to Edward Jones, who was a farmer, and Elizabeth Jones née Humphreys. She was 66 years old when she died, so she was born about 1799. Elizabeth and Edward married about 1825 in Liverpool when she was twenty-six. They had eight children:

• Mary, dead;
• Samuel aged 37 years (at the time of Elizabeth’s death in 1865, so born about 1828);
• Mary aged 35 years (born about 1830);
• John dead;
• Eliza Ann dead;
• Elizabeth Humphreys dead;
• Goodman Edward Jones dead; and
• Henry aged 24 years (born about 1841).

At the time of her death Elizabeth had been in Victoria for twelve years eleven months, so she had arrived about August 1852. Although she died in Brighton, the home address of her husband Edward was View Street, Bendigo (the town at that time was also known as Sandhurst), a hundred miles north. The cause of her death was recorded as chronic disease of the liver and stomach trouble. She had been ill for two months, which perhaps implies that she had come from Bendigo to Melbourne for treatment.

Elizabeth Hughes was buried in Brighton General Cemetery on 13 July 1865. The gravestone inscription reads:

In memory 
of 
Elizabeth
Beloved wife of 
Edward Hughes 
of Sandhurst
Died 10th July 1865 
aged 66.
Precious in the sight of the lord is 
the death of his saints

(The verse is from Psalm 116.)

The Bishop’s transcripts, copies of the parish registers which had been sent to the bishop, of Liverpool marriages includes a record at the church of St Philip for a marriage by banns on 24 April 1825 of Edward Hughes and Elizabeth Jones. Neither had been previously married; both were of the parish. A transcript of the marriage register shows the witnesses were John Parry and G. Jared; I believe the witnesses are not related to the bride and groom.

As this record is a better match for the details given at the time of Elizabeth’s death I am more confident that this is the record of the marriage of my fourth great grandparents Edward and Elizabeth Hughes. Unfortunately, details which would help to confirm that we have the right couple, such as their parents’ names and occupations, are not recorded.

Building a family tree with common surnames such as Hughes and Jones is often more difficult than not, because there is more likely to be confusion over two people with the same name. From the information on Elizabeth’s death certificate, it seems that I was wrong: my fourth great grandmother was not from Ysgeifiog and my Edward and Elizabeth were not married there. I have corrected my tree and added the new information.

RELATED POSTS

• F is for Flintshire

Wikitree:

• Edward Hughes (1803 – 1876)
• Elizabeth (Jones) Hughes (abt. 1798 – 1865)

600th blog post

I wrote my first family-history blog post ten years ago, on 25 April 2012. My 500th came two years ago, on 1 June 2020. This is my 600th.

My blog—really an online research journal—has been an effective and efficient way of recording my family history.

From time to time I like to measure the progress I have made in my research into my own direct ancestors and those of my handsome husband Greg (my very patient and helpful editor!).

Six months ago I found that of the previous ten generations of my children’s ancestors I knew little more than the names of most of the 86 of their 512 7th great grandparents. I didn’t know much about my German ancestors before my children’s 3rd great grandparents. When I first started reviewing progress on my ancestors in May 2018 I knew only 54 of these 7th great grand parents.

Generation from my children

parents to 3rd great grandparents

Ancestors identified

62

Change since May 2018

–

Tree
completeness

100%

4th great grandparents

58 of 64

+4

91%

5th great grandparents

80 of 128

+13

63%

6th great grandparents

91 of 256

+24

36%

7th great grandparents

91 of 512

+24

18%

Of the possible 1022 ancestors up to 10 generations of 7th great grandparents I have identified 366 or about 36%. I know all 32 of my children’s 3rd great grandparents and thus all 62 of their possible ancestors to that level. At the 4th to the 7th great grandparent level I now know about 65 more ancestors since I first documented my progress in May 2018. I have, of course, also been discovering more about our ancestors’ lives since that time.

Image of 10 generation tree generated using DNAPainter

I continue to enjoy my research and writing about our ancestors.

Related posts:

• 500th blog post
• Progress on my tree in May 2018
• Tree progress September 2021

Finding the parents of Frederick Harold Plowright born 1881

My husband Greg’s great great grandparents John Plowright (1831 – 1910) and Margaret Plowright nee Smyth (1834 – 1897) were married in 1855. They had six children, the youngest born in 1872. In 1881 they adopted a child named Frederick Harold Plowright. I have not found his birth certificate, and until recently I did not know how he was related to the Plowright family. Until 1929 there was no formal adoption process in Victoria and so there was no directly relevant documentary material from 1881 to establish a relationship.

Frederick Harold Plowright 1881 – 1929, photograph in the collection of his grandson J P

In 2018 J P, grandson of Frederick Plowright, took a DNA test. This showed that he was related to the descendants of John and Margaret Plowright but that his grandfather was not the son of John and Margaret.

I used a DNA Painter analysis tool called ‘What are the Odds?’ to estimate where J P stood in the family tree and so how Frederick Harold might be related. The tool calculates where somebody probably fits in the family tree based on the amount of DNA they share with people about whose position in the tree you have complete confidence. The tool predicted that the best hypothesis is that J P was the great grandchild of James Henry Plowright, one of the sons of John and Margaret Plowright, and that his grandfather Frederick was a half-sibling to the other children of James Henry.

In short, it appears very likely that Frederick was adopted by his paternal grandparents.

Using the What are the odds (WATO) tool from DNA Painter to calculate how J P might be related to his Plowright cousins. Hypothesis 5 is the most likely and is indicated with a red *. J P’s grandfather’s most probable position in the family tree is indicated with a green *.

The Avoca Mail reported on 28 June 1881 that Elizabeth Ann Cooke brought an affiliation case against James Henry Plowright. This is a legal proceeding, usually initiated by an unwed mother, claiming legal recognition that a particular man is the father of her child. It was often associated with a claim for financial support.

AVOCA POLICE COURT. Monday, June 28th, 1881. (Before C. W. Carr, Esq., P.M.)

Elizabeth Ann Cooke v. James Henry Plowright. — This was an affiliation case, and Mr Matthews, who appeared for the plaintiff, asked that it might be postponed to allow it to be arranged out of court. The case was accordingly postponed by mutual consent for one week.

Avoca Mail 28 June 1881

A week later the case had been settled, presumably by the parents of James Henry Plowright agreeing to adopt the child:

AVOCA POLICE COURT. Monday, July 4th, 1881. Before W. Goodshaw, Esq., J.P.

E. A. Cooke v. J. H. Plowright. — Mr Matthews, for the plaintiff, stated that the case (adjourned from last court) had been settled

Avoca Mail 5 July 1881

Elizabeth Ann Onthong was born in 1862 in Avoca, Victoria, to Thomas Onthong and Bridget Onthong nee Fogarty. The family later used the surname Cook or Cooke. Elizabeth was the fourth of six children; she had four brothers, none of whom apparently married or had children, and one sister, Mary Ann, who married and had children.

J P shares DNA with descendants of Mary Ann

Related posts:

• John Plowright (1831 – 1910)

Wikitree:

• Frederick Harold Plowright (1881 – 1929)
• James Henry Plowright (1860 – 1932)
• John Plowright (1831 – 1910)
• Margaret (Smyth) Plowright (1834 – 1897)
• Elizabeth Ann (Onthong) Wiffen (1862 – 1927)

More relatives at RootsTech

I wrote several weeks ago about Relatives at RootsTech.

In the past if you attended the RootsTech conference in person you had, of course, the opportunity to meet your fellow participants. At a genealogy conference you would naturally be interested to meet your relatives. RootsTech has an app to search for attendees you might be related to. As we cannot meet in person this year we can search for cousins who have also signed up to the virtual conference. There are more than 408,000 participants who have signed up to the connection tool and the conference. The connection tool is only available for a limited time, this year until 25 March.

On 21 February I had identified 700 cousins through the application. I now have 4,845. They include my daughter, a third cousin and a fourth cousin once removed. These three are from Australia. There are seven more distant cousins from Australia. The very great majority of my cousins are from America.

Relatives at RootsTech filtered by location

The cousin relationships are mostly too remote to be interesting. It’s usually by other means that I find cousins who might be interested in collaborating on family history.

I persuaded my daughter to sign up because I was wanted to find her cousins on the paternal side. Interestingly, she has only 1,963 relatives including me and the two close-ish cousins on my side.

Her closest paternal cousins are from the US and are descended from my husband’s first cousin four times removed, Rebecca Leavitt, formerly Waite nee Gibbons. Rebecca was a Mormon pioneer who emigrated from England to the US in the 1870s with her first husband. The closest connecting cousins are fourth cousins twice removed to my daughter; those cousins are great grandchildren of Rebecca Gibbons. There are 152 cousins at RootsTech descended from my daughter’s 5th great grandparents, John Gibbons (1780-1840) and Frances Atkins (1772-1856).

I wrote some years ago about discovering the DNA connection between my husband Greg and his cousins descended from Rebecca (DNA analysis: taking the tree back two generations).

An example of a family tree connection shown on RootsTech Relatives application between Waite cousins and my daughter’s Dawson forebears. Rebecca Gibbons married twice and there are also descendants from her second marriage.

Photograph of Rebecca Gibbons retrieved through FamilySearch profile KWN5-32S

Back to the numbers. Although my daughter’s matches include my forebears and those of my husband, she has only about 40% of the number of relatives I have. More than 60% of my relatives are so distant they are not included in her results. Testing the distance I found that two of my distant cousins from Argentina, a ninth cousin and an eighth cousin once removed, are not included in my daughter’s results table. These relatives were both on my Dana line, an early colonial American line. I am sure it was the source of many of my distant cousins, for that line is well researched.

While looking at relatives I used the opportunity to edit the FamilySearch tree. Some incorrect branches I edited and removed, but in other cases I merged profiles. I also managed to add a few people to my German pedigree. Despite this effort in contributing to the single family tree at FamilySearch, I haven’t yet connected with cousins from my mother’s German family who are interested in genealogy.

Slow progress on this bit of my family tree and as yet no connection with cousins who are interested in genealogy

Wikitree and FamilySearch links

• Wikitree: Rebecca (Gibbons) Leavitt (1843 – 1897)
• FamilySearch: Discovery person page for Rebecca Gibbons
• John Gibbons (abt. 1780 – 1840) on Wikitree and on FamilySearch
• Frances (Atkin) Gibbons (1777 – 1856) on Wikitree and on FamilySearch

Ethical issues of genealogy discussed at RootsTech 2022

RootsTech 2022, which ran from 3 to 5 March, was a virtual conference sponsored by FamilySearch, an organisation closely connected with the Family History Department of The Church of Jesus Christ of Latter-day Saints.

More than a million participants listened to 1,500 presentations in at least 30 languages. Many were pre-recorded; others were created during the conference. Recordings of conference sessions are now available online.

I listened to several sessions about ethical issues of genealogy.

Dr Penny Walters, a lecturer from Bristol University in England, gave several talks including one about the ethics of genealogy titled Damnatio memoriae – condemnation of a person’s memory.

She asked whether:

"…we, as family historians, are manipulating the past with our narratives of people's lives. Do we gloss over things, not investigate specific ancestors and favour others? If we do so, are we engaging in a form of subtle iconoclasm? How do we deal with unsavoury people in our family tree?"

The destruction of the images of a ruler after his or her death or overthrow, is known as damnatio memoriae. It means “condemnation of memory” and indicates that a person is to be excluded from official accounts.

In 2020 the statue in Bristol of a trans-Atlantic slave trader, Edward Colston (1636–1721) was felled by protestors.
Photograph by Caitlin Hobbs “The space where Colston stood is now filled with #BlackLivesMatter signs – a powerful day in Bristol” https://twitter.com/Chobbs7/status/1269682491465576448/photo/1 CC BY 3.0, Picture retrieved from Wikimedia Commons

I had a chat with Dr Walters before the conference. The questions she raises are very interesting, with no easy answers.

I myself find that it is challenging to include unsavoury details about my forebears in my family tree. On the other hand, I think that no one should be excluded, and perhaps sometimes just names and dates are sufficient while I wait to consider how to provide biographical details.

I have also listened to Dealing with Ethical Dilemmas in an Online World (A Discussion) where the panel included:

• American genealogist Lyn Broderick https://thesingleleaf.com/about-2/
• Australian genealogist and blogger Jill Ball, who blogs as Geniaus http://geniaus.blogspot.com/),
• Daniel Loftus a young Irish genealogist https://thehiddenbranch.com/who-we-are-2/,
• American genealogist Judy Russell who blogs as the Legal Genealogist https://www.legalgenealogist.com/,
• American genetic genealogy researcher CeCe Moore https://en.wikipedia.org/wiki/CeCe_Moore, and
• Australian genealogist Kerry Farmer https://www.kerryfarmer.info/.

The aim of the session was to “discuss common scenarios to help increase awareness, promote understanding, and educate the community on this important topic.” Scenarios included:

• The inclusiveness of the genealogy community; the discussion touched on the issue of cyber-bullying, concluding that we should promote the notion of genealogy for all.

• Daniel Loftus looked at the issue of memorials at FindAGrave and similar sites being created by people who are not close family members. FindAGrave has dealt with this problem by creating new guidelines for people who have recently died.

• Judy Russell spoke about copyright and also the terms of service for websites where we gain information in our genealogical searches. Some of the issues she discussed she had written about in January in her post Reprise: TNSTAAFL. Other earlier posts also covered the issues she explored:
  • Credit doesn’t cut it : nowhere in the law does it say “but it’s perfectly okay to copy and share it if you give the creator of the work credit.”
  • Contract, not copyright : websites rely on contract law (their terms and conditions) to restrict re-use of any out-of-copyright materials

• CeCe Moore spoke about investigative genetic genealogy. There are some misconceptions, for example about the databases available for investigative genetic genealogy: AncestryDNA and 23andme, the two largest databases do not permit access for law enforcement purposes. MyHeritage does not permit the use under their terms of service. GedMatch requires you to opt in to permit your data to be used for law enforcement and FamilyTreeDNA allows you to opt out if you do not wish your data to be used that way.

• Kerry Farmer talked about belonging to many family history societies and possible conflicts of interest with her roles including that for promoting her own genealogy business. She addresses these conflicts by declaring them if she recognises them as they arise and always being aware of what ‘hat’ she is wearing in different situations.

The session was slightly marred by technical issues:

• Those viewing later could neither see the questions posed to the 130 or so viewers in real time nor the see results. Some of the questions also were not worded so as to elicit the information the panel was looking for: the ‘societies’ question should have had as an option ‘belonging to no society’, and the DNA database question should have had as an option ‘to have been tested with multiple databases’.
• Reference was made several times to the chat log but that was not available to later viewers and unless an item raised was directly and coherently addressed was not of relevance to viewers.
• Screen sharing was not always smooth.
• The amount of time devoted issues was sometimes disproportionate to the amount of interest in them.

The RootsTech library has more than 1,500 sessions on 185 topics in over 30 languages. I chose Germany as a research location in my filter to find 51 relevant sessions.

RootsTech sessions continue to be available online even though the conference has ended, a terrific genealogy education resource. There are at least 51 sessions on German genealogy and I plan to work through many of these as I hope to improve my knowledge in this area.

Relatives at RootsTech

RootsTech, first held in 2011, is an annual family history and technology conference and trade show convened by FamilySearch, a nonprofit organization of The Church of Jesus Christ of Latter-day Saints (the Mormons).

Because of the Covid pandemic, in 2021 the conference was conducted online. It had more than a million participants, from 242 countries, who watched more than 2,000 on-demand genealogical class sessions taught by experts, archivists, and family-history companies. (These sessions are still available for viewing.)

I participated in 2021. This year I have signed up again, and I look forward to the 2022 presentations, which begin on 3 March. (Once again, FamilySearch will make these available after the conference.)

This year as part of RootsTech, FamilySearch produced an app for participants to determine whether and how they were related to each other. The app matches RootsTech participants worldwide by comparing the names of their ancestors found in the FamilySearch Family Tree. When a common ancestor is discovered, a participant is shown the names of living relatives and their family connections.

I have about 700 relatives at RootsTech, with the number growing as new participants sign up for the conference. Five hundred of these are from the United States, 9 from Canada, 2 from the UK, and 3 from Australia. About a quarter have not given their location.

My closest relative is a 3rd cousin from Australia, both of us descended from my great great grandfather James Francis Cudmore and his wife Margaret nee Budge. We have corresponded in the past.

James Francis Cudmore

Margaret Cudmore nee Budge.

My next closest cousins at RootsTech are 6th cousins once removed in the United States. Our shared common ancestor was Edward Mainwaring 1709 – 1795, my sixth great grandfather.

Disappointingly, there seems to be an error in the tree and I don’t think we are in fact related.

The family search tree showed Edward Mainwaring 1754 – 1842 (FamilySearch id M2CP-HGK) being the son of Edward Mainwaring 1709 – 1795 (Family search id L4HK-DWJ) and Mary Morgans (FamilySearch id M2XG-FBZ) born Wales (no dates). Mary is said to have married Edward on 8 August 1753 at Kinsham, Herefordshire.

Edward Mainwaring 1709 – 1795 married Sarah Bunbury 29 May 1735 at Whitmore, Staffordshire. They had 8 children, including an Edward (1736 – 1825). The family is well documented, with church records, wills, marriage settlements, and histories. Thee marriage and children are recorded on the FamilySearch tree.

The Edward Mainwaring in the Bishop’s Transcript of the marriage (referenced on FamilySearch) between Edwd Mainwaring and Mary Morgans on 8 August 1753 at Leysters, Herefordshire, is not the same man as the Edward Mainwaring of Whitmore.

Feeling a little deflated that my cousins were incorrectly linked, I set out to collaborate on editing the tree. The FamilySearch tree is one of several major online collaborative trees; I also contribute to Wikitree. The aim of these trees is to have only one profile per person, properly documented.

To correct the tree at FamilySearch I wrote a note attached to Mary Morgan’s profile explaining that the wrong Edward Mainwaring had been linked. The note shows up under a tab labelled ‘Collaborate’. I then removed Edward 1709 – 1795 as the father of Edward 1754 – 1842 and husband of Mary Morgans. I added a new Edward Mainwaring https://www.familysearch.org/tree/person/details/G67M-M97 as a husband of Mary Morgan’s and father to Edward Jr. I don’t know this man’s biographical details other than that he married Mary, so I had to leave the other fields blank. Perhaps some enterprising family historian will discover more about him. I ignored the possible match who is married to someone else; there are a lot of Edward Mainwarings.

Explaining my reasoning on the profile of Mary Morgans

Removing Edward Mainwaring of Whitmore from this family and leaving an explanation

Lastly add another Edward Mainwaring, a new husband for Mary Morgans and father to Edward Mainwaring born 1754

I expected that this change would reduce the number of cousins I have at RootsTech and, sure enough, I dropped from 705 to 667 relatives instantly.

Collaborative trees take work but I believe the result is better than a genealogist can achieve by working alone, and that over time these single family trees will become increasingly accurate.

In the mean time I look forward to finding more cousins and of course to learning from the presentations at RootsTech from the beginning of March.

Relatives at RootsTech is an optional activity that is part of the RootsTech Connect 2022 conference. Attendees can sign up for RootsTech and access some of the classes and sessions without choosing to join Relatives at RootsTech. Attendees who join Relatives at RootsTech can see how they are related to other conference attendees and send a text message to relatives, if desired. The functionality will be discontinued after the conference though you can still stay in contact with people who you have added to a friends list. Currently there are more than 50,000 participants in Relatives at RootsTech, I expect that participant numbers to grow significantly closer to the conference. Are we related?

Some of the speakers at RootsTech in 2022.

Wikitree:

• James Francis Cudmore (1837 – 1912) Family search tree : KC5C-TGP
• Margaret (Budge) Cudmore (1845 – 1912) Family search tree : 2H3D-LTH
• Edward Mainwaring (1709 – 1794) Family search tree : L4HK-DWJ

Disclosure:  I have signed up to be a RootsTech 2022 Influencer and have committed to writing about the conference.