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.
Keywords or tags can be pretty versatile metadata, so I think that they
should definitely be captured, along with what you mentioned.
I'm beginning to work on an internal SharePoint site that'll ultimately
house/provide access to a huge amount of technical content--standards,
specs, drawings--which are currently scattered among other sites,
drives, possibly e-mail, and quite possibly other sources I'm as yet
One thing I feel I need to do as part of my strategy/design work is to
create a content inventory--so I'll know what all there is to
organize/house/provide access to; all the content types and file types
dealing with; where everything lives now. The thing is: I've never done
one before. (And wouldn't you know, I'm under some pressure to get the
site up and running.)
In an attempt to get at least a clue, I searched this list's archives;
afraid that was worse than useless. I also searched the EServer
Communication Library (http://tc.eserver.org/), and the results I could
still access seemed to all be about inventorying the content on an
*existing* web site. Well, although the site I'm working on technically
already exists, I'm working as if I'm starting from scratch. Just
what they've got now is not an option.
So--my questions are these:
1. What all types of information will I want to record about each
element? Right now I've got category (categories decided on by me and a
teammate), content type (spec., drawing, etc.), file type (PDF, TIF,
2. Content management overall is a huge need in this organization...what
if anything can I do as I go through this to better set them up for
adopting some sort of CMS, if they should decide some day to do that?
Any other wisdom (or pointers to same) you can provide will be most
Senior Technical Communicator
American Electric Power
cewinch -at- aep -dot- com
ComponentOne Doc-To-Help 2009 is your all-in-one authoring and publishing
solution. Author in Doc-To-Help's XML-based editor, Microsoft Word or
HTML and publish to the Web, Help systems or printed manuals. http://www.doctohelp.com
Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-