Monday, July 17, 2017

A Precious Pension File


When all the evidence comes together to reveal family relationships, it's an exciting moment. Another Lake researcher finally was able to understand the connections in a document after my recent posts on two women named Precious. She shared with me the document, which is one that I had not seen.

As a quick recap, Precious Moore Weathers and her sister, Elizabeth Moore Muntman, were daughters of Elizabeth Lake Moore. After being orphaned as a toddler, Elizabeth was raised in the household of her (presumed) aunt, Precious Lake York.

Precious York filed for a military pension based on her husband's Civil War service. Wounded at the Battle of Shiloh, John York returned home to Morgan County, Illinois, where he died from his wounds.

There were few birth certificates in Illinois at the time of the Civil War, so the ages of pensioners and minor children needed to be proven via Bible records or through affidavits from neighbors. For elderly soldiers later in life, census lookups were even used to verify age.

Precious had several minor children and in her file is a fascinating affidavit. In July of 1880, a woman named as Lizzie Montman gave an affidavit that listed the names and birth dates of the children of John and Precious York, her aunt. She signed the affidavit as Elisabeth Muntman. The document was witnessed by her sister, Precious Weathers.

One of my theories had been that the 13-year-old Elizabeth in the York household in 1850 was actually Elizabeth Moore. The affidavit confirms there was no Elizabeth York; therefore, the theory holds.

Thank you to the researcher who shared this fascinating look at family members supporting one of their own.

The entire file and this complete document can be found on Fold3.




Sunday, July 16, 2017

Ready, Fire, Aim: Ancestry Misses the Target


Ancestry announced a change to DNA test management late this past Thursday that angered many of their core customers. Effective immediately, only one DNA test can be activated from each Ancestry account. The blog posting where the announcement was made was followed by hundreds of frustrated comments. I share many of the concerns stated by others and won't repeat them here. Rather, let me tell you about my first cousin.

Ro was raised in the eastern US, while I was raised in the west. We've now switched coasts. I can count on two hands the number of times we've seen each other in person. We email and are friends on Facebook, but we're not close. Ro lives on a fixed income, but decided to take a DNA test with Ancestry. We got together last year and she explained something that had just not registered with me before: she was an orphan.

Her father had died when she was in grade school and her mother had placed the children in boarding schools. The family unit was irretrievably broken at that point. Ro and her mother had a tumultuous relationship, but were starting to mend it when tragedy struck. Traveling on icy and treacherous roads, the two were in a horrendous accident. Both were badly hurt. Her mother never fully recovered. She died after lingering and fighting for over two years.

Ro's mother and my father, siblings, were orphaned young. Likewise, both their maternal grandparents (our great-grandparents) had been orphaned. Ro and her siblings had also been orphaned in their 20s. They were the third generation of orphans in four generations. Like many adoptees and orphans, she was curious about her heritage.

Ro had a free Ancestry account under which she registered her DNA test. When her test popped up as a match to mine, I looked over her tree and suggested a couple of changes that would make our trees align. She was able to make simple changes, but did not have an easy way to add the many generations of ancestors that I shared with her. I had done some work on her father's family, also, so had plenty of data to share.

After trying a couple of ways to get my data into her tree, we gave up on doing it the right way and used the dirty way. Ro gave me the password to her Ancestry account. Today her tree has about 100 names more than the number she started with. I maintain (or don't maintain) her tree. If there are questions from other researchers, she sends them to me.

I also have elevated rights for her DNA test. When I first logged into AncestryDNA as Ro, I was appalled at how limited her account was. Having spent as much as $100 for the test, she could only see a few of her top matches. That seems blatantly unfair. Instead, I am the one who reviews her matches and writes notes for them.

Ro also asked for a favor. Could I find any newspaper coverage of that awful car accident? I looked at several newspaper websites, including Newspapers.com (owned by Ancestry), to which I had a subscription at the time. I found some possible matches in that collection, but there was a problem. That particular newspaper was part of the "Publisher Extra" collection. Even with my paid subscription, I couldn't check out the articles without paying additional subscription fees.

In a previous post, I stated that Ancestry wants two things. This new policy shows they want three things:
  1. Your money for subscriptions
  2. Your genealogy data to grow their database
  3. Your DNA, with permission to use it for research
I'll stay with Ancestry for now, but I won't be buying any more DNA test kits from them. We'll all see what effects this policy will bring to the Ancestry landscape.

Two of my distant cousins who are reading this (I hope) might be able to find that newspaper coverage for Ro. One of you moved a couple of years ago from a state near me to a state where we have our shared roots. You are my best hope, as you now live near the accident site. The other cousin may have access to a full Newspapers.com subscription through your FHC. If either of you are willing to try to help Ro learn more about her past, please email me.

Saturday, July 1, 2017

A Confusing Widow


One of the challenges in family history is a woman who is a widow, but looks like an unmarried woman. Not knowing she is a widow, it is easy to make incorrect assumptions and conclusions about her name and her parents and to climb the wrong tree.

With increasing emphasis on DNA matching, such incorrect trees will cause even more confusion and wrong conclusions. In this case (and no doubt many others), the DNA matching could be especially incorrect due to the intermarriages between allied families.

There is no way to entirely guard against the problem. The best defense is to gather every document you can find about the family and question any inconsistency. If you see an inconsistency, try to find other information to support or disprove your conclusion.

The Lake family of Morgan County, Illinois, has such a widow in the extended family. If you search online trees, you will find a woman named Lucinda Lake who married John C Carter on December 24, 1835, in Morgan County, Illinois. Unfortunately, the marriage license refers to her as Miss Lucinda Lake, perpetuating the myth that she was not a widow.

There is a strong clue; however, that she might be a widow. The 1835 Illinois state census shows Lucinda Lake, age 20-30, with two girls aged 0-10. Lucinda is listed next to Lindsey Lake in that census.





There could be other explanations for Lucinda being the head of household, but in this case, the simplest one is correct. Lucinda was the widow of Aaron Lake, which is proven by his probate, though just barely.

On the 11th of July, 1835, Lucinda Lake took out letters of administration for the estate of Aaron Lake, who had died on July 6th. Her bondsmen were John York and Eleazer Skinner. The estate was inventoried on July 18th by Angus McDonald New, Joshua Knapp and Joel Stewart. With the inventory is a list of "property taken by the widow at the appraisement". That single line in the probate file is the only proof that Lucinda was the widow, rather than the daughter, of Aaron Lake.