Last week, we talked about some of the problems we face in tracing ancestors
with common surnames. New genealogy technology brings even more new challenges
for those of us with the curse of the common name. But this is a battle that
can often be won with a little creative thought. Here are some common dilemmas
that we may face when searching for our ancestors with common surnames and some
possible solutions.
Advanced Searching
When searching databases, I often catch myself overlooking some of the great
search options that are available. I find an interesting database, enter a surname,
and if an ancestor doesn't jump out of the crowd and bite me, I'm outta there.
With common surnames, it's easy to get discouraged and just toss that line aside.
It doesn't have to be that way though. Huge sets of results from some databases
can be copied into spreadsheets and sorted in a number of ways, making it easier
to narrow down the list.
For instance, using a database like the California Deaths, 1940-97, a search
for Charles Kelly turns up one hundred and thirty-two results. Since the data
is sorted by death date in the database, it can be difficult to compare various
entries of interest without much transcribing, clicking, and backtracking, which
can be frustrating. By copy/pasting all the results screen into an Excel spreadsheet,
I could sort the data by the various fields that were included in the database
(surname, given name, middle name, sex, birth date, death date, birth place,
death place, Social Security number, mother's maiden name, and father's surname).
A sort by birth place narrowed the search for Charles Kellys who were born in
NY to nine and one with birth place unknown. If I had only a birth date the
data could be sorted by date. (Although, since Excel doesn't allow the correct
formatting for dates previous to the 1900s, a separate column had to be created
in which I just entered the year in numeric form for sorting purposes. Another
option would be the free add-in that Beau Sharbrough mentions in his article,
"Rootsworks: SpreadsheetsCensus"(see links below).
Another advantage of sorting all the results, is that down the road, these records
can be helpful in sorting out others in the area with the same name as your
ancestor.
When the Surname is Also A Given Name
One reader wrote me about the difficulties she is having with the surname George.
Since I have spent much time searching for ancestors with the surname Dennis,
this is a problem I am all too familiar with. The trouble is in how some databases
are formatted. If there are not separate fields for the surname, the database
has no way of differentiating what is a given name and what is a surname. Fortunately,
many databases, like the Census indexes at Ancestry.com do allow for searching
by surname alone.
It is also important to note that an advanced search is necessary to specify
that it is a surname. If you were to search the database individually (one with
no field available for 'surname'), the database sees the term as a keyword and
searches all the text in the database for matches. Whereas, if you use the advanced
search template (http://www.ancestry.com/search/main.htm),
including the surname in the surname field, it will only search surname fields
in the database for the name (in the databases that are formatted with separate
fields for surnames).
Advanced searches are also helpful since they allow you to specify more information
that can narrow the search. The downside of this is that by specifying too much
information, you may rule out the very hit you seek. Even given names, when
abbreviated can cause problems. How often have you seen initials or abbreviations
like Chas for Charles, Jas for James, Robt for Robert, Thos for Thomas, etc.?
When these abbreviations appear in the database and you specify the entire first
name, the search will not return hits for those names. If you think that the
chances of this are slim, or that these abbreviations only occurred in older
records, consider the following from the Social Security Death Index:
Chas3160 hits
Thos631 hits
Jas231 hits
Robt359 hits
The initial "A"151498 hits
Cousin How Many Times Removed?
If you understand (and can articulate) how to calculate and communicate cousin
relationships and the "removed" part to a beginner, do them a favor and explain
it.
ACK! That's a bit disheartening. But there's still hope. Take a look at the
million or so results you got using just the surname. What other fields are
available? Is there something you can enter into the keyword search field, like
a Social Security number, another surname, a county name, etc.? If you keep
track of the criteria you use and rotate in various bits of information that
you have, you may be able to hone in on your John Smith yet!
On a side note, as I was experimenting, I did a search for 'George' in the AIS
Census Indexes and came across the following entry:
1850, GEORGE, George, Albany County, NY, 095 Albany 2nd Ward
Talk about complications. And there are even more George Georges in New York,
including a George McGeorge, and a couple George St. Georges, too.
When the Name is Not Just a Name
Another troublesome surname phenomena is when the surname is also a commonly
used term, like Lake or Wills, or a surname that is also a location. My deepest
sympathy goes out to all of you with this problem! Trying to locate these surnames
using your average search engine can be difficult at best. I am searching for
the surname Poland, and I am constantly rewarded with references to the country
as I search for this family. This is no help to me at all since this branch
of the family is from Ireland. Some of the methods I use to get around this
issue are:
- Include the terms 'genealogy' or 'family history' in your search
- Use Boolean search commands like 'and,' 'or,' 'not,' or 'near' to help narrow
your search. Example: 'lake and genealogy not county'
- Specify a location
- Include any unusual given names that may be in the family tree.
As with searches in databases, when using search engines, it is helpful to look
at the results you have, and try to pick out a common thread in those hits that
you want to weed out. Then use 'not' to get rid of them.
I also got a few requests for more information on Timelines. Next week, we'll
talk about creating a timeline for your ancestors and how they can help.
California Deaths, 1940-1997 (Free database)
http://www.ancestry.com/search/rectype/inddbs/5180.htm
AIS Census Indexes (Subscriber databases)
http://www.ancestry.com/search/rectype/census/ais/main.htm
Rootsworks: Spreadsheets-Census - Beau Sharbrough
http://www.ancestry.com/library/view/news/articles/4348.asp
Ancestry.com Help
http://www.ancestry.com/help/index/index.htm
(or click on the '?' at the end of the navigation bar near the top of the screen)
Search Engine Watch
http://www.searchenginewatch.com
"The Basics of Boolean Logic for the Genealogist," by Michael John Neill
(Ancestry Daily News, 1/19/1999)
http://www.ancestry.com/library/view/news/articles/1416.asp
"Searching for Peter Bieger's Pickled Pepper Web Page: Using Boolean Searches,"
by Michael John Neill
(Ancestry Daily News, 1/21/1999)
http://www.ancestry.com/library/view/news/articles/1495.asp
"Search Engine Searching--Update," by Michael John Neill
(Ancestry Daily News, 6/06/2000)
http://www.ancestry.com/library/view/news/articles/1497.asp
Juliana Smith is the editor of the Ancestry Daily News and author of
The Ancestry Family Historian's Address Book. She has written for Ancestry
Magazine and Genealogical Computing. Juliana can be reached by e-mail
at: editor@ancestry-inc.com, but
regrets that she is unable to assist with personal research.