<?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: Open Repositories Conference 09 Part 2</title>
	<atom:link href="http://cairss.caul.edu.au/blog/2009/06/10/open-repositories-conference-09-part-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://cairss.caul.edu.au/blog/2009/06/10/open-repositories-conference-09-part-2/</link>
	<description>The primary function of CAIRSS is to offer support for Repository Managers in the higher education sector in Australia.</description>
	<lastBuildDate>Tue, 08 Feb 2011 04:17:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: Borrowind</title>
		<link>http://cairss.caul.edu.au/blog/2009/06/10/open-repositories-conference-09-part-2/comment-page-1/#comment-11</link>
		<dc:creator>Borrowind</dc:creator>
		<pubDate>Tue, 16 Jun 2009 10:07:44 +0000</pubDate>
		<guid isPermaLink="false">http://caulcairss.wordpress.com/2009/06/10/open-repositories-conference-09-part-2/#comment-11</guid>
		<description>&gt;“developer challenge” ... creating an application, well more of a web service really that would harvest a repositories metadata and then display it in a web browser

Simply embed some of the basic metadata in the URL thus...

www.myuni.edu/repository/public/full-text/history/history-of-technology/thesis/2009-adams-peter-on-watermills.pdf

...and if there&#039;s a strict standard set among universities for how to structure and name repository directories, then IT techies can&#039;t break the URL by juggling the directories.</description>
		<content:encoded><![CDATA[<p>&gt;“developer challenge” &#8230; creating an application, well more of a web service really that would harvest a repositories metadata and then display it in a web browser</p>
<p>Simply embed some of the basic metadata in the URL thus&#8230;</p>
<p><a href="http://www.myuni.edu/repository/public/full-text/history/history-of-technology/thesis/2009-adams-peter-on-watermills.pdf" rel="nofollow">http://www.myuni.edu/repository/public/full-text/history/history-of-technology/thesis/2009-adams-peter-on-watermills.pdf</a></p>
<p>&#8230;and if there&#8217;s a strict standard set among universities for how to structure and name repository directories, then IT techies can&#8217;t break the URL by juggling the directories.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Sefton</title>
		<link>http://cairss.caul.edu.au/blog/2009/06/10/open-repositories-conference-09-part-2/comment-page-1/#comment-10</link>
		<dc:creator>Peter Sefton</dc:creator>
		<pubDate>Wed, 10 Jun 2009 05:14:50 +0000</pubDate>
		<guid isPermaLink="false">http://caulcairss.wordpress.com/2009/06/10/open-repositories-conference-09-part-2/#comment-10</guid>
		<description>One of the problems with normalization is that things need to be normalized for participation in a federation but locally institutions want to see their own terminology. So while a service like the one you propose might be useful I think we need to supply an easy way for people to adapt their OAI-PMH feeds, which is a possible new project as an outcome of the repository census - if we get the go ahead from the CAIRSS steering committee to work on it.</description>
		<content:encoded><![CDATA[<p>One of the problems with normalization is that things need to be normalized for participation in a federation but locally institutions want to see their own terminology. So while a service like the one you propose might be useful I think we need to supply an easy way for people to adapt their OAI-PMH feeds, which is a possible new project as an outcome of the repository census &#8211; if we get the go ahead from the CAIRSS steering committee to work on it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

