Search (59 results, page 1 of 3)

  • × year_i:[2000 TO 2010}
  • × theme_ss:"Register"
  1. Rowland, M.J.: Web site design for indexers (2000) 0.05
    0.050086193 = product of:
      0.100172386 = sum of:
        0.030249555 = weight(_text_:use in 225) [ClassicSimilarity], result of:
          0.030249555 = score(doc=225,freq=4.0), product of:
            0.12644777 = queryWeight, product of:
              3.0620887 = idf(docFreq=5623, maxDocs=44218)
              0.041294612 = queryNorm
            0.23922569 = fieldWeight in 225, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.0620887 = idf(docFreq=5623, maxDocs=44218)
              0.0390625 = fieldNorm(doc=225)
        0.015778005 = weight(_text_:of in 225) [ClassicSimilarity], result of:
          0.015778005 = score(doc=225,freq=16.0), product of:
            0.06457475 = queryWeight, product of:
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.041294612 = queryNorm
            0.24433708 = fieldWeight in 225, product of:
              4.0 = tf(freq=16.0), with freq of:
                16.0 = termFreq=16.0
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.0390625 = fieldNorm(doc=225)
        0.00955682 = product of:
          0.01911364 = sum of:
            0.01911364 = weight(_text_:on in 225) [ClassicSimilarity], result of:
              0.01911364 = score(doc=225,freq=6.0), product of:
                0.090823986 = queryWeight, product of:
                  2.199415 = idf(docFreq=13325, maxDocs=44218)
                  0.041294612 = 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.5 = coord(1/2)
        0.04458801 = product of:
          0.08917602 = sum of:
            0.08917602 = weight(_text_:computers in 225) [ClassicSimilarity], result of:
              0.08917602 = score(doc=225,freq=4.0), product of:
                0.21710795 = queryWeight, product of:
                  5.257537 = idf(docFreq=625, maxDocs=44218)
                  0.041294612 = queryNorm
                0.41074508 = fieldWeight in 225, product of:
                  2.0 = tf(freq=4.0), with freq of:
                    4.0 = termFreq=4.0
                  5.257537 = idf(docFreq=625, maxDocs=44218)
                  0.0390625 = fieldNorm(doc=225)
          0.5 = coord(1/2)
      0.5 = coord(4/8)
    
    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!
    Imprint
    Phoenix, AZ : American Society of Indexers / Information Today
  2. Hert, C.A.; Jacob, E.K.; Dawson, P.: ¬A usability assessment of online indexing structures in the networked environment (2000) 0.04
    0.035899878 = product of:
      0.071799755 = sum of:
        0.020873476 = weight(_text_:retrieval in 5158) [ClassicSimilarity], result of:
          0.020873476 = score(doc=5158,freq=2.0), product of:
            0.124912694 = queryWeight, product of:
              3.024915 = idf(docFreq=5836, maxDocs=44218)
              0.041294612 = queryNorm
            0.16710453 = fieldWeight in 5158, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.024915 = idf(docFreq=5836, maxDocs=44218)
              0.0390625 = fieldNorm(doc=5158)
        0.021389665 = weight(_text_:use in 5158) [ClassicSimilarity], result of:
          0.021389665 = score(doc=5158,freq=2.0), product of:
            0.12644777 = queryWeight, product of:
              3.0620887 = idf(docFreq=5623, maxDocs=44218)
              0.041294612 = queryNorm
            0.1691581 = fieldWeight in 5158, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.0620887 = idf(docFreq=5623, maxDocs=44218)
              0.0390625 = fieldNorm(doc=5158)
        0.01850135 = weight(_text_:of in 5158) [ClassicSimilarity], result of:
          0.01850135 = score(doc=5158,freq=22.0), product of:
            0.06457475 = queryWeight, product of:
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.041294612 = queryNorm
            0.28651062 = fieldWeight in 5158, product of:
              4.690416 = tf(freq=22.0), with freq of:
                22.0 = termFreq=22.0
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.0390625 = fieldNorm(doc=5158)
        0.0110352645 = product of:
          0.022070529 = sum of:
            0.022070529 = weight(_text_:on in 5158) [ClassicSimilarity], result of:
              0.022070529 = score(doc=5158,freq=8.0), product of:
                0.090823986 = queryWeight, product of:
                  2.199415 = idf(docFreq=13325, maxDocs=44218)
                  0.041294612 = 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.5 = coord(1/2)
      0.5 = coord(4/8)
    
    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
    Source
    Journal of the American Society for Information Science. 51(2000) no.11, S.971-988
  3. Ross, J.: ¬The impact of technology on indexing (2000) 0.03
    0.03009975 = product of:
      0.080266 = sum of:
        0.017850775 = weight(_text_:of in 263) [ClassicSimilarity], result of:
          0.017850775 = score(doc=263,freq=2.0), product of:
            0.06457475 = queryWeight, product of:
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.041294612 = queryNorm
            0.27643585 = fieldWeight in 263, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.125 = fieldNorm(doc=263)
        0.017656423 = product of:
          0.035312846 = sum of:
            0.035312846 = weight(_text_:on in 263) [ClassicSimilarity], result of:
              0.035312846 = score(doc=263,freq=2.0), product of:
                0.090823986 = queryWeight, product of:
                  2.199415 = idf(docFreq=13325, maxDocs=44218)
                  0.041294612 = queryNorm
                0.3888053 = fieldWeight in 263, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  2.199415 = idf(docFreq=13325, maxDocs=44218)
                  0.125 = fieldNorm(doc=263)
          0.5 = coord(1/2)
        0.0447588 = product of:
          0.0895176 = sum of:
            0.0895176 = weight(_text_:22 in 263) [ClassicSimilarity], result of:
              0.0895176 = score(doc=263,freq=2.0), product of:
                0.1446067 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.041294612 = 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.5 = coord(1/2)
      0.375 = coord(3/8)
    
    Source
    Indexer. 22(2000) no.1, S.25-26
  4. Wool, G.: Filing and precoordination : how subject headings are displayed in online catalogs and why it matters (2000) 0.03
    0.025167283 = product of:
      0.06711275 = sum of:
        0.025048172 = weight(_text_:retrieval in 5612) [ClassicSimilarity], result of:
          0.025048172 = score(doc=5612,freq=2.0), product of:
            0.124912694 = queryWeight, product of:
              3.024915 = idf(docFreq=5836, maxDocs=44218)
              0.041294612 = queryNorm
            0.20052543 = fieldWeight in 5612, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.024915 = idf(docFreq=5836, maxDocs=44218)
              0.046875 = fieldNorm(doc=5612)
        0.025667597 = weight(_text_:use in 5612) [ClassicSimilarity], result of:
          0.025667597 = score(doc=5612,freq=2.0), product of:
            0.12644777 = queryWeight, product of:
              3.0620887 = idf(docFreq=5623, maxDocs=44218)
              0.041294612 = queryNorm
            0.20298971 = fieldWeight in 5612, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.0620887 = idf(docFreq=5623, maxDocs=44218)
              0.046875 = fieldNorm(doc=5612)
        0.016396983 = weight(_text_:of in 5612) [ClassicSimilarity], result of:
          0.016396983 = score(doc=5612,freq=12.0), product of:
            0.06457475 = queryWeight, product of:
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.041294612 = queryNorm
            0.25392252 = fieldWeight in 5612, product of:
              3.4641016 = tf(freq=12.0), with freq of:
                12.0 = termFreq=12.0
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.046875 = fieldNorm(doc=5612)
      0.375 = coord(3/8)
    
    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
    Source
    The LCSH century: one hundred years with the Library of Congress Subject Headings system. Ed.: A.T. Stone
    Theme
    Verbale Doksprachen im Online-Retrieval
  5. Dextre Clarke, S.G.: Evolution towards ISO 25964 : an international standard with guidelines for thesauri and other types of controlled vocabulary (2007) 0.02
    0.023374373 = product of:
      0.06233166 = sum of:
        0.029222867 = weight(_text_:retrieval in 749) [ClassicSimilarity], result of:
          0.029222867 = score(doc=749,freq=2.0), product of:
            0.124912694 = queryWeight, product of:
              3.024915 = idf(docFreq=5836, maxDocs=44218)
              0.041294612 = queryNorm
            0.23394634 = fieldWeight in 749, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.024915 = idf(docFreq=5836, maxDocs=44218)
              0.0546875 = fieldNorm(doc=749)
        0.013526822 = weight(_text_:of in 749) [ClassicSimilarity], result of:
          0.013526822 = score(doc=749,freq=6.0), product of:
            0.06457475 = queryWeight, product of:
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.041294612 = queryNorm
            0.20947541 = fieldWeight in 749, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.0546875 = fieldNorm(doc=749)
        0.019581974 = product of:
          0.039163947 = sum of:
            0.039163947 = weight(_text_:22 in 749) [ClassicSimilarity], result of:
              0.039163947 = score(doc=749,freq=2.0), product of:
                0.1446067 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.041294612 = 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.375 = coord(3/8)
    
    Abstract
    Die geschichtliche Entwicklung von ISO 2788: Documentation - Guidelines for the establishment and development of monolingual thesauri und ISO 5964: Documentation - Guidelines for the establishment and development of multilingual thesauri wird kurz beschrieben. 2001 begann die Arbeit an der Entwicklung von BS 8723: Structured Vocabularies for Information Retrieval - Guide, einer fünfteiligen Norm, die konzipiert wurde, um die internationalen Normen zu aktualisieren, insbesondere mit Hinblick auf Interoperabilität. Der Verfahrensablauf zur Übernahme von BS 8723 als internationale Norm hat begonnen.
    Date
    8.12.2007 19:25:22
  6. Olason, S.C.: Let's get usable! : Usability studies for indexes (2000) 0.02
    0.022663213 = product of:
      0.060435236 = sum of:
        0.019957775 = weight(_text_:of in 882) [ClassicSimilarity], result of:
          0.019957775 = score(doc=882,freq=10.0), product of:
            0.06457475 = queryWeight, product of:
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.041294612 = queryNorm
            0.3090647 = fieldWeight in 882, product of:
              3.1622777 = tf(freq=10.0), with freq of:
                10.0 = termFreq=10.0
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.0625 = fieldNorm(doc=882)
        0.008828212 = product of:
          0.017656423 = sum of:
            0.017656423 = weight(_text_:on in 882) [ClassicSimilarity], result of:
              0.017656423 = score(doc=882,freq=2.0), product of:
                0.090823986 = queryWeight, product of:
                  2.199415 = idf(docFreq=13325, maxDocs=44218)
                  0.041294612 = queryNorm
                0.19440265 = fieldWeight in 882, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  2.199415 = idf(docFreq=13325, maxDocs=44218)
                  0.0625 = fieldNorm(doc=882)
          0.5 = coord(1/2)
        0.03164925 = product of:
          0.0632985 = sum of:
            0.0632985 = weight(_text_:22 in 882) [ClassicSimilarity], result of:
              0.0632985 = score(doc=882,freq=4.0), product of:
                0.1446067 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.041294612 = 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.5 = coord(1/2)
      0.375 = coord(3/8)
    
    Abstract
    The article discusses a series of usability studies on indexes from a systems engineering and human factors perspective. The purpose of these studies is to establish a set of user requirements that indexes need to satisfy. The results from the first set of studies are presented and suggestions made as to how these can be applied to improve the usability and quality of indexes.
    Footnote
    Vgl.: http://www.theindexer.org/files/22-2-olason.pdf.
    Source
    Indexer. 22(2000) no.2, S.91-95
  7. Holbert, S.: How to index Windows-based online help (2000) 0.02
    0.020793734 = product of:
      0.05544996 = sum of:
        0.025048172 = weight(_text_:retrieval in 224) [ClassicSimilarity], result of:
          0.025048172 = score(doc=224,freq=2.0), product of:
            0.124912694 = queryWeight, product of:
              3.024915 = idf(docFreq=5836, maxDocs=44218)
              0.041294612 = queryNorm
            0.20052543 = fieldWeight in 224, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.024915 = idf(docFreq=5836, maxDocs=44218)
              0.046875 = fieldNorm(doc=224)
        0.018933605 = weight(_text_:of in 224) [ClassicSimilarity], result of:
          0.018933605 = score(doc=224,freq=16.0), product of:
            0.06457475 = queryWeight, product of:
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.041294612 = queryNorm
            0.2932045 = fieldWeight in 224, product of:
              4.0 = tf(freq=16.0), with freq of:
                16.0 = termFreq=16.0
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.046875 = fieldNorm(doc=224)
        0.011468184 = product of:
          0.022936368 = sum of:
            0.022936368 = weight(_text_:on in 224) [ClassicSimilarity], result of:
              0.022936368 = score(doc=224,freq=6.0), product of:
                0.090823986 = queryWeight, product of:
                  2.199415 = idf(docFreq=13325, maxDocs=44218)
                  0.041294612 = queryNorm
                0.25253648 = fieldWeight in 224, product of:
                  2.4494898 = tf(freq=6.0), with freq of:
                    6.0 = termFreq=6.0
                  2.199415 = idf(docFreq=13325, maxDocs=44218)
                  0.046875 = fieldNorm(doc=224)
          0.5 = coord(1/2)
      0.375 = coord(3/8)
    
    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
    Imprint
    Phoenix, AZ : American Society of Indexers / Information Today
  8. Anderson, J.D.: Indexing, teaching of, See: Information retrieval design (2002) 0.02
    0.018516291 = product of:
      0.074065164 = sum of:
        0.058445733 = weight(_text_:retrieval in 550) [ClassicSimilarity], result of:
          0.058445733 = score(doc=550,freq=2.0), product of:
            0.124912694 = queryWeight, product of:
              3.024915 = idf(docFreq=5836, maxDocs=44218)
              0.041294612 = queryNorm
            0.46789268 = fieldWeight in 550, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.024915 = idf(docFreq=5836, maxDocs=44218)
              0.109375 = fieldNorm(doc=550)
        0.015619429 = weight(_text_:of in 550) [ClassicSimilarity], result of:
          0.015619429 = score(doc=550,freq=2.0), product of:
            0.06457475 = queryWeight, product of:
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.041294612 = queryNorm
            0.24188137 = fieldWeight in 550, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.109375 = fieldNorm(doc=550)
      0.25 = coord(2/8)
    
  9. Hedden, H.: Creating an index for your Web site to make info easier to see (2006) 0.02
    0.0164762 = product of:
      0.0659048 = sum of:
        0.0154592255 = weight(_text_:of in 2189) [ClassicSimilarity], result of:
          0.0154592255 = score(doc=2189,freq=6.0), product of:
            0.06457475 = queryWeight, product of:
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.041294612 = queryNorm
            0.23940048 = fieldWeight in 2189, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.0625 = fieldNorm(doc=2189)
        0.050445575 = product of:
          0.10089115 = sum of:
            0.10089115 = weight(_text_:computers in 2189) [ClassicSimilarity], result of:
              0.10089115 = score(doc=2189,freq=2.0), product of:
                0.21710795 = queryWeight, product of:
                  5.257537 = idf(docFreq=625, maxDocs=44218)
                  0.041294612 = queryNorm
                0.464705 = fieldWeight in 2189, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  5.257537 = idf(docFreq=625, maxDocs=44218)
                  0.0625 = fieldNorm(doc=2189)
          0.5 = coord(1/2)
      0.25 = coord(2/8)
    
    Abstract
    Most libraries have long had their own Web sites. The longer a library has had a Web site the more likely it is that the number of pages, and the amount of information within those pages, has grown beyond what users can find simply with the navigation menu. Building a site index is a great way to help seekers find all those bits of data they might otherwise miss.
    Source
    Computers in libraries. 26(2006) no.9, S.16-
  10. Stauber, D.M.: Facing the text : content and structure in book indexing (2004) 0.02
    0.016244993 = product of:
      0.043319978 = sum of:
        0.015124777 = weight(_text_:use in 5040) [ClassicSimilarity], result of:
          0.015124777 = score(doc=5040,freq=4.0), product of:
            0.12644777 = queryWeight, product of:
              3.0620887 = idf(docFreq=5623, maxDocs=44218)
              0.041294612 = queryNorm
            0.11961284 = fieldWeight in 5040, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.0620887 = idf(docFreq=5623, maxDocs=44218)
              0.01953125 = fieldNorm(doc=5040)
        0.019918753 = weight(_text_:of in 5040) [ClassicSimilarity], result of:
          0.019918753 = score(doc=5040,freq=102.0), product of:
            0.06457475 = queryWeight, product of:
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.041294612 = queryNorm
            0.3084604 = fieldWeight in 5040, product of:
              10.099504 = tf(freq=102.0), with freq of:
                102.0 = termFreq=102.0
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.01953125 = fieldNorm(doc=5040)
        0.0082764495 = product of:
          0.016552899 = sum of:
            0.016552899 = weight(_text_:on in 5040) [ClassicSimilarity], result of:
              0.016552899 = score(doc=5040,freq=18.0), product of:
                0.090823986 = queryWeight, product of:
                  2.199415 = idf(docFreq=13325, maxDocs=44218)
                  0.041294612 = 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.5 = coord(1/2)
      0.375 = coord(3/8)
    
    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.
    She divides the topics within the text to be indexed into the categories of metatopics, local main topics, and ancillary topics, followed by subheadings. The indexability of individual topics at whatever level, and their wording, absorb other chapters. Linkages among the topics - cross-references and doubleposting - arc tracked in the chapter "Connections and Access." Finally, the mechanics of indexing are contained in "Process" and "Inside an Indexer's Brain" describes her own procedure and feelings as she indexes a book from beginning to end. When I initially faced the text of this book, I felt overwhelmed, even bewildered, by the plethora of terminology, much of it Stauber's own. Further, each chapter is divided into a complex array of headings, subheadings, sub-subheadings, and more. But when I read from beginning to end, all those pieces fell into place. Stauber develops her text logically, explaining each step of the way clearly, distinguishing each detail from others, and frequently linking passages to relevant others. At every stage in the book, she illustrates with copious examples from indexes she or others have compiled. In the case of her own indexes, she describes her thought processes, her initial reactions to what she read, her decisions regarding the use of particular topics and at what level, and of her chosen terminology; and also, and often, how and why she later changed her mind as she got further into the text. This forms a candid and detailed analysis of indexing, step by step, stage by stage, complex and subtle but with a perceptibly firm connecting structure. In short, she's a good writer.
    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."
  11. Weinberg, B.H.: Predecessors of scientific indexing structures in the domain of religion (2001) 0.02
    0.015313288 = product of:
      0.061253153 = sum of:
        0.022089208 = weight(_text_:of in 4172) [ClassicSimilarity], result of:
          0.022089208 = score(doc=4172,freq=4.0), product of:
            0.06457475 = queryWeight, product of:
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.041294612 = queryNorm
            0.34207192 = fieldWeight in 4172, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.109375 = fieldNorm(doc=4172)
        0.039163947 = product of:
          0.078327894 = sum of:
            0.078327894 = weight(_text_:22 in 4172) [ClassicSimilarity], result of:
              0.078327894 = score(doc=4172,freq=2.0), product of:
                0.1446067 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.041294612 = 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.5 = coord(1/2)
      0.25 = coord(2/8)
    
    Source
    Indexer. 22(2001) no.4, S.178-180
  12. Mulvany, N.C.: Indexing books (2005) 0.01
    0.014791759 = product of:
      0.03944469 = sum of:
        0.01711173 = weight(_text_:use in 72) [ClassicSimilarity], result of:
          0.01711173 = score(doc=72,freq=2.0), product of:
            0.12644777 = queryWeight, product of:
              3.0620887 = idf(docFreq=5623, maxDocs=44218)
              0.041294612 = queryNorm
            0.13532647 = fieldWeight in 72, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.0620887 = idf(docFreq=5623, maxDocs=44218)
              0.03125 = fieldNorm(doc=72)
        0.016090471 = weight(_text_:of in 72) [ClassicSimilarity], result of:
          0.016090471 = score(doc=72,freq=26.0), product of:
            0.06457475 = queryWeight, product of:
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.041294612 = queryNorm
            0.2491759 = fieldWeight in 72, product of:
              5.0990195 = tf(freq=26.0), with freq of:
                26.0 = termFreq=26.0
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.03125 = fieldNorm(doc=72)
        0.0062424885 = product of:
          0.012484977 = sum of:
            0.012484977 = weight(_text_:on in 72) [ClassicSimilarity], result of:
              0.012484977 = score(doc=72,freq=4.0), product of:
                0.090823986 = queryWeight, product of:
                  2.199415 = idf(docFreq=13325, maxDocs=44218)
                  0.041294612 = 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.5 = coord(1/2)
      0.375 = coord(3/8)
    
    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. ..."
    Imprint
    Chicago : University of Chicago Press
  13. Rowland, M.J.: <Meta> tags (2000) 0.01
    0.014095396 = product of:
      0.056381583 = sum of:
        0.036299463 = weight(_text_:use in 222) [ClassicSimilarity], result of:
          0.036299463 = score(doc=222,freq=4.0), product of:
            0.12644777 = queryWeight, product of:
              3.0620887 = idf(docFreq=5623, maxDocs=44218)
              0.041294612 = queryNorm
            0.2870708 = fieldWeight in 222, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.0620887 = idf(docFreq=5623, maxDocs=44218)
              0.046875 = fieldNorm(doc=222)
        0.02008212 = weight(_text_:of in 222) [ClassicSimilarity], result of:
          0.02008212 = score(doc=222,freq=18.0), product of:
            0.06457475 = queryWeight, product of:
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.041294612 = queryNorm
            0.3109903 = fieldWeight in 222, product of:
              4.2426405 = tf(freq=18.0), with freq of:
                18.0 = termFreq=18.0
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.046875 = fieldNorm(doc=222)
      0.25 = coord(2/8)
    
    Abstract
    <META> tags are used to create meta-information, or information about the information in a Web site. There are many types of <META> tags, but those most relevant to indexing are the description and keyword tags. Description tags provide a short summary of the site contents that are often displayed by search engines when they list search results. Keyword tags are used to define words or phrases that someone using a search engine might use to look for relevant sites. <META> tags are of interest to indexers for two reasons. They provide a means of making your indexing business Web site more visible to those searching the Web for indexing services, and they offer indexers a potential new source of work: writing keyword and description tags for Web site developers and companies with Web sites. <META> tag writing makes good use of an indexer's ability to choose relevant key terms, and the closely related skill of abstracting: conveying the essence of a document in a sentence or two.
    Imprint
    Phoenix, AZ : American Society of Indexers / Information Today
  14. Mulvany, N.C.: Back-of-the-book indexing (2009) 0.01
    0.0128120845 = product of:
      0.051248338 = sum of:
        0.033397563 = weight(_text_:retrieval in 3749) [ClassicSimilarity], result of:
          0.033397563 = score(doc=3749,freq=2.0), product of:
            0.124912694 = queryWeight, product of:
              3.024915 = idf(docFreq=5836, maxDocs=44218)
              0.041294612 = queryNorm
            0.26736724 = fieldWeight in 3749, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.024915 = idf(docFreq=5836, maxDocs=44218)
              0.0625 = fieldNorm(doc=3749)
        0.017850775 = weight(_text_:of in 3749) [ClassicSimilarity], result of:
          0.017850775 = score(doc=3749,freq=8.0), product of:
            0.06457475 = queryWeight, product of:
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.041294612 = queryNorm
            0.27643585 = fieldWeight in 3749, product of:
              2.828427 = tf(freq=8.0), with freq of:
                8.0 = termFreq=8.0
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.0625 = fieldNorm(doc=3749)
      0.25 = coord(2/8)
    
    Abstract
    The book index occupies a special niche in the information retrieval world. Each index is a unique, authored work. Each book is a closed system. The text presented in a book does not change; the material is stable and fixed. Book indexers provide readers with a nonlinear way to access information in a text. Even though closed-system indexing predates the development of the printing press, a book index can be thought of as hypertext.
    Source
    Encyclopedia of library and information sciences. 3rd ed. Ed.: M.J. Bates
  15. Bell, H.K.: History of societies of indexing : part VII: 1992-95 (2000) 0.01
    0.011824571 = product of:
      0.047298282 = sum of:
        0.019324033 = weight(_text_:of in 113) [ClassicSimilarity], result of:
          0.019324033 = score(doc=113,freq=6.0), product of:
            0.06457475 = queryWeight, product of:
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.041294612 = queryNorm
            0.2992506 = fieldWeight in 113, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.078125 = fieldNorm(doc=113)
        0.02797425 = product of:
          0.0559485 = sum of:
            0.0559485 = weight(_text_:22 in 113) [ClassicSimilarity], result of:
              0.0559485 = score(doc=113,freq=2.0), product of:
                0.1446067 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.041294612 = 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.5 = coord(1/2)
      0.25 = coord(2/8)
    
    Abstract
    The development of international relations and technology predominated in indexing through these four years, 1992-95, as reflected in the four societies' international journal, The Indexer.
    Source
    Indexer. 22(2000) no.2, S.81-83
  16. Wright, J.C.: ¬The world of embedded indexing (2000) 0.01
    0.01181427 = product of:
      0.03150472 = sum of:
        0.01711173 = weight(_text_:use in 217) [ClassicSimilarity], result of:
          0.01711173 = score(doc=217,freq=2.0), product of:
            0.12644777 = queryWeight, product of:
              3.0620887 = idf(docFreq=5623, maxDocs=44218)
              0.041294612 = queryNorm
            0.13532647 = fieldWeight in 217, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.0620887 = idf(docFreq=5623, maxDocs=44218)
              0.03125 = fieldNorm(doc=217)
        0.009978888 = weight(_text_:of in 217) [ClassicSimilarity], result of:
          0.009978888 = score(doc=217,freq=10.0), product of:
            0.06457475 = queryWeight, product of:
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.041294612 = queryNorm
            0.15453234 = fieldWeight in 217, product of:
              3.1622777 = tf(freq=10.0), with freq of:
                10.0 = termFreq=10.0
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.03125 = fieldNorm(doc=217)
        0.004414106 = product of:
          0.008828212 = sum of:
            0.008828212 = weight(_text_:on in 217) [ClassicSimilarity], result of:
              0.008828212 = score(doc=217,freq=2.0), product of:
                0.090823986 = queryWeight, product of:
                  2.199415 = idf(docFreq=13325, maxDocs=44218)
                  0.041294612 = 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.5 = coord(1/2)
      0.375 = coord(3/8)
    
    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!
    Imprint
    Phoenix, AZ : American Society of Indexers / Information Today
  17. Connolly, D.A.: ¬The many uses of Email discussion lists (2000) 0.01
    0.010844591 = product of:
      0.043378364 = sum of:
        0.025667597 = weight(_text_:use in 216) [ClassicSimilarity], result of:
          0.025667597 = score(doc=216,freq=2.0), product of:
            0.12644777 = queryWeight, product of:
              3.0620887 = idf(docFreq=5623, maxDocs=44218)
              0.041294612 = queryNorm
            0.20298971 = fieldWeight in 216, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.0620887 = idf(docFreq=5623, maxDocs=44218)
              0.046875 = fieldNorm(doc=216)
        0.017710768 = weight(_text_:of in 216) [ClassicSimilarity], result of:
          0.017710768 = score(doc=216,freq=14.0), product of:
            0.06457475 = queryWeight, product of:
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.041294612 = queryNorm
            0.2742677 = fieldWeight in 216, product of:
              3.7416575 = tf(freq=14.0), with freq of:
                14.0 = termFreq=14.0
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.046875 = fieldNorm(doc=216)
      0.25 = coord(2/8)
    
    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
    Imprint
    Phoenix, AZ : American Society of Indexers / Information Today
  18. Miksa, F.: ¬The DDC Relative Index (2006) 0.01
    0.009413533 = product of:
      0.03765413 = sum of:
        0.023667008 = weight(_text_:of in 5775) [ClassicSimilarity], result of:
          0.023667008 = score(doc=5775,freq=36.0), product of:
            0.06457475 = queryWeight, product of:
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.041294612 = queryNorm
            0.36650562 = fieldWeight in 5775, product of:
              6.0 = tf(freq=36.0), with freq of:
                36.0 = termFreq=36.0
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.0390625 = fieldNorm(doc=5775)
        0.013987125 = product of:
          0.02797425 = sum of:
            0.02797425 = weight(_text_:22 in 5775) [ClassicSimilarity], result of:
              0.02797425 = score(doc=5775,freq=2.0), product of:
                0.1446067 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.041294612 = 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.25 = coord(2/8)
    
    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.
  19. Booth, P.F.: Indexing : the manual of good practice (2001) 0.01
    0.009114673 = product of:
      0.024305796 = sum of:
        0.008349391 = weight(_text_:retrieval in 1968) [ClassicSimilarity], result of:
          0.008349391 = score(doc=1968,freq=2.0), product of:
            0.124912694 = queryWeight, product of:
              3.024915 = idf(docFreq=5836, maxDocs=44218)
              0.041294612 = queryNorm
            0.06684181 = fieldWeight in 1968, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.024915 = idf(docFreq=5836, maxDocs=44218)
              0.015625 = fieldNorm(doc=1968)
        0.008555865 = weight(_text_:use in 1968) [ClassicSimilarity], result of:
          0.008555865 = score(doc=1968,freq=2.0), product of:
            0.12644777 = queryWeight, product of:
              3.0620887 = idf(docFreq=5623, maxDocs=44218)
              0.041294612 = queryNorm
            0.06766324 = fieldWeight in 1968, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.0620887 = idf(docFreq=5623, maxDocs=44218)
              0.015625 = fieldNorm(doc=1968)
        0.0074005406 = weight(_text_:of in 1968) [ClassicSimilarity], result of:
          0.0074005406 = score(doc=1968,freq=22.0), product of:
            0.06457475 = queryWeight, product of:
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.041294612 = queryNorm
            0.11460425 = fieldWeight in 1968, product of:
              4.690416 = tf(freq=22.0), with freq of:
                22.0 = termFreq=22.0
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.015625 = fieldNorm(doc=1968)
      0.375 = coord(3/8)
    
    Abstract
    Indexing is an activity which often goes unnoticed and can be taken for granted by reades. Indexing.- The Manual of Good Practice covers all aspects of whole document indexing of books, serial publications, images and sound materials. The book gives the purpose and principles of indexing, and covers areas such as managing the work, technology and other subject specialisms. The Manual takes the reader through the basic principles of indexing an to expert approaches, and therefore has a broad appeal for both indexers and prospective indexers whether they work freelance or in-house.
    Footnote
    Rez. in: nfd - Information Wissenschaft und Praxis 54(2003) H.7, S.440-442 (R. Fugmann): "Das Buch beginnt mit dem Kapitel "Myths about Indexing" und mit der Nennung von weit verbreiteten Irrtümern über das Indexieren, und zwar vorrangig über das Registermachen. Mit einem einzigen Satz ist die Problematik treffend skizziert, welcher das Buch gewidmet ist: "With the development of electronic documents, it has become possible to store very large amounts of information; but storage is not of much use without the capability to retrieve, to convert, transfer and reuse the information". Kritisiert wird die weit verbreitet anzutreffende Ansicht, das Indexieren sei lediglich eine Sache vom "picking out words from the text or naming objects in images and using those words as index headings". Eine solche Arbeitsweise führt jedoch nicht zu Registern, sondern zu Konkordanzen (d.h. zu alphabetischen Fundstellenlisten für Textwörter) und"... is entirely dependent an the words themselves and is not concerned with the ideas behind them". Das Sammeln von Information ist einfach. Aber die (Wieder-) Auffindbarkeit herzustellen muss gelernt werden, wenn mehr ermöglicht werden soll als lediglich das Wiederfinden von Texten, die man in allen Einzelheiten noch genau in Erinnerung behalten hat (known-item searches, questions of recall), die Details der sprachlichen Ausdrucksweise für die gesuchten Begriffe eingeschlossen. Die Verfasserin beschreibt aus ihrer großen praktischen Erfahrung, welche Schritte hierzu auf der gedanklichen und technischen Ebene unternommen werden müssen. Zu den erstgenannten Schritten rechnet die Abtrennung von Details, welche nicht im Index vertreten sein sollten ("unsought terms"), weil sie mit Sicherheit kein Suchziel darstellen werden und als "false friends" zur Überflutung des Suchenden mit Nebensächlichkeiten führen würden, eine Entscheidung, welche nur mit guter Sachkenntnis gefällt werden kann. All Dasjenige hingegen, was in Gegenwart und Zukunft (!) ein sinnvolles Suchziel darstellen könnte und "sufficiently informative" ist, verdient ein Schlagwort im Register. Man lernt auch durch lehrreiche Beispiele, wodurch ein Textwort unbrauchbar für das Register wird, wenn es dort als (schlechtes) Schlagwort erscheint, herausgelöst aus dem interpretierenden Zusammenhang, in welchen es im Text eingebettet gewesen ist. Auch muss die Vieldeutigkeit bereinigt werden, die fast jedem natursprachigen Wort anhaftet. Sonst wird der Suchende beim Nachschlagen allzu oft in die Irre geführt, und zwar um so öfter, je größer ein diesbezüglich unbereinigter Speicher bereits geworden ist.
    Der Zugang zum Informationsspeicher ist auch von verwandten Begriffen her zu gewährleisten, denn der Suchende lässt sich gern mit seiner Fragestellung zu allgemeineren und vor allem zu spezifischeren Begriffen leiten. Verweisungen der Art "siehe auch" dienen diesem Zweck. Der Zugang ist auch von unterschiedlichen, aber bedeutungsgleichen Ausdrücken mithilfe einer Verweisung von der Art "siehe" zu gewährleisten, denn ein Fragesteller könnte sich mit einem von diesen Synonymen auf die Suche begeben haben und würde dann nicht fündig werden. Auch wird Vieles, wofür ein Suchender sein Schlagwort parat hat, in einem Text nur in wortreicher Umschreibung und paraphrasiert angetroffen ("Terms that may not appear in the text but are likely to be sought by index users"), d.h. praktisch unauffindbar in einer derartig mannigfaltigen Ausdrucksweise. All dies sollte lexikalisch ausgedrückt werden, und zwar in geläufiger Terminologie, denn in dieser Form erfolgt auch die Fragestellung. Hier wird die Grenze zwischen "concept indexing" gegenüber dem bloßen "word indexing" gezogen, welch letzteres sich mit der Präsentation von nicht interpretierten Textwörtern begnügt. Nicht nur ist eine solche Grenze weit verbreitet unbekannt, ihre Existenz wird zuweilen sogar bestritten, obwohl doch ein Wort meistens viele Begriffe ausdrückt und obwohl ein Begriff meistens durch viele verschiedene Wörter und Sätze ausgedrückt wird. Ein Autor kann und muss sich in seinen Texten oft mit Andeutungen begnügen, weil ein Leser oder Zuhörer das Gemeinte schon aus dem Zusammenhang erkennen kann und nicht mit übergroßer Deutlichkeit (spoon feeding) belästigt sein will, was als Unterstellung von Unkenntnis empfunden würde. Für das Retrieval hingegen muss das Gemeinte explizit ausgedrückt werden. In diesem Buch wird deutlich gemacht, was alles an außertextlichem und Hintergrund-Wissen für ein gutes Indexierungsergebnis aufgeboten werden muss, dies auf der Grundlage von sachverständiger und sorgfältiger Interpretation ("The indexer must understand the meaning of a text"). All dies lässt gutes Indexieren nicht nur als professionelle Dienstleistung erscheinen, sondern auch als Kunst. Als Grundlage für all diese Schritte wird ein Thesaurus empfohlen, mit einem gut strukturierten Netzwerk von verwandtschaftlichen Beziehungen und angepasst an den jeweiligen Buchtext. Aber nur selten wird man auf bereits andernorts vorhandene Thesauri zurückgreifen können. Hier wäre ein Hinweis auf einschlägige Literatur zur Thesaurus-Konstruktion nützlich gewesen.
  20. Klement, S.: Open-system versus closed-system indexing : a vital distinction (2002) 0.01
    0.008043981 = product of:
      0.032175925 = sum of:
        0.018933605 = weight(_text_:of in 941) [ClassicSimilarity], result of:
          0.018933605 = score(doc=941,freq=4.0), product of:
            0.06457475 = queryWeight, product of:
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.041294612 = queryNorm
            0.2932045 = fieldWeight in 941, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              1.5637573 = idf(docFreq=25162, maxDocs=44218)
              0.09375 = fieldNorm(doc=941)
        0.013242318 = product of:
          0.026484637 = sum of:
            0.026484637 = weight(_text_:on in 941) [ClassicSimilarity], result of:
              0.026484637 = score(doc=941,freq=2.0), product of:
                0.090823986 = queryWeight, product of:
                  2.199415 = idf(docFreq=13325, maxDocs=44218)
                  0.041294612 = queryNorm
                0.29160398 = fieldWeight in 941, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  2.199415 = idf(docFreq=13325, maxDocs=44218)
                  0.09375 = fieldNorm(doc=941)
          0.5 = coord(1/2)
      0.25 = coord(2/8)
    
    Abstract
    On the difference between indexing of books and of journals