<?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 for Copac Developments</title>
	<atom:link href="http://copac.ac.uk/development-blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://copac.ac.uk/development-blog</link>
	<description>What's happening behind the scenes at Copac</description>
	<lastBuildDate>Thu, 18 Feb 2010 11:17:52 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Getting to know the Copac libraries 2 &#8211; York Minster, antiquarian material, and local notes by Copac Developments</title>
		<link>http://copac.ac.uk/development-blog/2009/02/getting-to-know-the-copac-libraries-2-york-minster-antiquarian-material-and-local-notes/comment-page-1/#comment-1745</link>
		<dc:creator>Copac Developments</dc:creator>
		<pubDate>Thu, 18 Feb 2010 11:17:52 +0000</pubDate>
		<guid isPermaLink="false">http://copac.ac.uk/development-blog/?p=165#comment-1745</guid>
		<description>[...] reengineering. We will also be exploring FRBR work level deduplication. As I’ve mentioned in an earlier blog post , we don’t de-duplicate anything published pre-1801. So what do we do for the post-1801 [...]</description>
		<content:encoded><![CDATA[<p>[...] reengineering. We will also be exploring FRBR work level deduplication. As I’ve mentioned in an earlier blog post , we don’t de-duplicate anything published pre-1801. So what do we do for the post-1801 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Behind the Copac record by HotStuff 2.0 &#187; Blog Archive &#187; Word of the Day: &#8220;typos&#8221;</title>
		<link>http://copac.ac.uk/development-blog/2010/01/behind-the-copac-record/comment-page-1/#comment-1401</link>
		<dc:creator>HotStuff 2.0 &#187; Blog Archive &#187; Word of the Day: &#8220;typos&#8221;</dc:creator>
		<pubDate>Fri, 29 Jan 2010 05:06:00 +0000</pubDate>
		<guid isPermaLink="false">http://copac.ac.uk/development-blog/?p=304#comment-1401</guid>
		<description>[...] the Copac record [web link]Copac Developments (26/Jan/2010)&#8220;&#8230;wouldn&#8217;t for example correct typos in [...]</description>
		<content:encoded><![CDATA[<p>[...] the Copac record [web link]Copac Developments (26/Jan/2010)&#8220;&#8230;wouldn&#8217;t for example correct typos in [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Behind the Copac record by Twitter Trackbacks for Behind the Copac record at Copac Developments [copac.ac.uk] on Topsy.com</title>
		<link>http://copac.ac.uk/development-blog/2010/01/behind-the-copac-record/comment-page-1/#comment-1385</link>
		<dc:creator>Twitter Trackbacks for Behind the Copac record at Copac Developments [copac.ac.uk] on Topsy.com</dc:creator>
		<pubDate>Tue, 26 Jan 2010 22:08:02 +0000</pubDate>
		<guid isPermaLink="false">http://copac.ac.uk/development-blog/?p=304#comment-1385</guid>
		<description>[...] Behind the Copac record at Copac Developments  copac.ac.uk/development-blog/2010/01/behind-the-copac-record &#8211; view page &#8211; cached  What’s happening behind the scenes at Copac [...]</description>
		<content:encoded><![CDATA[<p>[...] Behind the Copac record at Copac Developments  copac.ac.uk/development-blog/2010/01/behind-the-copac-record &ndash; view page &ndash; cached  What’s happening behind the scenes at Copac [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Yesterday&#8217;s loss of service by Database update at Copac Developments</title>
		<link>http://copac.ac.uk/development-blog/2009/10/yesterdays-loss-of-service/comment-page-1/#comment-1045</link>
		<dc:creator>Database update at Copac Developments</dc:creator>
		<pubDate>Fri, 13 Nov 2009 09:29:24 +0000</pubDate>
		<guid isPermaLink="false">http://copac.ac.uk/development-blog/?p=298#comment-1045</guid>
		<description>[...] had a recurrence of the problem I reported a month ago and so last night we installed an update to the database software we use. I&#8217;m told the update [...]</description>
		<content:encoded><![CDATA[<p>[...] had a recurrence of the problem I reported a month ago and so last night we installed an update to the database software we use. I&#8217;m told the update [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Copac Beta can search your library too by Copac and museum libraries &#171; London Museum Libraries and Archives</title>
		<link>http://copac.ac.uk/development-blog/2009/07/copac-beta-can-search-your-library-too/comment-page-1/#comment-868</link>
		<dc:creator>Copac and museum libraries &#171; London Museum Libraries and Archives</dc:creator>
		<pubDate>Tue, 29 Sep 2009 09:01:37 +0000</pubDate>
		<guid isPermaLink="false">http://copac.ac.uk/development-blog/?p=272#comment-868</guid>
		<description>[...] supported libraries to search both their local catalogue and Copac simultaneously. See Copac’s development blog for more [...]</description>
		<content:encoded><![CDATA[<p>[...] supported libraries to search both their local catalogue and Copac simultaneously. See Copac’s development blog for more [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on New Copac interface by Ashley</title>
		<link>http://copac.ac.uk/development-blog/2009/08/new-copac-interface/comment-page-1/#comment-807</link>
		<dc:creator>Ashley</dc:creator>
		<pubDate>Tue, 11 Aug 2009 08:53:10 +0000</pubDate>
		<guid isPermaLink="false">http://copac.ac.uk/development-blog/?p=278#comment-807</guid>
		<description>Owen, whichever authentication mechanism we support, we have to support the UK Federation (or Shibboleth if you prefer) as it is the JISC preferred authentication mechanism. The UK Federation is available to most, if not all, the UK academic research community and many other publicly funded organisations. And if you aren&#039;t a member of such an organisation, then anyone can sign up with ProtectNetwork or TypeKey and get a login that way. ProtectNetwork gives you an OpenID as well.

I think that supporting multiple different authentication mechanisms is going to be confusing for users (never mind those that have to support the services), so we&#039;d really like to support just the one authentication mechanism. The ID providers I mention above does make the UK Federation (and hence a Copac login) available to all.</description>
		<content:encoded><![CDATA[<p>Owen, whichever authentication mechanism we support, we have to support the UK Federation (or Shibboleth if you prefer) as it is the JISC preferred authentication mechanism. The UK Federation is available to most, if not all, the UK academic research community and many other publicly funded organisations. And if you aren&#8217;t a member of such an organisation, then anyone can sign up with ProtectNetwork or TypeKey and get a login that way. ProtectNetwork gives you an OpenID as well.</p>
<p>I think that supporting multiple different authentication mechanisms is going to be confusing for users (never mind those that have to support the services), so we&#8217;d really like to support just the one authentication mechanism. The ID providers I mention above does make the UK Federation (and hence a Copac login) available to all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on New Copac interface by Owen Stephens</title>
		<link>http://copac.ac.uk/development-blog/2009/08/new-copac-interface/comment-page-1/#comment-804</link>
		<dc:creator>Owen Stephens</dc:creator>
		<pubDate>Mon, 10 Aug 2009 15:56:44 +0000</pubDate>
		<guid isPermaLink="false">http://copac.ac.uk/development-blog/?p=278#comment-804</guid>
		<description>I guess the obvious question about logins is why not support OpenID for login?</description>
		<content:encoded><![CDATA[<p>I guess the obvious question about logins is why not support OpenID for login?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on New features of the Copac Beta Interface by New Copac interface at Copac Developments</title>
		<link>http://copac.ac.uk/development-blog/2009/03/new-features-of-the-copac-beta-interface/comment-page-1/#comment-802</link>
		<dc:creator>New Copac interface at Copac Developments</dc:creator>
		<pubDate>Mon, 10 Aug 2009 15:07:51 +0000</pubDate>
		<guid isPermaLink="false">http://copac.ac.uk/development-blog/?p=217#comment-802</guid>
		<description>[...]  [...]</description>
		<content:encoded><![CDATA[<p>[...]  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Atom and Shibboleth by William Waites</title>
		<link>http://copac.ac.uk/development-blog/2009/03/atom-and-shibboleth/comment-page-1/#comment-769</link>
		<dc:creator>William Waites</dc:creator>
		<pubDate>Fri, 24 Jul 2009 10:18:36 +0000</pubDate>
		<guid isPermaLink="false">http://copac.ac.uk/development-blog/?p=197#comment-769</guid>
		<description>JavaScript is not good for this sort of thing. This means making any of the data machine-useable is very hard which means building services or programs that use the information is hard - and it shouldn&#039;t be.

Also keep in mind that many web browsers, particularly those in mobile phones might not work properly with JavaScript cruft. Imagine you&#039;re somewhere deep in the stacks and you want to look something up - why not do it right then and there instead of going to find a computer?

Cookies are better but still unwieldy. I agree with Owen that if at all possible tokens in nice stable (RESTful) URLs are the best.</description>
		<content:encoded><![CDATA[<p>JavaScript is not good for this sort of thing. This means making any of the data machine-useable is very hard which means building services or programs that use the information is hard &#8211; and it shouldn&#8217;t be.</p>
<p>Also keep in mind that many web browsers, particularly those in mobile phones might not work properly with JavaScript cruft. Imagine you&#8217;re somewhere deep in the stacks and you want to look something up &#8211; why not do it right then and there instead of going to find a computer?</p>
<p>Cookies are better but still unwieldy. I agree with Owen that if at all possible tokens in nice stable (RESTful) URLs are the best.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Joy Palmer by Sarah O'Donnell</title>
		<link>http://copac.ac.uk/development-blog/joy-palmer/comment-page-1/#comment-735</link>
		<dc:creator>Sarah O'Donnell</dc:creator>
		<pubDate>Wed, 01 Jul 2009 17:54:41 +0000</pubDate>
		<guid isPermaLink="false">http://copac.ac.uk/development-blog/?page_id=36#comment-735</guid>
		<description>Thanks for putting me straight about twwets and twittering! 
Godd to talk to you and gain and insight into MIMAS</description>
		<content:encoded><![CDATA[<p>Thanks for putting me straight about twwets and twittering!<br />
Godd to talk to you and gain and insight into MIMAS</p>
]]></content:encoded>
	</item>
</channel>
</rss>
