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:Tips for Data Migration Manual From:Mark Stansfield <mstansfield -at- APTLTD -dot- CO -dot- UK> Date:Mon, 15 Feb 1999 16:52:52 +0000
Hi,
I'm emerging from the land of lurk to post this message on behalf of a
colleague. Could you please mail me with your thoughts on the subject
- I'll post a summary to the list.....
-------------------------------------------------
I've searched the archive for this information, but I couldn't find
any, I hope someone out there can help me.
Does anybody have any tips on what to include in a printed Data
Migration Manual?
We need to produce a manual for system administrators so that they can
import data from their old software to our system.
There is one setup screen to set up the import parameters. All the
importing is then carried out through a series of batch jobs: there
are about 30 or 40 jobs that update approximately 70 data files - note
we have another 600 data files that aren't updated here.
This data import will be a one-off process run by the system
administrator when they buy our software.
What kind of information should I provide in this manual?
-----------------------------------------------------
TIA,
Mark Stansfield
Technical Author
NSB Retail Systems PLC
mstansfield -at- aptltd -dot- co -dot- uk