Search (35 results, page 2 of 2)

0.0019223152 = product of:
  0.017300837 = sum of:
    0.017300837 = product of:
      0.034601673 = sum of:
        0.034601673 = weight(_text_:web in 5584) [ClassicSimilarity], result of:
          0.034601673 = score(doc=5584,freq=8.0), product of:
            0.09596372 = queryWeight, product of:
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.02940506 = queryNorm
            0.36057037 = fieldWeight in 5584, product of:
              2.828427 = tf(freq=8.0), with freq of:
                8.0 = termFreq=8.0
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.0390625 = fieldNorm(doc=5584)
      0.5 = coord(1/2)
  0.11111111 = coord(1/9)

Abstract

This article reports on a model and patterns of use of a library catalog that can be accessed through the Internet. Three categories of users are identified. individuals who perform a search of the catalog, tourists who look only at opening pages of the library catalog's site, and Web spiders that come to the site to obtain pages for indexing the Web. A number of types of use activities are also identified, and can be grouped with the presearch phase (which takes place before any searching begins): the search phase, the display phase (in which users display the results of their search), and phases in which users make errors, ask the system for help or assistance, and take other actions. An empirical investigation of patterns of use of a university Web-based library catalog was conducted for 479 days. During that period, the characteristics of about 2.5 million sessions were recorded and analyzed, and usage trends were identified. Of the total, 62% of the sessions were for users who performed a search, 27% were from spiders, and 11% were for tourists. During the study period, the average search session lasted about 5 minutes when the study began and had increased to about 10 minutes 16 months later. An average search consisted of about 1.5 presearch actions lasting about 25 seconds, about 5.3 display actions, and 2.5 searches per session. The latter two categories are in the range of 35-37 seconds per session each. There were major differences in usage (number of searches, search time, number of display actions, and display time), depending upon the database accessed

0.0019223152 = product of:
  0.017300837 = sum of:
    0.017300837 = product of:
      0.034601673 = sum of:
        0.034601673 = weight(_text_:web in 1174) [ClassicSimilarity], result of:
          0.034601673 = score(doc=1174,freq=8.0), product of:
            0.09596372 = queryWeight, product of:
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.02940506 = queryNorm
            0.36057037 = fieldWeight in 1174, product of:
              2.828427 = tf(freq=8.0), with freq of:
                8.0 = termFreq=8.0
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.0390625 = fieldNorm(doc=1174)
      0.5 = coord(1/2)
  0.11111111 = coord(1/9)

Abstract

Recherche in Bibliothekskatalogen war, zumindest in deutschen Bibliotheken, bis zur Mitte des 20. Jahrhunderts in der Regel Sache des Personals, eine wirklich erfolgreiche Recherche meist Spezialisten vorbehalten. Nur diese waren in der Lage, häufig unter Einbeziehung diverser Hilfsmittel, Titelwünsche der Leser nach den jeweiligen Katalog- und Bibliotheksregeln in entsprechende Kataloganfragen umzusetzen. Als dann den Bibliothekskunden selbst nach und nach der Zugang zu diesen Zettelkatalogen in den Bibliotheken eröffnet wurde, war für eine erfolgreiche Suche meist "guter Rat teuer". Hilfestellung und "guter Rat", oft schon bei einer simplen Titelsuche wie "Schuld und Sühne" nötig, konnte vom uneingeweihten Leser direkt vor Ort in der Bibliothek eingeholt werden. Elektronische Formen der Kataloge in Bibliotheken, kurz "OPACs" genannt, eröffneten neue, den alten Zettel- und Mikrofichekatalogen völlig unbekannte Suchmöglichkeiten. Sie zogen aber auch neue Fragestellungen nach sich, besonders zum Handling und zur Suchstrategie. Zumindest dem "fragemutigen" Nutzer konnte und kann dabei vor Ort in den Bibliotheken immer noch direkt geholfen werden. Diese Hilfestellung entfällt jedoch bei allen Bibliotheks- und Verbundkatalogen, die im Internet als so genannte "Web-OPACs" angeboten werden. Sie erreichen einen viel größeren, dafür aber anonym bleibenden Interessentenkreis, vom absoluten Bibliothekslaien bis zum kundigen Bibliotheksnutzer. Diese aktiven und potentiellen Nutzer treten mit den unterschiedlichsten Anforderungen und Fragestellungen an solche Web-OPACs heran. Ein Web-OPAC muss demnach so gestaltet sein, dass er für Laien und Profis gleichermaßen nutzbar ist und dabei möglichst wenige Fragen überhaupt erst aufkommen lässt, im Idealfall also über eine selbsterklärende Oberfläche verfügt. Hilfetexte müssen die nicht vorhandene persönliche Hilfestellung kompensieren helfen. Sie sind also übersichtlich, verständlich und zielgerichtet einsetzbar zu gestalten.

0.001902995 = product of:
  0.017126955 = sum of:
    0.017126955 = product of:
      0.03425391 = sum of:
        0.03425391 = weight(_text_:web in 1437) [ClassicSimilarity], result of:
          0.03425391 = score(doc=1437,freq=4.0), product of:
            0.09596372 = queryWeight, product of:
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.02940506 = queryNorm
            0.35694647 = fieldWeight in 1437, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.0546875 = fieldNorm(doc=1437)
      0.5 = coord(1/2)
  0.11111111 = coord(1/9)

Abstract

A major initiative at the Sandia National Laboratories Technical Library, New Mexico, is the provision of desktop access to information for Sandia researchers. During 1995, the library created a home page on the WWW with information on how to link to its client server based OPAC. Through multiple access points, researchers can search the catalogue from their desks and a new initiative is the provision of access to Sandia generated documents by converting them to electronic form, placing them on Sandia's 'internal Web' and linking them to the OPAC bibliographic record. Addresses the processes developed in the library and the procedures for cataloguing these electronic reports, including identification of the bibliographic information and MARC tags to be used

0.0017706576 = product of:
  0.015935918 = sum of:
    0.015935918 = product of:
      0.031871837 = sum of:
        0.031871837 = weight(_text_:22 in 1406) [ClassicSimilarity], result of:
          0.031871837 = score(doc=1406,freq=2.0), product of:
            0.10297151 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.02940506 = queryNorm
            0.30952093 = fieldWeight in 1406, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0625 = fieldNorm(doc=1406)
      0.5 = coord(1/2)
  0.11111111 = coord(1/9)

Series

British Library Research and Innovation Centre (BLRIC) report; 22

0.0015493254 = product of:
  0.013943928 = sum of:
    0.013943928 = product of:
      0.027887857 = sum of:
        0.027887857 = weight(_text_:22 in 3656) [ClassicSimilarity], result of:
          0.027887857 = score(doc=3656,freq=2.0), product of:
            0.10297151 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.02940506 = queryNorm
            0.2708308 = fieldWeight in 3656, 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=3656)
      0.5 = coord(1/2)
  0.11111111 = coord(1/9)

Series

Cataloging and classification quarterly; vol.22, nos.3/4

0.0015378521 = product of:
  0.013840669 = sum of:
    0.013840669 = product of:
      0.027681338 = sum of:
        0.027681338 = weight(_text_:web in 1936) [ClassicSimilarity], result of:
          0.027681338 = score(doc=1936,freq=2.0), product of:
            0.09596372 = queryWeight, product of:
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.02940506 = queryNorm
            0.2884563 = fieldWeight in 1936, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.0625 = fieldNorm(doc=1936)
      0.5 = coord(1/2)
  0.11111111 = coord(1/9)

0.0015378521 = product of:
  0.013840669 = sum of:
    0.013840669 = product of:
      0.027681338 = sum of:
        0.027681338 = weight(_text_:web in 2406) [ClassicSimilarity], result of:
          0.027681338 = score(doc=2406,freq=2.0), product of:
            0.09596372 = queryWeight, product of:
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.02940506 = queryNorm
            0.2884563 = fieldWeight in 2406, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.0625 = fieldNorm(doc=2406)
      0.5 = coord(1/2)
  0.11111111 = coord(1/9)

0.0015378521 = product of:
  0.013840669 = sum of:
    0.013840669 = product of:
      0.027681338 = sum of:
        0.027681338 = weight(_text_:web in 1776) [ClassicSimilarity], result of:
          0.027681338 = score(doc=1776,freq=2.0), product of:
            0.09596372 = queryWeight, product of:
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.02940506 = queryNorm
            0.2884563 = fieldWeight in 1776, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.0625 = fieldNorm(doc=1776)
      0.5 = coord(1/2)
  0.11111111 = coord(1/9)

0.0015378521 = product of:
  0.013840669 = sum of:
    0.013840669 = product of:
      0.027681338 = sum of:
        0.027681338 = weight(_text_:web in 2232) [ClassicSimilarity], result of:
          0.027681338 = score(doc=2232,freq=2.0), product of:
            0.09596372 = queryWeight, product of:
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.02940506 = queryNorm
            0.2884563 = fieldWeight in 2232, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.0625 = fieldNorm(doc=2232)
      0.5 = coord(1/2)
  0.11111111 = coord(1/9)

0.0015378521 = product of:
  0.013840669 = sum of:
    0.013840669 = product of:
      0.027681338 = sum of:
        0.027681338 = weight(_text_:web in 2594) [ClassicSimilarity], result of:
          0.027681338 = score(doc=2594,freq=2.0), product of:
            0.09596372 = queryWeight, product of:
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.02940506 = queryNorm
            0.2884563 = fieldWeight in 2594, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.0625 = fieldNorm(doc=2594)
      0.5 = coord(1/2)
  0.11111111 = coord(1/9)

0.0015378521 = product of:
  0.013840669 = sum of:
    0.013840669 = product of:
      0.027681338 = sum of:
        0.027681338 = weight(_text_:web in 2843) [ClassicSimilarity], result of:
          0.027681338 = score(doc=2843,freq=2.0), product of:
            0.09596372 = queryWeight, product of:
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.02940506 = queryNorm
            0.2884563 = fieldWeight in 2843, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.0625 = fieldNorm(doc=2843)
      0.5 = coord(1/2)
  0.11111111 = coord(1/9)

0.0015378521 = product of:
  0.013840669 = sum of:
    0.013840669 = product of:
      0.027681338 = sum of:
        0.027681338 = weight(_text_:web in 2523) [ClassicSimilarity], result of:
          0.027681338 = score(doc=2523,freq=2.0), product of:
            0.09596372 = queryWeight, product of:
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.02940506 = queryNorm
            0.2884563 = fieldWeight in 2523, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.0625 = fieldNorm(doc=2523)
      0.5 = coord(1/2)
  0.11111111 = coord(1/9)

Abstract

Der Beitrag fasst die Ergebnisse einer Untersuchung von über 50 000 Suchanfragen am Hamburger Campus-Katalog zusammen. Der Campus-Katalog ist ein WEB-Katalog auf der Basis des Pica-Lokalsystems LBS3, dessen Protokolldateien die Rohdaten lieferten. Über die statistische Analyse der Suchanfragen hinaus, wird ein Versuch unternommen, die einzelnen Schritte einer Katalogrecherche zusammenzufassen und die Reaktion der Benutzer auf erfolglose Suchanfragen zu untersuchen.

0.0013456206 = product of:
  0.012110585 = sum of:
    0.012110585 = product of:
      0.02422117 = sum of:
        0.02422117 = weight(_text_:web in 2444) [ClassicSimilarity], result of:
          0.02422117 = score(doc=2444,freq=2.0), product of:
            0.09596372 = queryWeight, product of:
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.02940506 = queryNorm
            0.25239927 = fieldWeight in 2444, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.0546875 = fieldNorm(doc=2444)
      0.5 = coord(1/2)
  0.11111111 = coord(1/9)

0.001331819 = product of:
  0.011986371 = sum of:
    0.011986371 = product of:
      0.023972742 = sum of:
        0.023972742 = weight(_text_:web in 577) [ClassicSimilarity], result of:
          0.023972742 = score(doc=577,freq=6.0), product of:
            0.09596372 = queryWeight, product of:
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.02940506 = queryNorm
            0.24981049 = fieldWeight in 577, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.03125 = fieldNorm(doc=577)
      0.5 = coord(1/2)
  0.11111111 = coord(1/9)

Abstract

Users move from one state (or task) to another in an information system's labyrinth as they try to accomplish their work, and the amount of time they spend in each state varies. This article uses continuous-time stochastic models, mainly based on semi-Markov chains, to derive user state transition patterns (both in rates and in probabilities) in a Web-based information system. The methodology was demonstrated with 126,925 search sessions drawn from the transaction logs of the University of California's MELVYL® library catalog system (www.melvyLucop.edu). First, user sessions were categorized into six groups based on their similar use of the system. Second, by using a three-layer hierarchical taxonomy of the system Web pages, user sessions in each usage group were transformed into a sequence of states. All the usage groups but one have third-order sequential dependency in state transitions. The sole exception has fourth-order sequential dependency. The transition rates as well as transition probabilities of the semi-Markov model provide a background for interpreting user behavior probabilistically, at various levels of detail. Finally, the differences in derived usage patterns between usage groups were tested statistically. The test results showed that different groups have distinct patterns of system use. Knowledge of the extent of sequential dependency is beneficial because it allows one to predict a user's next move in a search space based on the past moves that have been made. It can also be used to help customize the design of the user interface to the system to facilitate interaction. The group CL6 labeled "knowledgeable and sophisticated usage" and the group CL7 labeled "unsophisticated usage" both had third-order sequential dependency and had the same most-frequently occurring search pattern: screen display, record display, screen display, and record display. The group CL8 called "highly interactive use with good search results" had fourth-order sequential dependency, and its most frequently occurring pattern was the same as CL6 and CL7 with one more screen display action added. The group CL13, called "known-item searching" had third-order sequential dependency, and its most frequently occurring pattern was index access, search with retrievals, screen display, and record display. Group CL14 called "help intensive searching," and CL18 called "relatively unsuccessful" both had thirdorder sequential dependency, and for both groups the most frequently occurring pattern was index access, search without retrievals, index access, and again, search without retrievals.

9.611576E-4 = product of:
  0.008650418 = sum of:
    0.008650418 = product of:
      0.017300837 = sum of:
        0.017300837 = weight(_text_:web in 118) [ClassicSimilarity], result of:
          0.017300837 = score(doc=118,freq=2.0), product of:
            0.09596372 = queryWeight, product of:
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.02940506 = queryNorm
            0.18028519 = fieldWeight in 118, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.0390625 = fieldNorm(doc=118)
      0.5 = coord(1/2)
  0.11111111 = coord(1/9)