Search (27 results, page 1 of 2)

0.12902068 = product of:
  0.3225517 = sum of:
    0.21151231 = weight(_text_:books in 13) [ClassicSimilarity], result of:
      0.21151231 = score(doc=13,freq=2.0), product of:
        0.24756333 = queryWeight, product of:
          4.8330836 = idf(docFreq=956, maxDocs=44218)
          0.051222645 = queryNorm
        0.85437655 = fieldWeight in 13, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.8330836 = idf(docFreq=956, maxDocs=44218)
          0.125 = fieldNorm(doc=13)
    0.111039385 = weight(_text_:22 in 13) [ClassicSimilarity], result of:
      0.111039385 = score(doc=13,freq=2.0), product of:
        0.17937298 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.051222645 = queryNorm
        0.61904186 = fieldWeight in 13, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.125 = fieldNorm(doc=13)
  0.4 = coord(2/5)

Source

Indexer. 22(2001) no.3, S.14-18

0.03172685 = product of:
  0.15863423 = sum of:
    0.15863423 = weight(_text_:books in 941) [ClassicSimilarity], result of:
      0.15863423 = score(doc=941,freq=2.0), product of:
        0.24756333 = queryWeight, product of:
          4.8330836 = idf(docFreq=956, maxDocs=44218)
          0.051222645 = queryNorm
        0.6407824 = fieldWeight in 941, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.8330836 = idf(docFreq=956, maxDocs=44218)
          0.09375 = fieldNorm(doc=941)
  0.2 = coord(1/5)

Abstract

On the difference between indexing of books and of journals

0.022207877 = product of:
  0.111039385 = sum of:
    0.111039385 = weight(_text_:22 in 263) [ClassicSimilarity], result of:
      0.111039385 = score(doc=263,freq=2.0), product of:
        0.17937298 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.051222645 = queryNorm
        0.61904186 = fieldWeight in 263, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.125 = fieldNorm(doc=263)
  0.2 = coord(1/5)

Source

Indexer. 22(2000) no.1, S.25-26

0.022207877 = product of:
  0.111039385 = sum of:
    0.111039385 = weight(_text_:22 in 487) [ClassicSimilarity], result of:
      0.111039385 = score(doc=487,freq=2.0), product of:
        0.17937298 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.051222645 = queryNorm
        0.61904186 = fieldWeight in 487, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.125 = fieldNorm(doc=487)
  0.2 = coord(1/5)

Source

Indexer. 22(2000) no.1, S.14-20

0.022207877 = product of:
  0.111039385 = sum of:
    0.111039385 = weight(_text_:22 in 4160) [ClassicSimilarity], result of:
      0.111039385 = score(doc=4160,freq=2.0), product of:
        0.17937298 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.051222645 = queryNorm
        0.61904186 = fieldWeight in 4160, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.125 = fieldNorm(doc=4160)
  0.2 = coord(1/5)

Source

Indexer. 22(2001) no.3, S.135-141

0.019431893 = product of:
  0.09715946 = sum of:
    0.09715946 = weight(_text_:22 in 6443) [ClassicSimilarity], result of:
      0.09715946 = score(doc=6443,freq=2.0), product of:
        0.17937298 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.051222645 = queryNorm
        0.5416616 = fieldWeight in 6443, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.109375 = fieldNorm(doc=6443)
  0.2 = coord(1/5)

Source

Indexer. 22(2001) no.3, S.123-127

0.019431893 = product of:
  0.09715946 = sum of:
    0.09715946 = weight(_text_:22 in 12) [ClassicSimilarity], result of:
      0.09715946 = score(doc=12,freq=2.0), product of:
        0.17937298 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.051222645 = queryNorm
        0.5416616 = fieldWeight in 12, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.109375 = fieldNorm(doc=12)
  0.2 = coord(1/5)

Source

Indexer. 22(2001) no.3, S.119-122

0.019431893 = product of:
  0.09715946 = sum of:
    0.09715946 = weight(_text_:22 in 486) [ClassicSimilarity], result of:
      0.09715946 = score(doc=486,freq=2.0), product of:
        0.17937298 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.051222645 = queryNorm
        0.5416616 = fieldWeight in 486, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.109375 = fieldNorm(doc=486)
  0.2 = coord(1/5)

Source

Indexer. 22(2000) no.1, S.2-13

0.019431893 = product of:
  0.09715946 = sum of:
    0.09715946 = weight(_text_:22 in 488) [ClassicSimilarity], result of:
      0.09715946 = score(doc=488,freq=2.0), product of:
        0.17937298 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.051222645 = queryNorm
        0.5416616 = fieldWeight in 488, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.109375 = fieldNorm(doc=488)
  0.2 = coord(1/5)

Source

Indexer. 22(2000) no.1, S.27-28

0.019431893 = product of:
  0.09715946 = sum of:
    0.09715946 = weight(_text_:22 in 489) [ClassicSimilarity], result of:
      0.09715946 = score(doc=489,freq=2.0), product of:
        0.17937298 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.051222645 = queryNorm
        0.5416616 = fieldWeight in 489, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.109375 = fieldNorm(doc=489)
  0.2 = coord(1/5)

Source

Indexer. 22(2000) no.1, S.23-24

0.019431893 = product of:
  0.09715946 = sum of:
    0.09715946 = weight(_text_:22 in 4162) [ClassicSimilarity], result of:
      0.09715946 = score(doc=4162,freq=2.0), product of:
        0.17937298 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.051222645 = queryNorm
        0.5416616 = fieldWeight in 4162, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.109375 = fieldNorm(doc=4162)
  0.2 = coord(1/5)

Source

Indexer. 22(2001) no.4, S.191-194

0.019431893 = product of:
  0.09715946 = sum of:
    0.09715946 = weight(_text_:22 in 4172) [ClassicSimilarity], result of:
      0.09715946 = score(doc=4172,freq=2.0), product of:
        0.17937298 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.051222645 = queryNorm
        0.5416616 = fieldWeight in 4172, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.109375 = fieldNorm(doc=4172)
  0.2 = coord(1/5)

Source

Indexer. 22(2001) no.4, S.178-180

0.019431893 = product of:
  0.09715946 = sum of:
    0.09715946 = weight(_text_:22 in 4180) [ClassicSimilarity], result of:
      0.09715946 = score(doc=4180,freq=2.0), product of:
        0.17937298 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.051222645 = queryNorm
        0.5416616 = fieldWeight in 4180, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.109375 = fieldNorm(doc=4180)
  0.2 = coord(1/5)

Date

17.10.2005 13:54:22

0.016190538 = product of:
  0.08095269 = sum of:
    0.08095269 = weight(_text_:books in 5040) [ClassicSimilarity], result of:
      0.08095269 = score(doc=5040,freq=12.0), product of:
        0.24756333 = queryWeight, product of:
          4.8330836 = idf(docFreq=956, maxDocs=44218)
          0.051222645 = queryNorm
        0.3269979 = fieldWeight in 5040, product of:
          3.4641016 = tf(freq=12.0), with freq of:
            12.0 = termFreq=12.0
          4.8330836 = idf(docFreq=956, maxDocs=44218)
          0.01953125 = fieldNorm(doc=5040)
  0.2 = coord(1/5)

Footnote

Rez. in: KO 32(2005) no.3, S.135-136 (N. Bridge): "Authors of books have usually lived with their material for years before they embark on the arduous business of writing the book, followed by the revisiting during the editing and publishing processes. The indexers of their books usually have between two and four weeks to absorb the subject of the book. Even with a prior knowledge of the discipline, they are faced with the author's particular "take" on the subject and writing style, including any one of a number of ways of presenting the material. This is multiplied in complexity when the book is a multiauthored work, a collection of essays and papers, comprising several authors' differing views and individual styles. Ideally, the indexer is an expert in the subject matter of the book, perfectly matched to the book; in practice, this almost never happens. Indexers aim at producing an index that is truly reflective of the individual book and its author, a goal that often seems overwhelming when the pile of page proofs arrives with the courier, or electronically through a PDF file, hundreds of pages of closely argued text. As well as the time limit, there can be other restrictions, most commonly having to make the index fit into the number of pages decreed by the publisher, with difficult, even agonizing decisions lying ahead. Consequently, indexers can fall into a number of different traps: getting lost in a welter of detailed overindexing; or, mindful of time and space limits, indexing too broadly and simplistically, bouncing from text heading to heading, topic sentence to topic sentence. Most indexers of academic books I know, including myself, tend to fall into the first category at least with their first few indexes. Especially when the content is personally fascinating, it's easy to lose a rational, analytical approach to the content of a book, and wrest this back only with difficulty during the editing stage with the deadline looming. Do Mi Stauber's title, Facing the Text, is, thus, provocative, because that's what all indexers inevitably have to do. She knows the process: for example, at the start, the "gap between you and those pages that for a moment seems very wide" (p. 1). This sympathetic, personal tone pervades the book: the emphasis is on the personal experiences, feelings, and perceptions of indexers when confronted by the various situations thrown up by indexing; it's "I" and "you" throughout. The chapter subheadings often echo this: my tendency to lose sight of main topics is explained and diagnosed in "Lost Among the Trees" (p. 63-64). The section "Being Stuck" (p. 324-26), describes a number of reasons for this common malady, along with remedies for each, including the "Hammock Method" (p. 46). Stauber has been presenting workshops with the title "Facing the Text" since 1997, and her book reflects a friendly, listening engagement with her audience.
Facing the Text falls into what I call the third wave of books about back-of-the-book indexing. Each of these waves overlaps, but generally the first consists of the general manuals on indexing books (and other media): Booth, Knight, Mulvany, and Wellisch, along with chapter 18 of the Chicago Manual of Style, 15th ed. These set out the fundamental principles, conventions, or rules of indexing in a mostly impersonal, dispassionate tone. The second wave carried manuals on indexing in specific disciplines and genres: biography, medicine, law, psychology, history, genealogy, etc. The third wave, exemplified by Stauber's Facing the Text and Smith and Kells' Inside Indexing, delves into what goes through the mind of the indexer "facing the text" and putting together an index based on it. The tone is personal and subjective, the authors taking the reader through their own perceptions of the stages of indexing a book, the inevitable problems and subsequent decision making, expressed through their own reactions and reasoning. Facing the Text is not a manual where the newcomer to indexing can find immediate answers to specific problems: the first and second waves of books on indexing are designed to provide those. It's a book for the professional indexer or academic author indexing more than one book; its effect is to hone skills and refine working habits, to increase efficiency and effectiveness, to create indexes that make faithful, logical sense of the text. Newcomers, including first-time academic-author indexers, should begin with the last chapter "Inside an Indexer's Brain," then the second-to-last chapter, "Process"; in fact, I would suggest that any reader begin with "Inside an Indexer's Brain," for its introduction to the terminology and the overall look at indexing, from the first to the last page of the text to be indexed. As one would expect, the index to Facing the Text is comprehensive; in fact, exhaustive, and admirably detailed. The personable, conversational tone continues here, with entries such as "Subheadings/creating as you go" and "Notes to yourself." Of course, "Being stuck" is there as is, and also helpfully doubleposted as "Stuckness strategies." Finally, and on a relatively small note, this is a nicely designed book. Not only is it laid out for looks, it's laid out for use. The type is a friendly size, and the complex structure of headings, subheadings, and sub-subheadings is rendered immediately intelligible by the well-chosen fonts. My only criticism concerns the tightness of the binding; manuals should lie flat, without having to be anchored on each side with paperweights."

0.015863424 = product of:
  0.079317115 = sum of:
    0.079317115 = weight(_text_:books in 214) [ClassicSimilarity], result of:
      0.079317115 = score(doc=214,freq=2.0), product of:
        0.24756333 = queryWeight, product of:
          4.8330836 = idf(docFreq=956, maxDocs=44218)
          0.051222645 = queryNorm
        0.3203912 = fieldWeight in 214, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.8330836 = idf(docFreq=956, maxDocs=44218)
          0.046875 = fieldNorm(doc=214)
  0.2 = coord(1/5)

Abstract

The explosion in personal computing and in computer technology has brought a wealth of opportunities for indexers. Annually, traditional publishers produce numerous books on computer topics, while software and hardware companies constantly issue new products with manuals that require indexes. Indexers can find work with these high-technology publishers or can subcontract with technical documentation firms or with freelance technical writers. The range of audiences for computer-related documents is wide and varied, as is the range of topics. These documents are not limited to end-user software manuals, but include programming, Internet, and networking topics among others. Hardware companies, in addition to computer manufacturers, are also a good potential source of clients. Many hardware products have a sizeable software component that requires its own set of indexed manuals. There are advantages and disadvantages to working with high-technology companies (and their contractors) vs. working with traditional publishers. It is simply a matter of personal taste which type of client you prefer. I have truly enjoyed working with both.

0.015863424 = product of:
  0.079317115 = sum of:
    0.079317115 = weight(_text_:books in 745) [ClassicSimilarity], result of:
      0.079317115 = score(doc=745,freq=2.0), product of:
        0.24756333 = queryWeight, product of:
          4.8330836 = idf(docFreq=956, maxDocs=44218)
          0.051222645 = queryNorm
        0.3203912 = fieldWeight in 745, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.8330836 = idf(docFreq=956, maxDocs=44218)
          0.046875 = fieldNorm(doc=745)
  0.2 = coord(1/5)

0.015703341 = product of:
  0.0785167 = sum of:
    0.0785167 = weight(_text_:22 in 882) [ClassicSimilarity], result of:
      0.0785167 = score(doc=882,freq=4.0), product of:
        0.17937298 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.051222645 = queryNorm
        0.4377287 = fieldWeight in 882, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.0625 = fieldNorm(doc=882)
  0.2 = coord(1/5)

Footnote

Vgl.: http://www.theindexer.org/files/22-2-olason.pdf.

Source

Indexer. 22(2000) no.2, S.91-95

0.014956179 = product of:
  0.0747809 = sum of:
    0.0747809 = weight(_text_:books in 217) [ClassicSimilarity], result of:
      0.0747809 = score(doc=217,freq=4.0), product of:
        0.24756333 = queryWeight, product of:
          4.8330836 = idf(docFreq=956, maxDocs=44218)
          0.051222645 = queryNorm
        0.30206773 = fieldWeight in 217, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          4.8330836 = idf(docFreq=956, maxDocs=44218)
          0.03125 = fieldNorm(doc=217)
  0.2 = coord(1/5)

Abstract

Here's the scenario: Your favorite client calls to tell you they are changing their processes. "We've decided to go completely electronic and embed the indexing in the files. Can you do that?" It looks like your life and the way you do your work is going to change if you say yes. But before you do, make sure you know enough about the new process to know whether you want to take on the project. Embedded indexing brings a whole new level of complexity to the indexing process. You will need to incorporate new software technologies and special editing/index-compiling skills with the traditional thought and analysis that has always gone into the indexing process. What do we mean when we say you can embed indexing into files? The simplest answer is the one that Nancy Mulvany gives in Indexing Books: Embedded indexing software is generally a feature found in word processing or page design software such as WordPerfect or Ventura Publisher. Embedded indexing software allows the indexer to insert index entries (or tags for entries) directly into the document's text files. In other words, instead of writing an index in CINDEX, Macrex, or SkyIndex, you put the index entries directly into the same files that are used to create the book. Many companies use Microsoft Word, PageMaker, FrameMaker, or Quark to create their manuals and books, editing, layout, and printing directly from the program files. Pasting up pages manually and creating galleys are not part of electronic publishing. Everything lives in files, from the time it is written until the time it goes to the publisher's printing plates. When you embed indexing codes into these files, the publisher has no worry about what page numbers go into the index until the very end. If needed, files can go through layout, content and copy-edit changes even after indexing is completed. This approach also permits indexing and text to be re-used in the next edition or even converted into hyperactive links!

0.014956179 = product of:
  0.0747809 = sum of:
    0.0747809 = weight(_text_:books in 72) [ClassicSimilarity], result of:
      0.0747809 = score(doc=72,freq=4.0), product of:
        0.24756333 = queryWeight, product of:
          4.8330836 = idf(docFreq=956, maxDocs=44218)
          0.051222645 = queryNorm
        0.30206773 = fieldWeight in 72, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          4.8330836 = idf(docFreq=956, maxDocs=44218)
          0.03125 = fieldNorm(doc=72)
  0.2 = coord(1/5)

Footnote

Rez. in: KO 32(2005) no.4, S.160-162 (C. Jacobs): "This update maintains the place of Mulvany's 1994 work as an essential indexing resource. Addressed to indexers, authors and editors, it provides a thorough introduction to the field of back-of-the-book indexing, while providing context and direction for dealing with some of the more arcane problems that can arise. Book indexers must analyze text rapidly and organize the "map" that they are creating in a manner that fits the anticipated cognitive patterns of potential readers, is internally consistent and corresponds to standards. Intuition, high-level analytical skills, pattern-recognition abilities, commonsense and the ability to communicate the big picture as well as the details in few words are signs of a gifted indexer. Thus, it makes sense that Nancy Mulvany's conviction that indexers are born, not made, underlies the purpose and structure of Indexing Books. Consequently, this is a book that focuses on best practices and acceptable options, not on specializations. While it provides contexts and procedures for the practice of indexing so that individuals new to the field may use it as a textbook, it goes beyond this to suggest avenues and resources for decisionmaking. Established professionals as well as students will therefore find it useful. Mulvany speaks directly to the readers, engaging them with the material; her philosophy comes through clearly. Mulvany refers extensively to current authorities throughout, linking practice to ISO standards, the British standard, NISO guidelines, AACR2R, the Chicago Manual of Style, as well as to more specialized resources. Citations have been meticulously updated and references to the latest research and discussions included. ..."

0.013879924 = product of:
  0.06939962 = sum of:
    0.06939962 = weight(_text_:22 in 113) [ClassicSimilarity], result of:
      0.06939962 = score(doc=113,freq=2.0), product of:
        0.17937298 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.051222645 = queryNorm
        0.38690117 = fieldWeight in 113, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.078125 = fieldNorm(doc=113)
  0.2 = coord(1/5)

Source

Indexer. 22(2000) no.2, S.81-83