Article
0 comment

Pointing Readers in the Right Direction

Welcome back to this mini-series on the basic elements of an index.

I’m currently looking at what makes up an entry, which I described as “what this thing is + where to find it.” In my previous post I discussed main headings and subheadings, which form the first part of that equation. Today, I’m writing about the second part, “where to find it,” also known as locators.

Locators are the portion of the entry which tells readers where to find information about the main heading and subheading. They are like directions for the reader to follow. To be effective, locators need to be clear, specific, and accurate. 

There are three points that I want to make about locators.

The first is that a locator can be anything. Page numbers are usually the default locator, especially when indexing books, but other forms of locators can also be used, such as paragraph or policy numbers. The only criteria is that the locator is appropriate for the material being indexed.

My second point is that the locator needs to be clear and specific. Readers should understand how the locator relates to the text, and should be able to easily use the locator to find the desired information.

To give a few examples, page numbers are often augmented when referring to figures and tables or to footnotes and endnotes. For figures and tables, the page number may be placed in italics or bold, or have a fig. or t appended. For notes, the note number is usually appended to the page number, as in 253n43 or 265nn14-15. These allow the reader to more quickly pinpoint the information on the page.

For a cumulative index for a journal or multivolume series, the locator should probably include a volume or issue number alongside the page number, as in VII.343. For a policy document that I update every couple of years, I use unique policy numbers instead of page numbers, as in 20.2.1.2. These policy numbers both direct readers to the specific policy more quickly (especially if there are ten or more policies listed per page), and makes updating the index a whole lot easier as I don’t need to worry about the pagination shifting as policies are added, removed, and revised. 

When augmenting page numbers or using something different for a locator, it may be helpful to explain your choice in a headnote so readers understand how to interpret the locator. Page numbers, being the default, don’t need to be explained.

To give a few examples of locators:

conduction, 83, 84fig. 

convection, 85, 84t, 234n43

safety protocols, 2.1.13.4, 3.3.1.12, 3.4.3.6

thermodynamics, VI.343, IX.23

The last point I want to make is that the number of locators in an array should be reasonable for readers to search. As a general rule of thumb, no more than 6-10 undifferentiated locators. Larger arrays, with more than ten locators, should have subheadings to sort the references and make it easier for the reader to identify the relevant aspects of the subject. The concern is that searching through a long string of undifferentiated locators is time-consuming and may discourage the reader from finding what they need. Better to set the reader up for success by presenting locators in smaller chunks.

 

When writing an entry, the main heading and, possibly, subheadings, tell readers what the subject is, while the locator tells readers where to find information about that subject. Locators can be anything, and should be clear and specific. The number of locators should also be reasonable for readers to search. Do this, and you are setting your reader up for success.

Article
0 comment

Telling Readers What This Thing Is

In my last post I wrote about entries and arrays, which I described as the building blocks of an index. I defined an entry as “what this thing is + where to find it.” Today I’m going to expand on “what this thing is,” also known as main headings and subheadings.

The fundamental purpose of an index is to guide readers to the relevant information that the reader is searching for. To do that, the index needs to be clearly written, which begins with the first words that the reader sees. 

Main Headings

The main heading, also known simply as the heading, kicks off the entry. This is the first word or phrase that you see in an entry and array. It is typically a noun, and should be clear and concise. If a longer phrase is needed, the main heading should lead with the most important element. The main heading should also match how the term is used in the text, such as using the same spelling and capitalization. 

The heading should be reflective of both the text and the audience. Is the book discussing cars more generally or electric vehicles specifically? Or both? Will readers be reading this book to learn about the auto industry, new innovations, or specific brands and models? Or all of the above? To give another example, biblical characters such as Matthew, Silas, and Timothy probably don’t need a gloss clarifying their identity in a work of biblical studies to clarify their identities, but these names may be more unfamiliar to readers if they appear in other disciplines. 

Another consideration is whether or not to pluralize main headings. Should it be dog or dogs? Cantaloupe or cantaloupes? To start, be mindful of differences in nuance. Freedom is somewhat different from freedoms, for example. Otherwise, I tend to follow common usage. If a term is commonly pluralized, then I go ahead and make it plural in the index, which I think reads more naturally. 

To give a few examples of main headings:

Acts (biblical book)

Cleveland, Grover

electric vehicles

heat transfer

London (ON)

trade wars, retaliatory

Subheadings

For short arrays containing a handful of locators, a main heading is usually sufficient to specify what this thing is. But more specificity is often needed for topics with extensive discussion (usually when there are more than 6-10 locators) or if there are different aspects that readers would appreciate differentiated.

The subheading is placed after the main heading. Its purpose is to further clarify what this thing is. Because subheadings often differentiate references from one another, there are usually multiple subheadings per array.

Since the subheading is appended, there is more flexibility in how it can be phrased. Depending on the context, the subheading can be either a short word or phrase, or it can be longer and more descriptive.  In all cases, the relationship between the main heading and subheading should be clear. If possible, I try to also lead with the key word, which both affects how the subheadings are alphabetically sorted and, I think, makes it easier for readers to find the subheading as they scan the array. 

For example,

Acts (biblical book): authorship; within biblical canon; commentaries on; Paul within

Cleveland, Grover: first presidency; free-silver issue; legislative achievements; private life between presidential terms; second presidency

heat transfer: conduction; convection

Effective headings and subheadings connect readers to the text. Main headings are the point at which readers encounter the index, and readers should not need to guess what this thing is. The same is true for subheadings, if the reader decides to read further into the array. 

Tell the reader what they need to know. Be specific and concise. Do this, and your index will be well on its way to being excellent.

Article
0 comment

The Building Blocks of an Index

An index is a document that is scanned to find information. It usually spans several pages. But if you had to break an index down into its smallest part, what would that be?

An index is not like most books or documents in that it does not contain a narrative. It cannot be reduced to plot points or the components of an argument. An index doesn’t even contain proper sentences. Instead, an index is a compilation of references. Broken down, the smallest unit within an index is an entry. 

An entry has two components. Basically, “what this thing is + where to find it.” Using indexing terminology, this is “main heading + locator.” Or, to add another level of specificity, “main heading + subheading + locator.” From the entry, the reader can identify what they are looking at and where to find it in the text. For example,

Foxconn, 45

semiconductors: geopolitics of, 67

The second building block is an array. I like to think of an array as containing everything that an index—and by extension the book or document—has to say about a particular subject. If you want to learn about Foxconn, you search for the Foxconn array. Want to learn about semiconductors, you search for the semiconductors array.

If there is only one mention, then a single entry can serve as a single array. But more often, there are multiple discusses throughout the book, which lead to the creation of multiple entries. Combined together, the entries create an array.

Foxconn, 45, 49, 51-52

semiconductors: fabrication techniques, 54-57; geopolitics of, 67; history of, 23-25; properties of, 34, 44

Why are entries and arrays so important? No one writes an index composed of a single entry.

But every index begins with an entry, and as the index is written, the entries and arrays accumulate. It is through knitting the entries and arrays together than an index emerges.

Step one to writing an index is to write clear, concise, and specific entries, so that “what this thing is” is clear to the reader. Step two is to combine entries into arrays which are clearly organized and easy to scan. Step three is to sort and organize the arrays—creating the structure of the index—so that the index as a whole is easy to navigate. 

Each of these elements—the entry and the array—fit together, like interlocking pieces, to create a coherent whole.

A Note about Terminology 

I’ve noticed that not every indexer, including books about indexing, distinguishes between entries and arrays. I’m guilty myself of using the terms interchangeably, though I try to be clear when I’m writing.

But while terminology varies, I do think that the distinction is important. Because an index is composed of hundreds or thousands of pieces of information, it helps to know what these pieces are and how they interact with each other. An index is also easier to edit and organize if these building blocks are clearly written and well thought out.

As you index, how are these building blocks fitting together? How can you be more mindful of each piece of information and how it interacts with the entries and arrays around it? Does it make a difference to think about indexing as building up from the smallest unit to the larger whole?

Article
0 comment

Goodbye 2024, Hello 2025

Happy New Year! How is this first full week of 2025 shaping up for you?

I am having a slow start. I enjoyed unplugging from email and work for two weeks. I’m also recovering from a cold.

December was crazy busy, wrapping up nine indexes, which included a children’s book, one project which was simply names and biblical references, and two scholarly books that I began in November. So not quite as much work as nine indexes may sound, but still more than I bargained for. That was due to a couple of projects slipping and arriving when I did not expect and also, if I’m honest with myself, I did accept too much for December and didn’t leave enough margin for complications. 2024 was an odd year and I was trying to make up some missed income, but I should have been more disciplined and said no to a couple of projects.

2024 in Review

2024 was all about buying a house and moving. That dominated everything else in my life, including indexing. I’m thankful for this house. It still feels a bit surreal that I have a permanent place to live. I have always lived in anticipation of needing to move again within the next 1-4 years, and so a part of me is waiting to move again, another part is reassuring myself that I can stay where I am, and a third part doesn’t know how to compute living in a place for longer than four years. One day at a time, I guess.

Moving, settling, and learning the maintenance rhythms for this particular house has also taken time. There were a few months over the summer when I was indexing part-time at best. That impacted the number of projects I was able to complete, along with my income, so I am especially thankful for Elim, my wife, who is earning more than me. 

Looking at the numbers for 2024:

  • 44 indexing projects (down from 52 in 2023)
  • 25 trade books, 18 scholarly books, plus an index for a policy document that I update every couple of years
  • Worked with 12 publishers (30 indexes), 12 authors (1 index each), 1 professional association and 1 policy institute (1 indexes each)
  • 34 projects were from clients within Canada, 8 projects from clients in the US, and 2 projects from clients in Australia.

Overall, my numbers are fairly similar to 2023, despite fewer projects. My ratio of trade to scholarly books is similar, as is projects from publishers vs. authors, and where projects are coming from. I am very thankful for the publishers I work with and who continue to send me work year after year. Having these positive relationships and not needing to actively market as much definitely makes my life easier. 

One interesting point: one publisher sent me 11 books to index in 2024, which is 25% of my total projects. All of the other publishers sent me between 1-3 projects each. While I always enjoy working with that one publisher and I hope to continue to do so, I think this speaks to the value of working with a wide range of publishers, especially if they are fairly small companies. One or two publishers are not enough to fill my schedule, but 10+ combined keeps me fairly busy.

Indexing Highlights

Do you ever notice that certain topics can appear in waves, with two or three books in a row on a similar subject? I find that often happens to me and I wonder why. Very serendipitous. 

In the past few months I indexed two trade books on the Empress of Asia and the Empress of Ireland. These were both ocean liners owned by Canadian Pacific Steamships. The Empress of Ireland collided with another ship and sank in 1914 in the St. Lawrence River, causing the death of 1,012 people, Canada’s worst maritime disaster. The Empress of Asia had a longer career, serving in both WWI and WWII, before being sunk by the Japanese near Singapore. Reflecting their different trajectories, Beneath Dark Waters: The Legacy of the Empress of Ireland Shipwreck, by Eve Lazarus (Arsenal Pulp Press, 2025) is tightly focused on the collision and aftermath, while Oceans of Fate: Peace and Peril Aboard the Steamship Empress of Asia, by Dan Black (Dundurn Press, 2025) follows the Asia over its 30 year lifespan. Both focus on the lives of the passengers and crew, which is what brings these harrowing stories to life. I recommend both if you enjoy maritime history. 

Taking the prize for the most unexpected subject matter is Dialectics of the Big Bang and the Absolute Existence of the Multiverse, by Gregory Phipps (University of Alberta Press, 2024). Did you know that the first second after the Big Bang can be divided into six epochs? Difficult to study empirically, and so Phipps uses Hegelian dialectics to unpack what may have happened. A fascinating read, and also very challenging to index. Philosophy is not my strong suit. Thankfully the author seemed happy with the result. 

Whither 2025?

For 2025, my keyword is margin. I want time to write, to work on the house, to spend time with Elim, and for exercise and rest. This means managing my indexing schedule so that I’m not constantly chasing deadlines and needing to work long hours. I still have an income target, which is a decent amount but also about 10% less than what my target has been in the past. And I’m okay with that. The pace of work hasn’t felt healthy or sustainable, and I don’t like feeling like there are areas of my life I am missing out on.

So here’s to finding a better balance in 2025.

Article
0 comment

Making the Index Invisible

So the 18th edition of the Chicago Manual of Style dropped in September. I have to admit I have not bought a copy. While I think their recommendations are solid, I find I don’t use it very much, since I only index and not edit. But I do know some editors who are very excited about the new edition, and there has been chatter among indexers as well on the changes to the chapter on indexing.

The main change in regards to indexing is 15.66, which states:

Chicago now prefers the word-by-word system of alphabetization over the letter-by-letter system (but will accept either in a well-prepared index).

 

I think this change makes sense.

I personally most notice the difference in sorting when indexing Asian studies books, where I tend to see a lot of surnames like Chen, Kim, and Liu. Being so short, these names often get mixed up with other headings when sorted letter-by-letter, whereas I think the index is easier to scan if all of the surnames are sorted together. I’ve also received instructions from a scholarly press to sort the index letter-by-letter except for the names, which the press wants force-sorted word-by-word. Which begs the question: why not sort the entire index word-by-word?

For example, here is a comparison of letter-by-letter compared to word-by-word.

Letter-by-letter sorting
Liang Ji
Liang Qichao
Libailiu (Saturday)
Li Boyuan
Li Chen
Life Weekly
Lin Meijing
Li Shirui
List, Friedrich
Liu Denghan
Liu Jiang
Liu, Jianmei
Liu, Lydia
Liushou nüshi (Those Left Behind; film)
Liuxuesheng (overseas Chinese students)
Liu Yiqing
Li Yuanhong
 
Word-by-word sorting
Li Boyuan
Li Chen
Li Shirui
Li Yuanhong
Liang Ji
Liang Qichao
Libailiu (Saturday)
Life Weekly
Lin Meijing
List, Friedrich
Liu Denghan
Liu Jiang
Liu, Jianmei
Liu, Lydia
Liu Yiqing
Liushou nüshi (Those Left Behind; film)
Liuxuesheng (overseas Chinese students)
 

The word-by-word sorting, for me, is a lot easier to scan and parse when like surnames are grouped together, and when names are sorted together above other terms. It makes me confident that I am seeing all of the names present, rather than being concerned that I am missing a name that is buried below.

Also note that the Liu names are sorted according to the clarified 15.85, which states:

When the same family name is inverted for one person but not for another (e.g., “Li Jinghan” and “Li, Lillian”), the names may be listed together and alphabetized by first names regardless of the comma.

 

This also makes a lot of sense and has been my practice for a long time. By ignoring the comma, the second portion of the name is treated equally for all names, whereas if the comma is taken into account, all the names with commas sort to the top and may cause some names to appear out of order. For example,

Liu, Jianmei, 48
Liu, Lydia, 91
Liu Denghan, 148n6
Liu Jiang, 105
Liu Yiqing, 27, 144n13
 

For another interesting comparison, as a colleague pointed out, try looking for the sorting differences in the indexes between the 17th and 18th editions of the CMOS. And if you’d like to see a full list of the changes to the indexing chapter in CMOS 18,see here.

So will I now unilaterally switch to word-by-word sorting for all of my clients who request that the index follows CMOS? I don’t think so, unless I think that the index will really benefit. I think it is better if I first ask my clients if they want to change, so we are both on the same page and I am not springing a surprise on them. And, to be honest, for most indexes I don’t think that the difference between word-by-word and letter-by-letter sorting will be that noticeable.

This brings me to my larger point, which is that the mechanics of a well written index should be invisible to the user. I doubt that any reader will browse the index and think, “I wonder what the alphabetical sort is?” That is not the reader’s concern. What the reader cares about is quickly finding information.

To facilitate finding information, every aspect of the index needs to work together. This includes the sorting, the structure, term selection, phrasing, and cross-references. When it works, the reader shouldn’t notice how the index works because the reader is too busy digging into the book. When the index does not work—that is the point when the reader is pulled out of the index and is frustrated at their inability to access the information they want. The reader may not be able to articulate whythe index is not working, but something about the contents and mechanics of the index is wrong.

Bringing this back to sorting, for many indexes the difference will be negligible between letter-by-letter and word-by-word sorting. As CMOS states, they will accept either in a well-prepared index. For other books, like for me with Asian studies titles, the difference will be more pronounced.

When indexing, pay attention to when the difference matters. Make decisions based on what will make the user experience the most seamless. Pay attention to how the different elements of the index fit together. Striving to make the index invisible may be an odd way to think about indexing, but to be invisible means that the index works, which is what we ultimately want for our readers.

Article
0 comment

Paying Attention to Terminology

I am writing today about some decisions that I needed to make on a recent index. In the grand scheme of the index, these decisions only affected a few entries. I am tempted to brush these off as not very important and not worth discussing. Yet much of indexing is about paying attention to the details without getting lost in the details. And I think this is a unique situation that illustrates an important point about term selection. At least, it made me sit up and think carefully as I was working.

A good index encapsulates two different goals, which can sometimes seem like they are in opposition to each other. The index needs to be both a reflection of what the author has written and be an attempt to clearly communicate with the reader. Lose one of these aspects, and the index ceases to function.

Term selection is key to achieving both of these goals. The terms used in the index need to both match the text and how the reader is likely to search. Ideally the author and the reader are in alignment, but sometimes the author uses different language than what the reader might expect. In those situations, the index may need to bridge the gap.

I recently ran into this issue when writing the index for Saint Paul the Pharisee: Jewish Apostle to All Nations, by Father Stephen De Young (Ancient Faith Publishing, 2024).

If you are familiar with Christianity, the title may be a hint that the author is taking a different tact with terminology. While Paul was a pharisee prior to his conversion, he is now more commonly known as the Apostle Paul, or Paul the Apostle. Yet here Fr. Stephen is emphasizing Paul’s Jewishness.

In the book’s Introduction, Fr. Stephen addresses this question of terminology:

Throughout this book, I have deliberately eschewed certain language. This language is certainly acceptable and has become the usual language of the Church. However, familiar terminology can sometimes be misleading. By using the word Messiah instead of Christ, community instead of church, or Torah instead of law, I hope to unsettle commonly held notions and help the reader reassess Paul in his historical context, rather than project the experience of present-day Christians into the past.

 

This shift in terminology also extends to names, which is where I noticed the biggest difference in regards to the index.

In addition to “Paul the Pharisee,” Fr. Stephen also frequently refers to Paul by his former name, Saul of Tarsus. Jesus is referred to as “Jesus of Nazareth,” rather than Jesus Christ. A figure such as the Apostle John, also known as John the Evangelist, John the Theologian, or John the Divine, is here referred to as John, the son of Zebedee. None of these names are incorrect, but they are names that are less commonly used. They support the author’s focus on Paul and the early Church’s Jewish context and alerts readers that the author is taking a different approach.

From an indexing standpoint, do I follow Fr. Stephen’s lead? By using these names, I would provide continuity with the text and reinforce the point that Fr. Stephen is trying to make. But will readers still recognize these names in the index, outside of the context of the text? I am not helping anyone if I include names and terms that readers are unlikely to recognize.

In the end, I decided to lean into the author’s terminology. Christians form the primary audience for this book and, I assume, are familiar enough with with these Biblical figures, even if these are not the names typically used.

Paul I simply indexed as “Paul.” As the subject of the book, I decided a gloss was unnecessary. I also included a See cross-reference from Saul of Tarsus, for any readers looking under Saul and to keep all discussions of Saul/Paul in a single array.

I indexed Jesus as “Jesus of Nazareth,” with a subheading for “as Messiah,” to reflect how the author discusses Jesus. I indexed the other Biblical figures as is (“Peter,” “Silas,” “Timothy,’ etc…) except for when a gloss or tag was needed to disambiguate (for example, “James, brother of the Lord’ and “James, son of Zebedee”). This is again following the author’s approach and trusting that readers will recognize these names.

I did, however, include glosses for several of the provinces and cities discussed, such as “Achaia (province)” and “Perge (city),” especially the less well-known places (I didn’t include glosses for cities like Athens and Rome). This may not have been necessary, but I personally like knowing where things are and what things are, so as a reader I would have appreciated the differentiation.

As I wrote at the beginning, these names form a small proportion of the overall index. Was it really worth spending time considering how best to balance the author’s approach versus reader expectations? There are plenty of other discussions in the book, such as discussions about Paul’s missionary journeys, the history of the early Church, and theological issues that Paul addresses in his epistles, that I also wanted to get right.

And yet names matter and terminology matters. The index would have presented a different message if I had used more conventional names for these figures and the index would have appeared disjointed from the text. Writing a good index is often about paying attention to the details so that the entire index works together as a whole and in conjunction with both the text and readers. The trick is to see both the details and the whole. It can be easy to lose sight of the big picture.

For this book, while the author opted to shift the terminology to make a point, I decided that most readers would still be able to follow along in the index. I didn’t need to include much in the way of signposts and clarifications. But for other books, extensive use of cross-references and glosses may be necessary. While reflecting the text and the author’s intentions, the index also needs to be responsive to readers. Thankfully, we have tools to bridge that gap.

The first step, though, is paying attention to the language used by the author. The next step is considering the audience. Do the two match? From here you can select terms and write an index that is clear and recognizable to all.

Article
0 comment

My Index Editing Process

Last time I wrote about reading like an indexer and what it is I do and look for when reading a text and writing the rough draft of an index. Today I’d like to reflect on my editing process.

A few months ago I started tracking my time when I index. I had previously done so, but not effectively and I eventually gave up. This time, I’ve created a new system and a new spreadsheet that is much easier to use, and I am a lot happier with the results.

One of my insights so far is that I spend about an equal amount of time drafting and editing. I have to admit that this surprised me. I knew that editing took up a fair amount of time, but I didn’t realize that the time spent is often about 50/50. For some indexes, I actually spend a little more time editing, making the time split closer to 45/55 or even 40/60.

Reflecting further on my process, I tend to spread drafting the index over 3-6 days, depending on the length of the book. Whereas I tend to edit within 2-3 days. When drafting, I am learning what the book is about. When editing, I am fully immersed in the index and I treat it more like a sprint. It probably also helps that by the time I get to editing, the deadline is looming.

I’m realizing that I also tend to draft quickly. I do try to write a fairly clean draft, taking into account context, clarity, and relevance, as I previously discussed. I believe in trying to set myself up for an easier edit. But I also know that this is not my final draft and that some things won’t become clear until I’ve read the whole book, and so I also try to keep moving.

Editing an index, for me, is both seeing the index as a whole and going through the index line by line. I like to give myself space between drafting and editing, which usually means sleeping on the draft and beginning to edit the next day. This helps to give me some distance so I can more clearly see the whole index with fresh eyes.

I usually begin by skimming the index, making note of the larger arrays for the metatopic and supermain discussions. This reminds me of the structure I am aiming for, and is a chance to consider if I want to make any major changes. I then start at the top of the index and work my way down, line by line. I know some indexers edit using multiple passes, each pass looking at a different element. I think I would go utterly cross-eyed and unable to make sense of the index if I tried multiple passes. Instead, my goal is to fully edit the array in front of me before I move on to the next. This may mean jumping around the index to also edit related arrays, and sometimes I will go back to re-edit an array if I change my approach, but generally speaking, I systematically move through the index.

With each array, I am first of all looking for clarity. Does the main heading and any subheadings make sense? If there are subheadings, I look to see if any can be combined or reworded, or if subheadings need to be added for unruly locators. I consider if anything needs to be double posted, and check to make sure that is done properly. I consider and check cross-references. I investigate any notes I may have left for myself. I also spot-check a few locators to make sure I understood the text properly. I may also run a quick search of the PDF to see if I missed any references. I don’t check every locator, which I think would be very time-consuming—to a certain extent, I need to trust that my drafting process was thorough and accurate—but these spot checks do provide peace of mind and I do sometimes find errors.

Reviewing arrays with no subheadings is usually quick, unless I’ve left a note for myself or I decide to spot check. Arrays with subheadings take more time. If an arrays has 20+ subheadings, I may spend as much as twenty or more minutes making sure that the array is in order. I often find the larger the book, the larger the index, the more subheadings there will be, and the longer editing will take.

Considering my process, I do wonder if I can shave off time. I could spot check a little less, especially for simple arrays with no subheadings, trusting that I picked up what was necessary. I can also pay more attention, when drafting, to larger arrays, so that editing them isn’t so onerous. I could also explore using more macros and patterns for batching tasks such as double-posting or removing subheadings. What I like about my process, though, is that it is thorough and I can clearly see what is completed and what is still to come. Editing line by line helps to keep my thoughts in order.

Other Approaches to Editing

My approach to editing is not the only approach, of course. I’ve mentioned making multiple passes. I also know of indexers who do a quick edit at the end of each day, while drafting, so that the draft is cleaner. I’ve also heard indexers who say that they do such a thorough job drafting that the editing process only takes them a couple of hours. I don’t know how that works for them. I seem to need a lengthier editing process for the index to gel and come together. And that’s okay. We are all different. What matters is that you find a process that works for you.

I find it interesting to hear how others index, even if it is not something I would do myself. I hope this glimpse into my process gives you something to think about.

Article
0 comment

Reading Like an Indexer

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 structured the text, and I then pull apart all of those pieces, big or small, and reassemble them into the form of an index. This is very much an active reading, in which I am identifying, analyzing, and making decisions. 

I generally look for two types of information when I draft an index.

  • Specific details. These are names, places, companies, concepts, etc… that are explicitly mentioned and discussed. These are usually fairly obvious. If there are a lot of names or other such details, I may index a few pages, pick up these details, and then go back and re-read to make sure I also understand the larger discussion.
  • Broader topics. These range from the metatopic—what the whole book is about—to supermain and regular discussions—both themes spanning the book and what specific chapters or sections are about. It is important to have index entries which correspond to these broader discussions, and so in addition to picking up specific details, I try to also understand the big picture. These broader topics are also tied to the structure of the index, as I consider how best to reflect the book’s structure in the index, and as I anticipate that these large discussions will become large arrays, anchoring the index. Depending on the book, as mentioned, I may need to read a section two or more times to properly mine all relevant entries. 

Once I have identified the large and small pieces that the book is made of, I need to decide how to translate that into the index. Here are a few tips I find helpful to keep in mind.

  • Understand what you are reading. This may seem obvious, but I think it is worth stating. The temptation, at least for me, is to guess if I am unsure and to create an entry anyway. And sometimes guessing is the best I can do in that moment. I flag the entry for revisiting later and I move on. What can be more effective, though, is to read ahead a few pages until I do understand, and then go back and create the entry. It’s okay to be patient. Taking the time to understand can pay off later with better understanding of what comes next in the text and with less editing due to a stronger draft. 
  • Place the information in context. Are you looking at a specific detail or a broader topic? How does the detail or topic relate to other details or topics? Can this be turned into a subheading? Should it be double-posted? Is a cross-reference necessary? What other entries does this suggest? While subheadings, cross-references, and double-posts can all be revisited later, when editing the index, I like to start thinking about them while writing the rough draft. The information in the book is an interconnected web, which the index should reflect. So as part of your thought process, get in the habit of looking for these connections. 
  • Filter for relevance. In addition to understanding the larger context, also pay attention to relevance. Think about the audience before you begin writing the index. Consider how much space is available for the index. What should the index focus on? Sometimes I am not sure if an entry is relevant and so I pick it up anyway, labeling it for possible deletion later. But the more I can filter out now, the less I need to cut later. 
  • Communicate with clarity. This is especially true for subheadings. Make sure that readers understand what this entry means. Be concrete and, where relevant, link back to the larger context. You don’t want to leave readers guessing, nor do you want to leave yourself guessing when you come around again to edit.

All combined, this is a lot to do while reading and indexing. It can be difficult to identify both specific details and larger discussions, while also weighing relevance, and paying attention to the context, and thinking about related entries, and thinking about how best to phrase for clarity. Reading to index is a skill that takes practice.

Remember too that the rough draft does not need to be perfect. My drafts are certainly not perfect, and while I am thinking about all of this while drafting, I spend about an equal amount of time editing. 

How you read is up to you. I tend to start reading and I type entries into Cindex, the indexing software that I use, as the entries come to mind. Other indexers prefer to first mark up the proofs, identifying what is indexable and making notes for themselves, before they go back and type up the entries. There is no right or wrong approach, so long as you are paying attention to all aspects of the text, both big and small.

If you are newer to indexing, you may find marking up the proofs to be a good way to visualize or make concrete this thought process. I marked up proofs the first 3-4 years that I indexed, which in hindsight was necessary for me to engrain this way of reading. Once indexing started to become habit, I stopped marking up, though I still read ahead sometimes to better understand what the text is about. 

Writing an index is a unique way to interact with the text. It does require a shift in how you read and see the text. Once you make that shift, indexing becomes easier. 

Article
0 comment

Is AI Indexing Nearly Here?

No surprise, publishing continues to react and interact with artificial intelligence. A couple of colleagues recently raised AI on a couple of indexing email lists. I get the sense that many indexers are concerned about the potential for AI to replace us, or at least that publishers will believe that AI can replace a human-written, thoughtfully constructed index. I have to admit I also feel uncertain about what the future holds. I wrote about AI and indexing last year, and I think it is worth considering again. 

Is Indexing by AI Nearly Here?

One colleague flagged this article from The Scholarly Kitchen, “AI-Enabled Transformation of Information Objects Into Learning Objects,” by Lisa Janicke Hinchliffe. Hinchliffe reviews three new AI tools which purport to help readers access and understand academic writings. Of particular interest to indexers is what Hinchliffe writes about Papers AI Assistant: 

When exploring the functionality as a beta tester, I was curious how the results compared to my pre-AI tool practice of making heavy use of CTRL-F to locate keywords in lengthy texts. I found that, not only did the Papers AI save me a great deal of time by providing me with an overview annotated with links to specific sections of the text, it also often alerted me to places in the text where my topic of interest was conceptually discussed without the use of the specific keywords I would have searched.

Did you catch that last bit? Papers AI Assistant can apparently identify discussions of interest without the use of a keyword search. That is what a good index is supposed to do. Is this the beginnings of an AI that can replace indexers? Hinchliffe also writes that, “I am excited by the possibilities these AI tools offer for moving the focus from access to information to comprehension of it.”

A few thoughts: I have to admit that I am skeptical of the claim or hope that Papers AI and similar tools will help readers comprehend information. My sense is that AI works best as a tool, with the user clearly understanding its strengths and limitations, and with the user making the final decision on the quality of results and how best to use the results. That is similar to how I use the search function when indexing. Search is useful for double-checking facts and mentions, but I know that it doesn’t catch everything and isn’t good at providing context; I still need to read and understand the book. My fear is that many users will uncritically accept whatever the AI tool tells them, turning a program like Papers AI into glorified CliffNotes and enabling an even shallower engagement with the text. 

I think it is also worth pointing out that what is described here is not an index. An index is a static document that is browsable. That is very different from an AI highlighting a handful of potentially relevant passages. Browsability is key to an index because it allows the user to serendipitously find information they didn’t know they wanted to find. Being handed a few options leaves the rest of the text opaque and unaccessible. I imagine a user can keep asking the AI new questions, but that puts the onus on the user to know what they are searching for and how to ask relevant questions. 

Of course, if an AI can identify concepts and discussions in the absence of clear keywords, then a logical next step could be to ask that AI to generate an index. I can see value in the ability to create an index on the fly, for any document. I don’t know how much I would trust such an index, though. Hallucinations is one issue. Another is that AI, essentially, is built upon algorithms. Answers are always going to be follow a certain pattern. While indexing is built upon rules and conventions, the indexer also plays a key decision-making role as they shape the contents, phrasing, and structure. These judgement calls extend beyond the formal rules of indexing to take into account elements such as the audience and usability. I am skeptical that an AI would be able to understand and produce these nuances.

Another issue is that these AI tools are entirely digital. They will not work on a print book, though, of course, an AI-generated index could be published in print. Is the future of publishing and of engagement with texts entirely digital? Perhaps in academia and other specialized fields, in which there is so much information to access and consume. Print sales remain strong, however, and I am hopeful that there will continue to be a place for print indexes. Perhaps the future—finally arrived?—is what embedded indexing has long promised, which is one index capable of being used in multiple formats. 

Besides AI replacing indexers, I think it is also worth considering how we as indexers can use AI in our own work. I am aware of one colleague who uses ChatGPT to summarize complicated books and to answer queries about the text, which helps that indexer comprehend the book more quickly. Which sounds very similar to what Papers AI claims to do. I think that is a legitimate use of AI. So long as the indexer is in control—using the AI as a tool, understanding both indexing best practices and the contents of the book, and is actively shaping the index—then why not use AI? I’m also open to having AI index elements which are time-consuming to pick up, such as scientific names, so long as the indexer is providing quality control. What I don’t want to see are indexers—or anyone else—passively accepting an AI-generated index, assuming that it is accurate and functional when it is actually not. That is my worse nightmare about AI, that we abdicate our critical thinking and decision making skills, potentially leading to errors and disasters because we have lost the ability to assess what AI is telling us.

Author Pushback

In contrast to the gold rush to embed AI into publishing, another colleague pointed out that some books are beginning to be published with prohibitions against AI and machine learning listed on the copyright page.  I also recently noticed this in a book I am indexing.

I’ve also heard from a trade client that their authors are starting to insist that book contracts include a clause that their books will not be uploaded or otherwise used to train AI. By extension, this means that all freelancers hired by this press, including myself, are not allowed to use AI tools while working on their manuscripts and proofs (which isn’t a problem for me, since I wasn’t doing so anyway). 

Will authors and publishers win against AI? Will publishers find ways to enforce their contracts and prohibitions? Will publishers change their minds, or will AI developers sufficiently address the fears that authors have? I suspect this may be an area where the publishing industry goes in two different directions: some segments, such as academic publishing, which prize easy access to information (provided you can get behind the paywall), will embrace AI, while other segments, which care more about the author and which sell directly to readers, will reject AI. 

Or, maybe AI in publishing is a bubble and these new applications will fail to live up to their hype. 

I still think that someone will try to develop an AI capable to writing an index. Some publishers will probably adopt it for the sake of saving time and money, even if the resulting indexes are useless. I am also hopeful that the value of the human touch will remain. Even if AI is incorporated into our work, I think there is still place for human guidance and discernment. Machines may be capable of generating an approximation, but only humans can create what is truly useful for other humans.

Article
0 comment

One Year Book Birthday!

My book is one year old! Well, close enough to a full year. The official one year mark is July 11, two days from now. 

I feel like this anniversary has snuck up on me. Sales for Book Indexing: A Step-by-Step Guide have slowed over the last few months, but still plugging away at 5-8 copies per month. I probably could do more to market the book, though I find my attention elsewhere, and at a certain point, I think, you need to let books grow on their own. But I am still very proud for what I’ve accomplished writing and publishing Book Indexing. I occasionally hear from people that they have bought and read the book, which is always a lovely surprise and affirmation.

With the book out in the world for a full year, I thought this would be a fun opportunity to do a quick round-up on how the book has fared, as well as a good time to announce that the ebook version is once again on sale at Smashwords. 

Sales Update

Book Indexing has sold 206 copies to date, which I am thrilled about. I was really hoping to hit the 200 copy milestone within this first year. This breaks down to 106 print copies and 100 ebook copies. Ebook sales appear to be on the verge of overtaking print. Maybe Book Indexing can reach 300 copies by this time next year?

I find this breakdown between print and ebook interesting because I think it bucks a few different expectations. On the indie author side, my understanding is that the vast majority of sales tend to be ebook, though that may also be primarily for fiction. I am not sure what the numbers are for self-published nonfiction. While on the indexing side, most indexers I know are book people and like to own physical copies. So while I am not surprised at the number of print sales, I am a bit surprised at how print sales have slowed while ebook sales are holding steady. On the other hand, some of the ebook sales are from places like Japan, India, Serbia, and Australia, where I imagine it is more difficult or expensive to get a print copy. Whatever the reasons, I think I made the right decision to make the book available in both formats, and I’m happy that Book Indexing is finding its readers. 

Library Availability

I also recently checked Book Indexing in Worldcat and was surprised to see that it is available from five libraries, including public libraries in Greeley, CO; Richardson, TX; and Washington, DC. A huge thank you if you put in a word for me at your local library.

Libraries can order both the print and ebook versions. I think having the book available in libraries is a win-win for everyone. I still receive royalties for the sale and people can discover the book for free. If you’d like to see Book Indexing in your local library, please consider contacting your library and requesting it. I know my local library welcomes requests and yours probably does too. 

Marketing

I had a bit of momentum in the first six months or so after Book Indexing was publishing. I pushed past my fear of stuttering in public and completed two podcast interviews. The first was with Mark Leslie Lefebvre on his Stark Reflections podcast and the second was with Michelle Guiliano on the Freelance Indexer Exchange

I also received two positive reviews, from Daniel Heila in Key Words and Madelon Nanninga in The Indexer. I am so grateful for their feedback and kind words. With a book like this, I hoped it would be well received by my peers and colleagues, but it’s hard to predict. At least, I don’t want to assume. 

I also recently published an article in the June 2024 edition of The Indexer, in which I discuss my experience writing and publishing Book Indexing.

Otherwise, my focus has shifted. I still have my regular indexing workload. I recently presented at the Canadian indexing conference and am preparing to present again at another conference in a couple of months. I’ve also been getting back into writing fiction.

Looking ahead, one of my goals this year is to redo my website, which is badly out of date. Among other aspects to update, I want to better showcase my book and explain what it is all about. I am also thinking of taking, probably in the fall, Austin Church’s six-week Morning Marketing Habit course, to learn and develop better marketing habits, for both my indexing work and my book. For the time being, these are my two marketing goals going forward. 

Smashwords Summer Sale

If you are interested and haven’t yet picked up the ebook version, Book Indexing is once again 50% off at Smashwords.  The sale runs for the entire month of July. It’s hard to learn how to index for much cheaper. If you know of someone who would be interested, please feel free to share the link. Recommendations count for a lot.

Thank You

Thank you again for all of your support on this writing and publishing adventure. I wouldn’t be here—and Book Indexing wouldn’t be here—without your interest and encouragement. I am grateful to have you as a reader.