<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel rdf:about="http://blogmarks.net/api/user/biblio/marks">
<title>Public marks from user biblio</title>
<description>Public marks from user biblio</description>
<link>http://blogmarks.net/user/biblio/marks</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/biblio/mark/95614"/>
<rdf:li resource="http://blogmarks.net/api/user/biblio/mark/95613"/>
<rdf:li resource="http://blogmarks.net/api/user/biblio/mark/95612"/>
<rdf:li resource="http://blogmarks.net/api/user/biblio/mark/95441"/>
<rdf:li resource="http://blogmarks.net/api/user/biblio/mark/95424"/>
<rdf:li resource="http://blogmarks.net/api/user/biblio/mark/95418"/>
<rdf:li resource="http://blogmarks.net/api/user/biblio/mark/95417"/>
<rdf:li resource="http://blogmarks.net/api/user/biblio/mark/95416"/>
<rdf:li resource="http://blogmarks.net/api/user/biblio/mark/95415"/>
<rdf:li resource="http://blogmarks.net/api/user/biblio/mark/95414"/>
<rdf:li resource="http://blogmarks.net/api/user/biblio/mark/95412"/>
<rdf:li resource="http://blogmarks.net/api/user/biblio/mark/95411"/>
<rdf:li resource="http://blogmarks.net/api/user/biblio/mark/95409"/>
<rdf:li resource="http://blogmarks.net/api/user/biblio/mark/95408"/>
<rdf:li resource="http://blogmarks.net/api/user/biblio/mark/95407"/>
<rdf:li resource="http://blogmarks.net/api/user/biblio/mark/95406"/>
<rdf:li resource="http://blogmarks.net/api/user/biblio/mark/95405"/>
<rdf:li resource="http://blogmarks.net/api/user/biblio/mark/95404"/>
<rdf:li resource="http://blogmarks.net/api/user/biblio/mark/95403"/>
<rdf:li resource="http://blogmarks.net/api/user/biblio/mark/95402"/>
<rdf:li resource="http://blogmarks.net/api/user/biblio/mark/95400"/>
<rdf:li resource="http://blogmarks.net/api/user/biblio/mark/95399"/>
<rdf:li resource="http://blogmarks.net/api/user/biblio/mark/95398"/>
<rdf:li resource="http://blogmarks.net/api/user/biblio/mark/95397"/>
<rdf:li resource="http://blogmarks.net/api/user/biblio/mark/95396"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/biblio/mark/95614">
<title>mozdev.org - greasemonkey: index</title>
<link>http://greasemonkey.mozdev.org/</link>
<description></description>
<dc:date>2005-06-17T21:12:57Z</dc:date>
<dc:author>biblio</dc:author>
<dc:subject></dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://greasemonkey.mozdev.org/"><img border="0" src="http://blogmarks.net/screenshots/2006/12/19/eb2801f112f593c4c184e4fa52e572ac.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://greasemonkey.mozdev.org/">mozdev.org - greasemonkey: index</a></h4>
 
by <a href="http://blogmarks.net/user/biblio">biblio</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/18571">44 other(s)</a> 
<p class="tags">
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=95614">Copy</a> | 
<a href="http://blogmarks.net/link/18571">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/biblio/mark/95613">
<title>EclipsePlugins : plugin overview</title>
<link>http://eclipse-plugins.info/eclipse/plugins.jsp?category=Editor&amp;sort=name</link>
<description></description>
<dc:date>2005-06-17T21:09:25Z</dc:date>
<dc:author>biblio</dc:author>
<dc:subject></dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://eclipse-plugins.info/eclipse/plugins.jsp?category=Editor&amp;sort=name"><img border="0" src="http://www.blogmarks.net/screenshots/2005/06/16/cc5e59092dbbd324f2280815048229b5.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://eclipse-plugins.info/eclipse/plugins.jsp?category=Editor&amp;sort=name">EclipsePlugins : plugin overview</a></h4>
 
by <a href="http://blogmarks.net/user/biblio">biblio</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/135244">1 other(s)</a> 
<p class="tags">
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=95613">Copy</a> | 
<a href="http://blogmarks.net/link/135244">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/biblio/mark/95612">
<title>Wikipedia</title>
<link>http://wikipedia.org/</link>
<description></description>
<dc:date>2005-06-17T21:09:08Z</dc:date>
<dc:author>biblio</dc:author>
<dc:subject></dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://wikipedia.org/"><img border="0" src="http://blogmarks.net/screenshots/2006/12/30/b02ad0dd15a7efb2b28391983c361075.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://wikipedia.org/">Wikipedia</a></h4>
 
by <a href="http://blogmarks.net/user/biblio">biblio</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/135249">6 other(s)</a> 
<p class="tags">
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=95612">Copy</a> | 
<a href="http://blogmarks.net/link/135249">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/biblio/mark/95441">
<title>Similar Articles</title>
<link>http://magportal.com/cgi-bin/sim.cgi?w=134408</link>
<description></description>
<dc:date>2005-06-17T15:14:13Z</dc:date>
<dc:author>biblio</dc:author>
<dc:subject></dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://magportal.com/cgi-bin/sim.cgi?w=134408"><img border="0" src="http://www.blogmarks.net/screenshots/2005/06/17/bacbaf119814f185037f7569c954bc16.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://magportal.com/cgi-bin/sim.cgi?w=134408">Similar Articles</a></h4>
 
by <a href="http://blogmarks.net/user/biblio">biblio</a> 
<p class="tags">
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=95441">Copy</a> | 
<a href="http://blogmarks.net/link/136176">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/biblio/mark/95424">
<title>Open-ILS.org | Library software by librarians for librarians.</title>
<link>http://open-ils.org/</link>
<description>We hit a milestone today: the anonymous</description>
<dc:date>2005-06-17T14:46:40Z</dc:date>
<dc:author>biblio</dc:author>
<dc:subject></dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://open-ils.org/"><img border="0" src="http://www.blogmarks.net/screenshots/2005/06/17/3a3215db538e86118ef8efb587e3da3c.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://open-ils.org/">Open-ILS.org | Library software by librarians for librarians.</a></h4>
 
by <a href="http://blogmarks.net/user/biblio">biblio</a> 
<p class="description">We hit a milestone today: the anonymous</p>
<p class="tags">
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=95424">Copy</a> | 
<a href="http://blogmarks.net/link/136150">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/biblio/mark/95418">
<title>The OCKHAM Initiative</title>
<link>http://www.ockham.org/</link>
<description>The OCKHAM Initiative seeks to promote the development of digital libraries via collaboration between librarians and digital library researchers. By promoting simple, open approaches and standards for digital library tools, services, and content, the gap between digital library development and the adoption of digital library systems by the traditional library community will be bridged.</description>
<dc:date>2005-06-17T14:17:43Z</dc:date>
<dc:author>biblio</dc:author>
<dc:subject></dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.ockham.org/"><img border="0" src="http://www.blogmarks.net/screenshots/2005/06/17/5487273bd3e6026e7de8ae804bfc4702.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.ockham.org/">The OCKHAM Initiative</a></h4>
 
by <a href="http://blogmarks.net/user/biblio">biblio</a> 
<p class="description">The OCKHAM Initiative seeks to promote the development of digital libraries via collaboration between librarians and digital library researchers. By promoting simple, open approaches and standards for digital library tools, services, and content, the gap between digital library development and the adoption of digital library systems by the traditional library community will be bridged.</p>
<p class="tags">
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=95418">Copy</a> | 
<a href="http://blogmarks.net/link/136142">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/biblio/mark/95417">
<title>The OCKHAM Library Network -- Integrating the NSDL into Traditional Library Services</title>
<link>http://wiki.osuosl.org/download/attachments/527/ockham.pdf</link>
<description>(application/pdf Object)</description>
<dc:date>2005-06-17T14:16:58Z</dc:date>
<dc:author>biblio</dc:author>
<dc:subject></dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://wiki.osuosl.org/download/attachments/527/ockham.pdf"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://wiki.osuosl.org/download/attachments/527/ockham.pdf">The OCKHAM Library Network -- Integrating the NSDL into Traditional Library Services</a></h4>
 
by <a href="http://blogmarks.net/user/biblio">biblio</a> 
<p class="description">(application/pdf Object)</p>
<p class="tags">
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=95417">Copy</a> | 
<a href="http://blogmarks.net/link/136140">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/biblio/mark/95416">
<title>All About LinkBaton</title>
<link>http://my.linkbaton.com/</link>
<description></description>
<dc:date>2005-06-17T14:15:58Z</dc:date>
<dc:author>biblio</dc:author>
<dc:subject>linkbaton</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://my.linkbaton.com/"><img border="0" src="http://www.blogmarks.net/screenshots/2005/06/17/835f68aca63a162b29f8ddfa9f3c961e.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://my.linkbaton.com/">All About LinkBaton</a></h4>
 
by <a href="http://blogmarks.net/user/biblio">biblio</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/linkbaton">linkbaton</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=95416">Copy</a> | 
<a href="http://blogmarks.net/link/136138">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/biblio/mark/95415">
<title>Turn your Library into a Portal for Books with LinkBaton</title>
<link>http://my.linkbaton.com/index2lib.html</link>
<description></description>
<dc:date>2005-06-17T14:15:46Z</dc:date>
<dc:author>biblio</dc:author>
<dc:subject>linkbaton</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://my.linkbaton.com/index2lib.html"><img border="0" src="http://www.blogmarks.net/screenshots/2005/06/17/a3f54bfc62d12268150d329aceffbcc9.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://my.linkbaton.com/index2lib.html">Turn your Library into a Portal for Books with LinkBaton</a></h4>
 
by <a href="http://blogmarks.net/user/biblio">biblio</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/linkbaton">linkbaton</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=95415">Copy</a> | 
<a href="http://blogmarks.net/link/136136">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/biblio/mark/95414">
<title>Basic Research Methods for Librarians (Information Management, Policy, and Services) (isbn: 1567503381)</title>
<link>http://my.linkbaton.com/get?lbCC=q&amp;genre=book&amp;item=1567503381&amp;lbV=4934</link>
<description></description>
<dc:date>2005-06-17T14:15:29Z</dc:date>
<dc:author>biblio</dc:author>
<dc:subject>linkbaton</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://my.linkbaton.com/get?lbCC=q&amp;genre=book&amp;item=1567503381&amp;lbV=4934"><img border="0" src="http://www.blogmarks.net/screenshots/2005/06/17/0d28cb1234ea8630e2d02a4ad00c074c.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://my.linkbaton.com/get?lbCC=q&amp;genre=book&amp;item=1567503381&amp;lbV=4934">Basic Research Methods for Librarians (Information Management, Policy, and Services) (isbn: 1567503381)</a></h4>
 
by <a href="http://blogmarks.net/user/biblio">biblio</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/linkbaton">linkbaton</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=95414">Copy</a> | 
<a href="http://blogmarks.net/link/136134">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/biblio/mark/95412">
<title>Dublin Core Community Profile (DCCP) for Simple Dublin Core in KEV Format</title>
<link>http://alcme.oclc.org/openurl/docs/pdf/DublinCoreProfile-2004.pdf</link>
<description>(application/pdf Object)</description>
<dc:date>2005-06-17T14:14:23Z</dc:date>
<dc:author>biblio</dc:author>
<dc:subject></dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://alcme.oclc.org/openurl/docs/pdf/DublinCoreProfile-2004.pdf"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://alcme.oclc.org/openurl/docs/pdf/DublinCoreProfile-2004.pdf">Dublin Core Community Profile (DCCP) for Simple Dublin Core in KEV Format</a></h4>
 
by <a href="http://blogmarks.net/user/biblio">biblio</a> 
<p class="description">(application/pdf Object)</p>
<p class="tags">
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=95412">Copy</a> | 
<a href="http://blogmarks.net/link/136131">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/biblio/mark/95411">
<title>The OpenURL Router</title>
<link>http://openurl.ac.uk/doc</link>
<description>What does the OpenURL Router do?
openurl.ac.uk is the home of the OpenURL Router</description>
<dc:date>2005-06-17T14:13:25Z</dc:date>
<dc:author>biblio</dc:author>
<dc:subject></dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://openurl.ac.uk/doc"><img border="0" src="http://www.blogmarks.net/screenshots/2005/06/17/9fc05146a4245c6dba5bc9f3779dd3c3.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://openurl.ac.uk/doc">The OpenURL Router</a></h4>
 
by <a href="http://blogmarks.net/user/biblio">biblio</a> 
<p class="description">What does the OpenURL Router do?
openurl.ac.uk is the home of the OpenURL Router</p>
<p class="tags">
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=95411">Copy</a> | 
<a href="http://blogmarks.net/link/136129">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/biblio/mark/95409">
<title>NISO Committee AX -- Bibliography on OpenURL Issues</title>
<link>http://library.caltech.edu/openurl/Bibliography.htm</link>
<description></description>
<dc:date>2005-06-17T14:12:55Z</dc:date>
<dc:author>biblio</dc:author>
<dc:subject></dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://library.caltech.edu/openurl/Bibliography.htm"><img border="0" src="http://www.blogmarks.net/screenshots/2005/06/17/1be05bf0f15f916e3b6bd751ed920881.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://library.caltech.edu/openurl/Bibliography.htm">NISO Committee AX -- Bibliography on OpenURL Issues</a></h4>
 
by <a href="http://blogmarks.net/user/biblio">biblio</a> 
<p class="tags">
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=95409">Copy</a> | 
<a href="http://blogmarks.net/link/136125">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/biblio/mark/95408">
<title>OpenURL demonstrator - Distributed Systems - UKOLN</title>
<link>http://www.ukoln.ac.uk/distributed-systems/openurl/</link>
<description>This page provides a quick demonstration of OpenURLs and how they can be resolved in a context sensitive way.</description>
<dc:date>2005-06-17T14:11:31Z</dc:date>
<dc:author>biblio</dc:author>
<dc:subject></dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.ukoln.ac.uk/distributed-systems/openurl/"><img border="0" src="http://www.blogmarks.net/screenshots/2005/06/17/dfac16e056c6780bbcb790c7dd84b623.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.ukoln.ac.uk/distributed-systems/openurl/">OpenURL demonstrator - Distributed Systems - UKOLN</a></h4>
 
by <a href="http://blogmarks.net/user/biblio">biblio</a> 
<p class="description">This page provides a quick demonstration of OpenURLs and how they can be resolved in a context sensitive way.</p>
<p class="tags">
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=95408">Copy</a> | 
<a href="http://blogmarks.net/link/136123">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/biblio/mark/95407">
<title>Ex Libris - SFX - OpenURL Overview</title>
<link>http://www.exlibrisgroup.com/sfx_openurl.htm</link>
<description>The OpenURL standard, first developed by Oren Beit-Arie, of Ex Libris, and Herbert Van de Sompel, now of the Los Alamos National Laboratory, is a protocol for interoperability between an information resource and a service component, referred to as a link server, which offers localized services.
The underlying concept of the OpenURL standard is that links should lead a user to appropriate resources. A link server, such as the SFX™ server from Ex Libris, defines the context of the user. When the link server accepts an OpenURL as input, it acts on it to provide users with services that comply with their institution's collections and policies.
The OpenURL standard enables a user who has retrieved an article citation, for example, to obtain immediate access to the &quot;most appropriate&quot; copy of that object through the implementation of extended linking services. The selection of the best copy is based on user and organizational preferences regarding the location of the copy, its cost, and agreements with information suppliers, and similar considerations. This selection occurs without the knowledge of the user; it is made possible by the transport of metadata with the OpenURL link from the source citation to a &quot;resolver&quot; (the link server), which stores the preference information and the links to the appropriate material.</description>
<dc:date>2005-06-17T14:11:01Z</dc:date>
<dc:author>biblio</dc:author>
<dc:subject></dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.exlibrisgroup.com/sfx_openurl.htm"><img border="0" src="http://www.blogmarks.net/screenshots/2005/06/17/c53bd55eff14d4d95cfdf09f7fa52246.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.exlibrisgroup.com/sfx_openurl.htm">Ex Libris - SFX - OpenURL Overview</a></h4>
 
by <a href="http://blogmarks.net/user/biblio">biblio</a> 
<p class="description">The OpenURL standard, first developed by Oren Beit-Arie, of Ex Libris, and Herbert Van de Sompel, now of the Los Alamos National Laboratory, is a protocol for interoperability between an information resource and a service component, referred to as a link server, which offers localized services.
The underlying concept of the OpenURL standard is that links should lead a user to appropriate resources. A link server, such as the SFX™ server from Ex Libris, defines the context of the user. When the link server accepts an OpenURL as input, it acts on it to provide users with services that comply with their institution's collections and policies.
The OpenURL standard enables a user who has retrieved an article citation, for example, to obtain immediate access to the "most appropriate" copy of that object through the implementation of extended linking services. The selection of the best copy is based on user and organizational preferences regarding the location of the copy, its cost, and agreements with information suppliers, and similar considerations. This selection occurs without the knowledge of the user; it is made possible by the transport of metadata with the OpenURL link from the source citation to a "resolver" (the link server), which stores the preference information and the links to the appropriate material.</p>
<p class="tags">
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=95407">Copy</a> | 
<a href="http://blogmarks.net/link/136121">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/biblio/mark/95406">
<title>Gussying up OpenSearch</title>
<link>http://dilettantes.blogspot.com/2005/06/gussying-up-opensearch.html</link>
<description>So, last week, before I left for SMUG, Mike Rylander (of Evergreen-ILS), Joshua Ferraro (of Liblime/Koha) and I began talking about OpenSearch interfaces for our respective catalogs. The only reason I was able to really contribute to the conversation was the fact that I had my little python CGI, but I hadn't thought much about it since I wrote it.</description>
<dc:date>2005-06-17T14:08:59Z</dc:date>
<dc:author>biblio</dc:author>
<dc:subject>dilettante's ball</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://dilettantes.blogspot.com/2005/06/gussying-up-opensearch.html"><img border="0" src="http://www.blogmarks.net/screenshots/2005/06/17/a87373bbc4ae58a084b63ee761ec6841.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://dilettantes.blogspot.com/2005/06/gussying-up-opensearch.html">Gussying up OpenSearch</a></h4>
 
by <a href="http://blogmarks.net/user/biblio">biblio</a> 
<p class="description">So, last week, before I left for SMUG, Mike Rylander (of Evergreen-ILS), Joshua Ferraro (of Liblime/Koha) and I began talking about OpenSearch interfaces for our respective catalogs. The only reason I was able to really contribute to the conversation was the fact that I had my little python CGI, but I hadn't thought much about it since I wrote it.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/dilettante%2527s%2Bball">dilettante's ball</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=95406">Copy</a> | 
<a href="http://blogmarks.net/link/136119">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/biblio/mark/95405">
<title>Polishing the turd: the dangers of redesigning the OPAC</title>
<link>http://dilettantes.blogspot.com/2005/05/polishing-turd-dangers-of-redesigning.html</link>
<description>So as Art and I continue to try to export the data from our respective Voyager catalogs to create an alternative web opac, I have been trying to formulate what such a beast should look like. We have the opportunity to make the web interface look and behave in any way we want, so there are a lot of things to think about. The goal is to make the opac behave in the way non-information professionals would expect a searching interface to work, so we're not just talking about a cosmetic makeover to the current design.</description>
<dc:date>2005-06-17T14:05:36Z</dc:date>
<dc:author>biblio</dc:author>
<dc:subject>dilettante's ball</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://dilettantes.blogspot.com/2005/05/polishing-turd-dangers-of-redesigning.html"><img border="0" src="http://www.blogmarks.net/screenshots/2005/06/17/419d7f09046d4bf9cf42a967121fa4d0.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://dilettantes.blogspot.com/2005/05/polishing-turd-dangers-of-redesigning.html">Polishing the turd: the dangers of redesigning the OPAC</a></h4>
 
by <a href="http://blogmarks.net/user/biblio">biblio</a> 
<p class="description">So as Art and I continue to try to export the data from our respective Voyager catalogs to create an alternative web opac, I have been trying to formulate what such a beast should look like. We have the opportunity to make the web interface look and behave in any way we want, so there are a lot of things to think about. The goal is to make the opac behave in the way non-information professionals would expect a searching interface to work, so we're not just talking about a cosmetic makeover to the current design.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/dilettante%2527s%2Bball">dilettante's ball</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=95405">Copy</a> | 
<a href="http://blogmarks.net/link/136117">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/biblio/mark/95404">
<title>Loomware - Crafting New Libraries: Folksonomies Help Information Organization</title>
<link>http://blog.uwinnipeg.ca/loomware/archives/001025.html</link>
<description>Jashua Porter has a short piece about Folksonomies and their role in overcoming the difficulty in implementing taxonomies in the standard website.</description>
<dc:date>2005-06-17T14:00:52Z</dc:date>
<dc:author>biblio</dc:author>
<dc:subject></dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://blog.uwinnipeg.ca/loomware/archives/001025.html"><img border="0" src="http://www.blogmarks.net/screenshots/2005/06/17/b36ef9e1cb4bb9193dc3493f13d0df64.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://blog.uwinnipeg.ca/loomware/archives/001025.html">Loomware - Crafting New Libraries: Folksonomies Help Information Organization</a></h4>
 
by <a href="http://blogmarks.net/user/biblio">biblio</a> 
<p class="description">Jashua Porter has a short piece about Folksonomies and their role in overcoming the difficulty in implementing taxonomies in the standard website.</p>
<p class="tags">
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=95404">Copy</a> | 
<a href="http://blogmarks.net/link/136115">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/biblio/mark/95403">
<title>Loomware - Crafting New Libraries</title>
<link>http://blog.uwinnipeg.ca/loomware/</link>
<description>Discussions related to information and technology in academic libraries, universities and life in general.</description>
<dc:date>2005-06-17T13:59:49Z</dc:date>
<dc:author>biblio</dc:author>
<dc:subject></dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://blog.uwinnipeg.ca/loomware/"><img border="0" src="http://www.blogmarks.net/screenshots/2005/06/17/64b202275aab99c96bffbfc131553397.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://blog.uwinnipeg.ca/loomware/">Loomware - Crafting New Libraries</a></h4>
 
by <a href="http://blogmarks.net/user/biblio">biblio</a> 
<p class="description">Discussions related to information and technology in academic libraries, universities and life in general.</p>
<p class="tags">
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=95403">Copy</a> | 
<a href="http://blogmarks.net/link/136113">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/biblio/mark/95402">
<title>Folksonomies: A User-Driven Approach to Organizing Content</title>
<link>http://www.uie.com/articles/folksonomies/</link>
<description>Many of the design teams we talk to face the same major issue: how to organize the information on their sites. From creating navigation schemes to developing site hierarchies to refining checkout sequences, it’s highly important for design teams to organize information effectively for their users.
Information architects frequently must deal with the problem of managing more and more information. Rarely can they remove information from a site; in most cases, it’s add, add, add. Design teams must make room for this new content in some way, either by incorporating it into the current organizational scheme or by altering the information architecture to allow for it.</description>
<dc:date>2005-06-17T13:58:26Z</dc:date>
<dc:author>biblio</dc:author>
<dc:subject></dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.uie.com/articles/folksonomies/"><img border="0" src="http://www.blogmarks.net/screenshots/2005/04/28/228b2384af8d291c01c9696141ad8bb7.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.uie.com/articles/folksonomies/">Folksonomies: A User-Driven Approach to Organizing Content</a></h4>
 
by <a href="http://blogmarks.net/user/biblio">biblio</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/87497">2 other(s)</a> 
<p class="description">Many of the design teams we talk to face the same major issue: how to organize the information on their sites. From creating navigation schemes to developing site hierarchies to refining checkout sequences, it’s highly important for design teams to organize information effectively for their users.
Information architects frequently must deal with the problem of managing more and more information. Rarely can they remove information from a site; in most cases, it’s add, add, add. Design teams must make room for this new content in some way, either by incorporating it into the current organizational scheme or by altering the information architecture to allow for it.</p>
<p class="tags">
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=95402">Copy</a> | 
<a href="http://blogmarks.net/link/87497">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/biblio/mark/95400">
<title>Putting Context Into Context</title>
<link>http://www.uie.com/articles/putting_context_into_context/</link>
<description>When purchasing a computer from Dell.com, you have the option to configure the machine and get exactly the options you want. Once you've reached a configuration you're satisfied with, you can save it, print it out, fax it to someone, or e-mail it.
When the designers at Dell added this functionality, they knew something other online computer retailers didn't know. They knew that computers were high ticket purchases and that people, when buying one, often need to seek the approval of a high authority (such as their boss or spouse). The design needed to provide an easy way for someone to stop the purchase process and go off to get that approval.
How did the designers at Dell realize this important requirement while virtually every other vendor missed it? They understood something the other vendors didn't. They understood the “context” of buying a computer.</description>
<dc:date>2005-06-17T13:58:02Z</dc:date>
<dc:author>biblio</dc:author>
<dc:subject></dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.uie.com/articles/putting_context_into_context/"><img border="0" src="http://www.blogmarks.net/screenshots/2005/06/17/b312b014bfcc2008d6d2dddc5769ac94.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.uie.com/articles/putting_context_into_context/">Putting Context Into Context</a></h4>
 
by <a href="http://blogmarks.net/user/biblio">biblio</a> 
<p class="description">When purchasing a computer from Dell.com, you have the option to configure the machine and get exactly the options you want. Once you've reached a configuration you're satisfied with, you can save it, print it out, fax it to someone, or e-mail it.
When the designers at Dell added this functionality, they knew something other online computer retailers didn't know. They knew that computers were high ticket purchases and that people, when buying one, often need to seek the approval of a high authority (such as their boss or spouse). The design needed to provide an easy way for someone to stop the purchase process and go off to get that approval.
How did the designers at Dell realize this important requirement while virtually every other vendor missed it? They understood something the other vendors didn't. They understood the “context” of buying a computer.</p>
<p class="tags">
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=95400">Copy</a> | 
<a href="http://blogmarks.net/link/136109">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/biblio/mark/95399">
<title>RSS &amp; Libraries: Ahab's great white whale</title>
<link>http://dilettantes.blogspot.com/2005/04/rss-libraries-ahabs-great-white-whale.html</link>
<description>If the library blogosphere was your only source of current events within libraries, you would think that RSS was new MARC record and that podcasting will alleviate the need for circ rules.</description>
<dc:date>2005-06-17T14:07:21Z</dc:date>
<dc:author>biblio</dc:author>
<dc:subject>dilettante's ball</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://dilettantes.blogspot.com/2005/04/rss-libraries-ahabs-great-white-whale.html"><img border="0" src="http://www.blogmarks.net/screenshots/2005/06/17/3d4ef5c2682ff90d2aa66fa400c851c8.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://dilettantes.blogspot.com/2005/04/rss-libraries-ahabs-great-white-whale.html">RSS &amp; Libraries: Ahab's great white whale</a></h4>
 
by <a href="http://blogmarks.net/user/biblio">biblio</a> 
<p class="description">If the library blogosphere was your only source of current events within libraries, you would think that RSS was new MARC record and that podcasting will alleviate the need for circ rules.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/dilettante%2527s%2Bball">dilettante's ball</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=95399">Copy</a> | 
<a href="http://blogmarks.net/link/136107">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/biblio/mark/95398">
<title>xISBN Bookmarks</title>
<link>http://alcme.oclc.org/bookmarks/servlet/OAIHandler?verb=ListRecords&amp;metadataPrefix=oai_dc</link>
<description>* Repository Identification
* OPAC List
* Add Library

These bookmarklets were inspired by Jon Udell's LibraryLookup homepage. The enhancement provided here is to include other ISBNs for the same work in the query.
As Jon notes in his tips, the same work is often available in a variety of editions, all with different ISBNs. Based on OCLC's FRBR Research, related ISBNs have been clustered and made available as a stand-alone web service.
Sorting the list by the number of OCLC member libraries that hold that ISBN increases the probability of finding a hit near the top of the list. To account for the possibility that the user really is interested in a particular ISBN, that number appears first in the list, regardless of the number of holding libraries.
In the future, however, these bookmarklets may be further enhanced to take advantage of the fact that OCLC already knows which editions of a work your library holds and place those at the top of the list.</description>
<dc:date>2005-06-17T13:54:03Z</dc:date>
<dc:author>biblio</dc:author>
<dc:subject></dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://alcme.oclc.org/bookmarks/servlet/OAIHandler?verb=ListRecords&amp;metadataPrefix=oai_dc"><img border="0" src="http://blogmarks.net/screenshots/2006/08/02/84757a6299aa2b90604e2b2f66a0669a.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://alcme.oclc.org/bookmarks/servlet/OAIHandler?verb=ListRecords&amp;metadataPrefix=oai_dc">xISBN Bookmarks</a></h4>
 
by <a href="http://blogmarks.net/user/biblio">biblio</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/136105">2 other(s)</a> 
<p class="description">* Repository Identification
* OPAC List
* Add Library

These bookmarklets were inspired by Jon Udell's LibraryLookup homepage. The enhancement provided here is to include other ISBNs for the same work in the query.
As Jon notes in his tips, the same work is often available in a variety of editions, all with different ISBNs. Based on OCLC's FRBR Research, related ISBNs have been clustered and made available as a stand-alone web service.
Sorting the list by the number of OCLC member libraries that hold that ISBN increases the probability of finding a hit near the top of the list. To account for the possibility that the user really is interested in a particular ISBN, that number appears first in the list, regardless of the number of holding libraries.
In the future, however, these bookmarklets may be further enhanced to take advantage of the fact that OCLC already knows which editions of a work your library holds and place those at the top of the list.</p>
<p class="tags">
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=95398">Copy</a> | 
<a href="http://blogmarks.net/link/136105">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/biblio/mark/95397">
<title>Jon's Radio -- The LibraryLookup Project</title>
<link>http://weblog.infoworld.com/udell/stories/2002/12/11/librarylookup.html</link>
<description>If your local public (or college) library uses one of the online catalog systems listed here, you may be able to create a bookmarklet that will help you look up books in your library.
After you've &quot;installed&quot; your bookmarklet by dragging it to your browser's link toolbar, you can use it to look up books at your local library. Let's say you're on a book-related site (Amazon, BN, isbn.nu, All Consuming, possibly others), and a book's info page is your current page. (Specifically: its URL contains an ISBN. Choose a hardcover edition for best results -- see tips below.) You can click your bookmarklet to check if the book is available in your local library. The bookmarklet will invoke your library's lookup service, feed it the ISBN, and pop up a new window with the result.</description>
<dc:date>2005-06-17T13:52:54Z</dc:date>
<dc:author>biblio</dc:author>
<dc:subject></dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://weblog.infoworld.com/udell/stories/2002/12/11/librarylookup.html"><img border="0" src="http://www.blogmarks.net/screenshots/2005/06/17/f4147ee4a55ed8c5b0bd0a8e559f565e.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://weblog.infoworld.com/udell/stories/2002/12/11/librarylookup.html">Jon's Radio -- The LibraryLookup Project</a></h4>
 
by <a href="http://blogmarks.net/user/biblio">biblio</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/136103">3 other(s)</a> 
<p class="description">If your local public (or college) library uses one of the online catalog systems listed here, you may be able to create a bookmarklet that will help you look up books in your library.
After you've "installed" your bookmarklet by dragging it to your browser's link toolbar, you can use it to look up books at your local library. Let's say you're on a book-related site (Amazon, BN, isbn.nu, All Consuming, possibly others), and a book's info page is your current page. (Specifically: its URL contains an ISBN. Choose a hardcover edition for best results -- see tips below.) You can click your bookmarklet to check if the book is available in your local library. The bookmarklet will invoke your library's lookup service, feed it the ISBN, and pop up a new window with the result.</p>
<p class="tags">
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=95397">Copy</a> | 
<a href="http://blogmarks.net/link/136103">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/biblio/mark/95396">
<title>Getting Started with Z39.50 - AMICUS - Library and Archives Canada</title>
<link>http://www.collectionscanada.ca/amicus/006002-400-e.html</link>
<description>Services

Z39.50 is an information retrieval standard supported by libraries and software vendors to access information resources independent of the database location or the hardware/software used.
* NLC Z39.50 enables you to search and retrieve records from the National Library of Canada database using Z39.50 software connected to the Internet. The NLC collection is a portion (approximately 10%) of the entire AMICUS database. This service does not require registration.
* AMICUS Z39.50 enables you to search and retrieve records from the entire AMICUS database using Z39.50 software connected to the Internet. This service requires that you register for an AMICUS account.</description>
<dc:date>2005-06-17T13:48:48Z</dc:date>
<dc:author>biblio</dc:author>
<dc:subject></dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.collectionscanada.ca/amicus/006002-400-e.html"><img border="0" src="http://www.blogmarks.net/screenshots/2005/06/17/95f3d8ee5d264c67050e52e3ace0ca9d.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.collectionscanada.ca/amicus/006002-400-e.html">Getting Started with Z39.50 - AMICUS - Library and Archives Canada</a></h4>
 
by <a href="http://blogmarks.net/user/biblio">biblio</a> 
<p class="description">Services

Z39.50 is an information retrieval standard supported by libraries and software vendors to access information resources independent of the database location or the hardware/software used.
* NLC Z39.50 enables you to search and retrieve records from the National Library of Canada database using Z39.50 software connected to the Internet. The NLC collection is a portion (approximately 10%) of the entire AMICUS database. This service does not require registration.
* AMICUS Z39.50 enables you to search and retrieve records from the entire AMICUS database using Z39.50 software connected to the Internet. This service requires that you register for an AMICUS account.</p>
<p class="tags">
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=95396">Copy</a> | 
<a href="http://blogmarks.net/link/136101">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>