Search (100 results, page 5 of 5)

0.0022989952 = product of:
  0.006896985 = sum of:
    0.006896985 = weight(_text_:a in 1493) [ClassicSimilarity], result of:
      0.006896985 = score(doc=1493,freq=6.0), product of:
        0.05209492 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.045180224 = queryNorm
        0.13239266 = fieldWeight in 1493, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.046875 = fieldNorm(doc=1493)
  0.33333334 = coord(1/3)

Abstract

Describes the OKAPI projects and OKAPI's development as an experimental online catalogue system over 10 years, first at the University of Westminster (formerly the Polytechnique of Central London) and subsequently at City University, London. The 1st OKAPI project in 1984 introduced 'best match' retrieval and focused on the user interface design. The 2nd investigated word stemming, spelling correction and cross reference tables as retrieval aids. A comparative study of 2 library catalogues was undertaken in 1987, while in 1988 query expansion and relevance feedback were introduced and evaluated by laboratory tests. In 1990 live evaluation of automatic query expansion was carried out and in 1993 subject enhancement of bibliographic records was investigated. The latest project has examined the design of a graphical user interface to support interactive query expansion. Discusses the research and evaluation of each project

Type

a

0.002212209 = product of:
  0.0066366266 = sum of:
    0.0066366266 = weight(_text_:a in 277) [ClassicSimilarity], result of:
      0.0066366266 = score(doc=277,freq=2.0), product of:
        0.05209492 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.045180224 = queryNorm
        0.12739488 = fieldWeight in 277, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.078125 = fieldNorm(doc=277)
  0.33333334 = coord(1/3)

Type

a

0.002212209 = product of:
  0.0066366266 = sum of:
    0.0066366266 = weight(_text_:a in 7444) [ClassicSimilarity], result of:
      0.0066366266 = score(doc=7444,freq=2.0), product of:
        0.05209492 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.045180224 = queryNorm
        0.12739488 = fieldWeight in 7444, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.078125 = fieldNorm(doc=7444)
  0.33333334 = coord(1/3)

Type

a

0.002212209 = product of:
  0.0066366266 = sum of:
    0.0066366266 = weight(_text_:a in 188) [ClassicSimilarity], result of:
      0.0066366266 = score(doc=188,freq=2.0), product of:
        0.05209492 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.045180224 = queryNorm
        0.12739488 = fieldWeight in 188, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.078125 = fieldNorm(doc=188)
  0.33333334 = coord(1/3)

Type

a

0.0021899752 = product of:
  0.0065699257 = sum of:
    0.0065699257 = weight(_text_:a in 2769) [ClassicSimilarity], result of:
      0.0065699257 = score(doc=2769,freq=4.0), product of:
        0.05209492 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.045180224 = queryNorm
        0.12611452 = fieldWeight in 2769, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.0546875 = fieldNorm(doc=2769)
  0.33333334 = coord(1/3)

Abstract

The study assessed the ability of children to categorise concepts that will be used to organise an information retrieval interface. The work was done of Project SEED (Science for Early Educational Development), a project to develop hands-on science programmes for elementary schools. Aims to tailor an interface to the particular skills of children in organising science knowledge. The results are promising for the design of IR interfaces based on children's abilities to manipulate information.

0.0021899752 = product of:
  0.0065699257 = sum of:
    0.0065699257 = weight(_text_:a in 3378) [ClassicSimilarity], result of:
      0.0065699257 = score(doc=3378,freq=4.0), product of:
        0.05209492 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.045180224 = queryNorm
        0.12611452 = fieldWeight in 3378, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.0546875 = fieldNorm(doc=3378)
  0.33333334 = coord(1/3)

Abstract

Reports and combines the results of 2 assessments of full bibliographic displays in the online catalogue of academic libraries. The first assessment evaluated displays in 12 OPACs while the second evaluated displays in 10 WWW based catalogues. Displays were evaluated against a checklist of desirable features derived from published display guidelines. Results showed that, on average, displays in OPACs scored 58% and displays in Web catalogues scored 60%. Discusses some of the weaknesses identified by the assessments, focusing on those found in the majority of the displays evaluated

Type

a

0.0021899752 = product of:
  0.0065699257 = sum of:
    0.0065699257 = weight(_text_:a in 3379) [ClassicSimilarity], result of:
      0.0065699257 = score(doc=3379,freq=4.0), product of:
        0.05209492 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.045180224 = queryNorm
        0.12611452 = fieldWeight in 3379, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.0546875 = fieldNorm(doc=3379)
  0.33333334 = coord(1/3)

Abstract

Reports results of an evaluation study of 3 WWW based prototypes for bibliographic displays developed as part of an ongoing research project at the Faculty of Information Studies, Toronto University. The development of these prototypes builds upon results obtained in earlier phases of the project that addressed issues of both the content and form of bibliographic displays in OPACs. Anticipation of continued growth in the number of catalogues available through the WWW, combined with research evidence that existing Web based displays have not shown improvement over their text based counterparts, motivated the development of these prototypes for use on the Web. Reports findings from a focus group evaluation of the 3 prototypes and makes suggestions for future research

Type

a

0.00197866 = product of:
  0.00593598 = sum of:
    0.00593598 = weight(_text_:a in 2659) [ClassicSimilarity], result of:
      0.00593598 = score(doc=2659,freq=10.0), product of:
        0.05209492 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.045180224 = queryNorm
        0.11394546 = fieldWeight in 2659, product of:
          3.1622777 = tf(freq=10.0), with freq of:
            10.0 = termFreq=10.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.03125 = fieldNorm(doc=2659)
  0.33333334 = coord(1/3)

Abstract

The paper presents findings based on user feedback and opinion of online public access catalogues as tools for finding, identifying, and selecting bibliographic materials in a public library setting. Participants spoke their thoughts aloud while conducting known-item searches. The findings describe an iterative process of action, observation, identification, and emotion.

Content

1. Introduction Significant research in the design and use of online public access catalogues (OPACs) has been conducted by professionals in library and information science (Borgman, 1996; Carlyle, 2001, Carlyle & Timmons, 2002; Hancock, 1987). However, only limited research has addressed actual library user interaction with and perceptions of online catalogue displays and bibliographic elements (Abrera, 1986; Luk, 1996; Markey, 1983). Retrieval systems, specifically online library catalogues, should consider user perceptions and expectations as an important aspect of design and implementation for improved catalogue efficiency (Hert, 1996). Therefore, it is necessary to examine the online catalogue from a user perspective to determine if it is currently succeeding in meeting the bibliographic needs of users in terms of description, display, navigation, and to provide principles for design of future OPACs. A study seeking to understand better how public library users interact with general OPAC displays and the more specific displays of bibliographic information was conducted in 2003. Research questions focused an 1) user perceptions of the OPAC, 2) the elements in a bibliographic display standing out as most important in selection and identification, and 3) user feedback an the process of using the OPAC. The purpose of this paper is to highlight the larger study findings having implications for future research and online catalogue design.

Type

a

0.0019158293 = product of:
  0.005747488 = sum of:
    0.005747488 = weight(_text_:a in 5067) [ClassicSimilarity], result of:
      0.005747488 = score(doc=5067,freq=6.0), product of:
        0.05209492 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.045180224 = queryNorm
        0.11032722 = fieldWeight in 5067, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.0390625 = fieldNorm(doc=5067)
  0.33333334 = coord(1/3)

Abstract

Existing Online Public Access Catalogues (OPACs) demonstrate differences in the range and complexity of their functional features, terminology, and help facilities. Many libraries already have OPACs and many of them have a need for guidelines that help them to design or redesign the displays for their OPACs, taking their users' needs into account. This book provides such guidelines, recommendations and a corpus of good practice to assist libraries in this process. The audience for these guidelines is librarians charged with customising OPAC software and vendors and producers of this software. The guidelines are mainly designed for general libraries with collections of resources in the humanities, the social sciences, and the pure and applied sciences. They are intended to apply to any type of catalogue, independently of the kind of interface and technology used. This is the Final Report of a Task Force an the matter, which was approved by the Standing Committee of the IFLA Cataloguing Section.

0.0018771215 = product of:
  0.0056313644 = sum of:
    0.0056313644 = weight(_text_:a in 2782) [ClassicSimilarity], result of:
      0.0056313644 = score(doc=2782,freq=4.0), product of:
        0.05209492 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.045180224 = queryNorm
        0.10809815 = fieldWeight in 2782, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.046875 = fieldNorm(doc=2782)
  0.33333334 = coord(1/3)

Abstract

Current research on user interfaces to online public access catalogs is reviewed in an attempt to identify research methods and findings applicable to the design of effective user interfaces to online public access catalogs. A broad definition of user interface is employed which includes data structures, in addition to searching and indexing software. The following features of online public access catalogs are discussed: the demonstration of relationships between records, the provision of entry vocabularies, the arrangement of multiple entries on the screen, the provision of access points, the display of single records, and the division of the catalog into separate files or indexes. For each feature, user studies and other research on online public access catalogs are reviewed and those findings summarized which provide insight into user needs concerning that particular feature; issues are identified and directions for further research are suggested. Implications for cataloging codes and standards and system design are discussed

Type

a

0.0017697671 = product of:
  0.0053093014 = sum of:
    0.0053093014 = weight(_text_:a in 3672) [ClassicSimilarity], result of:
      0.0053093014 = score(doc=3672,freq=2.0), product of:
        0.05209492 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.045180224 = queryNorm
        0.10191591 = fieldWeight in 3672, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.0625 = fieldNorm(doc=3672)
  0.33333334 = coord(1/3)

Type

a

0.0017697671 = product of:
  0.0053093014 = sum of:
    0.0053093014 = weight(_text_:a in 6957) [ClassicSimilarity], result of:
      0.0053093014 = score(doc=6957,freq=2.0), product of:
        0.05209492 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.045180224 = queryNorm
        0.10191591 = fieldWeight in 6957, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.0625 = fieldNorm(doc=6957)
  0.33333334 = coord(1/3)

Type

a

0.0017697671 = product of:
  0.0053093014 = sum of:
    0.0053093014 = weight(_text_:a in 8476) [ClassicSimilarity], result of:
      0.0053093014 = score(doc=8476,freq=2.0), product of:
        0.05209492 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.045180224 = queryNorm
        0.10191591 = fieldWeight in 8476, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.0625 = fieldNorm(doc=8476)
  0.33333334 = coord(1/3)

Type

a

0.0017697671 = product of:
  0.0053093014 = sum of:
    0.0053093014 = weight(_text_:a in 1385) [ClassicSimilarity], result of:
      0.0053093014 = score(doc=1385,freq=2.0), product of:
        0.05209492 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.045180224 = queryNorm
        0.10191591 = fieldWeight in 1385, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.0625 = fieldNorm(doc=1385)
  0.33333334 = coord(1/3)

Type

a

0.0017697671 = product of:
  0.0053093014 = sum of:
    0.0053093014 = weight(_text_:a in 2111) [ClassicSimilarity], result of:
      0.0053093014 = score(doc=2111,freq=2.0), product of:
        0.05209492 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.045180224 = queryNorm
        0.10191591 = fieldWeight in 2111, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.0625 = fieldNorm(doc=2111)
  0.33333334 = coord(1/3)

Type

a

0.0017697671 = product of:
  0.0053093014 = sum of:
    0.0053093014 = weight(_text_:a in 1590) [ClassicSimilarity], result of:
      0.0053093014 = score(doc=1590,freq=2.0), product of:
        0.05209492 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.045180224 = queryNorm
        0.10191591 = fieldWeight in 1590, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.0625 = fieldNorm(doc=1590)
  0.33333334 = coord(1/3)

Type

a

0.0017697671 = product of:
  0.0053093014 = sum of:
    0.0053093014 = weight(_text_:a in 5069) [ClassicSimilarity], result of:
      0.0053093014 = score(doc=5069,freq=8.0), product of:
        0.05209492 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.045180224 = queryNorm
        0.10191591 = fieldWeight in 5069, product of:
          2.828427 = tf(freq=8.0), with freq of:
            8.0 = termFreq=8.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.03125 = fieldNorm(doc=5069)
  0.33333334 = coord(1/3)

Abstract

Several studies on OPACs have been made since the early 1980s. However, OPAC development has been governed by systems designers, bibliographic networks and technical services librarians, but not necessarily according to user needs. Existing OPACs demonstrate differences, for example, in the range and complexity of their functional features, terminology and help facilities. While many libraries have already established their own OPACs, there is a need to bring together in the form of guidelines or recommendations a corpus of good practice to assist libraries to design or re-design their OPACs.
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.0015485462 = product of:
  0.0046456386 = sum of:
    0.0046456386 = weight(_text_:a in 2255) [ClassicSimilarity], result of:
      0.0046456386 = score(doc=2255,freq=2.0), product of:
        0.05209492 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.045180224 = queryNorm
        0.089176424 = fieldWeight in 2255, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.0546875 = fieldNorm(doc=2255)
  0.33333334 = coord(1/3)

Type

a

0.0013273255 = product of:
  0.0039819763 = sum of:
    0.0039819763 = weight(_text_:a in 2767) [ClassicSimilarity], result of:
      0.0039819763 = score(doc=2767,freq=2.0), product of:
        0.05209492 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.045180224 = queryNorm
        0.07643694 = fieldWeight in 2767, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.046875 = fieldNorm(doc=2767)
  0.33333334 = coord(1/3)

Type

a

8.848836E-4 = product of:
  0.0026546507 = sum of:
    0.0026546507 = weight(_text_:a in 692) [ClassicSimilarity], result of:
      0.0026546507 = score(doc=692,freq=2.0), product of:
        0.05209492 = queryWeight, product of:
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.045180224 = queryNorm
        0.050957955 = fieldWeight in 692, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.153047 = idf(docFreq=37942, maxDocs=44218)
          0.03125 = fieldNorm(doc=692)
  0.33333334 = coord(1/3)

Type

a