> I'm happy with these suggestions. I'd like to dump stepSize and
Jannifer wanted targetDatabase. No one wants stepSize, as far as I can
Following on from my 'discovery' that index/term needs to be a
searchClause, everything fell to pieces fairly neatly:
Accepts clause, numberOfEntries and responsePosition for SRU, and also
xClause for SRW. Adds in echoedRequest ala searchRetrieveResponse for SRU.
Also has a diagnostics list, but everything is Diagnostic 2 for the
moment. [Temporary error :)]
Why 'numberOfEntries' and 'responsePosition'? These are the terms used in
ZOOM's scan, so I just copy them from the request onto the ZOOM object.
Also means for less confusion in having to do translations from one
object's attribute name to another.
Still working on the XSL for the display, but it does a simple linked
table so far which is enough to demonstrate that it works.
(Notably it doesn't use echoedRequest to generate the links, so the
searches are always against the default index and it doesn't generate
next/previous listing links)
Things which would be useful which Theo (IIRC) brought up: Some sort of
marker for where the term would be if it's not present, or that the term
is the one used from the request. Probably another field in <term> ?
,'/:. Rob Sanderson ([log in to unmask])
,'--/::(@)::. Special Collections and Archives, extension 3142
,'---/::::::::::. Twin Cathedrals: telnet: liverpool.o-r-g.org 7777
____/:::::::::::::. WWW: http://liverpool.o-r-g.org:8000/
I L L U M I N A T I