Search (3 results, page 1 of 1)

  • × author_ss:"Simmons, P."
  • × theme_ss:"Datenformate"
  1. Hagler, R.; Simmons, P.: ¬The bibliographic record and information technology (1982) 0.00 
    0.00275476 = product of:
  0.020660698 = sum of:
    0.015727427 = weight(_text_:und in 4279) [ClassicSimilarity], result of:
      0.015727427 = score(doc=4279,freq=2.0), product of:
        0.06422601 = queryWeight, product of:
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.028978055 = queryNorm
        0.24487628 = fieldWeight in 4279, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.078125 = fieldNorm(doc=4279)
    0.0049332716 = product of:
      0.009866543 = sum of:
        0.009866543 = weight(_text_:information in 4279) [ClassicSimilarity], result of:
          0.009866543 = score(doc=4279,freq=2.0), product of:
            0.050870337 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.028978055 = queryNorm
            0.19395474 = fieldWeight in 4279, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.078125 = fieldNorm(doc=4279)
      0.5 = coord(1/2)
  0.13333334 = coord(2/15)
    Abstract
    Gründliche Darstellung aller mit der Speicherung und Verarbeitung bibliographischer Daten (inkl. Sacherschließung) verbundenen Problembereiche. Im Anhang Dokumentation des CANMARC Formats
  2. Simmons, P.: Microcomputer software for ISO 2709 record conversion (1989) 0.00 
    5.2621565E-4 = product of:
  0.0078932345 = sum of:
    0.0078932345 = product of:
      0.015786469 = sum of:
        0.015786469 = weight(_text_:information in 2) [ClassicSimilarity], result of:
          0.015786469 = score(doc=2,freq=2.0), product of:
            0.050870337 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.028978055 = queryNorm
            0.3103276 = fieldWeight in 2, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.125 = fieldNorm(doc=2)
      0.5 = coord(1/2)
  0.06666667 = coord(1/15)
    Source
    Microcomputers for information management. 6(1989), S.197-205
  3. Simmons, P.: Converting UNIMARC records to CCF (1989) 0.00 
    1.9733087E-4 = product of:
  0.002959963 = sum of:
    0.002959963 = product of:
      0.005919926 = sum of:
        0.005919926 = weight(_text_:information in 2515) [ClassicSimilarity], result of:
          0.005919926 = score(doc=2515,freq=2.0), product of:
            0.050870337 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.028978055 = queryNorm
            0.116372846 = fieldWeight in 2515, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.046875 = fieldNorm(doc=2515)
      0.5 = coord(1/2)
  0.06666667 = coord(1/15)
    Abstract
    One of the primary goals of Unesco's Common Communication Format (CCF) has been to maintain compatibility between two major information communities: libraries; and abstracting and indexing organisations. While abstracting and indexing organisations do not follow any single standard for description or the structure and encoding of machine records, libraries have clearly defined standards and practices. Among CCF-using organisations are some that wish to incorporate records produced by national bibliographic agencies, especially national libraries, into their own data bases. They need the ability to convert UNIMARC records to CCF. To accomplish this they require a source of records, a computer to process them, a computer programm designed for record conversion and a table or instructions laying out the specific way in which each UNIMARC data element is to be processed in the course of conversion to CCF. Examines the factors to be considered in planning a table that would be sufficiently detailed to accomplish record conversion, and outlines problems that might be encountered.

Types