Search (4 results, page 1 of 1)

0.010066988 = product of:
  0.020133976 = sum of:
    0.00907636 = weight(_text_:research in 3401) [ClassicSimilarity], result of:
      0.00907636 = score(doc=3401,freq=2.0), product of:
        0.14397179 = queryWeight, product of:
          2.8529835 = idf(docFreq=6931, maxDocs=44218)
          0.050463587 = queryNorm
        0.063042626 = fieldWeight in 3401, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.8529835 = idf(docFreq=6931, maxDocs=44218)
          0.015625 = fieldNorm(doc=3401)
    0.011057617 = product of:
      0.022115234 = sum of:
        0.022115234 = weight(_text_:network in 3401) [ClassicSimilarity], result of:
          0.022115234 = score(doc=3401,freq=2.0), product of:
            0.22473325 = queryWeight, product of:
              4.4533744 = idf(docFreq=1398, maxDocs=44218)
              0.050463587 = queryNorm
            0.0984066 = fieldWeight in 3401, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.4533744 = idf(docFreq=1398, maxDocs=44218)
              0.015625 = fieldNorm(doc=3401)
      0.5 = coord(1/2)
  0.5 = coord(2/4)

Content

National FRBR experiments The larger the bibliographic database, the greater the effect of "FRBR-like" design in reducing the appearance of duplicate records. LC, RLG, and OCLC, all influenced by FRBR, are experimenting with the redesign of their databases. LC's Network Development and MARC Standards Office has posted at its web site the results of some of its investigations into FRBR and MARC, including possible display options for bibliographic information. The design of RLG's public catalog, RedLightGreen, has been described as "FRBR-ish" by Merrilee Proffitt, RLG's program officer. If you try a search for a prolific author or much-published title in RedLightGreen, you'll probably find that the display of search results is much different than what you would expect. OCLC Research has developed a prototype "frbrized" database for fiction, OCLC FictionFinder. Try a title search for a classic title like Romeo and Juliet and observe that OCLC includes, in the initial display of results (described as "works"), a graphic indicator (stars, ranging from one to five). These show in rough terms how many libraries own the work-Romeo and Juliet clearly gets a five. Indicators like this are something resource sharing staff can consider an "ILL quality rating." If you're intrigued by FRBR's possibilities and what they could mean to resource sharing workflow, start talking. Now is the time to connect with colleagues, your local and/or consortial system vendor, RLG, OCLC, and your professional organizations. Have input into how systems develop in the FRBR world."

0.009626932 = product of:
  0.03850773 = sum of:
    0.03850773 = weight(_text_:research in 2433) [ClassicSimilarity], result of:
      0.03850773 = score(doc=2433,freq=4.0), product of:
        0.14397179 = queryWeight, product of:
          2.8529835 = idf(docFreq=6931, maxDocs=44218)
          0.050463587 = queryNorm
        0.2674672 = fieldWeight in 2433, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          2.8529835 = idf(docFreq=6931, maxDocs=44218)
          0.046875 = fieldNorm(doc=2433)
  0.25 = coord(1/4)

Footnote

Vgl. auch: http://www.oclc.org/research/publications/archive/2002/oneill_frbr22.pdf.

Source

http://www.oclc.org/research/activities/frbr/clinker.html

0.0068072695 = product of:
  0.027229078 = sum of:
    0.027229078 = weight(_text_:research in 1086) [ClassicSimilarity], result of:
      0.027229078 = score(doc=1086,freq=2.0), product of:
        0.14397179 = queryWeight, product of:
          2.8529835 = idf(docFreq=6931, maxDocs=44218)
          0.050463587 = queryNorm
        0.18912788 = fieldWeight in 1086, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.8529835 = idf(docFreq=6931, maxDocs=44218)
          0.046875 = fieldNorm(doc=1086)
  0.25 = coord(1/4)

Abstract

This thought piece on the future of cataloging is long on musings and short on predictions. But that isn't to denigrate it, only to clarify it's role given the possible connotations of the title. Rather than coming up with solutions or predictions, Marcum ponders the proper role of cataloging in a Google age. Marcum cites the Google project to digitize much or all of the contents of a selected set of major research libraries as evidence that the world of cataloging is changing dramatically, and she briefly identifies ways in which the Library of Congress is responding to this new environment. But, Marcum cautions, "the future of cataloging is not something that the Library of Congress, or even the small library group with which we will meet, can or expects to resolve alone." She then poses some specific questions that should be considered, including how we can massively change our current MARC/AACR2 system without creating chaos

0.00453818 = product of:
  0.01815272 = sum of:
    0.01815272 = weight(_text_:research in 2429) [ClassicSimilarity], result of:
      0.01815272 = score(doc=2429,freq=2.0), product of:
        0.14397179 = queryWeight, product of:
          2.8529835 = idf(docFreq=6931, maxDocs=44218)
          0.050463587 = queryNorm
        0.12608525 = fieldWeight in 2429, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.8529835 = idf(docFreq=6931, maxDocs=44218)
          0.03125 = fieldNorm(doc=2429)
  0.25 = coord(1/4)

Abstract

Our catalog should not be called a FRBR catalog perhaps, but instead a "FRBR Inspired catalog." As such our main goal has been "practical findability," we are seeking to support the four identified user tasks of the FRBR model, or to "Search, Identify, Select, and Obtain," rather than to create a FRBR catalog, per se. By encoding as much information as possible in the MODS and MADS records we have created, we believe that useful searching will be supported, that by using unique identifiers for works and authors users will be able to identify that the entity they have located is the desired one, that by encoding expression level information (such as the language of the work, the translator, etc) users will be able to select which expression of a work they are interested in, and that by supplying links to different online manifestations that users will be able to obtain access to a digital copy of a work. This white paper will discuss previous and current efforts by the Perseus Project in creating a FRBRized catalog, including the cataloging workflow, lessons learned during the process and will also seek to place this work in the larger context of research regarding FRBR, cataloging, Library 2.0 and the Semantic Web, and the growing importance of the FRBR model in the face of growing million book digital libraries.