User manual

Chapter 13

We just copy this block above and replace the ID

biblioserver

with publicserver,

like so:

<ccl2rpn >/ etc /koha -dev/ etc / zebradb /ccl.properties < /ccl2rpn>

<user >kohauser < /user>

< password >zebrastripes < / password>

< /serverinfo>

Restarting the Zebra server

To make sure the Zebra server uses the updated configurations we have just

performed, we restart zebrasrv:

linux -4yut: /home /koha # sudo /etc /init.d /koha- zebra - daemon restart

Summary

In this final chapter we looked at some advanced features of Koha:

The ability to create one's own record matching rules gives us a powerful

way to import new records and to update and maintain the catalog.

Many large organization use LDAP to maintain users and passwords. Koha

can talk to any LDAP server including Microsoft Active Directory. The

configuration is simple; however, attention must be paid to the replicate,

update, and the mapping fields.

To setup customized OPACs for each library or branch that share a Koha

system, we set up separate Apache2 virtual hosts for each branch. For each

virtual host we set up the corresponding domain name, the name of the

stylesheet file, and the branch code.

To install additional languages, we learned how to use the

tmpl_process3 .

pl program to install language files.

Setting up a Z39.50 server allows us to share our catalog with others

and to include it in other Z39.50 solutions such as federated search.

[ 259 ]