Working With Local Obituary Archives in Topeka

I've spent years pulling obituaries from the Topeka Capital-Journal archives and cross-referencing them with county death records. The process isn't glamorous, but it's one of the most reliable ways to build accurate local family histories. People ask me about this a lot, so I'm going to walk through how it actually works instead of what the promotional material says. The concept is straightforward in theory. You take obituary notices, extract genealogical data, and connect them across multiple generations to create a continuous record of who lived in a specific area. The tricky part is that most of the useful information lives in places that don't index well for search engines. I'm talking about microfiche collections at the Shawnee County Library, the state archive in Topeka, and the actual print editions that got thrown away decades ago. Here's what I do when I start a new research project. First, I pull the person's death date and get the newspaper run. The Capital-Journal publishes online now, but the free tier only goes back about five years. If you're researching someone who died before 2019, you're going to need to access the physical archive or order scans through the library. The library charges $0.25 per page for digital copies and holds the microfilm for roughly 1940 onward. Before 1940, you're looking at the Kansas State Historical Society in Lawrence, which requires an appointment and a $15 researcher fee for non-members.

One thing nobody tells you about obituary research in Topeka specifically: the format changed significantly around 1987. Before that, most obits were brief and factual. After that, they became longer and more personal. That means you can't apply the same extraction logic to every era. Pre-1987 obits give you names, dates, and surviving relatives. Post-1987 obits often include biographical paragraphs that contain school names, employers, military service details, and church affiliations that weren't previously documented anywhere. I've had entire family trees fill in from a single paragraph in a 1993 Topeka obit that mentioned a grandmother's maiden name and her sister's location in California. The biggest problem I run into is name ambiguity. Topeka isn't a huge city, and family names repeat across decades. A Johnson death in 1952 could be the same person as a Johnson death in 1978 if the dates line up, but they might also be father and son with identical names. The workaround I use is to pull the funeral home information. The Topeka area has used the same handful of funeral homes for decades. Capers-Sherman has been operating since the 1940s, and their records are surprisingly thorough. They maintain burial location data that often reveals whether two deaths belong to the same family line. Another counter-intuitive thing: birth dates in obits are actually less reliable than death dates. I've seen at least twelve cases where the listed birth year was off by two to four years, usually because the family member writing the obit didn't know the exact date and guessed. Death dates, on the other hand, match city and county records nearly perfectly. Always verify birth dates against the Social Security Death Index or the Kansas statewide vital records before building your timeline around them.

If you're doing this research for free, the Shawnee County Public Library on Wanamaker Road has a dedicated local history section with microfilm readers. They're open to the public during normal library hours. Go early on weekdays. The machines break down more often than you'd expect, and there are only two working readers for the entire Topeka collection. I once spent forty-five minutes waiting for someone to finish while I stood there holding my notebook. Not something I enjoy repeating. For digitized versions, the library's heritage quest database covers some But what it misses is exactly what most people need. It doesn't cover the earlier decades well, and the full-text search is unreliable for anything before 1960 because the OCR quality on the older issues is poor. I've found names that definitely exist in the microfilm but return zero results in the digital database because a smudge on the original page corrupted the text recognition. My actual workflow takes about three hours for a standard single-obit project and eight to twelve hours for a full family line going back three generations. That includes the library visit, the scanning, the cross-referencing, and the record verification. If you're doing this professionally for clients, budget accordingly. Most people underestimate the time required by at least double.

Get the Full Details

The Eternal Tapestry: Weaving Together The Threads Of Omaha's Ancestry ...
The Eternal Tapestry: Weaving Together The Threads Of Omaha's Ancestry ...

The downsides are real. This method completely fails if the person died outside Kansas. Out-of-state obits often don't appear in the Capital-Journal at all, even if the person lived here. They might appear in the paper where they died, and you won't know to look there without already having that information. I lost an entire branch of a family tree for about six months because everyone in that generation moved to Arizona in the 1970s and died there. The obits were in Phoenix papers, not Topeka ones. You have to know the migration patterns to know where to look next. There's no single download or software that does this for you. What exists are databases like Ancestry and FamilySearch, but their Topeka coverage is incomplete and often copied from public records that have the same errors I just described. The only way to get accurate results is to go to the primary sources directly. It's slower, but it's the only way the data is actually correct. If you want to start, go to the Shawnee County Library website and look up their microfilm catalog. Make a list of the names and dates you're working with before you go. The librarians are helpful, but they won't dig through the reels for you. You pull the film, you find the issue, you photograph the page with your phone, and you bring it home to parse.