I had hoped to get more of a response - Re: Managing versions of documents - problems and concerns

["Svi Ben Elya" <svib -at- bezeqint -dot- net>]

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? ...

Your feedback will be used as part of an overview of what issues are
involved in managing changes made to documents. If it will help, please read
the list of issues that I have compiled so far.

Issue 1:  Keeping track of which changes were made after the version of a
document held by a specific customer. How can Technical Support quickly
identify whether corrections were already included in the document or were
added later?

Issue 2: When more than one person works on a document, how does each writer
know what changes have already been made?

Issue 3: Who made and who authorized a specific change? This can save
valuable time when problems occur and more information is needed on the
change and which customer's it affects.

Issue 4: When single-sourcing is used, changes and information related to a
specific document or version of the document.

Issue 5: Document rollbacks. How can I rollback to an old version of a
document when customers have problems with the newer documentation or the
product is rolled back? How do I identify what changes made to the document
are relevant to the older version of the product.

Issue 6: Version Management software commonly used by R&D does not always
identify changes made to documents.

Issue 7: When using a check-out/check-in system and different people work on
different chapters (FM files), how do you check for changes to an entire
book without checking-out all files, thus preventing writers form working on
the files.

----- Original Message ----- 
From: "Goober Writer" <gooberwriter -at- yahoo -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Sent: Wednesday, June 18, 2003 5:15 PM
Subject: Re: Managing versions of documents - problems and concerns


>
> > I think that was not the question asked. I believe
> > the OP was looking for advice on using things like
> > conditional text (or some other device) to manage
> > from within a document the need for multiple
> > (parallel) versions--for localization, for example.
>
> Perhaps, but "revision control" was specifically
> addressed in the question.
>
> OK, let's spend then next 3 days and 200 messages
> pontificating on the nature of the question. LOL!
>
> Seriously, maybe the original poster could elaborate?
>
> =====
> Goober Writer


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

ANNOUNCING ROBOHELP STUDIO

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.

Find out more about RoboHelp Studio at http://www.ehelp.com/techwr-l2

---
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.