Dean, B.C.: Reclassification in an automated environment (1984)
0.01
0.008156957 = product of:
0.057098698 = sum of:
0.028549349 = weight(_text_:classification in 340) [ClassicSimilarity], result of:
0.028549349 = score(doc=340,freq=4.0), product of:
0.09562149 = queryWeight, product of:
3.1847067 = idf(docFreq=4974, maxDocs=44218)
0.03002521 = queryNorm
0.29856625 = fieldWeight in 340, product of:
2.0 = tf(freq=4.0), with freq of:
4.0 = termFreq=4.0
3.1847067 = idf(docFreq=4974, maxDocs=44218)
0.046875 = fieldNorm(doc=340)
0.028549349 = weight(_text_:classification in 340) [ClassicSimilarity], result of:
0.028549349 = score(doc=340,freq=4.0), product of:
0.09562149 = queryWeight, product of:
3.1847067 = idf(docFreq=4974, maxDocs=44218)
0.03002521 = queryNorm
0.29856625 = fieldWeight in 340, product of:
2.0 = tf(freq=4.0), with freq of:
4.0 = termFreq=4.0
3.1847067 = idf(docFreq=4974, maxDocs=44218)
0.046875 = fieldNorm(doc=340)
0.14285715 = coord(2/14)
- Abstract
- For a variety of reasons, reclassification was a popular project in libraries in the 1960s. Although such projects have faded from the limelight, some of the reasons for doing them remain valid today, i.e., a need to cut processing costs, participation in cooperative ventures, the inconvenience caused by working with a collection split between two classification systems, and continuing changes in the Dewey schedules. This article compares the steps needed for reclassifying in a manual environment with those required when the library has an in-house computer system. The comparison shows how using the latter makes a reclassification project more feasible than it would be in a totally manual library. The article also discusses various issues associated with reclassification in an automated environment such as the problem posed by a frozen public catalog and the combining of reclassification and conversion projects.
- Source
- Cataloging and classification quarterly. 5(1984) no.2, S.1-11
