Search (6 results, page 1 of 1)

0.030024407 = product of:
  0.09007322 = sum of:
    0.09007322 = product of:
      0.27021965 = sum of:
        0.27021965 = weight(_text_:lcsh's in 3816) [ClassicSimilarity], result of:
          0.27021965 = score(doc=3816,freq=2.0), product of:
            0.493835 = queryWeight, product of:
              9.905128 = idf(docFreq=5, maxDocs=44218)
              0.049856503 = queryNorm
            0.54718614 = fieldWeight in 3816, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              9.905128 = idf(docFreq=5, maxDocs=44218)
              0.0390625 = fieldNorm(doc=3816)
      0.33333334 = coord(1/3)
  0.33333334 = coord(1/3)

Abstract

The Library of Congress Subject Headings schema (LCSH) is by far the most commonly used and widely accepted subject vocabulary for general application. It is the de facto universal controlled vocabulary and has been a model for developing subject heading systems by many countries. However, LCSH's complex syntax and rules for constructing headings restrict its application by requiring highly skilled personnel and limit the effectiveness of automated authority control. Recent trends, driven to a large extent by the rapid growth of the Web, are forcing changes in bibliographic control systems to make them easier to use, understand, and apply, and subject headings are no exception. The purpose of adapting the LCSH with a simplified syntax to create FAST is to retain the very rich vocabulary of LCSH while making the schema easier to understand, control, apply, and use. The schema maintains upward compatibility with LCSH, and any valid set of LC subject headings can be converted to FAST headings.

0.015761359 = product of:
  0.047284074 = sum of:
    0.047284074 = product of:
      0.09456815 = sum of:
        0.09456815 = weight(_text_:22 in 3247) [ClassicSimilarity], result of:
          0.09456815 = score(doc=3247,freq=2.0), product of:
            0.17458898 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.049856503 = 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.0067548677 = product of:
  0.020264603 = sum of:
    0.020264603 = product of:
      0.040529206 = sum of:
        0.040529206 = weight(_text_:22 in 5920) [ClassicSimilarity], result of:
          0.040529206 = score(doc=5920,freq=2.0), product of:
            0.17458898 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.049856503 = 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.0067548677 = product of:
  0.020264603 = sum of:
    0.020264603 = product of:
      0.040529206 = sum of:
        0.040529206 = weight(_text_:22 in 2205) [ClassicSimilarity], result of:
          0.040529206 = score(doc=2205,freq=2.0), product of:
            0.17458898 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.049856503 = 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.0067548677 = product of:
  0.020264603 = sum of:
    0.020264603 = product of:
      0.040529206 = sum of:
        0.040529206 = weight(_text_:22 in 3842) [ClassicSimilarity], result of:
          0.040529206 = score(doc=3842,freq=2.0), product of:
            0.17458898 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.049856503 = 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

0.006258128 = product of:
  0.018774385 = sum of:
    0.018774385 = product of:
      0.03754877 = sum of:
        0.03754877 = weight(_text_:management in 2224) [ClassicSimilarity], result of:
          0.03754877 = score(doc=2224,freq=2.0), product of:
            0.16804695 = queryWeight, product of:
              3.3706124 = idf(docFreq=4130, maxDocs=44218)
              0.049856503 = queryNorm
            0.22344214 = fieldWeight in 2224, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.3706124 = idf(docFreq=4130, maxDocs=44218)
              0.046875 = fieldNorm(doc=2224)
      0.5 = coord(1/2)
  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.