A Practical Guide to Working With When Language Dies Book

I spent four years doing documentation work on a small language community in the Philippines before I ever sat down with a formal framework. The tools in When Language Dies Book would have saved me months of re-recording. I'm going to walk through what the book actually covers, where it falls short, and the specific problems I ran into that the text doesn't address. The book is essentially a field guide to language documentation at the point of endangerment. It covers elicitation protocols, metadata standards, and the ethics of working with speaker communities. The authors, K. David Harrison and Gregory Anderson, wrote it after years of fieldwork across multiple continents. The core argument is that language documentation is not a luxury — it is the only thing standing between many languages and permanent extinction. The methodology section relies heavily on the paradigms established by the Berlin-Brandenburg Academy of Sciences and the Language Documentation and Conservation program at the University of Hawai'i. If you have any background in linguistics, the framework will feel familiar. If you are coming from another discipline, you will need to read the early chapters slowly.

I tried to follow the standard elicitation checklist in the book during my first solo field season. The problem was that the checklist assumes a certain level of speaker comfort with foreign researchers and repeated questioning. In practice, the community I was working with had been burned by outside researchers before. They were polite but guarded. The elicitation sessions produced almost nothing for three weeks. Here is the workaround I ended up using, which the book does not explicitly describe: I stopped doing formal elicitation entirely. Instead, I spent two weeks just sitting in the community space, recording casual conversation without asking for anything. I let the speakers get used to the equipment and to my presence. After that, the elicitation sessions became productive. The recorded natural speech also turned out to be far more valuable than the elicited word lists the book's initial protocol pushes for. The metadata quality from spontaneous speech is higher because the speaker is not performing for a researcher. That is a counter-intuitive point that took me a long time to accept. The book's coverage of digital archiving is its strongest section. It walks through file naming conventions, WAV versus MP3 trade-offs, and the importance of creating local copies before sending anything to a university repository. I followed the file naming structure religiously and it prevented a major headache when I had to organize over 80 hours of audio for a grant report. Getting the naming right from day one cut my time down from something like ten hours to about an hour.

Where the book is weakest is in its treatment of community ownership and data access. The ethical framework is sound in principle, but the practical guidance is thin. I encountered a situation where the community elders wanted certain ceremonial recordings restricted from public access, but the archive I was depositing into required open access by default. The book does not give you a clear path for handling restricted access agreements within existing repository infrastructures. The workaround I used was to create a two-tier system. The primary recordings went into the archive with full metadata, but I also maintained a separate set of access-tier metadata that flagged which files were restricted. I negotiated directly with the archive staff to honor the restrictions even though their system was not designed for that. It required phone calls and patience that the book does not prepare you for. If you are working with a community that has legitimate access concerns, budget time for that negotiation upfront. It usually takes two to three weeks of back-and-forth with institutional review boards and archive administrators. Another area the book glosses over is the equipment side. The recommendations are reasonable for a well-funded project, but many independent researchers or smaller institutions cannot afford the suggested setup. I ended up using a Zoom H6 recorder and a pair of Sennheiser MKE 2 lavalier microphones, which cost under four hundred dollars total. The audio quality was acceptable for documentation purposes, though not comparable to the field recorders the authors recommend. If you are on a tight budget, this setup will get you through most elicitation and narrative recording sessions. Just make sure you record at 24-bit/48kHz minimum and carry backup batteries.

Get the Full Details

(PDF) When Languages Die: Understanding Endangered Languages and Language Death
(PDF) When Languages Die: Understanding Endangered Languages and Language Death

The chapters on language revitalization tie-ins are useful but somewhat disconnected from the documentation methodology. The book presents documentation as the foundation for revitalization, which is true, but it does not adequately address what happens when documentation is completed and no revitalization infrastructure exists in the community. I know of at least one project where the archive was finished and then sat unused for five years because the community lacked the organizational capacity to take the materials and turn them into teaching resources. Documentation without a revitalization plan is still valuable, but it is not a substitute for one. If you are reading this book as a primary methodology guide, pair it with the Language Conservancy's free documentation toolkit and the Endangered Languages Project's field notes. Those resources fill in the practical gaps the book leaves open. The archive deposit guidelines in the book are also slightly outdated in places — check the current version on the ELAR website before you start sending files anywhere. I have been doing this work long enough to know that no single book covers every edge case you will encounter. When Language Dies Book gives you a solid foundation. It will not teach you how to handle a community that stops participating mid-project, or how to deal with a corrupted hard drive that wipes three months of recordings, or how to explain to a funding body why your fieldwork timeline slipped by six months. Those things come from doing the work. But the documentation protocols in this book are the best starting point I have found, and they are worth reading before you buy a single piece of recording equipment.