<?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: We call dibs! (or, the genius of the Harvard mandate)</title>
	<atom:link href="http://everybodyslibraries.com/2008/02/22/we-call-dibs-or-the-genius-of-the-harvard-mandate/feed/" rel="self" type="application/rss+xml" />
	<link>http://everybodyslibraries.com/2008/02/22/we-call-dibs-or-the-genius-of-the-harvard-mandate/</link>
	<description>Libraries for everyone, by everyone, shared with everyone, about everything</description>
	<pubDate>Mon, 01 Dec 2008 23:16:35 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John Mark Ockerbloom</title>
		<link>http://everybodyslibraries.com/2008/02/22/we-call-dibs-or-the-genius-of-the-harvard-mandate/#comment-149</link>
		<dc:creator>John Mark Ockerbloom</dc:creator>
		<pubDate>Wed, 27 Feb 2008 18:48:19 +0000</pubDate>
		<guid isPermaLink="false">http://everybodyslibraries.wordpress.com/?p=33#comment-149</guid>
		<description>Thanks for your comments, Adam.  I'd agree that getting hold of the content is a non-trivial issue.  In this post, I just gave it a quick mention, since I wanted to focus on the copyright issue.  Here at Penn, we're handling content acquisition in various ways, including making sure we have commitment from the departments that join, and hiring staff to bring the content in.   Our new Selected Works service is also intended to encourage more faculty to post their own work and/or citations of their work, which will then be easier for us to pull into the repository as well.  And yes, down the road I think automated protocols like SWORD and OAI will be important as well.

As far as I'm aware, though, Penn haven't done anything in terms of calling dibs on copyright, though; we have to work with whatever rights are left over after the publisher agreements are signed.  (We do have agreements with departments to deposit work, but they don't say anything about pre-emptively assigning certain copyright-realted rights to new creations.)  If we did have dibs, we could potentially bring in more content with less work, since the copyright clearance we now engage in could be greatly simplified.  But that's basically a change in the conditions of faculty employment, which the faculty themselves would have to embrace.  And at Harvard, they did.</description>
		<content:encoded><![CDATA[<p>Thanks for your comments, Adam.  I&#8217;d agree that getting hold of the content is a non-trivial issue.  In this post, I just gave it a quick mention, since I wanted to focus on the copyright issue.  Here at Penn, we&#8217;re handling content acquisition in various ways, including making sure we have commitment from the departments that join, and hiring staff to bring the content in.   Our new Selected Works service is also intended to encourage more faculty to post their own work and/or citations of their work, which will then be easier for us to pull into the repository as well.  And yes, down the road I think automated protocols like SWORD and OAI will be important as well.</p>
<p>As far as I&#8217;m aware, though, Penn haven&#8217;t done anything in terms of calling dibs on copyright, though; we have to work with whatever rights are left over after the publisher agreements are signed.  (We do have agreements with departments to deposit work, but they don&#8217;t say anything about pre-emptively assigning certain copyright-realted rights to new creations.)  If we did have dibs, we could potentially bring in more content with less work, since the copyright clearance we now engage in could be greatly simplified.  But that&#8217;s basically a change in the conditions of faculty employment, which the faculty themselves would have to embrace.  And at Harvard, they did.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Corson-Finnerty</title>
		<link>http://everybodyslibraries.com/2008/02/22/we-call-dibs-or-the-genius-of-the-harvard-mandate/#comment-147</link>
		<dc:creator>Adam Corson-Finnerty</dc:creator>
		<pubDate>Sat, 23 Feb 2008 17:13:09 +0000</pubDate>
		<guid isPermaLink="false">http://everybodyslibraries.wordpress.com/?p=33#comment-147</guid>
		<description>John,

I appreciate your thoughtful comments on the Harvard FAS decision.  I suppose that the key point is that Harvard has established a "default" in favor of Open Access.

In reading about this decision, I found myself wondering exactly how it was going to be carried out.  It's one thing to "mandate" that a faculty member do X, Y, or Z.  It's another thing to get him or her to do it.  As you know, when universitys have created repositories and invited their faculty to add their stuff, most faculty have not bothered to do so.

It appears that the Harvard Library's Office of Scholarly Communication will be charged with making the policy into reality.  I suspect that if they rely on the individual faculty member to submit their finished article electronically, they will have tons of problems with compliance unless they set up some sort of "automated" system, or the libarians do the work for them, through electronic harvesting.

I would guess that Harvard (and the rest of us) will be heavily influenced by the methods that NIH adopts.  See "How to Comply" at  http://publicaccess.nih.gov/ 

It is my impression that at the Penn Libraries, we have used a "Harvard Lite" policy.  We have approached the Dean and Faculty of a specific school (Engineering, Social Policy and Practice, Nursing) and asked them to adopt a default in favor of publication in our repository.  Then we harvest articles for each faculty member, show the list to her/him and allow them to cross out anything they don't want added.  John, have I got that right?</description>
		<content:encoded><![CDATA[<p>John,</p>
<p>I appreciate your thoughtful comments on the Harvard FAS decision.  I suppose that the key point is that Harvard has established a &#8220;default&#8221; in favor of Open Access.</p>
<p>In reading about this decision, I found myself wondering exactly how it was going to be carried out.  It&#8217;s one thing to &#8220;mandate&#8221; that a faculty member do X, Y, or Z.  It&#8217;s another thing to get him or her to do it.  As you know, when universitys have created repositories and invited their faculty to add their stuff, most faculty have not bothered to do so.</p>
<p>It appears that the Harvard Library&#8217;s Office of Scholarly Communication will be charged with making the policy into reality.  I suspect that if they rely on the individual faculty member to submit their finished article electronically, they will have tons of problems with compliance unless they set up some sort of &#8220;automated&#8221; system, or the libarians do the work for them, through electronic harvesting.</p>
<p>I would guess that Harvard (and the rest of us) will be heavily influenced by the methods that NIH adopts.  See &#8220;How to Comply&#8221; at  <a href="http://publicaccess.nih.gov/" rel="nofollow">http://publicaccess.nih.gov/</a> </p>
<p>It is my impression that at the Penn Libraries, we have used a &#8220;Harvard Lite&#8221; policy.  We have approached the Dean and Faculty of a specific school (Engineering, Social Policy and Practice, Nursing) and asked them to adopt a default in favor of publication in our repository.  Then we harvest articles for each faculty member, show the list to her/him and allow them to cross out anything they don&#8217;t want added.  John, have I got that right?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
