Search (3 results, page 1 of 1)

0.07873234 = product of:
  0.11809851 = sum of:
    0.08966068 = weight(_text_:systematic in 7410) [ClassicSimilarity], result of:
      0.08966068 = score(doc=7410,freq=2.0), product of:
        0.28397155 = queryWeight, product of:
          5.715473 = idf(docFreq=395, maxDocs=44218)
          0.049684696 = queryNorm
        0.31573826 = fieldWeight in 7410, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.715473 = idf(docFreq=395, maxDocs=44218)
          0.0390625 = fieldNorm(doc=7410)
    0.028437834 = product of:
      0.05687567 = sum of:
        0.05687567 = weight(_text_:indexing in 7410) [ClassicSimilarity], result of:
          0.05687567 = score(doc=7410,freq=4.0), product of:
            0.19018644 = queryWeight, product of:
              3.8278677 = idf(docFreq=2614, maxDocs=44218)
              0.049684696 = queryNorm
            0.29905218 = fieldWeight in 7410, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.8278677 = idf(docFreq=2614, maxDocs=44218)
              0.0390625 = fieldNorm(doc=7410)
      0.5 = coord(1/2)
  0.6666667 = coord(2/3)

Abstract

Once the library has been through a process of transition from traditional library procedures to automated ones, natural language searching became a necessity for both indexers and searchers. Therefore, aside from the precoordinated classified catalogue we started to build a dictionary of terms in order to make postcoordinate search possible in keeping with the UDC notations assigned to each bibliographic record. After a while we came to the conclusion that the dictionary needed a control of its terms so that synonymous concepts and semantic ambuguities be avoided. The project presented in this paper shows how reality imposed the improvement of the quality of indexing and hence of the searching possibilities. Is also shows the reasons why we consider a multilingual thesaurus based on UDC an ideal indexing and searching device. The experiment applied on class 8 of UDC illustrates the way the UDC tables can be quite successfully used in building a thesaurus due to their qulities and how their limitations can be overcome by a thesaurus. An appendix to the paper contains a sample of the multilingual thesaurus given in both alphabetical and systematic layouts

0.013270989 = product of:
  0.039812967 = sum of:
    0.039812967 = product of:
      0.079625934 = sum of:
        0.079625934 = weight(_text_:indexing in 4431) [ClassicSimilarity], result of:
          0.079625934 = score(doc=4431,freq=4.0), product of:
            0.19018644 = queryWeight, product of:
              3.8278677 = idf(docFreq=2614, maxDocs=44218)
              0.049684696 = queryNorm
            0.41867304 = fieldWeight in 4431, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.8278677 = idf(docFreq=2614, maxDocs=44218)
              0.0546875 = fieldNorm(doc=4431)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Abstract

This paper describes the Laurin thesaurus, which is used for indexing and searching in the Laurin system, a software package for digital clipping archives. As a multilingual thesaurus it complies with the corresponding standards, though presenting some approaches going beyond some of the standards' recommendations. The Laurin thesaurus integrates all kind of indexing terms, not only keywords, but proper names as well. The system of categories and relationships is described in detail.

0.008975455 = product of:
  0.026926363 = sum of:
    0.026926363 = product of:
      0.053852726 = sum of:
        0.053852726 = weight(_text_:22 in 932) [ClassicSimilarity], result of:
          0.053852726 = score(doc=932,freq=2.0), product of:
            0.17398734 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.049684696 = queryNorm
            0.30952093 = fieldWeight in 932, 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=932)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

1. 8.1996 22:01:00