Search (9 results, page 1 of 1)

0.018504292 = product of:
  0.055512875 = sum of:
    0.055512875 = weight(_text_:reference in 2224) [ClassicSimilarity], result of:
      0.055512875 = score(doc=2224,freq=2.0), product of:
        0.205834 = queryWeight, product of:
          4.0683694 = idf(docFreq=2055, maxDocs=44218)
          0.050593734 = queryNorm
        0.2696973 = fieldWeight in 2224, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.0683694 = idf(docFreq=2055, maxDocs=44218)
          0.046875 = fieldNorm(doc=2224)
  0.33333334 = coord(1/3)

Abstract

This report analyzes the methodologies used in establishing interoperability among knowledge organization systems (KOS) such as controlled vocabularies and classification schemes that present the organized interpretation of knowledge structures. The development and trends of KOS are discussed with reference to the online era and the Internet era. Selected current projects and activities addressing KOS interoperability issues are reviewed in terms of the languages and structures involved. The methodological analysis encompasses both conventional and new methods that have proven to be widely accepted, including derivation/modeling, translation/adaptation, satellite and leaf node linking, direct mapping, co-occurrence mapping, switching, linking through a temporary union list, and linking through a thesaurus server protocol. Methods used in link storage and management, as weIl as common issues regarding mapping and methodological options, are also presented. It is concluded that interoperability of KOS is an unavoidable issue and process in today's networked environment. There have been and will be many multilingual products and services, with many involving various structured systems. Results from recent efforts are encouraging.

0.015994422 = product of:
  0.047983266 = sum of:
    0.047983266 = product of:
      0.09596653 = sum of:
        0.09596653 = weight(_text_:22 in 3247) [ClassicSimilarity], result of:
          0.09596653 = score(doc=3247,freq=2.0), product of:
            0.17717063 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.050593734 = queryNorm
            0.5416616 = fieldWeight in 3247, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.109375 = fieldNorm(doc=3247)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Object

DDC-22

0.013709504 = product of:
  0.041128512 = sum of:
    0.041128512 = product of:
      0.082257025 = sum of:
        0.082257025 = weight(_text_:22 in 3985) [ClassicSimilarity], result of:
          0.082257025 = score(doc=3985,freq=2.0), product of:
            0.17717063 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.050593734 = queryNorm
            0.46428138 = fieldWeight in 3985, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.09375 = fieldNorm(doc=3985)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

25.11.2005 18:37:22

0.012179474 = product of:
  0.036538422 = sum of:
    0.036538422 = product of:
      0.073076844 = sum of:
        0.073076844 = weight(_text_:database in 1146) [ClassicSimilarity], result of:
          0.073076844 = score(doc=1146,freq=2.0), product of:
            0.20452234 = queryWeight, product of:
              4.042444 = idf(docFreq=2109, maxDocs=44218)
              0.050593734 = queryNorm
            0.35730496 = fieldWeight in 1146, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.042444 = idf(docFreq=2109, maxDocs=44218)
              0.0625 = fieldNorm(doc=1146)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Abstract

In addition to using title keywords and subject headings for searching in the online catalog, the searcher may also use class numbers as access points. Library of Congress class or call numbers are particular effective in certain kinds of specific-item subject searching and serve as supplements to keywords and descriptors, improving precision and recall. Class number searching in the database can produce unique results because these numbers collect citations in ways that differ from those of keywords and descriptors

0.01065704 = product of:
  0.03197112 = sum of:
    0.03197112 = product of:
      0.06394224 = sum of:
        0.06394224 = weight(_text_:database in 5560) [ClassicSimilarity], result of:
          0.06394224 = score(doc=5560,freq=2.0), product of:
            0.20452234 = queryWeight, product of:
              4.042444 = idf(docFreq=2109, maxDocs=44218)
              0.050593734 = queryNorm
            0.31264183 = fieldWeight in 5560, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.042444 = idf(docFreq=2109, maxDocs=44218)
              0.0546875 = fieldNorm(doc=5560)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Abstract

Suggests that recent developments in the way information is generated, packaged amd accessed have broadened and changed the nature and application of classification in library and information networks. Examines the role of classification by posing the following questions: what, how and why do we classify? Within this context the expanding role of classification is examined with regard to how classification affects accessing, browsing, identifying, navigating, mapping and evaluating information and how it is and may be used in collection and database management, controlled vocabulary construction and development, and research

0.0076121716 = product of:
  0.022836514 = sum of:
    0.022836514 = product of:
      0.045673028 = sum of:
        0.045673028 = weight(_text_:database in 1781) [ClassicSimilarity], result of:
          0.045673028 = score(doc=1781,freq=2.0), product of:
            0.20452234 = queryWeight, product of:
              4.042444 = idf(docFreq=2109, maxDocs=44218)
              0.050593734 = queryNorm
            0.2233156 = fieldWeight in 1781, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.042444 = idf(docFreq=2109, maxDocs=44218)
              0.0390625 = fieldNorm(doc=1781)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Abstract

Recognition, by libraries, of the need for improved efficiency and reliability in subject authority control in catalogues led to a study of the feasibility of automatically creating a subject heading validation file by scanning the OLUC. The premises were: that although the file would not be axhaustive, it would contain the majority of frequently used headings; and that the predicted level of accurary in the file would be high. A sample file of Library of Congress assigned subject headings, from the OCLC Subject Headings Corrections database was analyzed. Results showed that: the frequency of use varies inversely with the number of headings at a given rrate of use; a small number of headings with high frequencies of use accounts for the majority of total use, while a large proportion shows very low frequency of use; topical headings account for 2/3 of assigned headings; and error and obsolescence rates are both low and are in inverse relationship to the frequency of heading use. Concludes that an automatically generated subject heading validation file is feasible and could serve various purposes, including: verification of subject heading strings constructed by cataloguers; updating of subject headings in catalogue maintenance; and validation of subject headings during retrospective catalogue conversion

0.006854752 = product of:
  0.020564256 = sum of:
    0.020564256 = product of:
      0.041128512 = sum of:
        0.041128512 = weight(_text_:22 in 5920) [ClassicSimilarity], result of:
          0.041128512 = score(doc=5920,freq=2.0), product of:
            0.17717063 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.050593734 = queryNorm
            0.23214069 = fieldWeight in 5920, 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=5920)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

27. 5.2001 16:22:21

0.006854752 = product of:
  0.020564256 = sum of:
    0.020564256 = product of:
      0.041128512 = sum of:
        0.041128512 = weight(_text_:22 in 2205) [ClassicSimilarity], result of:
          0.041128512 = score(doc=2205,freq=2.0), product of:
            0.17717063 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.050593734 = queryNorm
            0.23214069 = fieldWeight in 2205, 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=2205)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

10. 9.2000 17:38:22

0.006854752 = product of:
  0.020564256 = sum of:
    0.020564256 = product of:
      0.041128512 = sum of:
        0.041128512 = weight(_text_:22 in 3842) [ClassicSimilarity], result of:
          0.041128512 = score(doc=3842,freq=2.0), product of:
            0.17717063 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.050593734 = queryNorm
            0.23214069 = fieldWeight in 3842, 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=3842)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

27. 8.2011 14:22:42