Search (211 results, page 1 of 11)

0.078236274 = product of:
  0.15647255 = sum of:
    0.15647255 = sum of:
      0.10786875 = weight(_text_:e.g in 2336) [ClassicSimilarity], result of:
        0.10786875 = score(doc=2336,freq=2.0), product of:
          0.23393378 = queryWeight, product of:
            5.2168427 = idf(docFreq=651, maxDocs=44218)
            0.044842023 = queryNorm
          0.4611081 = fieldWeight in 2336, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            5.2168427 = idf(docFreq=651, maxDocs=44218)
            0.0625 = fieldNorm(doc=2336)
      0.0486038 = weight(_text_:22 in 2336) [ClassicSimilarity], result of:
        0.0486038 = score(doc=2336,freq=2.0), product of:
          0.15702912 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.044842023 = queryNorm
          0.30952093 = fieldWeight in 2336, 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=2336)
  0.5 = coord(1/2)

Abstract

Offers advice on avaluating alternative cataloguing sources. The steps should be: identify the possible providers; network for advice; test or sample attractive systems; develop criteria based on library size, type and location (e.g. cost and equipment needs, currency of records, types of materials accessed, customer service and reputation of vendor, impact on staff/time and other library services and ability to share or network information); and evaluate the possible services; and implement the new service

Date

17.10.1995 18:22:54

0.048897676 = product of:
  0.09779535 = sum of:
    0.09779535 = sum of:
      0.06741798 = weight(_text_:e.g in 1903) [ClassicSimilarity], result of:
        0.06741798 = score(doc=1903,freq=2.0), product of:
          0.23393378 = queryWeight, product of:
            5.2168427 = idf(docFreq=651, maxDocs=44218)
            0.044842023 = queryNorm
          0.28819257 = fieldWeight in 1903, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            5.2168427 = idf(docFreq=651, maxDocs=44218)
            0.0390625 = fieldNorm(doc=1903)
      0.030377375 = weight(_text_:22 in 1903) [ClassicSimilarity], result of:
        0.030377375 = score(doc=1903,freq=2.0), product of:
          0.15702912 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.044842023 = queryNorm
          0.19345059 = fieldWeight in 1903, 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=1903)
  0.5 = coord(1/2)

Abstract

Teaching cataloguing requires the instructor to make strategic decisions about how to approach the variety and complexity of the field and to provide an adequate theoretical foundation while preparing students for their entry into the world of practice. Accompanying these challenges are the tactical demands of providing this instruction in a distance education environment. Rather than focusing on ways to support learners in catalogue record production, instructors may use a problem solving and decision making approach to instruction. In this paper, a way to conceptualize a decision making approach that builds on a foundation provided by theories of information navigation is described. This approach, which is called "wayfinding", teaches by having students learn to find their way in the sets of rules that are commonly used. The method focuses on instruction about the structural features of rule sets, providing basic definitions of what each of the "places" in the rule sets contain (e.g., "formatting personal names" in Chapter 22 of AACR2R) and about ways to navigate those structures, enabling students to learn not only about common rules but also about less well known cataloguing practices ("dragons"). It provides both pragmatic and pedagogical benefits and helps develop links between cataloguing practices and their theoretical foundations.

0.038137365 = product of:
  0.07627473 = sum of:
    0.07627473 = product of:
      0.15254946 = sum of:
        0.15254946 = weight(_text_:e.g in 8169) [ClassicSimilarity], result of:
          0.15254946 = score(doc=8169,freq=4.0), product of:
            0.23393378 = queryWeight, product of:
              5.2168427 = idf(docFreq=651, maxDocs=44218)
              0.044842023 = queryNorm
            0.65210533 = fieldWeight in 8169, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              5.2168427 = idf(docFreq=651, maxDocs=44218)
              0.0625 = fieldNorm(doc=8169)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Examines the arguments for and against minimal level cataloguing. The sort of materials that should undergo minimal level cataloguing or those that are popular and will be found e.g. bestsellers and required course reading not for marginally used materials. A useful kind of minimal level cataloguing should be created which matches the kinds of works to which it is applied. e.g. There should be one kind of minimal level cataloguing for standard, trade books not utilized for research purposes

0.034368075 = product of:
  0.06873615 = sum of:
    0.06873615 = product of:
      0.1374723 = sum of:
        0.1374723 = weight(_text_:22 in 4362) [ClassicSimilarity], result of:
          0.1374723 = score(doc=4362,freq=4.0), product of:
            0.15702912 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.044842023 = queryNorm
            0.8754574 = fieldWeight in 4362, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.125 = fieldNorm(doc=4362)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

22. 1.2000 19:22:27

0.026967188 = product of:
  0.053934377 = sum of:
    0.053934377 = product of:
      0.10786875 = sum of:
        0.10786875 = weight(_text_:e.g in 1418) [ClassicSimilarity], result of:
          0.10786875 = score(doc=1418,freq=2.0), product of:
            0.23393378 = queryWeight, product of:
              5.2168427 = idf(docFreq=651, maxDocs=44218)
              0.044842023 = queryNorm
            0.4611081 = fieldWeight in 1418, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              5.2168427 = idf(docFreq=651, maxDocs=44218)
              0.0625 = fieldNorm(doc=1418)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Describes the work of mediaeval librarians such as Paulaus Melissus and looks at current problems in cataloguing bibliographies. One of these is that the material used does not have the precise algorithmic format required by information technology; today's electronic cataloguing methods are merely a translation of the former manual ones e.g. book title keywords, and have similar defects. Analyses the 3 basi features of books i.e. text, text edition and materials used, and criticises traditional indexing methods

0.026967188 = product of:
  0.053934377 = sum of:
    0.053934377 = product of:
      0.10786875 = sum of:
        0.10786875 = weight(_text_:e.g in 432) [ClassicSimilarity], result of:
          0.10786875 = score(doc=432,freq=2.0), product of:
            0.23393378 = queryWeight, product of:
              5.2168427 = idf(docFreq=651, maxDocs=44218)
              0.044842023 = queryNorm
            0.4611081 = fieldWeight in 432, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              5.2168427 = idf(docFreq=651, maxDocs=44218)
              0.0625 = fieldNorm(doc=432)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

0.0243019 = product of:
  0.0486038 = sum of:
    0.0486038 = product of:
      0.0972076 = sum of:
        0.0972076 = weight(_text_:22 in 527) [ClassicSimilarity], result of:
          0.0972076 = score(doc=527,freq=2.0), product of:
            0.15702912 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.044842023 = queryNorm
            0.61904186 = fieldWeight in 527, 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=527)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Source

OCLC systems and services. 9(1993) no.3, S.20-22

0.0243019 = product of:
  0.0486038 = sum of:
    0.0486038 = product of:
      0.0972076 = sum of:
        0.0972076 = weight(_text_:22 in 4397) [ClassicSimilarity], result of:
          0.0972076 = score(doc=4397,freq=2.0), product of:
            0.15702912 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.044842023 = queryNorm
            0.61904186 = fieldWeight in 4397, 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=4397)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Source

Serials librarian. 22(1992), S.371-391

0.023835853 = product of:
  0.047671705 = sum of:
    0.047671705 = product of:
      0.09534341 = sum of:
        0.09534341 = weight(_text_:e.g in 2848) [ClassicSimilarity], result of:
          0.09534341 = score(doc=2848,freq=4.0), product of:
            0.23393378 = queryWeight, product of:
              5.2168427 = idf(docFreq=651, maxDocs=44218)
              0.044842023 = queryNorm
            0.40756583 = fieldWeight in 2848, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              5.2168427 = idf(docFreq=651, maxDocs=44218)
              0.0390625 = fieldNorm(doc=2848)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

In this article we present FLUX-CiM, a novel method for extracting components (e.g., author names, article titles, venues, page numbers) from bibliographic citations. Our method does not rely on patterns encoding specific delimiters used in a particular citation style. This feature yields a high degree of automation and flexibility, and allows FLUX-CiM to extract from citations in any given format. Differently from previous methods that are based on models learned from user-driven training, our method relies on a knowledge base automatically constructed from an existing set of sample metadata records from a given field (e.g., computer science, health sciences, social sciences, etc.). These records are usually available on the Web or other public data repositories. To demonstrate the effectiveness and applicability of our proposed method, we present a series of experiments in which we apply it to extract bibliographic data from citations in articles of different fields. Results of these experiments exhibit precision and recall levels above 94% for all fields, and perfect extraction for the large majority of citations tested. In addition, in a comparison against a state-of-the-art information-extraction method, ours produced superior results without the training phase required by that method. Finally, we present a strategy for using bibliographic data resulting from the extraction process with FLUX-CiM to automatically update and expand the knowledge base of a given domain. We show that this strategy can be used to achieve good extraction results even if only a very small initial sample of bibliographic records is available for building the knowledge base.

0.02359629 = product of:
  0.04719258 = sum of:
    0.04719258 = product of:
      0.09438516 = sum of:
        0.09438516 = weight(_text_:e.g in 2619) [ClassicSimilarity], result of:
          0.09438516 = score(doc=2619,freq=2.0), product of:
            0.23393378 = queryWeight, product of:
              5.2168427 = idf(docFreq=651, maxDocs=44218)
              0.044842023 = queryNorm
            0.40346956 = fieldWeight in 2619, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              5.2168427 = idf(docFreq=651, maxDocs=44218)
              0.0546875 = fieldNorm(doc=2619)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

To investigate which authority data elements are recorded by libraries in the Chinese character cultural sphere (e.g., Japan, Mainland China, Hong Kong, Taiwan, South Korea, and Vietnam), data elements recorded by each library were examined and compared to authority data elements defined in the standard Resource Description and Access (RDA) design. Recommendations were then made to libraries within this cultural sphere to improve and internationally standardize their authority data. In addition, suggestions are provided to modify RDA in an effort to increase compatibility with authority data in the Chinese character cultural sphere.

0.02359629 = product of:
  0.04719258 = sum of:
    0.04719258 = product of:
      0.09438516 = sum of:
        0.09438516 = weight(_text_:e.g in 5127) [ClassicSimilarity], result of:
          0.09438516 = score(doc=5127,freq=2.0), product of:
            0.23393378 = queryWeight, product of:
              5.2168427 = idf(docFreq=651, maxDocs=44218)
              0.044842023 = queryNorm
            0.40346956 = fieldWeight in 5127, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              5.2168427 = idf(docFreq=651, maxDocs=44218)
              0.0546875 = fieldNorm(doc=5127)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

The implementation of RDA poses questions regarding its application on early printed material, e.g., concerning transcription of title information. Cataloging rules used today for early printed books often include a normalization that is misleading, both for libraries and for users. In this article, ideas concerning transcription according to RDA are discussed. These ideas focus on the double purposes of identifying and retrieving an item. For the first purpose, I suggest a transcription of the title, which closely follows the original ("take what you see"), and for the second, a completely normalized variant title.

0.023354271 = product of:
  0.046708543 = sum of:
    0.046708543 = product of:
      0.093417086 = sum of:
        0.093417086 = weight(_text_:e.g in 1183) [ClassicSimilarity], result of:
          0.093417086 = score(doc=1183,freq=6.0), product of:
            0.23393378 = queryWeight, product of:
              5.2168427 = idf(docFreq=651, maxDocs=44218)
              0.044842023 = queryNorm
            0.39933133 = fieldWeight in 1183, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              5.2168427 = idf(docFreq=651, maxDocs=44218)
              0.03125 = fieldNorm(doc=1183)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

IFLA's Functional Requirements for Bibliographic Records (FRBR) lay the foundation for a new generation of cataloging systems that recognize the difference between a particular work (e.g., Moby Dick), diverse expressions of that work (e.g., translations into German, Japanese and other languages), different versions of the same basic text (e.g., the Modern Library Classics vs. Penguin editions), and particular items (a copy of Moby Dick on the shelf). Much work has gone into finding ways to infer FRBR relationships between existing catalog records and modifying catalog interfaces to display those relationships. Relatively little work, however, has gone into exploring the creation of catalog records that are inherently based on the FRBR hierarchy of works, expressions, manifestations, and items. The Perseus Digital Library has created a new catalog that implements such a system for a small collection that includes many works with multiple versions. We have used this catalog to explore some of the implications of hierarchical catalog records for searching and browsing. Current online library catalog interfaces present many problems for searching. One commonly cited failure is the inability to find and collocate all versions of a distinct intellectual work that exist in a collection and the inability to take into account known variations in titles and personal names (Yee 2005). The IFLA Functional Requirements for Bibliographic Records (FRBR) attempts to address some of these failings by introducing the concept of multiple interrelated bibliographic entities (IFLA 1998). In particular, relationships between abstract intellectual works and the various published instances of those works are divided into a four-level hierarchy of works (such as the Aeneid), expressions (Robert Fitzgerald's translation of the Aeneid), manifestations (a particular paperback edition of Robert Fitzgerald's translation of the Aeneid), and items (my copy of a particular paperback edition of Robert Fitzgerald's translation of the Aeneid). In this formulation, each level in the hierarchy "inherits" information from the preceding level. Much of the work on FRBRized catalogs so far has focused on organizing existing records that describe individual physical books. Relatively little work has gone into rethinking what information should be in catalog records, or how the records should relate to each other. It is clear, however, that a more "native" FRBR catalog would include separate records for works, expressions, manifestations, and items. In this way, all information about a work would be centralized in one record. Records for subsequent expressions of that work would add only the information specific to each expression: Samuel Butler's translation of the Iliad does not need to repeat the fact that the work was written by Homer. This approach has certain inherent advantages for collections with many versions of the same works: new publications can be cataloged more quickly, and records can be stored and updated more efficiently.

0.021480048 = product of:
  0.042960096 = sum of:
    0.042960096 = product of:
      0.08592019 = sum of:
        0.08592019 = weight(_text_:22 in 4367) [ClassicSimilarity], result of:
          0.08592019 = score(doc=4367,freq=4.0), product of:
            0.15702912 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.044842023 = queryNorm
            0.54716086 = fieldWeight in 4367, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.078125 = fieldNorm(doc=4367)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

22. 1.2000 19:36:10
22. 1.2000 19:40:40

0.021264162 = product of:
  0.042528324 = sum of:
    0.042528324 = product of:
      0.08505665 = sum of:
        0.08505665 = weight(_text_:22 in 2857) [ClassicSimilarity], result of:
          0.08505665 = score(doc=2857,freq=2.0), product of:
            0.15702912 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.044842023 = queryNorm
            0.5416616 = fieldWeight in 2857, 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=2857)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Source

Cataloging and classification quarterly. 13(1991) no.2, S.3-22

0.021264162 = product of:
  0.042528324 = sum of:
    0.042528324 = product of:
      0.08505665 = sum of:
        0.08505665 = weight(_text_:22 in 2391) [ClassicSimilarity], result of:
          0.08505665 = score(doc=2391,freq=2.0), product of:
            0.15702912 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.044842023 = queryNorm
            0.5416616 = fieldWeight in 2391, 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=2391)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Pages

22 S

0.021264162 = product of:
  0.042528324 = sum of:
    0.042528324 = product of:
      0.08505665 = sum of:
        0.08505665 = weight(_text_:22 in 2900) [ClassicSimilarity], result of:
          0.08505665 = score(doc=2900,freq=2.0), product of:
            0.15702912 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.044842023 = queryNorm
            0.5416616 = fieldWeight in 2900, 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=2900)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

10. 9.2000 17:38:22

0.021264162 = product of:
  0.042528324 = sum of:
    0.042528324 = product of:
      0.08505665 = sum of:
        0.08505665 = weight(_text_:22 in 4594) [ClassicSimilarity], result of:
          0.08505665 = score(doc=4594,freq=2.0), product of:
            0.15702912 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.044842023 = queryNorm
            0.5416616 = fieldWeight in 4594, 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=4594)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

21. 9.1996 16:03:22

0.021264162 = product of:
  0.042528324 = sum of:
    0.042528324 = product of:
      0.08505665 = sum of:
        0.08505665 = weight(_text_:22 in 6339) [ClassicSimilarity], result of:
          0.08505665 = score(doc=6339,freq=2.0), product of:
            0.15702912 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.044842023 = queryNorm
            0.5416616 = fieldWeight in 6339, 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=6339)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

18. 8.2002 17:22:13

0.021264162 = product of:
  0.042528324 = sum of:
    0.042528324 = product of:
      0.08505665 = sum of:
        0.08505665 = weight(_text_:22 in 6838) [ClassicSimilarity], result of:
          0.08505665 = score(doc=6838,freq=2.0), product of:
            0.15702912 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.044842023 = queryNorm
            0.5416616 = fieldWeight in 6838, 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=6838)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Source

Dialog mit Bibliotheken. 13(2001) H.3, S.20-22

0.021264162 = product of:
  0.042528324 = sum of:
    0.042528324 = product of:
      0.08505665 = sum of:
        0.08505665 = weight(_text_:22 in 1757) [ClassicSimilarity], result of:
          0.08505665 = score(doc=1757,freq=2.0), product of:
            0.15702912 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.044842023 = queryNorm
            0.5416616 = fieldWeight in 1757, 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=1757)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

17. 8.2003 15:50:22