Print

Print


Thank you, Ralph.

 

This is the URL I'm getting most of the info on SRU:

 

 

http://www.loc.gov/standards/sru/

 

Is there another one that might explain the diagnostics, and give more
details?

 

Thanks again!

 

  _____  

From: SRU (Search and Retrieve Via URL) Implementors [mailto:[log in to unmask]] On
Behalf Of LeVan,Ralph
Sent: Wednesday, February 08, 2006 4:18 PM
To: [log in to unmask]
Subject: Re: genreal question about implementation

 

Hi Jose!

 

No, you don't need to implement scan, but you do need to be prepared to get
a scan request and return the appropriate diagnostic
(info:srw/diagnostic/1/4).

 

There are plenty of diagnostics to allow you to explain why you didn't
process a particular query.  If you think you've got a case that isn't
covered by those diagnostics, let us know and we'll try to help you out.  In
addition, there are probably ways to say all those things in the Explain
record, but you can't count on the client reading them.

 

Hope this helps!

 

Ralph

 

  _____  

From: SRU (Search and Retrieve Via URL) Implementors [mailto:[log in to unmask]] On
Behalf Of Jose Blanco
Sent: Wednesday, February 08, 2006 3:49 PM
To: [log in to unmask]
Subject: genreal question about implementation

 

I'm working on implementing SRU, and I'm wondering if I need to implement
the scan operation to be SRU compliant.

 

Also, I realize that the possible queries coming from the searchRetrieve can
be quite complicated and long.  As an SRU gateway, do we have to be able to
support all possible CQL queries?  Are there standard error messages we
could use to indicate that the query can not be processed? Is there a way we
can let users know that we are only supporting certain Boolean operations
line "AND" and "OR", but say not "NOT", or "PROXIMITY".  And can we somehow
let users know that we will only search for a certain number of fields per
query

 

( A AND B AND C) is OK

 

But 

 

( A AND B AND C AND D) is not OK because it contains 4 fields and our limit
is 3.

 

Thank you!

 

Jose