<?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"
	>
<channel>
	<title>Comments on: Cut-and-Paste NIH Public Access Policy Message to Senate Updated</title>
	<atom:link href="http://digital-scholarship.org/digitalkoans/2007/09/17/cut-and-paste-nih-public-access-policy-message-to-senate-updated/feed/" rel="self" type="application/rss+xml" />
	<link>http://digital-scholarship.org/digitalkoans/2007/09/17/cut-and-paste-nih-public-access-policy-message-to-senate-updated/</link>
	<description>What Is the Sound of One E-Print Downloading?</description>
	<pubDate>Fri, 29 Aug 2008 20:33:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Kara Malenfant</title>
		<link>http://digital-scholarship.org/digitalkoans/2007/09/17/cut-and-paste-nih-public-access-policy-message-to-senate-updated/#comment-43826</link>
		<dc:creator>Kara Malenfant</dc:creator>
		<pubDate>Wed, 19 Sep 2007 19:34:00 +0000</pubDate>
		<guid isPermaLink="false">http://digital-scholarship.org/digitalkoans/2007/09/17/cut-and-paste-nih-public-access-policy-message-to-senate-updated/#comment-43826</guid>
		<description>ALA and ACRL recommend that you personalize your messages to Congress. The ALA alert contains talking points, instead of a form letter, and we hope you will use them to construct your own message. There is a huge issue right now with Congressional offices disregarding stock emails and letters. (In fact, over half of Congressional staffers &lt;a href="”http://www.cmfweb.org/index.php?option=com_content&#38;task=view&#38;id=63&#38;item”" rel="nofollow"&gt;believe&lt;/a&gt; the form-emails they receive from constituents are sent without the constituents' knowledge.) We encourage you to show your legislators the real effect that this legislation will have on people in your community. Personal stories bring the message to life. For help, read &lt;a href="”" rel="nofollow"&gt;tips on telling an effective story&lt;/a&gt; from the ALA Washington Office.</description>
		<content:encoded><![CDATA[<p>ALA and ACRL recommend that you personalize your messages to Congress. The ALA alert contains talking points, instead of a form letter, and we hope you will use them to construct your own message. There is a huge issue right now with Congressional offices disregarding stock emails and letters. (In fact, over half of Congressional staffers <a href="”http://www.cmfweb.org/index.php?option=com_content&amp;task=view&amp;id=63&amp;item”" rel="nofollow">believe</a> the form-emails they receive from constituents are sent without the constituents&#8217; knowledge.) We encourage you to show your legislators the real effect that this legislation will have on people in your community. Personal stories bring the message to life. For help, read <a href="”" rel="nofollow">tips on telling an effective story</a> from the ALA Washington Office.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Unilever Centre for Molecular Informatics, Cambridge - petermr&#8217;s blog &#187; Blog Archive &#187; US citizens: act!</title>
		<link>http://digital-scholarship.org/digitalkoans/2007/09/17/cut-and-paste-nih-public-access-policy-message-to-senate-updated/#comment-43619</link>
		<dc:creator>Unilever Centre for Molecular Informatics, Cambridge - petermr&#8217;s blog &#187; Blog Archive &#187; US citizens: act!</dc:creator>
		<pubDate>Tue, 18 Sep 2007 10:26:18 +0000</pubDate>
		<guid isPermaLink="false">http://digital-scholarship.org/digitalkoans/2007/09/17/cut-and-paste-nih-public-access-policy-message-to-senate-updated/#comment-43619</guid>
		<description>[...] Bailey has solved this problem with a strong, ready-to-paste message based on public texts (in particular, this one and this one) [...]</description>
		<content:encoded><![CDATA[<p>[...] Bailey has solved this problem with a strong, ready-to-paste message based on public texts (in particular, this one and this one) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
