LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  December 2004

CODE4LIB December 2004

Subject:

Re: resolver list.

From:

Ben Soares <[log in to unmask]>

Reply-To:

Ben Soares <[log in to unmask]>

Date:

Thu, 9 Dec 2004 13:47:00 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (127 lines)

Hello,

In the UK we have a pilot service that provides a registry for
OpenURL resolvers, and also a "routing" service, hence the name
OpenURL Router.

Institutions can register their OpenURL resolvers - base URL,
preferred button image and "alt" text, and various identifiers (IP
address range and authentication scheme IDs).

Service providers can then perform a lookup on the registry.  For
instance, a user from Edinburgh University is likely to access most
services with the "Athens" authentication system (which associates
them with the institutional identifier "edu");  the service provider
can perform a lookup with this HTTP request:
   http://openurl.ac.uk/lookup/athens:edu
The XML response details the resolver (try it, the XML is readable).

The EDINA BIOSIS service uses this technique to provide OpenURL links
to whatever resolver the institution has entered in the registry.  No
librarians ever have to inform EDINA about their OpenURL Resolver,
and EDINA does not have to hold tables mapping customers to OpenURL
Resolvers:  as soon as a resolver is entered into the OpenURL Router
registry, links automatically appear in EDINA services.

The OpenURL Router can also provide a redirection service, which
allows people to offer an OpenURL like:
  http://openurl.ac.uk/redirect?genre=journal&title=Journal+of+Ecology

When an end user clicks on that link, the OpenURL Router figures out
their institution from their IP address and redirects the browser to
their local resolver.  If their IP address is unrecognised there are
tricks using Athens that may identify them; if absolutely necessary,
they are asked to pick from a list of institutions.   The last resort
if no matching institution with a resolver can be found is to provide
them with a choice of free access resolvers.

Apart from the obvious gain that it could save librarians informing
all their different service providers about their resolver, the
OpenURL Router enables OpenURL Links from services that have no login
procedures.  Suppose you have an open access bibliographic portal;
anyone can use the service, so you are unlikely to keep big tables of
IP address ranges to identify users (it takes time, costs money, why
would you?)   You could add OpenURL links to your service, except you
cannot tell what resolver to address them to.  The OpenURL Router
fixes this;  either you can do a registry lookup using the end users'
IP address, or just create a link with openurl.ac.uk as the base
URL.

The OpenURL Router is funded by JISC (http://www.jisc.ac.uk/).  There
is no charge for using the service, and access is not restricted,
though because the funding is derived from the Higher/Further
Education sector in the UK it cannot really be extended to cover
resolvers outwith the UK.  Full details at http://openurl.ac.uk/doc/.

Best wishes,

Ben Soares

On Tue, 07 December, 2004 20:44, Hickey,Thom wrote:
> Forwarding a message from the OpenWorldCat team:
>
>
>
> As part of the Open WorldCat program, OCLC will be piloting a registry
> of OpenURL resolvers.  We plan to investigate building on the more than
 1200 OpenURL resolvers currently registered within our administrative
> systems.  We are in the early design stages and would welcome
> recommendations.  Feel free to email directly to:
>
> Mike Teets, Exec. Dir. Product Architecture & Development, OCLC
> mailto:[log in to unmask]
>
>
>
> It looks like we'll be prototyping that here in Research, so we might
> have some data for Dan to play with.
>
>
>
> --Th
>
>
>
>
>
> -----Original Message-----
> From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of
> Daniel Chudnov
> Sent: Monday, December 06, 2004 6:55 PM
> To: [log in to unmask]
> Subject: [CODE4LIB] resolver list.
>
>
>
> For some stuff I'd like to try, and maybe for browser extension authors,
>
> among others, it would be helpful to have at least one public list of
>
> some public openurl resolvers.  If you like, if you might kindly add
>
> your resolver to the just-started list here:
>
>
>
>    http://curtis.med.yale.edu/unalog-trac/wiki/OpenurlResolverTable
>
>
>
> ...it would be very helpful.
>
>
>
> Or, if there's already a list like this elsewhere, please let me know.
>
>
>
> Thanks, -Dan

--
Ben Soares                                         tel: +44 (0)131-651 1238
EDINA, Edinburgh University Data Library           fax: +44 (0)131-650 3308
Main Library Building, George Square             email: [log in to unmask]
Edinburgh EH8 9LJ, Scotland, UK                    www: http://edina.ac.uk/

"Hmmm, that makes no sense to me...
 But then you are very small, perhaps you're right." -- Treebeard

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager