User manual

Customizing Koha Software

Changing configuration files: We make changes to Koha, Apache2, or Zebra

configuration files in the etc folder.

Creating a commit: Once all the changes related to a feature have been made,

we commit the changes using the git commit command. The commit may

consist of a single file or several files, but all files should be logically related.

If we have changed any of configuration files in the etc folder, we install

them using the Makefile. PL, make, and make install set of commands.

These commands will install the new files in Koha's configuration folder,

/etc /koha -dev /etc /.

Changing the database: If we have made any database changes, we install

these using Koha's web installer. The web installer runs automatically when

we navigate to the staff client.

Creating a patch: Once the changes are tested, we can use the git format

patch command to create a patch. The patch can be sent to Koha's release

manager, or to others using the git send -email command.

Customizing Koha software

an example

Let's take a look at a specific example to understand how to modify Koha code.

Let's say we want to add the Google Indic Transliteration tool to the masthead

on the

OPAC. This tool transliterates text in the source language to a destination language

selected from a drop -down list. The transliterated expression

can be then be used as

a search expression.

My OPAC Header

Littditi C.LI.0

Ppty_.'és.t.fzsí<¿:

welcome, I

'Welcome to

Ted added to OPAC Main User Block kystem Preference.'

i enm,e.

My ;°PAC Credits

[ 234 ]