Search (164 results, page 1 of 9)

  • × language_ss:"e"
  • × theme_ss:"OPAC"
  1. Sullenger, P.: ¬A serials transaction log analysis (1997) 0.04
    0.039329153 = product of:
      0.19664577 = sum of:
        0.18360695 = weight(_text_:log in 1627) [ClassicSimilarity], result of:
          0.18360695 = score(doc=1627,freq=4.0), product of:
            0.18335998 = queryWeight, product of:
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.028611459 = queryNorm
            1.001347 = fieldWeight in 1627, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.078125 = fieldNorm(doc=1627)
        0.01303882 = product of:
          0.039116457 = sum of:
            0.039116457 = weight(_text_:29 in 1627) [ClassicSimilarity], result of:
              0.039116457 = score(doc=1627,freq=2.0), product of:
                0.10064617 = queryWeight, product of:
                  3.5176873 = idf(docFreq=3565, maxDocs=44218)
                  0.028611459 = queryNorm
                0.38865322 = fieldWeight in 1627, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.5176873 = idf(docFreq=3565, maxDocs=44218)
                  0.078125 = fieldNorm(doc=1627)
          0.33333334 = coord(1/3)
      0.2 = coord(2/10)
    
    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
    Date
    29. 7.1998 10:54:49
  2. Slone, D.J.: ¬The influence of mental models and goals on search patterns during Web interaction (2002) 0.03
    0.033800628 = product of:
      0.11266876 = sum of:
        0.041234493 = weight(_text_:web in 5229) [ClassicSimilarity], result of:
          0.041234493 = score(doc=5229,freq=12.0), product of:
            0.0933738 = queryWeight, product of:
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.028611459 = queryNorm
            0.4416067 = fieldWeight in 5229, product of:
              3.4641016 = tf(freq=12.0), with freq of:
                12.0 = termFreq=12.0
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.0390625 = fieldNorm(doc=5229)
        0.06491486 = weight(_text_:log in 5229) [ClassicSimilarity], result of:
          0.06491486 = score(doc=5229,freq=2.0), product of:
            0.18335998 = queryWeight, product of:
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.028611459 = queryNorm
            0.3540296 = fieldWeight in 5229, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.0390625 = fieldNorm(doc=5229)
        0.00651941 = product of:
          0.019558229 = sum of:
            0.019558229 = weight(_text_:29 in 5229) [ClassicSimilarity], result of:
              0.019558229 = score(doc=5229,freq=2.0), product of:
                0.10064617 = queryWeight, product of:
                  3.5176873 = idf(docFreq=3565, maxDocs=44218)
                  0.028611459 = queryNorm
                0.19432661 = fieldWeight in 5229, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.5176873 = idf(docFreq=3565, maxDocs=44218)
                  0.0390625 = fieldNorm(doc=5229)
          0.33333334 = coord(1/3)
      0.3 = coord(3/10)
    
    Abstract
    Thirty-one patrons, who were selected by Slone to provide a range of age and experience, agreed when approached while using the catalog of the Wake County library system to try searching via the Internet. Fifteen searched the Wake County online catalog in this manner and 16 searched the World Wide Web, including that catalog. They were subjected to brief pre-structured taped interviews before and after their searches and observed during the searching process resulting in a log of behaviors, comments, pages accessed, and time spent. Data were analyzed across participants and categories. Web searches were characterized as linking, URL, search engine, within a site domain, and searching a web catalog; and participants by the number of these techniques used. Four used only one, 13 used two, 11 used three, two used four, and one all five. Participant experience was characterized as never used, used search engines, browsing experience, email experience, URL experience, catalog experience, and finally chat room/newsgroup experience. Sixteen percent of the participants had never used the Internet, 71% had used search engines, 65% had browsed, 58% had used email, 39% had used URLs, 39% had used online catalogs, and 32% had used chat rooms. The catalog was normally consulted before the web, where both were used, and experience with an online catalog assists in web use. Scrolling was found to be unpopular and practiced halfheartedly.
    Date
    21. 7.2006 11:26:29
  3. Peters, T.A.: ¬The history and development of transaction log analysis (1993) 0.02
    0.022032835 = product of:
      0.22032835 = sum of:
        0.22032835 = weight(_text_:log in 5309) [ClassicSimilarity], result of:
          0.22032835 = score(doc=5309,freq=4.0), product of:
            0.18335998 = queryWeight, product of:
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.028611459 = queryNorm
            1.2016163 = fieldWeight in 5309, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.09375 = fieldNorm(doc=5309)
      0.1 = coord(1/10)
    
    Abstract
    Reviews the literature of transaction log analysis, looking at the types of situations, events, and users studied
  4. Sandore, B.: Applying the results of transaction log analysis (1993) 0.02
    0.022032835 = product of:
      0.22032835 = sum of:
        0.22032835 = weight(_text_:log in 5312) [ClassicSimilarity], result of:
          0.22032835 = score(doc=5312,freq=4.0), product of:
            0.18335998 = queryWeight, product of:
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.028611459 = queryNorm
            1.2016163 = fieldWeight in 5312, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.09375 = fieldNorm(doc=5312)
      0.1 = coord(1/10)
    
    Abstract
    Explores the different applications for the results of a transaction log analysis, including administration, public services, technical services, collection management, and systems development
  5. Tolle, J.: Current utilisation of online catalogs : transaction log analysis: final report to the Council on Library Resources (1983) 0.02
    0.020772757 = product of:
      0.20772757 = sum of:
        0.20772757 = weight(_text_:log in 3907) [ClassicSimilarity], result of:
          0.20772757 = score(doc=3907,freq=2.0), product of:
            0.18335998 = queryWeight, product of:
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.028611459 = queryNorm
            1.1328948 = fieldWeight in 3907, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.125 = fieldNorm(doc=3907)
      0.1 = coord(1/10)
    
  6. Zink, D.: Monitoring user search success through transaction log analysis : the WolfPAC example (1991) 0.02
    0.020772757 = product of:
      0.20772757 = sum of:
        0.20772757 = weight(_text_:log in 6040) [ClassicSimilarity], result of:
          0.20772757 = score(doc=6040,freq=2.0), product of:
            0.18335998 = queryWeight, product of:
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.028611459 = queryNorm
            1.1328948 = fieldWeight in 6040, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.125 = fieldNorm(doc=6040)
      0.1 = coord(1/10)
    
  7. Moulaison, H.L.: OPAC queries at a medium-sized academic library : a transaction log analysis (2008) 0.02
    0.019985175 = product of:
      0.099925876 = sum of:
        0.09088081 = weight(_text_:log in 3599) [ClassicSimilarity], result of:
          0.09088081 = score(doc=3599,freq=2.0), product of:
            0.18335998 = queryWeight, product of:
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.028611459 = queryNorm
            0.49564147 = fieldWeight in 3599, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.0546875 = fieldNorm(doc=3599)
        0.009045068 = product of:
          0.027135205 = sum of:
            0.027135205 = weight(_text_:22 in 3599) [ClassicSimilarity], result of:
              0.027135205 = score(doc=3599,freq=2.0), product of:
                0.10019246 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.028611459 = 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.33333334 = coord(1/3)
      0.2 = coord(2/10)
    
    Date
    10. 9.2000 17:38:22
  8. Davis, E.; Stone, J.: ¬A painless route on to the Web : Web services 1: The Royal Postgraduate Medical School (1997) 0.02
    0.01592547 = product of:
      0.07962735 = sum of:
        0.038090795 = weight(_text_:web in 1632) [ClassicSimilarity], result of:
          0.038090795 = score(doc=1632,freq=4.0), product of:
            0.0933738 = queryWeight, product of:
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.028611459 = queryNorm
            0.4079388 = fieldWeight in 1632, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.0625 = fieldNorm(doc=1632)
        0.041536555 = product of:
          0.06230483 = sum of:
            0.031293165 = weight(_text_:29 in 1632) [ClassicSimilarity], result of:
              0.031293165 = score(doc=1632,freq=2.0), product of:
                0.10064617 = queryWeight, product of:
                  3.5176873 = idf(docFreq=3565, maxDocs=44218)
                  0.028611459 = queryNorm
                0.31092256 = fieldWeight in 1632, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.5176873 = idf(docFreq=3565, maxDocs=44218)
                  0.0625 = fieldNorm(doc=1632)
            0.031011663 = weight(_text_:22 in 1632) [ClassicSimilarity], result of:
              0.031011663 = score(doc=1632,freq=2.0), product of:
                0.10019246 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.028611459 = queryNorm
                0.30952093 = fieldWeight in 1632, 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=1632)
          0.6666667 = coord(2/3)
      0.2 = coord(2/10)
    
    Date
    29. 7.1998 21:22:27
  9. Transaction log analysis (1993) 0.02
    0.015741019 = product of:
      0.15741017 = sum of:
        0.15741017 = weight(_text_:log in 5308) [ClassicSimilarity], result of:
          0.15741017 = score(doc=5308,freq=6.0), product of:
            0.18335998 = queryWeight, product of:
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.028611459 = queryNorm
            0.85847616 = fieldWeight in 5308, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.0546875 = fieldNorm(doc=5308)
      0.1 = coord(1/10)
    
    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
  10. Blecic, D.D.: Using transaction log analysis to improve OPAC retrieval results (1998) 0.02
    0.015741019 = product of:
      0.15741017 = sum of:
        0.15741017 = weight(_text_:log in 1444) [ClassicSimilarity], result of:
          0.15741017 = score(doc=1444,freq=6.0), product of:
            0.18335998 = queryWeight, product of:
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.028611459 = queryNorm
            0.85847616 = fieldWeight in 1444, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.0546875 = fieldNorm(doc=1444)
      0.1 = coord(1/10)
    
    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
  11. Kaske, N.K.: Research methodologies and transaction log analysis : issues, questions, and a proposed model (1993) 0.02
    0.015579566 = product of:
      0.15579566 = sum of:
        0.15579566 = weight(_text_:log in 5311) [ClassicSimilarity], result of:
          0.15579566 = score(doc=5311,freq=2.0), product of:
            0.18335998 = queryWeight, product of:
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.028611459 = queryNorm
            0.84967107 = fieldWeight in 5311, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.09375 = fieldNorm(doc=5311)
      0.1 = coord(1/10)
    
  12. Harmsen, B.: Adding value to Web-OPACs (2000) 0.01
    0.014946125 = product of:
      0.07473063 = sum of:
        0.053868517 = weight(_text_:web in 4672) [ClassicSimilarity], result of:
          0.053868517 = score(doc=4672,freq=2.0), product of:
            0.0933738 = queryWeight, product of:
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.028611459 = queryNorm
            0.5769126 = fieldWeight in 4672, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.125 = fieldNorm(doc=4672)
        0.02086211 = product of:
          0.06258633 = sum of:
            0.06258633 = weight(_text_:29 in 4672) [ClassicSimilarity], result of:
              0.06258633 = score(doc=4672,freq=2.0), product of:
                0.10064617 = queryWeight, product of:
                  3.5176873 = idf(docFreq=3565, maxDocs=44218)
                  0.028611459 = queryNorm
                0.6218451 = fieldWeight in 4672, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.5176873 = idf(docFreq=3565, maxDocs=44218)
                  0.125 = fieldNorm(doc=4672)
          0.33333334 = coord(1/3)
      0.2 = coord(2/10)
    
    Date
    28. 3.2002 10:08:29
  13. McCurley, H.H.; Weisbrod, E.J.: Use of series title authority cross-references at a large university library (1996) 0.01
    0.014688556 = product of:
      0.14688556 = sum of:
        0.14688556 = weight(_text_:log in 5544) [ClassicSimilarity], result of:
          0.14688556 = score(doc=5544,freq=4.0), product of:
            0.18335998 = queryWeight, product of:
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.028611459 = queryNorm
            0.80107754 = fieldWeight in 5544, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.0625 = fieldNorm(doc=5544)
      0.1 = coord(1/10)
    
    Abstract
    Reports results of a study, conducted at the Ralph Brown Draughton Library, Auburn University, Alabama, to determine whether users employ the cross references provided by the series title authority file in their searches of the library's OPAC. Presents and discusses the results of a transaction log analysis focusing attention on the usefulness of cross references from series title authority records, since only searches that required such cross reference appeared in the transaction log report. Results indicate that users do use the cross references gathered by series title authority records
  14. Dickson, J.: ¬An analysis of user errors in searching an online catalog (1984) 0.01
    0.012982972 = product of:
      0.12982972 = sum of:
        0.12982972 = weight(_text_:log in 316) [ClassicSimilarity], result of:
          0.12982972 = score(doc=316,freq=2.0), product of:
            0.18335998 = queryWeight, product of:
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.028611459 = queryNorm
            0.7080592 = fieldWeight in 316, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.078125 = fieldNorm(doc=316)
      0.1 = coord(1/10)
    
    Abstract
    The study extracts a sample of zero-hit author and title searches from the transaction log of Northwestern University Library's online catalog. It analyzes why the searches failed, in an effort to understand the users' conceptual model of the online catalog.
  15. Hunter, R.N.: Successes and failures of patrons searching the online catalog at a large academic library : a transaction log analysis (1991) 0.01
    0.012852487 = product of:
      0.12852487 = sum of:
        0.12852487 = weight(_text_:log in 489) [ClassicSimilarity], result of:
          0.12852487 = score(doc=489,freq=4.0), product of:
            0.18335998 = queryWeight, product of:
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.028611459 = queryNorm
            0.7009429 = fieldWeight in 489, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.0546875 = fieldNorm(doc=489)
      0.1 = coord(1/10)
    
    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.
  16. Peters, T.A.: When smart people fail : an analysis of the transaction log of an online public access catalog (1989) 0.01
    0.012852487 = product of:
      0.12852487 = sum of:
        0.12852487 = weight(_text_:log in 2283) [ClassicSimilarity], result of:
          0.12852487 = score(doc=2283,freq=4.0), product of:
            0.18335998 = queryWeight, product of:
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.028611459 = queryNorm
            0.7009429 = fieldWeight in 2283, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.0546875 = fieldNorm(doc=2283)
      0.1 = coord(1/10)
    
    Abstract
    This article reports on a low-cost study of the transaction log of an online public access catalog at an academic library. The three goals of the study were to determine failure rates, to study usage patterns, and to investigate problable causes of patron problems when using the OPAC. The study found that failure rates (defined as those searches that produced zero hits) of approximately 40% are common, and that usage patterns and failure rates do not vary greatly over time or from terminal to terminal, but that the distribution of probable causes of user problems varies significantly from terminal to terminal
  17. Wyly, B.J.: From access point to materials : a transaction log analysis of access point value for online catalog users (1996) 0.01
    0.011243585 = product of:
      0.11243584 = sum of:
        0.11243584 = weight(_text_:log in 7237) [ClassicSimilarity], result of:
          0.11243584 = score(doc=7237,freq=6.0), product of:
            0.18335998 = queryWeight, product of:
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.028611459 = queryNorm
            0.61319727 = fieldWeight in 7237, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.0390625 = fieldNorm(doc=7237)
      0.1 = coord(1/10)
    
    Abstract
    Reports results of a study to investigate judgements made by searchers of online catalogues by using transaction log analysis to associate online catalogue searchmethods with decisions so as to retrieve location information. The study used the Mainframe Interface to Libraries Online (MILO), an interface to the Illinois Library Computer Systems Office (ILCSO) online union catalogue for the 45 academic libraries belonging to ILCSO. MILO provides access to a bibliographic database and directly links to another database with circulation and location records. As the latter database only provides location and circulation status, searchers' decisions to make links to such data are seen as an indication that the records being linked represent potentially useful material. Via a transaction log analysis, the linked location records were associated wiht the access points used to retrieve them in order to analyze the value and problems of searchers' uses of specific access points. Transaction logs were analyzed for a 38-day sample of the 1994 logs. Counting of records retrieved through the use of multiple access points (making the total greater than 100%), subject fields were used to access over 30%, author fields to access over 19%, and title fields to access over 51% of all records linked to location information. Other fields were used to retrieve very small percentages of linked records
  18. Web services from special libraries (1997) 0.01
    0.011209594 = product of:
      0.05604797 = sum of:
        0.040401388 = weight(_text_:web in 1634) [ClassicSimilarity], result of:
          0.040401388 = score(doc=1634,freq=2.0), product of:
            0.0933738 = queryWeight, product of:
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.028611459 = queryNorm
            0.43268442 = fieldWeight in 1634, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.2635105 = idf(docFreq=4597, maxDocs=44218)
              0.09375 = fieldNorm(doc=1634)
        0.015646582 = product of:
          0.046939746 = sum of:
            0.046939746 = weight(_text_:29 in 1634) [ClassicSimilarity], result of:
              0.046939746 = score(doc=1634,freq=2.0), product of:
                0.10064617 = queryWeight, product of:
                  3.5176873 = idf(docFreq=3565, maxDocs=44218)
                  0.028611459 = queryNorm
                0.46638384 = fieldWeight in 1634, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.5176873 = idf(docFreq=3565, maxDocs=44218)
                  0.09375 = fieldNorm(doc=1634)
          0.33333334 = coord(1/3)
      0.2 = coord(2/10)
    
    Date
    29. 7.1998 11:32:17
  19. Bangalore, N.S.: Re-engineering the OPAC using transaction logs (1997) 0.01
    0.011016417 = product of:
      0.11016417 = sum of:
        0.11016417 = weight(_text_:log in 129) [ClassicSimilarity], result of:
          0.11016417 = score(doc=129,freq=4.0), product of:
            0.18335998 = queryWeight, product of:
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.028611459 = queryNorm
            0.60080814 = fieldWeight in 129, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.046875 = fieldNorm(doc=129)
      0.1 = coord(1/10)
    
    Abstract
    Describes an attempt, by Illinois University at Chicago (IUC) Library to respond to user needs as they are revealed in transaction logs of OPAC use. Illustrates success in improving access to catalogue records through a reengineering process. Outlines the IUC Library Reengineering Project, the administrative structure to study transaction logs, and the resultant managerial decisions. Notes the changes made to sreen display and to the OPAC. Focusing on customer satisfaction, IUC catalogue librarians joined forces with colleagues to identify Usrs' unmet needs and preferences through transaction log analysis. In order to minimize mismatches between users' expectations and services actually provided, IUC catalogue librarians studied logs and adjusted the OPAC. Descrinbes the specific efforts to increase access to the library's collections and the steps taken to enhance and customize bibliographic and authority records. Concludes that transition log analysis has enabled IUC to alter the form and content of its OPAC to fit the changing needs of diverse and widely disoersed users
  20. Burton, J.; Newport, J.; Robinson, E.: OPACs and JANET : a simple technique for easy user access (1989) 0.01
    0.0103863785 = product of:
      0.10386378 = sum of:
        0.10386378 = weight(_text_:log in 3107) [ClassicSimilarity], result of:
          0.10386378 = score(doc=3107,freq=2.0), product of:
            0.18335998 = queryWeight, product of:
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.028611459 = queryNorm
            0.5664474 = fieldWeight in 3107, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              6.4086204 = idf(docFreq=197, maxDocs=44218)
              0.0625 = fieldNorm(doc=3107)
      0.1 = coord(1/10)
    
    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

Authors

Years

Types

  • a 150
  • el 8
  • m 4
  • s 4
  • r 3
  • b 1
  • x 1
  • More… Less…