Search (3 results, page 1 of 1)

0.021425933 = product of:
  0.042851865 = sum of:
    0.042851865 = product of:
      0.08570373 = sum of:
        0.08570373 = weight(_text_:i in 5411) [ClassicSimilarity], result of:
          0.08570373 = score(doc=5411,freq=2.0), product of:
            0.17138503 = queryWeight, product of:
              3.7717297 = idf(docFreq=2765, maxDocs=44218)
              0.045439374 = queryNorm
            0.50006545 = fieldWeight in 5411, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.7717297 = idf(docFreq=2765, maxDocs=44218)
              0.09375 = fieldNorm(doc=5411)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

0.0071419775 = product of:
  0.014283955 = sum of:
    0.014283955 = product of:
      0.02856791 = sum of:
        0.02856791 = weight(_text_:i in 6109) [ClassicSimilarity], result of:
          0.02856791 = score(doc=6109,freq=2.0), product of:
            0.17138503 = queryWeight, product of:
              3.7717297 = idf(docFreq=2765, maxDocs=44218)
              0.045439374 = queryNorm
            0.16668847 = fieldWeight in 6109, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.7717297 = idf(docFreq=2765, maxDocs=44218)
              0.03125 = fieldNorm(doc=6109)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

The purpose of this paper is to review the challenges confronting cataloguing as we have known it and to consider how these challenges might be confronted and whether they may be surmounted. The main focus of this paper is on cataloguing rather than the catalogue, although it is obviously difficult to separate one from the other. First of all, what does "cataloguing" mean? For the purposes of this paper I have adopted a broad definition incorporating the following activities: - description of the resource sufficient for purposes of identification and for differentiation from other similar resources - identification and control of access points - identification and control of relationships with other resources - subject analysis of the resource - assignment of subject indexing terms - assignment of classification numbers The challenges facing cataloguing are all too well known. In no particular order, the major challenges are: - Increasing inputs - New kinds of information resource - Competition from other mediation services. - Perception that cataloguing is high cost and offers poor value for money. - Fiscal constraints - Declining workforce This is a daunting list. We have a choice, we could, to paraphrase John Lennon, "Turn off our minds, relax and float down stream", until we retire, take voluntary redundancy, or retrain as marketing consultants; or, we can choose to confront these challenges and consider what they really mean for cataloguing.

0.0035709888 = product of:
  0.0071419775 = sum of:
    0.0071419775 = product of:
      0.014283955 = sum of:
        0.014283955 = weight(_text_:i in 3401) [ClassicSimilarity], result of:
          0.014283955 = score(doc=3401,freq=2.0), product of:
            0.17138503 = queryWeight, product of:
              3.7717297 = idf(docFreq=2765, maxDocs=44218)
              0.045439374 = queryNorm
            0.083344236 = fieldWeight in 3401, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.7717297 = idf(docFreq=2765, maxDocs=44218)
              0.015625 = fieldNorm(doc=3401)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Content

What are these two Beowulf translations "expressions" of? I used the term work above, an even more abstract concept in the FRBR model. In this case, the "work" is Beowulf , that ancient intellectual creation or effort that over time has been expressed in multiple ways, each manifested in several different ways itself, with one or more items in each manifestation. This is a pretty gross oversimplification of FRBR, which also details other relationships: among these entities; between these entities and various persons (such as creators, publishers, and owners); and between these entities and their subjects. It also specifies characteristics, or "attributes," of the different types of entities (such as title, physical media, date, availability, and more.). But it should be enough to grasp the possibilities. Now apply it Imagine that you have a patron who needs a copy of Heaney's translation of Beowulf . She doesn't care who published it or when, only that it's Heaney's translation. What if you (or your patron) could place an interlibrary loan call on that expression, instead of looking through multiple bibliographic records (as of March, OCLC's WorldCat had nine regular print editions) for multiple manifestations and then judging which record is the best bet on which to place a request? Combine that with functionality that lets you specify "not Braille, not large print," and it could save you time. Now imagine a patron in want of a copy, any copy, in English, of Romeo and Juliet. Saving staff time means saving money. Whether or not this actually happens depends upon what the library community decides to do with FRBR. It is not a set of cataloging rules or a system design, but it can influence both. Several library system vendors are working with FRBR ideas; VTLS's current integrated library system product Virtua incorporates FRBR concepts in its design. More vendors may follow. How the Joint Steering Committee for Revision of Anglo-American Cataloging Rules develops the Anglo-American Cataloging Rules (AACR) to incorporate FRBR will necessarily be a strong determinant of how records work in a "FRBR-ized" bibliographic database.