Search (14 results, page 1 of 1)

0.049055643 = product of:
  0.09811129 = sum of:
    0.09811129 = sum of:
      0.05608411 = weight(_text_:searching in 917) [ClassicSimilarity], result of:
        0.05608411 = score(doc=917,freq=2.0), product of:
          0.2091384 = queryWeight, product of:
            4.0452914 = idf(docFreq=2103, maxDocs=44218)
            0.051699217 = queryNorm
          0.26816747 = fieldWeight in 917, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            4.0452914 = idf(docFreq=2103, maxDocs=44218)
            0.046875 = fieldNorm(doc=917)
      0.04202718 = weight(_text_:22 in 917) [ClassicSimilarity], result of:
        0.04202718 = score(doc=917,freq=2.0), product of:
          0.18104185 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.051699217 = queryNorm
          0.23214069 = fieldWeight in 917, 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=917)
  0.5 = coord(1/2)

Abstract

I started my professional career in library and information science because of my great interest in knowledge organization. The more experience I gained in the profession, the more I realized how crucial it is to understand which organization would be best for each group of users. This in turn requires an understanding of how users seek information. And so now my focus is an studying information seeking and searching behavior. Throughout the relatively long course of changing my focus, I followed Pauline Cochrane's writings. Now I can say that she has been among the first to have a "user-centered approach" to knowledge organization, and she has used the term three years before it became a mainstream phrase. The following is a short discussion about the usercentered approach which was presented in a workshop in 1997.

Date

22. 9.1997 19:16:05

0.04673676 = product of:
  0.09347352 = sum of:
    0.09347352 = product of:
      0.18694703 = sum of:
        0.18694703 = weight(_text_:searching in 3696) [ClassicSimilarity], result of:
          0.18694703 = score(doc=3696,freq=2.0), product of:
            0.2091384 = queryWeight, product of:
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.051699217 = queryNorm
            0.8938915 = fieldWeight in 3696, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.15625 = fieldNorm(doc=3696)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

0.03738941 = product of:
  0.07477882 = sum of:
    0.07477882 = product of:
      0.14955764 = sum of:
        0.14955764 = weight(_text_:searching in 2679) [ClassicSimilarity], result of:
          0.14955764 = score(doc=2679,freq=2.0), product of:
            0.2091384 = queryWeight, product of:
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.051699217 = queryNorm
            0.7151132 = fieldWeight in 2679, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.125 = fieldNorm(doc=2679)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

0.03738941 = product of:
  0.07477882 = sum of:
    0.07477882 = product of:
      0.14955764 = sum of:
        0.14955764 = weight(_text_:searching in 7930) [ClassicSimilarity], result of:
          0.14955764 = score(doc=7930,freq=2.0), product of:
            0.2091384 = queryWeight, product of:
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.051699217 = queryNorm
            0.7151132 = fieldWeight in 7930, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.125 = fieldNorm(doc=7930)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

0.03271573 = product of:
  0.06543146 = sum of:
    0.06543146 = product of:
      0.13086292 = sum of:
        0.13086292 = weight(_text_:searching in 7929) [ClassicSimilarity], result of:
          0.13086292 = score(doc=7929,freq=2.0), product of:
            0.2091384 = queryWeight, product of:
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.051699217 = queryNorm
            0.6257241 = fieldWeight in 7929, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.109375 = fieldNorm(doc=7929)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

0.031351972 = product of:
  0.062703945 = sum of:
    0.062703945 = product of:
      0.12540789 = sum of:
        0.12540789 = weight(_text_:searching in 1659) [ClassicSimilarity], result of:
          0.12540789 = score(doc=1659,freq=10.0), product of:
            0.2091384 = queryWeight, product of:
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.051699217 = queryNorm
            0.59964067 = fieldWeight in 1659, product of:
              3.1622777 = tf(freq=10.0), with freq of:
                10.0 = termFreq=10.0
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.046875 = fieldNorm(doc=1659)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

The model of operationalist and conceptualist searching styles describes searching behavior of experienced online searchers. It is based on the systematic observation of five experienced online searchers doing their regular, job-related searches, and on the analysis of 10 to 13 searches conducted by each of them. Operationalist searchers aim at optimal strategies to achieve precise retrieval; they use a large range of system capabilities in their interaction. They preserve the specific meaning of the request, and the aim of their interactions is an answer set representing the request precisely. Conceptualist searchers analyze a request by seeking to fit it into a faceted structure. They first enter the facet that represents the most important aspect of the request. Their search is then centered on retrieving subsets from this primary set by introducing additional facets. In contrast to the operationalists, they are primarily concerned with recall. During the interaction they preserve the faceted structure, but may change the specific meaning of the request. Although not comprehensive, the model aids in recognizing special and individual characteristics of searching behavior which provide explanations of previous research and guidelines for further investigations into the search process

0.031351972 = product of:
  0.062703945 = sum of:
    0.062703945 = product of:
      0.12540789 = sum of:
        0.12540789 = weight(_text_:searching in 2949) [ClassicSimilarity], result of:
          0.12540789 = score(doc=2949,freq=10.0), product of:
            0.2091384 = queryWeight, product of:
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.051699217 = queryNorm
            0.59964067 = fieldWeight in 2949, product of:
              3.1622777 = tf(freq=10.0), with freq of:
                10.0 = termFreq=10.0
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.046875 = fieldNorm(doc=2949)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

This article analyzes Web searching behavior for homework assignments of high school students through field observations in class and the terminal with students thinking alound, and through interviews with various participants, including the teacher and librarian. Students performed focused searching and progressed through a search swiftly and flexibly. They used landmarks and assumed that one can always start a new search and ask for help. They were satisfied with their searches and the results, but impatient with slow response. The students enjoyed searching the Web because it had a variety of formats, it showed pictures, it covered a multitude of subjects and it provided easy access to information. Difficulties and problems students encountered emphasize the need for training to all involved, and for a system design that is based on user seeking and searching behavior

0.028332658 = product of:
  0.056665316 = sum of:
    0.056665316 = product of:
      0.11333063 = sum of:
        0.11333063 = weight(_text_:searching in 3328) [ClassicSimilarity], result of:
          0.11333063 = score(doc=3328,freq=6.0), product of:
            0.2091384 = queryWeight, product of:
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.051699217 = queryNorm
            0.541893 = fieldWeight in 3328, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.0546875 = fieldNorm(doc=3328)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Experiments in online searching behaviour have failed to explain the phenomena they were designed to study. An examination of the variables used in research to data finds the most commonly used independent variables are searcher characteristics. Search-process and search outcome variables are the most commonly dependent variables. The search process variables are inadequate because they are situational and subject to constant change. Significantly, these variables measure the cost of a search rather than the intellectual processes involved in answering a request. While these experiments could support the discovery of the 'productive searcher', they cannot uncover searching behaviour. Only in-depth analyses of the search process itself can lead to productive research

0.028042056 = product of:
  0.05608411 = sum of:
    0.05608411 = product of:
      0.11216822 = sum of:
        0.11216822 = weight(_text_:searching in 2885) [ClassicSimilarity], result of:
          0.11216822 = score(doc=2885,freq=8.0), product of:
            0.2091384 = queryWeight, product of:
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.051699217 = queryNorm
            0.53633493 = fieldWeight in 2885, product of:
              2.828427 = tf(freq=8.0), with freq of:
                8.0 = termFreq=8.0
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.046875 = fieldNorm(doc=2885)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

A review of studies about searching beganiour in image retrieval suggests that retrieval tasks may affect searching behaviour. Retrieval tasks occur along a spectrum starting with the Data Pole, which involves retrieval of images for the information which the image include, and ending with the Objects Pole, which concerns the retrieval of images as objects. Each Pole generates a certain searching behaviour which has characteristics opposing those of the other pole. These characteristics suggest that: relevance feedback may not be useful for tasks on the Object Pole; measuring precision on the Data Pole should be replaced with another measurement of effort and time, while on the Objects Pole, the quality of browsing sets and the precision of the browsing process should be measured instead of precision; and recall is not useful for the Data Pole, and requires much exploration before it can be adopted for the Object Pole. Additional research in searching behaviour and about performance measurement will improve retrieval from image databases

0.018694704 = product of:
  0.03738941 = sum of:
    0.03738941 = product of:
      0.07477882 = sum of:
        0.07477882 = weight(_text_:searching in 684) [ClassicSimilarity], result of:
          0.07477882 = score(doc=684,freq=2.0), product of:
            0.2091384 = queryWeight, product of:
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.051699217 = queryNorm
            0.3575566 = fieldWeight in 684, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.0625 = fieldNorm(doc=684)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

0.016357865 = product of:
  0.03271573 = sum of:
    0.03271573 = product of:
      0.06543146 = sum of:
        0.06543146 = weight(_text_:searching in 8259) [ClassicSimilarity], result of:
          0.06543146 = score(doc=8259,freq=2.0), product of:
            0.2091384 = queryWeight, product of:
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.051699217 = queryNorm
            0.31286204 = fieldWeight in 8259, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.0546875 = fieldNorm(doc=8259)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Two distinct approaches describe the process of indexing. The document-oriented approach claims that indexing summarizes or represents the content of a document. The user-oriented approach requires that indexing reflect the requests for which a document might be relevant. Most indexing, in practice as well as in theory, subscribe to both, but the document-oriented approach has enjoyed most viability. While request-oriented indexing is a user-centered approach, it is very difficult to implement with human, a priori indexing. Automated indexing with its dynamic and flexible nature is most fit to tailor indexing to requirements of individual users and requests, yet most of current research in the area focuses on the development of global methods. Regardless of the method, user-centered indexing cannot be developed before searching behavior is understood better

0.014021028 = product of:
  0.028042056 = sum of:
    0.028042056 = product of:
      0.05608411 = sum of:
        0.05608411 = weight(_text_:searching in 2103) [ClassicSimilarity], result of:
          0.05608411 = score(doc=2103,freq=2.0), product of:
            0.2091384 = queryWeight, product of:
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.051699217 = queryNorm
            0.26816747 = fieldWeight in 2103, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.046875 = fieldNorm(doc=2103)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Direct observations and analysis of searching behaviour of professional online searchers shed light on thesaurus requirements for an intermediary expert system - a system that mediates between online databases and end users. Examination of searchers' decisions about the selection of search keys, and of the knowledge about terminological and subject properties that are employed, illuminated the requirements for a thesaurus that will facilitate the selection of search keys. Expert knowledge is needed when: a term occurs very frequently in the database; it has many synonyms; it is ambiguous; it is vague; or its meaning is context dependent. To diagnose such terms and to give advice, a thesaurus would be used together with a variety of text sources such as databases' thesauri, machine-readable dictionaries and glossaries and the databases' text. The thesaurus would be a knowledge structure that indicates frequency data, hedges, and a classificatory structure; both intellectual and automated procedures would be used to create it. Such a knowledge structure in place would require a new approach to text analysis and to the construction of controlled vocabularies

0.014021028 = product of:
  0.028042056 = sum of:
    0.028042056 = product of:
      0.05608411 = sum of:
        0.05608411 = weight(_text_:searching in 5695) [ClassicSimilarity], result of:
          0.05608411 = score(doc=5695,freq=2.0), product of:
            0.2091384 = queryWeight, product of:
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.051699217 = queryNorm
            0.26816747 = fieldWeight in 5695, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.046875 = fieldNorm(doc=5695)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

To provide advice for online searching about term selection and query expansion, an intermediary expert system should indicate a terminological knowledge structure. Terminological attributes could provide the foundation of a knowledge base, and knowledge acquisition could rely on knowledge base techniques coupled with statistical techniques. The strategies of expert searchers would provide 1 source of knowledge. The knowledge structure would include 3 constructs for each term: frequency data, a hedge, and a position in a classification scheme. Switching vocabularies could provide a meta-scheme and facilitate the interoperability of databases in similar subjects. To develop such knowledge structure, research should focus on terminological attributes, word and phrase disambiguation, automated text processing, and the role of thesauri and classification schemes in indexing and retrieval. It should develop techniques that combine knowledge base and statistical methods and that consider user preferences

0.008755663 = product of:
  0.017511327 = sum of:
    0.017511327 = product of:
      0.035022654 = sum of:
        0.035022654 = weight(_text_:22 in 2336) [ClassicSimilarity], result of:
          0.035022654 = score(doc=2336,freq=2.0), product of:
            0.18104185 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051699217 = queryNorm
            0.19345059 = fieldWeight in 2336, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0390625 = fieldNorm(doc=2336)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

22. 9.1997 19:16:05