Home Previous Readability/Usability/Quality Next 1-00 (March 2000) Next
by Åke Rullgård

RU20: Do Not Forget Bibliographical Data in Technical Documentation!

Information products, e.g. manuals, drawings etc, must, besides the technical message, contain certain formal data, which too often is left out. Proper formal data contributes to good order and favours the producer as well as the user of information products.

This article wants to stress the need for bibliographical data, i.e. data on document identification, revisions and origin. Lack of such data may cause problems and degrade the quality of the docu-mentation. First, here is an example that shows the need for bibliographical data in a particular case: plant documentation.

Plant documentation contains manuals on installation and maintenance of valves, instruments etc, bought by the main contractor from various subcontractors. Too often these manuals are supplied out of a non-current storage while the components are supplied directly from the production line. Bibliographical data in the manuals are often poor, which results in errors when specifying spare parts, maintenance procedures, etc, because clear specification of valid documentation is impossible. This becomes a great nuisance to the plant owner.

The manuals have been created by technical communicators. My point is that it is the communicator´s responsibility to make sure that the manuals are furnished with proper formal data. The communicators must claim, as part of their profession, that their employers supply a proper system for the formal data.

The following rules apply to the preparation of bibliographical and other formal data in all forms of technical documentation.

 
Basic Rule

Each part of a document, e.g. each page of a paper, must contain all data needed for unique specification of the context where the paper belongs. Therefore, each page in an operator´s manual and in maintenance manuals, etc, must be provided with

It is of the utmost importance that these particulars are found on each page in case of a paper document. The user´s knowledge of the formal data and its meaning can greatly facilitate communication between the user and the supplier. Therefore, the meaning of the formal data should be declared, possibly in a footnote. All this data needs to be inserted by the person responsible for the contents of the paper, and must not be confused with data often attached by the printing company. For electronically stored documents, the data also should include the file name.

 
Page Numbering

Pages need to be numbered so that each page shows the total number of pages that comprise the document, so the user can verify whether the document is complete.

 
Supplier Resonsibility

The supplier of components, valves, meters, etc, must be held responsible for supplying a fully documented manual for each component. By providing proper bibliographical data, the supplier facilitates correct specification of all documentation for the final product.

 
Closing Remarks

It should be part of the professionalism and ethics for all technical communicators to ensure that the above rules are followed in the development of all information products for which they are responsible. The rules can easily be applied and are needed regardless of medium, e.g. in paper-based and paperless documentation. I believe that a standard for formal data should be developed; maybe this could be a task for INTECOM.

I consider the ideas presented above so important that they deserve another item in the INTECOM´s code of good practice:

"11. All communicators shall ensure that their information products are provided with proper bibliographical and other formal data."

I welcome your comments!  


© TC Forum 1998-2001 - http://www.tc-forum.org - file last updated 08 Oct 2000
"transline Deutschland - Übersetzungsdienst für technische Übersetzung"
Web design by "Alexander von Obert"