Search (80 results, page 4 of 4)

0.0028464803 = product of:
  0.019925361 = sum of:
    0.019925361 = product of:
      0.039850723 = sum of:
        0.039850723 = weight(_text_:22 in 1427) [ClassicSimilarity], result of:
          0.039850723 = score(doc=1427,freq=2.0), product of:
            0.12874968 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.036766402 = queryNorm
            0.30952093 = fieldWeight in 1427, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0625 = fieldNorm(doc=1427)
      0.5 = coord(1/2)
  0.14285715 = coord(1/7)

Abstract

Considers whether, when there is a choice, a back-of-book indexer should use a duplicate entry or a see reference. Guidelines suggest that it is preferable to use the duplicate entry if it would not add to the length or complexity of the index. Studies 1.100 see references in 202 back-of-book indexes and concludes that 22% of the see references should have been replaced by duplicate entries. Failure to select a duplicate entry instead of a see reference occurs most frequently in science and techology books and in indexes with no subheadings

0.0028464803 = product of:
  0.019925361 = sum of:
    0.019925361 = product of:
      0.039850723 = sum of:
        0.039850723 = weight(_text_:22 in 737) [ClassicSimilarity], result of:
          0.039850723 = score(doc=737,freq=2.0), product of:
            0.12874968 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.036766402 = queryNorm
            0.30952093 = fieldWeight in 737, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0625 = fieldNorm(doc=737)
      0.5 = coord(1/2)
  0.14285715 = coord(1/7)

Date

8.12.2007 18:41:22

0.0027618909 = product of:
  0.019333236 = sum of:
    0.019333236 = product of:
      0.03866647 = sum of:
        0.03866647 = weight(_text_:c in 740) [ClassicSimilarity], result of:
          0.03866647 = score(doc=740,freq=2.0), product of:
            0.12682222 = queryWeight, product of:
              3.4494052 = idf(docFreq=3817, maxDocs=44218)
              0.036766402 = queryNorm
            0.3048872 = fieldWeight in 740, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.4494052 = idf(docFreq=3817, maxDocs=44218)
              0.0625 = fieldNorm(doc=740)
      0.5 = coord(1/2)
  0.14285715 = coord(1/7)

0.0024906702 = product of:
  0.01743469 = sum of:
    0.01743469 = product of:
      0.03486938 = sum of:
        0.03486938 = weight(_text_:22 in 7288) [ClassicSimilarity], result of:
          0.03486938 = score(doc=7288,freq=2.0), product of:
            0.12874968 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.036766402 = queryNorm
            0.2708308 = fieldWeight in 7288, 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=7288)
      0.5 = coord(1/2)
  0.14285715 = coord(1/7)

Footnote

Rez. in: JASIS 44(1993) no.2, S.119-121 (B.H. Weinberg); International cataloguing and bibliographic control 22(1993) no.2, S.34 (E. Svenonius); Information processing and management 29(1993) no.4, S.528-531 (L.L.Hill)

0.0024906702 = product of:
  0.01743469 = sum of:
    0.01743469 = product of:
      0.03486938 = sum of:
        0.03486938 = weight(_text_:22 in 4640) [ClassicSimilarity], result of:
          0.03486938 = score(doc=4640,freq=2.0), product of:
            0.12874968 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.036766402 = queryNorm
            0.2708308 = fieldWeight in 4640, 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=4640)
      0.5 = coord(1/2)
  0.14285715 = coord(1/7)

Date

9. 4.2000 17:22:00

0.0024906702 = product of:
  0.01743469 = sum of:
    0.01743469 = product of:
      0.03486938 = sum of:
        0.03486938 = weight(_text_:22 in 749) [ClassicSimilarity], result of:
          0.03486938 = score(doc=749,freq=2.0), product of:
            0.12874968 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.036766402 = 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.14285715 = coord(1/7)

Date

8.12.2007 19:25:22

0.0024888192 = product of:
  0.017421734 = sum of:
    0.017421734 = weight(_text_:u in 217) [ClassicSimilarity], result of:
      0.017421734 = score(doc=217,freq=2.0), product of:
        0.120389536 = queryWeight, product of:
          3.2744443 = idf(docFreq=4547, maxDocs=44218)
          0.036766402 = queryNorm
        0.14471136 = fieldWeight in 217, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2744443 = idf(docFreq=4547, maxDocs=44218)
          0.03125 = fieldNorm(doc=217)
  0.14285715 = coord(1/7)

Issue

Beyond book indexing: how to get started in Web indexing, embedded indexing and other computer-based media. Ed. by D. Brenner u. M. Rowland.

0.0024888192 = product of:
  0.017421734 = sum of:
    0.017421734 = weight(_text_:u in 223) [ClassicSimilarity], result of:
      0.017421734 = score(doc=223,freq=2.0), product of:
        0.120389536 = queryWeight, product of:
          3.2744443 = idf(docFreq=4547, maxDocs=44218)
          0.036766402 = queryNorm
        0.14471136 = fieldWeight in 223, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2744443 = idf(docFreq=4547, maxDocs=44218)
          0.03125 = fieldNorm(doc=223)
  0.14285715 = coord(1/7)

Issue

Beyond book indexing: how to get started in Web indexing, embedded indexing and other computer-based media. Ed. by D. Brenner u. M. Rowland.

0.0024888192 = product of:
  0.017421734 = sum of:
    0.017421734 = weight(_text_:u in 226) [ClassicSimilarity], result of:
      0.017421734 = score(doc=226,freq=2.0), product of:
        0.120389536 = queryWeight, product of:
          3.2744443 = idf(docFreq=4547, maxDocs=44218)
          0.036766402 = queryNorm
        0.14471136 = fieldWeight in 226, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2744443 = idf(docFreq=4547, maxDocs=44218)
          0.03125 = fieldNorm(doc=226)
  0.14285715 = coord(1/7)

Issue

Beyond book indexing: how to get started in Web indexing, embedded indexing and other computer-based media. Ed. by D. Brenner u. M. Rowland.

0.0024888192 = product of:
  0.017421734 = sum of:
    0.017421734 = weight(_text_:u in 2915) [ClassicSimilarity], result of:
      0.017421734 = score(doc=2915,freq=2.0), product of:
        0.120389536 = queryWeight, product of:
          3.2744443 = idf(docFreq=4547, maxDocs=44218)
          0.036766402 = queryNorm
        0.14471136 = fieldWeight in 2915, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2744443 = idf(docFreq=4547, maxDocs=44218)
          0.03125 = fieldNorm(doc=2915)
  0.14285715 = coord(1/7)

Theme

Grundlagen u. Einführungen: Allgemeine Literatur

0.0024166545 = product of:
  0.01691658 = sum of:
    0.01691658 = product of:
      0.03383316 = sum of:
        0.03383316 = weight(_text_:c in 7920) [ClassicSimilarity], result of:
          0.03383316 = score(doc=7920,freq=2.0), product of:
            0.12682222 = queryWeight, product of:
              3.4494052 = idf(docFreq=3817, maxDocs=44218)
              0.036766402 = queryNorm
            0.2667763 = fieldWeight in 7920, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.4494052 = idf(docFreq=3817, maxDocs=44218)
              0.0546875 = fieldNorm(doc=7920)
      0.5 = coord(1/2)
  0.14285715 = coord(1/7)

0.0024166545 = product of:
  0.01691658 = sum of:
    0.01691658 = product of:
      0.03383316 = sum of:
        0.03383316 = weight(_text_:c in 8500) [ClassicSimilarity], result of:
          0.03383316 = score(doc=8500,freq=2.0), product of:
            0.12682222 = queryWeight, product of:
              3.4494052 = idf(docFreq=3817, maxDocs=44218)
              0.036766402 = queryNorm
            0.2667763 = fieldWeight in 8500, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.4494052 = idf(docFreq=3817, maxDocs=44218)
              0.0546875 = fieldNorm(doc=8500)
      0.5 = coord(1/2)
  0.14285715 = coord(1/7)

0.0024166545 = product of:
  0.01691658 = sum of:
    0.01691658 = product of:
      0.03383316 = sum of:
        0.03383316 = weight(_text_:c in 949) [ClassicSimilarity], result of:
          0.03383316 = score(doc=949,freq=2.0), product of:
            0.12682222 = queryWeight, product of:
              3.4494052 = idf(docFreq=3817, maxDocs=44218)
              0.036766402 = queryNorm
            0.2667763 = fieldWeight in 949, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.4494052 = idf(docFreq=3817, maxDocs=44218)
              0.0546875 = fieldNorm(doc=949)
      0.5 = coord(1/2)
  0.14285715 = coord(1/7)

0.0024166545 = product of:
  0.01691658 = sum of:
    0.01691658 = product of:
      0.03383316 = sum of:
        0.03383316 = weight(_text_:c in 3905) [ClassicSimilarity], result of:
          0.03383316 = score(doc=3905,freq=2.0), product of:
            0.12682222 = queryWeight, product of:
              3.4494052 = idf(docFreq=3817, maxDocs=44218)
              0.036766402 = queryNorm
            0.2667763 = fieldWeight in 3905, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.4494052 = idf(docFreq=3817, maxDocs=44218)
              0.0546875 = fieldNorm(doc=3905)
      0.5 = coord(1/2)
  0.14285715 = coord(1/7)

0.0017790502 = product of:
  0.012453351 = sum of:
    0.012453351 = product of:
      0.024906702 = sum of:
        0.024906702 = weight(_text_:22 in 5775) [ClassicSimilarity], result of:
          0.024906702 = score(doc=5775,freq=2.0), product of:
            0.12874968 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.036766402 = 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.14285715 = coord(1/7)

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.0017261818 = product of:
  0.012083272 = sum of:
    0.012083272 = product of:
      0.024166545 = sum of:
        0.024166545 = weight(_text_:c in 742) [ClassicSimilarity], result of:
          0.024166545 = score(doc=742,freq=2.0), product of:
            0.12682222 = queryWeight, product of:
              3.4494052 = idf(docFreq=3817, maxDocs=44218)
              0.036766402 = queryNorm
            0.1905545 = fieldWeight in 742, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.4494052 = idf(docFreq=3817, maxDocs=44218)
              0.0390625 = fieldNorm(doc=742)
      0.5 = coord(1/2)
  0.14285715 = coord(1/7)

0.0013809454 = product of:
  0.009666618 = sum of:
    0.009666618 = product of:
      0.019333236 = sum of:
        0.019333236 = weight(_text_:c in 72) [ClassicSimilarity], result of:
          0.019333236 = score(doc=72,freq=2.0), product of:
            0.12682222 = queryWeight, product of:
              3.4494052 = idf(docFreq=3817, maxDocs=44218)
              0.036766402 = queryNorm
            0.1524436 = fieldWeight in 72, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.4494052 = idf(docFreq=3817, maxDocs=44218)
              0.03125 = fieldNorm(doc=72)
      0.5 = coord(1/2)
  0.14285715 = coord(1/7)

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.0012453351 = product of:
  0.008717345 = sum of:
    0.008717345 = product of:
      0.01743469 = sum of:
        0.01743469 = weight(_text_:22 in 1502) [ClassicSimilarity], result of:
          0.01743469 = score(doc=1502,freq=2.0), product of:
            0.12874968 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.036766402 = 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.14285715 = coord(1/7)

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.0012444096 = product of:
  0.008710867 = sum of:
    0.008710867 = weight(_text_:u in 1968) [ClassicSimilarity], result of:
      0.008710867 = score(doc=1968,freq=2.0), product of:
        0.120389536 = queryWeight, product of:
          3.2744443 = idf(docFreq=4547, maxDocs=44218)
          0.036766402 = queryNorm
        0.07235568 = fieldWeight in 1968, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2744443 = idf(docFreq=4547, maxDocs=44218)
          0.015625 = fieldNorm(doc=1968)
  0.14285715 = coord(1/7)

Theme

Grundlagen u. Einführungen: Allgemeine Literatur

8.630909E-4 = product of:
  0.006041636 = sum of:
    0.006041636 = product of:
      0.012083272 = sum of:
        0.012083272 = weight(_text_:c in 2294) [ClassicSimilarity], result of:
          0.012083272 = score(doc=2294,freq=2.0), product of:
            0.12682222 = queryWeight, product of:
              3.4494052 = idf(docFreq=3817, maxDocs=44218)
              0.036766402 = queryNorm
            0.09527725 = fieldWeight in 2294, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.4494052 = idf(docFreq=3817, maxDocs=44218)
              0.01953125 = fieldNorm(doc=2294)
      0.5 = coord(1/2)
  0.14285715 = coord(1/7)

Footnote

Rez. in: Knowledge organization 30(2003) no.2, S.115-116 (C. Jacobs): "This collection of articles by indexing practitioners, software designers and vendors is divided into five sections: Dedicated Software, Embedded Software, Online and Web Indexing Software, Database and Image Software, and Voice-activated, Automatic, and Machine-aided Software. This diversity is its strength. Part 1 is introduced by two chapters an choosing dedicated software, highlighting the issues involved and providing tips an evaluating requirements. The second chapter includes a fourteen page chart that analyzes the attributes of Authex Plus, three versions of CINDEX 1.5, MACREX 7, two versions of SKY Index (5.1 and 6.0) and wINDEX. The lasting value in this chart is its utility in making the prospective user aware of the various attributes/capabilities that are possible and that should be considered. The following chapters consist of 16 testimonials for these software packages, completed by a final chapter an specialized/customized software. The point is made that if a particular software function could increase your efficiency, it can probably be created. The chapters in Part 2, Embedded Software, go into a great deal more detail about how the programs work, and are less reviews than illustrations of functionality. Perhaps this is because they are not really stand-alones, but are functions within, or add-ons used with larger word processing or publishing programs. The software considered are Microsoft Word, FrameMaker, PageMaker, IndexTension 3.1.5 that is used with QuarkXPress, and Index Tools Professional and IXgen that are used with FrameMaker. The advantages and disadvantages of embedded indexing are made very clear, but the actual illustrations are difficult to follow if one has not worked at all with embedded software. Nonetheless, the section is valuable as it highlights issues and provides pointers an solutions to embedded indexing problems.