February 14th, 2012

definition of parent

I was tempted to get into the whole what-is-a-parent question when I posted about Fischer v Zollino. I didn't; I felt like the post was long enough as it was. The short form of the rant is: we had a definition of what makes a father a father and now we have a different definition of what makes a father a father. Under the old definition, there were rituals and records. Under the new definition, there are DNA samples. It's not that we only ever had _one_ definition and now it has changed; we've always had multiple definitions. It's more that the default definition has switched places with one of the alternate/must be explained definitions. And I don't have a problem with that happening, in general.

In specific, however, I _do_ have a problem when people take a default definition (whether it is what-it-means-to-be-gay or what-it-means-to-be-a-parent or what-it-means-to-be-female or what-it-means-to-be-christian or whatever) and attempt to enforce it across time and space where _it is not_ or _it was not_ the default definition.

So: novels written in an era where female-hot-bod defaults to big boobs with protruding clavicle bones (and if one has to be sacrificed it's likely to be the boobs) about an era where female-hot-bod defaults to the well-upholstered (think Lillian Russell) in which the super-hot main character looks suspiciously like the former and not really at all like the latter, and then the women hate her but the men, they have the lust, are an example applying a default inappropriately. A particular novel like this would be one thing; hosts of them are an indication of a problem.

Genealogy exists in a state of tension with past ideas of the past (e.g. confusing patronymics with surnames), present ideas of the past (e.g. that people viewed the husband of the mother as the father unless something really showed otherwise, and then did so anyway, if the husband of the mother recognized the child as his own. For example, a man who married a woman with an illegitimate five year old child thereby became the legitimate father of that child, if he so declared at the time of the marriage -- even if he'd never her met her until a few months before, at least in some jurisdictions) and current ideas (e.g. DNA tests prove who the father _really_ is).

I don't necessarily have a problem with advocating for a certain kind of genealogy per se (I'm an advocate for fuzzy match, comprehensive and iterative error checking, myself, and a big believer in doing maternal and paternal lines without preference, but I accept that other people do things in different ways). However, I _do_ have a problem with advocating a certain kind of genealogy by attacking other kinds of genealogy.

And this post really set me off this morning.


I like the blogger and there's some reason to suspect he's being deliberately provocative here. He succeeded. The title questions the validity of family trees that match paper over genetics. He fluffed the NPE question badly, altho it is hard to blame him for doing so because this is a subject area that is not well studied and full of Telephone-like transmission of bad data.


"The Sorenson Molecular Genealogy Foundation, which is based in Salt Lake City, now has a genetic and genealogical database covering almost 100,000 volunteers, with an overrepresentation of people interested in genealogy. The non-paternity rate for a representative sample of its father-son pairs is less than 2 percent."

I think this is the correct number to use as a genealogist -- after all, the survey overrepresented genealogists! There are bigger numbers out there, but they are not well sourced and/or they cover unusual groups of people. The 10% figure, IIRC, derives from a study of NPEs in a population of people in which the men were suspicious that they weren't the father (but feel free to go dig it out and point me at the real source).

If you use this number, there's no reason to believe a typical family tree is broken by genetic standards -- by the time the numbers are in your favor for finding an NPE, you're out of the range of the instrument that the blogger has selected to detect NPEs.

More importantly, family trees in which the paper doesn't match the genetics ARE NOT BROKEN, except if you choose to adopt genetics as a sole basis for genealogical relationships. And that is importing a highly specific and very modern definition of genealogy deep into the past. I'm not sure _why_ people think this is reasonable, but it's right up there with writing a novel set in the Netherlands in 1600 or thereabouts and having the female protagonist be depicted as scarecrow-like but super hot once she gets her makeover.

I'm all in favor of using genetics in genealogy and will probably get around to doing some myself. Eventually. Megan Smolenyak has an awesome chapter in _Hey, America, Your Roots Are Showing_ about her uncle turning out to be her father's half-brother, and no one knew until Smolenyak decided to do a bunch of testing of her relatives in an effort to determine whether the autosomal DNA tests could really do what they claimed to do (one of the many reasons why I Heart Megan Smolenyak, along with virtually every other genealogist, amateur or otherwise). But it is also worth pointing out that genetic testing is most effective at exposing relatively recent NPEs. Genealogy is already a bit of a dodgy activity. Suggesting that anyone who wants to "fix" their "broken" "tree" needs to run right out and rope all their relatives into submitting yDNA samples is _really asking for trouble_. At least Smolenyak handled the potential problems with sensitivity and grace. This blogger is just pointing a bunch of comparative young-uns as the family closet full of skeletons and saying, "go get 'em".

I can't even get my second cousins to respond in writing to questions like, "Did you know ID and Amy were first cousins?" -- and that's fully documented.

Mail from Washington State

I received mail from Washington State. The mail was a birth certificate I had requested. Washington State, unlike many other states, is Genealogist Friendly, so I was able to get this birth certificate even though the person who was born is still alive (and really not much older than me). I got this birth certificate because my sister called me and expressed some curiosity about how to go about tracking down an uncle who we had never known (as in, never knew his name).

The obvious first steps are unavailable to us: that is, asking the aunt doesn't work because she is dead and asking her other siblings doesn't work because they are either dead or alive and not talking to us and even when they were talking to us they wouldn't talk about this particular person. Another obvious step would be asking the offspring of this uncle, but it took a long time to find that person and our relationship is super tenuous at this point.

The next step is just to see if the name is on the birth certificate, hence, the mail from Washington State. I was a bit surprised to find out I could even get the record (I'd been missing on so many other states for people who were long dead). I warned my sister not to expect much; I was expecting exactly what we got: no name in the father field.

But I'm still amazed that there are no obvious limitations on vital records in that state and seriously contemplating sending in a ton of requests to get records before someone decides to make them every bit as annoyingly unavailable as a lot of other places. OTOH, their Digital Archives already have a ton of marriage licenses, so maybe they're just going to be reasonable and I can wait and cherry pick the ones I really want.

Hard to say.

A Bit More About Malls

I've blogged about malls before. I'll point to this entry, because it includes some stuff about the Galleria gardening thing.


A friend sent me this link, because of this interest. I haven't responded to the email (thank you!) and do not at this moment in time have any particular remarks to make about the coverage, other than to note that the Cleveland Galleria has an Insanely Great person or persons doing marketing for them.


There may be some additions to this entry later. I'm currently in the middle of walking back through a year's worth (holy crap do I post a lot) of blog entries and tagging the genealogy related ones, since someone has very kindly put me on his blog roll and I'd hate to have the people showing up to look at the genealogical stuff have to put up with my other highly random interests.

Administrivia: genealogy tagging more or less complete

Since I noticed this journal shows up in a blogroll for someone else who blogs about genealogical stuff, I thought I'd try to make this a slightly better experience for visitors who are here for the genealogy. That is, I caught up on tagging a bunch of genealogical posts. I'm very, very bad about tagging posts, but I will make an effort (I seem to have let about 8 months slide by. Whups!).

If you are here for the genealogy, try this:


You should however be aware that I do not regard myself as a professional genealogist nor do I aspire to be one (altho I do admire quite a few professional genealogists and make use of their fine work) or to acquire any kind of accreditation or credentials.

Here's a brief summary of some of my genealogical interests:

Prussian/Russian/Canadian Mennonites

the following places:

the Pacific Northwest, especially Skagit and Whatcom counties in Washington State
the Netherlands, especially Friesland
Exira, Iowa (Hamlins and associated families)
Mohawk Valley, New York State (especially the area around Amsterdam, especially Fonda)

My husband is particularly interested in French-Canadians (he could supply the village names) and New Jersey, especially places like Little Falls and Newark.

But we both go wherever our trees take us. We go up ancestors, out along collaterals wherever possible, we trace mothers as well as fathers, sisters and brothers and siblings and their children, down to present day cousins whenever we can.