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: Saving data to hard drive vs posting it to network
Subject:RE: Saving data to hard drive vs posting it to network From:"Margaret Cekis" <Margaret -dot- Cekis -at- comcast -dot- net> To:"'Cardimon, Craig'" <ccardimon -at- M-S-G -dot- com>, "'techwrl'" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Mon, 6 Jun 2011 11:16:04 -0400
Craig Cardimon asked about "Saving data to hard drive vs posting it to
"For those of you who store your work on a network rather than on your local
machine, do you actually work on the network, or do you just move your stuff
up there later?...The applications default to saving my data to the hard
drive. Overriding these defaults is taking some time. Also, it's just easier
to save my latest work to my hard drive. Then I have to play catch-up later,
and save my stuff on the network. How do you all handle this?
I think the safest course is to have complete copies of your work both on
your desktop PC and on the network. In my last job I was expected to make
all finished project material available on the network in the respective
product directories. I also had a personal network space that was to be a
duplicate of my documents on my laptop's hard drive. I tried to keep the
personal backup space current at the end of each day, if I had the time, or
at least weekly on Friday afternoons. This essentially meant that I compared
the network directory of each of my current projects with the same project
directory on my PC hard drive, and copied over any new or updated files. I'd
wait until a product document had been completed and reviewed before I'd
copy it to the respective product directory, and announce to the sales and
other groups that it was available for download on the network.
Because applications like Word and graphics programs open up temporary
working space on the drive where the document is stored, IT departments
whose network space is restricted definitely discourage employees from
working on the network drives. If you're using an app that locks up, you
often have to reboot to release whatever temporary space was tied to that
app when it became "non-responding". If that dead temporary space is on the
network drive, it may require attention from an IT network operator to find
it and release it. Thus IT discourages that approach.
Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-