How to archive documents

Knowing how to archive documents is essential to an efficient workflow. Think about it; you work hard to create the documents your organization needs to be effective. Why risk losing that hard work? Archives ensure that you can recover any lost documents, and make it easier to track the specific details of your project the next time you work on it.

Here are a few tips for creating an effective archive for your documents.

  • Create a readme file and store it with your project files. The readme should also be archived along with the rest of the project. Readme files should contain essential details, such as the working path, a list of files in the project, notes from the last person who worked on the project, when the document was last delivered and archived, and so on. This readme file will be essential if another writer picks up the project, or if you return to the project at a later date. Detailed notes will save you a lot of time and grief.
  • Schedule your backup process, and automate it. That way your backups will be reliable even if everyone working on the documents isn't familiar with how to archive documents according to your conventions. Use the scheduled tasks features in your operating system to launch scripts that will automatically backup your files on a regular basis.
  • Zip your files. Compacting the project archive will reduce the amount of space your backups require, and make it faster to copy or move the files, if necessary. Use tools such as WinZip or 7zip, or the built-in compression tools in recent versions of Windows and other operating systems.
  • Put your document archives on both a network drive (to take advantage of scheduled server backups), and on physical media, such as a CD or DVD. It's better to me cautious than to lose important project files and regret it.
  • Whether or not you compact (zip) your files when you archive them, be sure to maintain the folder structure. That way everything is in the correct place when you pull down the document files for the next update.

By following careful archiving procedures, you can decrease the risk of losing your files and make your workflow more efficient.

Similar posts:

Document automation - Word

This article contains tips and getting-started information for documentation automation with Microsoft Word.

MS Word has incredibly useful VBA features that allow you to automate routine documentation tasks. You can use the Record Macro feature to automate many repetitive actions, such as retagging paragraph styles, searching and replacing content, and so on. For advanced automation, use the Visual Basic Editor. The editor has many GUI features to assist you in writing code for complicated procedures.

Why automate?

Repetitive action is costly. How many hours does your documentation team spend performing the same actions over and over on the documents you produce regularly? When you analyze the time lost through such repetition, you can see how much more productive automation will make your team.

What is a Word macro?

Word stores automation code in the form of macros. Each macro contains the code necessary to perform a specific automation task. Often, macros are chained together to handle multiple taks.

You can view available macros from the Developer tab in the ribbon. Click the Macros button to view a list of macros available within your document.

Macros can be stored in individual documents, or in templates (.DOT files). I suggest storing them in templates, so that the macros will be available in all documents with the template attached.

The Macros dialog allows you to run, record, edit, organize, and step into macros.

Deciding what documentation tasks to automate

Some tasks are easier to automate than others. Here are a few quesions to help you decide if a task would benefit from automation.

  • Is the action you wish to automate exactly the same every time, or does each iteration require special consideration?
  • Can you summarize the steps involved in performing the action?
  • Do many people in your department perform the task regularly?
  • Does the task apply to many documents, or at least several long documents?

If you can answer Yes to most of these questions, chances are automation is worthwhile.

Recording a macro

Word allows you to record macros. This is the easy way to automate document tasks since it does not require you to write any code. Use the Record Macro feature on the Macros dialog to create a new macro. Then, perform the tasks that you wish to automate on the document you currently have open. Word will record your actions and write the macro code for you.

Click the Stop button when you are finished performing the tasks. Then, use the Run feature to test your new macro.

Recording macros and then editing them in the VBA editor is a great way to learn the VBA language. VBA is a flavor of the BASIC programming language, so it is easier to understand than many lower-level languages. Since you know what tasks you performed when recording, you can easily determine which chunks of code belong to each task.

Editing a macro in the VBA editor

Often the tasks you wish to automate are more complicated that what can be recorded in a single macro recording session. By working in the VBA editor, you can combine code from multiple recorded macros into a single, larger macro. You can also use the GUI tools to drag and drop code fragments for common document objects. You can also include more complicated code such as database connections and GUI forms for gathering information.

On the left side of the editor window, you'll see a list of the modules available in your template. You can store multiple macros in a module, or one per module. I recommend storing a single macro in each module to reduce confusion between module and macro names.

The editor also allows you to export your automation macros. However, for sharing and archiving purposes, it is often better to archive or share the entire template.

Each macro in the editor begins with a Sub statement and a name, and ends with an End Sub statement. All code between these statements belongs to that macro.

To include comments in your automation code, start the line with an apostrophe or a REM statement. Word will recognize this as a comment and will not try to execute it as code. Comments allow you to make important notes about the purpose of a block of code, so that you or others will have an easier time understanding it later.

As you develop more and more macros, you may find the Macros tab of the Organizer dialog useful. This dialog allows you to copy macros across document or template files. If you are sharing macros, it is best to just share the entire template, but you will find the Organizer tab useful for consolidating related macros and cleaning up your templates.

Wrapping up

As you continue recording and editing macros, you will find it easier and easier to understand the VBA language, and the types of features Word allows you to automate. Your document production process will become more efficient, and your bottom line will likely improve as a result.

Related post: Six Word macro tips you won't want to miss.

Review of Conversation and Community - The Social Web for Documentation by Anne Gentle

When I heard Anne Gentle was in the process of writing this book, I was excited. The initial buzz hinted at answers to questions being raised in professional discussion groups and in my own work, the most unsettling being "If users are resorting to community-generated documentation, where does that leave professional writers?"

When the publisher sent me a free copy to review, I couldn't wait to dig in.

New roles for technical writers

As social media digs its roots deeper and deeper into the lives of consumers, it is becoming clear that writers need to adapt and get involved. The old methods of documentation production and delivery don't always meet the needs of our users. The process is too slow. The resulting documents do not engage or involve users, or make efficient use of their feedback. Users are responding by searching Google instead of the product's help, and by starting their own product-based communities for asking and answering questions.

Anne Gentle sees this change in a positive light; she has jumped into the tangled world of Web 2.0 with both feet and emerged with a clearer sense of purpose. Through her experiences working on community-generated documents, she has discovered how writers can add value and authority to wikis, blogs, and other forms of social media. Her book is filled with insight gained from her work as a professional blogger, FLOSS Manuals veteran, and volunteer for the One Laptop per Child project.

The answers you seek are here

The initial pages of Conversation and Community - The Social Web for Documentation cover the various types of social media being used to generate documentation and product-based conversations. Gentle starts with the essentials, including wikis and blogs, but continues to suggest a vast range of tools along with details on how each applies to user documentation. Web 2.0 junkies might be familiar with some of this material, but I found quite a few suggestions that I hadn't considered before.

Then Gentle gets into the really good stuff. She covers, in detail, all of the nagging questions about how writers fit into this new world of social media. For example...

  • How to determine if your customers need or want an online community.
  • How to judge what features and information your customers will find useful.
  • How to judge what role the writer should play in a community.
  • A definition of the types of roles a writer can play.
  • How to ease your way into a community without being intrusive.
  • How to convince your company of the value of the social web for documentation.
  • Tips for implementing community technology and getting other writers involved.
  • Guidelines for measuring the success of your community-based documentation.
  • How to organize Book Sprints and grow a team for building a community-generated document.
  • Specific examples of FLOSS Manuals involvement and the tools used in Book Sprints.
  • Guidelines and tools for repurposing Wiki pages and other user-generated content.
  • How to find your voice and get involved immediately.

I could elaborate here, but you should really just read the book so you don't miss the vital details.

What I like best of all is that Gentle never makes the mistake of elevating the technology to greater importance than the people who use it. It isn't about the tools; it's about the community. It's about relationships.

My overall opinion

This is a very important book. Not reading it is like sticking your head in the sand and waiting for your career to dissipate into oblivion. Your community needs you.

You can Buy it from Amazon >>.