Search (58 results, page 1 of 3)

0.08370372 = product of:
  0.23018521 = sum of:
    0.0130612515 = weight(_text_:of in 3774) [ClassicSimilarity], result of:
      0.0130612515 = score(doc=3774,freq=8.0), product of:
        0.053998582 = queryWeight, product of:
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.034531306 = queryNorm
        0.24188137 = fieldWeight in 3774, product of:
          2.828427 = tf(freq=8.0), with freq of:
            8.0 = termFreq=8.0
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.0546875 = fieldNorm(doc=3774)
    0.07539768 = weight(_text_:technological in 3774) [ClassicSimilarity], result of:
      0.07539768 = score(doc=3774,freq=2.0), product of:
        0.18347798 = queryWeight, product of:
          5.3133807 = idf(docFreq=591, maxDocs=44218)
          0.034531306 = queryNorm
        0.41093582 = fieldWeight in 3774, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.3133807 = idf(docFreq=591, maxDocs=44218)
          0.0546875 = fieldNorm(doc=3774)
    0.12345601 = weight(_text_:innovations in 3774) [ClassicSimilarity], result of:
      0.12345601 = score(doc=3774,freq=2.0), product of:
        0.23478 = queryWeight, product of:
          6.7990475 = idf(docFreq=133, maxDocs=44218)
          0.034531306 = queryNorm
        0.525837 = fieldWeight in 3774, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          6.7990475 = idf(docFreq=133, maxDocs=44218)
          0.0546875 = fieldNorm(doc=3774)
    0.01827029 = weight(_text_:on in 3774) [ClassicSimilarity], result of:
      0.01827029 = score(doc=3774,freq=4.0), product of:
        0.07594867 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.034531306 = queryNorm
        0.24056101 = fieldWeight in 3774, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.0546875 = fieldNorm(doc=3774)
  0.36363637 = coord(4/11)

Abstract

Technological and regulatory developments are opening the door for competition and new services in the local loop. The reunification of Germany created an opprotunity for Deutsche Telekom to install fibre in the loop on a large scale in eastern Germany. Deutsche Telekom's strategy consists of 4 steps: fibre in the loop is seen as a process innovation. New broadband services - product innovations - can be based on the process innovation. Only a sufficient number of installations will enable the industry to invest in new products. Besides the local networks equipped with fibre, there is an overlay network for the rapid delivery of fibre access for business customers. The experience gained in eastern Germany will be transferred to western Germany when tranforming its existing network structure

0.022270055 = product of:
  0.081656866 = sum of:
    0.014751178 = weight(_text_:of in 4898) [ClassicSimilarity], result of:
      0.014751178 = score(doc=4898,freq=20.0), product of:
        0.053998582 = queryWeight, product of:
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.034531306 = queryNorm
        0.27317715 = fieldWeight in 4898, product of:
          4.472136 = tf(freq=20.0), with freq of:
            20.0 = termFreq=20.0
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.0390625 = fieldNorm(doc=4898)
    0.053855482 = weight(_text_:technological in 4898) [ClassicSimilarity], result of:
      0.053855482 = score(doc=4898,freq=2.0), product of:
        0.18347798 = queryWeight, product of:
          5.3133807 = idf(docFreq=591, maxDocs=44218)
          0.034531306 = queryNorm
        0.29352558 = fieldWeight in 4898, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.3133807 = idf(docFreq=591, maxDocs=44218)
          0.0390625 = fieldNorm(doc=4898)
    0.013050207 = weight(_text_:on in 4898) [ClassicSimilarity], result of:
      0.013050207 = score(doc=4898,freq=4.0), product of:
        0.07594867 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.034531306 = queryNorm
        0.1718293 = fieldWeight in 4898, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.0390625 = fieldNorm(doc=4898)
  0.27272728 = coord(3/11)

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.

0.019956816 = product of:
  0.07317499 = sum of:
    0.053516448 = weight(_text_:effect in 5155) [ClassicSimilarity], result of:
      0.053516448 = score(doc=5155,freq=2.0), product of:
        0.18289955 = queryWeight, product of:
          5.29663 = idf(docFreq=601, maxDocs=44218)
          0.034531306 = queryNorm
        0.2926002 = fieldWeight in 5155, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.29663 = idf(docFreq=601, maxDocs=44218)
          0.0390625 = fieldNorm(doc=5155)
    0.010430659 = weight(_text_:of in 5155) [ClassicSimilarity], result of:
      0.010430659 = score(doc=5155,freq=10.0), product of:
        0.053998582 = queryWeight, product of:
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.034531306 = queryNorm
        0.19316542 = fieldWeight in 5155, product of:
          3.1622777 = tf(freq=10.0), with freq of:
            10.0 = termFreq=10.0
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.0390625 = fieldNorm(doc=5155)
    0.009227889 = weight(_text_:on in 5155) [ClassicSimilarity], result of:
      0.009227889 = score(doc=5155,freq=2.0), product of:
        0.07594867 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.034531306 = queryNorm
        0.121501654 = fieldWeight in 5155, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.0390625 = fieldNorm(doc=5155)
  0.27272728 = coord(3/11)

Abstract

Hinich and Molyneux review the literature of internet measurement and note three results consistently to be found in network traffic studies. These are "self-similarity," "long-range dependence," by which is meant that events in one time are correlated with events in a previous time and remain so through longer time periods than expected, and "heavy tails" by which they mean many small connections with low byte counts and a few long connections with large byte counts. The literature also suggests that conventional time series analysis is not helpful for network analysis. Using a single day's traffic at the Berkeley National Labs web server, cumulated TCP flows were collected, log transforms were used with the adding of .01 to all values allowing log transforms of the zero values, and providing a distribution that overcomes the heavy tail problem. However, Hinich's bicorrelation test for nonlinearity using overlapping moving windows found strong evidence of nonlinear structures. Time series analysis assumes linear systems theory and thus additivity and scalability. Spectral analysis should provide large peaks at the lowest frequencies if long range dependence is present since the power spectrum would go to infinity if the frequency goes to zero. This does not occur and so long range dependence must be questioned, at least until it is determined what effect other OSI layers may have on the TCP data.

Source

Journal of the American Society for Information Science and technology. 54(2003) no.2, S.161-168

0.018701423 = product of:
  0.10285783 = sum of:
    0.016689055 = weight(_text_:of in 3103) [ClassicSimilarity], result of:
      0.016689055 = score(doc=3103,freq=10.0), product of:
        0.053998582 = queryWeight, product of:
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.034531306 = queryNorm
        0.3090647 = fieldWeight in 3103, product of:
          3.1622777 = tf(freq=10.0), with freq of:
            10.0 = termFreq=10.0
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.0625 = fieldNorm(doc=3103)
    0.08616877 = weight(_text_:technological in 3103) [ClassicSimilarity], result of:
      0.08616877 = score(doc=3103,freq=2.0), product of:
        0.18347798 = queryWeight, product of:
          5.3133807 = idf(docFreq=591, maxDocs=44218)
          0.034531306 = queryNorm
        0.46964094 = fieldWeight in 3103, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.3133807 = idf(docFreq=591, maxDocs=44218)
          0.0625 = fieldNorm(doc=3103)
  0.18181819 = coord(2/11)

Abstract

Describes the design of a front end enabling users to access a library's OPAC from locations remote from the physical libraries themselves. Current technological developments are renewed with reference to 10 years' experience of remote public access at the National Technical Library, Denmark

Source

OPACs and the user: Proc. of the 3rd Anglo-Nordic seminar, Apr. 90

0.008210947 = product of:
  0.045160204 = sum of:
    0.013193856 = weight(_text_:of in 799) [ClassicSimilarity], result of:
      0.013193856 = score(doc=799,freq=4.0), product of:
        0.053998582 = queryWeight, product of:
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.034531306 = queryNorm
        0.24433708 = fieldWeight in 799, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.078125 = fieldNorm(doc=799)
    0.031966347 = weight(_text_:on in 799) [ClassicSimilarity], result of:
      0.031966347 = score(doc=799,freq=6.0), product of:
        0.07594867 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.034531306 = queryNorm
        0.4208941 = fieldWeight in 799, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.078125 = fieldNorm(doc=799)
  0.18181819 = coord(2/11)

Editor

University of Sussex Library

Issue

A list of interactive library catalogues on Janet ...3 April 1991.

LCSH

Catalogs, On / line

Subject

Catalogs, On / line

0.0079206 = product of:
  0.043563295 = sum of:
    0.025293006 = weight(_text_:of in 6038) [ClassicSimilarity], result of:
      0.025293006 = score(doc=6038,freq=30.0), product of:
        0.053998582 = queryWeight, product of:
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.034531306 = queryNorm
        0.46840128 = fieldWeight in 6038, product of:
          5.477226 = tf(freq=30.0), with freq of:
            30.0 = termFreq=30.0
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.0546875 = fieldNorm(doc=6038)
    0.01827029 = weight(_text_:on in 6038) [ClassicSimilarity], result of:
      0.01827029 = score(doc=6038,freq=4.0), product of:
        0.07594867 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.034531306 = queryNorm
        0.24056101 = fieldWeight in 6038, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.0546875 = fieldNorm(doc=6038)
  0.18181819 = coord(2/11)

Abstract

The focus of this study is the search behavior of remote users of the University of California MELVYL Library System, an OPAC. Transaction logs from randomly selected remote user search sessions are analyzed. Descriptive data on the number and type of searches, choice of search mode and database, number of retrievals, number and type of errors, and use of system HELP facilities are presented. The search data have been cross-tabulated with demographic data on the same group of remote users, collected through an online survey conducted by the authors. Effectiveness of system usage is discussed. A case mode is made for the desirability of additional heuristics in the catalog portion of the system

0.0075523397 = product of:
  0.041537866 = sum of:
    0.01939093 = weight(_text_:of in 3099) [ClassicSimilarity], result of:
      0.01939093 = score(doc=3099,freq=6.0), product of:
        0.053998582 = queryWeight, product of:
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.034531306 = queryNorm
        0.3591007 = fieldWeight in 3099, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.09375 = fieldNorm(doc=3099)
    0.022146935 = weight(_text_:on in 3099) [ClassicSimilarity], result of:
      0.022146935 = score(doc=3099,freq=2.0), product of:
        0.07594867 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.034531306 = queryNorm
        0.29160398 = fieldWeight in 3099, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.09375 = fieldNorm(doc=3099)
  0.18181819 = coord(2/11)

Abstract

Reviews the pros and cons of providing library clients with access to remote OPACs and comments on the use of electronic communications as an alternative to the traditional conference

0.0070782644 = product of:
  0.038930453 = sum of:
    0.020567184 = weight(_text_:of in 1262) [ClassicSimilarity], result of:
      0.020567184 = score(doc=1262,freq=108.0), product of:
        0.053998582 = queryWeight, product of:
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.034531306 = queryNorm
        0.38088378 = fieldWeight in 1262, product of:
          10.392304 = tf(freq=108.0), with freq of:
            108.0 = termFreq=108.0
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.0234375 = fieldNorm(doc=1262)
    0.018363269 = weight(_text_:on in 1262) [ClassicSimilarity], result of:
      0.018363269 = score(doc=1262,freq=22.0), product of:
        0.07594867 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.034531306 = queryNorm
        0.24178526 = fieldWeight in 1262, product of:
          4.690416 = tf(freq=22.0), with freq of:
            22.0 = termFreq=22.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.0234375 = fieldNorm(doc=1262)
  0.18181819 = coord(2/11)

Abstract

The Z39.50 standard for information retrieval is important from a number of perspectives. While still not widely known within the computer networking community, it is a mature standard that represents the culmination of two decades of thinking and debate about how information retrieval functions can be modeled, standardized, and implemented in a distributed systems environment. And - importantly -- it has been tested through substantial deployment experience. Z39.50 is one of the few examples we have to date of a protocol that actually goes beyond codifying mechanism and moves into the area of standardizing shared semantic knowledge. The extent to which this should be a goal of the protocol has been an ongoing source of controversy and tension within the developer community, and differing views on this issue can be seen both in the standard itself and the way that it is used in practice. Given the growing emphasis on issues such as "semantic interoperability" as part of the research agenda for digital libraries (see Clifford A. Lynch and Hector Garcia-Molina. Interoperability, Scaling, and the Digital Libraries Research Agenda, Report on the May 18-19, 1995 IITA Libraries Workshop, <http://www- diglib.stanford.edu/diglib/pub/reports/iita-dlw/main.html>), the insights gained by the Z39.50 community into the complex interactions among various definitions of semantics and interoperability are particularly relevant. The development process for the Z39.50 standard is also of interest in its own right. Its history, dating back to the 1970s, spans a period that saw the eclipse of formal standards-making agencies by groups such as the Internet Engineering Task Force (IETF) and informal standards development consortia. Moreover, in order to achieve meaningful implementation, Z39.50 had to move beyond its origins in the OSI debacle of the 1980s. Z39.50 has also been, to some extent, a victim of its own success -- or at least promise. Recent versions of the standard are highly extensible, and the consensus process of standards development has made it hospitable to an ever-growing set of new communities and requirements. As this process of extension has proceeded, it has become ever less clear what the appropriate scope and boundaries of the protocol should be, and what expectations one should have of practical interoperability among implementations of the standard. Z39.50 thus offers an excellent case study of the problems involved in managing the evolution of a standard over time. It may well offer useful lessons for the future of other standards such as HTTP and HTML, which seem to be facing some of the same issues.
This paper, which will appear in two parts, starting with this issue of D-Lib, looks at several strategic issues surrounding Z39.50. After a relatively brief overview of the function and history of the protocol, I will examine some of the competing visions of the protocol's role, with emphasis on issues of interoperability and the incorporation of semantics. The second installment of the paper will look at questions related to the management of the standard and the standards development process, with emphasis on the scope of the protocol and how that relates back again to interoperability questions. The paper concludes with a discussion of the adoption and deployment of the standard, its relationship to other standards, and some speculations on future directions for the protocol. This paper is not intended to be a tutorial on the details of how current or past versions of Z39.50 work. These technical details are covered not only in the standard itself (which can admittedly be rather difficult reading) but also in an array of tutorial and review papers (see <http://lcweb.loc.gov/z3950/agency> for bibliographies and pointers to on-line information on Z39.50). Instead, the paper's focus is on how and why Z39.50 developed the way it did, and the conceptual debates that have influenced its evolution and use. While a detailed technical knowledge of the operation of Z39.50 is certainly helpful, it should not be necessary in order to follow most of the material here. Some disclaimers are in order. I have been actively involved in the development of Z39.50 since the early 1980s and have been a participant -- and on occasion, even an instigator -- of some of the activities described here. This paper is an attempt to make a critical assessment of the current state of Z39.50 and a review of its development with the full benefit of hindsight. It recounts a number of debates that occurred within the developer community over the past years. In many of these, I advocated specific positions or approaches, sometimes successfully and sometimes unsuccessfully. What is presented here is one person's perspective - mine --, which is sometimes at odds with the current consensus with the developer community; I've tried to represent opposing views fairly, and to differentiate my opinions from fact or consensus. However, others will undoubtedly disagree with many of the comments here.

0.006976935 = product of:
  0.038373142 = sum of:
    0.0159967 = weight(_text_:of in 7911) [ClassicSimilarity], result of:
      0.0159967 = score(doc=7911,freq=12.0), product of:
        0.053998582 = queryWeight, product of:
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.034531306 = queryNorm
        0.29624295 = fieldWeight in 7911, product of:
          3.4641016 = tf(freq=12.0), with freq of:
            12.0 = termFreq=12.0
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.0546875 = fieldNorm(doc=7911)
    0.022376444 = weight(_text_:on in 7911) [ClassicSimilarity], result of:
      0.022376444 = score(doc=7911,freq=6.0), product of:
        0.07594867 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.034531306 = queryNorm
        0.29462588 = fieldWeight in 7911, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.0546875 = fieldNorm(doc=7911)
  0.18181819 = coord(2/11)

Abstract

Examined two groups of online catalogue users segregated by their method of access to the system: terminals in the library or remote workstations. An online survey collected demographic data, perceptions on source and terminal accessibility, and information on usage, task variety and search satisfaction. Transaction logs furnished data on browsing behavious, while interviews of both groups provided additional information about remote use. Results indicate that remote use is comparable to traditional use

Source

Integrating technologies - converging professions: proceedings of the 56th Annual Meeting of the American Society for Information Science, Columbus, OH, 24-28 October 1993. Ed.: S. Bonzi

0.0065687574 = product of:
  0.036128163 = sum of:
    0.010555085 = weight(_text_:of in 3108) [ClassicSimilarity], result of:
      0.010555085 = score(doc=3108,freq=4.0), product of:
        0.053998582 = queryWeight, product of:
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.034531306 = queryNorm
        0.19546966 = fieldWeight in 3108, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.0625 = fieldNorm(doc=3108)
    0.025573079 = weight(_text_:on in 3108) [ClassicSimilarity], result of:
      0.025573079 = score(doc=3108,freq=6.0), product of:
        0.07594867 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.034531306 = queryNorm
        0.33671528 = fieldWeight in 3108, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.0625 = fieldNorm(doc=3108)
  0.18181819 = coord(2/11)

Abstract

Describes the cooperative efforts of computer centre staff and library staff at Bentley College, Massachusetts, to create end user interfaces to enable the locally loaded data bases on the on-line catalogue to be searched off-campus by remote users as well as by library users on campus. Describes the success obtained using 2 data bases: LEXIS and Dow Jones News Retrieval Service

0.0065104505 = product of:
  0.035807475 = sum of:
    0.014927144 = weight(_text_:of in 818) [ClassicSimilarity], result of:
      0.014927144 = score(doc=818,freq=8.0), product of:
        0.053998582 = queryWeight, product of:
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.034531306 = queryNorm
        0.27643585 = fieldWeight in 818, product of:
          2.828427 = tf(freq=8.0), with freq of:
            8.0 = termFreq=8.0
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.0625 = fieldNorm(doc=818)
    0.02088033 = weight(_text_:on in 818) [ClassicSimilarity], result of:
      0.02088033 = score(doc=818,freq=4.0), product of:
        0.07594867 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.034531306 = queryNorm
        0.27492687 = fieldWeight in 818, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.0625 = fieldNorm(doc=818)
  0.18181819 = coord(2/11)

COMPASS

Information retrieval / Use of / On-line computers

Footnote

Rez. in: College and research libraries 52(1991) S.590-591 (F. Wilson); Journal of academic librarianship 18(1992) no.1, S-40-42 (M.D. Behr)

Subject

Information retrieval / Use of / On-line computers

0.006372941 = product of:
  0.035051174 = sum of:
    0.01939093 = weight(_text_:of in 3209) [ClassicSimilarity], result of:
      0.01939093 = score(doc=3209,freq=24.0), product of:
        0.053998582 = queryWeight, product of:
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.034531306 = queryNorm
        0.3591007 = fieldWeight in 3209, product of:
          4.8989797 = tf(freq=24.0), with freq of:
            24.0 = termFreq=24.0
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.046875 = fieldNorm(doc=3209)
    0.015660247 = weight(_text_:on in 3209) [ClassicSimilarity], result of:
      0.015660247 = score(doc=3209,freq=4.0), product of:
        0.07594867 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.034531306 = queryNorm
        0.20619515 = fieldWeight in 3209, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.046875 = fieldNorm(doc=3209)
  0.18181819 = coord(2/11)

Abstract

The IOS rererence model of open distributed processing (RM-ODP) consists of: an overview of the reference model, the descriptive model, the prescriptive model, and the architectural semantics. They provide the concepts and rules of distributed processing to ensure openness between interacting distributed application components. Openness is a combination of characteristics: accessibility, heterogeneity, autonomy and distribution. The RM-ODP introduces the concept of viewpoint to describe a system from a particular set of concerns, and hence to deal with the complexity of distributed systems. While all the viewpoints are relevant to the description and design of distributed systems, the computational and engineering models are the ones that bear most directly on the design and implementation of distributed systems. From a distributes software engineering point of view, the computational and engineering viewpoints are again the most important; they reflect the software structure of the distributed application most closely. Concentrates on the computational and engineering viewpoints

0.0060084667 = product of:
  0.033046566 = sum of:
    0.018281942 = weight(_text_:of in 3102) [ClassicSimilarity], result of:
      0.018281942 = score(doc=3102,freq=12.0), product of:
        0.053998582 = queryWeight, product of:
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.034531306 = queryNorm
        0.33856338 = fieldWeight in 3102, product of:
          3.4641016 = tf(freq=12.0), with freq of:
            12.0 = termFreq=12.0
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.0625 = fieldNorm(doc=3102)
    0.014764623 = weight(_text_:on in 3102) [ClassicSimilarity], result of:
      0.014764623 = score(doc=3102,freq=2.0), product of:
        0.07594867 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.034531306 = queryNorm
        0.19440265 = fieldWeight in 3102, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.0625 = fieldNorm(doc=3102)
  0.18181819 = coord(2/11)

Abstract

This report presents the results of a survey of users who access the University of California's online union catalog, the MELVYL library system, via microcomputers with modems or connections carried through local or wide area networks. The report includes descriptive statistics on user location, status, subject interest, affiliation, in-library versus out-of-library usage patterns, need for assistance, and desire for new features

0.0060084667 = product of:
  0.033046566 = sum of:
    0.018281942 = weight(_text_:of in 1589) [ClassicSimilarity], result of:
      0.018281942 = score(doc=1589,freq=12.0), product of:
        0.053998582 = queryWeight, product of:
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.034531306 = queryNorm
        0.33856338 = fieldWeight in 1589, product of:
          3.4641016 = tf(freq=12.0), with freq of:
            12.0 = termFreq=12.0
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.0625 = fieldNorm(doc=1589)
    0.014764623 = weight(_text_:on in 1589) [ClassicSimilarity], result of:
      0.014764623 = score(doc=1589,freq=2.0), product of:
        0.07594867 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.034531306 = queryNorm
        0.19440265 = fieldWeight in 1589, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.0625 = fieldNorm(doc=1589)
  0.18181819 = coord(2/11)

Abstract

Computer and communications technology is having a profound impact on libraries and the way in which they serve their users. Discusses online catalogues in libraries, the development of the Internet and OSI, and the development of search and retrieve (SR) protocols to allow standardized access to library catalogues across communications networks. Considers the deployment of SR protocols, problems with interoperability of clients and servers, interlibrary loan possibilities of SR protocols, and the feasibility of electronic document delivery

0.005927445 = product of:
  0.032600947 = sum of:
    0.018565401 = weight(_text_:of in 3013) [ClassicSimilarity], result of:
      0.018565401 = score(doc=3013,freq=22.0), product of:
        0.053998582 = queryWeight, product of:
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.034531306 = queryNorm
        0.34381276 = fieldWeight in 3013, product of:
          4.690416 = tf(freq=22.0), with freq of:
            22.0 = termFreq=22.0
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.046875 = fieldNorm(doc=3013)
    0.014035545 = product of:
      0.02807109 = sum of:
        0.02807109 = weight(_text_:22 in 3013) [ClassicSimilarity], result of:
          0.02807109 = score(doc=3013,freq=2.0), product of:
            0.12092275 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.034531306 = queryNorm
            0.23214069 = fieldWeight in 3013, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.046875 = fieldNorm(doc=3013)
      0.5 = coord(1/2)
  0.18181819 = coord(2/11)

Abstract

The primary objective of the present study was to exmine whether readers conducting bibliographic searches in ALEPH - Israel's research library network - tend to search only within the OPAC of the library within which they are working or whether they access the remote OPACs of other libraries. The ALEPH network has a dezentralized database. Therefore, it was possible to examine this question because each library has its own access code and each database can be searched separately. The data were collected by means of a one-page questionnaire lefr beside each terminal in the library of the Graduate School of Library and Archive Studies of the Hebrew University of Jerusalem during an entire academic years. results of analysis of the data collected in this survey are presented in 6 tables

Date

22. 2.1999 13:06:18

0.0058857286 = product of:
  0.032371506 = sum of:
    0.0159967 = weight(_text_:of in 3696) [ClassicSimilarity], result of:
      0.0159967 = score(doc=3696,freq=12.0), product of:
        0.053998582 = queryWeight, product of:
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.034531306 = queryNorm
        0.29624295 = fieldWeight in 3696, product of:
          3.4641016 = tf(freq=12.0), with freq of:
            12.0 = termFreq=12.0
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.0546875 = fieldNorm(doc=3696)
    0.016374804 = product of:
      0.03274961 = sum of:
        0.03274961 = weight(_text_:22 in 3696) [ClassicSimilarity], result of:
          0.03274961 = score(doc=3696,freq=2.0), product of:
            0.12092275 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.034531306 = queryNorm
            0.2708308 = fieldWeight in 3696, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0546875 = fieldNorm(doc=3696)
      0.5 = coord(1/2)
  0.18181819 = coord(2/11)

Abstract

Provides examples to illustrate the growing use and acceptance of remote access to OPACs. Examines the differences between offering in-house public access and remote access to users and offers suggestions to help address some of the requirements of remote users. Discusses the shortcomings of the bibliographic record, what can be done to enhance the OPAC record, remote access to periodical indexes, access to the physical items represented by the bibliographic records, and the importance of establishing lines of communication with remote users

Date

8. 1.2007 17:22:42

0.0057188505 = product of:
  0.031453677 = sum of:
    0.016689055 = weight(_text_:of in 1895) [ClassicSimilarity], result of:
      0.016689055 = score(doc=1895,freq=10.0), product of:
        0.053998582 = queryWeight, product of:
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.034531306 = queryNorm
        0.3090647 = fieldWeight in 1895, product of:
          3.1622777 = tf(freq=10.0), with freq of:
            10.0 = termFreq=10.0
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.0625 = fieldNorm(doc=1895)
    0.014764623 = weight(_text_:on in 1895) [ClassicSimilarity], result of:
      0.014764623 = score(doc=1895,freq=2.0), product of:
        0.07594867 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.034531306 = queryNorm
        0.19440265 = fieldWeight in 1895, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.0625 = fieldNorm(doc=1895)
  0.18181819 = coord(2/11)

Abstract

Examines a number of possible OSI system implementation strategies based on the various prevailing system facilities: processes, threads, kernel and front-end processors. Analyzes the pros and cons of the strategies showing their relative merits in implementation. The analysis leads to the recommendation of an enhanced subsystem architecture that holds the best compromise of the conflicting requirements of modularity and efficiency

0.0057155304 = product of:
  0.031435415 = sum of:
    0.010555085 = weight(_text_:of in 3107) [ClassicSimilarity], result of:
      0.010555085 = score(doc=3107,freq=4.0), product of:
        0.053998582 = queryWeight, product of:
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.034531306 = queryNorm
        0.19546966 = fieldWeight in 3107, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.0625 = fieldNorm(doc=3107)
    0.02088033 = weight(_text_:on in 3107) [ClassicSimilarity], result of:
      0.02088033 = score(doc=3107,freq=4.0), product of:
        0.07594867 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.034531306 = queryNorm
        0.27492687 = fieldWeight in 3107, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.0625 = fieldNorm(doc=3107)
  0.18181819 = coord(2/11)

Abstract

OPACs in an increasing number of libraries are now available using the Joint Academic Network (JANET). Access has tended to be obstructed, for the casual user, by the lengthy JANET addressing codes and varying log-on procedures required by each library system. Discribed how a communications and menu package on an IBK/PC can be used so that by merely pressing cursor control, return and escape keays, any user can gain access to any one of over 40 OPACs linked to JANET

0.0056966436 = product of:
  0.03133154 = sum of:
    0.0130612515 = weight(_text_:of in 1496) [ClassicSimilarity], result of:
      0.0130612515 = score(doc=1496,freq=8.0), product of:
        0.053998582 = queryWeight, product of:
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.034531306 = queryNorm
        0.24188137 = fieldWeight in 1496, product of:
          2.828427 = tf(freq=8.0), with freq of:
            8.0 = termFreq=8.0
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.0546875 = fieldNorm(doc=1496)
    0.01827029 = weight(_text_:on in 1496) [ClassicSimilarity], result of:
      0.01827029 = score(doc=1496,freq=4.0), product of:
        0.07594867 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.034531306 = queryNorm
        0.24056101 = fieldWeight in 1496, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.0546875 = fieldNorm(doc=1496)
  0.18181819 = coord(2/11)

Abstract

The rapid growth of the Internet TCP/IP networks has encouraged the deployment of management products based on the Internet's Simple Network Management Protocol (SNMP). However, many organizations, including most telecommunications service providers, continue to define enterprise management solutions based on ISO/CCITT standard management and underlying Common Management Information Protocol (CMIP). Concludes that the key to achieving timely, effective, integrated management is to encourage a transition process aimed away from existing commercial investment in both ISO/CCITT and Internet based management technologies through deployment of common methods and tools which support integration

Source

Journal of network and systems management. 2(1994) no.3, S.317-322

0.0056966436 = product of:
  0.03133154 = sum of:
    0.0130612515 = weight(_text_:of in 7006) [ClassicSimilarity], result of:
      0.0130612515 = score(doc=7006,freq=8.0), product of:
        0.053998582 = queryWeight, product of:
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.034531306 = queryNorm
        0.24188137 = fieldWeight in 7006, product of:
          2.828427 = tf(freq=8.0), with freq of:
            8.0 = termFreq=8.0
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.0546875 = fieldNorm(doc=7006)
    0.01827029 = weight(_text_:on in 7006) [ClassicSimilarity], result of:
      0.01827029 = score(doc=7006,freq=4.0), product of:
        0.07594867 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.034531306 = queryNorm
        0.24056101 = fieldWeight in 7006, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.0546875 = fieldNorm(doc=7006)
  0.18181819 = coord(2/11)

Abstract

Discusses Austrian government policy on the information superhighway (ISH) since Aug. 94. The Austrian telecommunications infrastructure is far behind the standards of Europe. The Austrain PTT monopoly over the public telecommunications network is an obstacle to development. The rates for data services are still based on copper cable with transmission speeds of 9600 Kbps. Although there are various ISH initiatives in Austria, the gap between vision and reality is large. Describes the initiatives of the Austrian National Host and the Bureau for International Research and Technology Cooperation; the Austrian Platform for Telematic Applications; BNet (Burgenland); Telematik Initiative Wien; TELKIS Telekommunikationsinitiative Steiermark; Datahighway Upper Austria; Vorarlberger Telekommunikations GmbH; Telematik Initiative; Datenbahn Telecom GmbH (Salzburg); Ti-KOM (Tirol) and other initiatives