Ruminations on Genealogy: Part 3

 

English: The stemma of the kings of Lazica acc...

English: The stemma of the kings of Lazica according to Toumanoff, Cyril. “How Many Kings Named Opsites?”, p. 82. A Tribute to John Insley Coddington on the occasion of the fortieth anniversary of the American Society of Genealogists. Association for the Promotion of Scholarship in Genealogy, 1980 (Photo credit: Wikipedia)

 

A while ago, someone posted on Fb an infographic, part of which read ‘comparisons are cliché’. It should have read ‘comparisons are passé’. The writer, reader, and re-poster got it wrong as far as genealogy goes.

 

Comparisons are not passé as far as genealogy goes. We do comparisons as part of our basic research. We compare others’ recollections to known facts to prove or disprove what is the truth of a matter about our ancestors. The only thing that is passé about comparison in this way is that it becomes old hat after a while and we don’t bother thinking such things.

 

As far as writing clichés, that’s a different thing. There are only so many ways to write a birth, death, marriage sequence of sentences in a well-defined format. Indeed, all genealogists use clichéd formulas because they work. Most genealogy programs use hackneyed phrases (The Master Genealogist is an exception) to pass off their data and genealogists need to change them to something unique.

 

These hackneyed phrases, however, are usually the best way to portray compared data. Yes, they are passé but only in the sense that they work. The writer and reader have only to let their eyes see beyond these phrases to get to the real meaning and the underlying data. Doing this allows one to create a better proof statement and research report.

 

The writer is responsible for not making the reader’s eyes glaze over with too many redundant statements of the same form.

 

NPM

 

 

 

The word ‘genealogy’ is pronounced …

gee nee al o gy

that is, it is not pronounced

jen e al o gy

My understanding of Webster’s definition is that the E in genealogy is alike with that in ‘easy.’ I’ve heard some podcast speakers and others trying to make it sound like gen et ic, but it’s not; they are two separate words with two separate meanings.

Thanks, folks!

NPM

 

Sanity Checking with Multiple Genealogy Programs

There are some people, like me, who are not quite satisfied with just one program for genealogical purposes. I use several, and keep an eye out on the others for features that might suit me well.

Lifelines

LifeLines

LifeLines (Photo credit: Wikipedia)

is one of the programs I use on a semi-regular basis. It is an old program (console window, anyone?) and has a long history of strong development by the maintainers. Thomas Wetmore originally wrote it back in the olden days of Unix and DOS, but it’s still around.

One of the things I like about Lifelines is it’s powerful scripting language. This language takes a bit of getting used to but once you know it, it seems intuitive. The program comes bundled with a lot of scripts, some better than others, and some near-duplicates of others. The verify script is one of the most powerful sanity-checkers on the market (did I mention that Lifelines is free?). Some of the things it reports on are age boundaries (birth, marriage, and death), multiple marriages, kids out of order, and so on. Several scripts check for people who might be in the Social Security Death Master Index. Another script called, weirdly enough, zombies, looks for people who don’t have death items (death, probate, burial, and so on).

I ran verify recently on a 5500+ person database and it came up with nearly 1600 items that it thought were interesting and that fell outside of user-programmable boundaries. It’s not for the faint-of-heart to look at this report as it can be a lot to digest. The nice thing about the report is that when I go through it, item by item, I can tighten up the quality of the data on a semi-regular basis, and gain a semi-regular consistency for the entire database. It might take years to finally go through the entire list and complete each item, but knowing about these items is the important thing.

Like verify, the zombies script reads through the database and plucks out those that have death items. This report is much simpler, and sortable so you can find the people by year, instead of in database order. The great thing about this report is that you find out who is in the database that is not marked as dead, dead, dead, as in dead. The script doesn’t consider the deceased flag, if there is one on the person, it makes you think about getting the details, and you’ll want to go out and get the details right away.

If you’ve added a lot of what I call “the moderns” you’ll want to run one of the SSDI check scripts and follow up on a visit to the Death Master Index on your favorite online site that has one. I used to use the one at Rootsweb.com, but Ancestry.com removed it to their own site for some reason. Shucks, the Rootsweb version was better, IMHO.

Enough about the great Lifelines scripts. Multiple programs for genealogical data analysis are a must if you are serious about the pastime. Knowing what’s good data and bad is a good idea, as well as ethically correct. My other genealogy programs include an old version of Legacy, and a current version of The Master Genealogist.

TMG is the one I use on a regular basis as it is almost as powerful as Lifelines in the analysis and reporting facets. The only drawback to TMG’s reporting is that it’s not as flexible and programmable as Lifelines. Legacy, on the other hand, even though my copy is quite dated, is pretty good at picking out bad data, too. Even though I haven’t used Legacy for a while, like Lifelines, I keep it around as a variant finding tool.

Ruminations on Genealogy: Part Two

English: National Archives and Records Adminis...

NARA record

This is a continuation of the post referenced in the title “Ruminations on Genealogy,” that I put up a few weeks ago. Parts of the “essay” that I mentioned follow.

Genealogy is non-denominational; it is not a cultish thing. Genealogy is a global pastime for all who are interested in their ancestry, family history, and the works of their forebears. Genealogy goes beyond the simple ancestry charts, pedigree lists, and data tables. It encompasses history: itself, legal, medical, and family, to place individuals in their context of time and space.

Genealogy’s sources are diverse. Some of them include the items above: ancestry charts, pedigree lists, and so on. However, some such as those on the major data providers’ websites can only be classified as derivative. These data providers may, and often do, present images of the originals, but they also present images that have been manipulated. The changes made can only make one wonder what else the provider has changed.

Like all original sources, there is only one copy, and at most a few copies of that. The images often found on a providers’ website technically belong to them; the original, however, doesn’t. This is why you need to examine and cite to, the original and not the derivative on some website.

The best way to get an accurate, complete, and as close to possible, original, is to go to the archive where the best provenanced copies are kept. In the case of census records, this means going to a National Archives and Records Administration site and looking at their microfilm copies. Using a NARA-provided image is getting as close to the original as most people can, so it is the best available source. Use it, and cite to it, rather than a manipulated copy from Ancestry.com or Archives.com, or wherever.

To be continued.

NPM

© 2012 N. P. Maling — Sea Genes – Family History & Genealogy Research

Follow Friday: The Turning of Generations

In the midst of finalizing and indexing the Mellen genealogy, I try to keep abreast of geneablogging. This week I found a new (to me) blog, called The Turning of Generations. The current theme on this wonderful piece of work is the 21st Century Organized Family Historian (#21COFH).

What’s interesting about 21COFH is that all genealogists can learn from reading about it. I’ve been working on digital organizing since I had an 8086 KayPro, so had to use very restrictive (nowadays, anyway) file names and directory structures. Eeew!

There seems to be a growing number of other folks reading and practicing the exercises for this theme, so I hope to learn something and perhaps contribute something when I’m more free from other concerns.

NPM

© 2012 N. P. Maling