Saturday, April 30, 2011

Satruday Night Genealogy Fun - Problems in your Genealogy Database

Tonight's Saturday Night Genealogy Fun from Randy Seaver over at Genea-Musings is another software challenge - by far my favorite type of Randy's challenges. So tonight's challenge is to find the data error or problem report in your genealogy software, create the report, and describe the number of problems and types of errors, as well as any surprising results.

My usual genealogy software is Reunion, and I have to say I had a fair amount of trouble finding a way to produce these reports. I found nothing easily in browsing Reunion's menus, nor did I have any better luck searching the help file for keywords like "problem" or "error". So I turned to the ReunionTalk online forums and finally found an avenue to an answer, one I never would have found on my own.

The date feasibility report gives common date errors such as birth, marriage, or divorce events occurring after death, births occurring before or after particular ages, or marriages before certain ages. This report is nicely hidden under "Reunion preferences --> Dates" not listed amongst Reunion's other report options.

I ran the report using the default options. Output is a plain text file. Mine contained 9 various date errors, combinations of:
  • child born after parent died - 3
  • child born before parents' marriage - 3
  • child born before parent was age 12 - 2
  • child birth date is after death date - 1
Most of these merit a second look at the data entry and sources consulted. One of the "errors" reported is in fact, not an error. My grandmother's eldest child was indeed born after her first husband died in World War II. And I expect at least one error in the "child born after parent died" category may be a similar case.

Reunion does have other error-type reports I've used before: unlinked people and duplicate people, which I run on a semi-regular basis, especially if I do any Gedcom importing.

But I had hoped for a report that would deliver a variety of different errors in one place. One of Randy's other respondents tonight was Caro from Caro's Family Chronicles who reviewed Family Tree Maker's Data Errors Report.

Since I have the Mac version of FTM on my laptop, I decided to try this report in FTM. I don't use FTM regularly, but do have an older Gedcom of my database there so I can play with different genealogy software. So I easily found and ran the Database Errors Report, doing as Caro did excluding "birth date missing" and "marriage date missing". I also excluded "children out of order". The resulting report listed 25 problems, including date errors and a few unlinked people. But by far the most common error FTM listed was women who were entered using the same surname as their husband. I know I have the tendency to make this error, but was surprised to find quite so many (7). I don't easily see a way to find women entered with the same surname as their husband in Reunion, but I'll keep poking around.

At a glance, many of FTM's errors look different from the Reunion errors, so clearly I have some work to do to check these and correct them if they exist in Reunion. I'll also import a new Gedcom into Mac FTM once I get the errors cleaned up. I guess none of the errors really surprised me, but I'm surprised at the number of them. This was a great challenge, and I'm glad to have a few more tools to help me keep my data clean.

No comments:

Post a Comment