<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>See Also... &#187; oclc</title>
	<atom:link href="http://stevelawson.name/seealso/archives/tag/oclc/feed" rel="self" type="application/rss+xml" />
	<link>http://stevelawson.name/seealso</link>
	<description>a library weblog by Steve Lawson</description>
	<lastBuildDate>Wed, 16 May 2012 23:03:48 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>ARL Task Force report on the OCLC records policy</title>
		<link>http://stevelawson.name/seealso/archives/2009/02/arl_task_force_report_on_the_oclc_records_policy.html</link>
		<comments>http://stevelawson.name/seealso/archives/2009/02/arl_task_force_report_on_the_oclc_records_policy.html#comments</comments>
		<pubDate>Mon, 23 Feb 2009 18:06:20 +0000</pubDate>
		<dc:creator>steve</dc:creator>
				<category><![CDATA[Library]]></category>
		<category><![CDATA[arl]]></category>
		<category><![CDATA[oclc]]></category>
		<category><![CDATA[report]]></category>

		<guid isPermaLink="false">http://stevelawson.name/seealso/?p=9322</guid>
		<description><![CDATA[The ARL has reported on their take on the OCLC records policy, and it's a good read.]]></description>
			<content:encoded><![CDATA[<p>From <a href="http://cavlec.yarinareth.net/2009/02/21/in-which-arl-gets-it-right-again/">Caveat Lector</a>, I learned that the Association of Research Libraries&#8217; Ad Hoc Task Force to Review the Proposed OCLC Policy for Use and Transfer of WorldCat Records has <a href="http://www.arl.org/news/pr/oclc-policy-20feb09.shtml">released their final report</a>. It is a concise, well-written report that anyone who has been following this story will want to read.</p>
<p>Given that the task force itself had trouble understanding the intent of some parts of the proposed OCLC policy (and they found at least one area where &#8220;OCLC staff seem unaware of this provision and unable to explain its intended meaning,&#8221; (5)) and given that the Task Force points out numerous areas of ambiguity and contradiction, I feel better about my own inability to really understand what was going on in the OCLC policy change.</p>
<p>Some of the most interesting parts of are a discussion or critique of the process by which OCLC wrote and put forward the policy:</p>
<blockquote>
<p>The task force began its work with intent to focus mainly on the content of the policy document rather than on the process of its introduction, a process already widely acknowledged as flawed.  In the course of our analyses and discussions, we came to the conclusion that in the context of the collective endeavor necessary to create and maintain the WorldCat database, process and content are inextricably intertwined. (7)</p>
</blockquote>
<p>. . .</p>
<blockquote>
<p>In the eyes of the community, the guidelines expressed a mutual social contract, and the new Policy represents an authoritarian, unilaterally imposed legal restriction. Given that “<em>together</em> OCLC and its member libraries make up the world’s largest <em>consortium</em>” (emphasis ours) [i.e., ARL's] and that the substance and nature of the new Policy is so significant, it comes as no surprise that the membership has responded negatively to the introduction of a unilateral contract by OCLC as a <em>fait accompli</em>. (8)</p>
</blockquote>
<p>I also found one paragraph on unanimity and consensus to be particularly interesting:</p>
<blockquote>
<p>There is not, and will not be, a universal viewpoint on all issues that are covered by a policy.  There is not unanimity within the task force on the core issue:  while the majority of members believe that it is desirable to have a policy that limits large-scale redistribution of records that could be harmful to the collective, it is not a unanimous view even within the small membership of the task force.  But it is realistic to aim for consensus on a policy, i.e., agreement to follow a policy even though it is not identical in all ways to one’s individual, or even institutional, views.  Certainly a process for member input and engagementnecessary for such consensus. (9)</p>
</blockquote>
<p>And all those interesting parts don&#8217;t even begin to cover the part where they really fisk the policy itself, nor have I yet mentioned the appendix by a technology law and policy lawyer who examines the &#8220;Enforceability of OCLC Policy for Use and Transfer of WorldCat Records.&#8221; Again, if you care at all about this subject, you&#8217;ll want to read the report.</p>
<hr />
<p>On a related note, <a href="http://pegasuslibrarian.blogspot.com/2009/02/oclc-question-for-masses.html">Iris Jastram would like to see blog or email list posts by OCLC member libraries&#8217; staff (not OCLC employees) who have come out in favor of the policy change</a>. I would, too. I&#8217;m sure they are out there&#8211;if the ARL Task Force isn&#8217;t unanimous in its opinion, it is impossible that all librarians would be united&#8211;I just haven&#8217;t come across them. Drop Iris or me a link if you know where we can find one.</p>
]]></content:encoded>
			<wfw:commentRss>http://stevelawson.name/seealso/archives/2009/02/arl_task_force_report_on_the_oclc_records_policy.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Clarifications and cautions</title>
		<link>http://stevelawson.name/seealso/archives/2008/11/clarifications_and_cautions.html</link>
		<comments>http://stevelawson.name/seealso/archives/2008/11/clarifications_and_cautions.html#comments</comments>
		<pubDate>Tue, 18 Nov 2008 17:36:50 +0000</pubDate>
		<dc:creator>steve</dc:creator>
				<category><![CDATA[Tools]]></category>
		<category><![CDATA[library of alexandria]]></category>
		<category><![CDATA[oclc]]></category>

		<guid isPermaLink="false">http://stevelawson.name/seealso/?p=870</guid>
		<description><![CDATA[What Jessamyn said. And then what she said again. And then a little of what I said about the controversy surrounding changes to OCLC policy.]]></description>
			<content:encoded><![CDATA[<p>I was going to write a post wherein I mentioned the <a href="http://www.oclc.org/worldcat/catalog/policy/">OCLC policy changes</a> or &#8220;clarifications&#8221; or whatever they are and linked out to a few library blogs and sites like Inside HigherEd and Slashdot and the like to show how this is being discussed inside and outside the library world.</p>
<p>But then Jessamyn did <a href="http://www.librarian.net/stax/2536/what-is-up-with-oclc/">pretty much the same post that I was going to do</a>. Please read that if you haven&#8217;t already.</p>
<p>My main original contribution was going to be the observation that perhaps in the library blogosphere we have been so busy hating ALA and ILS vendors that we have forgotten to hate OCLC, too. In truth, I wasn&#8217;t inclined to be too sympathetic to OCLC&#8217;s point of view, but (as I would have said in this now-mostly-redundant post) I would really like to read something written by a person who wasn&#8217;t either on OCLC&#8217;s payroll, or intimately involved in a project directly threatened by the OCLC &#8220;clarifications.&#8221;</p>
<p>Then my main man Josh Neff <a href="http://friendfeed.com/e/bebe6456-b308-4f03-9d11-dd4a44f886da/Rule-1-for-Surviving-Paradigm-Shifts-Don-t-S-t/">posted a link to FriendFeed</a> for Stefano Mazzocchi&#8217;s post <a href="http://www.betaversion.org/~stefano/linotype/news/220/">Rule #1 for Surviving Paradigm Shifts: Don’t S**t Where You Eat</a>. So I was going to link to that and say that it was one of the more convincing posts I have read about the issue.</p>
<p>But then Jessamyn did <a href="http://www.librarian.net/stax/2548/oclc-kerfuffle-summarized-in-a-way-i-agree-with/">pretty much the same post that I was going to do. Again.</a></p>
<p>So let me just say this before Jessamyn can say it. Mazzocchi has a lot to say about OCLC&#8217;s monopoly and how they can best protect it. He says in part:</p>
<blockquote>
<p>OCLC can do exactly one of two things now:</p>
<ol>
<li>open up itself so that it becomes the de-facto centroid of an otherwise opened and more diverse ecosystem, where people are excited to contribute to them and not forced to.</li>
<li>try to use all the power they have to stop others from competing with them and displace them.</li>
</ol>
<p>The first one seems like the most risky one, but it&#8217;s really the second.</p>
</blockquote>
<p>and</p>
<blockquote>
<p>By locking the place down even more and alienating a bunch of alpha-librarians, they’re doing nothing but catalyze the movement that will eventually lead to their obsolescence and the establishment of another organization, similar in every aspect to OCLC save for one: the short sightedness in how to entice contribution without alienating the contributors.</p>
</blockquote>
<p>Coincidentally, I was reading Matthew Battles&#8217; <a href="http://openlibrary.org/b/OL7451085M"><em>Library: An Unquiet History</em></a> today and came across this interesting tidbit on page 29 about the Library of Alexandria:</p>
<blockquote>
<p>In an effort to stop the growth of the libraries at Rhodes and Pergamum, both of which threatened Alexandria&#8217;s preeminence, the city&#8217;s rulers banned the export of papyrus. The move backfired, however, spurring the Pergamenes to invent parchment (<em>charta pergamenum</em>), which for its strength and reusability would prove to be the preferred writing medium in Europe for more than a thousand years.</p>
</blockquote>
<p>That seems like a reasonably appropriate cautionary tale.</p>
]]></content:encoded>
			<wfw:commentRss>http://stevelawson.name/seealso/archives/2008/11/clarifications_and_cautions.html/feed</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>

