Search (38 results, page 1 of 2)

0.01803071 = product of:
  0.054092128 = sum of:
    0.054092128 = product of:
      0.108184256 = sum of:
        0.108184256 = weight(_text_:22 in 4147) [ClassicSimilarity], result of:
          0.108184256 = score(doc=4147,freq=2.0), product of:
            0.1747608 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04990557 = queryNorm
            0.61904186 = fieldWeight in 4147, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.125 = fieldNorm(doc=4147)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Source

Cogito. 9(1993) H.2, S.18-22

0.01577687 = product of:
  0.04733061 = sum of:
    0.04733061 = product of:
      0.09466122 = sum of:
        0.09466122 = weight(_text_:22 in 8109) [ClassicSimilarity], result of:
          0.09466122 = score(doc=8109,freq=2.0), product of:
            0.1747608 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04990557 = queryNorm
            0.5416616 = fieldWeight in 8109, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.109375 = fieldNorm(doc=8109)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Source

Cogito. 10(1994) H.4, S.17-22

0.01577687 = product of:
  0.04733061 = sum of:
    0.04733061 = product of:
      0.09466122 = sum of:
        0.09466122 = weight(_text_:22 in 2656) [ClassicSimilarity], result of:
          0.09466122 = score(doc=2656,freq=2.0), product of:
            0.1747608 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04990557 = queryNorm
            0.5416616 = fieldWeight in 2656, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.109375 = fieldNorm(doc=2656)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

30.11.1995 20:53:22

0.015399541 = product of:
  0.04619862 = sum of:
    0.04619862 = weight(_text_:on in 7061) [ClassicSimilarity], result of:
      0.04619862 = score(doc=7061,freq=6.0), product of:
        0.109763056 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.04990557 = queryNorm
        0.4208941 = fieldWeight in 7061, 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=7061)
  0.33333334 = coord(1/3)

COMPASS

Libraries / On-line computers

Subject

Libraries / On-line computers

0.015399541 = product of:
  0.04619862 = sum of:
    0.04619862 = weight(_text_:on in 799) [ClassicSimilarity], result of:
      0.04619862 = score(doc=799,freq=6.0), product of:
        0.109763056 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.04990557 = 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.33333334 = coord(1/3)

Issue

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

LCSH

Catalogs, On / line

Subject

Catalogs, On / line

0.013523031 = product of:
  0.040569093 = sum of:
    0.040569093 = product of:
      0.081138186 = sum of:
        0.081138186 = weight(_text_:22 in 354) [ClassicSimilarity], result of:
          0.081138186 = score(doc=354,freq=2.0), product of:
            0.1747608 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04990557 = queryNorm
            0.46428138 = fieldWeight in 354, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.09375 = fieldNorm(doc=354)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Source

Com!. 1997, H.8, S.22-24

0.013523031 = product of:
  0.040569093 = sum of:
    0.040569093 = product of:
      0.081138186 = sum of:
        0.081138186 = weight(_text_:22 in 5935) [ClassicSimilarity], result of:
          0.081138186 = score(doc=5935,freq=2.0), product of:
            0.1747608 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04990557 = queryNorm
            0.46428138 = fieldWeight in 5935, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.09375 = fieldNorm(doc=5935)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Footnote

Rez. in: Internet Professionell 2000, H.2, S.22

0.0124473 = product of:
  0.0373419 = sum of:
    0.0373419 = weight(_text_:on in 5701) [ClassicSimilarity], result of:
      0.0373419 = score(doc=5701,freq=2.0), product of:
        0.109763056 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.04990557 = queryNorm
        0.34020463 = fieldWeight in 5701, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.109375 = fieldNorm(doc=5701)
  0.33333334 = coord(1/3)

0.012319634 = product of:
  0.0369589 = sum of:
    0.0369589 = weight(_text_:on in 3108) [ClassicSimilarity], result of:
      0.0369589 = score(doc=3108,freq=6.0), product of:
        0.109763056 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.04990557 = 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.33333334 = coord(1/3)

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.011269193 = product of:
  0.03380758 = sum of:
    0.03380758 = product of:
      0.06761516 = sum of:
        0.06761516 = weight(_text_:22 in 877) [ClassicSimilarity], result of:
          0.06761516 = score(doc=877,freq=2.0), product of:
            0.1747608 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04990557 = queryNorm
            0.38690117 = fieldWeight in 877, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.078125 = fieldNorm(doc=877)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Pages

S.22-31

0.011269193 = product of:
  0.03380758 = sum of:
    0.03380758 = product of:
      0.06761516 = sum of:
        0.06761516 = weight(_text_:22 in 2955) [ClassicSimilarity], result of:
          0.06761516 = score(doc=2955,freq=2.0), product of:
            0.1747608 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04990557 = queryNorm
            0.38690117 = fieldWeight in 2955, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.078125 = fieldNorm(doc=2955)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

19. 2.1999 20:21:22

0.010779679 = product of:
  0.032339036 = sum of:
    0.032339036 = weight(_text_:on in 4216) [ClassicSimilarity], result of:
      0.032339036 = score(doc=4216,freq=6.0), product of:
        0.109763056 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.04990557 = queryNorm
        0.29462588 = fieldWeight in 4216, 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=4216)
  0.33333334 = coord(1/3)

Abstract

Hartford University mounted a DRA Atlas Integrated library system in 1991, using a DECnet/Ethernet network and a VAX 6310 mainframe computer. As VAX VT320 terminals were available in many campus buildings, the library's catalogue could be searched from many locations and could be dialed up by remote users. Commercial databases in MARC format could be mounted on the system and searched with the same commands that users employed for the OPAC. Explains the use of Periodical Abstracts from UMI on the online catalogue. Discusses searching strategies and compares the Periodical Abstracts Ondisc CD-ROM with the tape loaded product

0.010779679 = product of:
  0.032339036 = sum of:
    0.032339036 = weight(_text_:on in 7911) [ClassicSimilarity], result of:
      0.032339036 = score(doc=7911,freq=6.0), product of:
        0.109763056 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.04990557 = 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.33333334 = coord(1/3)

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

0.010669115 = product of:
  0.032007344 = sum of:
    0.032007344 = weight(_text_:on in 3099) [ClassicSimilarity], result of:
      0.032007344 = score(doc=3099,freq=2.0), product of:
        0.109763056 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.04990557 = 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.33333334 = coord(1/3)

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.010058938 = product of:
  0.030176813 = sum of:
    0.030176813 = weight(_text_:on in 3107) [ClassicSimilarity], result of:
      0.030176813 = score(doc=3107,freq=4.0), product of:
        0.109763056 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.04990557 = 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.33333334 = coord(1/3)

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.010058938 = product of:
  0.030176813 = sum of:
    0.030176813 = weight(_text_:on in 818) [ClassicSimilarity], result of:
      0.030176813 = score(doc=818,freq=4.0), product of:
        0.109763056 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.04990557 = 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.33333334 = coord(1/3)

COMPASS

Information retrieval / Use of / On-line computers

Subject

Information retrieval / Use of / On-line computers

0.008890929 = product of:
  0.026672786 = sum of:
    0.026672786 = weight(_text_:on in 809) [ClassicSimilarity], result of:
      0.026672786 = score(doc=809,freq=2.0), product of:
        0.109763056 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.04990557 = queryNorm
        0.24300331 = fieldWeight in 809, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.078125 = fieldNorm(doc=809)
  0.33333334 = coord(1/3)

0.008846363 = product of:
  0.02653909 = sum of:
    0.02653909 = weight(_text_:on in 1262) [ClassicSimilarity], result of:
      0.02653909 = score(doc=1262,freq=22.0), product of:
        0.109763056 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.04990557 = 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.33333334 = coord(1/3)

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.008801571 = product of:
  0.026404712 = sum of:
    0.026404712 = weight(_text_:on in 6038) [ClassicSimilarity], result of:
      0.026404712 = score(doc=6038,freq=4.0), product of:
        0.109763056 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.04990557 = 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.33333334 = coord(1/3)

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.008801571 = product of:
  0.026404712 = sum of:
    0.026404712 = weight(_text_:on in 1496) [ClassicSimilarity], result of:
      0.026404712 = score(doc=1496,freq=4.0), product of:
        0.109763056 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.04990557 = 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.33333334 = coord(1/3)

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