Article
July 2, 2018
1 comment
by Stephen

Three Indexing Mind Hacks

Photo by Patrick Perkins on Unsplash

It has so far been a busy summer. That means tight deadlines and renewed thoughts about how to be more efficient in my indexing process. I mean, indexing is tough. It is constant analysis, understanding what the text means and discerning how to make the text accessible to readers. If there is a way to simplify or expedite part of the process, it does make a difference on overall indexing time and cognitive load.

Learning how to effectively use indexing software is one approach that is commonly advocated for becoming more efficient. I agree, and I think there is more that I can learn with the software I use, Cindex. 

As I have written about earlier, practice is essential for becoming a more efficient indexer. I find so much about indexing is understanding the different ways a book can be structured, understanding the different ways an index can be structured and written, and understanding when to go with one approach versus another. For me, at least, the only way I can learn this is by doing, over and over again, and being mindful of what I am doing so that I can learn with each index. I think that I am more efficient now than I was even just a year ago. I hope to continue to improve. 

Recently, though, I have been thinking about three techniques I use. These are all ways to externalize and capture my thoughts so I do not have to keep everything in my mind all at once. 

Mind Mapping

Mind mapping is a way to quickly diagram relationships. I find this exercise most helpful for understanding difficult books. There is something about writing down the different components of an argument, and physically drawing lines between them, that boosts clarity. It can also be a way to see if I have captured the full scope of the book in the index, as I compare the mind map, based on the book, to the index. I have been finding it so helpful that I am starting to do a quick mind map for all indexes I write, usually before I start the final edit. It only takes about ten minutes, and it gives me an opportunity to reflect.

There is a website on mind mapping, if you want to learn more. Software is available, both free and for a price. I occasional use Scapple, but honestly, I usually just use a pen and a scrap piece of paper. 

Notes

Another technique I have used for years is keeping notes. I use Notes, a program on my MacBook. I have one note per project, and I simply keep a running list of whatever I want to remember for later. These are often notes about terminology, if I am trying to decide between two or three options. Or these can be questions for the author, or errors that I am finding which I want to share with the client. Sometimes I just free write, in order to understand a concept or a relationship. For some books, I will just have a couple of notes, while for others I’ll end up with a page or two. 

By making a note, I am removing the thought or question from my mind, and I am giving myself permission to move on, knowing that I will be able to come back later and resolve the issue. There is too much thinking going on while indexing to remember every last error I found and question I have, so writing the note down frees up a lot of cognitive space. This is also a recognition that for a lot of issues, I will not know the answer until I have read further in the book and seen how the issue is addressed elsewhere, or perhaps I do need to ask the author. In the meantime, I have to keep working, and making notes that I can refer to later allows me to do that.

Labels and Highlights

Coming back to indexing software, there is a feature in Cindex, the software I use, that I am appreciating more and more as a form of note-taking. This is the ability to label, or highlight, entries. I assume the same can be done in other programs, like Macrex and Sky. 

When I label entries, I am flagging the entry with a colour to remind myself to take action at a later date. I will often use two or three different colours to remind myself of different things. The most common is for an entry I might want to cut. Especially if space is tight for the index, it saves a lot of time at the end to be able to search for the labeled entries and hit delete for all of them. I use a different colour if I think I might want to remove subheadings. Another common reason is for entries I want to revisit, but I am afraid I will forget if it is not labeled. 

As with notes, using labels is about externalizing my thoughts so that I can put that thought away for later.

Working full time as an indexer is often about finding ways to be efficient, so we can maintain a full schedule without burning out. These are three mind hacks that I use to process my thoughts more efficiently, and to focus better without being distracted by a host of other thoughts. If you are an indexer, what techniques do you use? I am curious.

Article
May 28, 2018
1 comment
by Stephen

How to Marinate an Index and Other Time Factors

“How long does it take to index a book, anyway?”

This is one of the most common questions I am asked by non-indexers. It is a fair question. What is this alchemy of words and numbers that I do from which an index is created? Do I actually have to read the whole book?

This is also an important question for editors and authors who are looking to hire an indexer. How much time does the production schedule need to allow for indexing? If a rush job is required, how rushed is reasonable?

To answer this question, I often say that I can complete most indexes in fifteen to twenty-five hours. These are hours spent at the computer, actively working on the index. This is true enough, in that I time myself and these are the numbers I get. But it is still a simplistic answer. A better answer is, if I have no other projects on the go, I can complete an index for a 200 page book in three days. Three long days, depending on the book’s content, but still, three days. A week is more comfortable for me, for most books. I currently index, on average, 4-5 books per month.  

Most of my clients, when they send me a project, give me two to four weeks to complete the index (different clients have different schedules). Occasionally I am asked to complete an index in less time, which I might be able to do, but I still prefer at least two weeks. Why is this? Does this not contradict what I wrote above about completing an index in three days? Even three days is a somewhat simplistic answer. There are a number of factors that affect how long it takes to write an index. 

Length and Complexity

Let’s start with the easiest factors. A long book will usually take longer to index than a short book. A more complex book—as in complexity in structure, argument, or subject matter—will also usually take longer to index than a simple book. This is usually the different between a book intended for a general audience and a book intended for a specialist or scholarly audience. If you are an author or editor, think about the audience for your book and how it is written, as well as the page or word count. That should give you an idea for how long it will take to write the index.

Overlapping Projects and Deadlines

Some indexers prefer to work on only one project at a time. I see value in that. It is easier on the mind to not have to switch back and forth between projects. For that reason I try not to work on more than two indexes at a time, though I am currently working on three. When I edit an index, I also tend to double down and not work on anything else until I am done, in order to maintain focus and to keep the big picture of the index in my mind. 

But still, I often do work on more than one index at a time. I also usually have one or more projects waiting on my desktop for me to start. This means what while I may have three weeks to complete an index, I am not actively working on that index everyday for those three weeks. I am sorry if this bursts your conception of how I work. Please know, however, that sometime in those three weeks I will write the best index for you that I can.  

Why do I work like this, with multiple overlapping projects? The main reason is that publishing schedules often change. When I book a project, I mark those dates on my calendar and I try to space projects in a reasonable way. I also believe that my clients are being sincere about the dates they give me. But, dates change. I may learn about changes a few weeks or a month in advance, or it might just be a few days. I have decided that in order to maintain a full schedule, so that a change of dates does not leave a big hole, it is worthwhile to have overlapping projects. Having two or more weeks to complete an index, while technically more time than I usually need, does allow me to work on more than one project at a time, as well as provides a cushion when schedules slip. 

Time to Think

This, in my opinion, is the most important factor when thinking about the time it takes to write an index. If I am indexing a short book that will take, say, eight hours, I could conceivably write the index in one day. But I would never want to do that. Why? Because that kind of compressed work does not give me time to think.

What do I mean by this? Surely I am thinking all throughout the indexing process. There is reading the text and understanding what it means. There is thinking at the micro level, about what main headings and subheadings to use, and how to word them. There is thinking at the macro level, about the index structure. Then there is the final edit, which is a different sort of thinking from reading the book and creating the initial entries. In order to edit with a freshed mind, I prefer to start editing the day after I finish reading the book. So, yes, a lot of thinking goes into the index. 

By time to think, I also mean time away from the index, time that is not captured in those eight hours. These are insights that come to me when I am at the gym, washing the dishes, or driving. Sometimes if I am stuck I will simply go for a walk, hoping that the break and the change in activity will stimulate my thinking. I find that these moments away from the index, when I give my subconscious a chance to hum along while I do something else, are crucial to writing the index. In a way, the index needs time to marinate. The index will be better for spacing the work out over a few days.

Time to Rest

Related to time to think is time to rest. This is both for within a project and between projects. Reading sixty or a hundred pages per day, and created index entries, is a lot of information to process. My mind often feels like mush at the end of the day, and I need to take time to rest so that I can do it again the next day. The same is true between projects, especially as I prefer, as I mentioned, to double down on editing to keep the big picture in my mind. This can make for some long days editing. Depending on how I am feeling, I might take the next day off, or at least work fewer hours, to give my mind a chance to recover.

Rush Jobs

I mentioned rush jobs at the beginning of this post and how they fit in. When a client asks for a rush job, it usually means that I am being asked at the last minute, and the index is due in a week or less. Given that I am already often working on a couple of indexes, I usually turn down rush jobs. If you are lucky, another project has slipped and I have an unexpected hole in my schedule, but that is usually the exception. The other exception is if I really want to work on the project, for whatever reason, or if I am doing it as a favour to the client, at which point I am probably working evenings and the weekend to fit it in.

Figuring out the time it takes to write an index is complicated. Being a freelancer and working with multiple clients means a fluid schedule. There are the deadlines, and then there is how I structure my days and weeks to actually meet those deadlines. If you are an author or editor, hopefully this blog post will give you a better understanding of what you are helping to set in motion when you say, please complete this index in two weeks.  If you are an indexer, what factors are at play for you?

Article
August 31, 2016
2 comments
by Stephen

Plotter vs. Pantser? The Indexer Edition

fashion-men-vintage-colorful

If you read my previous post on genre, I’d understand if you think that this is another post inspired by the When Words Collide writing festival that I attended mid-August. This post, however, was actually inspired by Larry Sweazy’s keynote address at the joint ASI/ISC indexing conference I attended in June. Summer is a great time for conferences.

You fiction writers may already be familiar with the terms plotter and pantser. They refer to how an author approaches the process of writing a story. Do you first plot out the story before writing, or do you start with a blank page and write by the seat of your pants? Larry Sweazy, who is both an established indexer and an award-winning fiction writer, adds a twist to this concept by applying it to indexing.

Pantsing an index is to read through the text and simultaneously create and input the terms into your indexing software, without prior reading or planning. To plot would be to read through the text, either the whole text or by chapter or section, mark it up so that you have an idea of what terms you want to use, and then create the terms in your indexing software based on your notes and rereading of the text.

There are excellent indexers who fall on both sides of this divide (just as there are excellent writers who swear by both). Pantsers say that they can always revise and finalize the index later, during the editing phase. Plotters take the view that they produce a better index, and have less editing to do, if they can first understand the text.

My take? I think a lot comes down to experience, though certainly work styles and how you process information are important too. When I first started to index, I would plot out the index, chapter by chapter. Eventually I started to pants. Part of my decision to change my indexing approach was from learning from other indexers that this was an actual, viable option. Time was also a factor. I was getting more work, feeling crunched, and wondered if pantsing would speed me up. The biggest factor for me, though, at least in terms of successfully transitioning to pantsing, was experience. I had indexed enough books to have a rough template in mind that I could use when indexing blind. I was confident that making a decision, and then revisiting that decision during the editing phase, was sufficient for creating an excellent index. Plotting added an extra step, in that I would make a decision while marking up the text, and then revisit that decision twice, while inputting the entry into the index, and again while editing. I decided that extra step wasn’t necessary.

Still, I sometimes do get a particularly difficult book to index, and for those books pantsing is not as effective. For those I may decide that I do need to do some plotting. Perhaps not pre-reading the entire book, but certain key sections that illuminate the whole.

I have also increased the number of notes I make for myself while I input the terms, which I skim when I am ready to begin editing. These are to remind me of potential trouble spots that I will want to revisit during the editing phase, or these notes serve as brainstorming of alternative terms, or of similar terms I am seeing in the index and want to mull over for which is best to use. I also sometimes use mind maps to help me organize and understand what I am reading. I find visualizing the relationships between terms to be a quick and effective way to understand the structure of the text and hence the index.

For the pantser, I think plotting can still play a role in certain circumstances. The trick is to recognize those circumstances, and adapt your indexing strategy accordingly.

Now as a writer, do I plot or pants? I have to admit that I usually plot. I can often get away with pantsing short works of nonfiction, but fiction is another story. Right now I am experimenting with different plotting techniques, seeing what works best for me. I wonder if this will change too as I gain experience.

And Larry Sweazy? A pantser all the way, in both writing and indexing. That man has it figured out, or, better said, doesn’t, but knows how to finish the project regardless.