OK, Please make that zeerex database available. In the current situation
the portal that I linked to  recognizes metadata records (collection
descriptions) that contain a SRU base-URL in the way we use them in the
European Libray. If there is database with zeerex records I change the
portal to understand those records as well. 

Because this portal runs in the browser and because of the security
restrictions of Firefox and IE  we use a proxy to access the SRU targets
and we have to put all the target names in a list for this proxzy.
Installing a browser extension for SRU searching will solve this
problem. 

Theo

PS Maybe the availablity of such a SRU browser extension wil stimulate
the SRU acceptance with respect to Opensearch. SRU being technical
superior to opensearch  doesn't do the job. We saw what happened with
video 2000 with respect to VHS. We have to make SRU fun.





>>> [log in to unmask] 20-09-2005 9:38 >>>
http://srw.cheshire3.org/profiles/ZeeRex/ 

has a profile for searching zeerex records.

I do have a database for the profile configured, but not globally
available.  I can make it available easily enough, however :)

Rob

On Mon, 19 Sep 2005, Theo van Veen wrote:

>Ralph, it still is a very nice tool.
>Could you send me all the base-URLs that have been used? I would also
>like to make them all available in a  an SRU accessible database and
try
>to figure out how a metasearch portal can handle the differences
between
>different targets when doing simultaneous searching.
>A very prelimenary test version is available at
>http://krait.kb.nl/coop/tel/SRUportal/?start=sru_targets.xml.
>Such a concept (but then not written by me) could also help in
>compatibility testing.
>
>Theo
>
>
>>>> [log in to unmask] 19-09-2005 17:36 >>>
>At 11:02 AM 9/19/2005 -0400, LeVan,Ralph wrote:
>>Thanks, Sebastian!  I'd have spent too much time following that red
>>herring!
>>
>>Beats me why it doesn't like it.
>
>Try lots of raw onion.. i find that really complements red herring.
>Oooh.
>You're making me all homesick.
>
>--Seb
>
>>Ralph
>>
>> > -----Original Message-----
>> > From: Z39.50 Next-Generation Initiative [mailto:[log in to unmask]] 
>> > On Behalf Of Sebastian Hammer
>> > Sent: Monday, September 19, 2005 10:52 AM
>> > To: [log in to unmask] 
>> > Subject: Re: SRW/U vs OpenSearch blog [tester]
>> >
>> > Ralph,
>> >
>> > The 'register=on' was generated by your app -- it's not part
>> > of the base URL.
>> >
>> > Please try this base URL: z3950.loc.gov:7090/voyager
>> >
>> > Same result,
>> >
>> > --Seb
>> >
>> > At 09:56 AM 9/19/2005 -0400, LeVan,Ralph wrote:
>> > >Isn't this base URL in error?
>> > >http://z3950.loc.gov:7090/voyager?register=on? 
>> > >
>> > >You can't just stick whatever parameters you want into the URL.
>My
>> > >understanding of the rules was that the URL consisted of
>> > host, optional
>> > >port, and database.  Our parameters would follow a question
>> > mark that
>> > >we would provide (the question mark is not part of the
>> > database name).
>> > >
>> > >My tester is completely unprepared for a URL with a question
mark
>> > >embedded in it.
>> > >
>> > >Ralph
>> > >
>> > >
>> > > > -----Original Message-----
>> > > > From: Z39.50 Next-Generation Initiative [mailto:[log in to unmask]] 
>On
>> > > > Behalf Of Mike Taylor
>> > > > Sent: Friday, September 16, 2005 3:39 AM
>> > > > To: [log in to unmask] 
>> > > > Subject: Re: SRW/U vs OpenSearch blog [tester]
>> > > >
>> > > > > Date: Thu, 15 Sep 2005 18:00:55 -0400
>> > > > > From: "LeVan,Ralph" <[log in to unmask]>
>> > > > >
>> > > > > Okay, I've got my tester up as a site.  Try
>> > > > > http://alcme.oclc.org/srw/SRUServerTester.html.
>> > > >
>> > > > Nice!  Thanks for putting this up.
>> > > >
>> > > > However --
>> > > >
>> > > > http://alcme.oclc.org/srw/test/SRUServerTester?url=http%3A%2F%

>
>> > > > 2Fz3950.loc.gov%3A7090%2Fvoyager&register=on
>> > > >
>> > > >       running SRU tests for baseURL:
>> > http://z3950.loc.gov:7090/voyager 
>> > > >       tests of Explain
>> > > >           trying: http://z3950.loc.gov:7090/voyager 
>> > > >       test failed: opening URL: Connection timed out
>> > > >       test failed: expected an explainResponse, but got:
>> > > >       null
>> > > >           trying: http://z3950.loc.gov:7090/voyager? 
>> > > >       test failed: opening URL: Connection timed out
>> > > >       test failed: expected an explainResponse, but got:
>> > > >       null
>> > > >           trying:
>> > http://z3950.loc.gov:7090/voyager?operation=explain 
>> > > >       test failed: opening URL: Connection timed out
>> > > >       test failed: expected an explainResponse, but got:
>> > > >       null
>> > > >           trying:
http://z3950.loc.gov:7090/voyager?version=1.1 
>
>> > > >       test failed: opening URL: Connection timed out
>> > > >       test failed: expected an explainResponse, but got:
>> > > >       null
>> > > >           trying:
>> > > >
http://z3950.loc.gov:7090/voyager?operation=explain&version=1.1 
>
>> > > >       test failed: opening URL: Connection timed out
>> > > >       test failed: expected an explainResponse, but got:
>> > > >       null
>> > > >
>> > > >       5 tests given
>> > > >       5 tests failed
>> > > >       problems detected!
>> > > >
>> > > > Not good!
>> > > >
>> > > >  _/|_
>> > > >
>> >
>___________________________________________________________________
>> > > > /o ) \/  Mike Taylor  <[log in to unmask]>
>> > > > http://www.miketaylor.org.uk )_v__/\  "The interpreter is
>> > fairly bad
>> > > > at useful error reporting and
>> > > >       other such luxuries.  Just try to write bug-free code"
>--
>> > > >       David Fletcher.
>> > > >
>> >
>> > --
>> > Sebastian Hammer, Index Data, www.indexdata.com Direct phone:
>> > (603) 209-6853 Fax: (603) 357-1813
>> >
>
>--
>Sebastian Hammer, Index Data, www.indexdata.com 
>Direct phone: (603) 209-6853 Fax: (603) 357-1813
>