LISTSERV mailing list manager LISTSERV 16.0

Help for ZNG Archives


ZNG Archives

ZNG Archives


ZNG@C4VLPLISTSERV01.LOC.GOV


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

ZNG Home

ZNG Home

ZNG  June 2003

ZNG June 2003

Subject:

Re: Metaresponse

From:

"Matthew J. Dovey" <[log in to unmask]>

Reply-To:

Z39.50 Next-Generation Initiative

Date:

Tue, 3 Jun 2003 13:20:39 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (101 lines)

I've not followed all of turns and twists of this discussion, so here is my na´ve tuppence worth.

You can do this with SRW/SRU 1.0 as is!

You need the digital object servers to return appropriate persistent URLs (PURLS, Handles, OpenURLs etc.) which most do (and if they don't we can't solve that with SRW/SRU!!!). Your central server has to return a metadata format which includes these URLs (Mets, MarcXML, Mods, even DC return such a place holder for this sort of thing). Your client needs to know to follow these URLs for further information

You might want to write this up as an application profile/recommendation for this sort of application, but I can't see any changes to SRU/SRW needed to support this! 

The orthogonal question of whether it should be mandatory for any record to return a (SRW/SRU context) persistent id is probably better answered by considering whether there are any cases where this would not be applicable. My preference is that this sort of behaviour should be better in an application context/profile.

Matthew 

> 
> -----Original Message-----
> From: Oldroyd, Bill [mailto:[log in to unmask]] 
> Sent: Tuesday, June 03, 2003 12:36 PM
> To: [log in to unmask]
> 
> Mike,
> 
> Say I have 20 different systems serving digital objects.
> 
> There is a single server indexing these 20 systems, say by crawling or
> harvesting. The server provides a search interface.
> 
> The user performs a search against the search server. The records are
> retrieved from the digial object servers.
> 
> Why would you want to do this ?. Answer - because if you 
> could do it, it
> might allow one to design systems in a different way.
> 
> Bill
> 
> -----Original Message-----
> From: Mike Taylor
> To: [log in to unmask]
> Sent: 02/06/03 12:24
> Subject: Re: Metaresponse
> 
> > Date: Mon, 2 Jun 2003 09:55:09 +0100
> > From: "Oldroyd, Bill" <[log in to unmask]>
> >
> > > >   http://srw.o-r-g.org:8080/database/?query=rec.id 
> exact "ident1"
> >
> > > Exactly.
> >
> > This could be a unique, persistent URI, but I was asking that any
> > URI could be used to identify the record, not one requiring a stem
> > of the database and command.
> 
> Hi Bill.  I'm struggling to understand what difference this makes to
> anything -- perhaps you could help us with a usage scenario?
> 
> Thanks,
> 
>  _/|_    
> _______________________________________________________________
> /o ) \/  Mike Taylor  <[log in to unmask]>  
> http://www.miketaylor.org.uk
> )_v__/\  "Computers in the future may weigh no more than 1.5 tons"
>          -- Popular Mechanics, 1949.
> 
> --
> Listen to my wife's new CD of kids' music, _Child's Play_, at
>         http://www.pipedreaming.org.uk/childsplay/
> 
> 
> **************************************************************
> ************
> 
> Now exhibiting at the British Library Galleries:
> 
> Painted Labyrinth : the world of the Lindisfarne Gospels
> 
> Until 28 September 2003.  Admission Free.
> 
> **************************************************************
> ***********
> 
> The information contained in this e-mail is confidential and 
> may be legally
> privileged. It is intended for the addressee(s) only. If you 
> are not the
> intended recipient, please delete this e-mail and notify the
> [log in to unmask] : The contents of this e-mail must not be 
> disclosed or
> copied without the sender's consent.
> 
> The statements and opinions expressed in this message are those of the
> author and do not necessarily reflect those of the British 
> Library. The
> British Library does not take any responsibility for the views of the
> author.
> 
> **************************************************************
> ***********
> 
> 

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

July 2017
October 2016
July 2016
August 2014
February 2014
December 2013
November 2013
October 2013
February 2013
January 2013
October 2012
August 2012
April 2012
January 2012
October 2011
May 2011
April 2011
November 2010
October 2010
September 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
October 2009
September 2009
August 2009
July 2009
May 2009
April 2009
March 2009
February 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
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
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager