Sunday, February 16, 2020

What if it IS my Circus?


Sometimes, we run into messy stuff when researching our family history. Face it, if life can sometimes be messy, so can the narrative that flows out of our own family's history. And sometimes, the mess gets so confusing that we—or someone else following the same trail—can get thrown off track.

I've run into that problem before, most recently back at the end of last year, when I had two different genealogy companies yelling at me that I had the wrong wife for my Aaron Broyles. (No, as it turned out, I didn't; mine was long gone when the other Aaron—and the specific wife that had been mentioned—still lived in that other state everyone was insisting on.)

My response, once I put together my draft of a proof argument, was to just leave it alone. How could I first find all those other subscribers at two different companies who insisted otherwise, and then convince them of their error? I've often learned that no good deed goes unpunished, and I didn't want to try and prove that maxim wrong—at least, not in this instance. And, as my husband often likes to say, "Not my circus; not my monkeys." I left it alone.

But just this weekend, I ran across another messy research problem. It involved a fourth cousin once removed—removed far enough, that is, to be someone I wasn't personally acquainted with, but close enough to possibly show up as a DNA match to me. This woman's life story apparently included some sad or difficult episodes, and I'm sure there would be plenty to read between the lines of the few documents I was able to glean on her life's trajectory.

She was married at least twice, the first time to a man who eventually ended up in their state's "reformatory" institution, and the second time, when she was well into her thirties, to a man whom she left a widower when she died fifteen years later.

The problem was this: in all the census records where I found her with the first husband—in 1920 and 1930—there was never any mention of children. But by the time of the 1940 census, suddenly she and her new husband had a fifteen year old daughter, listed with the surname of the second husband.

Obviously, my question was: who were the actual parents? This second husband had never been married before, and all previous census records showed him living alone with his own widowed father. All previous census records for the wife showed her living alone with her first husband—with no children. Could this have been an adopted child? A child of a now-deceased sibling of one of the adults?

Obviously, a lot can unfold in the space of the ten years in between two census enumerations. There is probably quite a messy story that evolved in a decade's time, in this family's case. Of course, I tried my hardest to piece together the story, looking in every direction, both time-wise and relative-wise.

This is just one instance of the many types of confusing research clues we may encounter as we piece together the stories of our own families over the generations. And it brings up a question. What do we do when we find others have got the facts badly jumbled? Do we just walk away with a shrug, spouting that old Polish saying, "Not my circus; not my monkeys"?

What if it is our circus?

Thinking this through, I had to go back and revisit the case of mistaken identities for the two Aaron Broyles men in my mother's line. Do I really just leave everyone else thinking they had those details right? Or do I speak up?

That's a question that came up in a family history workshop I was teaching yesterday. In the past, I would have just said, yeah, leave it alone. Forget those sayings about the monkeys; how about this one: you can bring a horse to water, but you can't make it drink. Some people get really incensed about being approached, out of the blue, to inform them that they got something wrong. Especially if it concerns their own family.

On the other hand, the thoughtful people in my class yesterday wondered if there might be other ways to broach the subject and offer a correct version of the facts. And that is quite possible. After all, while we can't change someone else's tree, we certainly can exhibit correct documentation on our own tree. More than that, we can edit our entries to add brief statements on why we chose one version of the story over another one. After all, we do have control over our own public trees posted at such venues as Ancestry.com. And on the universal tree in places like FamilySearch.org, corrections can be made upon producing the determining documentation, so that all can benefit from that information.

While it still may earn you not much more than the ire of a total stranger if you go correcting other people's trees, the situation is far different when you make the case clearer on your own turf. By adding notes, comments, and listing resources on our own trees, we can publicly introduce others to our thinking process and provide evidence to support our contentions about specific family links different than the status-quo mistakes on other trees. In addition, that can become a way to flag the situation and bring it to the attention of researchers who don't, yet, even know about such a discrepancy.

People do take a look at other subscribers' trees. Though we can't necessarily make everyone look at our mini-proof arguments posted on our trees, by providing that information publicly, we are still making our contribution toward making the right lines of reasoning available to a wider audience. Hopefully, some people will be observant enough to take action and likewise correct their own tree.

While I don't—yet—think it is our responsibility to correct all the research wrongs in the world, I do see the pursuit of family history to be a collective effort. We do share what we've found with each other, even if passively (and perhaps even unwittingly). In that one small way, I've come to see I've needed a slight attitude adjustment to realize that, yes, in some cases, it is my circus—and by example, I can make that incremental contribution towards the collective betterment of the record-keeping for the family lines I'm most concerned about.

12 comments:

  1. And just when I thought I will leave Americo Thomas on the Family Search Tree for the third entry..... you have my brain going on how to get that FIXED......

    ReplyDelete
    Replies
    1. I think we all have some examples which need revisiting, too. Please feel free to share your thoughts, now that this has got your "brain going" on some ideas.

      Delete
  2. Very nice post - instructive, as usual. On a somewhat related thought, I hope nothing ever happens to Ancestry Dot Com to bring it crashing down. People have put so much work into it.

    ReplyDelete
    Replies
    1. That is certainly an ominous thought, Lisa--one far from ever happening, hopefully, but also one which requires some contingency planning. I think that was why such a howl of protest went up, a few years back when Ancestry decided to disinvest itself of its FamilyTreeMaker product: people instinctively saw the need to have a desktop-resident program in order to self-manage those family trees which represent such an investment of our own time and talents.

      Yes, it was convenient to sync the Ancestry online tree with the FTM desktop-based program, and yes, it was a pain to have to wait two years or so until the new proprietor of the FTM brand worked out all the bugs, but the real point is: people need to be the keepers of their own research work, not just be the "renters" of space in the cloud where someone else currently keeps their tree safe for them.

      You are absolutely right, Lisa: people have put so much work into their research. We need to never lose track of that investment. It is irreplaceable.

      Delete
    2. I worry about that, too. So many of my students only have their genealogy work on the site and nothing on their home computers--no genie program, no documents. That is the one thing I try to get them to do--buy a program and download their documents.

      Delete
    3. Lisa, that is indeed an important aspect to add to genealogy classes--at least in my opinion. And then, there is always the point that not everyone wishes to continue paying subscription rates for an online tree. It is always best to "own" one's own work.

      Delete
  3. Yes make notes in your own family tree, but I would still send an email to the tree holder with my thoughts!

    ReplyDelete
    Replies
    1. Yes, that would be the polite thing to do. And in some cases, I'll do just that. In others--especially with those cut-and-paste type of genealogists--the mistake can be multiplied to dozens of other trees, making that emailing process rather tedious. I just found another example of that tonight, and just bit my tongue...

      Delete
  4. Great post. I agree, the best thing to do is to write your own proofs and post them on your own tree. They will be found.

    ReplyDelete
    Replies
    1. I am always delighted when my "cousin bait" works. Sometimes, it takes years, but yes, things eventually get found.

      Delete
  5. Definitely document the correct information in your tree and send the correct information to those who have posted the wrong information. When (not if), they reject it and don't want to examine your evidence, then you can leave it go. I had the same situation where I have the documentary evidence that the Tom Doran of Junction, Texas infamy was my great-great-granduncle, who was born in Ireland, grew up in Carthage, Illinois and served on the Union side of the Civil War before moving to Texas and got involved in a bit of trouble. The Tom Doran that was born in Alabama and grew up in San Saba, Texas and served on the Confederate side was not the Tom Doran that was killed in Junction. I had a discussion with someone from Junction that was related to the one from Alabama that insisted it was her relative that was involved in the Junction story. I presented her with the evidence, including the Civil War widow's pension file of the Junction outlaw's widow where she stated directly that he grew up in Carthage, Illinois and served for the Union. The other person refused to acknowledge they even saw the proof. I just have to leave it as it is, knowing I tried.

    ReplyDelete
    Replies
    1. Matt, thanks for sharing that example--hopefully, someone will find your comment here in the future and may even find the recounting of it helpful!

      Those are the type of experiences that I think a lot of us have had, which make us weary of trying to correct the record. There are many ancestors with very similar circumstances--same names, year of birth, town of origin (for instance, two cousins)--that can easily be confused for each other. Those who really want to know will be glad to receive the documentation and proof arguments. We need to be happy with that, and just leave the other be, as you discovered in your own experience.

      Delete

Related Posts Plugin for WordPress, Blogger...