<?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: E-Reserve Issues</title>
	<atom:link href="http://www.librarywebchic.net/wordpress/2005/06/17/e-reserve-issues/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.librarywebchic.net/wordpress/2005/06/17/e-reserve-issues/</link>
	<description>Resources for librarians who are interested in the application of web design and technologies in libraries</description>
	<lastBuildDate>Tue, 09 Mar 2010 02:55:29 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: phil</title>
		<link>http://www.librarywebchic.net/wordpress/2005/06/17/e-reserve-issues/comment-page-1/#comment-392</link>
		<dc:creator>phil</dc:creator>
		<pubDate>Tue, 28 Jun 2005 14:09:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.librarywebchic.net/wordpress/2005/06/15/e-reserve-issues/#comment-392</guid>
		<description>Having worked for a publisher I can safely say that we were worried about coursepacks.  For our little enterprise, a university press publishing journals, royalties from classroom/textbook use were an important part of keeping the business going.  Given our setup it was often the difference between the red or the black that fiscal year.

The problem was that there wasn&#039;t really any way to police abuse.  Tracking down offenses was considered a waste of time.  And if you did pursue such an action, you came across as the evil publisher.

As to the general skiddishness nowadays... I think publishers are scared by the idea of Google print digitizing their whole backfile without any say in the matter.  

I&#039;m not a lawyer, or a librarian, but wouldn&#039;t the license (assuming there is one) the library signs dictate how the library can use these resources?   </description>
		<content:encoded><![CDATA[<p>Having worked for a publisher I can safely say that we were worried about coursepacks.  For our little enterprise, a university press publishing journals, royalties from classroom/textbook use were an important part of keeping the business going.  Given our setup it was often the difference between the red or the black that fiscal year.</p>
<p>The problem was that there wasn&#8217;t really any way to police abuse.  Tracking down offenses was considered a waste of time.  And if you did pursue such an action, you came across as the evil publisher.</p>
<p>As to the general skiddishness nowadays&#8230; I think publishers are scared by the idea of Google print digitizing their whole backfile without any say in the matter.  </p>
<p>I&#8217;m not a lawyer, or a librarian, but wouldn&#8217;t the license (assuming there is one) the library signs dictate how the library can use these resources?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Creative Librarian &#187; Next problem</title>
		<link>http://www.librarywebchic.net/wordpress/2005/06/17/e-reserve-issues/comment-page-1/#comment-388</link>
		<dc:creator>Creative Librarian &#187; Next problem</dc:creator>
		<pubDate>Mon, 20 Jun 2005 17:01:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.librarywebchic.net/wordpress/2005/06/15/e-reserve-issues/#comment-388</guid>
		<description>[...] laquo; TWAS 503: (Warnings and Promises) &#124;   Next problem  Monday, June 20, 2005  			Library Web Chic » Blog Archive » E-Reserve Issues 	Publishers want to be  [...]</description>
		<content:encoded><![CDATA[<p>[...] laquo; TWAS 503: (Warnings and Promises) | </p>
<p> Next problem</p>
<p> Monday, June 20, 2005</p>
<p> 			Library Web Chic » Blog Archive » E-Reserve Issues 	Publishers want to be  [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
