Archives for October 12, 2012

Word of Law No. 29 – A Collaboration on Collaboration

[Originally appeared 2000.]

Shared responsibility for the drafting and editing of documents can hardly be said to be unique to the practice of law. Yet lawyers do so with an intensity and attention to detail (perhaps better termed an obsession) difficult to match in any other document endeavor. Every word of a legal document may have consequences. At least, we lawyers are trained to draft as if that were the case. Once again we hope that an aspect of Word that so engages lawyers will inform others who use the program at industrial strength.

In this series we will explore the methods, tools and issues relating to the collaborative drafting of documents. This review will include the tools and functions within Word that assist (and sometimes hinder) this process, as well as third party products that can extend Word’s capabilities. We will look beyond word processing to consider issues relating to document storage and tracking when sharing responsibility for document drafting. In that spirit, we will look especially at the newly sprouting Web enabled systems to support collaborative drafting.

As we begin to explore this topic within our legal context, it will often matter who is participating in the process of collaboration. Let’s distinguish between “cooperative collaboration,” where all those who share responsibility live within our physical or virtual walls (and would sit on the same side of the table at a physical or virtual meeting) and “adversarial review” among those with differing (and sometimes very much competing) interests.

We will try to answer the following questions:

What activities must be supported when drafting documents collaboratively?

How should these activities be different when the collaboration context is cooperative, and when it is reviewed by the opposing side?

Has the ability to electronically share our documents altered our activities in any way? Or do we consider sharing our documents electronically with outside parties as being ‘different’ at all?

How do tools for document comparison – the phase which identifies changes in document content – improve or hinder our process? What are the strengths and weaknesses of these tools? Are tools internal to Word better than third-party tools?

What do the third-party tools enable which internal Word functionality does not? What causes the document comparison process to break down? Once broken, how can it be fixed?

What are the differences between Word’s Track Changes, File Versions and Compare Documents features?

What techniques can be used to assure the identity of the persons who have worked on a document?

How does Word preserve evidence of the drafting process? What strategies can be used to avoid creating this information in the first place? When it is desired to include such information during drafting, how can it be cleaned out before delivery of a document?

How should documents be stored to promote successful collaboration and maintain a proper revision history? What capabilities are offered by the file system, enterprise-wide document management systems and Web-based collaboration systems? Where do Web-enabled on-line collaboration tools fit into the process – better still, when will they fit in?

We will begin answering these questions in the next column. For now, just realize how few years ago it was that we supported teams of proofreaders whose job it was to review paper copies of the original document against paper copies of the revised version. eyeballing any differences they found between the two. Indeed, the term “redline” was derived from the generation of hand-drawn underlines made using a red pencil or pen. Today, we electronically produce this compared or redlined result, accelerating our ability to review, then accept or decline, changes made between parties.

But we’re moving toward a new document processing arena: where the revision process occurs not between parties on paper, but between parties on-line. We expect nearly instantaneous, if not simultaneous access to documents as they are drafted. As connectivity barriers faced as few as three years ago become relics of the past, we struggle through the new and emerging issues surrounding the document collaboration task: Do we have the same word processing applications? Do we share the same comparison technologies? Which choices better provide for the client share moment, and which choices produce a high-maintenance relationship where successful sharing is elusive?

The exchange of paper drafts of documents created few of practice issues described above. While the arrival of word processing both accelerated and intensified the drafting process, other times, the freedom to make changes invited more frequent and involved revisions. The electronic exchange of documents, however, both creates opportunities for enhancement of the speed and thoroughness with which collaboration can be accomplished, and risks accidental or malicious change as well as intentional or unintentional exposure of the details of the development of a document draft.

One could hardly imagine a more fitting topic on which to practice collaborative drafting than the writing of this series. Thus, a collaborative drafting environment has been established, in which Sherry Kappel of Microsystems (www.microsystems.com) will share her expertise with Word, especially extensive experience in the art and agony of document comparison, and with the hazards of electronically sharing document content.

 

This 2000 article originally appeared in Office Watch.Subscribe to Office Watch free at http://www.office-watch.com/.

Word of Law No. 17 – Word Wish List

[Originally appeared 1999.]

Early in the summer, many of you offered suggestions for improvements to Microsoft Word. The following suggestions seem intriguing.

Layout

Several readers requested support for logical page subdivision of physical pages. This would be in addition to the tables or labels workarounds.

Improve line spacing, especially for equations and sub or superscripts. A reader suggested that a possible solution to the line spacing problem would be to provide a paragraph property that basically tells Word to turn off its “don’t overlap objects in one line with another at all costs” feature. This would allow the user to take responsibility for any overlaps and let them correct this problem.

Support portrait headers or footers on landscape pages. This would allow proper orientation for page numbers and other header or footer information in documents with a mixture of landscape and portrait orientation.

Views

After scrolling through a document in Print Preview, support exiting with the cursor moved to the matching location in the document instead of the location of the cursor when entering Print Preview.

Allow screen display of revision markings separately by author, and to review revisions sequentially for a particular author only. The reader suggested that an author can preserve all revisions in a marked up draft, while focusing temporarily only on those changes proposed by a particular colleague or adverse party, for example.

Tools

Allow Word to be able to sort by other than the first word in a field.

Improve spell checking:

(a) Offer an option to recognize a possessive form of a word marked to be ignored or have added to the custom dictionary in its nominative form.

(b) Suggest replacements for weird misspellings that arise only because a single character, adjacent on the QWERTY keyboard to the intended one, has been struck.

Searching

Support stronger find/replace wildcards (pattern matching). The reader commented that that pattern matching in Word 97 might generate a “pattern too complex” message more frequently than Word 95.

Offer conditional searching that would include “find occurrences of foo that are occurrences of foobar”. Example, Find all occurrences of “From:” that are not “^^pFrom:” (ie. “From: at the beginning of the sentence”)

Printing

Allow sections to print to different printers. This would assist with documents with some color diagrams, especially if the color printer is either much slower or more expensive than the black and white printer.

Add sections to the “Print what” choice in the Print dialog. On large, multi-sectioned documents, it would be very helpful to print the current section.

File Management

In the File Open dialog, offer automatic scroll down or filtering based on letters or numbers entered in the File Name field. There is no matching in Word 97. In Word 2000, the File Name field autocompletes to the nearest matching name, but the file list focus does not shift to highlight the matching file.

These are a few of the ideas offered by the readers of this column. Thanks again for the thoughtfulness of your comments. Rereading those e-mails reminded me how many issues have been raised. Please keep writing.

This 1999 article originally appeared in Office Watch.Subscribe to Office Watch free at http://www.office-watch.com/.

 

Word of Law No. 15 – Inside the Style Gallery

[Originally appeared 1999.]

Word of Law No. 14 touched on use of the Style Gallery. It deserves deeper exploration. We explored how a document acquires styles and their settings from the template which gave birth to it. On creation of a document, that template becomes the document’s “attached template.”

The Style Gallery permits the settings of the styles in a document to be changed by copying the styles from another template. In a default installation, the Style Gallery can be accessed from the Format menu. The Style Gallery itself is a fancy display tool that has a simple result. When a template is picked, the resulting command, as described last time, is “ActiveDocument.CopyStylesFromTemplate (Template Name as String).” This can only copy those styles that are in the indicated template. That step automatically overwrites the settings for any of those styles that are in the current document and adds the styles in the copied template that are not in the current document. It will not change any styles in the current document that are not in the copied document.

The Style Gallery displays all of the templates that are located in the file locations for User Templates and Workgroup Templates in a single alphabetical list. If an organization has taken pains to organize its templates in a set of practice area related folders (such as Corporate or Litigation in a law practice), the list in the Style Gallery will not display that organization, since all of the templates in the subfolders join the single alphabetical list.

Effective use of the Style Gallery and template development generally can be helped by the creation and maintenance of a set of templates whose only purpose is to serve as a container for the styles for a class of documents. For example, there could be “Blank Correspondence,” “Blank Agreement”, “Blank Policy Manual” and “Blank Report.” These should contain the full set of styles that should be applied to those documents, obedient to the naming conventions in the Laws of Styles (Issue 4.20). To make these most easily visible in the Style Gallery list, their name can be preceded by a non alphabetic character such as an underscore ( _ ) to force them to the top of the list.

The Style Gallery dialog contains a preview window, controlled by the option buttons in the lower left corner of the dialog. The first Preview option, “Document,” displays the text of the active document, as it would appear if the styles from the selected template were copied to it. When working with fairly complete documents, this option works fine. When working with blank documents, such as in template development, the second and third Preview options, “Example” and “Style Samples” can be helpful. It takes some work in template development, however, for anything to be visible when these options are selected. Without that preparation, the preview will read “There is no example for this template” or “There is no sample for this template.”

The trick is to create AutoText entries in the template titled (precisely) “Gallery Example” and “Gallery Style Samples,” respectively. Any text containing whatever selection of styles can be used in these two AutoText entries. Thus, it would be helpful to include the name of the styles used in the sample text.

The details on the use of styles just in these last two columns, as with nearly all of the issues that have been explored in this column, emphasize the critical importance for an organization to separate the regular use from development and maintenance of Microsoft Word’s tools. Users should have the tools they need to create, edit and complete their work without having to deal with the underlying complexity we have explored. If the central development staff has prepared templates properly, including tools such as the Blank templates described above, users can easily produce or modify their Word documents in accordance with organization standards. The general user can limit the time spent on tweaking their documents, often damaging consistency with standards in the process.

The central development staff should master the complexities, such as construction of templates with Style examples described above. Please do not understand this suggestion to mean that all Word development should be limited to a group closeted away from regular users. The development staff should incorporate lead users who have the skill and interest to master the features. Such users may start as testers or pilot users for the work of the developers, then perhaps even move into a development group over time.

In a future column, we will compare the use of the Style Gallery to changing the Attached Template. Understanding that fully requires the context of the other characteristics of a template.

 

This 1999 article originally appeared in Office Watch.Subscribe to Office Watch free at http://www.office-watch.com/.