The Lucene issue requires that the responsePosition be 1 instead of 10.
That means your seed term must be the first term in the response and
that you can't go backwards through the index. That was the same
limitation in DSpace 1.4.
The getTermList() method in the SRWLuceneDatabase class needs to be
updated. It should look like familiar DSpace code. I just couldn't
figure out how to use the new API and couldn't find the equivalent
client code in the DSpace user interface.
Ralph
> -----Original Message-----
> From: SRU (Search and Retrieve Via URL) Implementors
[mailto:[log in to unmask]]
> On Behalf Of Blanco, Jose
> Sent: Friday, February 12, 2010 4:43 PM
> To: [log in to unmask]
> Subject: Re: browse not working
>
> I could look at the Dspace code, if you give me some guidance as to
what has to
> change in the API, but what about the the Lucene issue, would browsing
still not
> work because of the Lucene limitation?
>
> -Jose
>
> -----Original Message-----
> From: SRU (Search and Retrieve Via URL) Implementors
[mailto:[log in to unmask]]
> On Behalf Of LeVan,Ralph
> Sent: Friday, February 12, 2010 4:36 PM
> To: [log in to unmask]
> Subject: Re: browse not working
>
> You've run into 2 problems there Jose. The more serious one is that
the
> DSpace folks changed their browse interface with version 1.5 and I've
> not been able to get any help in changing my SRW interface to work
with
> it.
>
> The second problem is that Lucene doesn't support browsing backwards,
so
> even in version 1.4, a responsePosition of 10, instead of 1, would
have
> gotten you an error.
>
> If you've got the DSpace expertise to help with the API changes, I'd
be
> happy (thrilled!) to get them into my code.
>
> Ralph
>
> > -----Original Message-----
> > From: SRU (Search and Retrieve Via URL) Implementors
> [mailto:[log in to unmask]]
> > On Behalf Of Blanco, Jose
> > Sent: Friday, February 12, 2010 4:14 PM
> > To: [log in to unmask]
> > Subject: browse not working
> >
> > Ralph:
> >
> > I'm running version 1.5.2 of Dspace and I can't get browse to work.
> Take a look
> > at what you get at:
> >
> > http://deepblue.lib.umich.edu/SRW/search/DSpace/
> >
> > This is what I see in the error log:
> >
> > 2010-02-12 16:12:33,671 INFO ORG.oclc.os.SRW.SRWServlet @
> >
> operation=scan&scanClause=cql.resultSetId+%3D+%22%22&version=1.1&resp
> > onsePosition=10&maximumTerms=20
> > 2010-02-12 16:12:33,671 INFO ORG.oclc.os.SRW.SRWServletInfo @
> > pathInfo=/DSpace/
> > 2010-02-12 16:12:33,671 INFO ORG.oclc.os.SRW.SRWServletInfo @
> > dbname=DSpace
> > 2010-02-12 16:12:33,672 INFO ORG.oclc.os.SRW.SRWDatabase @
> > scanTerm:
> > 63 71 6c 2e 72 65 73 75 6c 74 53 65 74 49 64 20 cql.resultSetId
> > 3d 20 22 22 = ""
> >
> >
> > 2010-02-12 16:12:33,672 INFO ORG.oclc.os.SRW.SRWDatabase @
> > maxTerms=20, position=10
> > 2010-02-12 16:12:33,672 INFO
> > gov.loc.www.zing.srw.srw_bindings.SRWSoapBindingImpl @
> > returnTargetURL=null
> > 2010-02-12 16:12:33,672 INFO
> > gov.loc.www.zing.srw.srw_bindings.SRWSoapBindingImpl @ calling
> > setEchoedScanRequestType
> > 2010-02-12 16:12:33,672 INFO
> > gov.loc.www.zing.srw.srw_bindings.SRWSoapBindingImpl @
> > scanClause=cql.resultSetId = ""
> > 2010-02-12 16:12:33,673 INFO
> > gov.loc.www.zing.srw.srw_bindings.SRWSoapBindingImpl @ called
> > setEchoedScanRequestType
|