TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Queries on Single Sourcing From:"Mark Baker" <listsub -at- analecta -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 13 Feb 2004 17:33:13 -0500
> The places I've worked that tried the chunking
> approach in a single-source procedure, they abandoned
> the attempt when it became apparent the overhead of
> cataloging the chunks was just too much of a problem.
> So how do you use information chunking without having
> to spend hours each day doing nothing but categorizing
> and indexing chunks?
If you design proper information components, you do not spend very much time
labeling them. A well designed information component has certain discrete
and consistent properties that naturally identify it. These properties are
both part of its data and part of its metadata. You spend your time creating
components. Most of the metadata takes care of itself.
The situation you describe sounds like the typical attempt to turn fragments
into usable components by adding metadata too them. The reason that the
cataloging becomes overwhelming is because no matter how much metadata you
add, you can't change a fragment into a component. It's like trying to turn
straw into gold by adding margarine. Adding more margarine doesn't help and
you soon get tired of carrying it.