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: Scoping out possible document management solutions
Subject:Re: Scoping out possible document management solutions From:"Klopfenstein, Ed (AFS)" <EdK -at- ACCU-FAB -dot- COM> Date:Fri, 25 Jul 1997 13:31:09 -0700
Raymond:
Would like to help, but I don't understand what you need.
Rephrase, please.
Ed
>-----Original Message-----
>From: Raymond Chénier [SMTP:ray -at- PEAC -dot- COM]
>Sent: Friday, July 25, 1997 12:42 PM
>To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
>Subject: Scoping out possible document management solutions
>
>Hello
>
>We are a consulting/software development company with a rapidly growing
>training division. I am beginning to look at possible solutions for
>implementing document management before we end up in a bigger mess... :-)
>We have people who develop courseware using various tools on different
>platforms. Because many things are done at the last minute, not much
>thought is going into future ramifications of not having some type of
>system in place.
>
>Our training courses are of particular concern. We would want a solution
>that could handle this:
>
> 1. Courses, modules, types of info within a module, could be treated
>as
> information objects and called on demand.
>
> 2. Because we tailor courses for clients, we may for example want to
>create a course containing modules from programming, ooad, and
>architecture module objects (contained within course objects). The
>automatic creation of toc, index, etc, is, of course, desirable.
>
>We are a Microsoft Developer Network/Microsoft Office integrated company
>and we run UNIX and NT 4.0 servers. We may look at getting in-house senior
>programmers to look at the problem. I, in the meantime, am taking this
>opportunity to look at SGML and any existing solutions/systems already out
>there.
>
>I am the only full-time tech writer here, and asking outside people to
>deliver docs to me in Frame or other good tools is like pulling teeth.
>
>I love the initial process of research into possible solutions and I thank
>anyone with feedback in advance.
>
>Raymond Chenier
>Lead Writer/Trainer
>PEAC/Zenith
>Ottawa, Ontario
>
> 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
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
