<?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: XML Server and web services</title>
	<atom:link href="http://scriblio.net/scribbles/120/front-page-story2/feed/" rel="self" type="application/rss+xml" />
	<link>http://scriblio.net/scribbles/120/front-page-story2/</link>
	<description>open source software for libraries</description>
	<lastBuildDate>Sat, 21 Jan 2012 14:35:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: OPAC Web Services Should Be Like Amazon Web Services &#171; MaisonBisson.com</title>
		<link>http://scriblio.net/scribbles/120/front-page-story2/#comment-1621</link>
		<dc:creator>OPAC Web Services Should Be Like Amazon Web Services &#171; MaisonBisson.com</dc:creator>
		<pubDate>Wed, 30 Nov 2005 19:39:58 +0000</pubDate>
		<guid isPermaLink="false">http://libdev.plymouth.edu/?p=5#comment-1621</guid>
		<description>[...] Think about this for a moment: Our ILSs are inventory management systems, but our OPACs are (supposed to be) search and retrieval systems. The difference is obvious from here, but our vendors continue to operate as though you can&#8217;t have one without the other. [...]</description>
		<content:encoded><![CDATA[<p>[...] Think about this for a moment: Our ILSs are inventory management systems, but our OPACs are (supposed to be) search and retrieval systems. The difference is obvious from here, but our vendors continue to operate as though you can&#8217;t have one without the other. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Extending Blyberg&#8217;s XMLOPAC Class &#171; libdev</title>
		<link>http://scriblio.net/scribbles/120/front-page-story2/#comment-1620</link>
		<dc:creator>Extending Blyberg&#8217;s XMLOPAC Class &#171; libdev</dc:creator>
		<pubDate>Wed, 30 Nov 2005 14:59:28 +0000</pubDate>
		<guid isPermaLink="false">http://libdev.plymouth.edu/?p=5#comment-1620</guid>
		<description>[...] AADL&#8217;s John Blyberg is doing some great stuff with III&#8217;s XML Server, and his XMLOPAC PHP class is just what we need to start making use of the product (and cut through the bad XML it outputs). I&#8217;ve started re-writing the work I did previously, and I&#8217;m taking good advantage of the get_opac_data() function in that class. [...]</description>
		<content:encoded><![CDATA[<p>[...] AADL&#8217;s John Blyberg is doing some great stuff with III&#8217;s XML Server, and his XMLOPAC PHP class is just what we need to start making use of the product (and cut through the bad XML it outputs). I&#8217;ve started re-writing the work I did previously, and I&#8217;m taking good advantage of the get_opac_data() function in that class. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MaisonBisson.com &#187; Blog Archive &#187; Using XML In PHP5</title>
		<link>http://scriblio.net/scribbles/120/front-page-story2/#comment-1619</link>
		<dc:creator>MaisonBisson.com &#187; Blog Archive &#187; Using XML In PHP5</dc:creator>
		<pubDate>Tue, 22 Nov 2005 20:23:27 +0000</pubDate>
		<guid isPermaLink="false">http://libdev.plymouth.edu/?p=5#comment-1619</guid>
		<description>[...] Two problems: I haven&#8217;t encountered CDATA in my XML yet, but I do hope to develop a better solution than offered here when I do. The other is that SimpleXML chokes on illegal characters, a unfortunately common occurrence in documents coming from III&#8217;s XML Server. [...]</description>
		<content:encoded><![CDATA[<p>[...] Two problems: I haven&#8217;t encountered CDATA in my XML yet, but I do hope to develop a better solution than offered here when I do. The other is that SimpleXML chokes on illegal characters, a unfortunately common occurrence in documents coming from III&#8217;s XML Server. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Shifted Librarian</title>
		<link>http://scriblio.net/scribbles/120/front-page-story2/#comment-1618</link>
		<dc:creator>The Shifted Librarian</dc:creator>
		<pubDate>Fri, 18 Nov 2005 02:06:26 +0000</pubDate>
		<guid isPermaLink="false">http://libdev.plymouth.edu/?p=5#comment-1618</guid>
		<description>&lt;strong&gt;Casey Bisson Does It Again and Presents Exhibit B&lt;/strong&gt;

Displaying Clustered Search Results&#8220;A big point in my NEASIS&amp;T presentation Tuesday was how new technologies like XML and web services allow us to separate the tools that manage and store our data from the tools that display and manipulate it...</description>
		<content:encoded><![CDATA[<p><strong>Casey Bisson Does It Again and Presents Exhibit B</strong></p>
<p>Displaying Clustered Search Results&ldquo;A big point in my NEASIS&amp;T presentation Tuesday was how new technologies like XML and web services allow us to separate the tools that manage and store our data from the tools that display and manipulate it&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: libdev &#187; Displaying Clustered Search Results</title>
		<link>http://scriblio.net/scribbles/120/front-page-story2/#comment-1617</link>
		<dc:creator>libdev &#187; Displaying Clustered Search Results</dc:creator>
		<pubDate>Thu, 17 Nov 2005 03:07:08 +0000</pubDate>
		<guid isPermaLink="false">http://libdev.plymouth.edu/?p=5#comment-1617</guid>
		<description>[...] In this prototype, I&#8217;m using XML access to our catalog to fetch the top 150 results for a keyword search, aggregate the subject headings and authors, and display it all for the user. The data is live, so go get clicky on it. Also, try this version that displays the clusters in a more tag-like way. I&#8217;m not sure which view I like better, so I&#8217;m experimenting with both. [...]</description>
		<content:encoded><![CDATA[<p>[...] In this prototype, I&#8217;m using XML access to our catalog to fetch the top 150 results for a keyword search, aggregate the subject headings and authors, and display it all for the user. The data is live, so go get clicky on it. Also, try this version that displays the clusters in a more tag-like way. I&#8217;m not sure which view I like better, so I&#8217;m experimenting with both. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Casey</title>
		<link>http://scriblio.net/scribbles/120/front-page-story2/#comment-1616</link>
		<dc:creator>Casey</dc:creator>
		<pubDate>Mon, 25 Jul 2005 14:02:32 +0000</pubDate>
		<guid isPermaLink="false">http://libdev.plymouth.edu/?p=5#comment-1616</guid>
		<description>A relevant quote &lt;a href=&quot;http://panlibus.blogspot.com/2005/03/when-will-xml-replace-marc.html&quot; rel=&quot;nofollow&quot;&gt;found elsewhere&lt;/a&gt;:

&lt;blockquote&gt;...ILS systems themselves are endangered, not able to respond with agility to changing technologies. For libraries to flourish, bibliographic data needs to be flexibly deployable in broader environments lest we will gradually lose relevance.&lt;/blockquote&gt;

That was Dick Miller and his colleagues at the Lane Medical Library, Stanford University Medical Center. They weren&#039;t speaking specifically to this issue, but it seems to work. I found it at &lt;a href=&quot;http://panlibus.blogspot.com/2005/03/when-will-xml-replace-marc.html&quot; rel=&quot;nofollow&quot;&gt;Panlibus&lt;/a&gt;.

(note, I&#039;m conveniently ignoring the role of MARC in all this, since my real concern is about open access to any available metadata, no matter how it&#039;s structured.)</description>
		<content:encoded><![CDATA[<p>A relevant quote <a href="http://panlibus.blogspot.com/2005/03/when-will-xml-replace-marc.html" rel="nofollow">found elsewhere</a>:</p>
<blockquote><p>&#8230;ILS systems themselves are endangered, not able to respond with agility to changing technologies. For libraries to flourish, bibliographic data needs to be flexibly deployable in broader environments lest we will gradually lose relevance.</p></blockquote>
<p>That was Dick Miller and his colleagues at the Lane Medical Library, Stanford University Medical Center. They weren&#8217;t speaking specifically to this issue, but it seems to work. I found it at <a href="http://panlibus.blogspot.com/2005/03/when-will-xml-replace-marc.html" rel="nofollow">Panlibus</a>.</p>
<p>(note, I&#8217;m conveniently ignoring the role of MARC in all this, since my real concern is about open access to any available metadata, no matter how it&#8217;s structured.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MaisonBisson.com &#187; Blog Archive &#187; ILS: Inventory or Search and Retrieval System?</title>
		<link>http://scriblio.net/scribbles/120/front-page-story2/#comment-1615</link>
		<dc:creator>MaisonBisson.com &#187; Blog Archive &#187; ILS: Inventory or Search and Retrieval System?</dc:creator>
		<pubDate>Mon, 25 Jul 2005 13:15:32 +0000</pubDate>
		<guid isPermaLink="false">http://libdev.plymouth.edu/?p=5#comment-1615</guid>
		<description>[...] There&#8217;s an interesting discussion going at LibDev about what our ILSs are. It all started with a discussion of what role XML and webservices could/should play with ILS/catalogs, but a comment reminded us that Vendor&#8217;s decisions about adding new features to products that have been around for 20 or 30 years sometimes edge towards lock-in. I replied offering Flickr as an example of a vendor that&#8217;s been successful in part because of their open APIs. [...]</description>
		<content:encoded><![CDATA[<p>[...] There&#8217;s an interesting discussion going at LibDev about what our ILSs are. It all started with a discussion of what role XML and webservices could/should play with ILS/catalogs, but a comment reminded us that Vendor&#8217;s decisions about adding new features to products that have been around for 20 or 30 years sometimes edge towards lock-in. I replied offering Flickr as an example of a vendor that&#8217;s been successful in part because of their open APIs. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dwalker</title>
		<link>http://scriblio.net/scribbles/120/front-page-story2/#comment-1614</link>
		<dc:creator>dwalker</dc:creator>
		<pubDate>Fri, 15 Jul 2005 16:34:37 +0000</pubDate>
		<guid isPermaLink="false">http://libdev.plymouth.edu/?p=5#comment-1614</guid>
		<description>Allow to me to also play the devil’s (or at least the cynic’s) advocate. :-)

I would suggest that, much like Flickr, the Innopac actually &lt;strong&gt;does&lt;/strong&gt; do what it does well.  Like any ILS, the Innopac is really just an &lt;a href=&quot;http://www.google.com/search?q=inventory+management+system&quot; rel=&quot;nofollow&quot;&gt;inventory management system&lt;/a&gt;.  And a pretty good inventory management system it is -- so good, in fact, that our IT department here ditched their old system in favor of using our Innopac system to check-out laptops and multimedia equipment.

The problem is that we have long mistaken these systems for a search and retrieval tool.  That is really only a secondary (at best) feature of any ILS, and so it should come as no surprise to us that the Innopac leaves much, much to be desired in that area.  A good web services API, the ability to index and search on any field, and unlimited user liscences -- all without having to pay an arm and a leg for it.  Those would be the featres of a good search and retrieval tool.

We have inventory management systems.</description>
		<content:encoded><![CDATA[<p>Allow to me to also play the devil’s (or at least the cynic’s) advocate. <img src='http://scriblio.net/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>I would suggest that, much like Flickr, the Innopac actually <strong>does</strong> do what it does well.  Like any ILS, the Innopac is really just an <a href="http://www.google.com/search?q=inventory+management+system" rel="nofollow">inventory management system</a>.  And a pretty good inventory management system it is &#8212; so good, in fact, that our IT department here ditched their old system in favor of using our Innopac system to check-out laptops and multimedia equipment.</p>
<p>The problem is that we have long mistaken these systems for a search and retrieval tool.  That is really only a secondary (at best) feature of any ILS, and so it should come as no surprise to us that the Innopac leaves much, much to be desired in that area.  A good web services API, the ability to index and search on any field, and unlimited user liscences &#8212; all without having to pay an arm and a leg for it.  Those would be the featres of a good search and retrieval tool.</p>
<p>We have inventory management systems.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Casey</title>
		<link>http://scriblio.net/scribbles/120/front-page-story2/#comment-1613</link>
		<dc:creator>Casey</dc:creator>
		<pubDate>Thu, 14 Jul 2005 21:41:10 +0000</pubDate>
		<guid isPermaLink="false">http://libdev.plymouth.edu/?p=5#comment-1613</guid>
		<description>Brad, I can see you&#039;re playing devil&#039;s advocate. The following is targeted at vendors...

It used to be true that scarcity = value (or increased prices, anyway). The New York Times endorses that model in the way they put their content behind an auth-wall.

But as we look at commercial successes in the post dot-bomb era, we see more examples of how openness = value.

Google is one example, but I like &lt;a href=&quot;http://flickr.com&quot; rel=&quot;nofollow&quot;&gt;Flickr&lt;/a&gt; the best. It&#039;s a photo sharing site for the &quot;all electronic, no need for prints&quot; crowd. They&#039;ve made a lot of news and gotten a lot of customers by making it easy for people to use the Flickr-hosted content very easily.

A &lt;a href=&quot;http://conferences.oreillynet.com/cs/et2005/view/e_sess/6026&quot; rel=&quot;nofollow&quot;&gt;presentation at ETech2005&lt;/a&gt; spoke directly to this. I wasn&#039;t there, but the program description and online conversation made me wish I was.

If Flickr were an ILS, I would be incredibly pleased with it. It does what it does well -- the cataloging, classification, storage, and presentation of media objects (photos). I really like their &quot;OPAC&quot; interface, but Flickr has won me over because their API is so rich. I could export all my data and walk away, but I won&#039;t because I&#039;m happy to let them manage it for me. Instead, I can present my Flickr-hosted content elsewhere and re-use it in ways Flickr never imagined. &lt;a href=&quot;http://krazydad.com/colrpickr/index.php?group=graffiti&quot; rel=&quot;nofollow&quot;&gt;Flickr Colr Pickr&lt;/a&gt; is one outstanding example.</description>
		<content:encoded><![CDATA[<p>Brad, I can see you&#8217;re playing devil&#8217;s advocate. The following is targeted at vendors&#8230;</p>
<p>It used to be true that scarcity = value (or increased prices, anyway). The New York Times endorses that model in the way they put their content behind an auth-wall.</p>
<p>But as we look at commercial successes in the post dot-bomb era, we see more examples of how openness = value.</p>
<p>Google is one example, but I like <a href="http://flickr.com" rel="nofollow">Flickr</a> the best. It&#8217;s a photo sharing site for the &#8220;all electronic, no need for prints&#8221; crowd. They&#8217;ve made a lot of news and gotten a lot of customers by making it easy for people to use the Flickr-hosted content very easily.</p>
<p>A <a href="http://conferences.oreillynet.com/cs/et2005/view/e_sess/6026" rel="nofollow">presentation at ETech2005</a> spoke directly to this. I wasn&#8217;t there, but the program description and online conversation made me wish I was.</p>
<p>If Flickr were an ILS, I would be incredibly pleased with it. It does what it does well &#8212; the cataloging, classification, storage, and presentation of media objects (photos). I really like their &#8220;OPAC&#8221; interface, but Flickr has won me over because their API is so rich. I could export all my data and walk away, but I won&#8217;t because I&#8217;m happy to let them manage it for me. Instead, I can present my Flickr-hosted content elsewhere and re-use it in ways Flickr never imagined. <a href="http://krazydad.com/colrpickr/index.php?group=graffiti" rel="nofollow">Flickr Colr Pickr</a> is one outstanding example.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad</title>
		<link>http://scriblio.net/scribbles/120/front-page-story2/#comment-1612</link>
		<dc:creator>Brad</dc:creator>
		<pubDate>Wed, 13 Jul 2005 19:45:37 +0000</pubDate>
		<guid isPermaLink="false">http://libdev.plymouth.edu/?p=5#comment-1612</guid>
		<description>Digressing from the logical technical discussion...

Lock-in is a very real vendor strategy.  To export data, especially in lossless, standards-based bulk, is a giant red flag for some vendors.

What happens when the data is freed from the box and you can use it where you need it?  Burger King.  Have it your way.

Of course, the situation is infinately more complex...

Hopefully you under stand my point about logical viewpoints.  Our viewpoint is data freedom.  Some vendor&#039;s viewpoint is lock-in, thus continued revenue.</description>
		<content:encoded><![CDATA[<p>Digressing from the logical technical discussion&#8230;</p>
<p>Lock-in is a very real vendor strategy.  To export data, especially in lossless, standards-based bulk, is a giant red flag for some vendors.</p>
<p>What happens when the data is freed from the box and you can use it where you need it?  Burger King.  Have it your way.</p>
<p>Of course, the situation is infinately more complex&#8230;</p>
<p>Hopefully you under stand my point about logical viewpoints.  Our viewpoint is data freedom.  Some vendor&#8217;s viewpoint is lock-in, thus continued revenue.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
