Search (35 results, page 2 of 2)

0.008890929 = product of:
  0.026672786 = sum of:
    0.026672786 = weight(_text_:on in 5158) [ClassicSimilarity], result of:
      0.026672786 = score(doc=5158,freq=8.0), product of:
        0.109763056 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.04990557 = queryNorm
        0.24300331 = fieldWeight in 5158, product of:
          2.828427 = tf(freq=8.0), with freq of:
            8.0 = termFreq=8.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.0390625 = fieldNorm(doc=5158)
  0.33333334 = coord(1/3)

Abstract

Usability of Web sites has become an increasingly important area of research as Web sites proliferate and problems with use are noted. Generally, aspects of Web sites that have been investigated focus on such areas as overall design and navigation. The exploratory study reported on here investigates one specific component of a Web site-the index structure. By employing index usability metrics developed by Liddy and Jörgensen (1993; Jörgensen & Liddy, 1996) and modified to accommodate a hypertext environment, the study compared the effectiveness and efficiency of 20 subjects who used one existing index (the A-Z index on the FedStats Web site at http://www.fedstats.gov) and three experimental variants to complete five researcher-generated tasks. User satisfaction with the indexes was also evaluated. The findings indicate that a hypertext index with multiple access points for each concept, all linked to the same resource, led to greater effectiveness and efficiency of retrieval on almost all measures. Satisfaction measures were more variable. The study offers insight into potential improvements in the design of Web-based indexes and provides preliminary assessment of the validity of the measures employed

0.007888435 = product of:
  0.023665305 = sum of:
    0.023665305 = product of:
      0.04733061 = sum of:
        0.04733061 = weight(_text_:22 in 749) [ClassicSimilarity], result of:
          0.04733061 = score(doc=749,freq=2.0), product of:
            0.1747608 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04990557 = queryNorm
            0.2708308 = fieldWeight in 749, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0546875 = fieldNorm(doc=749)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

8.12.2007 19:25:22

0.0076997704 = product of:
  0.02309931 = sum of:
    0.02309931 = weight(_text_:on in 225) [ClassicSimilarity], result of:
      0.02309931 = score(doc=225,freq=6.0), product of:
        0.109763056 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.04990557 = queryNorm
        0.21044704 = fieldWeight in 225, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.0390625 = fieldNorm(doc=225)
  0.33333334 = coord(1/3)

Abstract

Do indexers really need Web sites? No, they do not. Indexers do not need computers either. Indexes can be done on cards; networking can be done at conferences; and marketing can be done with cold calls. But, just as email has become indispensable to communication, and computers have become essential to indexing, so Web sites have become more and more necessary for all types of businesses, particularly small companies with small advertising budgets, like indexing businesses. The amount of business being conducted on the Web is increasing exponentially. Publishers, packagers, and other potential clients are beginning to search the Web for indexers. Why not participate in e-commerce, the newest way of doing business? A good Web site not only helps you obtain work, it increases your professional reputation and helps you influence the future of indexing. You can use your site as an online resume, to display a list of all the books you have indexed in the past year, to provide examples of your work, and to network with others. You can use it to express your philosophy of indexing, to teach others about indexing, and to make your voice heard on issues affecting the indexing profession. Not all indexers need Web sites, but active, involved, and far-sighted indexers, like you, do!

0.0075442037 = product of:
  0.02263261 = sum of:
    0.02263261 = weight(_text_:on in 218) [ClassicSimilarity], result of:
      0.02263261 = score(doc=218,freq=4.0), product of:
        0.109763056 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.04990557 = queryNorm
        0.20619515 = fieldWeight in 218, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.046875 = fieldNorm(doc=218)
  0.33333334 = coord(1/3)

Abstract

My goal in this short article is to bring you up to speed on Web indexing. I assume you are a person with good word skills and an inquisitive mind. Also, I assume you have good keyboard skills, access to the Internet, and have already created some HTML pages using, say, Netscape Composer. You may need help from your Internet Service Provider (ISP) to upload pages onto your Web site. This article is based on my experience teaching an online interactive course in Web indexing for my company, WWWalker Web Development, in 1998. We develop Web sites, support Linux and Windows NT, write technical articles, and specialize in Web indexing.

0.006668197 = product of:
  0.020004591 = sum of:
    0.020004591 = weight(_text_:on in 5040) [ClassicSimilarity], result of:
      0.020004591 = score(doc=5040,freq=18.0), product of:
        0.109763056 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.04990557 = queryNorm
        0.1822525 = fieldWeight in 5040, product of:
          4.2426405 = tf(freq=18.0), with freq of:
            18.0 = termFreq=18.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.01953125 = fieldNorm(doc=5040)
  0.33333334 = coord(1/3)

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.0062868367 = product of:
  0.01886051 = sum of:
    0.01886051 = weight(_text_:on in 221) [ClassicSimilarity], result of:
      0.01886051 = score(doc=221,freq=4.0), product of:
        0.109763056 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.04990557 = queryNorm
        0.1718293 = fieldWeight in 221, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.0390625 = fieldNorm(doc=221)
  0.33333334 = coord(1/3)

Abstract

Creating an online index for a Web site is not a job for the timid. Those contemplating this form of Web indexing should already be accomplished indexers and should have strong experience in Web page creation. Knowledge of HTML is essential. In fact, depending on the nature of a Web indexing job, you may find that it requires more HTML knowledge than indexing skill. Like embedded indexing, Web site indexing is far more work than traditional indexing: the choice of terms is constrained, and the indexing process itself is slower and more challenging. Entries must be carefully chosen because the editing process can be tedious and time-consuming, sometimes more time-consuming than making the original entries. Hypertext links and anchors must be added, and the index itself must be tested to make sure that links work as intended. Adequate compensation for your project is imperative. Web indexing does have its rewards, though, especially for indexers who are intrigued by the Web and Web page design, for those who like a challenge, and, of course, for those who like to have their work online for all the world to see. This article provides a look at the process of creating a Web index for an online newsletter. It is also applicable to other forms of Web site indexing, and should give the beginning Web site indexer an idea of what to expect on that first job

0.006159817 = product of:
  0.01847945 = sum of:
    0.01847945 = weight(_text_:on in 226) [ClassicSimilarity], result of:
      0.01847945 = score(doc=226,freq=6.0), product of:
        0.109763056 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.04990557 = queryNorm
        0.16835764 = fieldWeight in 226, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.03125 = fieldNorm(doc=226)
  0.33333334 = coord(1/3)

Abstract

Why do you need samples of your indexing work on your Web site? Think about these situations: Scenario 1: You've contacted a potential client who says he has a project ready to be assigned. He requests some samples of your work. You fax them to him right away and call back a few hours later. "Oh," he says, "I didn't get the fax but anyway I already assigned the project. I can keep your name for future reference, though." Scenario 2: Another potential client asks you to send her some samples and if they're satisfactory, she'll put you on the freelance list. You mail them to her, or even FedEx them if you can spend the money. You wait a week and call her back. She does not remember who you are, and has not seen the samples. If she can find them, she says, she will file them for future reference. Scenario 3: You contacted a potential client who has asked to see some samples of your work. As it happens, she has a project ready to go and if your work is acceptable, you can have the job. You can FedEx her some samples, or you can fax them, she says. You think about FedEx and faxing costs, and mail and faxes that never get to her desk, and the risk of losing the assignment if she calls someone else later today, which she almost surely will, and you suggest an alternative. If she has Internet access, she can see a list of the indexes you've completed, and some samples of your indexes instantly. She is impressed that you have the know-how to create a Web site, and agrees to take a look and call you back shortly. You give her your URL and your phone number, and stand by. In five minutes she calls you back, says she is pleased with what she saw, and asks for your address so she can send the job out to you today.

0.0056345966 = product of:
  0.01690379 = sum of:
    0.01690379 = product of:
      0.03380758 = sum of:
        0.03380758 = weight(_text_:22 in 5775) [ClassicSimilarity], result of:
          0.03380758 = score(doc=5775,freq=2.0), product of:
            0.1747608 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04990557 = queryNorm
            0.19345059 = fieldWeight in 5775, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0390625 = fieldNorm(doc=5775)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Abstract

The "Relative Index" of the Dewey Decimal Classification (DDC) is investigated over the span of its lifetime in 22 editions of the DDC as to its character as a concept indexing system, its provision of conceptual contexts for the terms it lists, and the way in which the index intersects with special tables of categories used in the system. Striking features of the index that are discussed include how the locater function of an index is expressed in it, its practice of including concepts that have not been given specific notational locations in the system, its two methods of providing conceptual contexts for indexed terms (by means of the notation of the system and by the insertion of enhancement terms that portray conceptual context), and how the index has intersected with three types of special tables of categories in the system. Critical issues raised include the indexing of constructed or synthesized complex concepts, inconsistencies in how enhancement terms are portrayed and the absence of them in some instances, the problem of equating conceptual context with disciplinary context, and problems associated with not indexing one type of special table. Summary and conclusions are extended to problems that arise in studying the index.

0.0053345575 = product of:
  0.016003672 = sum of:
    0.016003672 = weight(_text_:on in 214) [ClassicSimilarity], result of:
      0.016003672 = score(doc=214,freq=2.0), product of:
        0.109763056 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.04990557 = queryNorm
        0.14580199 = fieldWeight in 214, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.046875 = fieldNorm(doc=214)
  0.33333334 = coord(1/3)

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.0053345575 = product of:
  0.016003672 = sum of:
    0.016003672 = weight(_text_:on in 219) [ClassicSimilarity], result of:
      0.016003672 = score(doc=219,freq=2.0), product of:
        0.109763056 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.04990557 = queryNorm
        0.14580199 = fieldWeight in 219, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.046875 = fieldNorm(doc=219)
  0.33333334 = coord(1/3)

Abstract

In this chapter we turn to embedded indexing for the Internet, frequently called Web indexing. We will define Web indexes; describe the structure of entries for Web indexes; present some of the challenges that Web indexers face; and compare Web indexes to search engines. One of the difficulties in defining Web indexes is their relative newness. The first pages were placed on the World Wide Web in 1991 when Tim Berners Lee, its founder, uploaded four files. We are in a period of transition, moving from using well-established forms of writing and communications to others that are still in their infancy. Paramount among these is the Web. For indexers, this is an uncharted voyage where we must jettison firmly established ideas while developing new ones. Where the voyage will end is anyone's guess.

0.005029469 = product of:
  0.015088406 = sum of:
    0.015088406 = weight(_text_:on in 72) [ClassicSimilarity], result of:
      0.015088406 = score(doc=72,freq=4.0), product of:
        0.109763056 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.04990557 = queryNorm
        0.13746344 = fieldWeight in 72, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.03125 = fieldNorm(doc=72)
  0.33333334 = coord(1/3)

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.0044454644 = product of:
  0.013336393 = sum of:
    0.013336393 = weight(_text_:on in 215) [ClassicSimilarity], result of:
      0.013336393 = score(doc=215,freq=2.0), product of:
        0.109763056 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.04990557 = queryNorm
        0.121501654 = fieldWeight in 215, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.0390625 = fieldNorm(doc=215)
  0.33333334 = coord(1/3)

Content

Enthält die Beiträge: Part 1: Beyond stand-alone indexes: embedded indexing: WRIGHT; J.C.: The world of embedded indexing; MONCRIEF, L.: Indexing computer-related documents - Part 2: Beyond the book: Web indexing: WALKER, D.: Subject-oriented Web indexing; BROCCOLI, K. u. G.V. RAVENSWAAY: Web indexing - anchors away; MAISLIN, S.: Ripping out the pages; ROWLAND, M.J.: Plunging in: Creating a Web site index for an online newsletter - Part 3: Special topics in computer-based indexing: ROWLAND, M.J.: <Meta> tags; WOODS. X.B.: Envisioning the word: Multimedia CD-ROM indexing; HOLBERT, S.: How to index Windows-based online help - Part 4: Beyond traditional marketing - selling yourself in hyperspace: ROWLAND, M.J.: Web site design for indexers; RICE, R.: Putting sample indexes on your Web site; CONNOLLY, D.A.: The many uses of Email discussion lists

0.0039442177 = product of:
  0.011832653 = sum of:
    0.011832653 = product of:
      0.023665305 = sum of:
        0.023665305 = weight(_text_:22 in 1502) [ClassicSimilarity], result of:
          0.023665305 = score(doc=1502,freq=2.0), product of:
            0.1747608 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04990557 = queryNorm
            0.1354154 = fieldWeight in 1502, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.02734375 = fieldNorm(doc=1502)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Content

"Unter der Leitung von Frank Merrett von der Socieryy of Indexers (www.indexers.org.uk), die in Sheffield ihren Hauptsitz hat, fand am 22. Januar in London ein Workshop statt, in dem Einblicke in das Indexing (Registererstellung) ermöglicht wurden. SechsTeilnehmerinnen und drei Teilnehmer (Bibliothekare, Katalogisierer, angehende Indexer, Benutzer von Indices) bekamen durch Merrett neben den grundlegenden Dingen auch ein wenig Einblick in die Berufswirklichkeit eines Indexers vermittelt. Zunächst wurden einige Definitionen dessen, was ein Index ist, angesprochen: Ein Index (Register) ist eine systematische Anordnung von Eintragungen, die es dem Benutzer ermöglichen, Informationen in einem Dokument zu finden (nach Norm BS ISO 999,1996). Auch andere Definitionen besagen, dass die im Hauptteil eines Dokuments enthaltenen Informationen so herausgefiltert werden sollen, dass durch die Benutzung des Registers ein möglichst benutzerfreundlicher Zugang zum Hauptteil erfolgen kann. Ein Index soll den einen Benutzer entscheiden lassen, ob ein Dokument etwas für ihn Interessantes enthält. Dem anderen soll es dazu dienen, das Gelesene wieder aufzufrischen. Ein Index muss beiden gerecht werden. Nach Eintreffen des Materials vom Verlag (sehr oft als Papierausdruck) beginnt der erste Schritt, der vom persönlichen Arbeitsstil des Indexers abhängt. Manche beginnen sofort beim Lesen mit dem Niederschreiben von Begriffen, oft unter Verwendung von Software (Macrex, Cindex), andere markieren oder unterstreichen zunächst die relevanten Begriffe. Hier beginnt die eigentliche Arbeit, die darin besteht, wichtige Informationen aus dem Text herauszufiltern und so aufzubereiten, dass ein Buchleser zu Wichtigem hingeführt wird. Dazu gehören Entscheidungen wie zum Beispiel »was ist wichtig«, »was kann/ muss weggelassen werden«, »wo müssen Siehe- beziehungsweise Siehe-auch-Verweise eingebrachtwerden«. Bibliothekarisch gesehen, ist dies Sacherschließung und zugleich formale Erfassung, letztlich das Aufbauen eines Kreuzkatalogs. So wie ein Sacherschließer muss auch ein Indexer ständig überlegen, mit welchen Begriffen er dem Benutzer des Registers einen guten Zugang zur Information verschaffen kann. Ein gutes Verständnis des Faches, das in der Vorlage behandelt wird, ist deshalb unbedingt notwendig. Das wurde anhand einiger Seiten geübt, genauso wie das Aufbe-reiten des Index. Äußerste Genauigkeit ist hier nötig. Anhand eines fertigen Index mit eingebauten Ungenauigkeiten wurde geübt, sehr genau hinzuschauen und kleinste Ungenauigkeiten zu erkennen. Merrett sagte, dass ein gut geschriebenes Buch besser zu bearbeiten sei als eines, das einen weniger guten Hauptteil hat. Oft hat ein Indexer nur zwei Wochen Zeit für die Erstellung eines Registers. Die wenigsten dürften allerdings ständig von morgens bis abends an einem Index arbeiten, und nur sehr wenige verdienen ausschließlich mit dem Erstellen von Registern ihren Lebensunterhalt. Meistens ist dies ein Nebenjob. Nach Frank Merrett sind die Verhandlungen mit einem Verlag über einen zu erstellenden Index recht vorsichtig zu führen. Insbesondere über die Termine (Eintreffen des Manuskripts, Abliefern des Produkts) sowie die Form der Vorlage (welches Format, welcher Umfang) muss sich ein Indexer absichern, um keine Überraschungen zu erleben. So kann es sein, dass die Vorlage nicht als Buch, sondern als ein Stapel von Druckbogen, ungefalzt und unsortiert, ankommt. Auch das Honorar muß vom Indexer in Anbetracht des zu erwartenden Aufwandes verhandelt werden. Indexer ist keine geschützte Bezeichnung, deshalb kann sich jeder so nennen. Die Prüfungen, die man bei der Sociery of Indexers ablegen kann, sind aber ein Qualitätsnachweis. Die Society kann durch das Aufführen der Namen und Spezialgebiete auf der Homepage beziehungsweise in einem Verzeichnis einiges für die Mitglieder tun. Die Sociery legt auf das Kontakthalten mit Verlegern großen Wert, um dort auf die Dienste der Indexer hinzuweisen. Um Aufträge muß sich aber jeder selbst kümmern.

0.0035563714 = product of:
  0.010669114 = sum of:
    0.010669114 = weight(_text_:on in 217) [ClassicSimilarity], result of:
      0.010669114 = score(doc=217,freq=2.0), product of:
        0.109763056 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.04990557 = queryNorm
        0.097201325 = fieldWeight in 217, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.03125 = fieldNorm(doc=217)
  0.33333334 = coord(1/3)

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.0035563714 = product of:
  0.010669114 = sum of:
    0.010669114 = weight(_text_:on in 223) [ClassicSimilarity], result of:
      0.010669114 = score(doc=223,freq=2.0), product of:
        0.109763056 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.04990557 = queryNorm
        0.097201325 = fieldWeight in 223, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.03125 = fieldNorm(doc=223)
  0.33333334 = coord(1/3)

Abstract

If you are an indexer who is accustomed to working in solitude with static words, you might face some big surprises in the production of a multimedia CD-ROM. You will not be working alone. You will not be working from a manuscript. Your dexterity with a dedicated software tool for indexing will be irrelevant. The coding or tagging might not be your worry either, because it will likely be done by members of a separate technical staff. The CD-ROM can currently hold 660 megabytes of data. Its production is a massive team effort. Because of the sheer volume of data involved, it is unlikely that one indexer working alone can handle the job in a reasonable period of time. The database for the actual index entries is likely to have been designed specifically for the project at hand, so the indexers will learn the software tools on the job. The entire project will probably be onscreen. So, if you choose to thrust yourself into this teeming amalgam of production, what are the prerequisites and what new things can you expect to learn? CD-ROM is an amorphous new medium with few rules. Your most important resume items might be your flexibility, imagination, and love of words. What remains unchanged from traditional back-of-the-book indexing is the need for empathy with the user; you will still need to come up with exactly the right word for the situation. What is new here is the situation: you might learn to envision the words that correspond to non-textual media such as graphics, photos, video clips, and musical passages. And because you will be dealing with vast amounts of textual and sensory data, you might find yourself rethinking the nature and purpose of an index as a whole. CD-ROM production can take many forms; three will be discussed here