LISTSERV mailing list manager LISTSERV 16.0

Help for ZNG Archives


ZNG Archives

ZNG Archives


[email protected]


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

ZNG Home

ZNG Home

ZNG  June 2002

ZNG June 2002

Subject:

Re: SRW Statuses

From:

Janifer Gatenby <[log in to unmask]>

Reply-To:

Z39.50 Next-Generation Initiative

Date:

Tue, 11 Jun 2002 16:38:43 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (97 lines)

I agree too. I don't really like partial success and don't see it is needed
if there are surrogate diagnostics. Success should mean that the search was
successfully performed even if the result count is zero.

I would also like to see sort as an option within CQL, not a separate
service.

Janifer

-----Original Message-----
From: LeVan,Ralph [mailto:[log in to unmask]]
Sent: Tuesday, 11 June 2002 15:59
To: [log in to unmask]
Subject: Re: SRW Statuses


I've got no problem with that.

Ralph

> -----Original Message-----
> From: Matthew Dovey [mailto:[log in to unmask]]
> Sent: Tuesday, June 11, 2002 5:35 AM
>
> But my view here is that we can simplify this by having a
> success/failed
> status and indicating the reason (search failed, present failed - or
> something a little more meaningful for those not steeped in
> Z39.50 - or
> whatever). I'm not sure either way about the need for the partial
> success value.
>
>
>
> Matthew
>
>
> > -----Original Message-----
> > From: LeVan,Ralph [mailto:[log in to unmask]]
> > Sent: 10 June 2002 23:51
> > To: [log in to unmask]
> > Subject: Re: SRW Statuses
> >
> >
> > I like the idea of the three statuses: search, result set and
> > present. In fact, the result set info could be in the
> > statuses part of the response.
> >
> > I also like surrogate diagnostics. There are many reasons
> > why a record can't be returned and often the client/user does
> > care what that reason was.
> >
> > Ralph
> >
> > -----Original Message-----
> > From: Ray Denenberg [mailto:[log in to unmask]]
> > Sent: Monday, June 10, 2002 5:19 PM
> > To: [log in to unmask]
> > Subject: SRW Statuses
> >
> >
> > Just looking at the response schema at
> > http://www.loc.gov/z3950/agency/zing/rs1.xml
> > and must admit I
> > haven't looked at it closely for
> > awhile.
> >
> > I think the status part needs work.
> >
> > First: there is a single status, whose values are
> > : "0 - success 1 - partial success (some surrogate
> > diagnostics present in records structure) 2 -
> > failure"; similar to the Z39.50 present status.
> > There's no search status or result set status.
> > Remember that the srw service (loosely) models
> > the Z39.50 Search with piggyback response. That
> > has a search status, result set status, and
> > present status.
> >
> > Second: couldn't we dispose of the surrogate
> > diagnostic for srw? How about an element that
> > accompanies a record, telling which result set
> > record it is. Then if you get records 1, 3,4,5 you
> > know that 2 couldn't be returned, for some reason.
> > Do we need to bother with the reason? And that's
> > only for a persistent result set anyway; much of
> > the time the queries are going to be re-executed
> > in which case the surrogate diagnostic isn't very
> > meaningful.
> >
> > Could we do away with the status(es) altogether,
> > and just send diagnostics?
> >
> > --Ray
> >
>

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