Search (25 results, page 2 of 2)

0.0070123314 = product of:
  0.014024663 = sum of:
    0.014024663 = product of:
      0.028049326 = sum of:
        0.028049326 = weight(_text_:22 in 2672) [ClassicSimilarity], result of:
          0.028049326 = score(doc=2672,freq=2.0), product of:
            0.18124348 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051756795 = queryNorm
            0.15476047 = fieldWeight in 2672, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03125 = fieldNorm(doc=2672)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

22. 2.2009 19:40:38

0.0066615148 = product of:
  0.0133230295 = sum of:
    0.0133230295 = product of:
      0.026646059 = sum of:
        0.026646059 = weight(_text_:cataloging in 1558) [ClassicSimilarity], result of:
          0.026646059 = score(doc=1558,freq=2.0), product of:
            0.20397975 = queryWeight, product of:
              3.9411201 = idf(docFreq=2334, maxDocs=44218)
              0.051756795 = queryNorm
            0.13063091 = fieldWeight in 1558, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.9411201 = idf(docFreq=2334, maxDocs=44218)
              0.0234375 = fieldNorm(doc=1558)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Content

"MOST INTEGRATED library systems, as they are currently configured and used, should be removed from public view. Before I say why, let me be clean that I think the integrated library system serves a very important, albeit limited, role. An integrated library system should serve as a key piece of the infrastructure of a library, handling such tasks as ma terials acquisition, cataloging (including holdings, of course), and circulation. The integrated library system should be a complete and accurate recording of a local library's holdings. It should not be presented to users as the primary system for locating information. It fails badly at that important job. - Lack of content- The central problem of almost any library catalog system is that it typically includes only information about the books and journals held by a parficular library. Most do not provide access to joumal article indexes, web search engines, or even selective web directories like the Librarians' Index to the Internet. If they do offen such access, it is only via links to these services. The library catalog is far from onestop shopping for information. Although we acknowledge that fact to each other, we still treat it as if it were the best place in the universe to begin a search. Most of us give the catalog a place of great prominente an our web pages. But Information for each book is limited to the author, title, and a few subject headings. Seldom can book reviews, jacket summaries, recommendations, or tables of contents be found-or anything at all to help users determine if they want the material. - Lack of coverage - Most catalogs do not allow patrons to discover even all the books that are available to them. If you're lucky, your catalog may cover the collections of those libraries with which you have close ties-such as a regional network. But that leaves out all those items that could be requested via interlibrary loan. As Steve Coffman pointed out in his "Building Earth's Largest Library" article, we must show our users the universe that is open to them, highlight the items most accessible, and provide an estimate of how long it would take to obtain other items. - Inability to increase coverage - Despite some well-meaning attempts to smash everything of interest into the library catalog, the fact remains that most integrated library systems expect MARC records and MARC records only. This means that whatever we want to put into the catalog must be described using MARC and AACR2 (see "Marc Must Die," LJ 10/15/02, p. 26ff.). This is a barrier to dramatically increasing the scope of a catalog system, even if we decided to do it. How would you, for example, use the Open Archives Initiative Harvesting Protocol to crawl the bibliographic records of remote repositories and make them searchable within your library catalog? It can't be dope, and it shouldn't. The library catalog should be a record of a given library's holdings. Period.

0.0061357897 = product of:
  0.012271579 = sum of:
    0.012271579 = product of:
      0.024543159 = sum of:
        0.024543159 = weight(_text_:22 in 1429) [ClassicSimilarity], result of:
          0.024543159 = score(doc=1429,freq=2.0), product of:
            0.18124348 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051756795 = queryNorm
            0.1354154 = fieldWeight in 1429, 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=1429)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

22. 9.1997 19:16:05

0.0061357897 = product of:
  0.012271579 = sum of:
    0.012271579 = product of:
      0.024543159 = sum of:
        0.024543159 = weight(_text_:22 in 2509) [ClassicSimilarity], result of:
          0.024543159 = score(doc=2509,freq=2.0), product of:
            0.18124348 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051756795 = queryNorm
            0.1354154 = fieldWeight in 2509, 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=2509)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Source

Electronic library. 22(2004) no.2, S.112-120

0.0061357897 = product of:
  0.012271579 = sum of:
    0.012271579 = product of:
      0.024543159 = sum of:
        0.024543159 = weight(_text_:22 in 3353) [ClassicSimilarity], result of:
          0.024543159 = score(doc=3353,freq=2.0), product of:
            0.18124348 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051756795 = queryNorm
            0.1354154 = fieldWeight in 3353, 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=3353)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Source

Mitteilungen der Vereinigung Österreichischer Bibliothekarinnen und Bibliothekare. 58(2005) H.1, S.22-37