• Join - It's Free

Jonathan Parsons - Wrong Richard P.

Started by Private User on Monday, September 7, 2015
Problem with this page?

Participants:

  • Private User
    Geni member
  • Geni Pro
  • Private User
    Geni Pro

Profiles Mentioned:

Showing all 9 posts

Someone molested Jonathan' paternal line. He was born in 1813, and his great grandfather RP was born about 1720, not his father Richard Parsons. So, in my line it goes Jonathan, Richard, John, Richard 1720. Someone made a mess by merging the two Richards ( and probably jumping to a concussion that Jonathan was John, sons of the respective Richards -- taking no notice of the 93 year gap between Jonathan and his "father".

Jonathan Parsons 1813 is my ffmmf via Nancy Parsons Dixon, then Emily Dixon Flowers, who I knew.

I think we're getting there. You were right & this was totally bolloxed up. It doesn't help that it's "out there" that Betsey Feathers was born 1720 - no, she wasn't.:)

Could I trouble you to re enter Jonathan's parents & grandparents? I'd rather have your dates & locations, because there's a confusion in Wilkes NC I think.

Rickey, you should hear about the messes created whenever someone jumps to the (bad) conclusion that Josephus Burton Waters, of Frederick County, MD, and Josephus W. Waters, of Anne Arundel County, MD, were the same person.

Oh no they weren't!

Josephus B. had acute "horizon fever" and made tracks to the west, eventually fetching up in Kentucky or Ohio or ??? (note: he's one of the ancestors of William Jennings Bryan)

Josephus W. was a stick-in-the-mud and never moved away from Anne Arundel County.

They *were* cousins - third cousins on the paternal side and first cousins once removed on the maternal.

People can just merge willy nilly when they get a whim?

Ah, there's a long History behind Mis merges, and who can merge what.

Maven has a horrific source for one of her key families, unfortunately the book is well known, easily accessible, popular -- and wrong. So a newer genealogist for instance would have every reason to believe they've found a well researched & valid source for their tree, enter it, etc.

In the Parsons case it's simpler. Same name, similar dates, and massive confusion from researchers. It looks like it unravels to Betsy Feathers actually, being married to a man with the same name as his Rev War Soldier ancestor. Have you checked what DAR in their database? The confusion could originate & perpetuate from there. Add in the sexy American Indian name / possibility, the connection to the prestigious Woodson family, and you've got internet mess.

Luckily the Master Profile designation does help a lot in those mixups.

But, how was it not hilariously clear that RP 1720 was NOT the father of Jonathan B. 1813?

Why would and why could these impossibly dissimilar RP's be merged, and by someone on 10/19 that joined on 10/18, and is only very distantly related if at all?

Where is there any evidence that Betsy Feathers married the 1720 RP?

Until these are fixed, I won't wade into the larger Richard/Joseph/Jonathan thicket.

If I can and actually do perform the labor again of enterring what I believe is Jonathan's ancestry, will someone again replace it with an absurdity that everyone else will just leave in place?

I took the Indian ancestor as an intentional insult to anyone with any NA ancestry. Possibly just honest massive cluelessness.

I think, so far, that the Woodson connection is real, but two generations further back. I do not care about any prestige from any of it.

Rickey - it "is" all fixed to the best of my ability now, including my own mistake (that did not impact your line at all) of linking "my" Parsons to Joseph Parsons.

In genealogy, as in life, it can get murky & confused, and for all sorts of reasons. The MP program is the best solution I've seen so far for preserving the integrity of the entered data, but even then it's only as good as the data entered.

So let's progress on to completing the fix, and for that, your info is needed.

My thanks.

Thank You.

Showing all 9 posts

Create a free account or login to participate in this discussion