<?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: IL2006 Day 2: Institutional Repository Basics: From Soup to Nuts</title>
	<atom:link href="http://meredith.wolfwater.com/wordpress/2006/10/25/il2006-day-2-institutional-repository-basics-from-soup-to-nuts/feed/" rel="self" type="application/rss+xml" />
	<link>http://meredith.wolfwater.com/wordpress/2006/10/25/il2006-day-2-institutional-repository-basics-from-soup-to-nuts/</link>
	<description>A librarian, writer and tech geek reflecting on the profession and the tools we use to serve our patrons</description>
	<lastBuildDate>Tue, 09 Mar 2010 13:59:34 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Roy Tennant</title>
		<link>http://meredith.wolfwater.com/wordpress/2006/10/25/il2006-day-2-institutional-repository-basics-from-soup-to-nuts/comment-page-1/#comment-113027</link>
		<dc:creator>Roy Tennant</dc:creator>
		<pubDate>Fri, 27 Oct 2006 01:29:53 +0000</pubDate>
		<guid isPermaLink="false">http://meredith.wolfwater.com/wordpress/index.php/2006/10/25/il2006-day-2-institutional-repository-basics-from-soup-to-nuts/#comment-113027</guid>
		<description>Thanks for the great write-up Meredith! It&#039;s nice to have such great note-takers in the audience.

What Dorothea fails to mention in her comment is that I asked to learn about her experience with DSpace at GMU, and she very helpfully replied with a long email that provided me with some of her insights and experience. I of course also recalled many of her blog postings about her institutional repository experiences as well. So....I can take some credit, but certainly not all. The great thing is that there are a lot of people out there now with experience doing this kind of thing, so anyone thinking about doing it shouldn&#039;t be shy about contacting those of us who have some experience.</description>
		<content:encoded><![CDATA[<p>Thanks for the great write-up Meredith! It&#8217;s nice to have such great note-takers in the audience.</p>
<p>What Dorothea fails to mention in her comment is that I asked to learn about her experience with DSpace at GMU, and she very helpfully replied with a long email that provided me with some of her insights and experience. I of course also recalled many of her blog postings about her institutional repository experiences as well. So&#8230;.I can take some credit, but certainly not all. The great thing is that there are a lot of people out there now with experience doing this kind of thing, so anyone thinking about doing it shouldn&#8217;t be shy about contacting those of us who have some experience.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dorothea</title>
		<link>http://meredith.wolfwater.com/wordpress/2006/10/25/il2006-day-2-institutional-repository-basics-from-soup-to-nuts/comment-page-1/#comment-112813</link>
		<dc:creator>Dorothea</dc:creator>
		<pubDate>Thu, 26 Oct 2006 12:00:32 +0000</pubDate>
		<guid isPermaLink="false">http://meredith.wolfwater.com/wordpress/index.php/2006/10/25/il2006-day-2-institutional-repository-basics-from-soup-to-nuts/#comment-112813</guid>
		<description>Mr. Tennant, he is Teh Smart.

My recommendations only diverge from his once: a service model is okay for a large institution *at first* -- but you have to manage expectations for the long term, and even if you&#039;re *not* planning a service model, you should understand that there WILL be services involved, as when a small campus research institute dumps several gigabytes of papers on your desk and says &quot;Archive these!&quot;</description>
		<content:encoded><![CDATA[<p>Mr. Tennant, he is Teh Smart.</p>
<p>My recommendations only diverge from his once: a service model is okay for a large institution *at first* &#8212; but you have to manage expectations for the long term, and even if you&#8217;re *not* planning a service model, you should understand that there WILL be services involved, as when a small campus research institute dumps several gigabytes of papers on your desk and says &#8220;Archive these!&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
