Search (27 results, page 2 of 2)

0.006968761 = product of:
  0.041812565 = sum of:
    0.041812565 = weight(_text_:web in 5069) [ClassicSimilarity], result of:
      0.041812565 = score(doc=5069,freq=8.0), product of:
        0.14495286 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.044416238 = queryNorm
        0.2884563 = fieldWeight in 5069, product of:
          2.828427 = tf(freq=8.0), with freq of:
            8.0 = termFreq=8.0
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.03125 = fieldNorm(doc=5069)
  0.16666667 = coord(1/6)

Abstract

As mentioned above, the guidelines are intended to apply to all types of catalogue, including Web-based catalogues, GUI-based interfaces, and Z39.50-web interfaces. The focus of the guidelines is on the display of cataloguing information (as opposed to circulation, serials check-in, fund accounting, acquisitions, or bindery information). However, some general statements are made concerning the value of displaying to users information that is drawn from these other types of records. The guidelines do not attempt to cover HELP screens, searching methods, or command names and functions. Thus, the guidelines do not directly address the difference between menu-mode access (so common now in GUI and Web interfaces) vs. command-mode access (often completely unavailable in GUI and Web interfaces). However, note that in menu-mode access, the user often has to go through many more screens to attain results than in command-mode access, and each of these screens constitutes a display. The intent is to recommend a standard set of display defaults, defined as features that should be provided for users who have not selected other options, including users who want to begin searching right away without much instruction. It is not the intent to restrict the creativity of system designers who want to build in further options to offer to advanced users (beyond the defaults), advanced users being those people who are willing to put some time into learning how to use the system in more sophisticated and complex ways. The Task Force is aware of the fact that many existing systems are not capable of following all of the recommendations in this document. We hope that existing systems will attempt to work toward the implementation of the guidelines as they develop new versions of their software in the future.

0.0065539777 = product of:
  0.039323866 = sum of:
    0.039323866 = weight(_text_:computer in 2772) [ClassicSimilarity], result of:
      0.039323866 = score(doc=2772,freq=2.0), product of:
        0.16231956 = queryWeight, product of:
          3.6545093 = idf(docFreq=3109, maxDocs=44218)
          0.044416238 = queryNorm
        0.24226204 = fieldWeight in 2772, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6545093 = idf(docFreq=3109, maxDocs=44218)
          0.046875 = fieldNorm(doc=2772)
  0.16666667 = coord(1/6)

Abstract

Reports the results of a research project, conducted by the School of Computing and Mathematics and the Library of Huddersfield Polytechnic, into the problem of matching the user interface of OPACs to the needs of users. The project brought together issues involving: Human Computer Instruction (HCI); system methods in the determinination of user requirements; and user centred design, and prototyping in a sequence of design and evaluation cycles. These cycles applied appropriate HCI styles, techniques and equipment (such as Graphical User Interface (GUI) and a mouse pointing device) and incorporated the lessons of each evaluation, to produce an OPAC user interface, ICARUS, which differs considerably in style, behaviour and characteristcs from those commonly encountered in academic and public libraries. The project concluded by evaluating ICARUS, against the BLCMP OPAC with 38 subjects in the Library of Huddersfield Polytechnic, and demonstrating a significant improvement in performance for different tasks for the ICARUS interface

0.0065539777 = product of:
  0.039323866 = sum of:
    0.039323866 = weight(_text_:computer in 5839) [ClassicSimilarity], result of:
      0.039323866 = score(doc=5839,freq=2.0), product of:
        0.16231956 = queryWeight, product of:
          3.6545093 = idf(docFreq=3109, maxDocs=44218)
          0.044416238 = queryNorm
        0.24226204 = fieldWeight in 5839, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6545093 = idf(docFreq=3109, maxDocs=44218)
          0.046875 = fieldNorm(doc=5839)
  0.16666667 = coord(1/6)

Abstract

Decribes the BookHouse, a system for the retrieval and indexing of fiction and non fiction literature developed for public and school libraries though cooperation between library and information science professionals. Discusses 3 aspects of the system: domain characteristic; task analysis; and user characteristics. Outlines the framework underlying the collection of field data with special emphasis on the work involved in transforming the empirical field studies of user behaviour in the library into computer system specifications and subsequent design of a retrieval system providing subject access to fiction. Describes a few of the many indexing policies, rules and practices which evolved for concept identification and book descriptions as well as the functionality and associated displays of the system for supporting the retrieval and indexing of fiction

0.0060976665 = product of:
  0.036585998 = sum of:
    0.036585998 = weight(_text_:web in 2198) [ClassicSimilarity], result of:
      0.036585998 = score(doc=2198,freq=2.0), product of:
        0.14495286 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.044416238 = queryNorm
        0.25239927 = fieldWeight in 2198, 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=2198)
  0.16666667 = coord(1/6)

Abstract

Over the last couple of years, there has been a surge of activity in the library automation arena directed toward improved user interfaces. As Breeding looks at the events and activities that have transpired over the last year or so, Breeding sees an incredible amount of progress in creating interfaces that help librarians compete better in an ever more crowded landscape of information providers. It's strategically important for libraries to have technologies in place that will optimize delivery of content and services in the context of today's Web. Breeding believes that failure to make progress in this area can foster a creep of irrelevancy as potential users increasingly rely on information resources provided by entities other than libraries.

0.005461648 = product of:
  0.03276989 = sum of:
    0.03276989 = weight(_text_:computer in 1300) [ClassicSimilarity], result of:
      0.03276989 = score(doc=1300,freq=2.0), product of:
        0.16231956 = queryWeight, product of:
          3.6545093 = idf(docFreq=3109, maxDocs=44218)
          0.044416238 = queryNorm
        0.20188503 = fieldWeight in 1300, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6545093 = idf(docFreq=3109, maxDocs=44218)
          0.0390625 = fieldNorm(doc=1300)
  0.16666667 = coord(1/6)

Abstract

This paper describes a new OPAC system called The Book House and discusses its relevance as a solution to current OPAC developments. The Book House is an interactive, multimedia, online public access catalogue system designed to support casual and/or novice end-users in information retrieval. It runs on a Macintosh and is available on CD-ROM and disks in English and Danish (it can be purchased from Risø for $100). It comprises an interface and module for classifying and indexing fact and fiction books in the database called Book House Write. It uses icons, text and animation in the display interface in order to enhance the utility of the system for the general public. Both words and pictures can be used for searching, which makes the system suitable for all age groups. It plays on users' previous experiencees with computer games to support learning by doing something in an enjoyable way. A prerequisite for the design of The Book House was a new approach to cognitive analysis of retrieval in libraries. Based on the success of this approach, it is claimed that OPAC systems will only be really useful and widespread (1) when their domain and task characteristics allow supplementary information to be added to existing descriptions of book content in online card catalogues in order to match end-users' intentions and needs, and (2) when the user interface and routes to the databases are configured as an integrated and uniform set of displays which match the search strategies of users, as well as their mental capabilities and limitations

0.0040118583 = product of:
  0.024071148 = sum of:
    0.024071148 = product of:
      0.048142295 = sum of:
        0.048142295 = weight(_text_:22 in 2765) [ClassicSimilarity], result of:
          0.048142295 = score(doc=2765,freq=2.0), product of:
            0.1555381 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.044416238 = 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)
  0.16666667 = coord(1/6)

Pages

S.20-22

0.0020059291 = product of:
  0.012035574 = sum of:
    0.012035574 = product of:
      0.024071148 = sum of:
        0.024071148 = weight(_text_:22 in 168) [ClassicSimilarity], result of:
          0.024071148 = score(doc=168,freq=2.0), product of:
            0.1555381 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.044416238 = queryNorm
            0.15476047 = fieldWeight in 168, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03125 = fieldNorm(doc=168)
      0.5 = coord(1/2)
  0.16666667 = coord(1/6)

Date

10. 9.2000 17:38:22