Hi Christophe!

I thought you were working on the SOLR interface to SRU?  I'm sorry that
hasn't worked out.

I think it is appropriate to support language specific elements in an
SRU response.  The simplest way to make this happen is to have your
server take advantage of the HTTP Accept-Language header.  But, not all
clients can send HTTP headers and sometimes users want to request
languages other than those specified to their browser.  For that you
need an optional parameter to override/replace the HTTP header.

We've set the pattern for this behavior with our new httpAccept
parameter that is being used to support media-type negotiation.  Using
an httpAcceptLanguage parameter as an alternative to the Accept-Language
header should work as well for language.


> -----Original Message-----
> From: SRU (Search and Retrieve Via URL) Implementors
[mailto:[log in to unmask]]
> On Behalf Of Christophe Dupriez
> Sent: Friday, August 21, 2009 7:36 AM
> To: [log in to unmask]
> Subject: Generic SRU Server interface for SolR (or Lucene)?
> Hi!
> As I am looking to a design allowing (for instance) the European
Library to query
> a SolR index of bibliographic references, I am wondering if a
> module exists to do this!
> Another question: I worked a lot to integrate authority lists with
DSpace. This
> allows to store concept codes in a database and to index all its
translations and
> synonyms.
> This bring a problem: where the concept code has to be translated into
the user
> language?
> In the SRU response? Then the SRU request must specify the user
language (is
> it the case?) In the SRU client (or in the calling application)? Then
the client
> application will need the possibility to query the authority lists to
translate the
> concepts codes it encounters in the SRU query results.
> I will be happy to read your thoughts!
> Have a nice week-end!
> Christophe Dupriez
> P.S. The application I am working on (with authority lists) is
beginning its
> operations: SolR will be for a new