‘Link Resolver’ understood as ‘OpenURL Service Provider’

Dan Chudnov envisions a scenario for using OpenURL to let a person carry their ‘services’ around with them from website to website, in an automatic way. At least that’s my interpretation of his scenario, I’m sure he or someone else will correct me if I’m mis-characterizing it.

That’s started me thinking in more detail about what the architecture needed to support this scenario would look like. I’m going to make a few posts about this, starting with this one investigating how we should think about the ‘link resolver’. (Note that I’m not sure if this is exactly what dchud was thinking just stated differently, or expands upon it, or even contradicts it! That’s why we write these things down, to tease out from each other what we mean and build shared mental models and vocabulary, right?)

So, what is a ‘link resolver’? Well, of course, it’s something that takes an OpenURL, which represents a bibliographic item and tells the user where he can get electronic access to the item. (And, yes, the OpenURL includes not just an item citation, but the ‘context’ of the request, but let’s face it, the item requested, the ‘referrent’, is the principle payload, and the main thing that ‘link resolvers’ act upon; in practice the extra stuff is just bonus). The very name ‘link resolver’ implies this scenario, but let’s consider an alternate more abstract understanding of the class of services our ‘link resolvers’ fit into. Continue reading “‘Link Resolver’ understood as ‘OpenURL Service Provider’”


Local indexing of scholarly articles

Richard Wallis of Talis posts on a project that impacts our fantasies of local indexing (rather than cross-search) for scholarly articles.

“By embedding Onix encoded journal article information in to a RSS 2.0 feed it was possible to build a process, capable of being automated, for those articles to be inserted in to a library catalogue without human intervention.”


Bibliographic Wilderness

So I finally get around to making a blog to write about library matters. Attending the Code4Lib conference was the final impetus. What a great conference. Nice to spend a week discussing with very smart people very interesting ideas about how to make libraries work better in the digital environment. The way we try to extend and grow this community is with communication, right? Less re-inventing of wheels and isolation, more synergy and collaboration. Not just on code, but sharing of analyses, plans and experiences, participation in public discourse to take our collective practice forward. So a blog is one way of doing that public communication (‘publishing’ is just a word for ‘public communication’, right? A blog may not be the best way to do it, but better than nothing).

Continue reading “Bibliographic Wilderness”