Search (75 results, page 3 of 4)

0.0018615347 = product of:
  0.0037230693 = sum of:
    0.0037230693 = product of:
      0.0074461387 = sum of:
        0.0074461387 = weight(_text_:a in 5158) [ClassicSimilarity], result of:
          0.0074461387 = score(doc=5158,freq=12.0), product of:
            0.04772363 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.041389145 = queryNorm
            0.15602624 = fieldWeight in 5158, product of:
              3.4641016 = tf(freq=12.0), with freq of:
                12.0 = termFreq=12.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0390625 = fieldNorm(doc=5158)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

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

Type

a

0.001823924 = product of:
  0.003647848 = sum of:
    0.003647848 = product of:
      0.007295696 = sum of:
        0.007295696 = weight(_text_:a in 224) [ClassicSimilarity], result of:
          0.007295696 = score(doc=224,freq=8.0), product of:
            0.04772363 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.041389145 = queryNorm
            0.15287387 = fieldWeight in 224, product of:
              2.828427 = tf(freq=8.0), with freq of:
                8.0 = termFreq=8.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046875 = fieldNorm(doc=224)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Today, more and more software packages come with online documentation. Some have complete manuals as well. Others have basic documentation on paper and more advanced information online. I recently purchased a computer that came with 20 software programs and not one page of written documentation. More and more, users have to find information by searching online. Most documentation teams focus on writing and ignore the problems of information retrieval, making information in printed documents difficult to find, and online information impossible to find. With online Help, you cannot browse the documentation. You cannot even browse more than a couple of inches of the index at a time. If online users do not get superb guidance into the jungle of online Help, they go away like the hero of Joseph Conrad's Heart of Darkness, saying "Oh, the horror! The horror!" How does an online Help index work? The following examples are based on the Windows 95 Help-type system, but do not represent actual Help screens

Type

a

0.001719612 = product of:
  0.003439224 = sum of:
    0.003439224 = product of:
      0.006878448 = sum of:
        0.006878448 = weight(_text_:a in 223) [ClassicSimilarity], result of:
          0.006878448 = score(doc=223,freq=16.0), product of:
            0.04772363 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.041389145 = queryNorm
            0.14413087 = fieldWeight in 223, product of:
              4.0 = tf(freq=16.0), with freq of:
                16.0 = termFreq=16.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.03125 = fieldNorm(doc=223)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

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

Type

a

0.001719612 = product of:
  0.003439224 = sum of:
    0.003439224 = product of:
      0.006878448 = sum of:
        0.006878448 = weight(_text_:a in 744) [ClassicSimilarity], result of:
          0.006878448 = score(doc=744,freq=4.0), product of:
            0.04772363 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.041389145 = queryNorm
            0.14413087 = fieldWeight in 744, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0625 = fieldNorm(doc=744)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Type

a

0.0015795645 = product of:
  0.003159129 = sum of:
    0.003159129 = product of:
      0.006318258 = sum of:
        0.006318258 = weight(_text_:a in 5612) [ClassicSimilarity], result of:
          0.006318258 = score(doc=5612,freq=6.0), product of:
            0.04772363 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.041389145 = queryNorm
            0.13239266 = fieldWeight in 5612, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046875 = fieldNorm(doc=5612)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Library of Congress Subjecl Headings retrieved as the results of a search in an online catalog are likely to be filed in straight alphabetical, word-by-word order, ignoring the semantic structures of these headings and scattering headings of a similar type. This practice makes LC headings unnecessarily difficult to use and negates much of their indexing power. Enthusiasm for filing simplicity and postcoordinate indexing are likely contributing factors to this phenomenon. Since the report Headings for Tomorrow (1992) first raised this issue, filing practices favoring postcoordination over precoordination appear to have become more widespread and more entrenched

Type

a

0.0015199365 = product of:
  0.003039873 = sum of:
    0.003039873 = product of:
      0.006079746 = sum of:
        0.006079746 = weight(_text_:a in 743) [ClassicSimilarity], result of:
          0.006079746 = score(doc=743,freq=2.0), product of:
            0.04772363 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.041389145 = queryNorm
            0.12739488 = fieldWeight in 743, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.078125 = fieldNorm(doc=743)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Type

a

0.0015046606 = product of:
  0.0030093212 = sum of:
    0.0030093212 = product of:
      0.0060186423 = sum of:
        0.0060186423 = weight(_text_:a in 740) [ClassicSimilarity], result of:
          0.0060186423 = score(doc=740,freq=4.0), product of:
            0.04772363 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.041389145 = queryNorm
            0.12611452 = fieldWeight in 740, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0546875 = fieldNorm(doc=740)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Type

a

0.0014892276 = product of:
  0.0029784553 = sum of:
    0.0029784553 = product of:
      0.0059569106 = sum of:
        0.0059569106 = weight(_text_:a in 72) [ClassicSimilarity], result of:
          0.0059569106 = score(doc=72,freq=12.0), product of:
            0.04772363 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.041389145 = queryNorm
            0.12482099 = fieldWeight in 72, product of:
              3.4641016 = tf(freq=12.0), with freq of:
                12.0 = termFreq=12.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.03125 = fieldNorm(doc=72)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Content

Enthält die Kapitel: Introduction to book indexing - The author and the index - Getting started - Structure of entries - Arrangement of entries - Special concerns in indexing - Names, names, names - Format and layout of the index - Editing the index - Tools for indexing - Appendix A: Specifications worksheet - Appendix B: Resources for indexers

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.0013163039 = product of:
  0.0026326077 = sum of:
    0.0026326077 = product of:
      0.0052652154 = sum of:
        0.0052652154 = weight(_text_:a in 225) [ClassicSimilarity], result of:
          0.0052652154 = score(doc=225,freq=6.0), product of:
            0.04772363 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.041389145 = queryNorm
            0.11032722 = fieldWeight in 225, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0390625 = fieldNorm(doc=225)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

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!

Type

a

0.001289709 = product of:
  0.002579418 = sum of:
    0.002579418 = product of:
      0.005158836 = sum of:
        0.005158836 = weight(_text_:a in 216) [ClassicSimilarity], result of:
          0.005158836 = score(doc=216,freq=4.0), product of:
            0.04772363 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.041389145 = queryNorm
            0.10809815 = fieldWeight in 216, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046875 = fieldNorm(doc=216)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

If you want to let other indexers know about a great new medical dictionary, discuss the pros and cons of using prepositions in subentries, find an indexer in Phoenix, or maybe share some marketing tips, then consider joining an email discussion list. Email discussion lists provide numerous tools and opportunities for indexers, especially for freelancers. Despite the rapid growth of Web- and graphical-based communication, email remains the linchpin of electronic communication. While the World Wide Web has become ubiquitous in our society, email remains the most reliable form of electronic communication. Email access is more prevalent than Web access, less cumbersome, and some would say, more egalitarian. Despite improvements over time, Web access is not available in equal quality or proportion to email access, especially in poorer or developing areas. Indeed, many users who have access to both restrict their use of the Web for important research efforts, and maintain nearconstant connection with their email servers for daily business

Type

a

0.001289709 = product of:
  0.002579418 = sum of:
    0.002579418 = product of:
      0.005158836 = sum of:
        0.005158836 = weight(_text_:a in 218) [ClassicSimilarity], result of:
          0.005158836 = score(doc=218,freq=4.0), product of:
            0.04772363 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.041389145 = queryNorm
            0.10809815 = fieldWeight in 218, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046875 = fieldNorm(doc=218)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

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.

Type

a

0.001289709 = product of:
  0.002579418 = sum of:
    0.002579418 = product of:
      0.005158836 = sum of:
        0.005158836 = weight(_text_:a in 219) [ClassicSimilarity], result of:
          0.005158836 = score(doc=219,freq=4.0), product of:
            0.04772363 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.041389145 = queryNorm
            0.10809815 = fieldWeight in 219, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046875 = fieldNorm(doc=219)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

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.

Type

a

0.0012159493 = product of:
  0.0024318986 = sum of:
    0.0024318986 = product of:
      0.004863797 = sum of:
        0.004863797 = weight(_text_:a in 2565) [ClassicSimilarity], result of:
          0.004863797 = score(doc=2565,freq=2.0), product of:
            0.04772363 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.041389145 = queryNorm
            0.10191591 = fieldWeight in 2565, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0625 = fieldNorm(doc=2565)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Type

a

0.0012159493 = product of:
  0.0024318986 = sum of:
    0.0024318986 = product of:
      0.004863797 = sum of:
        0.004863797 = weight(_text_:a in 736) [ClassicSimilarity], result of:
          0.004863797 = score(doc=736,freq=2.0), product of:
            0.04772363 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.041389145 = queryNorm
            0.10191591 = fieldWeight in 736, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0625 = fieldNorm(doc=736)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Type

a

0.0012159493 = product of:
  0.0024318986 = sum of:
    0.0024318986 = product of:
      0.004863797 = sum of:
        0.004863797 = weight(_text_:a in 738) [ClassicSimilarity], result of:
          0.004863797 = score(doc=738,freq=2.0), product of:
            0.04772363 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.041389145 = queryNorm
            0.10191591 = fieldWeight in 738, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0625 = fieldNorm(doc=738)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Type

a

0.0012159493 = product of:
  0.0024318986 = sum of:
    0.0024318986 = product of:
      0.004863797 = sum of:
        0.004863797 = weight(_text_:a in 741) [ClassicSimilarity], result of:
          0.004863797 = score(doc=741,freq=2.0), product of:
            0.04772363 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.041389145 = queryNorm
            0.10191591 = fieldWeight in 741, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0625 = fieldNorm(doc=741)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Type

a

0.0012159493 = product of:
  0.0024318986 = sum of:
    0.0024318986 = product of:
      0.004863797 = sum of:
        0.004863797 = weight(_text_:a in 746) [ClassicSimilarity], result of:
          0.004863797 = score(doc=746,freq=2.0), product of:
            0.04772363 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.041389145 = queryNorm
            0.10191591 = fieldWeight in 746, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0625 = fieldNorm(doc=746)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Type

a

0.0010747575 = product of:
  0.002149515 = sum of:
    0.002149515 = product of:
      0.00429903 = sum of:
        0.00429903 = weight(_text_:a in 215) [ClassicSimilarity], result of:
          0.00429903 = score(doc=215,freq=4.0), product of:
            0.04772363 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.041389145 = queryNorm
            0.090081796 = fieldWeight in 215, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0390625 = fieldNorm(doc=215)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Are you curious about new indexing technologies? Would you like to develop and create innovative indexes that provide access to online resources, multimedia, or online help? Do you want to learn new skills and expand your marketing possibilities? This book provides an in-depth look at current and emerging computer-based technologies and offers suggestions for obtaining work in these fields. Extensive refrences and a glossary round out this informative and exciting new book

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.0010639556 = product of:
  0.0021279112 = sum of:
    0.0021279112 = product of:
      0.0042558224 = sum of:
        0.0042558224 = weight(_text_:a in 6106) [ClassicSimilarity], result of:
          0.0042558224 = score(doc=6106,freq=2.0), product of:
            0.04772363 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.041389145 = queryNorm
            0.089176424 = fieldWeight in 6106, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0546875 = fieldNorm(doc=6106)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Type

a

0.0010639556 = product of:
  0.0021279112 = sum of:
    0.0021279112 = product of:
      0.0042558224 = sum of:
        0.0042558224 = weight(_text_:a in 747) [ClassicSimilarity], result of:
          0.0042558224 = score(doc=747,freq=2.0), product of:
            0.04772363 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.041389145 = queryNorm
            0.089176424 = fieldWeight in 747, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0546875 = fieldNorm(doc=747)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Type

a