All posts

Reading the records more carefully

A stated birth date now opens the war-years search, a veteran's burial record gives the service, and a misread census line is still found.

A search is only as good as what it does with the first record it finds. Three fixes this week came from one search that found a single record and stopped.

A stated birth date opens the war years

The record was a veteran's burial entry, and it gave a full date of birth in 1923. Lineage showed the birth, but the part of the search that works out draft windows only read birth years it had to estimate, from a census age or a marriage. A date written out in full never reached it, so the Second World War records were skipped. A stated birth now comes first.

The burial record gives the service

The VA gravesite record lists rank, branch and war period in their own fields. The reader kept the dates and dropped the service. Those fields now become a service fact, quoted from the record's own lines, once the record is matched to the person.

A misread census line

The 1950 census index is read from handwriting. The line for this man had two letters misread, one in each name. Lineage now:

  • takes a given name that is one letter off when the surname fits, and still checks the household on the page image before keeping it
  • reads 50 results a page instead of 25, because the right sheet was 28th of 31
  • narrows the search to the state of the burial record when no place was typed

None of this guesses. Each change lets Lineage use what a record already says.