Search (5 results, page 1 of 1)

0.02384748 = product of:
  0.04769496 = sum of:
    0.02956491 = weight(_text_:data in 2862) [ClassicSimilarity], result of:
      0.02956491 = score(doc=2862,freq=2.0), product of:
        0.120893985 = queryWeight, product of:
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.03823278 = queryNorm
        0.24455236 = fieldWeight in 2862, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.0546875 = fieldNorm(doc=2862)
    0.01813005 = product of:
      0.0362601 = sum of:
        0.0362601 = weight(_text_:22 in 2862) [ClassicSimilarity], result of:
          0.0362601 = score(doc=2862,freq=2.0), product of:
            0.13388468 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03823278 = queryNorm
            0.2708308 = fieldWeight in 2862, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0546875 = fieldNorm(doc=2862)
      0.5 = coord(1/2)
  0.5 = coord(2/4)

Abstract

Paper presented at a symposium on 'Implementing the Art and Architecture Thesaurus (AAT): Controlled Vocabulary in the Extended MARC format', held at the 1989 Annual Conference of the Art Libraries Society of North America. The only way to get bibliographic records on to campus on-line library catalogues, and slide records on the national bibliographic utilities, is through the use of MARC. Discusses the importance of having individual slide and photograph records on the national bibliographic utilities, and considers the obstacles which currently make this difficult. Discusses mapping to MARC from data base management systems.

Date

4.12.1995 22:51:36

0.014932535 = product of:
  0.05973014 = sum of:
    0.05973014 = weight(_text_:data in 4439) [ClassicSimilarity], result of:
      0.05973014 = score(doc=4439,freq=4.0), product of:
        0.120893985 = queryWeight, product of:
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.03823278 = queryNorm
        0.49407038 = fieldWeight in 4439, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.078125 = fieldNorm(doc=4439)
  0.25 = coord(1/4)

0.010558897 = product of:
  0.042235587 = sum of:
    0.042235587 = weight(_text_:data in 417) [ClassicSimilarity], result of:
      0.042235587 = score(doc=417,freq=2.0), product of:
        0.120893985 = queryWeight, product of:
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.03823278 = queryNorm
        0.34936053 = fieldWeight in 417, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.078125 = fieldNorm(doc=417)
  0.25 = coord(1/4)

Abstract

The British Library's national bibliographic service and UKMARC database are described in detail. The use of shared cataloguing data in the UK, and overseas distribution of UKMARC records are discussed.

0.008959521 = product of:
  0.035838082 = sum of:
    0.035838082 = weight(_text_:data in 2515) [ClassicSimilarity], result of:
      0.035838082 = score(doc=2515,freq=4.0), product of:
        0.120893985 = queryWeight, product of:
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.03823278 = queryNorm
        0.29644224 = fieldWeight in 2515, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.1620505 = idf(docFreq=5088, maxDocs=44218)
          0.046875 = fieldNorm(doc=2515)
  0.25 = coord(1/4)

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.

0.005180014 = product of:
  0.020720055 = sum of:
    0.020720055 = product of:
      0.04144011 = sum of:
        0.04144011 = weight(_text_:22 in 2861) [ClassicSimilarity], result of:
          0.04144011 = score(doc=2861,freq=2.0), product of:
            0.13388468 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03823278 = queryNorm
            0.30952093 = fieldWeight in 2861, 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=2861)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Date

4.12.1995 22:40:20