Search (6 results, page 1 of 1)

0.05485135 = product of:
  0.08227702 = sum of:
    0.06027615 = product of:
      0.18082845 = sum of:
        0.18082845 = weight(_text_:3a in 855) [ClassicSimilarity], result of:
          0.18082845 = score(doc=855,freq=2.0), product of:
            0.38609818 = queryWeight, product of:
              8.478011 = idf(docFreq=24, maxDocs=44218)
              0.045541126 = queryNorm
            0.46834838 = fieldWeight in 855, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              8.478011 = idf(docFreq=24, maxDocs=44218)
              0.0390625 = fieldNorm(doc=855)
      0.33333334 = coord(1/3)
    0.022000873 = weight(_text_:to in 855) [ClassicSimilarity], result of:
      0.022000873 = score(doc=855,freq=14.0), product of:
        0.08279609 = queryWeight, product of:
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.045541126 = queryNorm
        0.2657236 = fieldWeight in 855, product of:
          3.7416575 = tf(freq=14.0), with freq of:
            14.0 = termFreq=14.0
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.0390625 = fieldNorm(doc=855)
  0.6666667 = coord(2/3)

Abstract

Converting UDC numbers manually to a complex format such as the one mentioned above is an unrealistic expectation; supporting building these representations, as far as possible automatically, is a well-founded requirement. An additional advantage of this approach is that the existing records could also be processed and converted. In my dissertation I would like to prove also that it is possible to design and implement an algorithm that is able to convert pre-coordinated UDC numbers into the introduced format by identifying all their elements and revealing their whole syntactic structure as well. In my dissertation I will discuss a feasible way of building a UDC-specific XML schema for describing the most detailed and complicated UDC numbers (containing not only the common auxiliary signs and numbers, but also the different types of special auxiliaries). The schema definition is available online at: http://piros.udc-interpreter.hu#xsd. The primary goal of my research is to prove that it is possible to support building, retrieving, and analyzing UDC numbers without compromises, by taking the whole syntactic richness of the scheme by storing the UDC numbers reserving the meaning of pre-coordination. The research has also included the implementation of a software that parses UDC classmarks attended to prove that such solution can be applied automatically without any additional effort or even retrospectively on existing collections.

Content

Vgl. auch: New automatic interpreter for complex UDC numbers. Unter: <https%3A%2F%2Fudcc.org%2Ffiles%2FAttilaPiros_EC_36-37_2014-2015.pdf&usg=AOvVaw3kc9CwDDCWP7aArpfjrs5b>

0.0077611795 = product of:
  0.023283537 = sum of:
    0.023283537 = weight(_text_:to in 3742) [ClassicSimilarity], result of:
      0.023283537 = score(doc=3742,freq=2.0), product of:
        0.08279609 = queryWeight, product of:
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.045541126 = queryNorm
        0.28121543 = fieldWeight in 3742, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.109375 = fieldNorm(doc=3742)
  0.33333334 = coord(1/3)

Footnote

Übers. d. Titels: References to electronic information sources

0.0077611795 = product of:
  0.023283537 = sum of:
    0.023283537 = weight(_text_:to in 938) [ClassicSimilarity], result of:
      0.023283537 = score(doc=938,freq=8.0), product of:
        0.08279609 = queryWeight, product of:
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.045541126 = queryNorm
        0.28121543 = fieldWeight in 938, product of:
          2.828427 = tf(freq=8.0), with freq of:
            8.0 = termFreq=8.0
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.0546875 = fieldNorm(doc=938)
  0.33333334 = coord(1/3)

Abstract

In Sweden, the Medical Subject Headings System (MeSH) has been used for more than 3 decades but the decision to translate it to the Swedish language was made only in 1995. The reasons of the translation are the sophisticated strucuture of the keyword system and the expansion of the retrieval needs of medical information in Sweden

Content

Contribution to a special issue devoted in part to papers from the proceedings of the EAHIL (European Association of Health Information and Libraries) Conference, Budapest, Hungary

0.00627198 = product of:
  0.018815938 = sum of:
    0.018815938 = weight(_text_:to in 1740) [ClassicSimilarity], result of:
      0.018815938 = score(doc=1740,freq=4.0), product of:
        0.08279609 = queryWeight, product of:
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.045541126 = queryNorm
        0.22725637 = fieldWeight in 1740, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.0625 = fieldNorm(doc=1740)
  0.33333334 = coord(1/3)

Abstract

Outlines the problems which character sets limited to one byte and 256 characters have generated for library systems. Considers the benefits of the Unicode standard which is a 16 bit fixed width character encoding standard allowing room for more than 65.000 characters. Discusses the extent to which it is being used by applications, noting that some library system suppliers are implementing it, while some argue that the major operating systems do not yet cater for it adequately

0.005487982 = product of:
  0.016463947 = sum of:
    0.016463947 = weight(_text_:to in 3741) [ClassicSimilarity], result of:
      0.016463947 = score(doc=3741,freq=4.0), product of:
        0.08279609 = queryWeight, product of:
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.045541126 = queryNorm
        0.19884932 = fieldWeight in 3741, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.0546875 = fieldNorm(doc=3741)
  0.33333334 = coord(1/3)

Content

Contribution to a special issue devoted in part to papers from the proceedings of the EAHIL (European Association of Health Information and Libraries) Conference, Budapest, Hungary

0.0044349595 = product of:
  0.013304878 = sum of:
    0.013304878 = weight(_text_:to in 870) [ClassicSimilarity], result of:
      0.013304878 = score(doc=870,freq=2.0), product of:
        0.08279609 = queryWeight, product of:
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.045541126 = queryNorm
        0.16069452 = fieldWeight in 870, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.818051 = idf(docFreq=19512, maxDocs=44218)
          0.0625 = fieldNorm(doc=870)
  0.33333334 = coord(1/3)

Abstract

Presents a brief survey of the emergence of MARC formats, their components, standardization efforts, and the UseMARCON conversion program by means of which any MARC format can be converted to any other. HUNMARC was issued in 1994 in accordance with Hungarian standards of librarianship. Some important questions arising in connection with the implementation of HUNMARC can be answered by comparing the HUNMARC and USMARC formats