<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Reviewing a Journal Paper - Guidelines</title>
	<link>http://windowsil.org/2006/09/11/reviewing-a-paper-guidelines/</link>
	<description>Your window into the Wireless Systems Innovation Laboratory</description>
	<pubDate>Sun, 27 May 2012 13:08:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.3</generator>

	<item>
		<title>by: WNCG Blog</title>
		<link>http://windowsil.org/2006/09/11/reviewing-a-paper-guidelines/#comment-80482</link>
		<pubDate>Tue, 25 Jan 2011 02:06:58 +0000</pubDate>
		<guid>http://windowsil.org/2006/09/11/reviewing-a-paper-guidelines/#comment-80482</guid>
					<description>[...] Jeffrey G. Andrews, adapted and in some cases outright plagiarized from Prof. R. Heath’s guidelines .  The following should be interpreted as the opinions of Prof. Andrews and his alone. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Jeffrey G. Andrews, adapted and in some cases outright plagiarized from Prof. R. Heath’s guidelines .  The following should be interpreted as the opinions of Prof. Andrews and his alone. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jeff Andrews</title>
		<link>http://windowsil.org/2006/09/11/reviewing-a-paper-guidelines/#comment-6451</link>
		<pubDate>Tue, 08 May 2007 22:24:24 +0000</pubDate>
		<guid>http://windowsil.org/2006/09/11/reviewing-a-paper-guidelines/#comment-6451</guid>
					<description>Nice blog, very detailed and I agree with all of it.  I would, however, add one following opinion.  As an editor, I have found that a significant minority of papers (1/3 or more) aren't even at the standard that I think they deserve a serious review by 3 experts in the area.  They are poorly written and have no or virtually no novelty, and show naivety about research.

Usually, it is easy to identify such papers by reading the abstract and introduction and seeing that there really is no contribution over prior work, many key references are missing, English is really bad, etc.  In these cases, I do not believe a student should spend more than an hour on the review.  The rest of the paper should be glanced through, and problems with the paper still need to be documented, but you don't need to spend a whole day tearing the paper apart.  This is a waste of time. In these cases, a 2 paragraph decision is sufficient.</description>
		<content:encoded><![CDATA[<p>Nice blog, very detailed and I agree with all of it.  I would, however, add one following opinion.  As an editor, I have found that a significant minority of papers (1/3 or more) aren&#8217;t even at the standard that I think they deserve a serious review by 3 experts in the area.  They are poorly written and have no or virtually no novelty, and show naivety about research.</p>
<p>Usually, it is easy to identify such papers by reading the abstract and introduction and seeing that there really is no contribution over prior work, many key references are missing, English is really bad, etc.  In these cases, I do not believe a student should spend more than an hour on the review.  The rest of the paper should be glanced through, and problems with the paper still need to be documented, but you don&#8217;t need to spend a whole day tearing the paper apart.  This is a waste of time. In these cases, a 2 paragraph decision is sufficient.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Robert Heath</title>
		<link>http://windowsil.org/2006/09/11/reviewing-a-paper-guidelines/#comment-73</link>
		<pubDate>Sat, 16 Sep 2006 00:16:16 +0000</pubDate>
		<guid>http://windowsil.org/2006/09/11/reviewing-a-paper-guidelines/#comment-73</guid>
					<description>Regarding the normalization issue, I think you have to go for your gut instinct for journal papers. For conference papers, usually I get 5-20 to review at a time so I have a good feeling about the top versus the bottom and can calibrate accordingly. You have to be careful. Sometimes there is the temptation to give papers that are well written and easy to understand a low score because it is &quot;obvious&quot; when a paper with the same technical content but more obscure would be more highly rated.</description>
		<content:encoded><![CDATA[<p>Regarding the normalization issue, I think you have to go for your gut instinct for journal papers. For conference papers, usually I get 5-20 to review at a time so I have a good feeling about the top versus the bottom and can calibrate accordingly. You have to be careful. Sometimes there is the temptation to give papers that are well written and easy to understand a low score because it is &#8220;obvious&#8221; when a paper with the same technical content but more obscure would be more highly rated.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Bob Daniels</title>
		<link>http://windowsil.org/2006/09/11/reviewing-a-paper-guidelines/#comment-72</link>
		<pubDate>Thu, 14 Sep 2006 21:22:45 +0000</pubDate>
		<guid>http://windowsil.org/2006/09/11/reviewing-a-paper-guidelines/#comment-72</guid>
					<description>One of the problems that I have with reviews is that the review scale is not normalized.  Most review forms have  criteria which you are supposed to rate 1-4 where 4=groundbreaking research, 3= solid contribution, 2=average work, 1=no contribution.  Personally I rarely award a 3 and have never rewarded a 4.  In my opinion 4's should be saved for contributions of the magnitude of Alamouti's diversity scheme (probably wouldn't ask a student to review such a paper).  2 would represent your typical incremental paper (what I tend to give) and 3 lies somewhere in between.  1 would be for all papers whose contribution is not worthy of publication.  However, after reviewing papers for conferences you'll see many 4's and 3's.  Sometimes I think that papers are accepted mainly because the reviewers' scales were more generous than the reviewers of other papers.  I don't think there is anything you can do about this, but it's frustrating!</description>
		<content:encoded><![CDATA[<p>One of the problems that I have with reviews is that the review scale is not normalized.  Most review forms have  criteria which you are supposed to rate 1-4 where 4=groundbreaking research, 3= solid contribution, 2=average work, 1=no contribution.  Personally I rarely award a 3 and have never rewarded a 4.  In my opinion 4&#8217;s should be saved for contributions of the magnitude of Alamouti&#8217;s diversity scheme (probably wouldn&#8217;t ask a student to review such a paper).  2 would represent your typical incremental paper (what I tend to give) and 3 lies somewhere in between.  1 would be for all papers whose contribution is not worthy of publication.  However, after reviewing papers for conferences you&#8217;ll see many 4&#8217;s and 3&#8217;s.  Sometimes I think that papers are accepted mainly because the reviewers&#8217; scales were more generous than the reviewers of other papers.  I don&#8217;t think there is anything you can do about this, but it&#8217;s frustrating!
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Edward</title>
		<link>http://windowsil.org/2006/09/11/reviewing-a-paper-guidelines/#comment-71</link>
		<pubDate>Thu, 14 Sep 2006 06:26:43 +0000</pubDate>
		<guid>http://windowsil.org/2006/09/11/reviewing-a-paper-guidelines/#comment-71</guid>
					<description>&amp;#62;Do not rely just on the list provided by the authors

I totally agree with you! My experience is that some authors usually do self-reference, i.e. cite their own works for the topics / areas of the manuscripts only ...

Sometimes ... there is even an overclaim on the title of the manuscript, which is very bad ...</description>
		<content:encoded><![CDATA[<p>&gt;Do not rely just on the list provided by the authors</p>
<p>I totally agree with you! My experience is that some authors usually do self-reference, i.e. cite their own works for the topics / areas of the manuscripts only &#8230;</p>
<p>Sometimes &#8230; there is even an overclaim on the title of the manuscript, which is very bad &#8230;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Seijoon</title>
		<link>http://windowsil.org/2006/09/11/reviewing-a-paper-guidelines/#comment-69</link>
		<pubDate>Tue, 12 Sep 2006 19:02:58 +0000</pubDate>
		<guid>http://windowsil.org/2006/09/11/reviewing-a-paper-guidelines/#comment-69</guid>
					<description>I think that this guideline will be also helpful to write a paper because authors can see through the reviewer's viewpoint.</description>
		<content:encoded><![CDATA[<p>I think that this guideline will be also helpful to write a paper because authors can see through the reviewer&#8217;s viewpoint.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>

