Summary: | extern Z39.50 search bring no matches | ||
---|---|---|---|
Product: | Koha | Reporter: | Sebastian Krieg <sebastian.krieg> |
Component: | Z39.50 / SRU / OpenSearch Servers | Assignee: | Bugs List <koha-bugs> |
Status: | CLOSED INVALID | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | katrin.fischer, m.de.rooy |
Version: | 17.11 | ||
Hardware: | PC | ||
OS: | Linux | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Attachments: | Konsole listing using yaz-client to search with Z39.50 |
Description
Sebastian Krieg
2018-04-08 09:25:26 UTC
Hi Sebastian, Z39.50 in general works for me, so I think the problem is with the GBV target. I can't test it: Die Authentifizierung erfolgt automatisch per IP-Adresse oder mittels Zugangsdaten, die Sie von der Verbundzentrale erhalten. Maybe your server's IP is not allowed access? Did you double check your configuration in Koha? An additional space at the end can break things already. I don't think this is a bug in Koha - better to ask on the mailing list. If you look in the attachment you will see that I have access when I use the yaz-client: "...Connection accepted by v3 target...." I think, this shows a valid connection. If it was from the same server, that rules out the IP problem. Can you double check your config and post what you used? (preferrably on the mailing list :) ) Hello, do you mean the /etc/koha/koha-conf.xml? Or the configured Z39.50 server connections? The settings for the Z39.50 server. When you write that up, check for additional spaces etc. It often can break things there and it's hard to notice. |