<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2enclosuresfull.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:media="http://search.yahoo.com/mrss/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0"><channel><title>tompasley::: misc ramblings and thoughts</title><link>http://tompasley.blogspot.com/</link><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/TomPasley-misc" /><description>If you find something useful on this blog, then all good... my ramblings are generally about, (but not limited to), metadata, information sources and services.&lt;br&gt;

Fairly often, you'll find that my posts relate to OpenURL (both 0.1 and Z39.88-2004), the "SFX" for linking in the scholarly world.&lt;br&gt;

NTS:: are the odd blog postings which are "note(s) to self" (- I tend to lose bits of paper). Don't expect them to make sense!</description><language>en</language><managingEditor>noreply@blogger.com (tompasley)</managingEditor><lastBuildDate>Thu, 16 Feb 2012 14:34:38 PST</lastBuildDate><generator>Blogger http://www.blogger.com</generator><openSearch:totalResults xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/">46</openSearch:totalResults><openSearch:startIndex xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/">1</openSearch:startIndex><openSearch:itemsPerPage xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/">25</openSearch:itemsPerPage><feedburner:info uri="tompasley-misc" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><media:copyright>Attribution-Noncommercial-Share Alike 3.0 Unported [ http://creativecommons.org/licenses/by-nc-sa/3.0/ ]</media:copyright><media:category scheme="http://www.itunes.com/dtds/podcast-1.0.dtd">Technology</media:category><itunes:owner><itunes:email>tom.pasley@gmail.com</itunes:email><itunes:name>Tom Pasley</itunes:name></itunes:owner><itunes:author>Tom Pasley</itunes:author><itunes:explicit>no</itunes:explicit><itunes:subtitle>Mainly focussed on information content (the whole range, but mostly published, such as journal articles) and how it's stored, presented, communicated, and used.</itunes:subtitle><itunes:summary>Mainly focussed on information content (the whole range, but mostly published, such as journal articles) and how it's stored, presented, communicated, and used.</itunes:summary><itunes:category text="Technology" /><item><title>NTS:: Aureal brand Infrared remote</title><link>http://feedproxy.google.com/~r/TomPasley-misc/~3/wIfe40USwag/nts-aureal-brand-infrared-remote.html</link><category>infrared remote</category><category>xbmc</category><category>patch</category><category>crunchbang linux</category><category>usb</category><author>tom.pasley@gmail.com (Tom Pasley)</author><pubDate>Sat, 05 Feb 2011 17:32:55 PST</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8030521401785829981.post-252267812509851622</guid><description>&lt;span style="font-family:arial;"&gt;Here's where to get the &lt;a href="http://forum.xbmc.org/showpost.php?p=648689&amp;amp;postcount=3"&gt;instructions for the patch&lt;/a&gt;&lt;/span&gt; to get this "Computer Remoter Control" "P-01RN" working.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8030521401785829981-252267812509851622?l=tompasley.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TomPasley-misc/~4/wIfe40USwag" height="1" width="1"/&gt;</description><app:edited xmlns:app="http://www.w3.org/2007/app">2011-02-06T14:32:55.800+13:00</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://tompasley.blogspot.com/2011/02/nts-aureal-brand-infrared-remote.html</feedburner:origLink></item><item><title>NTS:: XBMC + MP3 playback</title><link>http://feedproxy.google.com/~r/TomPasley-misc/~3/UKLJhvDEW9U/nts-xbmc-mp3-playback.html</link><category>playback</category><category>sound</category><category>mp3</category><category>xbmc</category><category>spdif</category><category>crunchbang linux</category><author>tom.pasley@gmail.com (Tom Pasley)</author><pubDate>Fri, 04 Feb 2011 12:21:48 PST</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8030521401785829981.post-812569454048653703</guid><description>&lt;span style="font-family: arial;font-size:100%;" &gt;This took some checking to find, and it's kinda counter-intuitive... do not, not ever, use Crossfade in XBMC if you want MP3 playback to work with a guri el-cheapo spdif soundcard to work under XBMC.&lt;br /&gt;&lt;br /&gt;Under Crunchbang 9.01, avoid PulseAudio, ALSA works just fine, thanks very much - here's my asound.conf if you're in the same boat as I was:&lt;br /&gt;&lt;br /&gt;&lt;blockquote&gt;pcm.dmixer {&lt;br /&gt;type dmix&lt;br /&gt;ipc_key 1024&lt;br /&gt;ipc_key_add_uid false&lt;br /&gt;ipc_perm 0660&lt;br /&gt;slave {&lt;br /&gt;pcm "hw:0,1"&lt;br /&gt;rate 48000&lt;br /&gt;channels 2&lt;br /&gt;format S32_LE&lt;br /&gt;period_time 0&lt;br /&gt;period_size 1024&lt;br /&gt;buffer_time 0&lt;br /&gt;buffer_size 4096&lt;br /&gt;}&lt;br /&gt;}&lt;br /&gt;&lt;br /&gt;pcm.!default {&lt;br /&gt;type plug&lt;br /&gt;slave.pcm "dmixer"&lt;br /&gt;}&lt;/blockquote&gt;&lt;br /&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8030521401785829981-812569454048653703?l=tompasley.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TomPasley-misc/~4/UKLJhvDEW9U" height="1" width="1"/&gt;</description><app:edited xmlns:app="http://www.w3.org/2007/app">2011-02-05T09:21:48.563+13:00</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://tompasley.blogspot.com/2011/02/nts-xbmc-mp3-playback.html</feedburner:origLink></item><item><title>NTS:: #! setup</title><link>http://feedproxy.google.com/~r/TomPasley-misc/~3/4BO8w0qjS-I/nts-setup.html</link><category>shutdown</category><category>crunchbang linux</category><author>tom.pasley@gmail.com (Tom Pasley)</author><pubDate>Wed, 10 Nov 2010 21:48:32 PST</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8030521401785829981.post-4596553805343714997</guid><description>CrunchBang is my favourite Linux distro, and I have it running on my fileserver, which is running on a paltry 256Mb of RAM.&lt;br /&gt;&lt;br /&gt;I discovered after poking around how to shutdown OpenBox properly, without the whole sudo shutdown problem (I found it would hang, and power-off). This script allows me to power-off once downloads are complete, using &lt;a href="http://inbasic.mozdev.org/root/ext2/home/index.htm"&gt;auto-shutdown&lt;/a&gt;, together with DownThemAll.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-family: times new roman;"&gt;#/bin/bash&lt;/span&gt;&lt;br style="font-family: times new roman;"&gt;&lt;span style="font-family: times new roman;"&gt;#&lt;/span&gt;&lt;br style="font-family: times new roman;"&gt;&lt;span style="font-family: times new roman;"&gt;let wait_time=$1*60&lt;/span&gt;&lt;br style="font-family: times new roman;"&gt;&lt;span style="font-family: times new roman;"&gt;echo "will shutdown in $1 minutes"&lt;/span&gt;&lt;br style="font-family: times new roman;"&gt;&lt;span style="font-family: times new roman;"&gt;sleep $wait_time&lt;/span&gt;&lt;br style="font-family: times new roman;"&gt;&lt;span style="font-family: times new roman;"&gt;gdm-control --shutdown &amp;amp;&amp;amp; openbox --exit&lt;/span&gt;&lt;br style="font-family: times new roman;"&gt;&lt;span style="font-family: times new roman;"&gt;exit 0&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;One of the things I've got going nicely is DropBox, which normally works well under Nautilus, so not really so good on OpenBox. DropBox works well following &lt;a href="http://crunchbanglinux.org/wiki/howto/howto_setup_dropbox"&gt;the instructions on the OpenBox wiki&lt;/a&gt;.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8030521401785829981-4596553805343714997?l=tompasley.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TomPasley-misc/~4/4BO8w0qjS-I" height="1" width="1"/&gt;</description><app:edited xmlns:app="http://www.w3.org/2007/app">2010-11-11T18:48:32.067+13:00</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://tompasley.blogspot.com/2010/11/nts-setup.html</feedburner:origLink></item><item><title>NTS: SMP8635</title><link>http://feedproxy.google.com/~r/TomPasley-misc/~3/FT3hCLgIiPI/nts-smp8635.html</link><category>magictv mtv3600hd smp86xx</category><author>tom.pasley@gmail.com (Tom Pasley)</author><pubDate>Sun, 06 Jun 2010 15:42:21 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8030521401785829981.post-2101318260959179760</guid><description>There seems to be plenty of software out there to build a firmware -  there's various places to look, but I think there's a complete picture  between them:&lt;br /&gt;&lt;br /&gt;&lt;a href="http://b-rad.cc/wdlxtv/"&gt;http://b-rad.cc/wdlxtv/&lt;/a&gt;&lt;br /&gt;&lt;a href="http://support.wdc.com/product/download.asp?groupid=1001&amp;amp;sid=112&amp;amp;lang=en"&gt;http://support.wdc.com/product/download.asp?groupid=1001&amp;amp;sid=112&amp;amp;lang=en&lt;/a&gt;&lt;br /&gt;&lt;a href="http://www.networkedmediatank.com/download/firmware/nmt/gpl/gpl.htm"&gt;http://www.networkedmediatank.com/download/firmware/nmt/gpl/gpl.htm&lt;/a&gt;&lt;br /&gt;&lt;a href="http://wiki.opentvix.com/Sigma_Tools"&gt;http://wiki.opentvix.com/Sigma_Tools&lt;/a&gt;&lt;br /&gt;&lt;a href="http://www.wdtvc.com/downloads/"&gt;http://www.wdtvc.com/downloads/&lt;/a&gt;&lt;br /&gt;&lt;a href="http://download.opentvix.com/"&gt;http://download.opentvix.com/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I've asked MagicTV NZ (aka HookTech), and they're in  contact with Hong Kong, and hopefully trying to get the code from  PixelMagic. It would be nice if there were media player abilities on this box:&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_pYH7AU916_w/TAi7DfYOUcI/AAAAAAAAABQ/fN4EUtThHHo/s1600/MTV3600D_image_rear_panel.jpg"&gt;&lt;img style="display: block; margin: 0px auto 10px; text-align: center; cursor: pointer; width: 320px; height: 159px;" src="http://2.bp.blogspot.com/_pYH7AU916_w/TAi7DfYOUcI/AAAAAAAAABQ/fN4EUtThHHo/s320/MTV3600D_image_rear_panel.jpg" alt="" id="BLOGGER_PHOTO_ID_5478834615333310914" border="0" /&gt;&lt;/a&gt;... but I'm worried I'll brick the box in the process (and fall out of favour in the process!).&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8030521401785829981-2101318260959179760?l=tompasley.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TomPasley-misc/~4/FT3hCLgIiPI" height="1" width="1"/&gt;</description><app:edited xmlns:app="http://www.w3.org/2007/app">2010-06-07T10:42:21.365+12:00</app:edited><media:thumbnail url="http://2.bp.blogspot.com/_pYH7AU916_w/TAi7DfYOUcI/AAAAAAAAABQ/fN4EUtThHHo/s72-c/MTV3600D_image_rear_panel.jpg" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://tompasley.blogspot.com/2010/06/nts-smp8635.html</feedburner:origLink></item><item><title>Slippery slope for linked data</title><link>http://feedproxy.google.com/~r/TomPasley-misc/~3/EMR5rBB83Ok/slippery-slope-for-linked-data.html</link><category>linkeddata</category><category>openurl resolver</category><category>openurl</category><category>publishing</category><author>tom.pasley@gmail.com (Tom Pasley)</author><pubDate>Mon, 29 Mar 2010 01:27:15 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8030521401785829981.post-5202861990714798128</guid><description>I've been wondering for a while how to create a platform that used linked data natively.&lt;br /&gt;&lt;br /&gt;There are plenty of platform building options which understand ordinary relational databases, but, for my requirements, there's nothing like Yii with a linked-data backend.&lt;br /&gt;&lt;br /&gt;Anyway, I'd really like to see an OpenURL resolver re-use the data by making the requests it's given available as linked open data, in much the same way as SFX exposes it's data for other purposes, such as the bX service.&lt;br /&gt;&lt;br /&gt;I also hope I can see a time when publishers, or a body representing them (CrossRef)will make the metadata for the articles they produce freely available, like Nature Publishing... hell, a lot of them expose their content to Google, so why not maximise their exposure via other means?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8030521401785829981-5202861990714798128?l=tompasley.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TomPasley-misc/~4/EMR5rBB83Ok" height="1" width="1"/&gt;</description><app:edited xmlns:app="http://www.w3.org/2007/app">2010-03-29T21:27:15.408+13:00</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><feedburner:origLink>http://tompasley.blogspot.com/2010/03/slippery-slope-for-linked-data.html</feedburner:origLink></item><item><title>CrossRef Labs - worth a look!</title><link>http://feedproxy.google.com/~r/TomPasley-misc/~3/I-Np_dRzaug/crossref-labs-worth-look.html</link><category>RESTful api</category><category>crossref</category><category>opensearch</category><category>doi</category><category>doi registration agency</category><category>crossref labs</category><author>tom.pasley@gmail.com (Tom Pasley)</author><pubDate>Thu, 15 Oct 2009 10:41:51 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8030521401785829981.post-6622365311430559717</guid><description>If you work in the "information space", then it's nice to know that CrossRef have some &lt;a href="http://labs.crossref.org/"&gt;developmental services&lt;/a&gt;, but there's one, (okay, two), in particular that I really like the look of:&lt;br /&gt;&lt;br /&gt;&lt;ol&gt;&lt;li&gt;&lt;a href="http://labs.crossref.org/site/crossref_metadata_search.html"&gt;Metadata Search&lt;/a&gt; complete with an OpenSearch plugin. This is &lt;a href="http://labs.crossref.org/site/crossref_metadata_search.html"&gt;not, of course a complete "search"&lt;/a&gt;: "Instead, CrossRef Metadata Search is focused on allowing researchers to lookup citations using &lt;strong&gt;only&lt;/strong&gt; terms that might appear in the bibliographic metadata of the item they are searching for."&lt;/li&gt;&lt;li&gt;an undocumented aspect &lt;a href="http://twitter.com/tompasley/statuses/4873290548"&gt;which I discovered&lt;/a&gt; which is a more RESTful service providing the metadata for a given DOI. This is of the form: &lt;span class="status-body"&gt;&lt;span class="entry-content"&gt;&lt;a href="http://api.labs.crossref.org/" class="tweet-url web" rel="nofollow" target="_blank"&gt;http://api.labs.crossref.org/&lt;/a&gt;{DOI}.xml&lt;/span&gt;&lt;/span&gt;&lt;/li&gt;&lt;/ol&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8030521401785829981-6622365311430559717?l=tompasley.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TomPasley-misc/~4/I-Np_dRzaug" height="1" width="1"/&gt;</description><app:edited xmlns:app="http://www.w3.org/2007/app">2009-10-16T06:41:51.989+13:00</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://tompasley.blogspot.com/2009/10/crossref-labs-worth-look.html</feedburner:origLink></item><item><title>txtckr stage 1</title><link>http://feedproxy.google.com/~r/TomPasley-misc/~3/XOCiqOrlrWo/txtckr-stage-1.html</link><category>txtckr</category><category>php</category><category>coding</category><author>tom.pasley@gmail.com (Tom Pasley)</author><pubDate>Sat, 26 Sep 2009 22:08:37 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8030521401785829981.post-1364845105000270847</guid><description>Well, I've just committed a batch of updates to &lt;a href="http://code.google.com/p/txtckr/"&gt;txtckr&lt;/a&gt;, which has finally moved beyond a mix of php &amp;amp; pseudo-php to a stage where I run it on a laptop without any errors (with the included very simple test).&lt;br /&gt;&lt;br /&gt;It's almost at the stage of adding the finishing touches to the name handling, where the various openurl name parts get humpty-dumptied again. It's just skeleton coding at this stage, but hopefully a pretty sound basis for what's to come!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8030521401785829981-1364845105000270847?l=tompasley.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TomPasley-misc/~4/XOCiqOrlrWo" height="1" width="1"/&gt;</description><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-27T18:08:37.968+13:00</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://tompasley.blogspot.com/2009/09/txtckr-stage-1.html</feedburner:origLink></item><item><title>Google Co-op: EBSCO Connect search</title><link>http://feedproxy.google.com/~r/TomPasley-misc/~3/TQhiouBXbgU/google-co-op-ebsco-connect-search.html</link><category>google coop</category><category>ebscohost</category><category>esbcoconnect</category><category>ebscohost connect</category><category>google custom search</category><author>tom.pasley@gmail.com (Tom Pasley)</author><pubDate>Fri, 18 Sep 2009 01:23:37 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8030521401785829981.post-1964420248825426543</guid><description>There's been a bit of &lt;a href="http://dltj.org/article/ebscohost-connection/"&gt;talk about EBSCO Connect content&lt;/a&gt; appearing on Google, and while it's not the sort of thing that thrills me necessarily, I found it was easy enough to create yet another Google Custom search, which would allow the retrieval of &lt;a href="http://www.google.com/cse/home?cx=014186842424919502546:qzzw5rwa5cu&amp;amp;hl=en"&gt;EBSCO connect material&lt;/a&gt; only.&lt;br /&gt;&lt;br /&gt;There appears to be quite a bit of content there - give the search a go, and leave a response if you feel that way inclined...&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8030521401785829981-1964420248825426543?l=tompasley.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TomPasley-misc/~4/TQhiouBXbgU" height="1" width="1"/&gt;</description><app:edited xmlns:app="http://www.w3.org/2007/app">2009-09-18T20:23:37.683+12:00</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://tompasley.blogspot.com/2009/09/google-co-op-ebsco-connect-search.html</feedburner:origLink></item><item><title>Dealing with humans' (names)</title><link>http://feedproxy.google.com/~r/TomPasley-misc/~3/k8qOCjzxu5E/dealing-with-humans-names.html</link><category>databases</category><category>txtckr</category><category>references</category><category>openurl resolver</category><category>programming</category><category>names</category><category>php</category><category>openurl</category><category>authors</category><author>tom.pasley@gmail.com (Tom Pasley)</author><pubDate>Wed, 05 Aug 2009 11:26:52 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8030521401785829981.post-5281470129628553281</guid><description>Recently I hit a slight snag on a fairly common problem... dealing with names. This is a problematic area, given that everyone has one, and trying to build in what we know about names into software is actually a bit of a slog!&lt;br /&gt;&lt;br /&gt;What I'm doing is trying to parse names, (mainly author names), for txtckr, so that one of the output display formats could be a reference, (APA, for example).  To do this, I also need to untangle the "rft.au" information which is delivered through OpenURL, and I'm trying to build in some "forgiveness" to allow for people/companies that don't follow spec's properly!&lt;br /&gt;&lt;br /&gt;Things to consider:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;with a full name, is it supplied first-name(s) last-name/surname, and if so, where does the surname begin? This is fine for a fair number of relatively simple names, but what about surnames which aren't, such as "van der Weerden"?&lt;/li&gt;&lt;li&gt;if you're going to receive name fragments, how do you build these sensibly into software, so you can give permutations of the name, e.g. Pasley, Tom == Pasley, T. == Tom Pasley == T. Pasley?&lt;/li&gt;&lt;/ul&gt;No doubt I'm not the first person to tackle this problem, and I'm probably over-thinking things slightly, but I'm open to tips about projects that/from anyone else who's tackled this problem...&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8030521401785829981-5281470129628553281?l=tompasley.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TomPasley-misc/~4/k8qOCjzxu5E" height="1" width="1"/&gt;</description><app:edited xmlns:app="http://www.w3.org/2007/app">2009-08-06T06:26:52.735+12:00</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total><feedburner:origLink>http://tompasley.blogspot.com/2009/08/dealing-with-humans-names.html</feedburner:origLink></item><item><title>What if OpenURL resolvers could blog?</title><link>http://feedproxy.google.com/~r/TomPasley-misc/~3/CYMbYndV4bs/what-if-openurl-resolvers-could-blog.html</link><category>atom</category><category>wordpress</category><category>unapi coins</category><category>openurl resolver</category><category>blogging</category><category>openurl</category><category>rss</category><author>tom.pasley@gmail.com (Tom Pasley)</author><pubDate>Thu, 16 Jul 2009 18:21:38 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8030521401785829981.post-9031077803910640754</guid><description>I thought about this when I was thinking about having support for unAPI, etc. I found Mike Giarlo's &lt;a href="http://lackoftalent.org/michael/blog/unapi-wordpress-plug-in/"&gt;plugin for WordPress&lt;/a&gt;, which added this, and I could make it work for &lt;a href="http://code.google.com/p/txtckr/source/browse/?r=3#svn/trunk/lib%3Fstate%3Dclosed"&gt;txtckr&lt;/a&gt;, but why should I?&lt;br /&gt;&lt;br /&gt;I may have overlooked something, (since I don't use WordPress), but:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;what if WordPress was the OpenURL resolver, (well, actually it wasn't but just looked like it)?&lt;br /&gt;&lt;/li&gt;&lt;li&gt;what if txtckr could redirect to the WordPress post which had the request response once it had made a post which contained all of that info?&lt;/li&gt;&lt;/ul&gt;The advantage of automatic posting the details and output of an OpenURL resolver, (and subsequent redirection), to a blog post is that it  increases the discoverability of the item being requested.&lt;br /&gt;&lt;br /&gt;There's also the tools available through something like the WordPress platform, which further promotes the re-distribution of information about articles, books, etc., including COinS, RSS feeds, OAI-PMH, unAPI, etc.&lt;br /&gt;&lt;br /&gt;Of course there's also the ability for others to comment and refer, (trackback), on the item being represented in the blog post.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8030521401785829981-9031077803910640754?l=tompasley.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TomPasley-misc/~4/CYMbYndV4bs" height="1" width="1"/&gt;</description><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-17T13:21:38.439+12:00</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total><feedburner:origLink>http://tompasley.blogspot.com/2009/07/what-if-openurl-resolvers-could-blog.html</feedburner:origLink></item><item><title>txtckr under development</title><link>http://feedproxy.google.com/~r/TomPasley-misc/~3/a__jYjPmDV4/txtckr-under-development.html</link><category>google code</category><category>txtckr</category><category>gpl</category><category>textseeka</category><author>tom.pasley@gmail.com (Tom Pasley)</author><pubDate>Thu, 16 Jul 2009 18:17:29 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8030521401785829981.post-6337526319541045277</guid><description>While I was working at Crop &amp;amp; Food Research, I developed an &lt;a href="http://lib.crop.cri.nz/textseeka/"&gt;OpenURL resolver&lt;/a&gt;&lt;a href="http://lib.crop.cri.nz/textseeka/"&gt; called textseeka&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;&lt;a href="http://code.google.com/p/txtckr/"&gt;txtckr&lt;/a&gt; is a GPL, (open-source), OOP focussed, replacement for textseeka, based on what I know now, in terms of programming, OpenURL, webservices and metadata sources.&lt;br /&gt;&lt;br /&gt;This is not a simple overnight project, complicated by the fact that I need access to the original code-base, which is still at my old work. Over time, (snatched here and there),  txtckr will be fleshed out, starting from the bones that are there now, (currently just a class for the "context object").&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8030521401785829981-6337526319541045277?l=tompasley.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TomPasley-misc/~4/a__jYjPmDV4" height="1" width="1"/&gt;</description><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-17T13:17:29.987+12:00</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://tompasley.blogspot.com/2009/07/txtckr-under-development.html</feedburner:origLink></item><item><title>If you can't bet them, join 'em...</title><link>http://feedproxy.google.com/~r/TomPasley-misc/~3/Tdw4q1NdpDI/if-you-cant-bet-them-join-em.html</link><category>voyager</category><category>Ex Libris</category><category>voyager_7</category><author>tom.pasley@gmail.com (Tom Pasley)</author><pubDate>Sun, 05 Jul 2009 17:24:07 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8030521401785829981.post-6875924918068204303</guid><description>I've been at &lt;a href="http://library.ucol.ac.nz/"&gt;UCOL Library&lt;/a&gt; for a while now, which means I'm firmly part of the Ex Libris picture, as we have Voyager, which is quite a part of my job, as the Information systems Librarian.&lt;br /&gt;&lt;br /&gt;As such, I've spent quite a bit of time putting lipstick on the pig... and one of the features I've implemented recently is an APA citation for each of the books in our catalogue, which is bottom-rightish. This picture might be a little fuzzy, (but you can't see it unless you're on-campus anyway...):&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_pYH7AU916_w/SlFD4vjR4UI/AAAAAAAAABE/kyVXG24wOMM/s1600-h/Mockup+with+OCLC+APA+citation.bmp"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 385px; height: 238px;" src="http://3.bp.blogspot.com/_pYH7AU916_w/SlFD4vjR4UI/AAAAAAAAABE/kyVXG24wOMM/s320/Mockup+with+OCLC+APA+citation.bmp" alt="" id="BLOGGER_PHOTO_ID_5355136074036404546" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;Initially, I thought this would be quite easy, since I thought we must have at least some OCLC-derived records in our catalogue. The APA citation service requires an OCLC number, and I learnt that there are not that many records which have OCLC numbers... but there are, of course, lots which have ISBNs.&lt;br /&gt;&lt;br /&gt;The solution required writing some web scripts which:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;do a lookup on the ISBN, and get the OCLC number&lt;/li&gt;&lt;li&gt;use the OCLC number to get the APA citation&lt;/li&gt;&lt;li&gt;generate JSON output so this is accessible to the browser&lt;/li&gt;&lt;/ul&gt;Actually, thinking about it, I should be able to do this with javascript through and through... shouldn't I?&lt;br /&gt;&lt;br /&gt;Isn't this what LibX does? Maybe this is part of what is currently possible with their LibApps?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8030521401785829981-6875924918068204303?l=tompasley.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TomPasley-misc/~4/Tdw4q1NdpDI" height="1" width="1"/&gt;</description><app:edited xmlns:app="http://www.w3.org/2007/app">2009-07-06T12:24:07.489+12:00</app:edited><media:thumbnail url="http://3.bp.blogspot.com/_pYH7AU916_w/SlFD4vjR4UI/AAAAAAAAABE/kyVXG24wOMM/s72-c/Mockup+with+OCLC+APA+citation.bmp" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://tompasley.blogspot.com/2009/07/if-you-cant-bet-them-join-em.html</feedburner:origLink></item><item><title>NTS:: When Sansa's go bad...</title><link>http://feedproxy.google.com/~r/TomPasley-misc/~3/YoOddIhbuYY/nts-when-sansas-go-bad.html</link><category>repair</category><category>brick</category><category>sansa</category><category>sandisk</category><category>bricked</category><category>sansa express</category><category>recovery</category><category>disaster</category><author>tom.pasley@gmail.com (Tom Pasley)</author><pubDate>Fri, 12 Jun 2009 20:48:26 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8030521401785829981.post-4666654120060197726</guid><description>&lt;span style="font-family:arial;"&gt;&lt;span style="font-weight: bold; color: rgb(204, 0, 0);"&gt;[Legal Warning: By following these instructions, you agree not to hold me liable for any bad sh*t that happens to your MP3 player.]&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://tbn2.google.com/images?q=tbn:KoKi86cr_bLT6M:http://www.cnet.com.au/story_media/339279753/sandisk-sansa-express_1.jpg"&gt;&lt;br /&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 127px; height: 95px;" src="http://tbn2.google.com/images?q=tbn:KoKi86cr_bLT6M:http://www.cnet.com.au/story_media/339279753/sandisk-sansa-express_1.jpg" alt="" border="0" /&gt;&lt;/a&gt;&lt;span style="font-family:arial;"&gt;&lt;span style="font-weight: bold; color: rgb(204, 0, 0);font-family:times new roman;" &gt;&lt;/span&gt;&lt;br /&gt;In case this happens again, here's how to un-brick a Sansa Express... in Windows XP, with access to the &lt;span style="font-weight: bold;"&gt;Administrative Tools&lt;/span&gt; (I'm not sure how to do the same in Linux - any ideas?).&lt;br /&gt;&lt;br /&gt;I'm unsure how my son's Sansa Express was bricked, but a common cause fro "bricking" is the inability of the Sansa Updater to finish the complete process of updating the firmware. A complicating factor can be the lack of a newer version of the firmware... so you need to have a older version of the firmware on hand [thankfully &lt;a href="http://chrisjs.com/download/firmware/SEFirmware1_01_01.7z"&gt;chrisjs has a copy&lt;/a&gt;].&lt;br /&gt;&lt;br /&gt;Okay, here's what to do:&lt;br /&gt;&lt;/span&gt;&lt;ol&gt;&lt;li&gt;Unzip the files from the 7zip file, (see link above), into it's own directory.&lt;br /&gt;&lt;/li&gt;&lt;li&gt;Hold the Volume Down &lt;span style="font-weight: bold;"&gt;-&lt;/span&gt; button on the Sansa Express while inserting it into a USB port on your computer, and hold for about 20 seconds.&lt;br /&gt;&lt;/li&gt;&lt;li&gt;Release it, and hopefully in Windows Explorer you should see 2 Flash Drive symbols, but when you try to use them, they're empty, and you can't format them either (they're 0Mb in size :])&lt;br /&gt;&lt;/li&gt;&lt;li&gt;DON'T PANIC!&lt;/li&gt;&lt;li&gt;In my case, access to the Admin Tools is off the Control Panel - the one that I've used is Computer Management.&lt;/li&gt;&lt;li&gt;Under Storage, click on Disk Management&lt;/li&gt;&lt;li&gt;In the top right panel, locate your dud "Flash Drive"... it shouldn't indicate a file system, because that's what a bricked Sansa looks like...&lt;/li&gt;&lt;li&gt;Right-mouse click on the Disk Drive icon in the left column of that same panel, and you should see the option to format your Sansa - (at this point I can't remember is I used FAT as the filesystem, or FAT32).&lt;/li&gt;&lt;li&gt;Format the Sansa&lt;/li&gt;&lt;li&gt;Then go back to the directory with the unzipped files, and use SansaExpressUpdater.exe&lt;/li&gt;&lt;li&gt;You should find that the Sansa Updater will complete the update, and when the process is complete, the Sansa Express should be un-bricked.&lt;br /&gt;&lt;/li&gt;&lt;/ol&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8030521401785829981-4666654120060197726?l=tompasley.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TomPasley-misc/~4/YoOddIhbuYY" height="1" width="1"/&gt;</description><app:edited xmlns:app="http://www.w3.org/2007/app">2009-06-13T15:48:26.651+12:00</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://tompasley.blogspot.com/2009/06/nts-when-sansas-go-bad.html</feedburner:origLink></item><item><title>EndNote on Ubuntu</title><link>http://feedproxy.google.com/~r/TomPasley-misc/~3/pAy3zZous_k/endnote-on-ubuntu.html</link><category>linux</category><category>endnote</category><category>ubuntu</category><author>tom.pasley@gmail.com (Tom Pasley)</author><pubDate>Fri, 29 May 2009 19:59:01 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8030521401785829981.post-1274070130417312768</guid><description>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_pYH7AU916_w/SiCgmjHmgtI/AAAAAAAAAA0/5tsOnihyriM/s1600-h/EndNote.png"&gt;&lt;img style="float:left; margin:0 0 10px 10px;cursor:pointer; cursor:hand;width: 200px; height: 125px;" src="http://3.bp.blogspot.com/_pYH7AU916_w/SiCgmjHmgtI/AAAAAAAAAA0/5tsOnihyriM/s200/EndNote.png" border="0" alt=""id="BLOGGER_PHOTO_ID_5341445742184006354" /&gt;&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8030521401785829981-1274070130417312768?l=tompasley.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TomPasley-misc/~4/pAy3zZous_k" height="1" width="1"/&gt;</description><app:edited xmlns:app="http://www.w3.org/2007/app">2009-05-30T14:59:01.625+12:00</app:edited><media:thumbnail url="http://3.bp.blogspot.com/_pYH7AU916_w/SiCgmjHmgtI/AAAAAAAAAA0/5tsOnihyriM/s72-c/EndNote.png" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://tompasley.blogspot.com/2009/05/endnote-on-ubuntu.html</feedburner:origLink></item><item><title>Farewell PlantandFood.com, Hi UCOL</title><link>http://feedproxy.google.com/~r/TomPasley-misc/~3/plR9IrCLrpU/farewell-plantandfoodcom-hi-ucol.html</link><category>farewell</category><category>pfr</category><category>ucol</category><category>jobs</category><category>cfr</category><category>plantandfood.com</category><author>tom.pasley@gmail.com (Tom Pasley)</author><pubDate>Wed, 20 May 2009 15:19:51 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8030521401785829981.post-6024995344422694863</guid><description>Well, I'm in my "break period" between jobs.&lt;br /&gt;&lt;br /&gt;I start as the Information Systems Librarian at UCOL on Monday, so I might not be posting much for a little while, while I get my head around Voyager, etc.&lt;br /&gt;&lt;br /&gt;I really enjoyed my time at Crop &amp;amp; Food Research, (which merged with HortResearch and became Plant and Food Research 1 December 2008), and then at &lt;a href="http://plantandfood.com/"&gt;Plant and Food Research&lt;/a&gt;. It was a really interesting place for me, as a librarian, to work: I felt appreciated by other staff, (particularly "the scientists"), I had great people to work with, and there was plenty to get my teeth into! There was also &lt;a href="http://www.wizards.com/MAGIC/"&gt;Magic&lt;/a&gt; for a while at lunchtimes, and though I seldom won, it was good fun.&lt;br /&gt;&lt;br /&gt;So, thanks to all of the exCFR/PFR staff -those who were kind enough to put comments in my card, and for their farewells, and also for the lovely farewell gifts. I really enjoyed my time with you guys, and I hope to keep in touch!&lt;br /&gt;&lt;br /&gt;The laptop bag I'm especially chuffed with, since it's also a backpack - great for those times when you're tired, and your laptop seems to weigh a ton! (- no, I don't have a 17" laptop, but I'm optimistic...).&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.noelleeming.co.nz/renderImage.image?imageName=products/64/64058_lg.png&amp;amp;width=405&amp;amp;height=266&amp;amp;padding=2"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: left; cursor: pointer; width: 178px; height: 117px;" src="http://www.noelleeming.co.nz/renderImage.image?imageName=products/64/64058_lg.png&amp;amp;width=405&amp;amp;height=266&amp;amp;padding=2" alt="" border="0" /&gt;&lt;/a&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://www.dse.co.nz/isroot/dse/images/products/XH0503%7ELGE.JPG"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: right; cursor: pointer; width: 289px; height: 390px;" src="http://www.dse.co.nz/isroot/dse/images/products/XH0503%7ELGE.JPG" alt="" border="0" /&gt;&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8030521401785829981-6024995344422694863?l=tompasley.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TomPasley-misc/~4/plR9IrCLrpU" height="1" width="1"/&gt;</description><app:edited xmlns:app="http://www.w3.org/2007/app">2009-05-21T10:19:51.871+12:00</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://tompasley.blogspot.com/2009/05/farewell-plantandfoodcom-hi-ucol.html</feedburner:origLink></item><item><title>Librarian-developed/enhanced resources</title><link>http://feedproxy.google.com/~r/TomPasley-misc/~3/6mEEx5BzjUk/librarian-developedenhanced-resources.html</link><category>librarians</category><category>linkeddata</category><category>openurl resolver</category><category>librarian-developed/enhanced resources</category><author>tom.pasley@gmail.com (Tom Pasley)</author><pubDate>Sun, 17 May 2009 20:41:13 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8030521401785829981.post-2165175155663690707</guid><description>Okay, I've hinted at this in my last post... in this category would be anything that (any group)/Library/Librarian develops for/with it's clients/users - some examples:&lt;br /&gt;&lt;br /&gt;&lt;ul&gt;&lt;li&gt;OpenURL resolver logged data (and no, I'm not meaning like Ex Libris bX). This is meshed-up data from a variety of web-services which your OpenURL resolver consumes to deliver the data and services which are displayed to Library clients/users as a result of their request.&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Librarian-developed interfaces - an example being something like a Z39.50 interface to an existing catalogue/dataset which presents the data in a different way... like a more user-friendly interface which shows individual results in more detail, with an OpenURL link to request them (as I demo'd at work to Ann Barrie from NLNZ - I'll post a screenshot if I get time).&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_pYH7AU916_w/ShDYtfb8HMI/AAAAAAAAAAs/v9qbwz7c_Vc/s1600-h/texttrawla.PNG"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 320px; height: 60px;" src="http://4.bp.blogspot.com/_pYH7AU916_w/ShDYtfb8HMI/AAAAAAAAAAs/v9qbwz7c_Vc/s320/texttrawla.PNG" alt="" id="BLOGGER_PHOTO_ID_5337003834478435522" border="0" /&gt;&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;&lt;ul&gt;&lt;li&gt;&lt;a href="http://linkeddata.org/"&gt;LinkedData&lt;/a&gt; - there's plenty of this stuff being done including on the &lt;a href="http://dataincubator.org/"&gt;dataincubator site&lt;/a&gt; (no, I'm not employed by Talis, and I'm not sure how many of the people in this group are actually "Librarians")&lt;br /&gt;&lt;/li&gt;&lt;/ul&gt;So, as you can see, it's not just formal/normal "vendors" who provide &lt;span style="font-family:arial;"&gt;"information resources"&lt;/span&gt;. Why does Ex Libris &lt;i&gt;seem&lt;/i&gt; to miss this point?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8030521401785829981-2165175155663690707?l=tompasley.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TomPasley-misc/~4/6mEEx5BzjUk" height="1" width="1"/&gt;</description><app:edited xmlns:app="http://www.w3.org/2007/app">2009-05-18T15:41:13.872+12:00</app:edited><media:thumbnail url="http://4.bp.blogspot.com/_pYH7AU916_w/ShDYtfb8HMI/AAAAAAAAAAs/v9qbwz7c_Vc/s72-c/texttrawla.PNG" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">1</thr:total><feedburner:origLink>http://tompasley.blogspot.com/2009/05/librarian-developedenhanced-resources.html</feedburner:origLink></item><item><title>Picking fights with giants...</title><link>http://feedproxy.google.com/~r/TomPasley-misc/~3/AMF5qgu-Xnw/picking-fights-with-giants_06.html</link><category>Ex Libris</category><category>information resources</category><category>librarians</category><author>tom.pasley@gmail.com (Tom Pasley)</author><pubDate>Tue, 05 May 2009 21:39:31 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8030521401785829981.post-6291609876526866007</guid><description>&lt;span style="font-family:arial;"&gt;A while ago I picked a fight with Ex Libris, mainly about their EL Commons, mainly on two points (although I'd hoped they'd be moot points now):&lt;/span&gt;&lt;br /&gt;&lt;blockquote style="font-family: arial;"&gt;1) "I don't think it's appropriate for Ex Libris to promote "El Commons" as part of an "Open-Platform Strategy" though - I think you should promote it as a service to the "Ex Libris community". There's a big difference between the two, and I believe Ex Libris are mis-using the word "open" in this context."&lt;br /&gt;&lt;br /&gt;2) I'd "expect that there would be a system where developers, would be able to at least view other developer contributions and either:&lt;br /&gt;- submit details about resources for which they would like Ex Libris to provide adaptors&lt;br /&gt;- provide plugin documentation to create suitable adaptors themselves (if they have "Documentation Center log in details")"&lt;/blockquote&gt;&lt;span style="font-family:arial;"&gt;This was following on from an October 2008 post on a Talis blog [ &lt;/span&gt;&lt;a style="font-family: arial;" href="http://blogs.talis.com/panlibus/archives/2008/10/come-on-in-its-open-with-your-ex-libris-key.php" target="_blank"&gt;http://blogs.talis.com/panlibus/archives/2008/10/come-on-in-its-open-with-your-ex-libris-key.php&lt;/a&gt;&lt;span style="font-family:arial;"&gt; ], which ended on the note that:&lt;/span&gt;&lt;br /&gt;&lt;blockquote&gt;Well El Commons is up running and accessible at &lt;a href="http://www.exlibrisgroup.org/" target="_blank"&gt;http://www.exlibrisgroup.org&lt;/a&gt;.  Unfortunately as Oren hinted, you can only enter the commons with your  Ex Libris Documentation Center or SupportWeb user name and password – a bit of a misuse of the generally understood idea behind a commons methinks.&lt;/blockquote&gt;&lt;br /&gt;&lt;span style="font-family:arial;"&gt;What I didn't manage to convey in the last email I sent, (partly because I got bored with them not biting back, and never finished my very last email), was the fact that I thought Ex Libris  was overlooking another important information resource - Librarian-developed/enhanced resources.&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-family:arial;"&gt;[more about this later...]&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8030521401785829981-6291609876526866007?l=tompasley.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TomPasley-misc/~4/AMF5qgu-Xnw" height="1" width="1"/&gt;</description><app:edited xmlns:app="http://www.w3.org/2007/app">2009-05-06T16:39:31.655+12:00</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">2</thr:total><feedburner:origLink>http://tompasley.blogspot.com/2009/05/picking-fights-with-giants_06.html</feedburner:origLink></item><item><title>NTS:: CrossRef alternatives</title><link>http://feedproxy.google.com/~r/TomPasley-misc/~3/QTDAneVgbNU/nts-crossref-alternatives.html</link><category>crossref</category><category>doi</category><category>openurl resolver</category><category>openurl</category><author>tom.pasley@gmail.com (Tom Pasley)</author><pubDate>Sun, 03 May 2009 17:31:08 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8030521401785829981.post-4280737415918398801</guid><description>CrossRef provide a great service with their DOI/OpenURL resolver. There are times however, (esp. since their service was not designed to be a real-time service), goes down, or is unreachable from our network (at work).&lt;br /&gt;&lt;br /&gt;Thankfully, you are able to cache the data, as Chuck Koscher recently &lt;a href="http://bibwild.wordpress.com/2009/04/20/the-dangers-of-the-free-cloud-the-case-of-crossref/#comment-4246"&gt;commented&lt;/a&gt; - but what about alternative services? &lt;br /&gt;&lt;br /&gt;PubMed is good for recent articles, and other services (such as Web of Science, etc.) are probably no better, unless they have also happen to be able to access the CrossRef OAI-PMH service. You can probably do this search with other NLM databases too.&lt;br /&gt;&lt;br /&gt;Example PubMed search:&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.ncbi.nlm.nih.gov/sites/entrez?EntrezSystem2.PEntrez.Pubmed.Pubmed_SearchBar.Db=pubmed&amp;EntrezSystem2.PEntrez.Pubmed.Pubmed_SearchBar.Term=10.1002%2Fjmv.21494+%5Baid%5D"&gt;10.1002/jmv.21494 [aid]&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;The [aid] is, predictably, the "article identifiers submitted by journal publishers such as doi (digital object identifier). These data are typically used for generating LinkOut links." These include PIIs (Publisher's Item Identifiers), used by Elsevier (and some other publishers). This search can be used as part of a PHP script, such as &lt;a href="http://hublog.hubmed.org/archives/001762.html"&gt;Alf Eaton's&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;On a related note, PMC ids are also appearing in PubMed XML - to link to PubMedCentral with:&lt;br /&gt;PubMedCentral ID (PMCID): &lt;a href="http://www.pubmedcentral.nih.gov/articlerender.fcgi?artid=239018"&gt;http://www.pubmedcentral.nih.gov/articlerender.fcgi?artid=239018&lt;/a&gt;&lt;br /&gt;PubMed ID (PMID): &lt;a href="http://www.pubmedcentral.nih.gov/articlerender.fcgi?tool=pubmed&amp;pubmedid=2873788"&gt;http://www.pubmedcentral.nih.gov/articlerender.fcgi?tool=pubmed&amp;pubmedid=2873788&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8030521401785829981-4280737415918398801?l=tompasley.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TomPasley-misc/~4/QTDAneVgbNU" height="1" width="1"/&gt;</description><app:edited xmlns:app="http://www.w3.org/2007/app">2009-05-04T12:31:08.106+12:00</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://tompasley.blogspot.com/2009/05/nts-crossref-alternatives.html</feedburner:origLink></item><item><title>Cowtrails and standards</title><link>http://feedproxy.google.com/~r/TomPasley-misc/~3/HufeDeZmbk4/cowtrails-and-standards.html</link><category>standards</category><category>jeff young</category><category>openurl</category><author>tom.pasley@gmail.com (Tom Pasley)</author><pubDate>Mon, 27 Apr 2009 11:28:46 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8030521401785829981.post-2819928936855270131</guid><description>Comparing these two, the first thing you'd notice is that cowtrails are easier to follow... while standards give a sound base.&lt;br /&gt;&lt;br /&gt;If you have to implement a service which conforms to a standard though, you need to have something readable, and standards, while normally explicit, don't necessarily go into much detail about the philosophy or thought processes behind them. I suppose there's the expectation that, if you're reading this standard, you're already "there".&lt;br /&gt;&lt;br /&gt;I'm not sure about anyone else, but I found, despite comments like "you don't want to know WTF we were thinking" that getting some idea of these thought processes was useful. Admittedly, my experience is limited, and I've heard various comments about the Z39.88-2004 being over-engineered... but once I saw some of the stuff by Jeff Young on his &lt;a href="http://q6.oclc.org/"&gt;Q6 blog&lt;/a&gt;, OpenURL 1.0 made sense.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8030521401785829981-2819928936855270131?l=tompasley.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TomPasley-misc/~4/HufeDeZmbk4" height="1" width="1"/&gt;</description><app:edited xmlns:app="http://www.w3.org/2007/app">2009-04-28T06:28:46.307+12:00</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://tompasley.blogspot.com/2009/04/cowtrails-and-standards.html</feedburner:origLink></item><item><title>Naughty, naughty gateway!</title><link>http://feedproxy.google.com/~r/TomPasley-misc/~3/md5kqBxfg4Y/naughty-naughty-gateway.html</link><category>crossref</category><category>http error 502</category><author>tom.pasley@gmail.com (Tom Pasley)</author><pubDate>Mon, 20 Apr 2009 21:04:37 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8030521401785829981.post-8263757466975656519</guid><description>Not just me!&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_pYH7AU916_w/Se1FsoBShEI/AAAAAAAAAAk/22vdQgRBdF0/s1600-h/crossref.PNG"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer; width: 320px; height: 124px;" src="http://4.bp.blogspot.com/_pYH7AU916_w/Se1FsoBShEI/AAAAAAAAAAk/22vdQgRBdF0/s320/crossref.PNG" alt="" id="BLOGGER_PHOTO_ID_5326990567208551490" border="0" /&gt;&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8030521401785829981-8263757466975656519?l=tompasley.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TomPasley-misc/~4/md5kqBxfg4Y" height="1" width="1"/&gt;</description><app:edited xmlns:app="http://www.w3.org/2007/app">2009-04-21T16:04:37.062+12:00</app:edited><media:thumbnail url="http://4.bp.blogspot.com/_pYH7AU916_w/Se1FsoBShEI/AAAAAAAAAAk/22vdQgRBdF0/s72-c/crossref.PNG" height="72" width="72" /><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://tompasley.blogspot.com/2009/04/naughty-naughty-gateway.html</feedburner:origLink></item><item><title>Cow trails and standards (prelude)</title><link>http://feedproxy.google.com/~r/TomPasley-misc/~3/XlbGzgy9Huw/cow-trails-and-standards-prelude.html</link><category>peter keane</category><category>standards</category><category>oai-pmh</category><category>newsgroups</category><category>twitter</category><category>oai-ore</category><category>roderic page</category><author>tom.pasley@gmail.com (Tom Pasley)</author><pubDate>Mon, 20 Apr 2009 11:23:17 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8030521401785829981.post-4450854036625212467</guid><description>Just when I'm getting my head around something, I hear that what I've learnt could quite likely be irrelevant... such as OAI-PMH (OAI-ORE) and this:&lt;br /&gt;&lt;br /&gt;&lt;blockquote&gt;&lt;/blockquote&gt;&lt;blockquote&gt;&lt;blockquote&gt;"I have little doubt that Atom, a more widely supported specification than OAI-PMH, could supplant OAI-PMH, and I think that would be a good thing.  Why?  Because we could begin to see a dismantling of the silos that hold “library” or “archive” material on the web and keep it distinct from all of the other great stuff on the web."&lt;br /&gt;&lt;a href="http://blogs.law.harvard.edu/pkeane/2008/06/26/oai-ore-atom/"&gt;http://blogs.law.harvard.edu/pkeane/2008/06/26/oai-ore-atom/&lt;/a&gt;&lt;/blockquote&gt;&lt;a href="http://blogs.law.harvard.edu/pkeane/2008/06/26/oai-ore-atom/"&gt;&lt;/a&gt;&lt;/blockquote&gt;&lt;br /&gt;Thankfully, &lt;a href="http://twitter.com/pkeane"&gt;@pkeane&lt;/a&gt; has promised an update on this... it's going to be interesting to see how our perceptions change over relatively short periods of time (there's always disruptive technology running amok somewhere).&lt;br /&gt;&lt;br /&gt;Also via twitter, (love the way you can talk to anyone - easier than on the street!It's a pity you only get to overhear some of the conversation though be nice to have more of the threading made obvious ala &lt;a href="http://en.wikipedia.org/wiki/NNTP"&gt;NNTP&lt;/a&gt;/&lt;a href="http://en.wikipedia.org/wiki/Newsgroup"&gt;newsgroups&lt;/a&gt;):&lt;br /&gt;&lt;br /&gt;&lt;a href="http://twitter.com/rdmpage"&gt;Roderic Page&lt;/a&gt; made the comment that "&lt;span class="status-body"&gt;&lt;span class="entry-content"&gt;&lt;a href="http://twitter.com/rdmpage/statuses/1535036823"&gt;Trick is to have people use it, so that the links get out in the wild&lt;/a&gt;"&lt;/span&gt;&lt;/span&gt; - I'm not sure exactly what this was referring to, but it made me think about standards and cow trails... (now I just need to untangle my thoughts about this...).&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8030521401785829981-4450854036625212467?l=tompasley.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TomPasley-misc/~4/XlbGzgy9Huw" height="1" width="1"/&gt;</description><app:edited xmlns:app="http://www.w3.org/2007/app">2009-04-21T06:23:17.577+12:00</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://tompasley.blogspot.com/2009/04/cow-trails-and-standards-prelude.html</feedburner:origLink></item><item><title>twitter (bye, facebook)</title><link>http://feedproxy.google.com/~r/TomPasley-misc/~3/OoD2IQNuU3I/twitter-bye-facebook.html</link><category>social networking</category><category>facebook</category><category>twitter</category><author>tom.pasley@gmail.com (Tom Pasley)</author><pubDate>Mon, 13 Apr 2009 16:37:27 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8030521401785829981.post-7792914511800012374</guid><description>You can now reach me at &lt;a href="http://search.twitter.com/search?q=%40tompasley"&gt;@tompasley&lt;/a&gt; on twitter.&lt;br /&gt;&lt;br /&gt;I've ditched facebook, so although I decided to leave the option for people to still tag me on photos, etc., my &lt;a href="http://www.facebook.com/tompasley"&gt;facebook account has gone&lt;/a&gt;. Why? I wasn't checking/visiting it often enough, let alone making any postings... I was pretty much cyber-squatting. I've since discovered friendfeed, which was a bit thick (duh), but somehow, I don't think that would've made enough of a difference.&lt;br /&gt;&lt;br /&gt;Ultimately, I feel the concept of friends on facebook is artificial and flawed. I prefer the default of twitter, (though I reserve the right to change my mind!), which lets you communicate with anyone, and block those you don't want to to hear from... it's up to those twittering to say something worthwhile.&lt;br /&gt;&lt;br /&gt;This way, I can approach people, who do some cool stuff, and if they don't want to hear from me, then they can just ignore me or block me, rather than have to jump through some hoops first, and without having to worry about their email addresses, etc.&lt;br /&gt;&lt;br /&gt;Nice.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8030521401785829981-7792914511800012374?l=tompasley.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TomPasley-misc/~4/OoD2IQNuU3I" height="1" width="1"/&gt;</description><app:edited xmlns:app="http://www.w3.org/2007/app">2009-04-14T11:37:27.945+12:00</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://tompasley.blogspot.com/2009/04/twitter-bye-facebook.html</feedburner:origLink></item><item><title>NTS:: Metadata sources</title><link>http://feedproxy.google.com/~r/TomPasley-misc/~3/sSVmCRvIZaE/nts-metadata-sources.html</link><category>biodiversity heritage library</category><category>citeulike</category><category>metadata</category><category>nzetc</category><author>tom.pasley@gmail.com (Tom Pasley)</author><pubDate>Fri, 27 Mar 2009 12:52:34 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8030521401785829981.post-6520216417383810950</guid><description>More sources of article metadata:&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.citeulike.org/faq/data.adp"&gt;citeulike&lt;/a&gt;&lt;br /&gt;This data is useful because it groups related ids for each "view" of a resource (e.g. PMID &amp;amp; DOI for the same article). "&lt;br /&gt;Article linkout data Mapping CiteULike article_ids to resources on the web can be done with the linkout table.&lt;br /&gt;"The current snapshot is available at http://static.citeulike.org/data/linkouts.bz2 Data is available from 2008-02-02 onwards."&lt;br /&gt;"To understand the data in this file, you should refer to "The linkout formatter" section of the plugin developer's guide. This file contains a number of spam links. Although CiteULike filters spam postings, traces of the spam still remain in this table. In time this spam content will eventually be removed. The file is a simple unix ("\n" line endings) text file with pipe ("|") delimiters. Literal pipes within the fields are represented escaped ("\|"). The columns are: 1. Article Id 2. Linkout type 3. ikey_1 4. ckey_1 5. ikey_2 6. ckey_2&lt;br /&gt;NB If an article has n linkouts, then this will result in n rows in the file."&lt;br /&gt;&lt;br /&gt;&lt;a href="http://biodiversitylibrary.blogspot.com/2009/03/updates-to-bhl-exports-now-include-lcsh.html"&gt;BiodiversityHeritageLibrary&lt;/a&gt;&lt;br /&gt;150mb download, but most likely worth it&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.nzetc.org/tei-source/Bio07Tuat03.xml"&gt;NZETC&lt;/a&gt; (New Zealand Electronic Text Center)&lt;br /&gt;Some solid work, indexed by Index New Zealand, so can use Z39.50 to grab the data from INNZ. I'd like to see what can be done with the TEI-XML too.&lt;br /&gt;&lt;br /&gt;NCBI&lt;br /&gt;Worth listing for the version 2 of their &lt;a href="http://eutils.ncbi.nlm.nih.gov/entrez/query/static/esoap_help.html"&gt;wonderful web services&lt;/a&gt;.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8030521401785829981-6520216417383810950?l=tompasley.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TomPasley-misc/~4/sSVmCRvIZaE" height="1" width="1"/&gt;</description><app:edited xmlns:app="http://www.w3.org/2007/app">2009-03-28T08:52:34.576+13:00</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://tompasley.blogspot.com/2009/03/nts-metadata-sources.html</feedburner:origLink></item><item><title>twitter</title><link>http://feedproxy.google.com/~r/TomPasley-misc/~3/XXANr4cfSCE/twitter.html</link><category>social networking</category><category>delicious</category><category>blogging</category><category>twitter</category><author>tom.pasley@gmail.com (Tom Pasley)</author><pubDate>Fri, 27 Mar 2009 12:41:09 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8030521401785829981.post-2795405257035527674</guid><description>&lt;span style="font-family: arial;"&gt;Hi, I'm Tom, and I'm not on twitter.. yet.&lt;br /&gt;&lt;br /&gt;Twitter might be a great medium, but I find &lt;a href="http://delicious.com/Tom.Pasley"&gt;delicious&lt;/a&gt; is good enough for my purposes at the moment for my form of microblogging... &lt;br /&gt;&lt;br /&gt;I suppose I'm still in 'broadcast mode', though I'll probably get there originally.&lt;br /&gt;&lt;br /&gt;As &lt;a href="http://jimayson.wordpress.com/2008/04/29/john-c-dvorak-capitulates-joins-then-dominates-twitter/"&gt;John C. Dvorak&lt;/a&gt; points out, there are a number of &lt;a href="http://www.pcmag.com/article2/0,2817,2343672,00.asp"&gt;applications&lt;/a&gt; for twitter, and look how he turned 360!&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8030521401785829981-2795405257035527674?l=tompasley.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TomPasley-misc/~4/XXANr4cfSCE" height="1" width="1"/&gt;</description><app:edited xmlns:app="http://www.w3.org/2007/app">2009-03-28T08:41:09.113+13:00</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://tompasley.blogspot.com/2009/03/twitter.html</feedburner:origLink></item><item><title>tivo coming (to New Zealand) finally</title><link>http://feedproxy.google.com/~r/TomPasley-misc/~3/6AjLJaFpkEE/tivo-coming-to-new-zealand-finally.html</link><category>tivo</category><category>tv</category><category>television</category><category>tvnz</category><author>tom.pasley@gmail.com (Tom Pasley)</author><pubDate>Fri, 27 Mar 2009 12:23:19 PDT</pubDate><guid isPermaLink="false">tag:blogger.com,1999:blog-8030521401785829981.post-5371250745600804141</guid><description>&lt;span style="font-family: arial;"&gt;Well, we've all seen the ads on our regular tv channels in New Zealand, but it's still going to be a while before we see the &lt;/span&gt;&lt;a style="font-family: arial;" href="http://delicious.com/Tom.Pasley/tivo"&gt;tivo&lt;/a&gt;&lt;span style="font-family: arial;"&gt; here in New Zealand.&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-family: arial;"&gt;In Australia, there were problems with the pricing for the networking add-on, something TVNZ hopefully has learned, although if you're looking at wireless, it sounds a definite maybe: "Availability of TiVo &lt;/span&gt;&lt;span style="font-style: italic; font-family: arial;"&gt;complementary&lt;/span&gt;&lt;span style="font-family: arial;"&gt; products will be confirmed closer to launch."&lt;br /&gt;&lt;br /&gt;It sounds like a nice option to buy the unit outright, but in the meantime, there's some &lt;a href="http://delicious.com/Tom.Pasley/tivo_alternative"&gt;tivo alternatives&lt;/a&gt;, which might be worth considering... although it's hard to make comparisons when the final price for the tivo unit has not been established.&lt;br /&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/8030521401785829981-5371250745600804141?l=tompasley.blogspot.com' alt='' /&gt;&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/TomPasley-misc/~4/6AjLJaFpkEE" height="1" width="1"/&gt;</description><app:edited xmlns:app="http://www.w3.org/2007/app">2009-03-28T08:23:19.941+13:00</app:edited><thr:total xmlns:thr="http://purl.org/syndication/thread/1.0">0</thr:total><feedburner:origLink>http://tompasley.blogspot.com/2009/03/tivo-coming-to-new-zealand-finally.html</feedburner:origLink></item><copyright>Attribution-Noncommercial-Share Alike 3.0 Unported [ http://creativecommons.org/licenses/by-nc-sa/3.0/ ]</copyright><media:credit role="author">Tom Pasley</media:credit><media:rating>nonadult</media:rating></channel></rss>

