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:

"O.Stephens" <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Tue, 15 Sep 2009 14:52:53 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (201 lines)

Thanks Rosalyn,

As you say we could push a custom value into rfr_genre. I'm a bit torn on this, as I guess I'm trying to do something that isn't 'hacky' - or at least not from the OpenURL end of it. It might be that this is just wishful thinking, and that I'm just trying to fool myself into thinking I'm 'sticking to the standard' when the likelihood of what I'm doing being transferrable to other scenarios is zero (although Eric's comments make me hope not)

Yes, we are using SFX. What I'm proposing on the SFX end as the path of least resisitance is writing a source parser for our learning environment which can do a 'fetch' for an alternative URL, or use the primary URL, and put it in an SFX internal field rft_856. We can then use the existing Target Parser 856_URL which displays the contents of rft_856 in the menu. Combined with some logic which forces this as the only option under certain circumstances we can then push the user directly to the resulting URL.

Owen

Owen Stephens
TELSTAR Project Manager
Library and Learning Resources Centre
The Open University
Walton Hall
Milton Keynes, MK7 6AA

T: +44 (0) 1908 858701
F: +44 (0) 1908 653571
E: [log in to unmask]


> -----Original Message-----
> From: Code for Libraries [mailto:[log in to unmask]] On
> Behalf Of Rosalyn Metz
> Sent: 15 September 2009 14:42
> To: [log in to unmask]
> Subject: Re: [CODE4LIB] Implementing OpenURL for simple web resources
>
> you could force a timestamp if people don't include a date.
>
> and I like the idea of going to the Internet Archive of a
> website, because then you're not having to get into the
> business of handling www.bbc.co.uk differently than cnn.com
> and someblog.org.
>
> i also like the idea of using a redirect.  you could
> theoretically write a source parser (i'm assuming youre using
> SFX based on what you said about bX) that says if my rfr_id =
> mylocalid and the item is a website (however you choose to
> identify the website...which if you're writing your own
> source parser you could put website in the rft_genre even
> though its not technically a metadata format but you just
> want your source parser to forward the url on anyway, so the
> link resolver isn't actually going to do anything with it)
> bypass everything and just direct to the internet archive of
> the website.
>
> all of this is of course kind of hackish...but really isn't
> the whole thing hackish?  there were a few source parsers
> that would be good models for writing something like this.
> but i have no idea if they still exist because i haven't
> looked at the back end of sfx in about a year.
>
>
>
>
> On Tue, Sep 15, 2009 at 5:12 AM, O.Stephens
> <[log in to unmask]> wrote:
> > I agree with this Rosalyn. The issue that Nate brought up
> was that the content at http://www.bbc.co.uk could change
> over time, and old content might be moved to another URI -
> http://archive.bbc.co.uk or something. So if course A
> references http://www.bbc.co.uk on 24/08/09, if the content
> that was on http://www.bbc.co.uk on 24/08/09 moves to
> http://archive.bbc.co.uk we can use the mechanism I propose
> to trap the links to http://www.bbc.co.uk and redirect to
> http://archive.bbc.co.uk. However, if at a later date course
> B references http://www.bbc.co.uk we have no way of knowing
> whether they mean the stuff that is currently on
> http://www.bbc.co.uk or the stuff that used to be on
> http://www.bbc.co.uk and is now on http://archive.bbc.co.uk -
> and we have a redirect that is being applied across the board.
> >
> > Thinking about it, references are required to include a
> date of access when citing websites, so this is probably the
> best piece of information to use to know where to resolve to
> (and we can put this in the DC metadata). Whether this will
> just get too confusing is a good question - I'll have at
> think about this.
> >
> > Owen
> >
> > PS using the date we could even consider resolving to the
> Internet Archive copy of a website if it was available I
> guess - this might be useful I guess...
> >
> > Owen Stephens
> > TELSTAR Project Manager
> > Library and Learning Resources Centre
> > The Open University
> > Walton Hall
> > Milton Keynes, MK7 6AA
> >
> > T: +44 (0) 1908 858701
> > F: +44 (0) 1908 653571
> > E: [log in to unmask]
> >
> >
> >> -----Original Message-----
> >> From: Code for Libraries [mailto:[log in to unmask]]
> On Behalf
> >> Of Rosalyn Metz
> >> Sent: 14 September 2009 21:52
> >> To: [log in to unmask]
> >> Subject: Re: [CODE4LIB] Implementing OpenURL for simple
> web resources
> >>
> >> oops...just re-read original post s/professor/article
> >>
> >> also your link resolver should be creating a context
> object with each
> >> request.  this context object is what makes the openurl
> unique.  so
> >> if you want uniqueness for stats purposes i would image the link
> >> resolver is already doing that (and just another reason to use an
> >> rfr_id that you create).
> >>
> >>
> >>
> >>
> >> On Mon, Sep 14, 2009 at 4:45 PM, Rosalyn Metz
> <[log in to unmask]>
> >> wrote:
> >> > Owen,
> >> >
> >> > rft_id isn't really meant to be a unique identifier
> >> (although it can
> >> > be in situations like a pmid or doi).  are you looking
> for it to be?
> >> > if so why?
> >> >
> >> > if professor A is pointing to http://www.bbc.co.uk and
> >> professor B is
> >> > pointing to http://www.bbc.co.uk why do they have to have unique
> >> > OpenURLs.
> >> >
> >> > Rosalyn
> >> >
> >> >
> >> >
> >> >
> >> > On Mon, Sep 14, 2009 at 4:41 PM, Eric Hellman
> >> <[log in to unmask]> wrote:
> >> >> Nate's point is what I was thinking about in this comment in my
> >> >> original
> >> >> reply:
> >> >> If you don't add DC metadata, which seems like a good
> idea, you'll
> >> >> definitely want to include something that will help you
> to persist
> >> >> your replacement record. For example, a label or
> >> description for the link.
> >> >>
> >> >> I should also point out a solution that could work for
> some people
> >> >> but not
> >> >> you- put rewrite rules in the gateways serving your
> network. A bit
> >> >> dangerous and kludgy, but we've seen kludgier things.
> >> >>
> >> >> On Sep 14, 2009, at 4:24 PM, O.Stephens wrote:
> >> >>>
> >> >>> Nate has a point here - what if we end up with a commonly
> >> used URI
> >> >>> pointing at a variety of different things over time, and
> >> so is used
> >> >>> to indicate different content each time. However the
> >> problem with a 'short URL'
> >> >>> solution (tr.im, purl etc), or indeed any locally assigned
> >> >>> identifier that acts as a key, is that as described in
> >> the blog post
> >> >>> you need prior knowledge of the short URL/identifier to
> >> use it. The
> >> >>> only 'identifier' our authors know for a website is it's
> >> URL - and
> >> >>> it seems contrary for us to ask them to use something
> else. I'll
> >> >>> need to think about Nate's point - is this common or an
> >> edge case? Is there any other approach we could take?
> >> >>>
> >> >>
> >> >> Eric Hellman
> >> >> President, Gluejar, Inc.
> >> >> 41 Watchung Plaza, #132
> >> >> Montclair, NJ 07042
> >> >> USA
> >> >>
> >> >> [log in to unmask]
> >> >> http://go-to-hellman.blogspot.com/
> >> >>
> >> >
> >>
> >
> >
> > The Open University is incorporated by Royal Charter (RC
> 000391), an exempt charity in England & Wales and a charity
> registered in Scotland (SC 038302).
> >
>


The Open University is incorporated by Royal Charter (RC 000391), an exempt charity in England & Wales and a charity registered in Scotland (SC 038302).

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

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