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  March 2008

ZNG March 2008

Subject:

Re: Price information in SRU responses

From:

Yakov Shafranovich <[log in to unmask]>

Reply-To:

SRU (Search and Retrieve Via URL) Implementors

Date:

Fri, 28 Mar 2008 12:07:20 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (140 lines)

Perhaps in this specific case it would make more sense to use the ONIX
scheme? My fear is that most SRU implementations use MARC, MODS or DC
and ONIX is not as widely supported.

Yakov

On 3/28/08, Theo van Veen <[log in to unmask]> wrote:
>
>
>
>
> How many extra recordData fields will we have in the end? Users make use of
> a client. Clients can be smart enough to deal with unknown fields (alert the
> user or whatever). But users do not know that there are extra fields and
> clients will not request for all available extra fields because clients do
> not understand the semantics. Users do.
>
> The extension mechanism heavily relies on bilateral agreements and a priori
> knowledge and raises the barrier for users to get extra information that is
> useful and available.
>
>
>
> Theo
>
>
>
>  ________________________________
>
>
> Van: SRU (Search and Retrieve Via URL) Implementors [mailto:[log in to unmask]]
> Namens Janifer Gatenby
>  Verzonden: vrijdag 28 maart 2008 16:31
>  Aan: [log in to unmask]
>  Onderwerp: Re: Price information in SRU responses
>
>
>
>
> You can use extraRecordData to include price with any other resource
> description scheme. According to SRU, the client must know that you provide
> price as extraRecordData and must request it else you may not send it.
>
> See:
> http://www.loc.gov/standards/sru/specs/common.html#extraData
>
> Janifer Gatenby
>
> Research integration and standards  OCLC B.V.
>
> Schipholweg 99  P.O. Box 876  2300 AW Leiden  The Netherlands t +31 71
> 524 6516  m +31 6 1710 2867  f +31 71 522 31 19 e [log in to unmask]
>  w www.oclc.org
>  ________________________________
>
>
> From: SRU (Search and Retrieve Via URL) Implementors [mailto:[log in to unmask]] On
> Behalf Of Ray Denenberg
>  Sent: 28 March 2008 16:19
>  To: [log in to unmask]
>  Subject: Re: Price information in SRU responses
>
>
>
> Sorry Mike but you can't do that.
>
>
>
>
>
> Not if we're talking about the DC schema at:
>  http://www.loc.gov/standards/sru/resources/dc-schema.xsd
>
>  There is no provision in that schema for non-dc elements.
>
>
>
>
>
> (We could issue another version of the DC schema to allow this, and if
> someone thinks it's a good idea I'll draft it.)
>
>
>
>
>
> --Ray
>
>
>
> ----- Original Message -----
>
>
> From: Mike Taylor
>
>
> To: [log in to unmask]
>
>
> Sent: Friday, March 28, 2008 11:01 AM
>
>
> Subject: Price information in SRU responses
>
>
>
>
> Yakov Shafranovich writes:
>   > I am working on a SRU gateway for a book publisher. One of the
>   > things I have run into is that there is no way to pass pricing
>   > information in SRU without using the ONIX scheme. Is there a way to
>   > embed pricing information in SRU responses using other schemes?
>
>  Hi, Yakov.  Sure, you can embed whatever information you want in
>  records transferred via SRU, just as you can with any other XML
>  document.  Just add the elements you want wherever they make most
>  sense in the record, and be sure to put them in a namespace other than
>  that of the standardised part of the record.  For example:
>
>  <dc:record xmlns:dc='http://purl.org/dc/elements/1.1/'
> xmlns:mike='...'>
>    <dc:identifier>12345</dc:identifier>
>    <dc:creator>Hillare Belloc</mike:remitter>
>    <dc:title>Poems for Bad Children</dc:title>
>    <mike:price>5.99</mike:price>
>  </request>
>
>  The problem is: how do you get the client application to recognise and
>  understand the extra information you've added?  To make that work, you
>  need an agreement between server and client about the format of the
>  records -- in other words, the client needs to know that it will not
>  just be getting DC records, but DC-extended-with-mike:price records.
>
>   _/|_
> ___________________________________________________________________
>  /o ) \/  Mike Taylor    <[log in to unmask]>
> http://www.miketaylor.org.uk
>  )_v__/\  "A Linux system requires rebooting about as often as a Windoze
>  system requires re-installing" -- David Joffe.

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