Sometimes I do not really understand how the unexact searches at FamilySearch work.
I needed to review the 1940 census image for Anna Habben in Elvaston, Hancock County, Illinois. She’s there. I have seen her entry before. Away from my files, finding her in the 1940 census index and FamilySearch and navigating to the correct image would be a two-second project.
Without thinking I searched for her in FamilySearch’s 1940 census index as “anna habben” in Illinois–with the exact boxes checked. I got exactly Anna Habben. Not the one I wanted, but one in Iroquois County. It’s not the right person.
I repeated the search with the exact boxes unchecked and leaving the state set to Illinois. This should catch main spelling variant–including the one I really suspected the enumerator used: Hobbin. The Hancock County Anna was not found. There were entries though for a variety of last name spellings, including:
- and Habben
Certainly Hobbin would have been returned as a result.
After trial an error, I finally located her by searching for the first name of ann* living exactly in Elvaston, Hancock County, Illinois.
The one born in 1860 was confirmed to be her when I looked at the image–and Elvaston is not that large of a place.
But why wasn’t Annie Hobbin returned as a search result in my initial search?
I changed the first name to Annie did not change my results. For some reason searching for the last name of Habben (with the exact box unchecked) does not bring about results for Hobbin. That’s strange as the names are Soundex equivalents.
One work around is to search for the last name of H*bb*n in these search boxes at FamilySearch.
But that still doesn’t explain why (as of this writing) when Habben is put in the last name box and the exact box is unchecked, Hobbin is not returned as a result.