Community Experience Distilled
Koha 3 Library Management System Install, configure, and maintain your Koha installation with this easy -to- follow guide Savitra Sirohi Amit Gupta open source E community experience distilled PUBL ISHING BIRMINGHAM - MUMBAI `= `SvPD.' SHROFF PUBLISHERS & DISTRIBUTORS PVT. LTD.
Koha 3 Library Management System Copyright © 2010 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews. Every effort has been made in the preparation of this book to ensure the accuracy of the information presented.
Credits Authors Savitra Sirohi Amit Gupta Reviewers Kyle M Hall Vimal Kumar V Acquisition Editor Steven Wilding Development Editor Wilson D'souza Technical Editor Kavita lyer Indexer Hemangini Bari Editorial Team Leader Akshara Aware Project Team Leader Priya Mukherji Project Coordinator Srimoyee Ghoshal Proofreaders Aaron Nash Clyde Jenkins Graphics Nilesh Mohite Production Coordinator Adline Swetha Jesuthas Cover Work Adline Swetha Jesuthas
About the Authors Savitra Sirohi heads Nucsoft OSS Labs (http: //www.osslabs biz) - a Koha services provider. As part of his work, Savitra has lead several Koha implementations and conducts regular Koha workshops in India. Savitra is an Engineer and has an MBA from the Indian Institute of Management. . We would like to thank Kyle Hall, Vimal Kumar, and Nicole Engard and other members of the Koha community who took the time to review the chapter drafts.
About the Reviewers Kyle M Hall is an IT specialist for the Meadville Public Library and the Crawford County Federated Library System of Pennsylvania is a Free Open Source Software advocate and software developer. His contributions to Koha include bugfixes and new features, as well as the Koha Off -line Circulation system.
Table of Contents Preface 1 Chapter 1: Installing the Software Stack 7 An orientation to Koha's installation Koha's architecture What do we need to install? Installation tools Package manager Make utility CPAN shell Git Choosing between Linux Perl packages and CPAN modules Choosing a Linux distribution Getting help -Koha's community resources Preparing for installation Server prerequisites Downloading Koha and switching to a branch Cloning Koha Checking out a branch Preparing a list of installation p
Table of Contents Installing packages using dselect Installing Perl modules using CPAN Troubleshooting CPAN installations Setting up Koha's MySQL database Configuring Koha's installation: Makefile.
Table of Contents Chapter 3: Installing Koha's Zebra Search Engine About Zebra Koha's Zebra related components Zebrasry -the Zebra query and retrieval server Rebuild_zebra.
Table of Contents Configuring the correct SAX parser Setting up environment variables for the Linux shell Setting up KOHA_CONF environment variable Setting up PERL5LIB environment variable Setting up persistent environment variables Summary Chapter 5: Configuring the Cataloging Module A first look at Koha's cataloging configuration tools MARC frameworks Authority Control Authorized values Preparing a configuration plan Identifying Authority Control rules Identifying frequently cataloged types of materia
Table of Contents Item types Identifying Item types Creating Item types Circulation and fine rules Identifying circulation and fine rules Creating circulation and fine rules Configuring the calendar and calculation of due date and fines Calendar and fine calculation Calculation of due dates in Koha Preparing to configure the calendar and fines and due date calculations Editing the calendar Editing system preferences Due and overdue notices Preparing to configure due and overdue notices Editing notices E
Table of Contents Configuring general preferences Configuring messaging preferences Configuring security preferences Configuring search preferences Summary 138 138 142 145 147 Chapter 8: Test Driving Your Koha Installation 149 Patrons -create, search, and view patron record 149 150 Creating a new patron Searching for a patron Cataloging- create, search, and view bibliographic and item record Creating a bibliographic record Creating an item record Searching for the record Circulation- check -out, c
Table of Contents MARCEdit bulkmarckimport.
Table of Contents Software bugs Command line programs- environment variables not exported 211 Problems with Internet Explorer Summary 213 214 215 Chapter 11: Updating Software 217 Orientation to updating software 217 217 Understanding Koha's software versions Branches Heads Tags Choosing a version to update to Understanding components of software updates An overview of the installation process Updating the software Downloading updates using git pull command Switching to a new software version Ins
Table of Contents Using Git to manage software changes Understanding the software customization process Customizing Koha software -an example Creating a development branch Making CSS changes Creating a new JavaScript file Loading the Transliteration JavaScript file Creating a system preference Adding the transliteration tool to the display template Editing the Perl scripts to enable the system preference Committing changes Create a patch using Git Sending the patch to Koha's release manager Summary Chap
Preface Much of what we have written in this book is based on our experiences teaching Koha installation and maintenance of technology and library staff. We hope this book will help you to quickly install and set up a working Koha installation, complete with catalog data migrated from your current library system. The first nine chapters of this book are devoted to these topics.
Preface Chapter 3, Installing Koha's Zebra Search Engine In the third chapter we will focus on Zebra - Koha's powerful catalog search engine. We will learn how to install and test Zebra. Chapter 4, Koha's Web Installer, Crontab, and Other Server Configurations In the fourth chapter, we will learn about executing Koha's web installer, setting up Koha's Crontab, and configuring Koha services to start automatically when the machine reboots. At the end of this chapter, we will be able to launch Koha.
Preface Chapter 10, Troubleshooting In this chapter, we will learn about ways to troubleshoot Koha problems, we will learn about the community tools and resources and take a closer look at ten specific problems. Chapter 11, Updating Software It is good practice to keep your Koha software updated to benefit from new features and bug fixes, but also to avoid migration problems if your version falls too far behind. In this chapter we learn how to download and install software updates.
Preface Who this book is for This book is aimed at Linux System Administrators who need to install and maintain Koha. If you are a system administrator who wants to set up an open source integrated library system, then this book is for you. It will also be useful for system administrators who require help with specific aspects of implementing Koha. Conventions In this book, you will find a number of styles of text that distinguish between different kinds of information.
Preface If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide on www.packtpub. com /authors. Customer support Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase. Errata Although we have taken every care to ensure the accuracy of our content, mistakes do happen.
1 Installing the Software Stack In this chapter, our goal will be to install Koha's software stack -the Koha application itself and the various system and Perl packages it uses. Installing the stack in itself is not enough to be able to use Koha, but is an important first step. This task can be quite challenging, especially for novice Linux users. You will need to get familiar with using the Linux terminal and multiple installation tools.
Installing the Software Stack Koha's architecture First, let us take a quick look at Koha's architecture.
Chapter 1 Package manager A package manager makes installation easy by automatically installing prerequisites, tracking versions and updates, and verifying checksums. Your choice of the package manager will usually depend on the Linux distribution you use.
Installing the Software Stack Choosing between Linux Perl packages and CPAN modules CPAN is the largest archive of Perl modules. Perl modules are always available on CPAN. Many, but not all of Koha's Perl prerequisites are available as packages in a distribution's sources. The recommended approach in such a scenario is to use Linux packages where available. If you don't find packages for a certain module, then use CPAN to install it. The Linux package manager can manage all prerequisites of a module.
Chapter 1 Wiki: Koha's wiki might have useful material - http: //wiki .koha- community.org/. Installation documents: Up -to -date installation documents are available in Koha's application folder. Preparing for installation In this section we prepare for the installation- setting up a server, preparing a list of packages for installation and configuring installation tools.
Installing the Software Stack Now we are ready to download Koha, let us change to a folder where we want to install Koha. The user koha must own this folder: koha @1i190 -245:- # cd /home /koha To clone the application from Koha's git server we use the git clone command: koha @1i190 -245: -$ git clone git:: / /git.koha- community.org /koha.git kohaclone Checking out a branch Before installing Koha, we need to select the software version or branch that we want to use.
Chapter 1 System packages We use the term system packages for non -Perl modules. Here is a list of system packages that you must have in your installation list; you will need to to look up the right names for each of these from your distribution's sources: Package Apache2 MySQL Make Gcc Yaz Libyaz Libyaz -devel Description The web server. The database server. Programs that helps build and install packages. Is the compiler package. Is the toolkit used in Z39.50 clients and servers.
Installing the Software Stack Text::CSV_XS 0.32 not found. [Thu Aug 5 05:07:41 2010] Makefile.PL: Warning: prerequisite XML::RSS 1.31 not found. Writing Makefile for koha koha @1i190 -245: -/kohaclone$ You will need to look up these modules in your distribution's repositories to find corresponding packages. The system packages will usually be named with a prefix "perl -" and will have " -" instead of ":: ".
Chapter 1 deb http: / /ftp.indexdata.dk /debian lenny main deb -src http: / /ftp.indexdata.dk /debian lenny main With openSuSE 11.2, you will need the Perl repository: http: / /download.opensuse.org/ repositories /devel: /languages: /perl/ openSUSE_11.2/ We use zypper to add a repository from the command line: koha @li190 -245: -$ sudo zypper ar http: / /download.opensuse.org/ repositories /devel: /languages: /perl /openSUSS 11.2/ perl- repository Don't forget to refresh the package source.
Installing the Software Stack Installing Koha's software stack In this final section we demonstrate the installation steps on Debian and openSUSE. Installing packages using the package manager We will install most packages using the package manager. Having installed Git in an earlier section, readers are already familiar with the commands used to install individual packages; in this section, we also look at ways of speeding up the process.
Chapter 1 Installing packages using dselect Debian and Ubuntu users can use dselect, a convenient way to install package lists. First we install dselect: koha@li190- 245: -/kohaclone$ sudo apt -get install dselect Next, we select what needs to be installed by pointing to the file containing the list of packages: koha @li190 -245: -/kohaclone$ sudo dpkg -- set -selections < install_misc/ debian.
Installing the Software Stack Troubleshooting CPAN installations If CPAN modules don't install successfully, we would see messages like these at the end of install command: MIRK /Net- Z3950- ZOOM- 1.26.tar.gz writemakefile NO : ' /usr /bin /perl Makefile.PL INSTALLDIRS =site' returned status 512 WRW /Barcode- Code128- 2.01.tar.gz : make_test NO LARSLUND /PDF- Reuse -Barcode- 0.05.tar.
Chapter 1 This means we need to install YAZ related packages using the package manager, on Debian -yaz and libyaz-dev and on openSUSE -yaz, libyaz, libyaz -devel. After installing these packages using the package manager, we run the make series of commands to complete the installation: cpan[8]> look Net::Z3950::ZOOM sh -3.2# make clean sh -3.2# perl Makefile.PL sh -3.2# make sh -3.2# make test sh -3.2# make install sh -3.
Installing the Software Stack Configuring Koha's installation: Makefile.PL After we have installed required system and Perl packages and set up the database, we are ready to install Koha. The first step is to run Makef i le . PL to configure Koha's installation. We will need to supply responses to questions such as mode of installation or database name: koha @linux: /home /koha /kohaclone # perl Makefile.
Chapter 1 The program display a summary of the configuration at the end, make a note of the details: Koha will be installed with the following configuration parameters: DB_HOST localhost DB_NAME koha DB_PASS katikoan DB_PORT 3306 DB_TYPE mysql DB USER kohaadmin INSTALL BASE /home /koha /koha -dev INSTALL_MODE dev INSTALL ZEBRA yes KOHA_INSTALLED_VERSION RUN DATABASE_ TESTS USE MEMCACHED 3.01.00.
Installing the Software Stack Troubleshooting Perl module installations Setting up Koha's MySQL database Installing Koha using the Make utility In the next chapter, we will learn how to configure the Apache web server and Koha's web installer.
2 Configuring the Apache2 Web Server In this chapter, our goal will be to configure Apache2. Apache2 is Koha's web server -it serves Koha pages to users when they access the OPAC (Online Public Access Catalog) or the staff client. At the end of the chapter we will be able to launch Koha's OPAC and the staff client interfaces using a web browser. However, the interfaces won't work until we execute Koha's web installer, a topic for Chapter 4.
Configuring the Apache2 Web Server Securing access to Koha's application folders Logging error messages to a file Rewriting page URLs To learn more about Apache, refer to documentation here: http://httpd.apache.org/docs/2.2/. Apache2 virtual hosts Apache's documentation virtual hosts as follows: (http: // httpd .apache.org /docs /2.2 /vhosts /) defines The term Virtual Host refers to the practice of running more than one web site (such as www . companyl . corn and www . company2 .
Chapter 2 Here are some guidelines to help you work this out: Using host names is a better option because they are easier to remember. But if you are not in a position to create host names, you will need to use IP addresses. Using Apache2's default port 80 for both interfaces is a better choice. Port 80 is allowed for use on most networks. If you are not in a position to create two host names, you can consider using an additional port.
Configuring the Apache2 Web Server While on openSuSE such files are created in the folder vhosts . d: koha@1i190-245:/$ is /etc/apache2/vhosts.d/ Koha's default Apache2 file Koha's installation process from the previous chapter creates a default Apache2 configuration file named koha- httpd. conf. You will find this file under the Take a look at this file: etc folder inside Koha's configuration folder. koha @1i190 -245:/$ vi /home /koha /koha -dev /etc /koha -httpd.
Chapter 2 Virtual host configuration Each virtual host block has a set of directives that controls how Apache2 will work with respect to Koha. You will find that the default koha -httpd. conf file is already configured for the most part, but we may want to modify some of the settings to suit our environment. Some of the directives we may want to configure are: Directive ServerAdmin ServerName ServerAlias Description The e -mail address that is displayed when the website does not function properly.
Configuring the Apache2 Web Server Two host names This is the best way to configure the two interfaces - there are two different host names, both easy to remember and we don't use any non -standard ports. Item Value OPAC IP Address Any Staff Client IP Address Any OPAC Host Name libcat.mylibrary.org Staff Client Host Name libstaff.mylibrary.org OPAC Port 80 Staff Client Port 8 0 Comments We use host based virtual hosts; we don't need to use IP based virtual hosts.
Chapter 2 Item Value OPAC Port 80 Staff Client Port 8080 Comments We expect to use the staff client within our network, and using a non -standard port is not a problem for us. IP address with two ports If you are not in a position to setup hostnames, you would need to use IP addresses. Here we use a single IP address with two different ports. Item Value OPAC IP Address 192.168.1.21 Staff Client IP Address OPAC Host Name 192.168.1 .
Configuring the Apache2 Web Server Two IP addresses This is IP based virtual hosts. We use two IP addresses, one for the OPAC and the other for the staff client. Your Koha server needs to have at least two Network Interfaces cards. Item Value Comments OPAC IP Address 192. 168.1.21 Staff Client IP Address 192.168.1.22 This is just a test environment; here we can't get a host name and a DNS entry. Our server has or we can setup two IP addresses.
Chapter 2 Configuration prerequisites Here is a list of prerequisites that you might want to take care of; some of these may not apply to your situation depending on the sort of configuration plan you have. Item Open Firewall ports Host Names Domain Name Service (DNS) IP Addresses Description If you are using ports other port 80, you might need to open those ports on network firewalls or routers. If you intend to use host names, you will have to purchase or set them up.
Configuring the Apache2 Web Server Enabling Apache2's Rewrite module Koha uses Apache2's Rewrite module to manipulate URLs. To allow this we need to enable the module using the a2enmod command: koha @1i190 -245 : /$ sudo a2enmod rewrite Configuring the listener If you intend to use ports other than 80, you will need to configure the Listen directive. On Debian we add this directive to the ports . conf file: koha @1i190 -245:/$ sudo vi /etc /apache2 /ports.
Chapter 2 In a similar manner, we set other directives: ServerAdmin ErrorLog webmaster@mylibrary.org / var / log /apache2 /log /koha -opac- error_log Editing the staff client virtual host Next we edit the staff client virtual host block; we will need to repeat the steps above for this virtual host. If you need to change the port we edit the first line of the virtual host: ## Intranet < VirtualHost 127.0.0.
Configuring the Apache2 Web Server Once we complete the Apache2 configuration, we are ready to test Koha. To navigate to the OPAC, type the URL for the OPAC in your favorite browser. Depending on your configuration, you may access the site via the host name, something like this: http: / /libcat.mylibrary.org Or using an IP address, like this: http://192.168.1.21 If you are on a standalone machine, you would use a local loop IP address or the name localhost: http: / /localhost or http: //127.0.
Chapter 2 Or if have a dedicated IP address: http://192.168.1.22/ Or if you are on a standalone machine: http: //localhost : 8080 or http: //127 . 0 . 0.1 : 8080/ .y. http, 127 n n 2 6050 gi-birJ,ha/metallPrrmstall pl tel yr 9MM:hiQeal:z4,-.,4* m'F oha >Loy intohha 4koha OPEN- 5000.0E th'TE40.ATED EIEXAEY SYSTEM Welcome to the Koha Web Installer Before we begin, please verify you have the correct credentials to continue.
Configuring the Apache2 Web Server Rewrite module not enabled If you have not enabled Apache2's Rewrite module, you will see this error when starting Apache2: linux: /etc /apache2 /vhosts.d # sudo /etc /init.d /apache2 restart Syntax error on line 28 of / etc / apache2 /vhosts.d /koha -httpd.
Chapter 2 Ii http 4127 J 0 2' Moat Visaed", an't,psteiMiEv Wig Started koh Error Koha error The folio-wino fatal error has occurred Can't orn' to Ideal MySQL server through soetet ./varfron7mysql(mysql.sock. (2) at fogrfahartikohaflohtiC4/Centext.am liee 665. Compilation failed in reqiii re at (Gore,harelkohaelone/C4oCireulation.pm line 25. BEGIN felled- -compilatiod aborted at iogr(ahare(ket,aclonefC4/Eirotaatien.pm line 2S. Ca,mpilatlen failed in require at futr/shareikohaalonefE4fgeerdees.
Configuring the Apache2 Web Server Summary Here is what we learned in this chapter on configuring Apache2: Setting up a symbolic link to Koha's Apache2 configuration file Enabling Apache2's Rewrite module Configuring an IP address in Koha's virtual hosts Configuring host names in Koha's virtual hosts Setting up Apache2 to listen on the staff client port Configuring the Directory directive in a virtual host Launching Koha's OPAC and staff client In the next chapter, we will install and test Koha's Zebra sea
3 Installing Koha's Zebra Search Engine You will need to use Koha's Zebra search engine if you have more than say 10,000 catalog records. Without Zebra, catalog search results may be too slow. If you have a small catalog you can use Koha without Zebra, in fact earlier versions of Koha did not have Zebra. Without Zebra both installation and ongoing maintenance will be simpler. However you should consider using Zebra even for small catalog sizes because of Zebra's superior capabilities.
Installing Koha's Zebra Search Engine It can be queried using complex search expressions such as AND and OR operators It allows for additional features on Koha such as search limits, and refining searches that are otherwise not available It has sophisticated features such as approximate matching, and spelling correction It can be queried by any Z39.50 or SRU /W client Learn more about Zebra here: http: / /www.indexdata.com /zebra /. Documentation on Zebra is available here: http: / /www.indexdata.
Chapter 3 Rebuild _zebra.pl -the Zebra index maintenance program This is a Perl program that is used to create and maintain Zebra's search indexes.
Installing Koha's Zebra Search Engine Installing Koha with Zebra You might have already installed Koha with Zebra. If you had installed Zebra packages before installing Koha and had selected yes to the question Install the Zebra configuration files ?, then you can skip this section. Once Zebra packages are installed we need to install Koha. This installation process creates Zebra related configuration files and installs them in Koha's configuration folder, in our case /etc /koha -dev /.
Chapter 3 Testing zebrasry The zebrasry program is usually installed under /usr /bin and you should be able to invoke it from any folder location.
Installing Koha's Zebra Search Engine zebrasry daemon The Zebra Server is usually run in the background as a daemon. In this section we learn how to setup zebrasry as a daemon and how to set it up as a service that can be included in the system's start -up profile. Once again, we see how things are easier on Debian or Ubuntu than on openSuSE. Zebrasrv daemon on Debian or Ubuntu Koha ships with a script, koha- zebra -ctl . sh that can run zebrasry in the background as a daemon.
Chapter 3 zebrasry daemon on openSuSE The daemon command is not available on openSuSE. This is because the corresponding package daemon is not included in openSuSE repositories for copyright reasons. However there are alternatives to the daemon command: For starting a process For stopping a process startproc: killproc: We can modify the koha- zebra -ctl . sh file to work on openSuSE by replacing the daemon command with startproc and killproc and suitably modifying the options supplied to the commands.
Installing Koha's Zebra Search Engine To ensure that command: zebrasry starts when the machine reboots we use the chkconf ig linux -4yut: /home /koha # sudo chkconfig koha- zebra - daemon on Rebuilding Zebra Let us now test the second key Zebra related component program is used to maintain Zebra's search indexes. The program can be found in the folder misc kohac lone rebuild_zebra . pl.
Chapter 3 Parameters -nosanitize -w -y -mungeconfig - -help or -h Description Export biblio /authority records directly from DB marcxml field without sanitizing records. It speed up dump process but could fail if DB contains badly encoded records. Works only with -x. Skip shadow indexing for this batch.
Installing Koha's Zebra Search Engine Creating or recreating indexes To create or recreate the complete index of all bibliographic records in the database, we would run the command as follows: linux -4yut: /usr /share /kohaclone /misc /migration_ tools # sudo . /rebuild_ zebra.pl -b -r -v To index bibliographic records incrementally, we could set up the command as follows: linux -4yut: /usr /share /kohaclone /misc /migration_ tools # sudo . /rebuild_ zebra.
Chapter 3 Cyr -relic, Patrons Search 4koha NO_LIDRARY_SET LEO! kohaadmin ILeo Out) More n I al Search Search System Preferences Check Out Search the Catalog Hum oAdmÍnlStraticrt, System Preferences New Preference Admin Acquisitions Enhanced Content Authorrhes Cataloging System preferences admin all preferences Preference Value Explanation Nolebra If Oi Zebra indexing is turned off, simpler setup, but slower searches. WARNING: using NoZebra on even modest sized collections is very slow.
Installing Koha's Zebra Search Engine Summary Here is what we learned in this chapter: Installing Zebra packages Installing or reinstalling Koha to work with Zebra Invoking the zebrasry program from the Linux shell Running the zebrasry as a daemon Setting up the zebrasry daemon as a service Including the zebrasry service in the start -up profile Executing the rebuild_zebra.
i Koha's Web Installer, Crontab, and Other Server Configurations In this chapter, we will complete Koha's installation and system configuration tasks. First we will execute Koha's web installer to populate the Koha database structure and some important administrative settings. This will allow us to launch Koha's staff interface and its OPAC. We will set up the koha user's crontab to schedule periodic execution of Koha programs such as those that generate overdue notices or calculate fines.
Koha's Web Installer, Crontab, and Other Server Configurations Understanding the web installer's functions Koha's web installer performs the following functions: Checks for the existence of Koha's database, the connectivity to the database, and if the database user has the required privilege on the Koha database Creates Koha's database structure-its tables, relationships between tables, database constraints, and other rules Accepts user input on important configuration questions such as Language or MARC fl
Chapter 4 v http i,I_7 f o 2 8080rcgl LintAohatmstalteiFinstall pl ,...: . . ¢m of h oha ", Log In to holla 4koha OREN S01.1105 INTE4RATE0 IIERARY SYSTEM Welcome to the Koha Web Installer Before we begin, please verify you have the correct credentials to continue. Please log in with the username and password given to you by your systems administrator and located in your koha- oonr.=mt configuration file.
Koha's Web Installer, Crontab, and Other Server Configurations Understanding optional data available for import Let us understand some of the optional setting and sample data that we can choose to install using the web installer. Settings for MARC frameworks MARC frameworks define how data is captured for different types of material. The frameworks control things such as, which MARC fields are used, which of these fields is mandatory, or which fields are under authority control.
Chapter 4 Fast Add framework: This framework is designed for quickly adding catalog records; it has fewer fields when compared to other frameworks. Simple MARC 21 Bibliographic frameworks: A set of bibliographic frameworks for common types of material such as books, CDs, or serials. Other data Here is a listing of data we can import under the Other data section: Optional Ll Some basic default authorised values for Library Departments, Item Lost status, etc.
Koha's Web Installer, Crontab, and Other Server Configurations Sample Label and Patron Card Data: A set of sample layouts and templates for use in Koha's label and patron card generation, and printing tool. Sample Holidays: A sample set of holidays for use in Koha's calendar. The calendar is used in Koha's circulation module to calculate due dates and fines. Default Item Types: A sample set of item types. Item types are used to define circulation policy such as loan period or fine amount.
Chapter 4 Launching Koha Once the installer finishes it should automatically redirect to the staff interface: 4koha OPEN-SOURCE !4i ?EGRATES E9a5AAY SYSTEM dïd username ttr pa Err Username. .......... kohaadmin Password: .........................
Koha's Web Installer, Crontab, and Other Server Configurations To launch the OPAC navigate to the OPAC url and you should see a screen such as this: Library Catalog kl Configuring the crontab Several Koha programs need to be run periodically. These programs calculate fines, generate overdue notices, send out e- mails, or build Zebra indexes. We use Linux's Cron utility to schedule the execution of these programs. Editing the crontab The cronjobs are set up under the koha user's crontab.
Chapter 4 Generating advance notices Advance notices are sent to patrons when items are due. To generate such notices, we need to script advanced_ not ices .pl as a cronjob. Add a line to the crontab as follows: 49 5 * * * perl / home /koha /kohacone/ bin /cronjobs /advance_notices.pl -c This cronjob will execute at 5:49 AM every day and generate and queue advance notices messages to patrons. Generating overdue notices Overdue notices are sent to patrons when items are past due.
Koha's Web Installer, Crontab, and Other Server Configurations Rebuilding Zebra indexes In Chapter 3, Installing Koha's Zebra Search Engine, we learned how to rebuild Zebra indexes by passing different parameters to the rebuild_zebra.pl program. To schedule index rebuilds, we script a cronjob as follows: */1 * * * * perl /home /koha /kohaclone /misc /migration_ tools /rebuild_ zebra.
Chapter 4 Auto -starting Apache2 On Debian, Apache2 is configured by default to start automatically on server reboot. In openSuSE, however, this is not the case.
Koha's Web Installer, Crontab, and Other Server Configurations Add the zebrasry command to the file somewhere near the end of the file as follows: # script with local commands to be executed from init on system startup # Here you should add things, that should happen directly after booting # before we're going to the first run level. /usr /bin /zebrasry -f /etc /koha -dev /etc /koha- conf.
Chapter 4 koha@linux:/home/koha/kohaclone/misc # cd /usr/lib/per15/vendor_perl/5.10.0/XML/SAX/ koha@linux:/usr/lib/per15/vendor_perl/5.10.0/XML/SAX # vi ParserDetails. ini [XML::LibXML::SAX::Parser] http://xml.org/sax/features/namespaces = 1 Let us test the parser configuration again; a correct file will result in an output like this: koha @ linux: /home /koha /kohaclone /misc # . /sax_parser_print.
Koha's Web Installer, Crontab, and Other Server Configurations Setting up PERL5LIB environment variable The PERL5LIB environment variable points to the kohaclone folder.
Chapter 4 Summary Here is what we learned in this chapter: Executing Koha's web installer to populate the database structure and mandatory administrative settings Configuring the crontab to schedule Koha's batch programs Configuring the necessary XML SAX parser Configuring Apache2, MySQL, and Zebra server to start automatically on reboot We have now completed the installation and server configuration phase of the book.
5 Configuring the Cataloging Module In this chapter, we will learn how to configure Koha's Cataloging module. This module is used to maintain information about items in the library. Cataloging is an important function -a good catalog helps patrons find and evaluate items easily.
Configuring the Cataloging Module A first look at Koha's cataloging configuration tools Before we create our cataloging configuration plan let us understand Koha's configuration tools: MARC frameworks are cataloging templates for different types of material in the library Authority Control allows us to control data entry in certain fields. Authority Control is used for title, name, and subject fields Authorized values offer an additional way to control data entry.
Chapter 5 Here are some notes on frameworks: While installing Koha you can choose to install a set of frameworks for commonly used material types New frameworks can be created by modelling them on existing ones Frameworks can be edited or deleted at any time The default framework has a broad set of fields and can be used for material that doesn't fit into any other framework Frameworks control how a catalog record is entered and displayed in the cataloging screens Frameworks have no impact on records that
Configuring the Cataloging Module Second, authority control is used by catalogers to collocate materials that logically belong together, although they present themselves differently. For example, authority records are used to establish uniform titles, which can collocate all versions of a given work together even when they are issued under different titles. Authority records are usually created for name, title, and subject headings.
Chapter 5 Authority Types are mapped to fields in Bibliographic MARC frameworks Authority Types control how an authority record is entered and displayed in the authorities cataloging screens as shown in the following screenshot: Cir culation Patrons Search NO_LIBRARY_SET (ÿg) I kohaadmin (Loa Out) I 121 More 4koha Suhrnit Check Out Check In 1 Search the Catalog Hume .
Configuring the Cataloging Module Catalogers will not be able to enter free text in fields that are controlled via authorized values; they will only be able to pick values from a list. Like Authority Control, authorized values help reduce errors and bring about consistency in catalog records. Circulation Patrons Search 4koha RO_UBRARY SET (} I kohaadmin (Log L.tu(} I ( .. _gp k Out Search the Catalog Check Irr Horsy .Administration ,Authorted \rattles System Preferences .
Chapter 5 And here are some key points about authorized values: While installing Koha you can choose to install a set of commonly used authorized values categories along and corresponding values New Authority values categories and values can be created, edited, or deleted Authorized values categories can be mapped to fields in Bibliographic MARC frameworks Some authorized values such as branch and item type are special and they are configured under Koha's Administration screens Preparing a configuration p
Configuring the Cataloging Module Based on this you can develop a plan that looks something like this: Question Plan Use Authority Control? Create authority records before bibliographic records are created, or after they are created Do you want bibliographic records to be automatically updated when authority records are updated? Yes After bibliographic records are created Yes Identifying frequently cataloged types of material Create a list of materials that are cataloged often and have distinct biblio
Chapter 5 260$c: Date of publication 300: Physical description 500: General note 505: Formatted contents note 6XX: Various subject fields 7XX: Other authors 952$a: Home branch 952$d: Date acquired 952$p: Barcode 952$y: Item type Identifying mandatory fields Next, for each field and subfield we will indicate if it needs to be mandatory. If data for a certain field is always available, and the field helps patrons find or evaluate an item, it might be a good idea to make it mandatory.
Configuring the Cataloging Module Identifying Authority Control rules Here will need to decide which bibliographic fields will be under Authority Control. The usual name, title, and subject fields are natural choices, but you can consider other fields too.
Chapter 5 Tag/Subfield Mandatory? 020: ISBN No 082: Call number No 1XX: Author fields Yes 245: Title Yes 260$a: Place of Yes publication 260$b: Publisher Yes 260$c: Date of Yes Authority Control Authorized values control Yes Yes Yes publication 300: Physical description 500: General note 505: Formatted contents note Yes Yes No 6XX: Various subject fields 7XX: Other authors Yes Yes No Yes 952$a: Home branch Yes 952$d: Date acquired Yes 952$p: Barcode Yes 952$y: Item Type
Configuring the Cataloging Module Configuring authorities system preferences We will need to set two system preferences: BiblioAddsAuthorities: Turn this Off, if you expect to have authority records available for use during creation of bibliographic records. If this is set to On, authority control is turned off; Catalogers can enter the data in the field, and Koha automatically creates authority records based on what is entered in the corresponding bibliographic field.
Chapter 5 Configuring Authority Types Authority Types are MARC frameworks for authority records. Commonly used Authority Types are available with the default installation of Koha. You can create new ones if you want to bring fields other than name and subject headings under Authority Control. To create a new authority type, follow these steps: We find Authority Types screens in the Catalog section under Administration. 2. Click on New Authority Type button. 3.
Configuring the Cataloging Module Configuring authorized values categories We will need an authorized values category for each field we want to control using authorized values. Find Authorized Values screens in the Catalog section under Administration. The pre- configured set of categories is listed in the Show Category list of values. To create new categories, we use the New Category button. ulation Patrons Search 4koha More e NO_LtBRARY_SET t,..2:) ..__ Cheik.ut. . . .........
Chapter 5 Circulation Patrons Search 4 ko ha NO_LIBRARY_SE7 í More I kohaadmin (Log Out) I1? 1 `eubnd Check In Check Out Search the Catalog Home , Administration ,Authorized' Values , hivdify authorized value System Preferences Modify authorized value System Preferences Basic parameters Libraries and groups Funds and budgets Currencies and exchange rates Item types Patrons and circulation Patron types and categories Cities and towns Road types Patron attribute types Circulation and fines rule
Configuring the Cataloging Module Library Libraries can be maintained in Libraries and groups section in the Basic parameters section under Administration. Circulation Patrons Search 4koha Homer More . Chec. Cut minletar tian.
Chapter 5 Circulation Patrons Search 4koha MO_LIBRARY_SET (Set} More 7 j,:,.:, .::.. . . ,.. I kohaadmin (Log Out¡ I L? 1 .<.
Configuring the Cataloging Module Creating a new framework To create a new framework, we use the New Framework button. Once the Framework Code and Description is saved, we click on the MARC structure link. Circulation Patrons Seaton 4kQ%2Cl More n NO_LIBRARY SET (WI I kohaadmin t_ rut) I L? j Subnnt Check Out Check In Search the Catalog .............. ..........._____.__..._........
Chapter 5 irculerme Patrons Search 4k o h a HO LIBRARY_SET Set I kohaadmin (Lou C1.
Configuring the Cataloging Module Use the Search for tag feature to navigate to the field you wish to edit. Use the Display only used Tags /Subfields checkbox as a navigation aid. Circulation Patrons Search More e 4koha NO_LIBRARY_SET Qat I kehaadmin (Leg Out) I f,? I Suimvt ; Search the Catalog Check In Nome r Administration >MARC Franr.eworrs : kiPRC Framework for Soaks, Booklets, Workbooks (BKS) System Preferences System Preferences Basic parameters Libraries and .
Chapter 5 Circulation Eear=h Patrons RO_LIBRARY SET (;,yf) I kohaadmin (Loo Out) ILL] More n 4koha Submit Check Out Search the Catalog ................ .......................: Check In Harne, Administration >JdARC Frameworks, BKS Framework Strucfaat ,Tag 260 SD60eld Structure MARC subfield structure admin for 260 (framework BKS) This screen shows the subfields associated with the selected tag. You can edit subfields or add a new one by clicking on edit.
Configuring the Cataloging Module Editing labels of fields or subfields To edit how a tag or subfields is labeled in the cataloging screens, edit the field Text for librarians. Making a field or subfield mandatory To make a tag or subfield mandatory simply check the box Mandatory in the Basic Constraints block. Advanced constraints Click on the link Display more constraints below the Basic constraints block to display Advanced constraints.
Chapter 5 Summary In this chapter, we used three tools to make cataloging simpler and to control data entry: MARC Frameworks Authority Control Authorized values Developing an effective configuration plan in advance is important. There are cost implications to using Authority Control. You will need to incorporate your process of using Authority Control in the configuration plan.
6 Configuring the Circulation Module In this chapter, we will learn how to configure Koha's circulation module. This module is used to loan library items to the patrons. Our goal will be to map the library's circulation policies to rules and preferences in Koha. A library's circulation policies govern loan periods, renewals, membership duration, fines, holds, reference material, and so on.
Configuring the Circulation Module You can find the Patron Category Administration screen in the Patrons and Circulation section in Koha's Administration module. Patrons Circulation Mar.. -earr.h 4koha NO_LIBRARY_SET 50 kohaadmìn (Log Out) .arclr Search Patron Categories Check Out Search the Catalog Home ,Administration >Patron Categories System Preferences . System Preferences Basic parameters Libraries and groups Funde and budgets .
Chapter 6 Here are some examples for different types of libraries: Public library: In a public library, these categories might be suitable: o Adult Child Student o Staff o Institution o o Academic library: In an academic library, these categories might be suitable: o o o Under graduate student Post graduate student Faculty Commercial library: In a commercial library, you might create categories like these: o Plan A: Rs. 250 a month o Plan B: Rs. 500 a month Plan C: Rs. 1,000 a month.
Configuring the Circulation Module Field Upper Age Limit Enrolment Fee Mandatory? Instructions Enter upper age limit. Comments No No Enter fee amount. Overdue Notice Required Hold Fee No Select or deselect the checkbox. No Enter Fee Amount. Category Type Yes Choose from list of values. This fee will be charged when first enrolled. Controls if due and overdue notices will be sent to patrons of this category.
Chapter 6 Circulation Patrons Search 4koha NO_LIBRARY_SET (Setj More. Check In Check Out kohaadmin (Loa Out) I L Search the Catalog Home ,Administration >Item Types Administration System Preferences System Preferences Bask parameters Libraries and groups Funds and budgets Currencies and exchange New ltemType Item Types Administration Image Code Elk. Description , Not for loan Renewable.
Configuring the Circulation Module Here's a good example of Koha's default Item type list: Books Reference Journals Reports CD /DVDS Creating Item types To create a new item type we use the New Item Type button.
Chapter 6 Circulation and fine rules In Koha, for a combination of library or branch, patron category and item type, you can specify: Loan period Fine amount Maximum checkouts In addition, for a combination of library or branch and patron category, you can also specify: Maximum checkouts The second type of rule is used to constrain the total number of checkouts across all item types.
Configuring the Circulation Module Identifying circulation and fine rules Unless your library is just starting up, you will already have your list of circulation and fine rules. However, you might consider modifying the list to take advantage of some of Koha's capabilities.
Chapter 6 Library or branch Patron category Item Type Loan Period Fine Amount Current Checkout Allowed Default Library C Student Student Default Default 21 5 5 14 10 3 The first rule above can apply to Library C as well; however Koha will use the second rule for Library C, as it is more specific.
Configuring the Circulation Module If you have Koha include holidays in the loan period, the due date will be calculated as checkout date plus loan period, if this date falls on a holiday, Koha will move the due date forward to the next working day.
Chapter 6 To configure the calendar, we follow these steps: 1. 2. 3. 4. If Sundays are holidays, click on the nearest Sunday in the calendar and choose option Holiday repeated every same day of the week. If Saturdays are holidays, click on the nearest Saturday in the calendar and choose options Holiday repeated every same day of the week. For holidays that repeat every year on the same date (for example, Christmas), click on the date and choose option Holiday repeated yearly on the same date.
Configuring the Circulation Module Cir.:teat:on Patrons Seirch 4koha More y NO_LIBRARY SET ac I kohaadmin (Loa Out) I j Search Search System Preferences - Check Out Search the Cataloq Home ,Administration > System Preferences New Preference Admín System preferences admin Acquisitions Circulation preferences Preference Enhanced Content Circulation AllowOnSheltHolds Allow hold requests to be placed on items that are not on loan O ON Edit Delete ',ono l Ldril Delete ON O tee `.
Chapter 6 Preparing to configure due and overdue notices To configure due and overdue notices, we will need to prepare a plan. We will need to identify which patron categories will receive notices, how many notices will be sent and when, and what the content will be in each notice.
Configuring the Circulation Module Editing notices The Notices screen can be found in the Tools section. The following screenshot shows the notices templates: Circulation Patrons r,t,re e Seao:h 4koha NO LIBRANY_SET raa I kohaadm
Chapter 6 Circulation Patrons Sealcn JC o h a 4koha NO_LIBRARY_SET Sei ,dore i Check but Search Notices Search the Catalog Search ------- I kohaadmrn (Log Out] 11211 I . Harne 'Tools Notices > Modift notice Modify notice Kohn modale: _...... ...... . Uca!ancr. Code: OOUE Name: Message Subject: Item overdue Message Body: Dear !brailanf_rslnama L: btu i:rSU reame .:b: ar:anEmailaddroes BRAT h. HES - -- ranches bra nchcode anrhes.
Configuring the Circulation Module Editing notice triggers Notice triggers screens can be found in the Tools section. Here we configure, for each patron category when each notice should be e- mailed. mutation Patrons Search 4k©ha More NO LIIdNARY SET (gi) I kohaadmin (Log Gut) la Submit Check Cut Check In Search the iCatelag Home .15515.
Chapter 6 Configuring holds Replace this with "Finally, let us turn our attention to holds. Using Koha's holds feature, patron can request that certain items be reserved for them. Holds are usually placed on items that checked out. Once an item is placed on hold for a patron, the patron needs to pick up the item from the library within a specified number of days failing which the hold is cancelled and the item is made available for circulation. We configure holds in Koha using system preferences.
Configuring the Circulation Module Circulation Patrons Search 4koha Moran NO LIBRARY_S'ET I Search System Preferences Check Out I kohaadmin {Log l'ut) Search Search the Catalog Home ,Administration > System Preferences New Preference_,, Admix System preferences admin Acquisitions all preferences _.......
Chapter 6 Summary Circulation is arguably the most important function in a library. In this chapter, we learned: How to map a library's policies to Koha's rules and system preferences. Patron categories control enrolment duration, age restrictions, and circulation and fine policies for different groups of patrons. Item types control renewals, not for loan, and circulation and fine policies for different types of material in the library.
Configuring Other System Preferences In this chapter, our goal will be to complete the application configuration and be in a position to use Koha in a test or production environment.
Configuring Other System Preferences Koha's global system preferences module The Global system preferences module can be found under Koha Administration. Circulator Patrons Search 4koha li ru r Department of Library and Information Stiance Çpr:. :i:. le¿rl:: cali I aeslabe ILcy7.
Chapter 7 Using system preferences Here are some key points to note about using these preferences: These preferences apply to the whole system; it is not possible to have different choices for different libraries, patron categories, or other types of divisions with your library. Access to system preferences should be controlled. Changes to these preferences can significantly alter system behavior.
Configuring Other System Preferences Configuring patrons preferences Let us start by learning about patrons- related system preferences. These preferences can be found under the Patrons tab. Patrona Circnlat :on More Sean -.h 4koha Department ai library acrd Information Sciences f, Seich System Presences .. ^.ht
Chapter 7 System preference BorrowerMandatoryField System preferences tab Patrons Description Default values Instructions Mandatory fields when creating a patron record zipcode I surname I It is important to pay attention to this preference. Ensure that fields that you will need, e-mail address for instance, are made mandatory. This way you will not have to correct patron records at a later date. cardnumber Add fields separated by " " Fields are column names in database table "borrowers ".
Configuring Other System Preferences System preference autoMemberNum borrowerRelationship System preferences tab Patrons Patrons Description Default values Instructions Whether to auto calculate the patron number On Koha generates a running sequence of numbers. Relationships between guarantee and guarantor, used for Child patron type. father I [116] mother If you wish to generate card numbers outside of Koha turn this preference Off.
Chapter 7 System preference memberofinstitution System preferences tab Patrons Description Default values Instructions Whether patrons can be linked to Institutions Off Turn this preference On, to link patrons of type Professionals to specific institutions. You will need to set up a patron category for institutions, and then create patron records for various institutions.
Configuring Other System Preferences Tracking of late or missing orders Generation of claim letters Unlike Cataloging and Circulation, relatively fewer libraries use Koha's Acquisitions module, instead they prefer to manage the process manually or on some other system. Perhaps for this reason, Koha's Acquisitions module is a simple module and has few system preferences. These preferences can be found under the Acquisitions tab. elation Patrons Search M»re n 4koha i NO_LIBRARY_SET ( _.........
Chapter 7 Here is an explanation of the Acquisitions preferences with instructions on how to configure them: System preference acquisitions emailPurchaseSuggestions System preferences tab Acquisitions Acquisitions Description Default value Instructions Whether to use budgets or not normal Set to "normal" to use budgets. Set to "simple" to make Whether to have purchase suggestions Off acquisitions without budgets. Turn "On" to use e -mail.
Configuring Other System Preferences In version 3.02 there is no serials or subscriptions category. You can find related system preferences by searching for the term subscriptions. Ciro.
Chapter 7 System preference System preferences tab Description Default value RenewSerialAddsSuggestion Serials Whether to add a new purchase suggestion when renewing a serial Off Additional information Turn this on, if you want a way to remind the acquisition staff to renew the subscription with the vendor. A new purchase suggestion will be listed in the Manage suggestions module under Acquisitions.
Configuring Other System Preferences Configuring OPAC preferences Koha's Online Public Access Catalog (OPAC) is not just an online catalog; it is also a self service tool for the patrons.
Welcome to Koha... Text added to OPAC Main User Block stem Preference. My OPAC Credits These preferences allow us to change OPAC content without having to edit the files on the server. It will help to have some HTML skills to maintain this set of preferences. With HTML you can format the content with color, emphasis, fonts, and font sizes.
Configuring Other System Preferences System preference System preferences tab Description opacheader OPAC Contents at the top of the OPAC page Default value Instructions Enter HTML contents, something like:
Welcome to my library < / h3> OpacMainUserBlock OpacNav opacsmallimage OPAC OPAC OPAC Contents in the middle of OPAC home page Contents in the navigation block to the left of the page in the Welcome to Koha ...
Important links here. Enter HTML contents.
My Website Welcome to Mlle... Log in to Your Account: Text added to OPAC Main User Block System Preference. Login. _._....__. ......... .........................._____ Here are the preferences along with instructions on how to use them: System preference OpacAuthorities System preferences tab OPAC Description Default value Instructions Whether to display On This will allow you to search the Authorities records.
Configuring Other System Preferences System preference OpacTopissue System preferences tab OPAC virtualshelves OPAC OPACShelfBrowser OPAC Description Default value Instructions Whether to display the "Most Popular" link below the Search box on the OPAC Whether to display the "Lists" button in the mast head of the OPAC Whether to enable the Off The link will display a listing of items that are circulated most often.
Chapter 7 Description Default value Instructions opacuserlogin System preferences tab OPAC Whether to allow user login in the OPAC On If you turn this on, you will need to shoulder the burden of administering user names and passwords. Initial passwords will have to be distributed in a secure manner. You might get ongoing password reset requests.
Configuring Other System Preferences System preference RequestOnOpac System preferences tab OPAC Description Default value Instructions Whether to allow patron holds on the OPAC On You might want to turn this off if most of your patrons do not have access to the OPAC and you maintain hold requests outside of Koha.
Chapter 7 Search .I..tt e R0.;yry(, top( INSeck, Important links here. Building a virtual library O Normal View EN MARC View OiErc ctr: MARC .Wew TR' Add to Your Cart by Hanson Ardis' Levin. Bruce Lubotsky. Search for this title in: Type'. gEisce, Publisher: ie nl:':oeen Seifeeee fui,. cTCel ÿitet ISBN: IeSI Llpran££.LV.'Lotl9S.111 - Other Databases ïfîemnk r .g F _rn+sn [s[HS (' R let d áUfle4ts 'i $IAçaa .._ q.._ x..... asanejo TIUSrä- ......,....e-:...
Configuring Other System Preferences Here is a listing of select enhanced content preferences along with instructions on how to set these up: OPACFRBRizeEditions OPACAmazonEnabled System preferences tab Enhanced Content Description Default value Instructions Whether to display Book Jackets and reviews from Amazon Off To get this to work, you will need to set values for the preferences AWSAccess KeyID and AmazonAssoc Tag. Get the key and tag from here: http://aws. amazon.com.
Chapter 7 OPACFRBRizeEditions OPACFRBRizeEditions System preferences tab Enhanced Content Description Default value Instructions Whether to display an editions tab in the item details page Off To get this to work you will need one of the FRBR Web Services listed below turned on.
Configuring Other System Preferences OPACFRBRizeEditions ThingISBN XISBN System preferences tab Enhanced Content Enhanced Content Description Default value Whether to use Off the ThingISBN web service to populate the editions tab Whether to Off use the OCLC xISBN Web Service to PINSEISBN Enhanced Content populate the editions tab Whether to use the OINES TagsEnabled Enhanced Content To use this system preference you will need to first turn on OPACFRBRize Editions.
Chapter 7 These preferences related to: Themes or templates: These are a broad set of elements - style sheets, JavaScript programs, or header and footer programs - that control not just styling and appearance but also the behavior of the screens. Stylesheets: Stylesheets are CSS files, and in some cases XSLT files that relate to a narrower set of styling and appearance elements - font, color, font size, or background images. To use these preferences effectively you will need some HTML and CSS skills.
Configuring Other System Preferences Here is a listing of OPAC styling- related preferences along with instructions on how to set them up: System preference System preferences tab Description Default value Instructions opacthemes OPAC These themes control the style and appearance and lot of functionality prog The default theme "prog" is available in the folder /kohatmpl /opac - tmpl /. You can copy the default theme folder and create a new theme.
Chapter 7 System preference System preferences tab Description opacstylesheet OPAC This contains the Web Default value Instructions This is useful if the stylesheet you want to use is maintained on a different server. Specify the full URL including the http : //, something URL of a stylesheet that will override the default stylesheets of Koha like: http://mysite. com/css/ mystylesheet. css.
Configuring Other System Preferences System preference System preferences tab Description Default value Instructions XSLTResultsDisplay OPAC This Off The XSLT stylesheet preference allows you to decide whether to can be found at / koha- tmpl /opactmpl /prog /en/ xslt /. use XSLT The file name is: stylesheets or regular MARC21s1im2OPAC CSS ones Results.xsl.
Chapter 7 Circulation Patrons Search NO_LIBNARY_SET ( kohaadmin (Lág_CgE1) Mare 4koha is Search System Preferences _ Check Out hi Search the Catalog Home , pdenínistration . System Preferences Nev Preference Admìn Acquisitions System preferences admin StaffClient preferences Preference Enhanced Content Value Explanation .....................
Configuring Other System Preferences System preference intranetstylesheet System preferences tab Staff Client Description It contains the Web URL of a stylesheet that will override the default stylesheets of Koha. Default value Additional information This is useful if the stylesheet you want to use is maintained on a different server. Specify the full url including the http: something like: //, http://mysite. com/css/ mystaffstylesheet. css.
Chapter 7 Koha can send messages to patrons via e-mail or SMS. Most Koha libraries use e -mail. We are already familiar with setting up overdue notices and trigger from previous chapters. In addition to overdue notices Koha can send other types of messages on upcoming events, when holds are fulfilled, or when items are nearly due. Libraries can choose to allow patrons to set their individual messaging preferences or the Library staff can set these up for patrons.
Configuring Other System Preferences Here is a listing of messaging -related preferences along with instructions on how to set then up: System preference EnhancedMessagingPreferences System preferences tab Patrons Description Default value Additional information Whether to allow enhanced messaging preferences Off With this turned on, an additional Messaging tab becomes available in the OPAC and the staff client.
Chapter 7 System preference AutoEmailPrimaryAddress System preferences tab Patrons Description Default value Additional information The default patron email address to use when sending messages Off A patron record may have one or more e-mail addresses. This preference controls how the e-mail address is selected. Select email if you want the home e -mail to be used. Select emailpro if you want the office e -mail to be used. Select B_email if you want the alternate e-mail to to be used.
Configuring Other System Preferences System preference KohaAdminEmailAddress System preferences tab Admin Description Default value Additional information This root@ address is used to both send and receive localhost Make sure this is set to a valid e-mail address. It is also a good practice to set up e-mail addresses for each library in Libraries, Branches and e -mails Groups under Administration.
Chapter 7 Circulation Patrons Search NO_LIBRARY SET ((St) I kohaadmin (Log Out) I III More xi 4kaha Search I Search System Preferences i Search the Catalog gidack Out Howie .Administration System Preferences I Admin Acquisitions New Preference System preferences admin Admin preferences Preference Enhanced Content Autoberation Cataloging De bugLevel Define the level of debugging information sent to the browser when errors are encountered (set to It in production). 0=none, 1=some, 2=most ..
Configuring Other System Preferences System preference Description Default value Instructions IndependantBranches System preferences tab Admin Whether to increase security between multiple libraries or branches setup on the system Off AutoLocation Admin Whether to block access to the staff client from unauthorized IP addresses Off Staff with super librarian privileges will not see any difference.
Chapter 7 Configuring search preferences The catalog search tool is available on both the OPAC and the staff client. It is the most frequently used tool. Although the default search -related system preference should work for most libraries, it might be a good idea to consider changing some of these preferences to better tailor the search to your library's needs. The search related system preferences can found under the Searching tab.
Configuring Other System Preferences Here is the explanation of the search -related preferences along with instructions on configuring them: System preference AdvancedSearchTypes expandedSearchOption QueryRemoveStopwords System preferences tab Searching Searching Searching Description Default value Instructions Whether to use Item types or Collection codes as search limits in the Advanced Search tool itemtypes Search limits allow one to search within item types or collection codes.
Chapter 7 Summary Here is what we learned in this chapter: How to browse system preferences categories or to find them using the search tool Configuring Patrons, Acquisitions, and Serials preferences Configuring OPAC preferences - static content, tools for patrons, patron access control, and enhanced content Configuring styling and appearance on the OPAC and the staff client Configuring messaging, security, and search related preferences This completes our application configuration work and we ready to us
8 Test Driving Your Koha Installation We have completed the server setup and the application configuration. We are now in a position to take our Koha installation for a test drive. We will look to complete a transaction cycle in each of the primary Koha modules: Patrons Cataloging Circulation Acquisition Serials We will also test: The reports module The catalog search on the OPAC Patrons create, search, and view patron record Let us first create a patron record.
Test Driving Your Koha Installation Creating a new patron To create a patron record, navigate to the Patrons module using the menu bar at the top of the page and click on the New button in the Patrons home page. You will need to select the appropriate Patron Category first. ,ration Patrons More `äaa.ch 4koha L NO_LIBRARY_SET (5:;Ìt) I kohaadmin (LOO cut) I LLI 1 order by Search Patrons Cher, Ott Surname ...............
Chapter 8 Searching for a patron Let us make sure the patron has been saved successfully. Use the Search Patrons tab under the search box to search for the particular patron. Circulation Patrons Search 4kaha NO_UBRARY SET Mare n (ail I kohaadmin (i ay Out I ill order by: Surname ............. ___........... . catch the Catalog Search Patrons Home 'Flat= Patron Details tor SaviSa Sirohi (1 ) Savitra Sirohi )1) My Address 1 My Address 3 City 12345578 etr:ltzv3 c S Category.
Test Driving Your Koha Installation Creating a bibliographic record To create a new record, navigate to the Cataloging module using the More drop -down list in the menu bar on the top of the page. Then use the New Record button. You will need to select the appropriate MARC framework first. Circulation Patrons Search More to NQ LIBRARY SET (aoti kohaadmin (Log Out) I )dir E Garalodina Editing Marketing manatiement 1.4 4am a petaTective /PN9p Xatier..
Chapter 8 Creating an item record Once the bibliographic record is created, you will automatically move to the Add Item screen.
Test Driving Your Koha Installation Searching for the record Let us now make sure the bibliographic and item records are saved properly. Use the Search the Catalog tab under the search box to search for the record you just added. Circulation Patrons Search 4koha M ND_LiDRARY_SET i5at,, I kohaadmin (Log Dug 112 j nit heck In The..
Chapter 8 Checking out First navigate to the Circulation module using the menu bar on the top of the page. Then enter the name of the patron or the patron's card number in the search box. Make sure you are using the Check Out tab under the search box.
Test Driving Your Koha Installation Checking in To check in, use the Check In tab under the search box. You will need to enter the item's barcode. Circulation Patrons Search 4kaha Mere e Business Administration Library Set I kohaadmin utnut Check Out Nome. Circulation Cvt) 11.11 name earch t e Catalo..g Check ln Check In Options Enter item barcode w Submit ...
Chapter 8 Circulahon Patrons Semen 4koha I Business Administration Library (WI osslabs ILOVA I al More a order by Surname Search Patrons Check Out Search Search the Cutyag Home Patrons Reading Record tor Saida Sirohi Sentira Sirohi F' Ede 'KC chila CesagePoseecel '7. Pm* (23529001223685) Reading Record Ssrnstng Last HO !terra Show,4_41Ligma Airthg4 idsdoung kr dunindis COHN. Bandode Wombat OfitenoWahl Date Due Rearm Date 09 30 2013 34142110 bec630.
Test Driving Your Koha Installation Creating budgets Navigate to the Funds and budgets section under Koha Administration. First create a Fund by entering a code, a name and optionally, indicate to the library what the fund is for. Then click on the Add Budget link. Enter the Fund and the Budget amount. Optionally, enter in the Library what the budget is for and the Start date and End date.
Chapter 8 Circulation Patrons 4koha Burines Administration Library Cast) i kehaadmin (.
Test Driving Your Koha Installation Receiving shipments To receive a shipment, click on the Receive Shipment button. Circulation Patrons Search 4kaha More r Business Administration Library (Set) I osslabs (Loa Out) I L21 ........... t Vendor Search . Home, Acouisitions Search for Vendor Late orders Manacle soogestions Fonds and Budgets 'le. Van,: r .... Test Vendor Order Re,r.e 1.-dp klana;ie Orders...
Chapter 8 Viewing budget utilization Finally, let us take a peek at the budget figures; the Spent and Avail amount will be automatically changed to reflect the order you just closed. Circulation Patrons Saar.
Test Driving Your Koha Installation Fields with labels in red are mandatory. Here are the steps to entering subscription details: Select a vendor by using the Search for a vendor link Use the Search for Biblio or the Create Biblio links to link a bibliographic record to the subscription 3. Choose whether you want an item record for each issue or not 4. Enter other details such as Call Number and Library the subscription belongs to 1. 2. Here are steps to Serials planning: 1. 2.
Chapter 8 Searching for the subscription Let us make sure that the subscription is saved successfully. Use the Search Subscriptions tab to find the record. Enter either the ISSN or the Title of the subscription and click on the Search button. Circulation Patrons Search 4koha Business Administration Library (Sat) I kohaadmin Mare , . a¢h Title ISSN Search Subscriptions Check Out Search the Catalog Home , Serials , Details for Subscription #1 ............_..__ ..............
Test Driving Your Koha Installation Receiving an issue When the issue arrives in the Library, the staff needs to update the subscription record to account for this event. To receive an issue, we use the Receive button as shown in the previous screenshot. Cnrulatrn Patrons Snore 4koha Murr ISSN Business Administration Library Search :........................................._Title: Search Subscriptions et I koh,admin (Log Cu) a I 1.
Chapter 8 We go through the following steps to create the report: Select the module that we want to query. 2. Choose the display format. 3. Choose a set of fields for the reports' columns. 4. Set selection criteria or limits. 5. Configure how you want data to be totaled. 6. Choose how you want the report to be ordered. 1. Click on the Finish button to create the report. You will need to save the report before using it. Circulation Patrons Search 4koha Business Administration Library (-.3..
Test Driving Your Koha Installation Using a saved report To test the report you just created click on the Use Saved button on link. Click on the Run this Report link to execute the report. You also have an option of downloading the report in a comma separated format. The file can then be opened in a spreadsheet program for further analysis.
Chapter 8 e,ncarae. i Leg Pet My OPAC Header kotier" returned 2 results ' 8 Refkreyorn search Availability Limito ç::rreralr"..ev;l;ghlr .L-. -¡! Addta Marketing urar:agalnent : an Asian nerserective _... Publication - Fr :: it Pell . -r_ Date ::'.:l A vailebl @y: Copies available: Dunb ces A:Realistretan Lbrard Libraries Pusiness .A9nrvail.atlnn Match: Lama 9 Actions Authors ist a; Ili, Kotler. Ardir r,c to Lists db _. 4Coal te Cart Marketing inar:agenyent: arLalysis.
9 Migrating Catalog Data Migrating catalog data from the legacy system is a prerequisite to using Koha for most libraries. The process involves exporting MARC records from the legacy system and importing them into Koha using Koha's import tools. Migrating bibliographic data is usually easy; holdings data, however, presents a few challenges. This stems from the fact that different library systems record holdings data in different ways -fields and subfields used for an element may be different.
Migrating Catalog Data Understanding MARC files We will need to convert MARC files exported from the legacy system, which have an extension . mrc. Let's understand more about the structure of such files: Records: Each MARC file will contain one or more MARC records. Each MARC record contains bibliographic data and one or more holdings fields. Bibliographic data: Each MARC record contains bibliographic data, such as title, author, ISBN, or subject.
Chapter 9 Some 952 subfields are very important from a Koha perspective. These include: 952$a - Permanent location: This is the home library or branch of the particular item. It is important for circulation purposes that this subfield should have a valid library code. 952$b - Current location: Usually the same as home library or branch; this too must have a valid library code. 952$y -Koha item type: Item types are used for setting up circulation rules. This field must have a valid item -type code.
Migrating Catalog Data MARCEdit A very popular tool used to view and edit MARC records, and convert them from text to MARC and vice versa. The software is free to download and use, but runs only on Windows. MARCEdit is available for download at this link: http: / /people . oregonstate . edu /- reeset /marcedit /html /downloads.html.
Chapter 9 Bulkmarcimport.pl option Mandatory? Explanation Example fk No -fk n No o No commit No t No s No When importing records, values for fields such as library code (952$a) need to be present in the Koha database. Use this option to turn off such checks during imports; records will be imported even if the corresponding data is not present in the database. The number of records to import from a file, if not used all the records are imported.
Migrating Catalog Data Bulkmarcimport.pl option Mandatory? Explanation Example c No -c d No m No x No Y No idmap No The characteristic MARC flavor of records in the import file. Default is MARC21. Deletes all catalog records in the database prior to importing the file. Be very careful with this option, there is no way to recover lost records. The format of the records in the import file. Default is ISO2709, if you are importing XML, use the MARCXML option.
Chapter 9 SAMPLE: $ export KOHA CONF= /etc /koha.conf $ perl misc/migration_tools/bulkmarcimport.pl -d -commit 1000 \ -file /home /jmf /koha.mrc -n 3000 Koha's GUI import tool Koha also is an end -user -friendly GUI import tool.
Migrating Catalog Data Record matching rules can match the incoming records to those already in the database. These rules can be used to: Add holdings to existing bibliographic records Replace bibliographic records with new ones Choosing an import tool Here are some pointers to help you decide which tool to employ when importing MARC files: In general, bulkmarcimport .pl is better when you are setting up Koha for the first time. It is faster and can handle large files.
Chapter 9 Mapping Koha's holdings subfields to subfields in source MARC file In the first part of the plan, we set up a table listing all of Koha's holdings subfields. We map each subfield to a corresponding subfield in the source file. If corresponding fields for any mandatory Koha fields are not available in the source file, we will need to add data manually for such subfields while editing the file.
Migrating Catalog Data Planning setup of administrative fields in Koha In the second part of the plan, we plan how to setup values in Koha's administrative fields. We need to ensure that libraries, item types, collection codes, and shelving locations in the various MARC records in the source files are setup in Koha prior to importing the file.
Chapter 9 Migrating catalog data In this section, we demonstrate how to implement our migration plan. We edit the source file using MARCEdit, setup administrative fields in Koha, and then use either the bulkmarcimport . pl or the GUI import tool to complete the migration. Setting up values in Koha's administrative fields First, we need to make sure that we prepare the Koha database for importing the new records by setting values in administrative fields, such as library, item type, or collection code.
Migrating Catalog Data Setting up Item types The Item type(s) can be setup from the Item Types page under Koha Administration. Circular cri Patrons M_ra Search 4koha NO LIBRARY SET; Chad, Ont Check In Search the Catalog _._ .... .......................____.... timoe :.
Chapter 9 Setting up collection codes The collection code(s) can be setup from the Authorized values page under Koha Administration. Add values to the category CCODE. Circulai or Patrols Search 4 koha Business Administration Library (a.%). I postage (I co add 1W M. ,Qineni_uf Roturo Co rl Search the Catalog duCiR Amin chaton, alialOakaa VaalaS System Preferences %LULU MJSZA Basic parameters idhares argi moos timetednonzedidue for CROCE Authorized values This table toned in MARC definition.
Migrating Catalog Data Setting up shelving locations The item type(s) can be setup from the Authorized values page under Koha Administration. Add values to the category LOC. cartnttr COculatiso Seam,: More e Business Administration Library iSei) I cssiabs j[doi Oczt I [ Zj 4ko ha reneW th:: utalog Hem, !,...q.:33:na!uttän :Autkoriosd4aitle, Neu. sJJ.:: System Preferences Sv.e,r: Authorized values Basic parameters This teOe :s ...sad in MARC &Oration Cal can define as :Uwe. g::::LTY ca.
Chapter 9 Use the MarcBreaker tool to convert the MARC file into a readable file with the extension . mrk. Click on the Edit Records button to view the records. Use the various options under MARCEdit's Edit and Tools menu to create the file as per Koha's standards. Here are instructions on some of the key operations you are likely to need-swapping subfields, adding a new subfield, and merging subfields: Jr-fnikH-rrwa-.mr. File ErLt Fortb T ReFfs s RE4KJa Cataktg CatcJlato( 19i: =LDP, 01659pa.
Migrating Catalog Data Swapping subfields To swap fields, use the Swap Field Data tool under the Tools menu. Here are the steps to swapping subfields: 1. 2. 3. Fite Eft Specify Field and Subfield for the Original and Modified data. Check Copy Source if you want to retain the original holdings field. Check Add to existing field; this way you ensure that newly swapped subfields are included in the same holdings tag. Fonts 1'...] n m '9/ Reports Tools . Piug ms 2_1 £3 4,1 Help V r.
Chapter 9 Adding a new subfield To add a new field, use the Add/Delete Field utility under the Tools menu. Enter Field as 952, and Field data as \ \ . For instance, to add a 952$a with value LIB1, enter Field data as \ \$aLIB1. -d FN EOIt Fpnta Reports T00.13 Http =LDR 0'859pam 22020'3a4-5(2 =0C1 1CI09376914t =003 'CIF =ir'.5 205323311213153 =008 (4.:J'2s226ti'.rtlnyuat,`,.S:.
Migrating Catalog Data Let's now look at a specific example - merging subfields $h and $i, with a space between the two values, into Koha's call number subfield $o. First, we setup a Find expression as follows: ( =952 \\\\)(1(\$ h)([ a- zA- Z0- 9 .] *)(*)( \$i)([a- zA- Z0- 9.1*)(. *) Here is an explanation of this expression: ( =952 \ \ \ \): Look for the pattern =952 \ \.
Chapter 9 Here is an explanation of the Replace expression: $1: In the replace string start with the value in the first back -reference field, the value here is =952 \\ $o: Append the subfield label $o $4: Append the value of the subfield $h that is stored in the fourth back -reference field : Append a space as a separator $7: Append the value of the subfield $i that is stored in the seventh back -reference field $2: Append the text if any, before the $h subfield; this is stored in the second bac
Migrating Catalog Data Once you are done, use the Compile File into MARC option under the File menu to create your new MARC file. £M7.tE><.iNEXE Eat _ ml _r EOM ù Loots 3.pa*s 4 Pu_stlrs J Sala .J fI =LCR 01F5qpam 22302'3a4'J': =OG' `51,51.7E5-» 17"7 I521= -r5 293803313213153 =058 048712s2C7S`:.lnyval0.50lr50fA1{engti =010 nßa 20040155=57 =020 '.Sa14 02' f 453X =035 'vSa CICrIF',1 à9890 =OSft itSa3LC£cCLC50OLC53IQ3F =00.3 13ae-unan -050 0:$aPR4621562:304 =082 0032E29185222 ,00 1l8aCryla, .
Chapter 9 To import a file, we run the command as follows: linux- 4yut: /usr/ share /kohaclone /mist /migration_tools # . /bulkmarcimport. pl -d -file /home /koha /Download /sample -marc deleting biblios 300 322 MARC records done in 15.4088408946991 seconds Note the use of -d option; this deletes all the data in the catalog before importing the file. Importing catalog records using the GUI tools You can use Koha's GUI tool to import the MARC file.
Migrating Catalog Data Koha comes preconfigured with two matching rules, one that matches on ISBN, and the other on ISSN. By using matching rules, you can make sure that all items or copies are grouped under the same parent bibliographic record. Here are the steps to staging your MARC file: Select the MARC file, and click on Upload to load the MARC file. 2. Select the matching rule (ISBN for books and ISSN for serials). 1. Set Action if matching bibliographic records found to ignore. 4.
Chapter 9 At the end of the process, Koha will let you review the records before you actually import the records. Managing records In this step, the records will be imported into Koha's database. Simply click on the Import into Catalog button to start the process.
Migrating Catalog Data Once the import completes, you will see a summary of the import.
Chapter 9 Summary Here is what we learned in this chapter on migrating catalog data from MARC compliant legacy library systems: Using MARCEdit to manipulate source MARC files Adding, merging, or swapping holdings subfields Setting up administrative fields in Koha prior to importing MARC files Using bulkmarcimport . pl and the GUI import tools This completes the implementation section of this book. In the next chapter, we will learn how to troubleshoot installation and migration problems.
10 Troubleshooting In this chapter, we will look at ways to troubleshoot problems with our Koha installation. If you are responsible for ensuring the availability of your Koha installation, troubleshooting is a key skill that you will need to develop. You may face problems during installation, during upgrades, or when users use the system in new ways.
Troubleshooting Where to get help community resources There are several tools and resources that you can use to get help from the Koha community. In this section, we will point to you these resources. Koha's mailing lists You should join the main Koha list; this is the users list, it is very active, and is the best way to get support from the community. You can consider joining other specialized lists, depending on your interest. You can join the lists via this page: http: / /koha -community.
Chapter 10 Koha's IRC chat If you need to chat with Koha developers in real time, you should use the IRC chat. You can join the chat via this page: http://koha-community.org/support/. The IRC server is irc . kat ipo . co . nz and channel is #koha. Koha's bug tracker Koha's bug tracker is available at this URL: http: // bugs .koha- community.org /bugzilla3 /. Welcome to Bugzilla Q Y axa Y,íf.wßxa.
Troubleshooting Koha's Git repository A web display of Koha's Git software repository is available at at: http://git.koha-community.org/. This is the version control repository for the K,ha s:ro:e: it To clone a repository and start working on Koha or its doco:nentation posse install lit and run .__ clone git:; -aen kc s- conmurity a%aase_e_neccsito =Ynit Fer example. gut 0005 . .ftgit .serin- carnurit3.cng.kc`uo.0it Connut statistics are wadable for Kohd : roasts. 'ranch -Jp.,, F:;` ....
Chapter 10 Apache2 web server is down If the Apache2 web server is down, you will not be able to connect to the server; you should see something like this. Unable to connect Firefo< cant establish a connection to the server at 127.0.0.2. The site could be temporarily unavailable or too busy. Try again in a few moments If you are unable to load any pages, check your computer's network connection If your computer or network is protected by a firewall or proxy, make sure that Fret .
Troubleshooting To make sure Apache2 starts at boot, we use the chkconf ig command with the on option: koha @linux: - # sudo chkconfig apache2 on Let's run a test once again to see if the configuration is correct: koha @linux: /home /koha # sudo chkconfig apache2 apache2 on There could be other reasons for the problem, of course; look at the Apache2 log files for clues.
Chapter 10 The unused message above indicates that MySQL is down. To bring the database server up, we execute the start command: koha @linux: - # sudo /etc /init.d /mysql start done Starting service MySQL As with Apache2 on openSuSE and similar distributions, MySQL may not have been configured to start up at boot time.
Troubleshooting Zebra search not returning any results Another common problem is Zebra searches don't return any results. The No Result found message looks perfectly innocuous. Maybe you don't have a match for the search term. But if this happens for search terms you know should return results, then the first thing you should look at is the Zebra server. My OPAC Header No Result found ! No results match your search for "a" in My Library Name Catalog. My OPAC Credits L'dnoUSi)a`,.°3: cs:*ri.
Chapter 10 The output this time tells us that there is an active zebrasry process. A common reason for the Zebra server being down is that it is not configured to start up when the machines reboots. On Debian, we use the update -rc .d command to set this up: linux -4yut: /home /koha # sudo update -rc.
Troubleshooting If you do not see rebuild_ zebra.pi executing in the log file, then you know that there is problem with the Crontab configuration. To view how the Crontab is setup, we use the crontab command with the -1 option: koha @linux: /home /koha # crontab -1 A properly configured Crontab will look something like this: PERL5LIB= /home /koha /kohaclone KOHA CONF= /etc /koha -dev /etc /koha- conf.xml */1 * * * * perl / home / koha /kohaclone /misc /migration_tools /rebuild_ zebra.
Chapter 10 LJórary CataWg harry potter rt -aq -bu.l Error: ut18'\xC3" does not map to Unload, at lusrtlib /per15/5.8.8/1386- linux- thread- multi/Encode.pm line 174. In this type of situation, you should check the SAX parser setting. We do this by executing Koha's SAX parser print program /misc /sax_parser_print .pl: koha @koha @linux: -> cd /home/koha/kohaclone/misc/ koha @ linux: /home /koha /kohaclone /mist # ./sax_parser_print.
Troubleshooting Overdues e -mail not working In our experience, problems related to overdue notice e-mails are fairly common. This is a more complex problem to troubleshoot, as there are a whole set of things that need to be in place. Reviewing notice triggers Overdue notices may not work correctly if they are not setup correctly in the Notice /status triggers section under Tools. Make sure the Letter and Delay is setup correctly for the Patron Category in question.
Chapter 10 Circulation Patrons Search 4koha No_LIgRANY SET ad I kahaadmin 0.541_21.0 I ai More E, n n n u Search Search Patrons Check Dut F Search the Catalog Home > Patrons >Patron Details for SavItra Sirohi (1) ..........
Troubleshooting To view how the Crontab is setup, we use the crontab command with the -1 option: koha@linux:/home/koha # crontab -1 A properly configured Crontab will have the Koha -related environment variables setup: PERLSLIB=/home/koha/kohaclone KOHA CONF=/etc/koha-dev/etc/koha-conf.xml And, the 30 6 pl * * cronj ob should be setup as follows: * perl / home /koha /kohaclone /bin /cronjobs /process message queue.
Chapter 10 If the Crontab configuration is fine, try running the overdue_notices .pl program from the Linux shell for clues: koha @ linux: / home /koha /kohaclone /mist /cronjobs # perl overdue_notices.pl -v -t Fines not working Problems with fines calculations are fairly common as well. Fines calculations may not work correctly if your fine rules are not setup correctly in the Circulation and fine rules section under Koha Administration.
Troubleshooting You might also want to make sure that the fines . pl program is setup in the correctly in the Crontab: koha @linux: /home /koha # tail -f /var /log /messages Jul 14 10:05:01 koha @ linux /usr /sbin /cron[7741]: perl / home / koha /kohaclone /bin /cronjobs /fines.pi) (root) CMD A properly configured Crontab will have the Koha -related environment variables setup, and a Cronjob for the fines .
Chapter 10 Software bugs Sometimes, you may come across software bugs. You can raise such issues in Koha's bug tracker. Often, you will find that someone has already raised a bug report, and a fix is available as well. Here is an example of a bug report on the tracker: Search Bug 4840 - Cost not rotndod Reported 2010 -05 -31 11 45 UTC by Nahuel Angelmette Stut + +c NEu Modified 2010-07 -07 15 4-7 UTC t -1 Product hohe _.
Troubleshooting If a bug fix is available, and if Koha's release manager has pushed the fix into the repository, you will find the patch in Koha's Git repository. ' ts_ c! koha.slit ! shoEttoy summx, I shuxtIng I laa I cmnitmlt 1 ..ar stud.* 1 tree first prey nn -v C dktM1üt v - searh kohe git 7 days ago Nenni- Damian... 7 days ago Nenni -Damien bug3812 :Illegal Date îsé does not match lea forma... sa..
Chapter 10 If a bug fix is available, but has not been pushed into the Koha repository, you can download the patch from the bug reports, and try to apply it yourself. To apply a patch, we use the command git apply: koha@linux: /home /koha /kohaclone # git apply name -of- patch.
Troubleshooting Problems with Internet Explorer Some Koha screens may not display properly in Microsoft's Internet explorer: You can try looking for a fix in the Koha bug tracker or in its Git repository. It is best, however, if you use Firefox, Chrome, or other browsers; things should be just fine on those.
Chapter 10 Summary In this chapter, we learned how to troubleshoot application problems. Koha's community tools - mailing lists, IRC chat, Git repository, and bugs repository are a great help. To get you started on Koha troubleshooting skills, we walked you through troubleshooting tasks for some common problems with Apache2, MySQL, and Zebra. We learned how to tackle more complex problems related to overdue notices e- mails, fines, and finding and applying bug fix patches.
11 Updating Software The Koha software is always changing, almost every day. These changes contain bug fixes, minor revisions to existing features, and entirely new features. You should keep the software updated to benefit from these changes. Even if the new versions do not contain changes of interest to you, it is good practice to keep the software updated. If your version falls too far behind the current version, the update process to the latest version is likely to be very difficult.
Updating Software Branches At any given point Koha has at least two main software branches: Stable: This branch is older and is considered stable or bug free for the most part. Only bug fixes are allowed on this branch. Development: This branch is where new features are developed. This branch is ahead of the stable branch, meaning it has all the features of the stable branch and the new features in development. Heads Both branches - stable and development have heads.
Chapter 11 Choosing a version to update to We can choose to move to the head of the stable branch or the head of the development branch or to any tag in one of these branches.
Updating Software Configure Apache2: The new version of the software may have an updated Apache2 configuration file. We will need to configure this new file. Upgrade the database: We will use Koha's web installer to upgrade the database to the new version. Rebuild Zebra indexes: The new software version may contain updates to Zebra configuration files. To have these changes reflected in search results, we will need to do a full rebuild of Zebra's indexes.
Chapter 11 Of the several branches listed in the output above, two are of immediate interest /3 . 0.x and origin /HEAD or origin /master. Origin /3 .0 x is the stable branch while origin /HEAD or origin /master is the development branch. to us- origin If we are on a production server and we are interested only in updates for the stable branch, we will run the git pull command pointing to the stable branchorigin /3.0.x: koha @1i190 -245:- /kohaclone$ git pull origin 3.0.
Updating Software To switch to the master or the head of the branch, we run the git checkout command as follows: koha @li190 -245: -/kohaclone$ git checkout master We see from the output of the git tag command that the latest tag or version in Koha's stable branch is version v3.00.06.
Chapter 11 Set the configuration directory to the directory configuration directory of the current installation: Configuration directory: [ /home /koha /koha -dev] Make sure to specify the current database name here: Please specify the name of the database to be used by Koha [koha] Specify the MySQL user that has privileges over the database: Please specify the user that owns the database to be used by Koha [kohaadmin] Specify the password of this MySQL user: Please specify the password of the user tha
Updating Software Configuring Apache2 Installation of the new Koha version will overwrite Koha's Apache2 configuration /koha -dev /etc /koha -httpd. conf. This is why we will need to configure Apache2 once again. Refer to Chapter 2 for more information on how to configure Apache2. file- /etc Upgrading the database Once we have Apache2 configured we navigate to Koha's staff client to launch Koha's web installer. Here we use the kohaadmin MySQL user to log on.
Chapter 11 Web Installer > Step 3 We are upgrading from Koha 3.00.02.012 to 3. 00.06.010, you must update your database Once the database upgrade finishes, you should be able to log in to the new version of Koha. Zebra rebuilding indexes and restarting the server As a final step we need to do a full rebuild of Zebra indexes in line with the new Zebra configuration files. We also restart zebrasry to load the new configurations. Rebuilding Zebra indexes We run the rebuild_zebra.
Updating Software Summary Here is what we learned in this chapter on updating software: Using git pull command to download software updates Using git branch command to switch to a specific software version Installing the new Koha version using the Make utility Upgrading the database using Koha's web installer Rebuilding Zebra indexes using new Zebra configuration files Restarting Zebra server to load new configurations In the next chapter, we will learn about a related topic - how to make your own modific
12 Customizing Koha Software Most serious Koha users will want to customize the software to suit their needs, perhaps to modify the styling or appearance or to tweak a certain page to show additional information. If you have the skills, you can even take on more serious work, such adding new features. It is best to share the code you create by sending patches to Koha's release manager. Koha's license requires that we share any enhancements we make.
Customizing Koha Software Skills needed Here is a quick overview of the skills needed to customize Koha. If you want to modify styling and appearance, HTML and CSS skills should suffice.
Chapter 12 Template files Let's take a closer look at the related to Koha's screens: koha -tmpl file; this folder contains files and folders -tmpl folder contains two folders - opac -tmpl for the OPAC, and intranet -tmpl for the staff client The OPAC and staff client template folder each contains a theme folder named prog The theme folder in turn contains a language folder - en or f r, depending how you installed Koha Within the language folder, you will find a set of folders j s - containing JavaScript
Customizing Koha Software Understanding Koha's database We also need to understand how Koha's database is organized. This will help us make software changes that require access to the database or that require updates to be made to it. In this section we take a quick look at how to browse the database; we also list some of the important tables. Browsing Koha's database Let's start by logging in to MySQL.
Chapter 12 cardnumber surname I I varchar(16) YES I mediumtext I NO I UNI I I I NULL NULL I firstname I text I YES I NULL I An overview of important Koha tables Here is a quick overview of some of the important tables in Koha, categorized by function. Cataloguing The following three tables are key Cataloguing related tables: Contains bibliographic data such as title or author.
Customizing Koha Software Administration Administrative setting and data are stored in the following tables: Libraries participating in the system itemtypes: Item types are used in circulation rules categories: Patron categories issuingrules: Circulation and fine rules systempreferences: Global system preferences aqbookfund: Funds, budgets are created under funds aqbudget: Budgets under each fund libraries: Serials Serials data is captured in the following tables: subscription: Subscription information su
Chapter 12 Using Git to manage software changes It is highly recommended that the software changes be managed using Git.
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.
Chapter 12 This feature requires the following changes: Modify the CSS file to position the transliteration control Modify the search box on the masthead to accept input in the source language Add the language selector drop -down list to the right of the search box Include a Google- provided JavaScript file; the transliteration is performed by this file Add a new system preference to control the availability of the tool Creating a development branch Lets first create a development branch in which to work
Customizing Koha Software And add the contents of the transliteration file to the file: // Load the Google Transliteration API google.load( "elements ", "1 ", { packages: "transliteration" }) ; function onLoad() var options = Loading the Transliteration JavaScript file Next, we add a block to load the transliteration JavaScript file. We add this block to the doc- head -close. inc file in the koha - tmpl /opac -tmpl /prog /en /includes folder. The doc- head -close .
Chapter 12 Patrons Circulation 4 Oj2 NO_LIBRARY_SET met) kohaadri n (Lag Uuti Mores Search I '? ,I s =_Arch _naglelndicTrensliteratlan Check Out Search System Preferences ! Search the Catalog Home 'Administration y System Froth rrcas , Modify system preference VoogietndicTranalteraEon' Modify a system preference Admire Explanation: Acquisitions Variable: Value: Authonties Cataloging ancel Circulation Koha internal Enhanced Content Variable type: ItBtt.
Customizing Koha Software koha @linux: /home /koha /kohaclone # vi installer /data /mysql/ updatedatabase30.pl We add a block as follows at the bottom of the file. The field $DBvers ion is important; Koha's web installer, when deciding whether to upgrade the Koha database, checks if the database's current version is below the highest $DBvers value indicated in this file. If it is below this number, it initiates the database upgrade process.
Chapter 12 Adding the transliteration tool to the display template Next, we add the code to display the transliteration control on the OPAC pages. We add this block of code to the masthead. inc file in the folder koha -tmpl /opac -tmpl/ prog /en /includes /. The masthead. inc file is included in all OPAC pages that have the Search tool on the top. Let's edit the file: koha @linux: /home /koha /kohaclone # vi koha -tmpl /opac - tmpl /prog /en/ includes /masthead.
Customizing Koha Software Committing changes We will use Git to commit the changes we have just made. First, let's check what files are modified using the git status command: koha @ linux: /home /koha /kohaclone # git status # On branch koha -3.0.2 # Changed but not updated: # (use "git add ..." to update what will be committed) (use "git checkout -- ..." to discard changes in working directory) # # modified: admin /systempreferences.
Chapter 12 # Committer: root # On branch mydevel # Changes to be committed: # (use "git reset HEAD ..." to unstage) # modified: admin /systempreferences.pl # modified: installer/ data /mysql /en /mandatory /sysprefs.sgl Save the comment by using : wq, and the command should exit with a message such as this: [mydevel 4727d7c] This adds the Google Indic Transliteration tool to the OPAC masthead.
Customizing Koha Software Note the use of the word master in the command above; this indicates that the patch should be created against the master branch. By doing this, we ensure that the patch can be applied on the master. The command should exit by creating a single file containing all the changes: 0001 -This -adds- the -Google- Indic -Transliterater -to- the -OPA.
Chapter 12 +++ b/opac/opac-search.pl @@ -581,5 +581,8 @@ if (defined $barshelves) { } my $content_type = ($format eq 'rss' or $format eq 'atom') ? $format : 'html'; +# If GooglelndicTransliteration system preference is On Set paramter to load Google's JavaScript in OPAC search screens +if (C4:: Context -> preference ('GooglelndicTransliteration')) + { $ template- >param ('GooglelndicTransliteration' => 1); +} output_html_with_http_headers $cgi, $cookie, $template ->output, $content_type; 1.6.4.
Customizing Koha Software Summary In this chapter on customizing Koha software, we learned about: The organization of Koha's application folder The structure of Koha's database How to make changes to configuration, database, and application files How to commit changes using Git How to generate patches using Git How to send patches to others using Git In the next and final chapter, we will cover advanced topics, such as LDAP authentication, internationalization, and exposing the catalog to the outside worl
13 Advanced Topics In this final chapter, we will learn about setting up some less widely used but nevertheless important features of Koha. These features are: Creating and using one's own matching rules for catalog imports Authenticating users against an LDAP server Setting up custom OPAC interfaces for each library in your Koha installation Setting up Koha screens in other languages Publishing the catalog via Z39.
Advanced Topics Creating and using matching rules for use during catalog imports Koha's default installation includes two record matching rules for use during catalog imports - one based on ISBN and the other for matching on ISSN. We can also create our own matching rules from the Record Matching Rules section under Koha Administration. Circulation Patrons tAarnr Search 4kaha Business Administration Library (U.) I sadtra.siroh! ULcg Cell I LU Submit Check Out ,.
Chapter 13 To create a new rule we use the New Matching Rule button. Patrons Circulation Search 4 koha ND LIBRARY_SET Capfi I kohaadmin (Log Gott I L' More Submit Check Out Search the Catalog Check In Home . Administration. Record Matching Rules >Add record matching rule System Preferences Add record matching rule System Preferences Basic parameters Libraries and croups Funds.
Advanced Topics Match checks: Optionally 1 or more match checks can be created for each matching rule. These checks compare a field in the incoming record to the same or different field in the records in the database. Think of these as an additional check to ensure records are correctly matched. For instance, if you have a match point on Title, you might want a match check based on author. Search index: This is the Zebra index that is used to match the records.
Chapter 13 Next we look at the file ccl .properties stored in the folder /etc /koha -dev /etc/ zebradb /: linux- 4yut: /usr/ share /kohaclone /misc /migration_tools # vi /etc /koha -dev/ etc /zebradb /ccl.properties If we run a search on the index Local -number, we find an entry as follows: Local- number 1 =12 sn Local- number The index Local -number is present in both these files and we can use it in the Search index field in matching rules.
Advanced Topics Configuring LDAP To configure Koha to use LDAP, we edit the file and add an LDAP block similar to this: /et c /koha -dev /etc /koha -conf .
Chapter 13 8. Set tag to 1 if you want updates to user records on the LDAP server to update user records in Koha as well. 9. The fields listed in the block refer to fields in the borrowers tables in Koha. 10. The fields listed in the block must include all mandatory fields in the borrowers table except the field borrowernumber. Mandatory fields in the table are-surname, address, city, branchcode, and categorycode (patron category code). 11.
Advanced Topics Setting permissions If you use LDAP, you must set permissions for each individual staff user in Koha. To set permissions use the Set Permissions option under the More menu available in the details page for a patron. Çircutatron Patrons Search 4 koha Mor - NO IIBRARY_SET all)1 icheadmm an CO I L^_j weer by baoramp - arch Rarr' Itiante . Patrons. Bet arivlinee for 3,,,i.. C ante Savitra Sirohi )I) My Address 1 Set Privileges for Sirohi, Savitra M- Address 3 City 12346633 baver..
Chapter 13 2. You will need domain names for each branch, for example, branchi . mykohalibrary .org,branch2.mykohalibrary.org. 3. In each virtual host, repeat this stanza, change the values of environment variables OPAC_CSS_OVERRIDE and OPAC_SEARCH_LIMIT appropriately. SetEnv OPAC_CSS_OVERRIDE branchl.css SetEnv OPAC_SEARCH_LIMIT branch :branchi SetEnv OPAL LIMIT OVERRIDE 1 4. Create the corresponding style sheet files in the folder: / koha - tmpl / opac - tmpl /prog /en /css /branchl.
Advanced Topics Installing new languages If you need to have Koha OPAC and staff client screens in another language, you will need to install the particular language. Here are the steps involved: Install Perl module prerequisite Locale: : Po. 2. Check availability of the corresponding language files in the Koha folder. 3. Create new folders for the new language in the appropriate OPAC and staff client folders. 4. Use Koha's program- tmpl _process2 .pl to install the new language. 5.
Chapter 13 We would install the Spanish language file for the OPAC in this fashion: koha@1i190-245:-/kohaclone/misc/translator # perl tmpl_process3.pl install -i ../../koha-tmpl/opac-tmpl/prog/en/ -o ../../koha-tmpl/opactmpl/prog/es/ -s po/es-SS-i-opac-t-prog-v-3000000.po -r Creating language templates for the staff client In a similar fashion, we can create the language templates for the staff client.
Advanced Topics Here are the system preferences you will need to change: language: Use this preference to enable the new language for the staff client opaclanguages: Use this preference to enable the new language for the OPAC opaclangaugesdisplay: Choose whether you want to display a language selection bar on the OPAC c,in.ulahnn Pat = Sevrrh 4k©ha Adora NO_LIBFtARY_SET kohaadmin U og } I j? j arch Search System Preferences Check Out Search the Home ,.
Chapter 13 ,ro 'lad; Cxpttsr. ...,.... Welcome to Koha... My Wehsite Text added to OPAC Main User Block System Preference. My OPAC Credits kdìumxu: Eriq:iü:': ;;_,px'.I Setting up a public Z39.50 server With Koha you can publish your catalog records to the outside world via the Z39.50 protocol. This will allow any Z39.50 compliant client software to search and copy records from your catalog.
Advanced Topics The 9999 after the colon in the lines above is the port the server will listen on. You can change this as well, to something like this: tcp:192.168.1.123:7090< /listen> Configuring the server directive Next we add a server directive. This directive essentially sets up a new Zebra server.
Chapter 13 We just copy this block above and replace the ID biblioserver with publicserver, like so: / etc /koha -dev/ etc / zebradb /ccl.properties < /ccl2rpn> 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.
Index Symbols -a parameter 46 -b parameter 46 -d parameter 46 --help parameter 47 -k parameter 46 -munge -config parameter 1 -nosanitize parameter 47 -noxml parameter 46 -r parameter 46 -s parameter 46 -v parameter 47 -w parameter 47 -x parameter 46 -y parameter 47 -z parameter 46 A acquisitions module about 117 budgets, creating 158 budget utilization, viewing 161 functions 117 orders, creating 159 shipments, receiving 160 testing 157 vendor, creating 158 acquisitions preferences configuring 117 Apache2 a
Authorized values about 71, 72 fields 72 key points 73 B Bulkmarcimport.pl, options c 174 commit 173 d 174 file 172 fk 173 idmap 174 m 174 n 173 o 173 s 173 t 173 v 172 x 174 y 174 bulkmarcimport.pl program using 188,189 bulkmarckimport.pl 172 C c, Bulkmarcimport.
Koha IRC chat 197 Koha mailing lists 196 components, software updates 219 configuration, Apache2 web server. See Apache2 web server configuration configuration folder, Apache2 25 configuration plan, Apache2.
H holds preferences configuring 107 editing 107 idmap, Bulkmarcimport.pl option 174 imports tools, Koha about 171 bulkmarckimp ort.
Koha database about 230 acquisitions related data 232 administration 232 browsing 230 Cataloguing related tables 231 circulation related tables 231 Koha tables, overview 231 patrons related tables 231 serials data 232 structure 232 Koha default Apache2 file 26 Koha features about 91 calendar 99 circulation and fine rules 97 Item types 94 notices 102 patron categories 91 system preferences 107 Koha Git repository 198 Koha installation branch, checking out 12 common problems 198 completing 21 configuring 20 i
new framework, creating 84 subfields, editing 85 matching rules understanding 247, 248 matching rules for use during catalog imports creating 246, 247 using 246, 247 messaging preferences, Koha AutoEmailOpacUser 140 AutoEmailPrimaryAddress 141 configuring 138, 139 EnhancedMessagingPreferences 140 migration process preparation, catalog data administrative fields setup, planning 178 holdings subfields, mapping to subfields in source MARC file 177 multiple OPAC interfaces 252 MySQL configuring 61 MySQL databas
patron, searching for 151 testing 149 patrons preferences autoMemberNum 116 BorrowerMandatoryField 115 borrowerRelationship 116 configuring 114 ExtendedPatronAttributes 115 memberofinstitution 117 patronimages 117 PERL5LIB environment variable setting up 64 Perl modules installing 223 installing, CPAN used 17 persistent environment variables setting up 64 prerequisites, Apache2 configuration about 31 DNS 31 host names 31 IP addresses 31 open Firewall ports 31 public Z39.
switching, to new software version 221 source MARC file editing, MARCEdit used 182,183 new subfield, adding 185 subfields, merging 185,186,188 subfields, swapping 184 Spanish language, installing in Koha example 254 language templates, creating for OPAC opacheader 124 OpacMainUserBlock 124 OpacNav 124 OpacPasswordChange 127 OpacRenewalAllowed 127 OPACShelfBrowser 126 opacsmallimage 124 OpacTopissue 126 opacuserlogin 127 PINSEISBN 132 RequestOnOpac 128 reviewson 128 suggestion 128 TagsEnabled 132 TagsModera
about 35 incorrect or missing directory directive 36 listener not setup 37 rewrite module not enabled 36 unable to connect to MySQL 36 V AT, Bulkmarcimport.pl option 172 virtual host configuration 27 virtual hosts, Apache2 24 x x, Bulkmarcimport.pl option 174 XML SAX parser configuring 62 XSLT style sheets 133 Y y, Bulkmarcimport.
open source community experience distilled PUBLISHING Thank you for buying Koha 3 Library Management System About Packt Publishing Packt, pronounced 'packed', published its first book "Mastering phpMyAdmin for Effective MySQL Management" in April 2004 and subsequently continued to specialize in publishing highly focused books on specific technologies and solutions.
Join Packt! Work at the Leading Edge of IT Publishing We're looking for good people to join our Team in Mumbai.
o'e ' 1' 000 *or' ISBN Title Author Year Zehoo Landis 2010 Price Shroff / Packt Publishing 9789350233016 9788184045802 9789350230077 9788184042436 .NET Compact Framework 3.5 Data Driven Applications, 492 Pages 3CX IP PBX Tutorial, The, 234 Pages 3D Game Development with Microsoft Silverlight 3: Beginner's Guide, 456 Pgs 3D Graphics with XNA Game Studio 4.0, 300 Pages Active Directory Disaster Recovery, 256 Pages ADempiere 3.
ISBN Title 9788184049671 Backbase 4 RIA Development, 490 Pages Beginning OpenVPN 2.0.9, 360 Pages BIRT 2.
9789350232149 9788184042368 9788184042313 Compiere 3, 232 Pages Configuring IPCop Firewalls: Closing Borders with Open Source, 244 Pgs Creating your MySQL Database: Practical Design Tips and Techniques, 108 Pages 9789350230916 CUPS Administrative Guide: A practical tutorial to installing, managing, and securing this powerful printing system, 256 Pgs 9788184042290 Designing and Implementing Linux Firewalls and QoS Using Netfiler, Iproute, NAT and L7 - Filter, 288 Pages 9788184048810 9789350231647 97893
ISBN 9789350233023 9789350231630 9789350232156 9789350232583 9788184049077 9788184048940 9789350232163 9789350230046 9788184042429 9789350231654 9789350231494 Title Facebook Graph API Development with Flash Beginners Guide, 332 Pages Firebug 1.5: Editing, Debugging, and Monitoring Web Pages, 232 Pages Flash 10 Multiplayer Game Essentials, 344 Flash Multiplayer Virtual Worlds, 420 Pages Rash with Drupal, 388 Pages Flex 3 with Java, 312 Pages FreeSWITCH 1.0.
ISBN 9789350233146 9788184048230 9789350232170 9788184049442 9788184047738 9788184047707 9788184049268 9788184047790 9788184049947 9788184045345 9788184048360 9789350231500 9789350231326 9788184048605 9789350231807 9788184047646 9789350232200 9788184044690 9788184044584 9788184049251 9788184049299 9788184049282 9789350232194 9788184047653 9789350232217 9788184049275 9788184049220 9789350230015 9788184043952 9788184047561 9788184049305 9788184049251 9789350232033 9789350232651 9789350233849 9788184046557 9
9788184044638 9788184049312 9789350230909 9788184044737 9788184048346 9789350230084 9789350231432 9789350233085 9788184049107 9789350231333 9788184044713 9788184044539 9788184044676 9788184042252 9788184044003 9788184047820 9788184042351 9788184049336 9789350230008 9789350231548 9788184043853 9789350233092 9789350230091 9788184049541 9789350232231 9789350231982 9789350232668 9789350233603 9788184049343 LING) Quickly A practical guide to programming Language Integrated Query with C #, 254 Pages Linux E -ma
Author Year Price 9788184049169 ModSecurity 2.5, 288 Pages Mischel 2009 425.00 9788184049121 MODx Web Development, 284 Pages Moodie 1.9 E- Learning Course Development, 388 Pages John 2009 425.00 Rice IV 2008 450.00 Hillar 2010 475.00 Moore Taylor 2010 400.00 2010 450.00 Stanford 2009 800.00 ISBN 9788184045710 9789350232286 9789350231623 9789350231999 9788184048636 9788184047639 Title Moodie 1.9 English Teacher's Cookbook, 312 Pages Moodie 1.
9789350234099 9789350230640 9789350231579 9789350233061 9788184047660 9789350232712 9789350231968 9788184046076 9789350231098 9789350231067 9788184047837 9788184049978 9789350231234 9788184048629 9788184048421 9788184048384 9788184045796 9788184044720 9788184043914 9788184049176 9789350230497 9788184049145 9789350232729 9789350230480 9789350230121 9788184047721 9789350233177 9788184043945 9788184048582 9788184044096 9789350230107 9789350232736 9789350231838 9789350231814 9788184048377 9789350232316 9789350
ISBN Title 9788184044652 9788184049329 9788184045291 Programming Microsoft® DynamicsTM NAV, 482 Pages Programming Microsoft® DynamicsTM NAV 2009, 624 Pgs 9788184043983 Project Management with dotProject: Implement, Configure, Customize, and Maintain your DotProject Installation, 232 Pages 9789350233047 9789350232330 9789350232989 9789350232743 9788184049961 9788184043938 Python 2.
ISBN 9789350231784 9789350231876 9788184047585 Title Spring Python 1.1, 272 Pages Spring Security 3, 428 Pages Author Year Price Turnquist Mularien 2010 400.00 2010 650.00 Luppken 2009 400.00 9788184044560 Spring Web Flow 2 Web Development, 274 Pages SQL Server Integration Services Using Kríshnaswamy 2007 375.00 9788184045321 Swing Extreme Testing, 328 Pages Lavers 2008 375.00 9788184048599 Symfony 1.3 Web Application Development, 232 Pages Bowler 2009 350.
9789350232835 9789350232378 9789350231555 9788184045741 9788184048575 9788184044614 9788184045789 XNA 4.0 Game Development by Example: Beginner's Guide, 452 Pages YUI 2.8 Learning the Library, 416 Pages Zabbix 1.8 Network Monitoring, 436 Pages Jaegers Barreiro Olups 2011 650.00 2010 625.00 2010 650.00 Sarkar Pope 2008 375,00 2009 575.00 Zimbra Implement, Administer and Manage, 222 Pages Zenoss Core Network and System Monitoring, 282 Pages Resnick Badger 2008 300.00 2008 350.
. For Wholesale enquiries contact:- ..s .e -. .: .----... C -103, TTC Industrial Area, MIDO, Pawane, Navi Mumbai - 400 705. Tel: (91 22) 4158 4158 Fax: (91 22) 4158 4141 E -mail: spdorders @shroffpublishers.com Branches:Bangalore 7, Sharada Colony, Basaveshwarnagar, 8th Main, Bangalore 560 079 Tel: (91 80) 4128 7393 Fax: 4128 7392 E -mail: spdblr @shroffpublishers.
Koha 3 Library Management System Koha is the first full- featured open source library management system that is widely used for efficiently managing libraries. However, setting up and maintaining Koha is no walk in the park. It is not as straightforward as setting up the other popular LAMP applications. This practical guide provides all the essential information is needed to make the task of installing and configuring Koha seem simple and easy.
