On Wed, Dec 09, 2009 at 07:48:45AM +, Jonathan Field wrote:
> The values for the port is found in your koha-conf.xml
>
>
>
> in this case . You can change the port number if you wish though.
>From my experiments, this is not enough, because publicserver won't
serve any records. Host of
I did change the settings as you said. The name of z39.50 server appears in
the list of the servers. When I make a search it shows up "No Results". But
when I make search in the server using the same field, it gives me about 50
results.
I have also noticed that other z39.50 targets here have encod
If you want your Koha system to be searched as a target you need to set
it up in your koha-conf.xml on the server. If you look at it right now,
it probably has the lines commented out.
If you are then looking to search it FROM Koha (that is, back to
yourself) you need to configure the target as
I have tried it before but its a bit confusing. I could not get the search
results. I think I made something wrong.
Don't we have to configure the target from backend???
I have made a new z39.50 target with the following parameters:
Z39.50 Server: Healthnet Nepal
Hostname: 202.70.88.18
Port: 999
Hello Nitesh,
I have this working on my installation. You need to configure your
koha-conf.xml. It is described here:-
http://koha.org/documentation/faq/could-someone-tell-me-the-exact-steps-i-need-to-take-to-configure-zebra-to-expose-my-koha-3-db-as-a-public-z39.50-service
I believe, right now,
Hello all.
I am using KOHA 3.0.3 in Debian Lenny. We are currently hosting 10 different
libraries. We want the records of one library to be searched from another
library. For this we are thinking to make a z39.50 server in our Koha
Installation with all the records of 10 libraries into a single se
