When Subheadings Are Not So Useful


Hello,

I love subheadings. They add so much to an index, breaking down long strings of locators into smaller chunks, highlighting meaning distinctions, and gathering related entries into lists so readers only need to search in one place. As I discuss in my last reflection, subheadings can also reflect the story that the text is telling. Well-written subheadings are clear, specific, and meaningful.

But…in indexing there is always a but. Occasionally, a project comes along that proves the exception.

This happened with a recent index I wrote, for To See What He Saw: J.E.H. MacDonald and the O’Hara Years, 1924-1932, by Stanley Munn and Patricia Cucman (Figure 1 Publishing, 2024). J.E.H. MacDonald was a Canadian painter and a member of the Group of Seven. He fell in love with the landscape around Lake O’Hara, in the Rocky Mountains, and spent several summers there painting. This book takes an interesting approach to MacDonald. Over the course of almost twenty years, the authors sought to identify the exact locations where MacDonald painted. The bulk of the book is composed of a brief discussion of each of the O’Hara paintings, alongside a photograph of what the scene looks like today. The rest of the book is composed of an introduction, an overview of each of MacDonald’s eight trips, and excerpts from MacDonald’s diaries and other writings. The result is a beautifully illustrated coffee-table book.

The instructions from the press were to only index the paintings, people, and places. While narrow in scope, there isn’t too much else discussed, and these are what readers are most likely to want to find, so I thought the instructions reasonable. Figure 1 Publishing is also very good at providing clear specifications for how long the index can be. For this book, the specs were 55-60 characters per line, for 675 lines total.

I quickly realized that the book mentions a lot of paintings and places. The book discusses 226 paintings, almost all of them by MacDonald. With each painting taking up at least a line, some of them more, the paintings alone fill up about a third of the index. The rest of the index is mostly places—mountains, lakes, creeks, trails, huts—in and around Lake O’Hara that MacDonald either painted or visited. In comparison, only a few people are mentioned.

I also realized that the book contains a lot of repetition. For example, the same mountain may appear in a couple dozen different paintings. That mountain is mentioned again in the overviews of MacDonald’s trips, and then again in MacDonald’s diaries. This kind of repetition makes sense given how the book describes the same events and paintings from different angles, but it does mean that the mentions add up. Arrays with especially long strings of locators include Cathedral Mountain (49 page references), Hungabee Mountain (39 references), Odaray Bench (34 references), Lake McArthur (32 references), and Lake Oesa (27 references).

Normally, I would add subheadings to these arrays. Asking readers to look up each page reference is a big ask. But for this index, I left those strings, for paintings and places, intact.

Not using subheadings was a conscious decision, and one I didn’t make lightly. My initial instinct was to find subheadings. But as I indexed and considered the entries, I also realized that subheadings would not be so useful in this particular index. Wanting a second opinion and to avoid surprising the press with a departure from my usual approach, I also queried the editor I was working with and got their approval.

I decided to not use subheadings for two reasons. One, I realized that too many subheadings would quickly make the index too long. Unfortunately, space constraints can sometimes mean putting aside the index that you want to write for the index that fits. In these situations, I need to be strategic about picking and choosing the subheadings that will have the biggest impact, while also being okay with other arrays not having subheadings.

More importantly, though, for this book, I couldn’t think of subheadings that I was satisfied with. For subheadings to be effective, they need to clearly articulate additional information that readers can use to narrow their search. But what if there are no clear distinctions between locators? In that case, I think the long strings of locators should be left alone. It is not helpful to introduce artificial distinctions or to get so granular that context is lost.

As I mentioned, this book contains a lot of repetition. Places either appear in MacDonald’s paintings, are places that MacDonald visited, or both. This doesn’t provide much to hang a wide range of subheadings.

I briefly considered listings all of the paintings that each mountain or other feature appears in, along with a subheading for MacDonald’s presence at. For example,

Cathedral Mountain: MacDonald at; in painting 1; in painting 2; in painting 3; in painting 4; in painting 5; etc…

But this approach presents a few problems. Some arrays would have been enormous, with a dozen or two subheadings for each of the paintings. Besides the space issue, I’m not convinced that listing each painting would have been meaningful to readers. Would readers remember the titles of individual paintings? In many cases, multiple paintings shared the same title. Thankfully, the authors give each painting a unique alphanumeric code, which I included in the index to differentiate. For example, “Lake O’Hara (25-1.3(S))” and “Lake O’Hara (30-3.1).” But I imagine it would still be difficult remembering which is which. Alternatively, I could have created a subheading for “in paintings,” but that would have still resulted in a long string of locators, as would the subheading “MacDonald at.” “MacDonald at” also isn’t very useful since readers can presumably assume that MacDonald was there, as that is the focus of the book.

Given the space constraint and that either way—with a couple of generic subheadings or without subheadings—the arrays would have long strings of locators, I decided it was best to keep the arrays simple and to forego subheadings. This does mean that readers will need to search through each locator, though readers should also quickly notice the repetition, and it is all there for the dedicated searcher.

This isn’t to say that I avoided subheadings entirely. I did use them in a few places, mostly for people, though even with people I found it difficult to avoid longer strings of locators. Many of these references are brief mentions and again reflect the repetition throughout the book. For example, here are two arrays for MacDonald’s friend, George Link, and wife, Joan.

Link, George K.K.: about, 234, 343n83; Lake O’Hara Trails Club and, 340n25; MacDonald and, 82, 91, 104, 107, 113, 114, 143, 215, 224, 233, 234, 239, 243, 249, 252, 253, 254, 256, 258, 264, 294, 301, 307, 308, 310; photographs, 246, 260
MacDonald, Joan: encouragement from to travel west, 13, 202, 205; letters to, 93, 96, 115, 120, 121, 122, 131, 167, 175, 200, 203, 204, 205–6, 211–12, 229, 230–31, 236, 240, 256, 265; Links and, 341n47; MacDonald’s departure west and, 250; mentions in MacDonald’s diary, 304, 308; O’Hara trip with MacDonald, 36, 123, 191, 217, 221, 222, 223–24, 259; photo album, 224

While I highly encourage you to include subheadings and to make sure that subheadings are clear, specific, and meaningful, I think it is also worthwhile considering the exceptions to the rule. I hope that my approach to the index for To See What He Saw, about J.E.H. MacDonald’s paintings in and around Lake O’Hara, is helpful for considering when subheadings may not be useful. If there is a lot of repetition in the text, if it is difficult to find meaningful distinctions, and if there is a hard space constraint, then it is okay to have long strings of undifferentiated locators. It is not ideal, but it may still be the best solution for that particular text and index.

Happy indexing,

Stephen

Stephen Ullstrom

2x award-winning book indexer and the author of Book Indexing: A Step-by-Step Guide. I teach you how to write excellent indexes, along with reflections on succeeding as a freelance indexer.

Read more from Stephen Ullstrom

Hello, It’s hard to believe I moved house two and a half months ago. This new house has reached a sort of equilibrium, in which much has been unpacked and is functional, and much is still in boxes and to be done. The baseline functionality is making what remains seem less urgent, though still a lot to do and now that fall is here, there is the pressure of winterizing before the snow arrives. You may have noticed that I haven’t written as frequently in the last couple of months. I’ve struggled...

Hello, So you are sitting down to write an index. You scroll to the first page in the PDF, or, if you’ve printed out the proofs, you place the first page on the desk in front of you, and then…what? What is your thought process? How do you decide what entries to extract? How do you read? Reading to index is different than reading to edit, reading to learn, or reading for pleasure. I think of reading to index as a process of disassembly. I try to identify how the author has written and...

Hello, Today’s reflection is in response to a question I received through the feedback survey. Thank you very much for your question, and my thanks to everyone who took the time to provide feedback. Your thoughtful responses are very encouraging and have given me good ideas for what to write and focus on. (And if you haven’t yet given feedback or asked a question about something that is puzzling you about indexing, and you would like to do so, the link to the survey is here. It is anonymous...