<?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: The DSpace Digital Repository: A Project Analysis</title>
	<atom:link href="http://subjectobject.net/2006/11/09/the-dspace-digital-repository-a-project-analysis/feed/" rel="self" type="application/rss+xml" />
	<link>http://subjectobject.net/2006/11/09/the-dspace-digital-repository-a-project-analysis/</link>
	<description>Home of Steven Chabot and his writings on knowledge, books, computers, and libraries.</description>
	<pubDate>Sun, 23 Nov 2008 13:31:29 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7-beta2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dirk Swart</title>
		<link>http://subjectobject.net/2006/11/09/the-dspace-digital-repository-a-project-analysis/comment-page-1/#comment-82363</link>
		<dc:creator>Dirk Swart</dc:creator>
		<pubDate>Thu, 03 Apr 2008 13:25:22 +0000</pubDate>
		<guid isPermaLink="false">http://subjectobject.net/2006/11/09/the-dspace-digital-repository-a-project-analysis/#comment-82363</guid>
		<description>&lt;p&gt;This is a great article. Any chance you could do the same thing for Fedora?&lt;/p&gt;

&lt;p&gt;Jenny, I completely agree with you about open source, but want to add that in my experience implementing FOSS at universities is typically more expensive than an off the shelf solution, and that a significant portion of the costs are hidden, so much so that it may look cheaper.&lt;/p&gt;

&lt;p&gt;This increased cost is not necessarily bad - it spends money "at home", usually on people, and given low staff turnover there is at least a strong case that this is a sound investment.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>This is a great article. Any chance you could do the same thing for Fedora?</p>

<p>Jenny, I completely agree with you about open source, but want to add that in my experience implementing FOSS at universities is typically more expensive than an off the shelf solution, and that a significant portion of the costs are hidden, so much so that it may look cheaper.</p>

<p>This increased cost is not necessarily bad - it spends money &#8220;at home&#8221;, usually on people, and given low staff turnover there is at least a strong case that this is a sound investment.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Chabot</title>
		<link>http://subjectobject.net/2006/11/09/the-dspace-digital-repository-a-project-analysis/comment-page-1/#comment-53376</link>
		<dc:creator>Steven Chabot</dc:creator>
		<pubDate>Tue, 09 Oct 2007 04:07:34 +0000</pubDate>
		<guid isPermaLink="false">http://subjectobject.net/2006/11/09/the-dspace-digital-repository-a-project-analysis/#comment-53376</guid>
		<description>&lt;p&gt;Jenny,&lt;/p&gt;

&lt;p&gt;All things with which I agree, and which I also addressed in my analysis.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Jenny,</p>

<p>All things with which I agree, and which I also addressed in my analysis.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Jenny</title>
		<link>http://subjectobject.net/2006/11/09/the-dspace-digital-repository-a-project-analysis/comment-page-1/#comment-53375</link>
		<dc:creator>Jenny</dc:creator>
		<pubDate>Tue, 09 Oct 2007 04:04:32 +0000</pubDate>
		<guid isPermaLink="false">http://subjectobject.net/2006/11/09/the-dspace-digital-repository-a-project-analysis/#comment-53375</guid>
		<description>&lt;p&gt;I'm surprised that the fact that DSpace is open source is considered a 'problem'. It is just open source. Open source has considerable advantages over proprietary software where the code is unavailable - you can actually do things with it. This is a benefit and not a problem. Anyone who works with open source, including libraries, understands that open source is not free - that you need to have the tech support in place or available to support the implementation. But products like DSpace (and others like Moodle, Sakai, Shibboleth etc) have been built by a group or community who have a professional approach to the development process. It's not a world of cowboys out there any more -but communities of contributors. 
The establishment of the DSpace foundation also means that DSpace will be properly supported into the future.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I&#8217;m surprised that the fact that DSpace is open source is considered a &#8216;problem&#8217;. It is just open source. Open source has considerable advantages over proprietary software where the code is unavailable - you can actually do things with it. This is a benefit and not a problem. Anyone who works with open source, including libraries, understands that open source is not free - that you need to have the tech support in place or available to support the implementation. But products like DSpace (and others like Moodle, Sakai, Shibboleth etc) have been built by a group or community who have a professional approach to the development process. It&#8217;s not a world of cowboys out there any more -but communities of contributors. 
The establishment of the DSpace foundation also means that DSpace will be properly supported into the future.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Unilever Centre for Molecular Informatics, Cambridge - Jim Downing &#187; Blog Archive &#187;</title>
		<link>http://subjectobject.net/2006/11/09/the-dspace-digital-repository-a-project-analysis/comment-page-1/#comment-564</link>
		<dc:creator>Unilever Centre for Molecular Informatics, Cambridge - Jim Downing &#187; Blog Archive &#187;</dc:creator>
		<pubDate>Tue, 14 Nov 2006 14:22:47 +0000</pubDate>
		<guid isPermaLink="false">http://subjectobject.net/2006/11/09/the-dspace-digital-repository-a-project-analysis/#comment-564</guid>
		<description>&lt;p&gt;[...] Steven Chabot has posted an analysis of the DSpace project and software (Full report in PDF).  As has been addressed, there are some problems with DSpace. In the first place, the software is open source. While this does come with its own benefits, it also comes with its own problems. Commercial support for the software does not exist at this time, neither for installation nor for later technical issues. Libraries used to working with commercial software or ILS vendors may find implementation difficult. Furthermore, some who have previously implemented the software have had problems with performance while updating files and with the structure of the communities, although these may have been fixed in successive releases of the software. The major difficulty we have found is with DSpace’s handling of metadata. While we feel that the number of fields in Dublin Core is adequate for most if not all uses (DCMI Usage Board 2006), we are troubled by the lack of authority control when completing its fields. Without some control over uniform titles, authors and subjects accessing the items in the future will very problematic. However, this could be solved at an institutional policy level, with guidelines for submission and librarians or faculty having roles in the “workflow” overseeing metadata. While there is no scope in this paper for a discussion of necessity of controlled vocabulary, we will stress that this necessity does not just apply to paper documents, but to digital ones as well. [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] Steven Chabot has posted an analysis of the DSpace project and software (Full report in PDF).  As has been addressed, there are some problems with DSpace. In the first place, the software is open source. While this does come with its own benefits, it also comes with its own problems. Commercial support for the software does not exist at this time, neither for installation nor for later technical issues. Libraries used to working with commercial software or ILS vendors may find implementation difficult. Furthermore, some who have previously implemented the software have had problems with performance while updating files and with the structure of the communities, although these may have been fixed in successive releases of the software. The major difficulty we have found is with DSpace’s handling of metadata. While we feel that the number of fields in Dublin Core is adequate for most if not all uses (DCMI Usage Board 2006), we are troubled by the lack of authority control when completing its fields. Without some control over uniform titles, authors and subjects accessing the items in the future will very problematic. However, this could be solved at an institutional policy level, with guidelines for submission and librarians or faculty having roles in the “workflow” overseeing metadata. While there is no scope in this paper for a discussion of necessity of controlled vocabulary, we will stress that this necessity does not just apply to paper documents, but to digital ones as well. [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Chabot</title>
		<link>http://subjectobject.net/2006/11/09/the-dspace-digital-repository-a-project-analysis/comment-page-1/#comment-480</link>
		<dc:creator>Steven Chabot</dc:creator>
		<pubDate>Sat, 11 Nov 2006 01:07:05 +0000</pubDate>
		<guid isPermaLink="false">http://subjectobject.net/2006/11/09/the-dspace-digital-repository-a-project-analysis/#comment-480</guid>
		<description>&lt;p&gt;Thank you for your comments.&lt;/p&gt;

&lt;p&gt;And I agree with you on the authority control issue.  I realize that things like that are difficult, but I had to say &lt;i&gt;something&lt;/i&gt; negative about the project.  And as I indicated, authority control could be implemented by a librarian.&lt;/p&gt;

&lt;p&gt;However my conclusions are genuine.  I am particularly excited by the project and I would love to get involved with DSpace installation at my own university, but it doesn't seem to be as publicized as it could be.  I never new U of T had is own repository all through my undergrad here, and looking at it now things are kind of a mess.&lt;/p&gt;

&lt;p&gt;Too bad that the student positions they advertise seem to be for undergraduates and not graduate library students.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Thank you for your comments.</p>

<p>And I agree with you on the authority control issue.  I realize that things like that are difficult, but I had to say <i>something</i> negative about the project.  And as I indicated, authority control could be implemented by a librarian.</p>

<p>However my conclusions are genuine.  I am particularly excited by the project and I would love to get involved with DSpace installation at my own university, but it doesn&#8217;t seem to be as publicized as it could be.  I never new U of T had is own repository all through my undergrad here, and looking at it now things are kind of a mess.</p>

<p>Too bad that the student positions they advertise seem to be for undergraduates and not graduate library students.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Dorothea</title>
		<link>http://subjectobject.net/2006/11/09/the-dspace-digital-repository-a-project-analysis/comment-page-1/#comment-477</link>
		<dc:creator>Dorothea</dc:creator>
		<pubDate>Fri, 10 Nov 2006 17:26:13 +0000</pubDate>
		<guid isPermaLink="false">http://subjectobject.net/2006/11/09/the-dspace-digital-repository-a-project-analysis/#comment-477</guid>
		<description>&lt;p&gt;Thank you; this is an excellent summary.&lt;/p&gt;

&lt;p&gt;Re: authority control. While DSpace could conceivably provide a scaffold for authority control, even tying it into national or international authority files wouldn't solve the problem in fields where the monograph is not the primary mode of publication. Too many scientists don't have authority records!&lt;/p&gt;

&lt;p&gt;For what it's worth, I check authority via the LoC, intervene in the database as necessary to unite author representations, and don't fret about representations for authors with no authority records.&lt;/p&gt;

&lt;p&gt;A union authority database would be a wonderful thing...&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Thank you; this is an excellent summary.</p>

<p>Re: authority control. While DSpace could conceivably provide a scaffold for authority control, even tying it into national or international authority files wouldn&#8217;t solve the problem in fields where the monograph is not the primary mode of publication. Too many scientists don&#8217;t have authority records!</p>

<p>For what it&#8217;s worth, I check authority via the LoC, intervene in the database as necessary to unite author representations, and don&#8217;t fret about representations for authors with no authority records.</p>

<p>A union authority database would be a wonderful thing&#8230;</p>]]></content:encoded>
	</item>
</channel>
</rss>
