Search (3792 results, page 1 of 190)

  1. Smet, E. de: Evaluation of a computerised community information system through transaction analysis and user survey (1995) 0.18 
    0.1812794 = product of:
  0.3625588 = sum of:
    0.3625588 = sum of:
      0.31282145 = weight(_text_:transaction in 2304) [ClassicSimilarity], result of:
        0.31282145 = score(doc=2304,freq=6.0), product of:
          0.34995425 = queryWeight, product of:
            6.6730065 = idf(docFreq=151, maxDocs=44218)
            0.052443266 = queryNorm
          0.8938924 = fieldWeight in 2304, product of:
            2.4494898 = tf(freq=6.0), with freq of:
              6.0 = termFreq=6.0
            6.6730065 = idf(docFreq=151, maxDocs=44218)
            0.0546875 = fieldNorm(doc=2304)
      0.049737368 = weight(_text_:22 in 2304) [ClassicSimilarity], result of:
        0.049737368 = score(doc=2304,freq=2.0), product of:
          0.18364738 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.052443266 = queryNorm
          0.2708308 = fieldWeight in 2304, 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=2304)
  0.5 = coord(1/2)
    Abstract
    Reports on the results of a transaction analysis and user survey, evaluating a pilot system for computerized community information in a public library, based on the GDIS system (Gemeenschaps Informatie Documentair System). The non hierarchical and global approach to the integrated database proved to be useful for novice users. Out of many parameters only frequency of use correlates with retrieval success. The online questionnaire proved to be worthwhile although restricted in scope. The logbook transaction analysis yielded a rich amount of useful management information for the systems managers. The user survey yielded a rich set of data on which to perform statistical analyses according to social science practice, from which some interesting relations could be detected
    Date
    23.10.1995 19:22:11
  2. Flaherty, P.: Transaction logging systems : a descriptive summary (1993) 0.16 
    0.15641072 = product of:
  0.31282145 = sum of:
    0.31282145 = product of:
      0.6256429 = sum of:
        0.6256429 = weight(_text_:transaction in 5310) [ClassicSimilarity], result of:
          0.6256429 = score(doc=5310,freq=6.0), product of:
            0.34995425 = queryWeight, product of:
              6.6730065 = idf(docFreq=151, maxDocs=44218)
              0.052443266 = queryNorm
            1.7877848 = fieldWeight in 5310, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              6.6730065 = idf(docFreq=151, maxDocs=44218)
              0.109375 = fieldNorm(doc=5310)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
    Abstract
    Discusses the features of transaction logging facilities and suggests some components of an ideal transaction logging facility
  3. Moulaison, H.L.: OPAC queries at a medium-sized academic library : a transaction log analysis (2008) 0.15 
    0.1525775 = product of:
  0.305155 = sum of:
    0.305155 = sum of:
      0.25541764 = weight(_text_:transaction in 3599) [ClassicSimilarity], result of:
        0.25541764 = score(doc=3599,freq=4.0), product of:
          0.34995425 = queryWeight, product of:
            6.6730065 = idf(docFreq=151, maxDocs=44218)
            0.052443266 = queryNorm
          0.72986007 = fieldWeight in 3599, product of:
            2.0 = tf(freq=4.0), with freq of:
              4.0 = termFreq=4.0
            6.6730065 = idf(docFreq=151, maxDocs=44218)
            0.0546875 = fieldNorm(doc=3599)
      0.049737368 = weight(_text_:22 in 3599) [ClassicSimilarity], result of:
        0.049737368 = score(doc=3599,freq=2.0), product of:
          0.18364738 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.052443266 = queryNorm
          0.2708308 = fieldWeight in 3599, 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=3599)
  0.5 = coord(1/2)
    Abstract
    Patron queries at a four-year comprehensive college's online public access catalog were examined via transaction logs from March 2007. Three representative days were isolated for a more detailed examination of search characteristics. The results show that library users employed an average of one to three terms in a search, did not use Boolean operators, and made use of limits one-tenth of the time. Failed queries remained problematic, as a full one-third of searches resulted in zero hits. Implications and recommendations for improvements in the online public access catalog are discussed.
    Date
    10. 9.2000 17:38:22
  4. Hoskisson, T.: Making the right assumptions : know your user and improve the reference interview (1998) 0.13 
    0.13162567 = product of:
  0.26325133 = sum of:
    0.26325133 = sum of:
      0.20640862 = weight(_text_:transaction in 2194) [ClassicSimilarity], result of:
        0.20640862 = score(doc=2194,freq=2.0), product of:
          0.34995425 = queryWeight, product of:
            6.6730065 = idf(docFreq=151, maxDocs=44218)
            0.052443266 = queryNorm
          0.58981603 = fieldWeight in 2194, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            6.6730065 = idf(docFreq=151, maxDocs=44218)
            0.0625 = fieldNorm(doc=2194)
      0.056842707 = weight(_text_:22 in 2194) [ClassicSimilarity], result of:
        0.056842707 = score(doc=2194,freq=2.0), product of:
          0.18364738 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.052443266 = queryNorm
          0.30952093 = fieldWeight in 2194, 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=2194)
  0.5 = coord(1/2)
    Abstract
    Reference librarians often make incorrect assumptions about the library knowledge of their users. These assumptions can impede the reference interview and influence the outcome of the reference transaction. Examines 7 misconceptions about users and discusses how librarians can correct them to better understand their public and improve reference service. the misconceptions discussed involve users: stating their actual information needs, knowing what sources to use, understanding library arrangement anf jargon, communicating with librarians, and caring about competency
    Date
    14.11.1998 19:22:48
  5. Hancock-Beaulieu, M.: Searching behaviour and the evaluation of online catalogues (1991) 0.13 
    0.13162567 = product of:
  0.26325133 = sum of:
    0.26325133 = sum of:
      0.20640862 = weight(_text_:transaction in 2765) [ClassicSimilarity], result of:
        0.20640862 = score(doc=2765,freq=2.0), product of:
          0.34995425 = queryWeight, product of:
            6.6730065 = idf(docFreq=151, maxDocs=44218)
            0.052443266 = queryNorm
          0.58981603 = fieldWeight in 2765, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            6.6730065 = idf(docFreq=151, maxDocs=44218)
            0.0625 = fieldNorm(doc=2765)
      0.056842707 = weight(_text_:22 in 2765) [ClassicSimilarity], result of:
        0.056842707 = score(doc=2765,freq=2.0), product of:
          0.18364738 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.052443266 = queryNorm
          0.30952093 = fieldWeight in 2765, 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=2765)
  0.5 = coord(1/2)
    Abstract
    Presents a brief report on a study, carried out by the Centre for Interactive Systems Research, City University, to investigate the techniques used for evaluating OPACs: to explore and assess different data gathering methods in studying information seeking behaviour at the on-line catalogue; and to examine how a transaction logging facility could be enhanced to serve as a more effective diagnostic tool. For a full report see British Library research paper 78
    Pages
    S.20-22
  6. Peters, T.A.: ¬The history and development of transaction log analysis (1993) 0.11 
    0.109464705 = product of:
  0.21892941 = sum of:
    0.21892941 = product of:
      0.43785882 = sum of:
        0.43785882 = weight(_text_:transaction in 5309) [ClassicSimilarity], result of:
          0.43785882 = score(doc=5309,freq=4.0), product of:
            0.34995425 = queryWeight, product of:
              6.6730065 = idf(docFreq=151, maxDocs=44218)
              0.052443266 = queryNorm
            1.2511888 = fieldWeight in 5309, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              6.6730065 = idf(docFreq=151, maxDocs=44218)
              0.09375 = fieldNorm(doc=5309)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
    Abstract
    Reviews the literature of transaction log analysis, looking at the types of situations, events, and users studied
  7. Kaske, N.K.: Research methodologies and transaction log analysis : issues, questions, and a proposed model (1993) 0.11 
    0.109464705 = product of:
  0.21892941 = sum of:
    0.21892941 = product of:
      0.43785882 = sum of:
        0.43785882 = weight(_text_:transaction in 5311) [ClassicSimilarity], result of:
          0.43785882 = score(doc=5311,freq=4.0), product of:
            0.34995425 = queryWeight, product of:
              6.6730065 = idf(docFreq=151, maxDocs=44218)
              0.052443266 = queryNorm
            1.2511888 = fieldWeight in 5311, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              6.6730065 = idf(docFreq=151, maxDocs=44218)
              0.09375 = fieldNorm(doc=5311)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
    Abstract
    Addresses a number of issues and questions that need to be confronted before selecting a method, or methods, for analyzing transaction logs
  8. Sandore, B.: Applying the results of transaction log analysis (1993) 0.11 
    0.109464705 = product of:
  0.21892941 = sum of:
    0.21892941 = product of:
      0.43785882 = sum of:
        0.43785882 = weight(_text_:transaction in 5312) [ClassicSimilarity], result of:
          0.43785882 = score(doc=5312,freq=4.0), product of:
            0.34995425 = queryWeight, product of:
              6.6730065 = idf(docFreq=151, maxDocs=44218)
              0.052443266 = queryNorm
            1.2511888 = fieldWeight in 5312, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              6.6730065 = idf(docFreq=151, maxDocs=44218)
              0.09375 = fieldNorm(doc=5312)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
    Abstract
    Explores the different applications for the results of a transaction log analysis, including administration, public services, technical services, collection management, and systems development
  9. Hotho, A.; Bloehdorn, S.: Data Mining 2004 : Text classification by boosting weak learners based on terms and concepts (2004) 0.10 
    0.104609825 = sum of:
  0.08329381 = product of:
    0.24988142 = sum of:
      0.24988142 = weight(_text_:3a in 562) [ClassicSimilarity], result of:
        0.24988142 = score(doc=562,freq=2.0), product of:
          0.4446146 = queryWeight, product of:
            8.478011 = idf(docFreq=24, maxDocs=44218)
            0.052443266 = queryNorm
          0.56201804 = fieldWeight in 562, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            8.478011 = idf(docFreq=24, maxDocs=44218)
            0.046875 = fieldNorm(doc=562)
    0.33333334 = coord(1/3)
  0.021316014 = product of:
    0.04263203 = sum of:
      0.04263203 = weight(_text_:22 in 562) [ClassicSimilarity], result of:
        0.04263203 = score(doc=562,freq=2.0), product of:
          0.18364738 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.052443266 = queryNorm
          0.23214069 = fieldWeight in 562, 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=562)
    0.5 = coord(1/2)
    Content
    Vgl.: http://www.google.de/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&ved=0CEAQFjAA&url=http%3A%2F%2Fciteseerx.ist.psu.edu%2Fviewdoc%2Fdownload%3Fdoi%3D10.1.1.91.4940%26rep%3Drep1%26type%3Dpdf&ei=dOXrUMeIDYHDtQahsIGACg&usg=AFQjCNHFWVh6gNPvnOrOS9R3rkrXCNVD-A&sig2=5I2F5evRfMnsttSgFF9g7Q&bvm=bv.1357316858,d.Yms.
    Date
    8. 1.2013 10:22:32
  10. Tolle, J.: Current utilisation of online catalogs : transaction log analysis: final report to the Council on Library Resources (1983) 0.10 
    0.10320431 = product of:
  0.20640862 = sum of:
    0.20640862 = product of:
      0.41281724 = sum of:
        0.41281724 = weight(_text_:transaction in 3907) [ClassicSimilarity], result of:
          0.41281724 = score(doc=3907,freq=2.0), product of:
            0.34995425 = queryWeight, product of:
              6.6730065 = idf(docFreq=151, maxDocs=44218)
              0.052443266 = queryNorm
            1.1796321 = fieldWeight in 3907, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              6.6730065 = idf(docFreq=151, maxDocs=44218)
              0.125 = fieldNorm(doc=3907)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
  11. Murfin, M.E.; Gugelchuk, G.M.: Development and testing of a reference transaction assessment instrument (1987) 0.10 
    0.10320431 = product of:
  0.20640862 = sum of:
    0.20640862 = product of:
      0.41281724 = sum of:
        0.41281724 = weight(_text_:transaction in 4616) [ClassicSimilarity], result of:
          0.41281724 = score(doc=4616,freq=2.0), product of:
            0.34995425 = queryWeight, product of:
              6.6730065 = idf(docFreq=151, maxDocs=44218)
              0.052443266 = queryNorm
            1.1796321 = fieldWeight in 4616, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              6.6730065 = idf(docFreq=151, maxDocs=44218)
              0.125 = fieldNorm(doc=4616)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
  12. Zink, D.: Monitoring user search success through transaction log analysis : the WolfPAC example (1991) 0.10 
    0.10320431 = product of:
  0.20640862 = sum of:
    0.20640862 = product of:
      0.41281724 = sum of:
        0.41281724 = weight(_text_:transaction in 6040) [ClassicSimilarity], result of:
          0.41281724 = score(doc=6040,freq=2.0), product of:
            0.34995425 = queryWeight, product of:
              6.6730065 = idf(docFreq=151, maxDocs=44218)
              0.052443266 = queryNorm
            1.1796321 = fieldWeight in 6040, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              6.6730065 = idf(docFreq=151, maxDocs=44218)
              0.125 = fieldNorm(doc=6040)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
  13. Larson, R.R.: Transaction logs : gathering information about MELVYL (1984) 0.10 
    0.10320431 = product of:
  0.20640862 = sum of:
    0.20640862 = product of:
      0.41281724 = sum of:
        0.41281724 = weight(_text_:transaction in 6042) [ClassicSimilarity], result of:
          0.41281724 = score(doc=6042,freq=2.0), product of:
            0.34995425 = queryWeight, product of:
              6.6730065 = idf(docFreq=151, maxDocs=44218)
              0.052443266 = queryNorm
            1.1796321 = fieldWeight in 6042, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              6.6730065 = idf(docFreq=151, maxDocs=44218)
              0.125 = fieldNorm(doc=6042)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
  14. Bookstein, A.; Klein, S.T.: Compression, information theory, and grammars : a unified approach (1990) 0.10 
    0.10320431 = product of:
  0.20640862 = sum of:
    0.20640862 = product of:
      0.41281724 = sum of:
        0.41281724 = weight(_text_:transaction in 2970) [ClassicSimilarity], result of:
          0.41281724 = score(doc=2970,freq=2.0), product of:
            0.34995425 = queryWeight, product of:
              6.6730065 = idf(docFreq=151, maxDocs=44218)
              0.052443266 = queryNorm
            1.1796321 = fieldWeight in 2970, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              6.6730065 = idf(docFreq=151, maxDocs=44218)
              0.125 = fieldNorm(doc=2970)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
    Source
    ACM transaction on information systems. 8(1990), S.27-49
  15. Saastamoinen, M.; Järvelin, K.: Search task features in work tasks of varying types and complexity (2017) 0.10 
    0.09871925 = product of:
  0.1974385 = sum of:
    0.1974385 = sum of:
      0.15480646 = weight(_text_:transaction in 3589) [ClassicSimilarity], result of:
        0.15480646 = score(doc=3589,freq=2.0), product of:
          0.34995425 = queryWeight, product of:
            6.6730065 = idf(docFreq=151, maxDocs=44218)
            0.052443266 = queryNorm
          0.442362 = fieldWeight in 3589, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            6.6730065 = idf(docFreq=151, maxDocs=44218)
            0.046875 = fieldNorm(doc=3589)
      0.04263203 = weight(_text_:22 in 3589) [ClassicSimilarity], result of:
        0.04263203 = score(doc=3589,freq=2.0), product of:
          0.18364738 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.052443266 = queryNorm
          0.23214069 = fieldWeight in 3589, 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=3589)
  0.5 = coord(1/2)
    Abstract
    Information searching in practice seldom is an end in itself. In work, work task (WT) performance forms the context, which information searching should serve. Therefore, information retrieval (IR) systems development/evaluation should take the WT context into account. The present paper analyzes how WT features: task complexity and task types, affect information searching in authentic work: the types of information needs, search processes, and search media. We collected data on 22 information professionals in authentic work situations in three organization types: city administration, universities, and companies. The data comprise 286 WTs and 420 search tasks (STs). The data include transaction logs, video recordings, daily questionnaires, interviews. and observation. The data were analyzed quantitatively. Even if the participants used a range of search media, most STs were simple throughout the data, and up to 42% of WTs did not include searching. WT's effects on STs are not straightforward: different WT types react differently to WT complexity. Due to the simplicity of authentic searching, the WT/ST types in interactive IR experiments should be reconsidered.
  16. Sullenger, P.: ¬A serials transaction log analysis (1997) 0.09 
    0.09122059 = product of:
  0.18244117 = sum of:
    0.18244117 = product of:
      0.36488235 = sum of:
        0.36488235 = weight(_text_:transaction in 1627) [ClassicSimilarity], result of:
          0.36488235 = score(doc=1627,freq=4.0), product of:
            0.34995425 = queryWeight, product of:
              6.6730065 = idf(docFreq=151, maxDocs=44218)
              0.052443266 = queryNorm
            1.0426573 = fieldWeight in 1627, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              6.6730065 = idf(docFreq=151, maxDocs=44218)
              0.078125 = fieldNorm(doc=1627)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
    Abstract
    A transaction log analysis of searches for serials looks at how users go about their searching (by title, subject, or keyword) and what problems they encounter, and then examines the results of those searches. Explores ways in which serials records could be improved to enhance retrieval
  17. Hunter, R.N.: Successes and failures of patrons searching the online catalog at a large academic library : a transaction log analysis (1991) 0.09 
    0.09030377 = product of:
  0.18060754 = sum of:
    0.18060754 = product of:
      0.36121508 = sum of:
        0.36121508 = weight(_text_:transaction in 489) [ClassicSimilarity], result of:
          0.36121508 = score(doc=489,freq=8.0), product of:
            0.34995425 = queryWeight, product of:
              6.6730065 = idf(docFreq=151, maxDocs=44218)
              0.052443266 = queryNorm
            1.032178 = fieldWeight in 489, product of:
              2.828427 = tf(freq=8.0), with freq of:
                8.0 = termFreq=8.0
              6.6730065 = idf(docFreq=151, maxDocs=44218)
              0.0546875 = fieldNorm(doc=489)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
    Abstract
    This article reports on a transaction log study of the BIS online catalog at North Caroline State University. Transaction logs were used to gather data on failure rates, usage patterns, and causes of problems. The result show that 54 percent of the searches analyzed failed. Subject searching was the most often used but least successful search. Problems experienced by patrons searching BIS were often due to a misunderstanding of how to operate the system, typographical errors, and the use of uncontrolled vocabulary. As in earlier studies, transaction logs analysis proved to be a fruitful and practical methodology for studying users' searching behaviour in an online catalog.
  18. Transaction log analysis (1993) 0.09 
    0.09030377 = product of:
  0.18060754 = sum of:
    0.18060754 = product of:
      0.36121508 = sum of:
        0.36121508 = weight(_text_:transaction in 5308) [ClassicSimilarity], result of:
          0.36121508 = score(doc=5308,freq=8.0), product of:
            0.34995425 = queryWeight, product of:
              6.6730065 = idf(docFreq=151, maxDocs=44218)
              0.052443266 = queryNorm
            1.032178 = fieldWeight in 5308, product of:
              2.828427 = tf(freq=8.0), with freq of:
                8.0 = termFreq=8.0
              6.6730065 = idf(docFreq=151, maxDocs=44218)
              0.0546875 = fieldNorm(doc=5308)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
    Abstract
    For the purposes of library and information science research, transaction lof analysis can be narrowly defined as the study of electronically recorded interactions between online information retrieval systems and the persons who search for the information found in those systems. Researchers most often use transaction log data with the intention of improving an information retrieval system, human utilization of the system, and human (and perhaps also system) understanding of how the system is used by information seekers. Transaction log analysis can provide system designers and managers with valuable information about how the system is being employed by actual users. It also can be used to study prototype systems or potential system improvements
  19. Blecic, D.D.: Using transaction log analysis to improve OPAC retrieval results (1998) 0.09 
    0.09030377 = product of:
  0.18060754 = sum of:
    0.18060754 = product of:
      0.36121508 = sum of:
        0.36121508 = weight(_text_:transaction in 1444) [ClassicSimilarity], result of:
          0.36121508 = score(doc=1444,freq=8.0), product of:
            0.34995425 = queryWeight, product of:
              6.6730065 = idf(docFreq=151, maxDocs=44218)
              0.052443266 = queryNorm
            1.032178 = fieldWeight in 1444, product of:
              2.828427 = tf(freq=8.0), with freq of:
                8.0 = termFreq=8.0
              6.6730065 = idf(docFreq=151, maxDocs=44218)
              0.0546875 = fieldNorm(doc=1444)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
    Abstract
    Reports results of the work of the Transaction Logs Task Force, composed of public and technical services librarians charged with reviewing OPAC to identify library wide problems and issues. This OPAC transaction log analysis study compared data derived from 2 sets of logs within a 6 month period. Analysis of the first set of data revealed that users experienced difficulty with basic searching techniques. The OPAC introductory screens were simplified and clarified to help users improve search success rates. The second set of data, analyzed after screen changes had been made, showed statistically significant differences in search results. Concludes that regular monitoring of OPACs through transaction log analysis can lead to improved retrieval when changes are made in response to an analysis of user search patterns
  20. Ciliberti, A.: Empty handed? : a material availability study and transaction log analysis verification (1998) 0.09 
    0.09030377 = product of:
  0.18060754 = sum of:
    0.18060754 = product of:
      0.36121508 = sum of:
        0.36121508 = weight(_text_:transaction in 3898) [ClassicSimilarity], result of:
          0.36121508 = score(doc=3898,freq=2.0), product of:
            0.34995425 = queryWeight, product of:
              6.6730065 = idf(docFreq=151, maxDocs=44218)
              0.052443266 = queryNorm
            1.032178 = fieldWeight in 3898, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              6.6730065 = idf(docFreq=151, maxDocs=44218)
              0.109375 = fieldNorm(doc=3898)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Authors

Years

Languages

Types

  • a 3182
  • m 349
  • el 164
  • s 144
  • b 39
  • x 35
  • i 23
  • r 18
  • ? 8
  • p 4
  • d 3
  • n 3
  • u 2
  • z 2
  • au 1
  • h 1
  • More… Less…

Themes

Subjects

Classifications