Search (1 results, page 1 of 1)

0.00334869 = product of:
  0.00669738 = sum of:
    0.00669738 = product of:
      0.01339476 = sum of:
        0.01339476 = weight(_text_:a in 362) [ClassicSimilarity], result of:
          0.01339476 = score(doc=362,freq=16.0), product of:
            0.053105544 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046056706 = queryNorm
            0.25222903 = fieldWeight in 362, product of:
              4.0 = tf(freq=16.0), with freq of:
                16.0 = termFreq=16.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0546875 = fieldNorm(doc=362)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

The information in a manual card catalogue cannot be transformed into a machine-readable file without some cleanup work. Correcting problem records only as they are reported by patrons or discovered by staff, in the course of normal workflow, can mean that incomplete, incorrect or obsolete information is left in the database for long periods of time. A large database editing project, while it requires a major investment of staff time, can clean up the online file and improve patron access in a relatively short time. Suggests a method which focuses on specific types of catalogue records in the library's online system. Such a database editing project represents an investment in the future that more than justifies the time and effort that go into it

Type

a