How Misinformation Can Be Spread via Ancestry Trees

When I was a new family historian, I made a mistake on my Ancestry tree. My 2x-great grandmother was a woman named Mattie, who married my 2x great-grandfather, Andrew Jackson Pike. I knew she later married William T. Adams. My mother knew and had heard about her great-grandfather, Malcolm Argul Pike and knew he had a step-father and half-siblings. Records for Mattie indicated her maiden name was Childress or Childers. The informants on these records would have been her grandson (on Malcolm’s death certificate) or her son Claude Adams (on his Social Security Application). When searching for the marriage of Mattie to A.J. Pike, I found the following record in Tipton County, Tennessee, the birthplace of Malcom Pike.

Marriage License for A.J. Pike and Mattie Fisher, 1878

I was thrilled to have this record because maiden names are typically used in marriage records, and she was almost certainly the informant on her own marriage certificate, so I believed her maiden name was actually Fisher. I added the record to my Ancestry tree and gave her the birth surname of Fisher. I could not find a Mattie Fisher prior to her marriage who fit Mattie’s calculated death date or possible birth states. That should have been a clue.

Less than a year later, when I learned more about thoroughly exhaustive research and how to resolve conflicting evidence, I realized I had never looked for a marriage of Mattie prior to her marriage to A.J. Pike. And that’s when I found this, also in Tipton County:

Marriage license of James Fisher to Mattie Childres in 1877.

I reviewed the timelines of the likely first marriage of Mattie to James Fisher with the marriage to A.J. Pike (they were 9 months apart) and searched for a death record for James. To date, none has been found. To rule out a marriage prior to Mattie before James Fisher, I looked for a married Mattie Childres in the years she would have been old enough to marry and found none. I looked for Mattie Childres in different Childress families in the south and created a long list that I am still working through. I turned up additional conflicting evidence. Another son of Mattie, Ben Adams, said her maiden name was Pike when he applied for a Social Security Card. I looked of birth records for her children (none, they weren’t required in Tennessee at that time and no delayed records have been located). I haven’t been able to find her daughter Luella (Adams) Moss after 1910 or her son Wallace Adams after 1900. I did start to find DNA matches that linked her to the Childres surname and some possible families for her prior to her first marriage, and some matches that fit as descendants of Mattie with no evidence of her in their trees. (It’s possible they descend from Luella. As of this time, none of the Adams men were known to have had families, but that can’t be ruled out.) Mattie became (and still is) my most recent brick wall.

It was appalling to learn how quickly the misinformation I had posted on my Ancestry tree spread. After I discovered my error, I wrote to 14 people on Ancestry who had copied my erroneous information. Only one responded and she was grateful. See below.

Message in Ancestry Messaging System thanking me for letting them know about the correction

At the current time, there are 17 trees on Ancestry that have Mattie with the maiden name of Fisher in their trees. It’s humbling to know that the information is there because of my lack of good research standards.

What do I do to avoid spreading misinformation now?

  • Follow genealogy standards while doing my research. Reasonably exhaustive research and resolution of conflicting information would have prevented this.
  • Avoid sharing information publicly before I am more certain. The difficulty with that approach is that certainty is highly variable when researching mysterious people like Mattie!
  • Share my information on WikiTree. WikiTree acknowledges that profiles are works-in-progress and allows for a more nuanced presentation of information. When I create WikiTree profiles I can use language to describe how sure I am of the research. I can say her maiden name is “likely” Childres or “almost certainly” Childres when I am more sure. I can write a proof argument and attach a PDF to her WikiTree profile if I want to. (See this WikiTree page for my ongoing efforts to disambiguate three men named James Stoker in Kentucky.) I’m still bothered by the stricken out Smith on one of Mattie’s records. Was that just a clerical copying error? Or did Mattie mention the name Smith when she was applying for a marriage license with A.J. Pike? I do have a cluster of Smiths in the Childres genetic network…
  • Keep Ancestry trees private. Unfortunately this does not prevent Ancestry from using the information in a ThruLines hint. And ThruLines sadly tells me that Mattie’s father is someone named J.E. Fisher born in 1820. The error continues to compound!
  • Name my Ancestry tree as a “Working Tree” to let people know it is a work-in-progress. All genealogy is a work-in-progress, but it’s hard to make that clear when trees can be so freely copied without analysis.

And I remember when I am looking at other people’s trees that I need to verify the information myself. And be kind when there are mistakes. After all, I’ve made them, too.

Gaining a Family Treasure: The Barnett Family Bible (or How to Increase the Chances People Will Contact You about Your Ancestors and How to Find Cousins)

Have you ever had a family treasure almost drop into your lap? Recently it happened to me. And it happened to me because I make sure my name and my family tree are publicly accessible. This is the story of how an 1811 Barnett family Bible came into my possession. It’s also a guide to how you can make yourself findable or find people without paying for a membership at any website. But first, some historical notes about research and sharing genealogy from my experience.

From the late 1970s to the late 1990s, I worked on my family history, saving what I learned in file folders and then Reunion (a software program for Mac users where I diligently associated facts with sources). My family history information was held privately and exchanges of information happened through exchanging letters and photocopies with cousins I met through other cousins. When the internet arrived, I joined listservs and bulletin boards to share information about family history. Distant cousins exchanged disks and electronic files. Then membership sites arrived like Ancestry. Currently, family historians can save their family trees and documents in paid membership sites or share that information where the public can access it without the barrier of cost. Find a Grave, FamilySearch, and WikiTree are three examples. All three offer free membership and two (Find a Grave and WikiTree) can be seen by anyone without a membership. The benefits of sharing in publicly accessible places became clear when I received the following message:

Screenshot of an email

What? A family Bible mentioning my ancestors, who were born in the 1700s? Who was James Barnett? Was this really about my family?

Thankfully the seller on ebay had taken photos of the Bible pages with genealogical information and it was enough to reveal that this Bible contained information about my ancestors, John Barnett and Lucy (Matlock) Barnett. It almost certainly belonged to the descendants of their son, James Barnett. Some of the information about my direct ancestors was recorded after the fact but there were children listed that I had not known about, and James Barnett’s descendants were new to me and likely recorded closer to the times of the events. With the help of a friend (an experienced ebay buyer and seller), I purchased the Bible below the posted price. It is now waiting for me at my friend’s home. She has taken better pictures of it, such as the marriage page below.

Barnett Family Bible, portion of the Marriages page

The only reason I found out about this Bible is because I posted a note on John Barnett’s Find a Grave profile as shown below.

My 5x-great grandfather, John Barnett on Find a Grave

Whenever I complete a WikiTree profile of an ancestor, like John Barnett, I add a sunflower and a link to the WikiTree profile to the Flowers page at Find a Grave. I mention my relationship to the person on the memorial to help cousins find me and to give them the opportunity to find more information about our shared ancestor through the WikiTree link. Without this simple sunflower post, I would not have been contacted about the Barnett Bible.

That brings us to the first opportunity to make you and your family visible: Find a Grave. anyone can look at Find a Grave, and you need a membership to contribute. Membership is free and you can be visible by adding flowers and links like I do. You can also be helpful by connecting family members to each other, suggesting edits, and contributing photos. Note: Find a Grave was purchased by Ancestry in 2013.

In addition to Find a Grave, I’ve also made myself visible on FamilySearch and WikiTree.

On FamilySearch, you can make yourself visible by adding sources (number 1 in image below), posting notes or discussions in the collaborate tab, or sharing memories (3).

John Barnett on FamilySearch

FamilySearch users can be messaged by clicking on their user name, and it may be worthwhile to click on people who have been editing members of your family. They could be volunteers or they could be cousins.

Under collaborate, you can choose to write a note to other researchers or have a discussion about a topic as shown below.

Family Search Collaborate tab

The person who posted the Note above seemed pretty frustrated, so I chose to message them about the Barnett family Bible as an additional source.

The message system at FamilySearch

I also decided to add a PDF of the transcribed Barnett Family Bible to the Memories tab. I will add photographs once I have a chance to take them myself.

John Barnett with the Bible Transcription added as a PDF to the Memories Tab

Now that I’ve done several things to help people find me, I can now search for cousins who descend from John Barnett. Navigate to the “View Tree” tab for any ancestor.

Navigation to the Tree Tab at FamilySearch

In the tree tab you can choose how to view the tree. The descendants view incorporates down arrows to open additional detail, eventually bringing you to living descendants who have memberships at FamilySearch. Instead of having you scroll down an incredibly long page, I’ve put three images side-by-side here to show the path to me. (Usually I would be looking for other descendants, but you get the idea!)

Descendant view on FamilySearch from John Barnett to me

The third option, and my favourite way to be findable or to find people is through WikiTree. In order for these options to work, you need to sign up for WikiTree and connect yourself to the tree. There are three main ways people may find you (or you can find people) on WikiTree: Using the descendants tab, managing ancestor profiles, and DNA Connections. I’ve numbered them in the image below. (In all of the images below, purple hypertext indicates I’ve clicked on a link in the past.) This is the WikiTree profile for John Barnett .

WikiTree profile of John Barnett

The descendants tab adds a descendant view to the profile, and you can find more recent generations using the blue arrow next to a named descendant, almost identical to the descendant view on FamilySearch. I’ve scrolled down a bit to find my branch of the family. Lucy F. (Walker) Key is my 2x great-grandmother and the great-granddaughter of John Barnett. The blue arrow icon next to my grandfather, Lindell Scott Johnson, indicates there are descendants below him. (This arrow will be a dark pink for a female ancestor.) You can also see a green DNA checkmark, indicating there is a DNA tester in this line who has confirmed this relationship. Handy information for your research!

More descendants of John Barnett in the descendant diagram, down to my grandfather, Lindell Scott Johnson

Clicking on the blue arrow icon opens the descendants tab on Lindell’s profile. You will see the green DNA checkmark next to my mother and me.

The descendancy diagram ending with me

The second way people may find you is if you manage a profile. You can click on the connections icon next to the name of the profile manager to see their connection. I’m using the profile of Lindell’s mother, Lillie May (Key) Johnson, for this example.

Profile manager Connections icon

The image that comes up shows the connections with green boxes indicating a biological connection. If I weren’t a direct descendant, the boxes would switch to yellow indicating a connection through marriage.

Connection of the profile manager to the person being profiled on WikiTree

The third way to make sure you are found on WikiTree is to notify WikiTree that you have done DNA testing so that you will show up in the DNA Connections box on a profile. WikiTree is not a DNA website and the only DNA information available is shared by WikiTree genealogists voluntarily.

Many descendants of John Barnett have taken DNA tests and shared information on WikiTree. The DNA Connections box is arranged with those who inherited the most DNA from John Barnett at the top. The first person on the list is my mother.

DNA Connections for John Barnett.

If you are finding cousins, you can click on any name and you will be taken to their profile where you can message them with one click. They will receive an email with your message. If you want to be on this list, you need to let WikiTree know that you have done DNA testing. To do that, go to your profile page and click on the Add Menu at the top.

Use the Add menu to Add DNA test information to your WikiTree profile

That opens your DNA Tests page where you can either edit or remove existing tests or add new tests. Click on “Add New Test.”

DNA Tests Menu at WikiTree

After you click on the button you will fill out the boxes to add your test. There are templates for Ancestry, 23andMe, FamilyTreeDNA, MyHeritage and GEDmatch. Include as much information as you want in the boxes.

Add information for each DNA test you’ve completed

After you’ve clicked the “Add Test” button, your test will be added to your ancestors profiles. It may take a day for it to populate throughout the tree. After your DNA has been added, anyone looking at your ancestor on WikiTree will see your name associated with that ancestor up to 6x great-grandparents for autosomal DNA. YDNA and mtDNA will be populated to all of your direct paternal or maternal ancestors that are associated with that test.

I hope this review of three ways to be findable and find cousins on publicly available websites has been useful to you. And I also hope you were doing the genealogy happy dance with me when the Bible came my way! I wish for you the same good fortune through being “out there in public” with your research.

WikiTree Has a New Look!

Over the past year, a team of paid consultants and volunteer developers at WikiTree created an updated look for WikiTree. WikiTree, the free, one-world tree, is the place I share my best genealogical research. Check out my profile to see how active I am on WikiTree. I joined in 2017 and since then I have edited hundreds of profiles, created Free Space Pages, and I manage over 350 profiles. I’ve used the old system and the new one to edit and create profiles and Free Space Pages. I’m very familiar with WikiTree, including its strengths and shortcomings.

WikiTree is a publicly available website and far more likely to outlast me than any other place my research resides. WikiTree is not known for flash. After all, without income from memberships (WikiTree is financed by unobtrusive ads that are only shown to non-members or members who are not logged in), WikiTree lacks the budget power of Ancestry, MyHeritage, or software companies. They have done an amazing job with the redesign.

Let’s take a look at some of the updates on the profile of Arthur Hilton. I’m his two-times-great grand-niece. He died young, and he’s one of the people I honour at WikiTree.

Side-by-side comparison of old and new

The overall look is cleaner and better organized. The huge grey border (a total waste of space) is gone and there’s a better balance between the two columns. The larger font is easier to read and the use of colour makes sense. See that blue box? It’s a visual cue that I’m looking at the profile of a biological male. The hypertext is green and links you have clicked are purple.

Wiki ID and menus

The area for the WikiTree ID and dropdown menus has been streamlined and cleaned up. The menus are more visible with the larger font and the menus themselves contain less clutter. (The menus are not shown here! Click on one and check them out!)

Copyable text options

The visibility of useful copyable text options is perfect! In the old version, they were almost invisible in tiny green font. They are now clearly marked with a new copy icon, familiar from other websites. I use these links when sharing profiles in emails, adding links within profiles, and in my research logs. And if you like to cite WikiTree, you can do that here with one click.

Menu placement and improved icons

Like all good websites, there’s usually more than one way to navigate. This menu in grey background is a redesigned tab menu. It uses icons and text to move commonly used features and actions together. The more experienced WikiTree user wants to access profiles and features quickly without scrolling, and here they are. I’m referring to this as the “Quick Menu.” Well done, design team! I love the simple navigation arrows and ability to jump to the part of the profile I want to see, (including the ancestors and descendants tabs), the “edit” pencil, the profile change history icon, familiar privacy icon (padlock), and the new Tree apps icon.

Key details and relationships

Information that was small and difficult to parse is now separated with better placement in the profile. Key details (birth and death with locations and certainty indicators) now appears immediately below the larger, improved name block. Relationship information is in the shaded block, blue for Arthur, a biological male.

Finding the profile manager is also easier.

The new profile manager section

The profile manager formerly appeared in small font in the crowded area on the left. It now has its own shaded block on the right. In addition to allowing an instant email to the profile manager, there is now a redesigned “connections” icon which allows you to see how the profile manager is connected to the profile. In the past, I needed to go to another part of WikiTree to see this information. Now when I contact a profile manager, I may gain insight of their motivation to create or manage the profile.

The next improvement may be lost on many WikiTreer users.

Better placement of Ancestors and Problems/Questions buttons

As part of the Ambassador team at WikiTree and someone who is often demonstrating WikiTree, I appreciate that the Ancestors Button and Problems/Questions buttons are no longer in a similar position with the same design. Note: There would be a descendants button on the “old” version if Arthur had descendants. The new design allows the user to access ancestors or descendants using the icon in the grey Quick Menu bar or using the clearly visible tab.

New Ancestor View

Either option opens a family tree for Arthur, also with an improved look and feel. It features separated colour blocks, cleaner font and icons, and arrows to navigate further back in the tree. The Descendants view has similar improvements.

Back on the profile page, it’s time to look at the treatment of DNA in the new profile.

DNA Connections

DNA Connections can now be accessed via the Quick Menu in grey and is found in a familiar location along the right, now below a redesigned photo section. Again, the text block is cleaner, easier to read, and only contains the information it needs to contain.

Images are now Photos

The old images block sometimes made a simple profile like Arthur’s lopsided, with the photos dominating the right side. A new photo block allows you to toggle through the uploaded images using a navigation arrow to the side of each photo. You can also navigate quickly to the “Upload Photos” page, which has also received an update and is cleaner and easier to use. Again, kudos to the Design Team and programmers. They went over this website with a fine-toothed comb!

Collaboration stands out

In the past, the use of yellow background wasn’t clear to me. Now yellow highlights collaboration and ongoing research. The collaboration language is friendly and clear. The research block encourages people to check out the incredibly useful WikiTree Sourcer Extension (which works great with the new updates.)

Comments, Matches and Merges, and useful Connection and Relationship Information

Scrolling down, you can see how the new design makes better use of space – there is not a huge empty block to the left. In profiles with a longer biography, there will be blank space to the smaller right side of the page. The Comments and Match and Merge sections have gotten the cleaner, pithier treatment, and thankfully, the text with “See your connection or your genealogical relationship with Arthur” is now separated from the Featured Connections text.

Even the footer is now easier to read and more pleasing to the eye.

I know this is a tiny glimpse of all that was accomplished with this redesign, and there’s much more I haven’t noticed yet. I look forward to finding the features I’ve missed, and new features that may replace what I’ve shown here.

Well done, WikiTree!

And if you’re new to WikiTree, welcome! Check out the Help links on WikiTree and useful information at the WikiTree YouTube channel.

Reflecting on 2023 and gearing up for 2024

It’s been a busy year in genetic genealogy! I’m getting a head start on reviewing the year as I plan for 2024.

You can still find me as a coach over at Your DNA Guide. Through that opportunity, I’ve connected with many people learning how powerful DNA can be to support their understanding of their family and themselves.

In addition to creating course content and coaching people at Your DNA Guide, I’ve worked with clients who are surfacing their family’s involvement in slavery. It’s an honour and privilege to support efforts to face history. Much of this work is on WikiTree as part of the US Black Heritage Project.

I’ve also enjoyed many great educational opportunities such as the 15th Annual Conference on Genetic Genealogy and the National Genealogical Society’s course on Empowering Genealogists with AI.

I’ve also provided educational opportunities for WikiTree, the Linked Descendants group at Coming to the Table, and the Indiana African American Genealogy Group. I am doing one more presentation this year for the Virtual Genealogical Association.

Next year, I’m looking forward to revamping this website, offering a hands-on course for people getting started with their DNA, and being part of an instructor team at the Genealogical Research Institute of Pittsburgh for a course coordinated by my teammate at Your DNA Guide, Kelli Bergheimer. I’ll be coaching participants in all of the Your DNA Guide courses and supporting other Academy Offerings. As part of the Your DNA Guide team, I will be attending RootsTech. I’ll be speaking for a couple of genealogy societies and expect to have a chance to work with others as the year unfolds.

Working on my own genealogy has included moving more of my family to WikiTree. This includes the ancestors of my grandchildren, which has given me an opportunity to work with more DNA testers and explore records in new geographic areas! I continue to make slow progress on some of my own DNA puzzles.

Thanks for following me on this journey!

Research Like a Pro Week 2: Timeline and Citations

This is the second entry about my experience doing a research project while I serve as a peer group leader for the Research Like a Pro Study Group hosted by Diana Elder and Nicole Dyer of Family Locket.

Updating the Research Objective

With the assistance of my peers, I revised my research objective to be:

This project seeks to uniquely identify each James Stoker in Bourbon County, Kentucky from approximately 1820 to 1880. 

  • James Stoker filed a bond to marry Polly Ross on 9 December 1822 in Bourbon County.
  • Jas. Stoker, age 79, lived in the household of his son-in-law, Silas. Cleaver, in 1880 in Millersburg, Bourbon County. 
  • James H. Stoker, presumed age 40-50, lived in Bourbon County in 1830.

The task this week was two-fold: create a timeline of known facts and to cite them properly.

Timeline

Creating a timeline involves taking everything already known about the research topic and arranging it in order. This provides an opportunity to see new patterns and identify gaps in the research. I am using Airtable to organize my research.

I entered the documents I had about the various James Stokers into the timeline tab in Airtable. My timeline has the following fields (columns): Event, Stoker as named in record, Stoker sorting tests (more on this later), Date (text field YYYY-MM-DD with as much information as is known), Place (Single-select field type written State, County, Town using 2 letter state abbreviations), Type (of event, another single-select field with choices like birth, census, death), URL (to the source document), Source citation (yes, the entire citation. This is the master location for the citation), Details (an abstract of the information in the source), FANS (link to the FAN Club table), Notes (thoughts about the source).\

I included all the known events for my ancestor James Stoker since I had eight census records for him (two are state censuses). I have a birth state, birth date calculated from his cemetery marker, marriage date and place, death and cemetery information.

Since this is a project to distinguish different people of the same/similar name, I am testing using two columns for name, one as it appears in the record, and the second column to try different ways to sort the James Stokers. Place and time will guide the sorting.

Citations

Complete source citations form the foundation for genealogical analysis. Fortunately, I formed good habits citing my sources starting in 1998 when I was enrolled in the certificate program in Family History and Genealogy at the University of Washington. Citations weren’t as exacting then as they are now. Citation is also required in my other field, health care, and I worked in research for several years and co-authored scientific publications. Transitioning to the professional genealogist role meant switching to humanities-style citations and meeting genealogical standards. I frequently refer to the Chicago Manual of Style to manage the mechanics of humanities writing and citations. I refer to Elizabeth Shown Mill’s comprehensive book, Evidence Explained, and Thomas Jones’ Mastering Genealogical Documentation as needed.

Using a template for genealogical citations made it easier for me to meet the genealogical standards. I have an Airtable Citation Guide accessible from my bookmarks bar. It is based on the Research Like a Pro templates. The fields in my base are Name (type of source, like Birth Certificate Original, FindAGrave, Pension File), Category (birth, cemetery, military, for example), template (see example below), Citation Example (a completed citation of that type), Short Form (when citing the source multiple times.) I tend to put more in citations than others (like complete dates instead of just years and complete stable URLs) because I can always shorten the citation if needed.

Here is an example of a template for FindAGrave:

Find A Grave, database and images ([Stable URL] : accessed [DD Month YYYY]), memorial [NNNNN], [Name As Appears], ([BBBB-DDDD]), gravestone photographed by [Contributor], citing [Name of Cemetery, Town, County, State].

And the 1921 Canadian Census at Library and Archives Canada:

1921 Census, [Province], [name] District [#], Enumeration Sub-district [#], page [#], dwelling [#], household [#], [Name as Written]; database with images Library and Archives Canada ([stable URL] : accessed [DD Month YYYY]); citing LAC microfilm [#].

Creating the timeline and the source citations supports the next part of the research process, analyzing the evidence.