Search (7 results, page 1 of 1)

0.0061666453 = product of:
  0.024666581 = sum of:
    0.024666581 = product of:
      0.049333163 = sum of:
        0.049333163 = weight(_text_:22 in 132) [ClassicSimilarity], result of:
          0.049333163 = score(doc=132,freq=2.0), product of:
            0.15938555 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.045514934 = queryNorm
            0.30952093 = fieldWeight in 132, 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=132)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Date

10. 9.2000 17:38:22

0.0059357807 = product of:
  0.023743123 = sum of:
    0.023743123 = product of:
      0.047486246 = sum of:
        0.047486246 = weight(_text_:software in 2782) [ClassicSimilarity], result of:
          0.047486246 = score(doc=2782,freq=2.0), product of:
            0.18056466 = queryWeight, product of:
              3.9671519 = idf(docFreq=2274, maxDocs=44218)
              0.045514934 = queryNorm
            0.2629875 = fieldWeight in 2782, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.9671519 = idf(docFreq=2274, maxDocs=44218)
              0.046875 = fieldNorm(doc=2782)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

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

0.005395815 = product of:
  0.02158326 = sum of:
    0.02158326 = product of:
      0.04316652 = sum of:
        0.04316652 = weight(_text_:22 in 735) [ClassicSimilarity], result of:
          0.04316652 = score(doc=735,freq=2.0), product of:
            0.15938555 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.045514934 = queryNorm
            0.2708308 = fieldWeight in 735, 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=735)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Footnote

Vgl. auch: Pt.2: Cataloging and classification quarterly. 19(1994) no.2, S.5-22; Pt.3: Cataloging and classification quarterly. 20(1995) no.1, S.25-46; Pt.4: Cataloging and classification quarterly. 20(1995) no.2, S.3-24

0.0046249838 = product of:
  0.018499935 = sum of:
    0.018499935 = product of:
      0.03699987 = sum of:
        0.03699987 = weight(_text_:22 in 4503) [ClassicSimilarity], result of:
          0.03699987 = score(doc=4503,freq=2.0), product of:
            0.15938555 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.045514934 = queryNorm
            0.23214069 = fieldWeight in 4503, 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=4503)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Footnote

Vgl. auch: Pt.1: Cataloging and classification quarterly. 19(1994) no.1, S.9-28; Pt.2: Cataloging and classification quarterly. 19(1994) no.2, S.5-22; Pt.4: Cataloging and classification quarterly. 20(1995) no.2, S.3-24

0.0046249838 = product of:
  0.018499935 = sum of:
    0.018499935 = product of:
      0.03699987 = sum of:
        0.03699987 = weight(_text_:22 in 5945) [ClassicSimilarity], result of:
          0.03699987 = score(doc=5945,freq=2.0), product of:
            0.15938555 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.045514934 = queryNorm
            0.23214069 = fieldWeight in 5945, 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=5945)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Source

Cataloging and classification quarterly. 19(1994) no.2, S.5-22

0.0046249838 = product of:
  0.018499935 = sum of:
    0.018499935 = product of:
      0.03699987 = sum of:
        0.03699987 = weight(_text_:22 in 595) [ClassicSimilarity], result of:
          0.03699987 = score(doc=595,freq=2.0), product of:
            0.15938555 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.045514934 = queryNorm
            0.23214069 = fieldWeight in 595, 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=595)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Footnote

Vgl. auch: Pt.1: Cataloging and classification quarterly. 19(1994) no.1, S.9-28; Pt.2: Cataloging and classification quarterly. 19(1994) no.2, S.5-22; Pt.3: Cataloging and classification quarterly. 20(1995) no.1, S.25-46.

0.0039571873 = product of:
  0.01582875 = sum of:
    0.01582875 = product of:
      0.0316575 = sum of:
        0.0316575 = weight(_text_:software in 5069) [ClassicSimilarity], result of:
          0.0316575 = score(doc=5069,freq=2.0), product of:
            0.18056466 = queryWeight, product of:
              3.9671519 = idf(docFreq=2274, maxDocs=44218)
              0.045514934 = queryNorm
            0.17532499 = fieldWeight in 5069, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.9671519 = idf(docFreq=2274, maxDocs=44218)
              0.03125 = fieldNorm(doc=5069)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

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.