Re: managing document revisions?

Subject: Re: managing document revisions?
From: "Engstrom, Douglas D." <EngstromDD -at- PHIBRED -dot- COM>
Date: Tue, 1 Apr 1997 08:16:37 -0600

Dan:

This is written in response to:

>> In the environment you're describing, you could use versions to
>> designate software-driven documentation changes, and the sub-versions to
>> represent maintenance of the old-version document. You can have up to
>> 99 versions of each document, along with up to 26 sub-versions of each
>> version available in the document database at any given time.
>That sounds ideal, but I don't think we have the personnel or disk space!
You can also limit the number of versions or sub-versions by work group
or document type. However, making those kinds of decisions is the sort
of thing that makes document management difficult. Deploying a document
management system is essentially like developing and deploying a small
client-server app. It's a project, and needs to be treated as such.
>
>> I'm administering a document
>> management system here (ironically, not for technical communications as
>> such) and will be happy to talk to you about it.
>We are having some meetings over the next few days... I may contact you for
>more advice!
Feel free...

Skoal,

Doug Engstrom "It's hard not to rock the boat when you're
engstromdd -at- phibred -dot- com sailing against the undertow."
--- The Indigo Girls

#######################################################################
My opinions only, not those of Pioneer Hi-Bred International, Inc.
#######################################################################

TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html


Previous by Author: Re: value of good technical writing
Next by Author: Usability: Tutorial *chapter* or *manual*
Previous by Thread: Re: managing document revisions?
Next by Thread: [no subject]


What this post helpful? Share it with friends and colleagues:

Sponsored Ads


Sponsored Ads