LOC Z39.50 Connection configuration setup
Dear Koha community, Is there anyone in the community who successfully connect to Library of Congress Z39.50 server for copy cataloguing practices or search on port 210? Maybe I could have missed out on any new changes and updates with the Library of Congress connection issues. As instruction on Wiki Koha <https://wiki.koha-community.org/wiki/Troubleshooting_Koha_as_a_Z39.50_serve r> but all seems to be unsuccessful. Can someone help advice about the this issue Decka David PNG
Hi, On Mon, Jun 6, 2016 at 10:09 PM, Decka David <ddavid@lib.unitech.ac.pg> wrote:
Is there anyone in the community who successfully connect to Library of Congress Z39.50 server for copy cataloguing practices or search on port 210?
It works for me when I tested just now, although the LoC Z39.50 server is known to have occasional outages. If you have access to the command line on your Koha server, try the following command: yaz-client lx2.loc.gov/LCDB If it can connect at all, you should see something like this: Connecting...OK. Sent initrequest. Connection accepted by v3 target. ID : 81 Name : Metaproxy/YAZ Version: 1.11.2/5.15.3 7b9b025f4ca925ef5a1a939b989f8b35d3a17a72 Options: search present scan namedResultSets Elapsed: 0.431115 Z> If it cannot connect, it may signify that there is a firewall in place that is blocking access to port 210 on the LoC Z39.50 server. If it *can* connect, you can try running a search at the "Z>" prompt like this: Z> f @attr 1=4 "special relativity" If it works, you should see something like this: in particular, what you're looking for is whether it returns a non-zero number of hits: Sent searchRequest. Received SearchResponse. Search was a success. Number of hits: 138, setno 1 records returned: 0 Elapsed: 0.847077 To exit yaz-client, just enter "quit" at the "Z>" prompt. If you get this far and the yaz-client test indicates that the Koha server can reach and search LoC's Z39.50 server, then the next thing to check is the Z39.50 target definitions, which you can find in Home › Administration › Z39.50/SRU servers in the staff interface. The entry for the LC Z39.50 server should have values like this: Server name: LIBRARY OF CONGRESS Hostname: lxc.loc.gov Port: 210 Database: LCDB Syntax: MARC21/USMARC Encoding: utf8 Record type: Bibliographic Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Software, Inc. / Open Your Library email: gmc@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org
I tried yaz-client lx2.loc.gov/LCDB and the result was Connecting......error = System (lower-layer) error: connection time out What could have been the problem? I also tried Z> f @attr 1=4 "special relativity" and shows Not connected yet. Thank you for your kind responses. Decka -----Original Message----- From: Galen Charlton [mailto:gmc@esilibrary.com] Sent: Tuesday, June 07, 2016 12:25 PM To: Decka David Cc: Koha-List Subject: Re: [Koha] LOC Z39.50 Connection configuration setup Hi, On Mon, Jun 6, 2016 at 10:09 PM, Decka David <ddavid@lib.unitech.ac.pg> wrote:
Is there anyone in the community who successfully connect to Library of Congress Z39.50 server for copy cataloguing practices or search on port 210?
It works for me when I tested just now, although the LoC Z39.50 server is known to have occasional outages. If you have access to the command line on your Koha server, try the following command: yaz-client lx2.loc.gov/LCDB If it can connect at all, you should see something like this: Connecting...OK. Sent initrequest. Connection accepted by v3 target. ID : 81 Name : Metaproxy/YAZ Version: 1.11.2/5.15.3 7b9b025f4ca925ef5a1a939b989f8b35d3a17a72 Options: search present scan namedResultSets Elapsed: 0.431115 Z> If it cannot connect, it may signify that there is a firewall in place that is blocking access to port 210 on the LoC Z39.50 server. If it *can* connect, you can try running a search at the "Z>" prompt like this: Z> f @attr 1=4 "special relativity" If it works, you should see something like this: in particular, what you're looking for is whether it returns a non-zero number of hits: Sent searchRequest. Received SearchResponse. Search was a success. Number of hits: 138, setno 1 records returned: 0 Elapsed: 0.847077 To exit yaz-client, just enter "quit" at the "Z>" prompt. If you get this far and the yaz-client test indicates that the Koha server can reach and search LoC's Z39.50 server, then the next thing to check is the Z39.50 target definitions, which you can find in Home › Administration › Z39.50/SRU servers in the staff interface. The entry for the LC Z39.50 server should have values like this: Server name: LIBRARY OF CONGRESS Hostname: lxc.loc.gov Port: 210 Database: LCDB Syntax: MARC21/USMARC Encoding: utf8 Record type: Bibliographic Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Software, Inc. / Open Your Library email: gmc@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org
Hi, On Mon, Jun 6, 2016 at 10:42 PM, Decka David <ddavid@lib.unitech.ac.pg> wrote:
I tried yaz-client lx2.loc.gov/LCDB and the result was
Connecting......error = System (lower-layer) error: connection time out
What could have been the problem? I also tried Z> f @attr 1=4 "special relativity" and shows Not connected yet.
So, one possibility is that there is a firewall blocking the LC Z39.50 server outright, or just your ability to access port 210. To distinguish, you could try the following command: curl http://lx2.loc.gov If you get a response like the following: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>403 Forbidden</title> </head><body> <h1>Forbidden</h1> <p>You don't have permission to access / on this server.</p> </body></html> ... it means that while you are able to access the Z39.50 server on port 80, access to port 210 is blocked. If that's the case, your next step would be to check with your server and network administrators to see if there is an outgoing block on port 210. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Software, Inc. / Open Your Library email: gmc@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org
participants (2)
-
Decka David -
Galen Charlton