<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Peer-Review Scandal Shakes French Geologists</title>
	<atom:link href="http://scholarlykitchen.sspnet.org/2009/01/09/peer-review-scandal-shakes-french-geologists/feed/" rel="self" type="application/rss+xml" />
	<link>http://scholarlykitchen.sspnet.org/2009/01/09/peer-review-scandal-shakes-french-geologists/</link>
	<description>What&#039;s Hot &#38; What&#039;s Cooking in Scholarly Publishing - from the Society for Scholarly Publishing</description>
	<lastBuildDate>Wed, 15 Feb 2012 17:25:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Dave Jago</title>
		<link>http://scholarlykitchen.sspnet.org/2009/01/09/peer-review-scandal-shakes-french-geologists/#comment-2226</link>
		<dc:creator><![CDATA[Dave Jago]]></dc:creator>
		<pubDate>Mon, 12 Jan 2009 10:30:46 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=2498#comment-2226</guid>
		<description><![CDATA[Our process is described by Richard Sever, with the additional twist that I assign the paper to an Associate Editor without letting the EIC know which one (all correspondence is channelled through the office to maintain the blinding). The Associate Editor can then make an adverse decision without risking any fallout.]]></description>
		<content:encoded><![CDATA[<p>Our process is described by Richard Sever, with the additional twist that I assign the paper to an Associate Editor without letting the EIC know which one (all correspondence is channelled through the office to maintain the blinding). The Associate Editor can then make an adverse decision without risking any fallout.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Sever</title>
		<link>http://scholarlykitchen.sspnet.org/2009/01/09/peer-review-scandal-shakes-french-geologists/#comment-2211</link>
		<dc:creator><![CDATA[Richard Sever]]></dc:creator>
		<pubDate>Fri, 09 Jan 2009 15:35:54 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.sspnet.org/?p=2498#comment-2211</guid>
		<description><![CDATA[Phil - This is only an issue in journals that have a single, all-powerful Editor-in-Chief (there are numerous other drawbacks to this beyond conflict of interest).

 The simple solution is to have Associate Editors empowered to make decisions independently and make it policy that they handle any submissions for which the Editor-in-Chief would be conflicted. The hard part is dealing with potential fall-out that can ensue - but that is all part of being a wise publisher who picks responsible Editors.]]></description>
		<content:encoded><![CDATA[<p>Phil &#8211; This is only an issue in journals that have a single, all-powerful Editor-in-Chief (there are numerous other drawbacks to this beyond conflict of interest).</p>
<p> The simple solution is to have Associate Editors empowered to make decisions independently and make it policy that they handle any submissions for which the Editor-in-Chief would be conflicted. The hard part is dealing with potential fall-out that can ensue &#8211; but that is all part of being a wise publisher who picks responsible Editors.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

