When I first saw Ancestry's TreeTags, I was intrigued by the categories. The idea is to indicate the research status of each ancestor.
Tag, You're It!
I like "unverified" and "hypothesis" because they are a great way to tag ancestors who I've either found on some document and been unable to verify further, or ancestors who I suspect (but can't yet prove) are related in a certain way to my tree. Extremely useful.
"Actively researching" and "brick wall" seem less useful tags for my purposes. "Verified" is, however, highly useful for situations where I've got clear, solid evidence for these ancestors and can verify how they are actually related to my family.
What Does Complete Mean?
But after 21 years of active research, the word "complete" is not in my #genealogy vocabulary and I doubt I'll ever tag any ancestor in this way.
Ancestry defines "complete" as: "I am confident that I have executed thorough searches to help answer my questions."
As thorough as my research may be, new records become available all the time. And that's not all. DNA is also changing the research landscape.
So although I may have answered my current questions, and may even have amassed a huge amount of data through research, I don't view any ancestor as completely researched.
New Records Galore
Just this month, for instance, Family Search posted a database of 34 million U.S. obituaries from GenealogyBank, 1980-2014. Woo-hoo! I'm searching for the names of cousins, aunts, and uncles who died in the past 40 years. Maybe an obit will reveal a previously unknown spouse or challenge my knowledge of that person's life in some other way.
Family Search also posted databases of Cook County, Illinois births-marriages-deaths from the 1870s into the 20th century, as late as 1994 for the deaths. Another woo-hoo, as I search for ancestors who lived or died in Chicago. Found two already.
I may stop researching some ancestors for a while, focusing on others who I know less about or certain ancestors I have a special interest in, but I can't imagine tagging any ancestor (even my parents) as "complete."
What about you?
PS: To see the very latest collections on Family Search, go to the collections page here and sort by "last updated" (on the far right).
Adventures in #Genealogy . . . learning new methodology, finding out about ancestors, documenting #FamilyHistory, and connecting with cousins! Now on BlueSky as @climbingfamilytree.bsky.social
Pages
- Home
- Wm Tyler Bentley story
- Isaac & Henrietta Birk's story
- Abraham & Annie Berk's Story
- Farkas & Kunstler, Hungary
- Mary A. Demarest's story
- Rachel & Jonah Jacobs
- Robt & Mary Larimer's story
- Meyer & Tillie Mahler's story
- McClure, Donegal
- Wood family, Ohio
- McKibbin, Larimer, Work
- Schwartz family, Ungvar
- Steiner & Rinehart
- John & Mary Slatter's story
- MY GENEALOGY PRESENTATIONS
Showing posts with label MyTreeTags. Show all posts
Showing posts with label MyTreeTags. Show all posts
Tuesday, May 21, 2019
Tuesday, March 12, 2019
Cleaning Up Online Trees, One Ancestor at a Time
One ancestor at a time. Because I use my Ancestry trees as my main tree (and sync to my RootsMagic software as backup, then backup my backup), I'm cleaning up my online trees. (Also known as a Genealogy Go-Over.)
Trying to be systematic, I'm working backward from my husband on his tree (and from me on my tree).
As shown above on hubby's grandma, my goal is to have a MyTreeTag for each ancestor AND sources attached as media for each main fact.*
My process, generation by generation, is:
- Starting with parents and grandparents, I'm adding a MyTreeTag (new Ancestry feature) to indicate that these people are verified. Ancestry defines that as "I have done my best to verify the facts of this ancestor’s life with records which are attached." All true. I'm reluctant to say "Complete" because, despite thorough research, something new is liable to pop up someday. But verified indicates I've attached proper sources and used them to support the facts in the ancestor's timeline.
- When I don't have enough records attached, I'm doing a search to turn up more records. If little shows up, I'm tagging these ancestors actively researching or, in some cases, unverified. Several are, unfortunately, still hypothesis, meaning I'm still testing whether they truly belong where I put them on the tree.
- Ancestor by ancestor, I'm taking a screen shot of each source and uploading it as media visible by anyone who wants to see my source for a given fact. This makes my sources public and viewable. At a glance, someone can click and see a birth, marriage, or death cert--and save it or download it if desired. I don't mind sharing records I've spent money on! Others have been generous enough to do this, and I'm paying it forward by sharing mine.
This is a good project for when I have 10 minutes here or 10 minutes there. Inch by inch, making progress.
*UPDATE: Before attaching any sources as images visible on public trees, must check that they will not violate copyright or terms of service for the site.
Monday, March 4, 2019
Trying ThruLines and MyTreeTags
The new Ancestry ThruLines feature is a step forward in understanding how DNA matches *might* fit on a family tree. This feature also suggests "potential ancestors" to add to a tree.
The key is to understand that names, dates, relationships all depend on the accuracy of other people's trees. As with any info found online or provided by someone else, it's up to me to investigate and verify or disprove each potential ancestor and possible DNA match.
Pick Your Ancestor
ThruLines is arranged by most recent ancestor and stretches back to most distant ancestor. Above, a snippet of the 100 ancestors/"potential ancestors" on my husband's ThruLines page. That makes it easy to investigate links to specific ancestors of interest. I can be as systematic as I like in drilling down into my husband's father's side or mother's side, in a particular generation.
As shown, one of these "potential ancestors" is not marked as male or female, and is actually "private" because he or she is listed on a family tree not made public by the owner.
How Private?
Well, not that private. I blocked out the info, but it was easy to figure out exactly who this "potential ancestor" was and the gender, too, without contacting the owner of the private tree. It was listed in the "private tree" notification above.
To check, I returned to my tree and looked at the outstanding hints for this branch. One second later, I had the details from sources other than the private tree, sources more objective and verifiable. So it actually helped me get a generation back. Unfortunately, there were NO DNA matches associated with this ancestor (nor for the spouse).
And in case I wasn't sure, right next to this "private" "potential ancestor" was listed his wife, Hannah O'Killey. Just in time for St. Paddy's Day, a possible new Irish ancestor to research and confirm.
Interestingly, the person who posted Hannah O'Killey's info on a public tree is NOT a DNA match for my husband, which is a disappointment and raises the question of whether this is an actual ancestor for one or both of us. My husband has no DNA matches through Hannah, according to Ancestry. Hmm.
Finding a Match
To find an actual DNA match in ThruLines, I started at the most recent ancestor and worked my way backward to hubby's great-granddaddy, Thomas Haskell Wood. That's where I finally found two cousins previously unknown to me, each of whom had more than 20 centimorgans in common with my husband.
Although neither of these cousins had anything new on their trees, at least I now know who they are and can be in touch to share info.
For the vast majority of the 100 ancestors on hubby's ThruLines page, Ancestry shows NO DNA matches.
Check Those TreeTags
Working through the ancestors on my own ThruLines page, it quickly became clear that my "potential ancestors" were highly speculative. I noticed suggested ancestors plucked from trees I already knew were not supported by good sources.
Here's where Ancestry's other new feature, MyTreeTags, would be very, very useful.
The idea is to be able to indicate the research status of a particular person on a tree. For instance, I could note that someone is a "hypothesis" (meaning I'm testing whether someone fits, based on DNA or other evidence).
Or I could note someone is "unverified" (meaning I got the info from somewhere but have done nothing to check its accuracy).
After looking, I can see that some of the trees that appear in hints or "potential ancestor" suggestions have inaccurate info and few if any sources other than other trees.
To be helpful, I've contacted tree owners in the past to say, for example, that although my grandma is shown on their tree, it's highly unlikely that she is actually related to the people on their tree. Dates, places, names don't add up, I point out tactfully. I invite them to please look at my tree and the documented evidence that proves who she is. Of course, I can't rule out that maybe there's something I don't know about my grandma?!
Usually I hear nothing, or I get a note saying their tree is a work in progress, with hypotheticals. Or the note says the tree is being built for a friend who had a couple of clues, and my info will be passed along to the friend for consideration. Those trees are often left as is, unfortunately.
As I work on my public trees, I'm going to try to use MyTreeTags to alert others when someone is a hypothesis or unverified, in particular, as a red flag to verify before accepting anything as a fact!
The key is to understand that names, dates, relationships all depend on the accuracy of other people's trees. As with any info found online or provided by someone else, it's up to me to investigate and verify or disprove each potential ancestor and possible DNA match.
Pick Your Ancestor
ThruLines is arranged by most recent ancestor and stretches back to most distant ancestor. Above, a snippet of the 100 ancestors/"potential ancestors" on my husband's ThruLines page. That makes it easy to investigate links to specific ancestors of interest. I can be as systematic as I like in drilling down into my husband's father's side or mother's side, in a particular generation.
As shown, one of these "potential ancestors" is not marked as male or female, and is actually "private" because he or she is listed on a family tree not made public by the owner.
How Private?
Well, not that private. I blocked out the info, but it was easy to figure out exactly who this "potential ancestor" was and the gender, too, without contacting the owner of the private tree. It was listed in the "private tree" notification above.
To check, I returned to my tree and looked at the outstanding hints for this branch. One second later, I had the details from sources other than the private tree, sources more objective and verifiable. So it actually helped me get a generation back. Unfortunately, there were NO DNA matches associated with this ancestor (nor for the spouse).
And in case I wasn't sure, right next to this "private" "potential ancestor" was listed his wife, Hannah O'Killey. Just in time for St. Paddy's Day, a possible new Irish ancestor to research and confirm.
Interestingly, the person who posted Hannah O'Killey's info on a public tree is NOT a DNA match for my husband, which is a disappointment and raises the question of whether this is an actual ancestor for one or both of us. My husband has no DNA matches through Hannah, according to Ancestry. Hmm.
Finding a Match
To find an actual DNA match in ThruLines, I started at the most recent ancestor and worked my way backward to hubby's great-granddaddy, Thomas Haskell Wood. That's where I finally found two cousins previously unknown to me, each of whom had more than 20 centimorgans in common with my husband.
Although neither of these cousins had anything new on their trees, at least I now know who they are and can be in touch to share info.
For the vast majority of the 100 ancestors on hubby's ThruLines page, Ancestry shows NO DNA matches.
Check Those TreeTags
Working through the ancestors on my own ThruLines page, it quickly became clear that my "potential ancestors" were highly speculative. I noticed suggested ancestors plucked from trees I already knew were not supported by good sources.
Here's where Ancestry's other new feature, MyTreeTags, would be very, very useful.
The idea is to be able to indicate the research status of a particular person on a tree. For instance, I could note that someone is a "hypothesis" (meaning I'm testing whether someone fits, based on DNA or other evidence).
Or I could note someone is "unverified" (meaning I got the info from somewhere but have done nothing to check its accuracy).
After looking, I can see that some of the trees that appear in hints or "potential ancestor" suggestions have inaccurate info and few if any sources other than other trees.
To be helpful, I've contacted tree owners in the past to say, for example, that although my grandma is shown on their tree, it's highly unlikely that she is actually related to the people on their tree. Dates, places, names don't add up, I point out tactfully. I invite them to please look at my tree and the documented evidence that proves who she is. Of course, I can't rule out that maybe there's something I don't know about my grandma?!
Usually I hear nothing, or I get a note saying their tree is a work in progress, with hypotheticals. Or the note says the tree is being built for a friend who had a couple of clues, and my info will be passed along to the friend for consideration. Those trees are often left as is, unfortunately.
As I work on my public trees, I'm going to try to use MyTreeTags to alert others when someone is a hypothesis or unverified, in particular, as a red flag to verify before accepting anything as a fact!
Subscribe to:
Posts (Atom)