Maintaining data integrity by documenting the system: Putting database policy in writing
Article publication date: 1 March 1992
Most libraries already have some documentation. Software vendors provide manuals for the “out‐of‐the‐box” programs they sell. The bibliographic utilities also provide documentation, which libraries use for guidance on entering data into the utilities. System documentation may exist also in scattered guides, “cheat sheets,” and “how to” manuals that have been developed for staff use as the need has arisen. Relevant documentation may reside even in non‐library sources. With all this existing documentation, one might conclude that there is no need for yet more system documentation. Yet it is precisely because of the scattered nature of the documentation, the selective use of these sources, the inadequacy of some of the sources, and, most importantly, the need for standardized input into the database that there is a need to develop adequate documentation for a particular library's system.
Sealy, B. (1992), "Maintaining data integrity by documenting the system: Putting database policy in writing", Library Hi Tech, Vol. 10 No. 3, pp. 25-34. https://doi.org/10.1108/eb047854
MCB UP Ltd
Copyright © 1992, MCB UP Limited