<?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/"
		>
<channel>
	<title>Comments on: Troubled Tuesday (Reactions to Marcus Monday)</title>
	<atom:link href="http://davidrothman.net/2008/02/12/troubled-tuesday-reactions-to-marcus-monday/feed/" rel="self" type="application/rss+xml" />
	<link>http://davidrothman.net/2008/02/12/troubled-tuesday-reactions-to-marcus-monday/</link>
	<description>Health Information &#124; Geekery</description>
	<lastBuildDate>Wed, 01 Feb 2012 21:49:12 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rachel</title>
		<link>http://davidrothman.net/2008/02/12/troubled-tuesday-reactions-to-marcus-monday/comment-page-1/#comment-128576</link>
		<dc:creator>Rachel</dc:creator>
		<pubDate>Sat, 23 Feb 2008 17:20:55 +0000</pubDate>
		<guid isPermaLink="false">http://davidrothman.net/2008/02/12/troubled-tuesday-reactions-to-marcus-monday/#comment-128576</guid>
		<description>This is going to be a long one, and I apologize for that in advance. I tend to agree with T. Scott on these matters, for several reasons. I don&#039;t see any reason why librarianship journals as blogs should be singled out as a specialty (goose, gander, etc.) in this discussion, so I&#039;ll talk about this more generally. 

1) I believe there is value in having a final version of a manuscript on the record. Getting things out quickly isn&#039;t the only goal in publishing a paper, or shouldn&#039;t be. A larger goal is to contribute to the body of knowledge on a topic, in a way that can be cited and referred to and built upon in the future.  If the idea is that authors would post their work to a blog and solicit comments, presumably that manuscript is in a constant revisional state, forever and ever, unless the authors finally shut down comments (at what point is the amount of critique enough?) and post a &quot;final&quot; version. This is perhaps more important when large flaws are detected, and it is nice to have a record of the final version of the manuscript. When citing it, are you citing the final version, or some version in which the author tweaked something in the post? If you cite it, will changes happen later that render your reference irrelevant? I think this process would make it harder to talk about what a given author said or did, and it also puts a tremendous amount of trust in the authors not to change things in a way that is dishonest or unethical. With an official &quot;final&quot; version, the author is officially on the record, and I think that&#039;s an important concept.

2)&quot;The argument for pre-publication peer review is that it filters out poor research.&quot; Marcus seems to believe that this isn&#039;t an issue for library research, or at least that the stakes aren&#039;t high enough to matter. I would ask whether librarians seeking tenure and professional respect are really willing to hang themselves out there like this, simply assuming that what they&#039;ve done is good enough for public consumption. Like Scott, I believe this simply isn&#039;t true. Librarians are perfectly capable of producing research that, in its initial state, would be ripped to shreds by competent reviewers. I suspect that many would prefer that critique to happen more privately, to give them a chance to rethink their assumptions and presentation before opening themselves up to professional criticism and embarrasment. 

3) Peer review takes work. When a committed board of peer reviewers exists with a demonstrated interest in the process and a deadline for providing feedback, and an editor does the work Scott mentions prior to publication, it is a certainty that an author will receive feedback. Blog comments are an unreliable thing. Commenters may never hit on the one true major flaw of a manuscript, may not have the expertise to critique to manuscript, or may simply not have time to digest a full manuscript in its raw form and suggest all of the appropriate revisions. The manuscript and the professional body of knowledge may suffer from this, as its not just the shiny, catchy papers that need feedback and critique. 

4) Related to #3, it would be important to determine whether a manuscript was just open to whoever felt like commenting (or not), or if peer reviewers would be assigned drop by and comment. Would they be allowed to do so anonymously? Could an editor comment anonymously? If not, would the editor continue to make the needed comments Scott mentions about organization and content? I know some have advocated for peer review that is not anonymous, but I suspect that harsher, yet needed, criticisms might be held back if they had to be publicly written with a name and IP attached. 

I&#039;m not saying it couldn&#039;t be done. These are just a handful of issues I see as barriers that would have to be considered. Ultimately, I think part of the question is whether we&#039;re so determined as authors to put our unfiltered thoughts out there as fast as possible, or whether we&#039;re really interested in being accountable and on the record and contributing to the professional knowledge base in a substantial way, even if it takes a little longer.  I want to think about this a little longer.</description>
		<content:encoded><![CDATA[<p>This is going to be a long one, and I apologize for that in advance. I tend to agree with T. Scott on these matters, for several reasons. I don&#8217;t see any reason why librarianship journals as blogs should be singled out as a specialty (goose, gander, etc.) in this discussion, so I&#8217;ll talk about this more generally. </p>
<p>1) I believe there is value in having a final version of a manuscript on the record. Getting things out quickly isn&#8217;t the only goal in publishing a paper, or shouldn&#8217;t be. A larger goal is to contribute to the body of knowledge on a topic, in a way that can be cited and referred to and built upon in the future.  If the idea is that authors would post their work to a blog and solicit comments, presumably that manuscript is in a constant revisional state, forever and ever, unless the authors finally shut down comments (at what point is the amount of critique enough?) and post a &#8220;final&#8221; version. This is perhaps more important when large flaws are detected, and it is nice to have a record of the final version of the manuscript. When citing it, are you citing the final version, or some version in which the author tweaked something in the post? If you cite it, will changes happen later that render your reference irrelevant? I think this process would make it harder to talk about what a given author said or did, and it also puts a tremendous amount of trust in the authors not to change things in a way that is dishonest or unethical. With an official &#8220;final&#8221; version, the author is officially on the record, and I think that&#8217;s an important concept.</p>
<p>2)&#8221;The argument for pre-publication peer review is that it filters out poor research.&#8221; Marcus seems to believe that this isn&#8217;t an issue for library research, or at least that the stakes aren&#8217;t high enough to matter. I would ask whether librarians seeking tenure and professional respect are really willing to hang themselves out there like this, simply assuming that what they&#8217;ve done is good enough for public consumption. Like Scott, I believe this simply isn&#8217;t true. Librarians are perfectly capable of producing research that, in its initial state, would be ripped to shreds by competent reviewers. I suspect that many would prefer that critique to happen more privately, to give them a chance to rethink their assumptions and presentation before opening themselves up to professional criticism and embarrasment. </p>
<p>3) Peer review takes work. When a committed board of peer reviewers exists with a demonstrated interest in the process and a deadline for providing feedback, and an editor does the work Scott mentions prior to publication, it is a certainty that an author will receive feedback. Blog comments are an unreliable thing. Commenters may never hit on the one true major flaw of a manuscript, may not have the expertise to critique to manuscript, or may simply not have time to digest a full manuscript in its raw form and suggest all of the appropriate revisions. The manuscript and the professional body of knowledge may suffer from this, as its not just the shiny, catchy papers that need feedback and critique. </p>
<p>4) Related to #3, it would be important to determine whether a manuscript was just open to whoever felt like commenting (or not), or if peer reviewers would be assigned drop by and comment. Would they be allowed to do so anonymously? Could an editor comment anonymously? If not, would the editor continue to make the needed comments Scott mentions about organization and content? I know some have advocated for peer review that is not anonymous, but I suspect that harsher, yet needed, criticisms might be held back if they had to be publicly written with a name and IP attached. </p>
<p>I&#8217;m not saying it couldn&#8217;t be done. These are just a handful of issues I see as barriers that would have to be considered. Ultimately, I think part of the question is whether we&#8217;re so determined as authors to put our unfiltered thoughts out there as fast as possible, or whether we&#8217;re really interested in being accountable and on the record and contributing to the professional knowledge base in a substantial way, even if it takes a little longer.  I want to think about this a little longer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcus Banks</title>
		<link>http://davidrothman.net/2008/02/12/troubled-tuesday-reactions-to-marcus-monday/comment-page-1/#comment-128372</link>
		<dc:creator>Marcus Banks</dc:creator>
		<pubDate>Sun, 17 Feb 2008 17:59:41 +0000</pubDate>
		<guid isPermaLink="false">http://davidrothman.net/2008/02/12/troubled-tuesday-reactions-to-marcus-monday/#comment-128372</guid>
		<description>Thanks for the round-up of reactions David; I&#039;ve been oblivious these past several days!

Regards,
Marcus</description>
		<content:encoded><![CDATA[<p>Thanks for the round-up of reactions David; I&#8217;ve been oblivious these past several days!</p>
<p>Regards,<br />
Marcus</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marie</title>
		<link>http://davidrothman.net/2008/02/12/troubled-tuesday-reactions-to-marcus-monday/comment-page-1/#comment-128034</link>
		<dc:creator>Marie</dc:creator>
		<pubDate>Tue, 12 Feb 2008 21:09:08 +0000</pubDate>
		<guid isPermaLink="false">http://davidrothman.net/2008/02/12/troubled-tuesday-reactions-to-marcus-monday/#comment-128034</guid>
		<description>see the post at MLA&#039;s Task Force on Social Networking Software blog to read about an author posting chapters of a book on his blog, using the comments as peer-review: http://sns.mlanet.org/blog/2008/01/28/blog-based-peer-review/.</description>
		<content:encoded><![CDATA[<p>see the post at MLA&#8217;s Task Force on Social Networking Software blog to read about an author posting chapters of a book on his blog, using the comments as peer-review: <a href="http://sns.mlanet.org/blog/2008/01/28/blog-based-peer-review/." rel="nofollow">http://sns.mlanet.org/blog/2008/01/28/blog-based-peer-review/.</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

