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.
RE: I had hoped to get more of a response - Re: Managing versions of documents - problems and concerns
Subject:RE: I had hoped to get more of a response - Re: Managing versions of documents - problems and concerns From:"Bill Darnall" <darcom -at- sbcglobal -dot- net> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Thu, 19 Jun 2003 14:07:20 -0700
Svi Ben Elya wrote:
>I had hoped to get more of a response. Maybe my request was not clear. I am
>not looking for single-sourcing techniques or information on how to manage
>version of software.
>What I need is information on how you keep track of what changes were made
>to documents, when and why. What drawbacks are there to the method used?
>What you would like to keep track of if you could find a practical way to
do
>it? ...
I believe that you should research the capabilities of several electronic
document management systems (EDMS). An EDMS is a special type of content
management system (CMS) that manages real documents, not software revision
levels. The EDMS you need will maintain the content, and more. An EDMS
workflow subsystem is the key to answering the questions (issues) you have
posed.
After spending a few hundred thousand dollars for your EDMS:
1. State your document management objectives. You have listed these as
Issues 1 through 7.
2. Put these objectives into the form of step-by-step procedures.
3. Implement your procedures using the EDMS workflow package.
4. Test each procedure to make sure it works the way you want it to.
5. Be sure someone is available to maintain the EDMS!
RoboHelp Studio maximizes your Help authoring power by combining
RoboHelp Office and RoboDemo, so you can easily create professional
Help systems that feature interactive tutorials and demos.
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
