<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Membership Meeting, April 2007</title>
	<link>http://www.stc-techedit.org/2007/04/17/membership-meeting-april-2007/</link>
	<description></description>
	<pubDate>Sun, 06 Jul 2008 21:01:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2</generator>

	<item>
		<title>By: Marjorie</title>
		<link>http://www.stc-techedit.org/2007/04/17/membership-meeting-april-2007/#comment-229</link>
		<author>Marjorie</author>
		<pubDate>Wed, 30 May 2007 18:14:56 +0000</pubDate>
		<guid>http://www.stc-techedit.org/2007/04/17/membership-meeting-april-2007/#comment-229</guid>
		<description>I agree with Violet's comments above and am looking forward to the next virtual SIG meeting.</description>
		<content:encoded><![CDATA[<p>I agree with Violet&#8217;s comments above and am looking forward to the next virtual SIG meeting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: violet</title>
		<link>http://www.stc-techedit.org/2007/04/17/membership-meeting-april-2007/#comment-228</link>
		<author>violet</author>
		<pubDate>Wed, 30 May 2007 18:11:10 +0000</pubDate>
		<guid>http://www.stc-techedit.org/2007/04/17/membership-meeting-april-2007/#comment-228</guid>
		<description>I really enjoyed this format. The course materials were a sufficient replacement to a shared or remote desktop experience.

My only comment is to remind users beforehand to mute their telephone receivers. 

I would happily participate in future events of this sort.</description>
		<content:encoded><![CDATA[<p>I really enjoyed this format. The course materials were a sufficient replacement to a shared or remote desktop experience.</p>
<p>My only comment is to remind users beforehand to mute their telephone receivers. </p>
<p>I would happily participate in future events of this sort.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mcorbin</title>
		<link>http://www.stc-techedit.org/2007/04/17/membership-meeting-april-2007/#comment-162</link>
		<author>mcorbin</author>
		<pubDate>Wed, 18 Apr 2007 18:04:00 +0000</pubDate>
		<guid>http://www.stc-techedit.org/2007/04/17/membership-meeting-april-2007/#comment-162</guid>
		<description>Wow!  This sounds fantastic.  I'll contact you offline to see if we can have you tell us more or present at a future membership meeting!  We're glad that you found the first membership meeting so useful.</description>
		<content:encoded><![CDATA[<p>Wow!  This sounds fantastic.  I&#8217;ll contact you offline to see if we can have you tell us more or present at a future membership meeting!  We&#8217;re glad that you found the first membership meeting so useful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aashita Shekhar</title>
		<link>http://www.stc-techedit.org/2007/04/17/membership-meeting-april-2007/#comment-161</link>
		<author>Aashita Shekhar</author>
		<pubDate>Wed, 18 Apr 2007 05:08:34 +0000</pubDate>
		<guid>http://www.stc-techedit.org/2007/04/17/membership-meeting-april-2007/#comment-161</guid>
		<description>It was a true pleasure to be a part of virtual SIG membership meeting held on April 17. The presentation was informative and inspiring. I could see similarities between your work and my experience. I would like to share my experience of working on an editing tool that may help you enhance features in your in-house tool.
Let me first introduce myself first. I was working as a Technical Writer/Editor in India. Recently I moved to Greater Boston area. 

The editing tool that I used was a Microsoft Word Add-in that helps reduce the turnaround time for document reviews, by automating various review tasks like calculating Documentation Quality Index (DQI) and generating the defect log and review report in excel format. This tool automates the task of logging defects based on its severity and classification. It is important that defects be classified and categorised correctly, and appropriate edit corrections made to the document. Those defects are categorised as accessibility, accuracy, audience orientation, clarity, completeness, consistency, presentation, redundancy, and more.

As an editor, I used to assign severity to those defects as medium, high or low and log defects using the editing tool. The edit corrections are automatically logged in MS WORD.  After I had finished editing, I used to generate defect log in an excel format. This excel was automatically generated by the editing tool.

The benefits of using this editing tool are manifold, such as: 
•	Providing a numerical analysis of document’s quality
•	Indicating the specific problem areas of the document to both the author and the reviewer. Example: A high incidence of the “consistency” defect type along with the related remarks indicates the key problem area of the document and focussed action can be taken to rectify this.
•	Maintaining record of the remarks of the reviewer and the author’s response to them.
•	Providing the two way communication. 
Example: The author may not be able to implement a formatting suggestion by the reviewer and can document the reason in the defect log.
•	Improving both the author’s documentation skills as well as reviewer’s understanding of the document.
•	Providing a standardized method of editing across the enterprise.

Hope this helps.</description>
		<content:encoded><![CDATA[<p>It was a true pleasure to be a part of virtual SIG membership meeting held on April 17. The presentation was informative and inspiring. I could see similarities between your work and my experience. I would like to share my experience of working on an editing tool that may help you enhance features in your in-house tool.<br />
Let me first introduce myself first. I was working as a Technical Writer/Editor in India. Recently I moved to Greater Boston area. </p>
<p>The editing tool that I used was a Microsoft Word Add-in that helps reduce the turnaround time for document reviews, by automating various review tasks like calculating Documentation Quality Index (DQI) and generating the defect log and review report in excel format. This tool automates the task of logging defects based on its severity and classification. It is important that defects be classified and categorised correctly, and appropriate edit corrections made to the document. Those defects are categorised as accessibility, accuracy, audience orientation, clarity, completeness, consistency, presentation, redundancy, and more.</p>
<p>As an editor, I used to assign severity to those defects as medium, high or low and log defects using the editing tool. The edit corrections are automatically logged in MS WORD.  After I had finished editing, I used to generate defect log in an excel format. This excel was automatically generated by the editing tool.</p>
<p>The benefits of using this editing tool are manifold, such as:<br />
•	Providing a numerical analysis of document’s quality<br />
•	Indicating the specific problem areas of the document to both the author and the reviewer. Example: A high incidence of the “consistency” defect type along with the related remarks indicates the key problem area of the document and focussed action can be taken to rectify this.<br />
•	Maintaining record of the remarks of the reviewer and the author’s response to them.<br />
•	Providing the two way communication.<br />
Example: The author may not be able to implement a formatting suggestion by the reviewer and can document the reason in the defect log.<br />
•	Improving both the author’s documentation skills as well as reviewer’s understanding of the document.<br />
•	Providing a standardized method of editing across the enterprise.</p>
<p>Hope this helps.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
