Search (2 results, page 1 of 1)

0.0051332987 = product of:
  0.025666492 = sum of:
    0.025666492 = weight(_text_:information in 1496) [ClassicSimilarity], result of:
      0.025666492 = score(doc=1496,freq=8.0), product of:
        0.08270773 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.047114085 = queryNorm
        0.3103276 = fieldWeight in 1496, product of:
          2.828427 = tf(freq=8.0), with freq of:
            8.0 = termFreq=8.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.0625 = fieldNorm(doc=1496)
  0.2 = coord(1/5)

Abstract

In this article I will look at the changig computing resources required to run a large information retrieval system like the MELVYL system. I will give a historical perspective, examining the aerly days of the MELVYL system and how the system has changed in the last decade. I will also provide some perspective on how new technologies have affected large information retrieval systems and what technologies will be required of such systems in the future, as the demands and requirements of large information retrieval systems continue to mature to meet increasing user needs.

Source

Information technology and libraries. 11(1992), S.168-172

0.0016041556 = product of:
  0.008020778 = sum of:
    0.008020778 = weight(_text_:information in 4898) [ClassicSimilarity], result of:
      0.008020778 = score(doc=4898,freq=2.0), product of:
        0.08270773 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.047114085 = queryNorm
        0.09697737 = fieldWeight in 4898, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.0390625 = fieldNorm(doc=4898)
  0.2 = coord(1/5)

Abstract

This article will examine the Z39.50 Information Retrieval protocol. It will look at some of the history of the protocol, its operation, and some of the major projects that have made use of it. There has been enough written (perhaps too much) about Z39.50 in the last several years so it is not intended to be a tutorial or detailed description of the protocol. The material that will be presented will try and put some context around the discussion. For those readers who are interested in delving into Z39.50 in a more technical manner, references to much of the material that has been written about it over the years will be provided at the end. Finally, the article will conclude with some thoughts on how technology and technological infrastructure have changed in the years since Z39.50 was initially developed and deployed, and where the protocol has so far lived up to its goals, and where it has perhaps failed to meet some of the high expectations that at least some people involved in the Z39.50 community held for it. The article will conclude with some of the author's speculations (and they are really no more than that) of what the future role of Z39.50 is likely to be.