<?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: ILS Customer Bill-of-Rights</title>
	<atom:link href="http://www.blyberg.net/2005/11/20/ils-customer-bill-of-rights/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.blyberg.net/2005/11/20/ils-customer-bill-of-rights/</link>
	<description>A library-geek blog</description>
	<lastBuildDate>Tue, 16 Mar 2010 15:34:50 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Empathy, But Not Sympathy for Innovative</title>
		<link>http://www.blyberg.net/2005/11/20/ils-customer-bill-of-rights/comment-page-2/#comment-562706</link>
		<dc:creator>Empathy, But Not Sympathy for Innovative</dc:creator>
		<pubDate>Tue, 11 Aug 2009 03:33:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.blyberg.net/?p=38#comment-562706</guid>
		<description>[...] John Blyberg of blyberg.net has responded to this and similar complaints by penning an ILS Customer Bill of Rights. [...]</description>
		<content:encoded><![CDATA[<p>[...] John Blyberg of blyberg.net has responded to this and similar complaints by penning an ILS Customer Bill of Rights. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ding #21: web20 catalogi &#171; Harold&#8217;s 23 dingen</title>
		<link>http://www.blyberg.net/2005/11/20/ils-customer-bill-of-rights/comment-page-2/#comment-562577</link>
		<dc:creator>Ding #21: web20 catalogi &#171; Harold&#8217;s 23 dingen</dc:creator>
		<pubDate>Wed, 15 Jul 2009 08:30:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.blyberg.net/?p=38#comment-562577</guid>
		<description>[...] 2005 schreef de ontwikkelaar in dienst bij de Ann Arbor bibliotheek een bill of rights, 4 basale grondbeginselen waaraan onze bibliotheeksystemen zouden moeten voldoen. Het word tijd dat [...]</description>
		<content:encoded><![CDATA[<p>[...] 2005 schreef de ontwikkelaar in dienst bij de Ann Arbor bibliotheek een bill of rights, 4 basale grondbeginselen waaraan onze bibliotheeksystemen zouden moeten voldoen. Het word tijd dat [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Library 2.0, How we begin ? &#171; :: Go To Library 2.0 ::</title>
		<link>http://www.blyberg.net/2005/11/20/ils-customer-bill-of-rights/comment-page-1/#comment-551991</link>
		<dc:creator>Library 2.0, How we begin ? &#171; :: Go To Library 2.0 ::</dc:creator>
		<pubDate>Fri, 13 Mar 2009 20:53:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.blyberg.net/?p=38#comment-551991</guid>
		<description>[...] John. (2005). ILS Customer Bill of Rights, [...]</description>
		<content:encoded><![CDATA[<p>[...] John. (2005). ILS Customer Bill of Rights, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lis.dom &#187; reading offline, reading online</title>
		<link>http://www.blyberg.net/2005/11/20/ils-customer-bill-of-rights/comment-page-1/#comment-532439</link>
		<dc:creator>lis.dom &#187; reading offline, reading online</dc:creator>
		<pubDate>Sun, 23 Nov 2008 20:19:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.blyberg.net/?p=38#comment-532439</guid>
		<description>[...] when he&#8217;s writing: my natural inclination is to write something like this: John Blyberg’s ILS Customer Bill of Rights kicked off a lot of discussion regarding what libraries might demand of ILS vendors, especially in [...]</description>
		<content:encoded><![CDATA[<p>[...] when he&#8217;s writing: my natural inclination is to write something like this: John Blyberg’s ILS Customer Bill of Rights kicked off a lot of discussion regarding what libraries might demand of ILS vendors, especially in [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karen Celona</title>
		<link>http://www.blyberg.net/2005/11/20/ils-customer-bill-of-rights/comment-page-1/#comment-369967</link>
		<dc:creator>Karen Celona</dc:creator>
		<pubDate>Thu, 29 May 2008 01:11:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.blyberg.net/?p=38#comment-369967</guid>
		<description>I work for a library that is currently collaborating with an LMS vendor for many of these ideas. Our particular focus at the moment is on customer customisation, rss feeds and gadget/widgets to offer interaction on the website. It&#039;s nice to know we are heading in the right direction!</description>
		<content:encoded><![CDATA[<p>I work for a library that is currently collaborating with an LMS vendor for many of these ideas. Our particular focus at the moment is on customer customisation, rss feeds and gadget/widgets to offer interaction on the website. It&#8217;s nice to know we are heading in the right direction!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Library Software Manifesto &#124; Information Wants To Be Free</title>
		<link>http://www.blyberg.net/2005/11/20/ils-customer-bill-of-rights/comment-page-1/#comment-214913</link>
		<dc:creator>Library Software Manifesto &#124; Information Wants To Be Free</dc:creator>
		<pubDate>Tue, 13 Nov 2007 14:39:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.blyberg.net/?p=38#comment-214913</guid>
		<description>[...] relationship between libraries and vendors and libraries and patrons. This and John Blyberg&#8217;s ILS Customer Bill of Rights are two important documents that outline what we all should expect from our vendors, though [...]</description>
		<content:encoded><![CDATA[<p>[...] relationship between libraries and vendors and libraries and patrons. This and John Blyberg&#8217;s ILS Customer Bill of Rights are two important documents that outline what we all should expect from our vendors, though [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 数图研究 &#187; 火烧供应商，油炸OPAC</title>
		<link>http://www.blyberg.net/2005/11/20/ils-customer-bill-of-rights/comment-page-1/#comment-24673</link>
		<dc:creator>数图研究 &#187; 火烧供应商，油炸OPAC</dc:creator>
		<pubDate>Wed, 13 Dec 2006 14:43:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.blyberg.net/?p=38#comment-24673</guid>
		<description>[...] 最近太平洋那边的网络图林很是热闹，Blyberg去年11月写了著名的&#8221;图书馆集成管理系统用户权利法案(ILS Customer Bill-of-Rights)&#8221;（包含四条&#8221;权利&#8221;，类似于偶的&#8221;图书馆2.0五原则&#8220;，但还要&#8221;技术&#8221;的多）之后，Blyberg又写了一篇有趣的文章：火烧供应商，油炸OPAC 。编目精灵也用一幅截图点了III名，做了一个简要报道。SirsiDynix和其它一些ILS厂商或许正偷着乐，但是我估计这些一丘之貉的紧张要多于幸灾乐祸。 [...]</description>
		<content:encoded><![CDATA[<p>[...] 最近太平洋那边的网络图林很是热闹，Blyberg去年11月写了著名的&#8221;图书馆集成管理系统用户权利法案(ILS Customer Bill-of-Rights)&#8221;（包含四条&#8221;权利&#8221;，类似于偶的&#8221;图书馆2.0五原则&#8220;，但还要&#8221;技术&#8221;的多）之后，Blyberg又写了一篇有趣的文章：火烧供应商，油炸OPAC 。编目精灵也用一幅截图点了III名，做了一个简要报道。SirsiDynix和其它一些ILS厂商或许正偷着乐，但是我估计这些一丘之貉的紧张要多于幸灾乐祸。 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: OPAC Tips and Tricks &#171; Internet Librarian 2006</title>
		<link>http://www.blyberg.net/2005/11/20/ils-customer-bill-of-rights/comment-page-1/#comment-14541</link>
		<dc:creator>OPAC Tips and Tricks &#171; Internet Librarian 2006</dc:creator>
		<pubDate>Tue, 14 Nov 2006 14:21:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.blyberg.net/?p=38#comment-14541</guid>
		<description>[...] ILS Customer Bill of Rights &amp; PatRest (API to make library catalog content available for power users in other contexts) [...]</description>
		<content:encoded><![CDATA[<p>[...] ILS Customer Bill of Rights &amp; PatRest (API to make library catalog content available for power users in other contexts) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George Duimovich</title>
		<link>http://www.blyberg.net/2005/11/20/ils-customer-bill-of-rights/comment-page-1/#comment-8929</link>
		<dc:creator>George Duimovich</dc:creator>
		<pubDate>Thu, 19 Oct 2006 13:39:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.blyberg.net/?p=38#comment-8929</guid>
		<description>Having felt quite alienated on this issue for years, it is very encouraging to see this kind of discussion finally taking off in the last year.

Your comment on the traditional business model is correct, only I wish more people understood the dilemma (i.e. library directors, managers, etc.)

We all know this is a niche, &quot;mature market&quot; so ILS vendors have naturally accomodated their business models for this marketplace. Only now there&#039;s more widespread understanding of this two-fold problem: 1) architecture and systems engineering for obfuscation (the &quot;castle wall&quot; approach to systems engineering preventing you from finding/developing your own solutions); and 2) extreme product segmentation built upon and benefiting from 1).

IMO, Libraries are really getting **killed** by this situation, further marginalized, and the vendors will not be able to keep up. We get ILS innovations 2-6 years out of date, then have to follow-up with 6-24 months for a procurement /planning cycle to implement (assuming you can afford the upgrade).

We need the ILS to be built upon a general application foundation, and open in the ways described by the Customer Bill of Rights.</description>
		<content:encoded><![CDATA[<p>Having felt quite alienated on this issue for years, it is very encouraging to see this kind of discussion finally taking off in the last year.</p>
<p>Your comment on the traditional business model is correct, only I wish more people understood the dilemma (i.e. library directors, managers, etc.)</p>
<p>We all know this is a niche, &#8220;mature market&#8221; so ILS vendors have naturally accomodated their business models for this marketplace. Only now there&#8217;s more widespread understanding of this two-fold problem: 1) architecture and systems engineering for obfuscation (the &#8220;castle wall&#8221; approach to systems engineering preventing you from finding/developing your own solutions); and 2) extreme product segmentation built upon and benefiting from 1).</p>
<p>IMO, Libraries are really getting **killed** by this situation, further marginalized, and the vendors will not be able to keep up. We get ILS innovations 2-6 years out of date, then have to follow-up with 6-24 months for a procurement /planning cycle to implement (assuming you can afford the upgrade).</p>
<p>We need the ILS to be built upon a general application foundation, and open in the ways described by the Customer Bill of Rights.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Information Wants To Be Free &#187; Blog Archive &#187; Happy Blog Day!</title>
		<link>http://www.blyberg.net/2005/11/20/ils-customer-bill-of-rights/comment-page-1/#comment-5297</link>
		<dc:creator>Information Wants To Be Free &#187; Blog Archive &#187; Happy Blog Day!</dc:creator>
		<pubDate>Thu, 31 Aug 2006 17:07:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.blyberg.net/?p=38#comment-5297</guid>
		<description>[...] 5. When I first saw John Blyberg&#8217;s blog blyberg.net, I didn&#8217;t think it would be something I&#8217;d add to my blogroll because what I saw was a lot of code. I was like, &#8220;ok, he&#8217;s cool, but we don&#8217;t have III at Norwich and I have no idea what I&#8217;m reading anyways. But I saw an inkling of what was to come on his blog with the ILS Customer Bill of Rights and decided to stick with it. John came on most people&#8217;s radar screens as one of the major architects of the Ann Arbor District Library&#8217;s incredible Web site. He is a passionate advocate of Library 2.0 and of libraries empowering themselves to take control of their technological future. His posts show off his creative writing background as he muses on the philosophy of Library 2.0, how to bridge the tech gap, and how libraries can capitalize on mashups. His posts are the kind you reall need to print out and mull over. John to me is truly a philosopher of Library 2.0, but with the mad coding skills to back it up. I can&#8217;t wait to finally meet him in the flesh at Internet Librarian this October! [...]</description>
		<content:encoded><![CDATA[<p>[...] 5. When I first saw John Blyberg&#8217;s blog blyberg.net, I didn&#8217;t think it would be something I&#8217;d add to my blogroll because what I saw was a lot of code. I was like, &#8220;ok, he&#8217;s cool, but we don&#8217;t have III at Norwich and I have no idea what I&#8217;m reading anyways. But I saw an inkling of what was to come on his blog with the ILS Customer Bill of Rights and decided to stick with it. John came on most people&#8217;s radar screens as one of the major architects of the Ann Arbor District Library&#8217;s incredible Web site. He is a passionate advocate of Library 2.0 and of libraries empowering themselves to take control of their technological future. His posts show off his creative writing background as he muses on the philosophy of Library 2.0, how to bridge the tech gap, and how libraries can capitalize on mashups. His posts are the kind you reall need to print out and mull over. John to me is truly a philosopher of Library 2.0, but with the mad coding skills to back it up. I can&#8217;t wait to finally meet him in the flesh at Internet Librarian this October! [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Swem Review of Technology &#187; Blog Archive &#187; List of Blogs on the OPAC</title>
		<link>http://www.blyberg.net/2005/11/20/ils-customer-bill-of-rights/comment-page-1/#comment-1998</link>
		<dc:creator>Swem Review of Technology &#187; Blog Archive &#187; List of Blogs on the OPAC</dc:creator>
		<pubDate>Thu, 06 Jul 2006 21:57:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.blyberg.net/?p=38#comment-1998</guid>
		<description>[...] Addendum: I&#8217;m not sure there is an end to this topic. On Blyberg.net is this posting: OPACs in the frying pan, vendors in the fire. John takes an interesting chronological approach to the recent discussions particularly in light of his ILS Customer Bill -of -Rights. Recommended reading if you are concerned about the OPAC. Well, even if you are not concerned it is still recommended reading because you should be.  Explore posts in the same categories: Uncategorized [...]</description>
		<content:encoded><![CDATA[<p>[...] Addendum: I&#8217;m not sure there is an end to this topic. On Blyberg.net is this posting: OPACs in the frying pan, vendors in the fire. John takes an interesting chronological approach to the recent discussions particularly in light of his ILS Customer Bill -of -Rights. Recommended reading if you are concerned about the OPAC. Well, even if you are not concerned it is still recommended reading because you should be.  Explore posts in the same categories: Uncategorized [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Life as I Know It &#187; Blog Archive &#187; OPAC Blog Posts - A List</title>
		<link>http://www.blyberg.net/2005/11/20/ils-customer-bill-of-rights/comment-page-1/#comment-1949</link>
		<dc:creator>Life as I Know It &#187; Blog Archive &#187; OPAC Blog Posts - A List</dc:creator>
		<pubDate>Thu, 06 Jul 2006 01:43:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.blyberg.net/?p=38#comment-1949</guid>
		<description>[...] Blyberg.net 2006: the year of the phoenix OPAC? ILS Customer Bill of Rights Library 2.0 websites: Where to begin? Why bother: the impact of social OPACs [...]</description>
		<content:encoded><![CDATA[<p>[...] Blyberg.net 2006: the year of the phoenix OPAC? ILS Customer Bill of Rights Library 2.0 websites: Where to begin? Why bother: the impact of social OPACs [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
