Date:         Fri, 8 Oct 2004 14:23:27 -0400
Reply-To:     "Z39.50 Next-Generation Initiative" <[log in to unmask]>
Sender:       "Z39.50 Next-Generation Initiative" <[log in to unmask]>
From:         "LeVan,Ralph" <[log in to unmask]>
Subject:      Re: Requesting summary counts
Comments: To: "Z39.50 Next-Generation Initiative" <[log in to unmask]>
Content-Type: text/plain

That looks like result set metadata.  It would have to go in
extraResponseData, which means that you'd need to include something in your
request that triggered it in the response.

Ralph

> -----Original Message-----
> From: Ray Denenberg [mailto:[log in to unmask]]
> Sent: Friday, October 08, 2004 2:09 PM
> To: [log in to unmask]
> Subject: Fw: Requesting summary counts
>
> This is from Janifer Gatenby who had touble posting it.
>
> ----- Original Message -----
> From: "Janifer Gatenby" <[log in to unmask]>
> To: "'Z39.50 Next-Generation Initiative'" <[log in to unmask]>
> Sent: Friday, October 08, 2004 11:51 AM
> Subject: Requesting summary counts
>
>
> > In an SRU request, we want the ability to request a report rather than a
> > result set itself.  The server would sort the result set by a specified
> > criteria and give a summary counts in a report. E.g.
> >
> > 2003    15 hits
> > 2002    8 hits
> > 2001    16 hits
> > etc.
> >
> > What would be the recommended way to do this - via a specific record
> schema
> > for summary counts?
> >
> > Thanks in advance for your help,
> >
> > Janifer
> >   _____
> >
> > OCLC|PICA Please note the change of my e-mail address!
> >   _____
> >
> > J.L. Gatenby
> > Product Management
> > Schipholweg 99 | 2316 XA Leiden | The Netherlands
> > tel. +31 71 524 65 16 | mobile +31 6 4852 3006 | fax +31 71 522 31 19
> > e-mail [log in to unmask] <mailto:[log in to unmask]>  |
> website:
> > http://www.oclcpica.org <http://www.oclcpica.org/>
> >
> >
> >
> >
> > ________________________
> >
> > The information in this electronic mail message is private and may be
> > confidential. It is intended solely for the use of the recipient. Should
> you
> > receive this message by mistake, you are hereby notified that any
> > disclosure, reproduction, distribution or use of this message is
> prohibited.
> > Please delete this message and notify the sender immediately by return
> > email. OCLC PICA accepts no liability for the improper transmission of
> > information contained in this communication nor for any delay in its
> > receipt. Although we have taken steps to ensure that this email and
> > attachments are free from any virus, we do advise you to scan
> attachments
> > before opening them.
> >
> >