I’m currently indexing a history of nuclear reactors. It is about 300,000 words. Meticulously researched and written, with a strong narrative.
It is a big book, and it is taking a while to get through. It is also not the only large volume I’ve indexed this year. I feel like I’ve done more than usual, including an Oxford handbook on Baptist studies, an edited collection on Black Canadian art and literature, and a biography of Canadian poet Margaret Avison. These are books that are the equivalent of two or three regular-length volumes.
Large books can be challenging to index. I have a theory that the length of the index grows exponentially with the length of the book (while, maybe not quite exponentially, but the length does grow), because the longer the book, the more details there are to index, the more locators there are, and the more likely subheadings are needed. Subheadings take up more space and take more time to write and edit, and so the work goes on and on. Also, the larger the book, the more there is to keep in mind. I need to remind myself to reset my expectations for how long the index will take.
I still want to complete the index efficiently and as quickly as possible, even if the overall number of days and weeks is longer. I’ve been reflecting on what it is I do that is different compared to indexing a shorter book. This is what I’ve gathered so far:
- I write more notes for myself, such as brief summaries for each chapter. Because there is so much more to remember, I don’t want to forget what the beginning of the book was about by the time I reach the end. These notes can also help me see the overarching storyline and themes running through the book.
- I slow down and consciously remind myself to connect back to the big picture. With so many pages to get through, the temptation is to rush and to focus on picking up the easy entries—the low-hanging fruit—of people, places, reactors, chemical elements, etc…Those details are important and need to be picked up, but why are they important? What is the larger discussion or story? I need to make sure that I am creating headings and subheadings at those broader levels too, which means slowing down and understanding what all this is actually about.
- I write subheadings at a broader level. I still pick up plenty of smaller details, but I think broader subheadings are both easier to understand and navigate, and can help keep the array at a manageable length. For main characters and topics, which are going to have a lot of subheadings anyway, indexing less granular may be the difference between forty subheadings versus sixty or eighty, for example. Forty subheadings is still a lot, while still being easier to scan.
- As I mentioned, broader subheadings can also be easier to navigate. This is because they encompass more and clearly express the larger context. Say a person is involved in constructing the National Research Experimental (NRX) reactor, is quoted reflecting on the reactor, and is also present for the reactor’s meltdown. A more granular approach would be to have separate subheadings for each of those three elements, which are arguably distinct. But in a large array, those three subheadings may sort apart from each other and a reader may not see all of them. Three distinct subheadings also take up more space (see point above). Better, I think, for a single subheading at a broader level, “National Research Experimental (NRX) reactor and,” to capture all of those discussions. The details of construction and meltdown can still be delineated as subheadings under the reactor itself.
- While indexing at a broader level, I still want main headings and subheadings to be clear and specific. Indexing at a less granular level is not synonymous with being vague. If I go back, say when editing the index, and I don’t know what the subheading is referring to, then I can’t expect the reader to know. The meaning needs to be clear. Which reactor? Which relationship? Which concept or discovery? I try to make my first pass as clear as possible, so I have less work on my second pass and so I don’t leave myself confused when I come back around again.
- Lastly, I want to acknowledge that I use subcontractors on this large projects. I usually ask subcontractors to pick up the names of people, and perhaps also other common elements, such as, for the Avison biography, titles of poems and other works. Having a subcontractor handle these aspects frees up my headspace to focus on the subject entries and the overall structure of the index. It also helps me to get through my own draft more quickly, because I have less to pick up. So many thanks to the indexers I work with. With so much material to get through, I find it can make a noticeable difference.
In one sense, indexing a large book is no different from indexing any other book. I still pick up the same types of entries and my process doesn’t change too much. On the other hand, everything that makes indexing a regular monograph difficult is magnified simply because there is more of it. There are more details, more entries, more subheadings, more cross-references. I find writing the index requires a bit more planning, more notes, and more patience. Because the big picture is so big, it can be difficult to focus on, and so I need to make an even more conscious effort to keep referring back to what the book is about.
The big picture—the story that is being told—is the underlying aboutness, which needs to be visible in the index. I don’t want to get lost while indexing, and I don’t want the reader to be lost either. I need to slow down, think through my decisions, make sure I am seeing as clearer as I can in that moment, so that the reader can hopefully see through me.