<?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: If I Could Build a Library Catalogue</title>
	<atom:link href="http://cecily.info/2009/10/12/if-i-could-build-a-library-catalogue/feed/" rel="self" type="application/rss+xml" />
	<link>http://cecily.info/2009/10/12/if-i-could-build-a-library-catalogue/</link>
	<description>they see me shushin&#039;, they hatin&#039;</description>
	<lastBuildDate>Mon, 30 Jan 2012 23:08:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: brett</title>
		<link>http://cecily.info/2009/10/12/if-i-could-build-a-library-catalogue/comment-page-1/#comment-349</link>
		<dc:creator>brett</dc:creator>
		<pubDate>Thu, 22 Oct 2009 01:55:24 +0000</pubDate>
		<guid isPermaLink="false">http://cecily.info/?p=2122#comment-349</guid>
		<description>A lot of this stuff is structurally impossible with the current crop of ILS without significant hacking, The best projects I&#039;ve seen (including Aquabrowser) require you to export your data to them in order to display it properly.

My ILS wishlist would include direct links to each item, a clear, non-authenticated (or simply authenticated) POST search support, an open, XML based API that does not require you to hack around with YAZ, RSS, the ability to easily integrate with social media (share on twitter, facebook, etc).

Then I could make an interface do all the things your asking about without having to have a degree in computer science.

You might want to check out the Drupal for Libraries project as well as the Scriblio project. Solr shows some promise as the basis for an OPAC., Solr projects like the Blacklight OPAC are still being activly developed and are easier to hack.</description>
		<content:encoded><![CDATA[<p>A lot of this stuff is structurally impossible with the current crop of ILS without significant hacking, The best projects I&#039;ve seen (including Aquabrowser) require you to export your data to them in order to display it properly.</p>
<p>My ILS wishlist would include direct links to each item, a clear, non-authenticated (or simply authenticated) POST search support, an open, XML based API that does not require you to hack around with YAZ, RSS, the ability to easily integrate with social media (share on twitter, facebook, etc).</p>
<p>Then I could make an interface do all the things your asking about without having to have a degree in computer science.</p>
<p>You might want to check out the Drupal for Libraries project as well as the Scriblio project. Solr shows some promise as the basis for an OPAC., Solr projects like the Blacklight OPAC are still being activly developed and are easier to hack.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: brett</title>
		<link>http://cecily.info/2009/10/12/if-i-could-build-a-library-catalogue/comment-page-1/#comment-1012</link>
		<dc:creator>brett</dc:creator>
		<pubDate>Thu, 22 Oct 2009 01:55:00 +0000</pubDate>
		<guid isPermaLink="false">http://cecily.info/?p=2122#comment-1012</guid>
		<description>A lot of this stuff is structurally impossible with the current crop of ILS without significant hacking, The best projects I&#039;ve seen (including Aquabrowser) require you to export your data to them in order to display it properly.

My ILS wishlist would include direct links to each item, a clear, non-authenticated (or simply authenticated) POST search support, an open, XML based API that does not require you to hack around with YAZ, RSS, the ability to easily integrate with social media (share on twitter, facebook, etc).

Then I could make an interface do all the things your asking about without having to have a degree in computer science.

You might want to check out the Drupal for Libraries project as well as the Scriblio project. Solr shows some promise as the basis for an OPAC., Solr projects like the Blacklight OPAC are still being activly developed and are easier to hack.</description>
		<content:encoded><![CDATA[<p>A lot of this stuff is structurally impossible with the current crop of ILS without significant hacking, The best projects I&#039;ve seen (including Aquabrowser) require you to export your data to them in order to display it properly.</p>
<p>My ILS wishlist would include direct links to each item, a clear, non-authenticated (or simply authenticated) POST search support, an open, XML based API that does not require you to hack around with YAZ, RSS, the ability to easily integrate with social media (share on twitter, facebook, etc).</p>
<p>Then I could make an interface do all the things your asking about without having to have a degree in computer science.</p>
<p>You might want to check out the Drupal for Libraries project as well as the Scriblio project. Solr shows some promise as the basis for an OPAC., Solr projects like the Blacklight OPAC are still being activly developed and are easier to hack.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cecily</title>
		<link>http://cecily.info/2009/10/12/if-i-could-build-a-library-catalogue/comment-page-1/#comment-350</link>
		<dc:creator>cecily</dc:creator>
		<pubDate>Tue, 13 Oct 2009 18:35:14 +0000</pubDate>
		<guid isPermaLink="false">http://cecily.info/?p=2122#comment-350</guid>
		<description>Yep, I&#039;ve seen it, though I&#039;ve never worked with it personally. I like the idea - but the conventional wisdom I&#039;ve been hearing is that systems like Koha and Evergreen aren&#039;t well suited for library systems as large as mine. I don&#039;t know how true that is because I haven&#039;t done the legwork, but in just looking at the list of libraries who are using Koha, I don&#039;t see anyone that&#039;s a comparable size.

Still, it&#039;s good to see competitors adopting these kinds of features for catalogues. I think the major vendors are definitely taking notice.</description>
		<content:encoded><![CDATA[<p>Yep, I&#039;ve seen it, though I&#039;ve never worked with it personally. I like the idea &#8211; but the conventional wisdom I&#039;ve been hearing is that systems like Koha and Evergreen aren&#039;t well suited for library systems as large as mine. I don&#039;t know how true that is because I haven&#039;t done the legwork, but in just looking at the list of libraries who are using Koha, I don&#039;t see anyone that&#039;s a comparable size.</p>
<p>Still, it&#039;s good to see competitors adopting these kinds of features for catalogues. I think the major vendors are definitely taking notice.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cecily Walker</title>
		<link>http://cecily.info/2009/10/12/if-i-could-build-a-library-catalogue/comment-page-1/#comment-1013</link>
		<dc:creator>Cecily Walker</dc:creator>
		<pubDate>Tue, 13 Oct 2009 18:35:00 +0000</pubDate>
		<guid isPermaLink="false">http://cecily.info/?p=2122#comment-1013</guid>
		<description>Yep, I&#039;ve seen it, though I&#039;ve never worked with it personally. I like the idea - but the conventional wisdom I&#039;ve been hearing is that systems like Koha and Evergreen aren&#039;t well suited for library systems as large as mine. I don&#039;t know how true that is because I haven&#039;t done the legwork, but in just looking at the list of libraries who are using Koha, I don&#039;t see anyone that&#039;s a comparable size.

Still, it&#039;s good to see competitors adopting these kinds of features for catalogues. I think the major vendors are definitely taking notice.</description>
		<content:encoded><![CDATA[<p>Yep, I&#039;ve seen it, though I&#039;ve never worked with it personally. I like the idea &#8211; but the conventional wisdom I&#039;ve been hearing is that systems like Koha and Evergreen aren&#039;t well suited for library systems as large as mine. I don&#039;t know how true that is because I haven&#039;t done the legwork, but in just looking at the list of libraries who are using Koha, I don&#039;t see anyone that&#039;s a comparable size.</p>
<p>Still, it&#039;s good to see competitors adopting these kinds of features for catalogues. I think the major vendors are definitely taking notice.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: @sheatsb</title>
		<link>http://cecily.info/2009/10/12/if-i-could-build-a-library-catalogue/comment-page-1/#comment-351</link>
		<dc:creator>@sheatsb</dc:creator>
		<pubDate>Tue, 13 Oct 2009 07:25:45 +0000</pubDate>
		<guid isPermaLink="false">http://cecily.info/?p=2122#comment-351</guid>
		<description>I know you&#039;ve probably seen this already, but what about Koha (&lt;a href=&quot;http://koha.org/)?&quot; target=&quot;_blank&quot;&gt;http://koha.org/)?&lt;/a&gt; It&#039;s pretty user-friendly from the end-user and admin perspective.</description>
		<content:encoded><![CDATA[<p>I know you&#039;ve probably seen this already, but what about Koha (<a href="http://koha.org/)?" target="_blank"></a><a href="http://koha.org/" rel="nofollow">http://koha.org/</a>)? It&#039;s pretty user-friendly from the end-user and admin perspective.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: @sheatsb</title>
		<link>http://cecily.info/2009/10/12/if-i-could-build-a-library-catalogue/comment-page-1/#comment-1014</link>
		<dc:creator>@sheatsb</dc:creator>
		<pubDate>Tue, 13 Oct 2009 07:25:00 +0000</pubDate>
		<guid isPermaLink="false">http://cecily.info/?p=2122#comment-1014</guid>
		<description>I know you&#039;ve probably seen this already, but what about Koha (&lt;a href=&quot;http://koha.org/)?&quot; rel=&quot;nofollow&quot;&gt;http://koha.org/)?&lt;/a&gt; It&#039;s pretty user-friendly from the end-user and admin perspective.</description>
		<content:encoded><![CDATA[<p>I know you&#039;ve probably seen this already, but what about Koha (<a href="http://koha.org/)?" rel="nofollow"></a><a href="http://koha.org/" rel="nofollow">http://koha.org/</a>)? It&#039;s pretty user-friendly from the end-user and admin perspective.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

