Health and science indexing tips and hints—Mary Russell (ISC conference 2014)

Mary Russell, representative from the Australian and New Zealand Society of Indexers, gave us a glimpse into her bag of tricks for indexing health and science texts.

“If you wear an editor’s hat,” she warned, “you’ll have to get comfortable sitting on your hands.” The terminology in health and science can be quite daunting, with eponyms, an idiosyncratic mix of British and American spelling, chemical names, drug names, botanical names, and so on. Medicine and science are full of alternative names, abbreviations, and precise distinctions between categories of varying complexity. You’ll have to use more cross-references and know your audience so that you can guide your readers to the terms preferred in the text.

Eponyms—diseases or body parts named after a person or place—are common in medicine and can be tricky because punctuation and possession can be lost. (Should it be “Braxton Hicks contractions” or “Braxton-Hicks contractions”?) Double-check with an authoritative source to get these right.

The use of British versus American spellings may also seem inconsistent; a book published in the U.S. may use British spelling because that’s what the profession uses. “Follow the profession,” said Russell, “not necessarily the nationality of your audience.”

Chemicals can have many alternative names—for example, vinegar can be known as a dilute solution of acetic acid, ethanoic acid, glacial acetic acid, among other names. If you have room in your index, offer your readers the most common of these as multiple access points.

Drug names “can get frightfully complicated,” said Russell. “Drug names really test your typing, because they simply do not make sense.” Drugs have a class name, a drug group, a drug name, and a trade name. It’s important to provide as many of these as possible in the index, because people may be looking up drug names and side effects in a crisis situation, and your index is the entry point.

For scientific names, classification to the level of genus and species is usually all that’s needed. Plant names are very structured, but common names and cultivars can add confusion. Although sometimes you may see zoological names inverted (species, genus), don’t do that with botanical names.

Resources

If you’re working in health and science indexing, you can turn to several different types of resources to guide you and help you understand terminology and conventions.

Dictionaries and thesauri

Specialized subject dictionaries are great resources. Sometimes they’re available as an app, which may be cheaper to buy than the print edition—or you can get a short-term subscription for your project.

For medicine, refer to the U.S. National Library of Medicine’s medical subject headings (MeSH). MeSH terms can clarify the hierarchy of terms, alert you to alternative terms, help with alternative spellings, help with politically correct terms, and clarify the use of abbreviations.

Style guides

Russell recommended the following style guides:

Name authorities and taxonomies

Many scientific areas have authorities that can be consulted online:

People

Get to know indexers who also work in science and medicine, and talk to subject experts, perhaps the work’s author or editor, to get a handle on the terminology that the audience is likely to look for.

Ten principles for creating better indexes—Margie Towery (ISC conference 2014)

Margie Towery, two-time winner of the American Society for Indexing’s award for excellence in indexing, not to mention an indexer of The Chicago Manual of Style, treated Indexing Society of Canada conference-goers to a three-hour seminar covering ten principles for creating better indexes.

An index, said Towery, should

  • help readers find specific information faster
  • have an easy-to-use structure
  • reflect the text
  • provide multiple entry points.

Indexing is both an art and a science; when we choose what to index, we rely on reason, experience, and intuition. To create better indexes,

1. Consider your audience

Who are the readers, what are their expectations, and what terminology might they look for? Towery suggests getting familiar with terminology by referring to

  • subject dictionaries
  • similar books
  • the author’s previous works
  • the author’s website
  • the press website
  • online searches on the topic

Also refer to the book’s table of contents and introduction, as well as the author’s concept list, if it’s offered. Some indexers refuse to work with an author’s concept list, a position Towery doesn’t understand. To her, it’s easier just to include those terms in the index and keep the author happy.

Add cross-references as soon as you see the opportunity—for example, if the author mentions using two terms interchangeably.

For a long project, Towery encourages immersing yourself completely in the subject, using other books, movies, music, and art.

2. Consider the metatopic

How to treat the metatopic can be controversial among indexers. Towery believes that the metatopic main heading is a keystone to the index and can be a teaching tool, as new users may naturally want to start looking in the metatopic.

A good approach may be to begin with a table of contents structure that points readers to the main headings that will let them find what they need. You may also find mind mapping helpful; there are apps that can turn a mind-map into an outline for you.

Refer to the “indexing” heading in Hans H. Wellisch’s Indexing from A to Z for an example of a metatopic done well.

3. aim for accuracy

  • Ensure the terms accurately reflect the text (more on that later) and are spelled correctly.
  • If you’re providing dates for events or years for legal cases, make sure those are accurate.
  • Disambiguate similar names—e.g., Smith, John (dentist); Smith, John (doctor).
  • Don’t allow subheadings to make adjectives of main headings.
  • Cross-references have to be accurate and consistent, in spelling, capitalization, and punctuation.
  • Triple-check accuracy of double-postings.
  • Make sure your page locators are accurate—not only that they point to the right pages but also that they are of the right type. Should 2, 3 be 2–3? Are the locators correctly formatted according to press style?

4. Aim for comprehensiveness

“In best-case scenarios,” said Towery, “every index would be comprehensive—that is, it includes all substantive information and provides multiple ways of finding the information.” In reality, however, we face space, time, and wage limitations, so the key is to achieve balance. Indexers have to consider the many ways a user might “name” and search for something.

5. Aim for conciseness

Encapsulate meaning in as few words as possible: avoid using a fifteen-letter word when a five-letter one means the same thing. Balance jargon with everyday language. (Although clarity, reflexivity, accuracy, and audience issues are equally important.)

In some cases, conciseness may trump specificity (for example, if the heading “railroad development” has only two locators and “railroads” only one, you might want to combine them under one heading.)

6. Aim for consistency

Topics of equal weight in the text should be treated similarly in the index, both in depth and specificity. Do they have similar numbers and types of locators and subheadings?

Also ensure that you have consistency in

  • cross-references (Are cross-references from similar entries—e.g., initialisms—treated the same way?)
  • formatting details (e.g., does the text use the serial comma? Where are you placing your cross-references?)
  • structure (i.e., headings should be parallel)

Finally, said Towery, don’t be afraid to be consistently inconsistent. In some situations, you have to bend rules for headings of a certain type. Just ensure that all of the headings in that category are treated the same way, and you won’t confuse your readers.

7. Aim for clarity

“The relationship between the main and the subheading must be instantly obvious,” said Towery. “Indexers shouldn’t have to figure out what’s meant.” That’s why function words like as, of, by, and so on, are so critical. “They should not be used willy-nilly,” said Towery, “but to clarify the main–subheading relationship.” Towery also cautioned that a phrase like “influence of” can be ambiguous. Be clear by specifying “influence on” or “influence by.”

Keep in mind that “words reverberate neurolinguistically differently in different people,” said Towery. Choose between terms like terrorists and revolutionaries carefully, keeping in mind that the headings should reflect the text but also help readers find what they need.

Names may benefit from glosses to clarify who they are or what their relationship is to key players in the text.

Towery also challenges us to “love the alphabet: use the alphabet not only to keep the most important word in front but also to keep logic in the subheadings whenever possible.” Fortunately, birth comes before death in the alphabet, but illness comes after death. You might need to get creative with your wording or force sort for chronology.

8. Aim for readability

Check out Susan Olason’s “Let’s get usable! Usability studies for indexes” article in The Indexer. The article notes that commas can be confusing, especially for reversals, and that table of contents–styled entries and indented formatting is more user friendly. Interestingly, Caroline Diepeveen mentioned research in the Netherlands that showed run-in subheadings are easier to read. Towery suspects that may be because run-in subheadings force indexers to be clearer and more succinct. Indented styles work better with technical texts; run-in may work better for narratives.

Towery noted the need to chunk information to accommodate the fact that we can keep only a few bits of information in short-term memory at a time.

Don’t use old indexing devices like ff. and passim., which most readers don’t understand.

Tips for readability overlap considerably with the other principles for creating better indexes:

  • Use a visible metatopic structure.
  • Include parallel structure where appropriate.
  • Be consistent in the treatment of topics.
  • Be sure the relationships between main and subheadings are unambiguous.
  • Place the most important word first in the subheadings whenever possible.
  • Avoid jargon, especially in subheadings.
  • Use the alphabet for logical progressions.
  • Clarify subheading meanings with function words.
  • Consider clumping and gathering similar subheadings.
  • Sort out long entries into more approachable chunks.
  • Avoid inversions whenever possible.

Although Olason found that indented styles were more readable, they also have their own problems. If a series of subheadings start with the same function word (e.g., on), they can create what Towery calls “gridlock” or eyeball barriers. Reword the subheading if needed to prevent this problem.

Towery also cautions that our training and work have biased our thought process. We may not be objective about what makes an index usable. If you can, show your index to someone else, a reader who can provide more unbiased feedback.

9. Aim for reflexivity

“An index should reflect the text from which it comes,” said Towery. “The index internalizes the text. But it’s not simply a regurgitation of the text in alphabetical order.” Indexers digest books to create an approachable alphabetical and structured index from the text.

Reflexivity also applies to the tone that characterizes the text. However, Towery says that an index doesn’t need to carry forward the author’s biases. Use neutral headings and subheadings to point to the text, where the author’s voice and opinions can take over.

10. Use common sense

Use natural, everyday language whenever possible. Make sure that the index makes sense to all of its possible audiences and that it’s usable by a variety of people. Again, sometimes you need to break the “rules”—with experience, you’ll get a better sense of when and how you should overrule standard practices to make a better index.

Read other indexes and critically evaluate how well they work, why, and what could be done differently. To evaluate what makes a good index, use the American Society for Indexing’s checklist for its excellence in indexing award.

***

Beyond these ten principles, Towery emphasizes the need for

  • cross-training: “Keep indexing skills fresh by learning other related skills,” she said. She finds that trying to summarize a book in a haiku helps her distill the text into its essence and achieve the precision and conciseness that an index needs.
  • napping: It’s scientifically proven to increase alertness, boost creativity and the ability to see connections, strengthen memory, clarify decision making, and improve productivity. Towery suggests reading Sara Mednick’s Take a Nap!

For an eye opener, Towery recommends reading What Is an Index?, a book Henry Wheatley wrote back in 1878 that discussed a lot of the same issues we are dealing with today.

Food for thought: the expanding universe of cookbook indexing—Gillian Watts (ISC conference 2014)

Gillian Watts, a past president of the Indexing Society of Canada, is an avid cook who’s always been drawn to cookbook indexing. Frustrated by not being able to find what she needed in a Time-Life series of cookbooks she owned called Foods of the World, Watts began cataloguing the recipes and ingredients in the series using index cards. She has since indexed about 140 cookbooks on a variety of topics, from breadmaking to gluten-free recipes to Indian cuisine.

Why index cookbooks?

There’s a big market for cookbooks today, particularly those focusing on healthy foods or cuisine from other countries, as well as those written by celebrity chefs.

Cookbooks are also comparatively easy, if you already know how to index. They’re “not a strain on intellectual faculties,” said Watts, and you can make “quick bucks, though not necessarily big bucks.”

What’s more, cookbooks are fun: every book has a different challenge, a “different world of sensory delights,” although, warned Watts, they “can lead to frequent snacking.”

Indexing approach

As with any index, know your client’s preferences before you begin, although sometimes the publisher doesn’t know what they want. In cookbooks there seems to be a preference for letter-by-letter sorting, and generally you need only one level of subhead. “Only once did I have to go to two levels,” Watts said.

Some publishers ask indexers to use special formatting, such as italics or bold, for main entries, particular techniques, or images.

“As a matter of practice,” said Watts, “I over-index. It’s easier to cut stuff out later rather than add it back in.” Watts keeps the main headings lowercase singular, to take advantage of her indexing software’s autocomplete function.

Bear in mind that the cookbook author had a reason for giving the recipes the titles they have, so try to preserve the original syntax when indexing. Also, Watts will index any ingredient in a recipe name, even if very little of it is used.

Knowing how to cook is a huge asset to a cookbook indexer; it’s important to understand the flavour profile of ingredients. An experienced cook, for example, would recognize that 1/4 cup of cilantro has more flavour than a 1/4 cup of parsley—and that it would have more influence in 2 cups of sauce than an 8-serving stew.

Cross-references are also important: often fresh and dried ingredients are used very differently.

Watts keeps a “staples list” that sets the threshold for which certain ingredients (e.g., beer, breadcrumbs, butter, carrots) make it into the index, but, she emphasized, you need to be flexible. In books for parents or for people with health problems, foods normally considered staples (e.g., flour) may become important to know about—and hence important to index.

For common cookbook terms, Watts has added a series of abbreviations to her software that autocorrect to the longer word—e.g., ch will render as chocolate. This trick saves her keystrokes and is especially useful for terms with accented characters.

The metatopic can be tricky for books that focus on a particular ingredient. For a book about quinoa that Watts worked on, where every recipe included quinoa, she indexed special forms of quinoa, such as “quinoa flour” and “quinoa flakes,” and implied that anything not listed simply used quinoa.

In cookbooks that have a health component as well as recipes, the index entries sometimes make “awkward bedfellows.” You may end up with “unappealing juxtapositions of symptoms and recipe items” and may need to get creative with wording. In one project she recommended using two separate indexes in order not to ruin the reader’s appetite.

Editing and trimming

Once you’re done data entry, edit the index, eliminating all one-entry headings. Check all cross-references.

The number of entries isn’t the same as the number of lines; some recipes have long, descriptive titles. The number of entries should be about 85 per cent of the lines available.

If space is at a premium, get rid of entries beginning with cooking techniques; people look up food, not techniques. Staple products and flavourings are also good candidates for cuts. “Sometimes you have to cut your pet entries,” said Watts, and “it’s important not to clutter the index with trivialities, even if they sound yummy.”

You may also want to group similar ingredients, such as berries, nuts, seafood, and so on, for space. “Sometimes I cheat and use the flavour profile rather than the actual food,” said Watts. For example, the entry “apple” would include applesauce, apple juice—basically anything that tastes like apple.

References

If the universe of cookbook indexing appeals to you, Watts recommends the following resources:

Watts also suggests looking at indexes in your own cookbooks. Which are useful? Which are irritating? And makes them so?

***

(Related: See my post about cookbook indexing using Microsoft Word.)

Whither the ebook index?—Erin Mallory (ISC conference 2014)

Erin Mallory is the manager of cross-media at House of Anansi Press, which has been publishing ebooks (in addition to its print books) since 2009. Mallory launched the Indexing Society of Canada’s 2014 conference with an overview of the current state of ebook indexing workflows.

Ebook formats

Ebooks come in three main formats:

  • PDFs support some multimedia and interactivity and are easy to create but have limited sales channels. The static format of PDFs makes them popular for technical or reference books but may create poor reading experience for readers using certain devices (for example, trying to read on a smartphone).
  • EPUB is the most popular ebook format and is essentially a self-contained website, using XML and CSS. Text is reflowable. EPUB is a neutral, standard format compatible with all current e-readers except the Kindle. EPUB 2, still the most commonly used version, is based on HTML 4 and CSS 2. EPUB 3 is a newer format, with many improvements in functionality, accommodating languages that read vertically or from right to left, as well as MathML.
  • MOBI is also based on XML and CSS but is proprietary to Amazon and is compatible only with Kindle devices and apps.

The main reading engines are:

  • Adobe Reader Mobile SDK, which renders ebooks on Adobe Digital Editions, Kobo, and Nook.
  • WebKit, which renders ebooks on most mobile e-readers, including the iPad, and browser-based e-readers.

Publisher’s considerations

Ebook indexes are really only useful if they are fully hyperlinked. Until recently, hand coding each hyperlink was the only way to create a fully functional ebook index, so publishers had to consider the return on investment. Not only is creating an ebook index time consuming, but proofing the index adds time to the quality-assurance process.

Further, the publisher has to consider what devices its audience is using. First-generation Kindles and Kobos don’t support hyperlinking, and not all e-readers support a “back to” function.

Because of these limitations, Anansi decided when it launched its ebook program in 2009 not to include indexes in ebooks at all. Today, the publisher has adopted a workflow that has streamlined some aspects of ebook index creation.

Recent improvements

Scripts for Adobe Creative Suite 5+ can be very useful; some auto-generate cross-references in a formatted index that are maintained when exported to EPUB. The scripts aren’t perfect, so some (about half) of the links still need to be hand coded. These scripts use styles, so if a designer hasn’t properly styled the index, they won’t work properly.

There are also scripts that convert an external index (for example, one created in Word or a program like Cindex) to create an index in InDesign that is maintained on PDF export.

The Creative Cloud version of InDesign allows for linked indexes to be exported into EPUB. Publishers can be reluctant to relinquish control of their InDesign files to an indexer, but Mallory acknowledges that if professional indexers can save the time by embedding the index, publishers may have to push aside their reluctance and find ways of working with them.

Project considerations

For each project, ask yourself the following:

  • Does your ebook need an index?
  • Does the index have to match the print book?
  • What devices will your readers use?
  • Can the index be adapted to better serve the digital reading experience?
  • Can you change your indexing workflow to simplify the ebook index creation process?
  • What kind of markers do you want to use?

Mallory points out that in an ebook, using page numbers may not make the most sense. Some indexers in the audience remarked that seeing a page range communicates important information about subject coverage. InDesign indexes can allow the range to be listed but link only the first page number.

(On Day 2 of the conference, Judy Dunlop gave an excellent summary of the workflow she used in a recent project doing embedded indexing in InDesign Creative Cloud. Post coming soon!)

Resources

Indexing Society of Canada and Editors’ Association of Canada conferences 2014—personal highlights

I’m back from four and a half days in Toronto, where I attended ISC’s and EAC’s national conferences. As in previous years, I’ll be posting summaries of some of the talks I attended—a process that, as I’ve learned, will take me several weeks. Both conferences were excellent, featuring a variety of sessions that appealed to novices as well as seasoned pros and that tackled not only the technical aspects of indexing and editing but also the business side of freelancing. Best of all was being able to see old friends and pick up conversations as if no time had passed, as well as meeting new colleagues and putting faces to names.

My days were packed: I had the privilege of introducing indexing superstar Enid Zafran at her talk about indexer–author relations at the ISC conference, and at the EAC conference I ran a two-part senior editors’ unconference: at a lunchtime session on Saturday, editors shouted out topics they wanted to discuss. I recorded the topics on a flip chart, then, with the help of sticky dots, the editors voted on their favourite ones. I ranked the topics based on votes and created our discussion agenda for our session on Sunday. It was impossible to get through all fourteen of the proposed topics, and it would have been great to have more time, but in general I thought the format worked reasonably well. It also helped that we had a great group; I’m consistently amazed by how much can happen when you just get a bunch of smart people talking to each other about what they know.

The highlight of my week, though, was the EAC banquet. Not only did we learn from Moira White that EAC has established a new award—for a person or organization that has helped advance the editing profession—in memory of our late friend Karen Virag, but we also saw Certification Steering Committee co-chairs Anne Brennan and Janice Dyer acknowledged for their enormous volunteer contributions to the association. Both won the President’s Award for Volunteer service—a well-deserved and long-overdue recognition of the hours and hours and hours of work they put into steering the certification program. Congratulations go out to all the President’s Award winners, including Lee d’Anjou Award–winning volunteer of the year, Michelle Boulton. (Just as note to the national executive, I would have loved to hear what these fantastic volunteers had done for EAC, not just their names! Please consider a giving one-sentence summary of each volunteer’s contributions at next year’s banquet.)

Congratulations, also, of course, to Claudette Upton Scholarship winner Daniel Polowin, and to University of Alberta Press’s Peter Midgley, who finally, finally received the Tom Fairley Award for Editorial Excellence he so deserves.

For me, the most exciting part of the evening was being able to present, on behalf of the Certification Steering Committee, designations of Honorary Certified Professional Editor to six pioneers of EAC’s certification program. Without them, the program simply wouldn’t exist. As someone who’s benefited tremendously from certification, both as a CPE and as a CSC member who’s had the privilege to work for the past two and half years with some of the most brilliant, funniest people I know, I want to thank and congratulate these champions, mentors, and friends for their dedication: Lee d’Anjou, Peter Moskos, Maureen Nicholson, Jonathan Paterson, Frances Peck, and Ruth Wilson. I would not be where I am today without them.

If anyone has any photos of the presentation they could send me, I’d be grateful for them. Believe me—the amount of restraint it took to keep from spilling the beans about this surprise was enormous!

Book review: Starting an Indexing Business

You’ve taken indexing courses. Read the indexing chapter of the Chicago Manual of Style and Nancy Mulvaney’s Indexing Books. Bought yourself indexing software.

Now what?

For most would-be indexers hoping to start their own freelancing business (as many of us are now aware), the actual indexing work isn’t the biggest challenge. Getting that work, not to mention managing the financial and administrative details of self-employment, is the tough part, and it’s one that gets very little attention in most indexing reference books. Starting an Indexing Business, edited by Enid Zafran and Joan Shapiro, is a rare exception, offering people who are launching—or considering—a career as a freelance indexer some insider wisdom about running their own business.

The fourth edition of Starting an Indexing Business was published in 2009, but it was recently released as an ebook. With chapters about moonlighting as an indexer while holding down a full-time job by Melanie Krueger, the business of being in business, by Pilar Wyman, and liability and exposure issues for indexers, by Enid Zafran, this book tries to answer a lot of questions that a freelancer just starting out might have. It’s a quick read, and it’s packed with tips from indexing veterans who have spent years in the trenches. Seeing the issues from different indexers’ perspectives is helpful, and the diversity of contributors shows that, despite having similar traits that make us good at what we do, different indexers take different approaches to running their business. Particularly interesting is the debate about whether to invest in disability insurance, with Wyman advocating for it and Zafran saying she didn’t see the need.

Zafran’s chapter about liability has a lot to offer, spurring the reader to think about how best to protect their business and to assert their copyright to make sure they get paid. A sample letter of agreement for indexing services also appears as an appendix to the book, and it serves as a helpful tool for freelancers to communicate clearly with a new client and start off their working relationship on the right foot.

Although the book has plenty of solid advice for new indexers, much of it will be old hat to people who have had a few projects under their belt. Being five years old, it also needs an update. I suspect that cold calling and mailing out brochures to prospective clients, as marketing strategies recommended by a few of the contributors, have largely given way to email enquiries and websites. I would also hope that a fax machine is no longer a must-have in the home office. Workflow and file transfer technologies have also evolved dramatically since the book’s publication, and ebooks and self-publishing have exploded. Further, the book is geared toward a primarily American audience, with references to health insurance and U.S. taxes that wouldn’t apply to Canadian indexers.

New freelancers may find Starting an Indexing Business helpful, although I wouldn’t call it a must-read. For those with a few years’ experience already, there isn’t much in this book that you won’t already know. And beyond the sample letter, I don’t see much in this book that you would refer to time and again, so I’d be inclined to borrow it from the library, if you can. If you do want to add this title to your collection, I’d suggest waiting for an updated edition, so that the advice better reflects current practices and technology.

Back to school: A self-indulgent personal post

This week I got an official letter of acceptance to the PhD program in SFU’s Faculty of Health Sciences, where I’ll be studying knowledge translation. In particular, I’ll be looking at ways to apply plain language principles to mental health research to make it more accessible to patients, practitioners, advocacy groups, and policy makers. I’m thrilled by the prospect of applying my editorial skills and clear communication knowledge to increase health and scientific literacy.

Although I’m heading back to school, in no way will I be leaving publishing; I adore my career, and my plan (although plans may change, of course) is to come right back once I’ve completed the degree. In the meantime, I’ll be dialing down the amount of publishing work I take on to a small handful of projects a year so that I can focus on my research.

I’ll also be drastically cutting back on my volunteer commitments with organizations such as the Editors’ Association of Canada. Over the past two years I’ve been a member of EAC’s Certification Steering Committee, which oversees the national program that certifies editors who have demonstrated excellence in proofreading, copy editing, stylistic editing, or structural editing. This committee is made up of some of the smartest, funniest, and most dedicated people I know, and working with them on projects to promote and strengthen the certification program has been a huge privilege. Leaving this collegial, optimistic, and productive group in August will be bittersweet.

At the branch level, I’ve worked with Frances Peck for the past two seasons (and with Micheline Brodeur last year) on the EAC-BC Programs Committee to set topics and invite speakers for our monthly meetings. We managed to put together an impressive lineup of speakers on fascinating subjects from forensic linguistics and cartography to subcontracting and the evolving role of libraries. Our ideas have spilled over into next season, and whoever takes over on the committee next year will be able to hit the ground running.

I can’t emphasize enough that my experiences on these committees—not to mention the professional relationships and friendships I’ve forged—have been tremendous for professional development, and I urge anyone considering volunteering for EAC to seize the opportunity. I will still be an active EAC member, and I am still happy to volunteer for small jobs here and there or for one-off events, but I’ll no longer have the time for ongoing committee work. If there’s still demand after this year’s PubPro unconference, a peer-driven professional development event for publication production professionals, I would be more than willing to run it again. And I still hope to attend EAC meetings and conferences and write up what I’ve gleaned from the sessions on my blog (although once I’m off the Programs Committee, I may allow myself to miss the odd meeting).

Speaking of my blog, my intention is still to post regularly on editorial, indexing, publishing, and plain language topics, but you might start seeing a bit more of a knowledge translation, health literacy, or mental health bent to my writing. Realistically, though, I won’t have time to do any more book reviews once school starts up. I’d love to keep crapping out my dumb little cartoons, but I might not be able to keep up with my monthly schedule.

Finally, I’d love to keep teaching in SFU’s Writing and Communications program. Changes are afoot in how those courses are being offered, though, so I’m not sure if I’ll still have a role to play. If it turns out that I will, I’ll be sure to post news about upcoming courses.

I’d like to thank all of my friends, colleagues, and mentors who have given me encouragement and advice as I’ve plotted this next step, which I have wanted to take for a long time. I feel incredibly lucky to be surrounded by so many amazing, supportive people.

Cookbook indexing in Microsoft Word

I’ve just wrapped up a cookbook index, and while I was putting it together I found myself referring to notes I’d made a while ago for a friend who wanted to do cookbook indexing but didn’t want to invest in indexing software. When I worked in house, I’d prepared several cookbook indexes using only Microsoft Word and figured out, through trial and error, a reasonably efficient system. I figured I’d share my notes here for anyone interested. If you have a client with a specific house style, you might have to adjust the approach a bit.

What follows isn’t a guide for writing a good cookbook index. For that kind of information, I’d suggest “A Piece of Cake? Cookbook Indexing–Basic Guidelines and Resources” by Cynthia D. Bertelsen and Recipes into Type by Joan Whitman and Dolores Simon (relevant excerpt about indexes here). The notes below are just a step-by-step system you can follow to take advantage of Word’s functions when creating a cookbook index even though it ordinarily isn’t a great program to use for indexing.

***

Specialized indexing software is invaluable if you’re indexing most nonfiction titles, but a cookbook index has a straightforward structure that Word can easily accommodate.  The key is to keep the following in mind:

  • As tempting as it might be to sort as you go along—as indexing software allows you to do—don’t. You’ll have a much easier time if you alphabetize near the end.
  • The pages may not be final when you start data entry. Be prepared to adjust your locators if they move around.
  • Microsoft Word does not sort letter by letter; you may have to go through your index at the end and tweak the ordering of the entries.

1. Data entry

a) Start with the first recipe. Key in the recipe title verbatim (or copy and paste from a PDF), along with the page range. If the recipe has a photo, add that page number in italics.

Type the title in as it appears if it starts with a descriptor:

Deen’s Buttered Bacon Rolls, 108–9, 109

If the title starts with a main ingredient, state the main ingredient category first, followed by a comma. Keep everything on the same line for now.

chickpeas, Chickpea, Green Onion and Quinoa Salad, 54–55

b) Copy the recipe title and locator (the highlighted part):

chickpeas, Chickpea, Green Onion and Quinoa Salad, 54–55

c) Paste the recipe title and locator after keying in all other main ingredients and broad categories (like “beef,” “fish,” “salads,” “sauces,” etc.) on separate lines:

green onions, Chickpea, Green Onion and Quinoa Salad, 54–55
quinoa, Chickpea, Green Onion and Quinoa Salad, 54–55
salads, Chickpea, Green Onion, and Quinoa Salad, 54–55

d) If the recipe title starts with more than one descriptor, add entries for all possible inversions that readers might look up. Add a special mark like an asterisk, which indicates that this entry could be considered for cutting if space is tight:

Buttered Bacon Rolls, Deen’s, 108–9, 109*

e) Key in any subrecipe titles and page ranges, under an appropriate category if necessary. If the subrecipe title is generic, you may also have to add the full recipe title for clarity. Append a double-asterisk, indicating that this is a subrecipe:

dressing, Special Dressing, for Chickpea, Green Onion and Quinoa Salad, 54–55**

f) Index special ingredients or techniques only if they are defined/discussed in detail. If the book contains many definitions, you may want to indicate these by setting the locators in boldface. Again, append a double-asterisk:

cold smoking, 56, 56–59**

g) Repeat steps 1a to 1e for all recipes in the cookbook, proceeding in order. Apply 1f as needed, as you go along.

h) Add any logical cross-references.

beef. See also veal

i) Run a spell check on the index.

j) Save this file as index_v1.

k) Once the cookbook’s pages have been finalized, confirm locators, making any necessary adjustments. Save index_v1.

2. Structuring

a) Alphabetize: select all, go to Table → Sort… → Sort by paragraphs, ascending.

b) You’ll have lists like these:

beef, Chinese Five-Spice Beef Short Ribs
beef, Curried Beef and Vegetable Skewers
beef, Grilled Garam Masala Burgers
beef, Wine-Marinated Prime Rib Roast
beef. See also veal

Move the general category and any cross-references to the top, then replace the category in all other entries with a tab indent by selecting that segment of text and using Word’s Find and Replace function.

beef. See also veal
     Chinese Five-Spice Beef Short Ribs
     Curried Beef and Vegetable Skewers
     Grilled Garam Masala Burgers
     Wine-Marinated Prime Rib Roast

Go through the index and repeat this step for all categories that have two or more subentries.

c) For main ingredient categories that have only one recipe, just invert the recipe name to showcase that ingredient first:

quinoa, Chickpea, Green Onion and Quinoa Salad, 54–55

becomes

Quinoa, Green Onion and Chickpea Salad, 54–55

d) Add line spaces after the end of each section that begins with the same letter. Add group headings “A,” “B,” etc. before each section only if there is enough room.

e) Add a headnote mentioning that photos are referenced in italics and definitions in boldface.

f) Save as index_v2.

3. Cutting to spec and finalizing the index

a) Save as index_v3.

b) If the index is too long, consider first eliminating whole categories that readers are unlikely to look up or that are redundant. For example, if the book itself has a section devoted to desserts, having a dessert category in the index is not needed.

c) If the index is still too long, consider combining some categories and adding cross-references. For example, if you have divided “fish” and “shellfish,” consider combining them under “seafood” and adding cross-references to the new category under both “fish” and “shellfish.” Doing so will allow you to cut duplicates of recipes that include both fish and shellfish.

d) If the index is still too long, consider cutting all subrecipes and special ingredients/techniques, which you’d marked off earlier with double-asterisks.

(If the index needs a lot of cutting and you’re confident you will need to cut all entries marked off with double-asterisks, you can use Word’s Replace function to get rid of all of them at once. If you’re comfortable with wildcard searches, place your cursor at the top of the document, then, in the Replace dialogue box, put [!^13]@\*\*^13 in the “Find what” field and nothing in the “Replace with” field. Make sure “Use wildcards” is checked. Clicking “Replace all” should get rid of any lines that end with a double-asterisk.)

e) If the index is still too long, evaluate for cutting or abridging only those entries that have an asterisk. (Never cut out or modify an entry that matches the recipe title exactly.) If it makes sense to cut the whole entry, do it. You could also cut part of the title if it refers to sauces and garnishes that aren’t a fundamental part of the dish.

f) Delete all the asterisks. (Using the Replace function, put * in the “Find what” field and nothing in the “Replace with” field.)

g) Edit the index as outlined in Chicago 16.133, in particular double-checking alphabetization, then save index_v3 and submit it.

Versioning system

  • Index_v1: This version makes it easier to update locators if pages—especially if spreads or larger groups of pages—are moved around.
  • Index_v2: Go back to this version if the publisher decides to add pages to allow more room for the index.
  • Index_v3: Your final submitted index.

Recent innovations in indexing software

ISC conference attendees were treated to a tour of four of the most popular indexing programs.

TExtract

Harry Bego, developer of TExtract, came from the Netherlands to give us a presentation and demo of his “semi-automatic” indexing software. Having been a researcher in natural language processing at Tilburg University, Bego incorporated linguistic and statistical analysis algorithms into TExtract; these identify important terms and compile them all into an initial draft index, taking out a lot of grunt work of data entry. Bego was quick to emphasize that the user is always completely in control. Although TExtract puts together the initial index automatically, the indexer can review each entry and choose whether to accept or discard it. For each entry, the program shows its frequency and “significance score.” Users can adjust the significance threshold of a text to control what kinds of terms are picked out in the initial index, and they can add filters to determine which terms the program should exclude or include.

TExtract also has a “document replacement” feature that allows the indexer to compare a new version of the text with an old one and update the index accordingly. The entries are linked to the text—a feature that supports in-context navigation and editing.

Although TExtract is in itself a complete indexing program, Bego told us that TExtract outputs can then be fed into any of the other major indexing programs (such as the ones below), if an indexer is more comfortable editing on different software.

SKY Index

SKY Index’s developer, Kamm Schreiner, was unable to join us in person, but he sent a video that showed off some of this program’s features.

SKY has a spreadsheet-like interface and allows you to do data entry on the right-hand pane while a preview pane on the left shows you the index as it’s being built. Schreiner has built in several functions that in other programs might require a macro: SKY Index can easily consume subheadings, swap acronyms, and so on. The program also flags common errors for the indexer (e.g., adding a locator to an entry that already has a See cross-reference).

SKY Index has an edit view, which allows for quick and efficient editing. You can open up a browse pane that allows you to see and compare two separate sections of the index side by side. The browse pane can be used in data entry view as well, and the program bookmarks where you left off before opening the browse pane.

More information and videos are available on the SKY Software website.

CINDEX

Frances Lennie, a freelance indexer since 1977, established Indexing Research in 1986 to develop CINDEX, which is available on both Windows and Mac. The company also features a publishers’ edition of CINDEX, available only on Windows, which accommodates multi-user production environments, such as legal publishing houses or government publishing houses.

CINDEX uses an index card metaphor and allows up to 15 levels of subheadings. The indexer enters data in the record entry window while the index builds in the background. All records are date and time stamped.

CINDEX is fully Unicode compliant and supports different sorting conventions and spell checking in a variety of languages. Lennie gave us a demonstration of an index created in Hebrew, which reads right to left and so has entries in inverted order (locator on the left, entry on the right).

Lennie showed how CINDEX supports searching specific entries based on a character string, page range, or style attributes. Editing is also easy: CINDEX offers both global and individual editing options, and it also uses a variety of techniques to check the integrity of the index. Finally, the index may be exported in many different formats and file types.

Macrex

Gale Rhoades, the North American publisher of Macrex, gave us a demo of Macrex’s just-released ninth version. Macrex is a Windows-based program that was first developed in 1981. It boasts a seemingly overwhelming list of features, but the secret to using it, explained Rhoades, is to focus only on your current project and not worry about what may seem like overhead. She has worked with many indexers over the years, she explained, and she has always managed to help them configure Macrex to do what they need it to do.

Macrex is big about giving the user control. Entries are written directly in the index; different components (e.g., cross-references, locators, etc.) are colour coded, and you can change the colour palette to suit your tastes. Further, you can create a folder with a particular client’s specifications (e.g., sort order, layout, cross-reference format, output format, etc.) and use it essentially as a template for all of the work you do for that client.

Rhoades emphasized the client support that you get with Macrex. She hosts a weekly chat session for North American Macrex users to talk about indexing and software issues; she can also connect directly to your computer to troubleshoot Macrex problems.