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  September 2009

CODE4LIB September 2009

Subject:

Re: Implementing OpenURL for simple web resources

From:

Jonathan Rochkind <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Mon, 14 Sep 2009 16:19:45 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (78 lines)

Of course it's possible.  But if you're counting on all (or a majority) 
of actually in-the-wild resolvers to do a certain thing, you should 
probably do some investigation to see if that assumption is true. Some 
probably do some probably don't. If the usefulness of your technique 
depends on most doing so, then you should check it.

And if the usefulness of your technique does NOT count on being 
inter-operable with existing link resolver infrastructure... PERSONALLY 
I would be using OpenURL, I don't think it's worth it.

Incidentally, I have been unhappy with the "pre-check a http URL before 
giving it to the user" technique. First of all, WAY too much stuff on 
the web still returns an HTTP 200 OK response message for what are in 
fact error pages (including MOST of our licensed scholarly content 
providers). Secondly, even if it's not an error page, there's no way for 
pre-checking to tell you WHAT the page has, what it represents and how 
useful it might be to the user. I don't think it serves the user well to 
say "Here's a URL that'll give you something related to this citation, 
click on it to find out what." I want to tell them if it's going to be 
full text, or just a description, or what.  As well as have the software 
be able to display it differently depending. I think that's important to 
making the service useful.

Jonathan

Eric Hellman wrote:
> I can't imagine that SFX has some fundamental assumption that  an http  
> URL in rft_id is never ever something that can be used for access, and  
> even if it did, it would be letting the tail wag the dog to suggest  
> that other resolvers should not do so; some do.
>
> There are also resolvers that pre-check urls, at least there were  
> before exlibris acquired linkfinderplus. So it's possible for a  
> resolver agent to discover whether a url leads somewhere or not.
>
>
> On Sep 14, 2009, at 2:23 PM, Jonathan Rochkind wrote:
>
>   
>> I disagree.   Putting URIs that unamiguously identify the referent,  
>> and in some cases provide additional 'hooks' by virtue of additional  
>> identifiers (local bibID, OCLCnum, LCCN, etc) is a VERY useful thing  
>> to do to me.  Whether or not they resolve to an end-user appropriate  
>> web page or not.
>>
>> If you want to use rft_id to instead be an end-user appropriate  
>> access URL (which may or may not be a suitable unambiguous  
>> persistent identifier), I guess it depends on how many of the  
>> actually existing in-the-wild link resolvers will, in what contexts,  
>> treat an http URI as an end-user appropriate access URL. If a lot of  
>> the in-the-wild link resolvers will, that may be a practically  
>> useful thing to do. Thus me asking if the one you had knowledge of  
>> did or didn't.
>>
>> I'm 99% sure that SFX will not, in any context, treat an rft_id as  
>> an appropriate end-user access URL.
>>
>> Certainly providing an appropriate end-user access URL _is_ a useful  
>> thing to do. So is providing an unambiguous persistent identifier.  
>> Both are quite useful things to do, they're just different things,  
>> shame that OpenURL kinda implies that you can use the same data  
>> element for both.  OpenURL's not alone there though, DC does the  
>> same thing.
>>
>> Jonathan
>>
>>     
>
> Eric Hellman
> President, Gluejar, Inc.
> 41 Watchung Plaza, #132
> Montclair, NJ 07042
> USA
>
> [log in to unmask]
> http://go-to-hellman.blogspot.com/
>
>   

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

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