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: Help - I/T Library From:"Lakritz, Andrew M." <Andrew -dot- Lakritz -at- Ruesch -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Tue, 20 Aug 2002 16:59:23 -0400
I have implemented a knowledge portal at our corporation using SharePoint
Portal Server (for the Technology department). It has several attractive
features that made it attractive to us. Low cost. Workflow enabled. Check in
and check out and versioning of documents. Easy to use interface (Web
interface based on Microsoft's digital dashboard technology). Fairly easy to
administer. Staff do not need to learn new formats or tools (they can use
Word, Excel, Visio, Photoshop, whatever). It's easy to enhance with readily
available Web parts from Microsoft or Third-party, or you can grow your own
looked at out there are much heavier, and much more expensive. The
technology of SharePoint Portal server borrows from Exchange, SQL Server,
and Microsoft's indexing facility. We've had it up for about a year now with
pretty good results.
From: Joy_Owen -at- Dell -dot- com [mailto:Joy_Owen -at- Dell -dot- com]
Sent: Tuesday, August 20, 2002 3:53 PM
Subject: Help - I/T Library
Recently, I put a front end onto my document tracking database so that
engineers could search and click for documents they wanted. Now, management
wants more of an I/T library ... and frankly, I've never created one. Most
of the users and engineers will be internal.
We used to have an I/T Library that folded because there was no way to
effectively get the engineers to post the most recent versions of their
documents (as far as I know - I'm the only tech writer in the entire I/T
Department - probably about 1200 people). That means a lot of the writing
and revising is still being done by the engineers.
My question is: Is there anyone else out there in this predicament? How do
you enforce the stability of the docs in your library?
I mentioned "corporate policy" to my boss... but that's a no go in this
environment. Our "corporate" rarely has policies around anything that I/T
does as far as communications.
Check out the new release of RoboDemo, our easy-to-use tutorial software.
Plus, buy RoboHelp Office in August and save $100 with our mail-in rebate.
Get details and download free trial versions at http://www.ehelp.com/techwr-l
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.