Search (5 results, page 1 of 1)

0.02100763 = product of:
  0.08403052 = sum of:
    0.08403052 = weight(_text_:assess in 1800) [ClassicSimilarity], result of:
      0.08403052 = score(doc=1800,freq=2.0), product of:
        0.36863554 = queryWeight, product of:
          5.8947687 = idf(docFreq=330, maxDocs=44218)
          0.062536046 = queryNorm
        0.22795013 = fieldWeight in 1800, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.8947687 = idf(docFreq=330, maxDocs=44218)
          0.02734375 = fieldNorm(doc=1800)
  0.25 = coord(1/4)

Abstract

The SAC Subcommittee on Subject Relationships/Reference Structures was authorized at the 1995 Midwinter Meeting and appointed shortly before Annual Conference. Its creation was one result of a discussion of how (and why) to promote the display and use of broader-term subject heading references, and its charge reads as follows: To investigate: (1) the kinds of relationships that exist between subjects, the display of which are likely to be useful to catalog users; (2) how these relationships are or could be recorded in authorities and classification formats; (3) options for how these relationships should be presented to users of online and print catalogs, indexes, lists, etc. By the summer 1996 Annual Conference, make some recommendations to SAC about how to disseminate the information and/or implement changes. At that time assess the need for additional time to investigate these issues. The Subcommittee's work on each of the imperatives in the charge was summarized in a report issued at the 1996 Annual Conference (Appendix A). Highlights of this work included the development of a taxonomy of 165 subject relationships; a demonstration that, using existing MARC coding, catalog systems could be programmed to generate references they do not currently support; and an examination of reference displays in several CD-ROM database products. Since that time, work has continued on identifying term relationships and display options; on tracking research, discussion, and implementation of subject relationships in information systems; and on compiling a list of further research needs.

0.015005451 = product of:
  0.060021803 = sum of:
    0.060021803 = weight(_text_:assess in 1211) [ClassicSimilarity], result of:
      0.060021803 = score(doc=1211,freq=2.0), product of:
        0.36863554 = queryWeight, product of:
          5.8947687 = idf(docFreq=330, maxDocs=44218)
          0.062536046 = queryNorm
        0.16282153 = fieldWeight in 1211, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.8947687 = idf(docFreq=330, maxDocs=44218)
          0.01953125 = fieldNorm(doc=1211)
  0.25 = coord(1/4)

Abstract

From the user's perspective, however, it is still difficult to use current information retrieval systems. Users frequently have problems expressing their information needs and translating those needs into queries. This is partly due to the fact that information needs cannot be expressed appropriately in systems terms. It is not unusual for users to input search terms that are different from the index terms information systems use. Various methods have been proposed to help users choose search terms and articulate queries. One widely used approach is to incorporate into the information system a thesaurus-like component that represents both the important concepts in a particular subject area and the semantic relationships among those concepts. Unfortunately, the development and use of thesauri is not without its own problems. The thesaurus employed in a specific information system has often been developed for a general subject area and needs significant enhancement to be tailored to the information system where it is to be used. This thesaurus development process, if done manually, is both time consuming and labor intensive. Usage of a thesaurus in searching is complex and may raise barriers for the user. For illustration purposes, let us consider two scenarios of thesaurus usage. In the first scenario the user inputs a search term and the thesaurus then displays a matching set of related terms. Without an overview of the thesaurus - and without the ability to see the matching terms in the context of other terms - it may be difficult to assess the quality of the related terms in order to select the correct term. In the second scenario the user browses the whole thesaurus, which is organized as in an alphabetically ordered list. The problem with this approach is that the list may be long, and neither does it show users the global semantic relationship among all the listed terms.

0.014827349 = product of:
  0.059309397 = sum of:
    0.059309397 = weight(_text_:22 in 4324) [ClassicSimilarity], result of:
      0.059309397 = score(doc=4324,freq=2.0), product of:
        0.21899058 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.062536046 = queryNorm
        0.2708308 = fieldWeight in 4324, 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=4324)
  0.25 = coord(1/4)

Date

11. 2.2011 18:22:25

0.008472771 = product of:
  0.033891086 = sum of:
    0.033891086 = weight(_text_:22 in 1163) [ClassicSimilarity], result of:
      0.033891086 = score(doc=1163,freq=2.0), product of:
        0.21899058 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.062536046 = queryNorm
        0.15476047 = fieldWeight in 1163, 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=1163)
  0.25 = coord(1/4)

Source

Proceedings of the Fourth Workshop on Link Analysis, Counterterrorism, and Security, SIAM Data Mining Conference, Bethesda, MD, 20-22 April, 2006. [http://www.siam.org/meetings/sdm06/workproceed/Link%20Analysis/15.pdf]

0.008472771 = product of:
  0.033891086 = sum of:
    0.033891086 = weight(_text_:22 in 3447) [ClassicSimilarity], result of:
      0.033891086 = score(doc=3447,freq=2.0), product of:
        0.21899058 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.062536046 = queryNorm
        0.15476047 = fieldWeight in 3447, 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=3447)
  0.25 = coord(1/4)

Date

22. 2.2017 10:16:49