> I will use explain. Not yet using explain does not have anything to do
> with XSL but with the following. We use collection descriptions to build
> And the collection description should contain other Zeerex information
> to enable searching. So I need most relevant information already befor
> actually accessing the target.
Interesting. We do that as well, as it turns out, using ZeeRex for Z39.50
services and will do so for SRW too when we get Scan finalised.
The issue I found with SRU and XSL was that you don't have the explain
information cached anywhere accessable in the browser, which is a real
pain, but there's little to be done about it outside of frameset hacks.
This is what I meant by not wanting to use Explain ... because it's just
HARD when you don't have full control of the client environment, nor the
> Currently I am thinking of retrieving the explain record when a user
> selects it for using the native search fields. If you do not mind I will
> use your stylesheet for it.
Please, feel free :) If you have any improvements on it, I'd love to hear
> Some of the issues that Bill has 'solved' by adding in new fields, are
> my fault I will admit. We need to sit down and document the possible
> values for types of <link> in Zeerex. (As well as finalising a character
> set element!)
> The issue appears to be that Theo and Bill want to just use XSL to do
> their display work in a browser and hence don't want to use Explain for
> what it was designed for. At least that's the feeling I get.
> Do we need a brief title element for Zeerex?
> Two pretty important link types that need to go into the Zeerex
,'/:. Dr Robert Sanderson ([log in to unmask])
,'--/::(@)::. Special Collections and Archives, extension 3142
,'---/::::::::::. Nebmedes: telnet: nebmedes.o-r-g.org 7777
____/:::::::::::::. WWW: http://nebmedes.o-r-g.org:8000/
I L L U M I N A T I