Why do I "mine" these statewide vital records databases? Because I have been building a "one-name study" type of database for all Seaver/Seavers/Sever/Severs/Sevier/etc. persons in the USA for over 25 years. I get queries every month from persons with a Seaver ancestor and often I cannot help them without doing a little more research.
The Indiana Death Certificate collection provides many "new-to-me" Seaver folks, especially in two of the non-New England lines. On Ancestry, the record summary page for an Indiana death certificate may provide a Suggested Records link to census records, a birth record, a marriage record, a gravestone location, a draft registration card, and many other record types.
Some of the death certificates have names have have been extracted and indexed erroneously. One of the names on the Results list that caught my eye was Benjamin Wiley Seaver. I looked in my database, and did not see that name, so I figured I had found another "new-to-me" Seaver. I clicked on the name and saw the record Summary:
I also didn't have the father's name in my database. No surprise, because it;'s given as Weaver!
Here is the death certificate for Benjamin Wiley "Seaver":
Look at that - the typed name of the decedent is Benjamin Wiley Weaver. And his father is Henry Clay Weaver. The record is very clear! The record summary was wrong.
I went back to the record Summary, and clicked on the link to "View/Add Alternate Info." I added the correct name for the decedent.
Of the 50 Seaver entries I've resolved so far, three of the surnames for the decedent were misspelled. One or two had the wrong death date or birth date, and there were spelling errors for some place names. Three out of 50 is a 6% error rate. I could understand the error if the name was handwritten and was only semi-legible, but this one for Benjamin Weaver is not that - it's typewritten.
What all of this means is that if a searcher does not find a death record (in this case) using the correct surname spelling, they should try alternate spellings, and should try wild cards for names. Wild cards should be tried for the first letter, each of the consonants, and adding an "s" to the end of the surname. They could search for one or both parents names also (which might also be misspelled!).
In my search process in this Death Certificate database, I need to consider that there are:
* 97 entries for "exact" Seaver surname
* 83 entries for "exact" Seavers surname
* 72 entries for "exact" Sever surname
* 69 entries for "exact" Severs surname
* 94 for "exact" Sevier" surname
* 1,138 for "exact" se*v*r* surname
* 8,322 for "exact "?eaver" surname
The possibilities seem endless, don't they? This may be a lifetime exercise for me. This is why a genealogist's work is never done.
Even with all of the possible errors in the indexing, these vital record certificates are invaluable additions for those of us that need them. I just wish that Ancestry's indexing error rate was lower than it apparently is.
Copyright (c) 2016, Randall J. Seaver