<?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: The Importance of Being First</title>
	<atom:link href="http://scholarlykitchen.sspnet.org/2008/08/07/the-importance-of-being-first/feed/" rel="self" type="application/rss+xml" />
	<link>http://scholarlykitchen.sspnet.org/2008/08/07/the-importance-of-being-first/</link>
	<description>What&#039;s Hot &#38; What&#039;s Cooking in Scholarly Publishing - from the Society for Scholarly Publishing</description>
	<lastBuildDate>Thu, 02 Sep 2010 11:43:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Downloads, Citations, and Positional Effects in the arXiv &#171; The Scholarly Kitchen</title>
		<link>http://scholarlykitchen.sspnet.org/2008/08/07/the-importance-of-being-first/#comment-4066</link>
		<dc:creator>Downloads, Citations, and Positional Effects in the arXiv &#171; The Scholarly Kitchen</dc:creator>
		<pubDate>Wed, 29 Jul 2009 10:41:49 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.wordpress.com/?p=544#comment-4066</guid>
		<description>[...] and confirming an earlier study on the positional effects in the arXiv, Haque and Ginsparg focused this time on articles deposited between 2002-2004 in three subsections [...]</description>
		<content:encoded><![CDATA[<p>[...] and confirming an earlier study on the positional effects in the arXiv, Haque and Ginsparg focused this time on articles deposited between 2002-2004 in three subsections [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bench Marks &#187; Blog Archive &#187; Link Roundup</title>
		<link>http://scholarlykitchen.sspnet.org/2008/08/07/the-importance-of-being-first/#comment-655</link>
		<dc:creator>Bench Marks &#187; Blog Archive &#187; Link Roundup</dc:creator>
		<pubDate>Thu, 07 Aug 2008 15:03:02 +0000</pubDate>
		<guid isPermaLink="false">http://scholarlykitchen.wordpress.com/?p=544#comment-655</guid>
		<description>[...] The Importance of Being First The Scholarly Kitchen looks at the ways scientists are gaming the arXiv system, and submitting their papers at specific times to ensure a higher listing in e-mailed announcements, which results in more citations. This is something very worrying about switching from our current editorially-supervised system of publishing papers to an open system. Sure, the current system isn&#8217;t perfect, but things like arXiv and social networks are very open to manipulation. A switch from one to the other may just be a lateral move in terms of bias and favoritism. Note that most of the proponents of Web 2.0 for science are all well-networked and well-versed in how things work, so adoption of these technologies would give the evangelists a distinct advantage over everyone else. [...]</description>
		<content:encoded><![CDATA[<p>[...] The Importance of Being First The Scholarly Kitchen looks at the ways scientists are gaming the arXiv system, and submitting their papers at specific times to ensure a higher listing in e-mailed announcements, which results in more citations. This is something very worrying about switching from our current editorially-supervised system of publishing papers to an open system. Sure, the current system isn&#8217;t perfect, but things like arXiv and social networks are very open to manipulation. A switch from one to the other may just be a lateral move in terms of bias and favoritism. Note that most of the proponents of Web 2.0 for science are all well-networked and well-versed in how things work, so adoption of these technologies would give the evangelists a distinct advantage over everyone else. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
