<?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: Wood and Hoffmann, Library Collection Development Policies</title>
	<atom:link href="http://www.pzed.ca/words/2006/12/14/wood-and-hoffmann-library-collection-development-policies/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pzed.ca/words/2006/12/14/wood-and-hoffmann-library-collection-development-policies/</link>
	<description>what do you read, m'lord?</description>
	<lastBuildDate>Thu, 26 Nov 2009 02:31:29 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: words &#187; Blog Archive &#187; Wood and Hoffmann II</title>
		<link>http://www.pzed.ca/words/2006/12/14/wood-and-hoffmann-library-collection-development-policies/comment-page-1/#comment-556</link>
		<dc:creator>words &#187; Blog Archive &#187; Wood and Hoffmann II</dc:creator>
		<pubDate>Tue, 19 Dec 2006 20:11:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.pzed.ca/words/archives/2006/wood-and-hoffmann-library-collection-development-policies/#comment-556</guid>
		<description>[...] In my first post on Wood and Hoffmann, I identified four general categories of arguments in favour of libraries having collection development policies: planning, accountability, staff, and information. Partially, what I&#8217;m thinking about now is not so much a reduction of those categories to two, but a recognition that specific aspects of a policy may be either internally or externally oriented. Indeed, a policy could be entirely oriented in one or the other direction. My gut feeling is that collection development policies often try to do too much. Does a library benefit from having a comprehensive policy, or is it better to sketch a general framework that outlines the library&#8217;s general philosophy? [...]</description>
		<content:encoded><![CDATA[<p>[...] In my first post on Wood and Hoffmann, I identified four general categories of arguments in favour of libraries having collection development policies: planning, accountability, staff, and information. Partially, what I&#8217;m thinking about now is not so much a reduction of those categories to two, but a recognition that specific aspects of a policy may be either internally or externally oriented. Indeed, a policy could be entirely oriented in one or the other direction. My gut feeling is that collection development policies often try to do too much. Does a library benefit from having a comprehensive policy, or is it better to sketch a general framework that outlines the library&#8217;s general philosophy? [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
