History Detective: From Telegram to Identification

A lot of Keepa stories have their origin in a line or two buried in a newspaper article or a letter. That line signals to me that something interesting or important happened somewhere to somebody, and I go off on a hunt to find out more. For every hunt that results in a story, though, there are probably 8 or 10 hunts that go nowhere – either I don’t find what I need in order to tell a story, or the story turns out to be unsuitable for one reason or another.

I went on one of those unproductive hunts on Saturday. The story turned out to be terribly sad, and personal (not of general historical interest, as life-shattering as it was to the families involved), and didn’t reveal anything especially newsworthy about Mormonism.

Still, because at the moment I’m involved in questions of how to teach others to do what I do, presenting this sad tale as an exercise in online detective work might be useful to some readers, illustrating how you can go about chasing some of the details in your own historical or family history work.

On Saturday morning, I read a telegram from 1929:

Yakima Wash
1929 Feb 4 PM 3 51

Presiding Bishops Office
North Main St
Bishops Bldg
Salt Lake City Utah

A good faithful woman married first husband in temple He died leaving her destitute with six small children She married a nonmember for home Has three children by marriage Friday he shot and killed her also himself Is it permissible to hold his funeral with hers Wire reply at once one hundred three South Seventh st

Pres John C Preston

There’s certainly a dramatic if terrible story in that. It seemed worth investigating; if the story itself was too narrow to be a Keepa story, it still might be worth filing away for future use in, say, an exploration of intimate violence in the Mormon community. (Clients are always looking for material on topics you might not expect – and such material is very difficult to find on demand. I’m always alert to stories that might be of interest to another historian someday, and file them away, on spec.)

The first step in expanding such a slim clue is to evaluate the document for every last clue you can wring out. In this case:

  • No names are mentioned, other than the presiding elder wiring from Yakima. Identifying the people involved is of primary importance.
  • The murder/suicide probably took place on or shortly before 4 February 1929.
  • It may have taken place in Yakima, or it may have taken place in some other nearby community within the Yakima Branch – an area that could be quite wide, geographically. (In other words, I shouldn’t focus on Yakima so narrowly that I miss an event occurring next door.)
  • The whole family – including the non-member husband since he had presumably Mormon children – is probably somewhere in FamilySearch, but I’ll need a name to search for them.
  • The woman bore 9 children, and there could have been a gap in births between her two marriages. She could hardly have done that in less than 20 years, maybe 30 or more years. A rough estimate of her age, then, would be 40-50 years, perhaps a little older – so, likely born around 1880, give or take.
  • A violent incident must have been covered by some newspaper; an incident involving the welfare of so many presumably young children would probably leave its mark in civil records.

I decided to go after the names first. Everything else would grow from there. And while other research paths could have worked just as well, this is what I did:

I first searched the database at newspapers.com, a subscription database that I find so valuable that I subscribe for the premium service (that is, it includes newspapers whose owners charge a fee for inclusion). Many libraries subscribe to the same database, so you can get free access almost everywhere.

The database is easily searched. I narrowed the search to newspapers of Washington State, and the time period of the search to January-February 1929. Then I played around with various search terms: “shot wife” and “murder suicide.” Alarmingly, there were so many hits that I added the term “Yakima” even though I wasn’t sure the event had actually taken place there.

And that turned up this article from a Spokane paper, along with several others that more or less repeated these facts.

.

.

Okay, now we’re getting somewhere … but very slowly. “Mrs. Stone” isn’t given a full name, and “Harry Stone” isn’t distinctive enough to aid with searching. I tried googling, searching Family Search, and re-searching the newspaper database with Harry Stone’s name, without being able to sort through the massive numbers of hits to find anything relevant. He’s there, no doubt, but lost in the woods.

Next, I searched the Find-a-Grave website, a huge project dedicated to providing – free of charge – genealogical information found on gravestones, contributed by legions of volunteers. It can be a little tricky to search because you have to get everything just right – if Harry Stone had been Harold Stone or Henry Stone, a search for Harry Stone would have missed him. But I had a reliable date of death, so tweaking the search criteria quickly turned up his record.

.


.

Well, the new middle initial may be useful, but I didn’t find what I had hoped to find: Find-a-Grave users often upload obituaries, or chart other family members buried in the same cemetery, but there is none of that here. It looks like another person named Stone is buried next to Harry T, but I can’t make out the name so it doesn’t lead to a new search.

Okay, with a more or less complete name for Harry T, and a death date and place, it’s time to turn to ancestry.com. (Some searchers probably would have gone there earlier, but I was hoping to find a shortcut with something on Find-a-Grave.)

Selecting the “birth, marriage and death” search option, I plug in the name Harry Stone and the death information of February 1929 (it’s often best not to zero in on precise names and dates, in case a transcriber misread something or there is some other variance) and Yakima, Washington. A fraction of a second later, I see a list of results – including the death record for Harry Stone on the precise date I’m hoping for, and the name of his wife: Emma Stone. It’s only a transcription of some key information from the death certificate, not the certificate itself, but it’s what I need.

Searching the same database for Emma Stone, I find the same type of record giving her parents’ names. The search results for Harry Stone’s death also turn up a marriage record from the Mormon colonies in Canada. That’s really all I need – more than enough information to search Family Search and to find the record for Emmaline Eliza Layne Smith Stone, 1881-1929 (Family Search has a fuzzy feature that is very helpful with names: searching for “Emma” turned up “Emmaline.” If Harry’s full name had been Henry or Harold, searching for “Harry” would still have found his record.)

.

.

Everything matches: Names and dates and places, the names of Emma’s nine children, in two groups surnamed Smith and Stone. Her Memories page includes a few more clippings from Canadian sources, indicating that Emma’s family had objected to the planned joint funeral and burial – and that the funeral, in charge of the Church, had been changed at the last minute: Harry Stone was buried with only a graveside prayer; Emma Stone was given a funeral, her body returned to Raymond, Alberta, for burial next to her first husband.

So that is the story – or at least a listing of bare facts – behind the telegram for advice from the Presiding Bishop’s Office. It is not a story, on its own, that is particularly revealing of Mormon history, except, perhaps, an acknowledgment that such dreadful things have befallen Latter-day Saints – Church membership is no guarantee of a peaceful, happy life. But this exercise does point to the tremendous set of resources we have at our fingertips, for solving certain types of historical problems. Even when you start with practically nothing, it is often still possible to follow the trail.

Cite Keepa

Regrettably, meanies have stolen content from Keepa in the past! I'm confident you will choose honesty and cite this page like this:

MLA: Parshall, Ardis E. "History Detective: From Telegram to Identification." Keepapitchin.org, 28 Oct 2019, https://keepapitchinin.org/2019/10/28/history-detective-from-telegram-to-identification/.

APA: Parshall, A. (2019, Oct 28). History Detective: From Telegram to Identification. Keepapitchinin.org. https://keepapitchinin.org/2019/10/28/history-detective-from-telegram-to-identification/

HTML: <a target="_new" href="https://keepapitchinin.org/2019/10/28/history-detective-from-telegram-to-identification/">History Detective: From Telegram to Identification</a>

14 thoughts on “History Detective: From Telegram to Identification”

  1. You are amazing! Because of similar stories you have posted I have done a little detective work on my family. It is so fun to follow the clues, narrow the search, and zero in on the details. I am often reminded while looking around, that if I would just keep a journal my grandchildren wouldn’t have to have such fun!!

    Thank you for sharing your technique and tips on family research.

  2. Sheridan Stone (a son) is the other grave marker. Interesting that a boy left an orphan at ten by his father’s actions would choose to be buried next to said father.

    Searches like yours have been a regular feature at our house. My wife has been doing genealogy research for Better Days 2020. She’d get tossed a list of names and asked to find what she could about them as they worked to find 50 notable Utah women. We’re in Montana.

    Turning names into people is what makes genealogy interesting. Those using an app to get a name are missing the fun.

  3. I think it says something about Mormon history that such an obvious solution was only reached after an appeal to the Presiding Bishop. Any record of the response?

  4. Yes. The telegram was passed to the First Presidency who responded that there should be no LDS funeral for the husband.

  5. There are a few questions left to keep someone busy for a while: who were John C. Preston and “Dr. B. Hawkins,” named in a newspaper article as elders of the church who conducted the funeral service?

  6. John Carter Preston was born in Durham, England, in 1888, immigrated to the US in 1906, moved to Sunnyside, Carbon County, Utah, married Maud Ethelyn Redman in 1910, served a mission in the Southern States Mission from 1914 to 1916, moved to Washington between 1925 and 1928, had four children by 1930, was living in Yakima at the time of the 1930 US Census, died in Mercer Island, King County, Washington, in 1965, and was buried in Yakima–in a different cemetery from Mr. Stone. And, in 1930 he was working as a salesman for a newspaper.

    Now, how about Dr. B. Hawkins?

  7. I love the various ways you-all put on your deerstalker caps and became detectives yourselves!

    Mark, I haven’t been able to think of a way to identify B. Hawkins via internet sources, but it should be fairly easy to identify him through records in the Church History Library: There are the membership records for the branch/mission in question, and minutes of branch/mission meetings, and the local unit histories compiled by Andrew Jenson. Even if certain of these records no longer exist (if, say, the membership records walked off with a branch clerk and never made it to Salt Lake), it would be difficult to wipe out ALL the records for that time and place.

    Not sure when I will next be at CHL, but I accept the challenge!

  8. I’m late to this discussion. But, Ardis, I’ve got to say, This is really great. I hope you’re thinking about writing up more of your experiences as a master researcher/scholar. The insight, etc., you provide is incredibly helpful. Thanks.

  9. I keep thinking about this description of your methods of delving into historical records. I’m wondering if you keep a log of the work as you are doing it. It’s so easy to just keep digging and searching and lose track of where I have been and what I have found. I end up with scribbles on a piece of paper with random details. I assume you have a more organized method of logging the information you find.

  10. Hooboy, that’s a can of worms, ML.

    On something like this, where I might have spent only a half hour or so, still in the phase of casting around to see if there is a story I want to tell, I tend not to save anything, just have a lot of open tabs (which might mean having 3 or 4 copies of Ancestry or Newspapers.com running at the same time). That way, if I do decide there is a story, I can go back to each open tab and copy or extract material into a folder, carefully noting the source of each and closing the now unnecessary tabs.

    Because I decided not to save this story (there really are too many possibilities to log them all in my computer!), I did not save the various documents I looked at, except to make this post. However, the telegram that started this search came from a transcription project and would be saved there regardless of whether it had resulted in a story of its own. So I added a footnote to that telegram briefly identifying the people by name and life dates. If I should ever want the story for a client or for something else, that little bit of saved information will be all I need to quickly re-search my typical sources. But it isn’t worth (to me) the trouble to save the bits and pieces on my computer — it’s hard enough already for me to search my computer: it’s entirely possible to have too much of a good thing, making it difficult to find a wanted item among so much else.

    In a more general description, because my work is peculiarly heavy on transcriptions of full sources that could be sold to multiple clients or find a use in multiple of my own projects, I have, over the years, developed a filing system that works for me: All correspondence transcriptions are filed in date order in a correspondence file; all newspaper transcriptions are filed in date order in a newspaper file, and so on. When I work on a particular story or article or client request, I open a separate file for that project, and copy into it whatever materials I might pull from my main correspondence/newspaper/etc. files. That way, when I want a particular document for a second client or a third project, I can just go back to my main file and find it, without having to remember where I last used it.

    The one hard and fast rule, though, throughout my filing system: Never copy anything without first entering the full citation. You can’t count on remembering where ANYthing came from, no matter how noteworthy, and it’s useless without a citation.

Comments are closed.