On Jon Elsas’s suggestion, I dug into Ancestry.com’s genealogy web site & did some searching for my wife’s and my ancestors. In additional to the personal and historical interest, I was curious to learn about the data and the data sets from an information seeking perspective.
Ancestry.com federates thousands of databases and archives of varying size, purpose and quality. They provide an interface for searching the data, for saving results, for building up family trees, and for connecting with other people.
Searching this collection presents a range of challenges both for the system designers and for its users.
Ancestry.com provides structured indexes that include dates, names, and places for records such as census data, immigration and naturalization records, military service records, births, deaths, marriages, etc. In addition to these structured items, a record may contain a lot of other interesting information that is not indexed.
From the searcher’s perspective, the challenge is to find the right records given incomplete or conflicting starting information. To complicate matters, the data can be quite noisy, with spelling variants, missing data, and outright mistakes. Many records that appear quite similar to the query parameters may vary on dimensions for which the searcher may not have enough information to discriminate among the results or to triangulate on the right person. The problems are particularly severe for immigrants from non-English-speaking countries whose names were Anglicized at the port of entry or by the immigrants themselves. For example, in my searches, I found the following variants for one family’s last name – Volkostavtser, Volkostavsky, Volcastofski, and Volcastopki. I also found Wolkenstawska and Wolkostawcer, but I am not sure whether these people are related.
From the system builders’ perspective, there are many challenges, including what constitutes a match, how to rank partial matches, how to combine evidence of similarity that comes from dates, place names, people’s names, ancestral relations, etc. Queries can return no results, or thousands of records, and neither may be useful to the searcher. The web site provides a range of fields on which to search, making it possible to express rather complex matching criteria. Unfortunately, it doesn’t do a very good job of faceted browsing of the results. Just about the only facet that can be manipulated effectively is the collection type and years.
It would be interesting, although possibly computationally difficult, to select spelling variants for names and places, to group data geographically, and to select dates as facets of the query rather than as a complete reformulation. The advantage of faceted search over the existing mechanism is that facets would give a better sense for how much variability is present in each kind of information, giving the searcher insight into the depth of the available collections.
Finally, it’s interesting to consider whether genealogical searching represents precision-oriented, known-item searching, or recall-oriented, exploratory search. At first blush, the whole point of the exercise is to find the right individual, making it a precision-oriented activity. On the other hand, this is just a small sub-task of the larger goal that many searchers have, which is to build a family tree that consists of many individuals, complete with as much detail about their lives as can be gleaned from the historical record. Finally, we should not overlook the serendipitous discovery of new relatives or of previously-unknown details of one’s ancestors’ lives. Such discoveries can prompt new avenues of exploration, new search strategies to be adopted, new collections to be explored, etc. All such activity clearly falls in the exploratory search category.
This combination of rich and challenging data, highly motivated users, and the possibility of defining interesting task metrics, this area seems ripe for academic research from the HCIR perspective. Unfortunately, this area remains under-explored with only four articles in the entire digital library tagged with the keyword genealogy as of this writing; the query “family tree” retrieved 133 hits, but did not identify any other documents related to genealogy per se.