Step 1. Create a Google app password

An App Password permits a non-Google app to access Google's SMTP server. App Passwords can only be used with accounts that have 2-step verification turned on. Google recommends using "Sign in with Google" whenever possible, a more secure way to connect apps. Here, we must create an app password for GMail to work with Koha ILS. Create a dedicated Gmail account or GMail-based email service for Koha. Don't use an existing email for other purposes when SMTP is configured; the inbox will be filled with bounced emails. 

1. Visit the Google Account Security settings page and turn on 2-step verification. Here is the link to your Google Account Security Settings, https://myaccount.google.com/u/2/security.

Step 2. SMTP configuration

Open Administration > Additional parameters > SMTP servers > New SMTP Server.

Add the details.

Name: Give server name, e.g. MGU Mail

Host: Enter the server's hostname. Here, the Gmail SMTP hostname is smtp.gmail.com

Port: Enter the port number of Gmail SMTP, 587. 

Timeout (seconds): Enter the number of seconds after which an unsent email will result in an error

SSL: Choose the security protocol. STARTTLS works with Gmail.

Username: Enter the Gmail ID. 

Password: Enter the Google App Password.

Debug mode: Select debug mode to send additional output to the logs.

Default server: Select it if all libraries use the default server.

Click the ‘Submit’ button to save the configuration.

Step 3. Enable email messaging in Koha

1. Apply the following command in a Terminal to enable email services from Koha ILS.

sudo koha-email-enable library

Other configurations to prepare Koha to send email messages.

1. Enable Enhanced Messaging preferences.

Koha Administration > Global System Preferences > Patrons > Enhancedmessagingpreferences > Allow

2. Visit each patron category at Administration > Patron categories and change the configuration, Overdue notice required (Yes).

3. Overdue Notice/Status triggers

Koha >  Tools > Overdue Notice/status triggers

Le symposium Koha s’est tenu du lundi 17 juin après-midi au mercredi 19 juin à la Maison méditerranéenne des sciences de l’homme (MMSH, AMU/CNRS) à Aix-en-Provence. Merci aux équipes de la MMSH et de l’AMU pour leur accueil chaleureux et énergique. Venir à la MMSH Lundi 17 juin 14h00-14h30 : Accueil 14h30-14h45 : Ouverture (Cyril […]

L’article Symposium 2024 est apparu en premier sur Association KohaLa.

Many libraries started to use SMTP-based email services in Koha. Koha provides SMTP server configuration from Administration > SMTP servers > New SMTP server. Such libraries use Gmail free account as the email service provider. Gmail allow you to send 100 emails per day. Users can't send new messages for up to 24 hours if the number of messages exceeds the limit. Google says, "If a user exceeds their sending limits, their account might be suspended". Another drawback of using an ordinary Gmail account is that libraries can't add their domain to the email ID. Sending emails from an ordinary Gmail account is a non-professional approach.

What's the solution?

Libraries can use a dedicated email service to deliver emails. Hiring an SMTP email service to work with Koha is a good idea. Libraries can choose email services from an array of service providers. Such services enable sending, receiving, and tracking emails. Netcore, MailGun, and Mailchimp are examples of transactional email service providers. Libraries can subscribe to the plan based on the number of transactions per day. Email services give the SMTP server settings details to configure with Koha.

L’association KohaLa organise en 2024 plusieurs sessions de formations gratuites à Koha pour ses adhérents, uniquement en visioconférence via Zoom. Si vous êtes intéressés par une ou plusieurs sessions du programme ci-dessous, mais pas encore adhérent, ou bien si vous n’avez pas encore renouvelé votre adhésion,  il est encore temps de le faire ICI ! […]

L’article Formations 2024 est apparu en premier sur Association KohaLa.

Pour donner suite à l’atelier sur le module Périodiques Koha lors du Symposium 2022 et aux réflexions du Hackfest de Marseille la même année, l’association Kohala a mis en place un groupe de travail « Périodiques ». Module peu ‘glamour’ (du fait même du traitement des périodiques qui apparaît souvent comme complexe), le souhait est de faciliter […]

L’article GT Périodiques est apparu en premier sur Association KohaLa.

L’après-midi d’étude s’est tenue le mardi 30 janvier 2024 en visio-conférence. Vous avez assisté à cet événement ? Vous avez des suggestions à apporter ? Donner votre avis ! Voici le programme de cette après-midi.Vous 14h00-14h10 – Accueil 14h10-15h10 – Retours Hackathon & GT Groupe Koha / ABES – Vidéo Groupe transition bibliographique – Vidéo Groupe […]

L’article Journée Koha 2024 est apparu en premier sur Association KohaLa.

Le Hackathon 2024 organisé par l’association KohaLa a eu lieu en visioconférence, les 22 et 23 janvier 2024, de 9h30 à 16h30, et a permis de travailler ensemble sur l’amélioration de Koha et notamment avancer sur les questions traitées par les groupes techniques, à savoir : la traduction la transition bibliographique (https://koha-fr.org/gt-transition-bibliographique/) les échanges entre […]

L’article Hackathon 2024 est apparu en premier sur Association KohaLa.

Installation of PCloud drive in Debian/Ubuntu.

Here are the steps on how to install PCloud software in Ubuntu:

1. Go to the pCloud website, and create an account.

2. Download the pCloud AppImage file for Linux.

3. Save the file to your computer.

4. Open a terminal window and navigate to the directory where you saved the file.

5. Run the following command to give the file executable permissions:

sudo chmod +x pcloud

Either double-click on the PCloud icon or run the following command to start the pCloud AppImage:

./pcloud

6. The pCloud login window will appear. Enter your pCloud email address and password, and click Log in.

A folder named pCloudDrive will be created in your home directory. This is your pCloud virtual drive. You can now start storing and accessing your files in pCloud.

To schedule Koha backup to pCloud please visit the following link,

http://kohageek.blogspot.com/2021/08/backup-with-auto-delete-old-files.html

The blog post gives the details of schedule backup in Dropbox cloud storage. The same steps can follow to schedule Koha backup to pCloud.

Problem statement

Solution

sudo mousepad /etc/koha/sites/library/koha-conf.xml

Find the location of the lines from the screenshot. Check the line number.

Reference

  Le symposium Koha s’est tenu du mercredi 28 juin après-midi au vendredi 30 juin à Sciences Po Grenoble – UGA (sur le campus universitaire). Comment venir à Sciences Po Grenoble – UGA ?           Mercredi 28 juin 14h00-14h30 : Accueil 14h30-14h45 : Introduction et présentation de l’association KohaLa (Sonia Bouis, […]

L’article Symposium 2023 est apparu en premier sur Association KohaLa.

BibLibre a organisé du 27 au 31 mars 2023, un Hackfest dans leurs locaux à Marseille, 108 rue Breteuil. Cette semaine s’adressait à tous les utilisateurs de Koha : développeurs, administrateurs, bibliothécaires, informaticiens, qui souhaitaient contribuer à améliorer Koha en : testant de nouvelles fonctionnalités ou de corrections de bugs, qui ont été intégrées récemment […]

L’article Hackfest 2023 est apparu en premier sur Association KohaLa.

        This article shows how to prepare the reports we need on the koha home page, such as koha circulation reports, catalog reports, account reports, library membership reports and etc as instant reports, with an exquisite menu.

Go to: Koha Home/Tools/HTML customizations and Click  New Entry, as shown in the image below.

Display Location Select for Librarian Interface and fill in all details.

Click the Source Code.

Copy and paste the below source code and change your library reports link, finally change all report links and save the source code.

<div class="dropdown"><button class=" btn btn-danger  btn-sm btn-block" p="" style="font-size: 16px;" type="button" id="dropdownMenuButton" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false"><strong> 📚 Catalog Report&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </strong><b class="caret"></b></button>
<ol class="dropdown-menu" p="" style="font-size: 14px;">
<li><a href="/cgi-bin/koha/reports/guided_reports.pl?reports=1&amp;phase=Run%20this%20report">Accession Register</a></li>
<li><a href="/cgi-bin/koha/reports/guided_reports.pl?reports=12&amp;phase=Run%20this%20report">Total Number of Books</a></li>
<li><a href="/cgi-bin/koha/reports/guided_reports.pl?reports=33&amp;phase=Run%20this%20report">Department Wise Number of Books</a></li>
<li><a href="/cgi-bin/koha/reports/guided_reports.pl?reports=34&amp;phase=Run%20this%20report">Collection Wise Number of Books</a></li>
<li><a href="/cgi-bin/koha/reports/guided_reports.pl?reports=15&amp;phase=Run%20this%20report">Item Type Wise Number of Books</a></li>
</ol>
</div>
<div class="dropdown"><button class=" btn btn-danger btn-sm btn-block" p="" style="font-size: 16px;" type="button" id="dropdownMenuButton" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false"><strong>💻Circulation Report &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </strong><b class="caret"></b></button>
<ol class="dropdown-menu" p="" style="font-size: 14px;">
<li><a href="/cgi-bin/koha/reports/guided_reports.pl?reports=13&amp;phase=Run%20this%20report">Check Out List of Books (Date wise)</a></li>
<li><a href="/cgi-bin/koha/reports/guided_reports.pl?reports=7&amp;phase=Run%20this%20report">Check in List of Books (Date wise)</a></li>
<li><a href="/cgi-bin/koha/reports/guided_reports.pl?reports=30&amp;phase=Run%20this%20report">Item Type Wise (Check Out Books)</a></li>
<li><a href="/cgi-bin/koha/reports/guided_reports.pl?reports=24&amp;phase=Run%20this%20report">Circulation Daily Transaction</a></li>
<li><a href="/cgi-bin/koha/reports/guided_reports.pl?reports=44&amp;phase=Run%20this%20report">Date wise Circulation Activity</a></li>
<li><a href="/cgi-bin/koha/reports/guided_reports.pl?reports=20&amp;phase=Run%20this%20report">Month Wise Circulation Report</a></li>
<li><a href="/cgi-bin/koha/reports/guided_reports.pl?reports=9&amp;phase=Run%20this%20report">Overdues Book List</a></li>
</ol>
</div>
<div class="dropdown"><button class=" btn btn-danger btn-sm btn-block" p="" style="font-size: 16px;" type="button" id="dropdownMenuButton" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false"><strong>💰 Accounts Report &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </strong><b class="caret"></b></button>
<ol class="dropdown-menu" p="" style="font-size: 14px;">
<li><a href="/cgi-bin/koha/reports/guided_reports.pl?reports=5&amp;phase=Run%20this%20report">Paid Fine for Students</a></li>
<li><a href="/cgi-bin/koha/reports/guided_reports.pl?reports=14&amp;phase=Run%20this%20report">Writeoff Fine for Students</a></li>
<li><a href="/cgi-bin/koha/reports/guided_reports.pl?reports=16&amp;phase=Run%20this%20report">Accounting Type Wise Collection</a></li>
<li><a href="/cgi-bin/koha/reports/guided_reports.pl?reports=17&amp;phase=Run%20this%20report">Students Fine Arrears Details</a></li>
</ol>
</div>
<div class="dropdown"><button class=" btn btn-danger btn-sm btn-block" p="" style="font-size: 16px;" type="button" id="dropdownMenuButton" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false"><strong>👩&zwj;🎓 Library Membership Report &nbsp; &nbsp; </strong><b class="caret"></b></button>
<ol class="dropdown-menu" p="" style="font-size: 14px;">
<li><a href="/cgi-bin/koha/reports/guided_reports.pl?reports=11&amp;phase=Run%20this%20report">Membership Staff &amp; Students</a></li>
<li><a href="/cgi-bin/koha/reports/guided_reports.pl?phase=Use%20saved">More Library Reports</a></li>
</ol>
</div>
<div><br /><br /><br /><br /><br /><br /><br /><br /></div>

Go to Koha Home Page and your exquisite instant koha reports menu is ready.

Reference: https://getbootstrap.com/docs/4.0/components/buttons/#sizes 

 Date Wise Circulation  Transaction Counts.

Save and close.

SELECT 

date(datetime) AS Date,

      SUM( IF(type = 'issue', 1, 0 )) AS Issues,

      SUM( IF(type = 'renew', 1, 0 )) AS Renewals,

      SUM( IF(type = 'return', 1, 0 )) AS Returns,

      SUM( IF(type = 'payment', 1, 0 )) AS Payment,

      COUNT(statistics.type) AS 'Total Transactions'

FROM  statistics

WHERE DATE(datetime) BETWEEN <<From Date |date>> AND <<To Date |date>>

GROUP BY date

Run Report

L’association KohaLa organise en 2023 plusieurs sessions de formations gratuites à Koha pour ses adhérents : En présentiel, à l’ENSSIB – Lyon (Villeurbane), En visioconférence via Zoom. Si vous êtes intéressés par une ou plusieurs sessions du programme ci-dessous, mais pas encore adhérent, ou bien si vous n’avez pas encore renouvelé votre adhésion,  il est […]

L’article Formations 2023 est apparu en premier sur Association KohaLa.

Le Hackathon organisé par l’association kohaLa s’est tenu en visioconférence, du 23 au 25 janvier 2023. Une dizaine de participants ont travaillé ensemble sur l’amélioration de Koha et ont fait avancer la traduction. La traduction La version 21.11 de Koha a été traduite à près de 98%. Un effort a été porté au manuel 22.05 […]

L’article Hackathon 2023 est apparu en premier sur Association KohaLa.

La journée d’étude s’est tenue à la BULAC, le jeudi 26 janvier 2023. Elle a été diffusée en streaming sur la chaîne YouTube BULAC. Voici le programme de cette journée. 10h00-10h30 – Accueil café & échanges [Foyer de l’Auditorium] 10h30-12h00 – Sessions en parallèle : Import automatique des lecteurs dans Koha : Retours d’expériences [Auditorium] […]

L’article Journée Koha 2023 est apparu en premier sur Association KohaLa.

Patron attributes help define custom fields (e.g. blood group, Course name (BSc, BA) etc.) with patron details.

1. Enable Patron Attributes from Global System Preferences

Administration  System preferences > Patrons > ExtendedPatronAttributes > Enable

2. Create an Authorized Value for the blood group

Administration > Authorized values > New category

Add a new patron attribute type for the blood group.

Administration > Patron attribute types > New Patron attribute type

Enter details of the new Patron Attribute type

Save the Patron Attribute Type for Blood Group. 

Add a new patron and see the blood group list.

Patrons  > Add patron

A library Clearance/Discharge certificate certifies that the user has no holds, no active checkouts, and no outstanding debt. Here are the steps to generate a clearance certificate;

1. Enable useDischarge from Koha Administration > Global System Preferences. Search and find the useDischarge settings. Turn it into Allow.

2. Customize the Discharge notice at Tools > Notices and slips. Search and find the Discharge notice. The content of the notice is blank. Visit the Notice Template site and copy the content. Edit and save the notice.

3. Open the Patron account to generate Discharge. Find the Discharge button at the end of the Patron account.

4. Click on the Generate discharge button.

1. Below are three essential backups to take in dspace.

1.dspace.backup (Database backup)

2.assetstore  (All uploaded files for e.g, pdf, image,etc..)

Step - 1

2. Take a backup of Dspace database.

Assume that the old version of Dspace is running. Take a PostgreSQL database backup. 

Open a Terminal and apply following commands, 

sudo su - postgres

pg_dump dspace > dspace.backup

The above command take a backup of Dspace database and store in /var/lib/postgresql/ 

Copy the database backup file to a safe place.

Step - 2

3. Take a backup assetstore and log folders.

Here we are going to backup essential things. All uploaded files stored in assetstore folder.

Save the assetstore and log files to External hard disc. (below red color command your external hard disc storage location)

cd /media/your pc name/External hard disc name

sudo zip -r assetstore.zip /dspace/assetstore

sudo zip -r log.zip /dspace/log

Step - 3

4. Restoration of backup to the latest version of Dspace

Stop Tomcat server

sudo service tomcat stop

Remove the new dspace assetstore and log folders.

sudo rm -rf /dspace/assetstore

sudo rm -rf /dspace/log/

Move the old dspace assetstore and log folders.

Move your old assetstore and log folders to /dspace folder. (Copy & paste the assetstore and log folder in Home folder)

sudo mv /home/assetstore /dspace

sudo mv /home/log /dspace

Restoration of database

sudo systemctl stop postgresql

sudo systemctl start postgresql

Drop the database and create a new one. 

sudo -u postgres psql

DROP DATABASE dspace;

CREATE DATABASE dspace;

\quit

Restore the data base backup

sudo su postgres

psql -f dspace.backup dspace

exit

sudo su postgres

psql --username=postgres dspace -c "CREATE EXTENSION pgcrypto;"

exit

Apply following commands

sudo /dspace/bin/dspace database info

sudo /dspace/bin/dspace database migrate

sudo /dspace/bin/dspace index-discovery -b

sudo /dspace/bin/dspace filter-media

sudo /dspace/bin/dspace index-discovery

sudo /dspace/bin/dspace index-discovery -o

Restart Tomcat

sudo service tomcat start

SELECT CONCAT('<a href="/cgi-bin/koha/catalogue/detail.pl?biblionumber=',b.biblionumber,'">Notice</a>') AS 'Notice', b.title AS 'Titre', b.author AS 'Auteur', MIN(i.withdrawn_on) AS 'Pilon depuis', COUNT(i.itemnumber) AS 'Nb exemplaires' FROM items i JOIN biblio b ON(i.biblionumber = b.biblionumber) WHERE b.biblionumber IN ( SELECT biblionumber FROM items GROUP BY biblionumber HAVING COUNT(itemnumber) > 0 AND COUNT(IF(withdrawn = 1,1,NULL)) = COUNT(itemnumber) ) AND i.homebranch LIKE <<Site|branches:all>> AND […]

L’article Liste des notices avec des exemplaires pilonnés est apparu en premier sur Association KohaLa.

In out Management Auto Backup in Dropbox.

Blank Screen After Installation

How patrons can intuitively navigate through the Koha OPAC, access their account information, and browse all materials.

This webinar covers the basics of the Koha Staff interface and how staff can intuitively navigate the models.

Install Ubuntu MATE

Open Terminal on your Ubuntu machine for Dspace installation.

sudo apt-get update

sudo apt-get upgrade

sudo apt-get install git

git --version

sudo add-apt-repository ppa:git-core/ppa

sudo apt update; apt install git

sudo apt-get install openjdk-8-jdk

sudo apt-get install maven

sudo apt-get install ant

sudo sh -c 'echo "deb http://apt.postgresql.org/pub/repos/apt $(lsb_release -cs)-pgdg main" > /etc/apt/sources.list.d/pgdg.list'

wget --quiet -O - https://www.postgresql.org/media/keys/ACCC4CF8.asc | sudo apt-key add -

sudo apt-get update

sudo apt-get install postgresql-9.6

sudo su postgres

createuser --username=postgres --no-superuser --pwprompt dspace

createdb --username=postgres --owner=dspace --encoding=UNICODE -T template0 dspace

psql --username=postgres dspace -c "CREATE EXTENSION pgcrypto;"

exit

sudo gedit /etc/postgresql/9.6/main/pg_hba.conf

local 	all 		dspace 					md5

sudo /etc/init.d/postgresql restart

sudo useradd -m dspace

sudo passwd dspace

sudo mkdir /dspace

sudo chown dspace /dspace

sudo mkdir /build

sudo chmod -R 777 /build

cd /build

wget https://github.com/DSpace/DSpace/releases/download/dspace-6.3/dspace-6.3-src-release.tar.gz

tar -zxf dspace-6.3-src-release.tar.gz 

sudo gedit /build/dspace-6.3-src-release/dspace-api/pom.xml

<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>buildnumber-maven-plugin</artifactId>
<version>1.4</version>
<executions><execution>
<phase>validate</phase>
<goals>
<goal>create</goal >
</goals>
</execution
</executions>
</plugin>

cd /build/dspace-6.3-src-release

sudo mvn -U package

cd dspace/target/dspace-installer

sudo ant fresh_install

cd /opt

sudo wget https://dlcdn.apache.org/tomcat/tomcat-8/v8.5.83/bin/apache-tomcat-8.5.83.tar.gz

sudo tar xvzf apache-tomcat-8.5.83.tar.gz

sudo mv apache-tomcat-8.5.83 tomcat

sudo rm apache-tomcat-8.5.83.tar.gz

sudo gedit /etc/profile

export JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64
export CATALINA_HOME=/opt/tomcat

sudo cp -r /dspace/webapps/* /opt/tomcat/webapps

sudo gedit /etc/init.d/tomcat

#!/bin/bash
### BEGIN INIT INFO
# Provides: 		tomcat8
# Required-Start: 	$network
# Required-Stop: 	$network
# Default-Start: 	2 3 4 5
# Default-Stop : 	0 1 6
# Short-Description: Start/Stop Tomcat server
### END INIT INFO

PATH=/sbin:/bin:/usr/sbin:/usr/bin 

start() {
sh /opt/tomcat/bin/startup.sh
}

stop() {
sh /opt/tomcat/bin/shutdown.sh
}

case $1 in
  start|stop) $1;;
  restart) stop; start;;
  *) echo "Run as $0 <start|stop|restart>"; exit 1;;
esac

sudo chmod +x /etc/init.d/tomcat

sudo update-rc.d tomcat defaults

sudo service tomcat start

sudo /dspace/bin/dspace create-administrator

I hope this tutorial will help you to install the DSpace in Ubuntu MATE22.4 LTS.

Install same server in Koha Latest version 
Visit: https://libpowertech.blogspot.com/2021/03/how-to-install-koha-on-ubuntu-mate-2004.html

 If you have any error PHP, use the following method

Blank screen phpmyadmin page after install

sudo systemctl restart apache2

sudo mousepad /etc/apache2/conf-enabled/phpmyadmin.conf

Alias /phpmyadmin /usr/share/phpmyadmin

<Directory /usr/share/phpmyadmin>
    Options SymLinksIfOwnerMatch
    DirectoryIndex index.php

    <IfModule mod_php8.c>
        <IfModule mod_mime.c>
            AddType application/x-httpd-php .php
        </IfModule>
        <FilesMatch ".+\.php$">
            SetHandler application/x-httpd-php
        </FilesMatch>

        php_value include_path .
        php_admin_value upload_tmp_dir /var/lib/phpmyadmin/tmp
        php_admin_value open_basedir /usr/share/phpmyadmin/:/etc/phpmyadmin/:/var/lib/phpmyadmin/:/usr/share/php/php-gettext/:/usr/share/php/php-php-gettext/:/usr/share/javascript/:/usr/share/php/tcpdf/:/usr/share/doc/phpmyadmin/:/usr/share/php/phpseclib/
        php_admin_value mbstring.func_overload 0
    </IfModule>
    <IfModule mod_php.c>
        <IfModule mod_mime.c>
            AddType application/x-httpd-php .php
        </IfModule>
        <FilesMatch ".+\.php$">
            SetHandler application/x-httpd-php
        </FilesMatch>

        php_value include_path .
        php_admin_value upload_tmp_dir /var/lib/phpmyadmin/tmp
        php_admin_value open_basedir /usr/share/phpmyadmin/:/etc/phpmyadmin/:/var/lib/phpmyadmin/:/usr/share/php/php-gettext/:/usr/share/php/php-php-gettext/:/usr/share/javascript/:/usr/share/php/tcpdf/:/usr/share/doc/phpmyadmin/:/usr/share/php/phpseclib/
        php_admin_value mbstring.func_overload 0
    </IfModule>

</Directory>

# Authorize for setup
<Directory /usr/share/phpmyadmin/setup>
    <IfModule mod_authz_core.c>
        <IfModule mod_authn_file.c>
            AuthType Basic
            AuthName "phpMyAdmin Setup"
            AuthUserFile /etc/phpmyadmin/htpasswd.setup
        </IfModule>
        Require valid-user
    </IfModule>
</Directory>

# Disallow web access to directories that don't need it
<Directory /usr/share/phpmyadmin/templates>
    Require all denied
</Directory>
<Directory /usr/share/phpmyadmin/libraries>
    Require all denied
</Directory>
<Directory /usr/share/phpmyadmin/setup/lib>
    Require all denied
</Directory>

sudo systemctl restart apache2

If you have any error mysql password, use the following method

Follow the Mysql update change

PASSWORD UPDATE (Mysql)

sudo su

Use mysql;

update user set password=PASSWORD("mynewpassword") where User='root';

update user set plugin="mysql_native_password";

quit;

/etc/init.d/mysql stop

kill -9 $(pgrep mysql)

/etc/init.d/mysql start

mysql -u root -p

Page en cours de construction

L’article GT Traduction est apparu en premier sur Association KohaLa.

Ce groupe de travail a été créé pour contribuer à l’adaptation de Koha aux évolutions liées à la transition bibliographique, en prenant en compte les spécificités françaises. Un premier travail important a été fait depuis 2019 pour adapter Koha aux changements du format Unimarc tel que défini par l’IFLA. Cela implique de mettre à jour […]

L’article GT Transition bibliographique est apparu en premier sur Association KohaLa.

Ce groupe de travail est né de la constatation qu’un quart des établissements du réseau SUDOC utilisaient Koha et qu’il y avait des enjeux spécifiques liés aux échanges d’information entre Koha et les outils de l’ABES. Le GT effectue d’une part une analyse des outils de l’ABES (applications, protocoles d’échange, webservices..) et en relation avec […]

L’article GT Koha-ABES est apparu en premier sur Association KohaLa.

Step - 1

Step - 2

Click the Source code

Copy and paste the following HTML Code.

Replace your koha report link in the red colored area. 

All Links in replace and finally save the source code.

<div style="text-align: justify;"></div>

<div style="text-align: justify;">

<table border="0" cellspacing="1" cellpadding="1" style="border-collapse: collapse; width: 280px; height: 90px; margin-left: auto; margin-right: auto;">

<tbody>

<tr style="height: 18px;">

<td style="height: 10px; width: 278px; text-align: center;" colspan="2">

<h3 style="text-align: center;">?? Catalog Report</h3>

</td>

</tr>

<tr style="height: 18px;">

<td style="height: 18px; width: 10px; text-align: center;"><strong>1</strong></td>

<td style="height: 18px; width: 265px;"><strong><a href="/cgi-bin/koha/reports/guided_reports.pl?reports=1&amp;phase=Run%20this%20report" rel="noopener"><span style="color: green;">Accession Register</span></a></strong></td>

</tr>

<tr style="height: 18px;">

<td style="height: 18px; width: 10px; text-align: center;"><strong>2</strong></td>

<td style="height: 18px; width: 265px;"><strong><a href="/cgi-bin/koha/reports/guided_reports.pl?reports=12&amp;phase=Run%20this%20report"><span style="color: green;">Total Number of Books</span></a><br /></strong></td>

</tr>

<tr style="height: 18px;">

<td style="height: 18px; width: 10px; text-align: center;"><strong>3</strong></td>

<td style="height: 18px; width: 265px;"><strong><a href="/cgi-bin/koha/reports/guided_reports.pl?reports=33&amp;phase=Run%20this%20report"><span style="color: green;">Department Wise Number of Books</span></a><br /></strong></td>

</tr>

<tr style="height: 18px;">

<td style="height: 18px; width: 10px; text-align: center;"><strong>4</strong></td>

<td style="height: 18px; width: 265px;"><strong><a href="/cgi-bin/koha/reports/guided_reports.pl?reports=34&amp;phase=Run%20this%20report"><span style="color: green;">Collection Wise Number of Books</span></a><br /></strong></td>

</tr>

<tr style="height: 18px;">

<td style="height: 18px; width: 10px; text-align: center;"><strong>5</strong></td>

<td style="height: 18px; width: 265px;"><strong><a href="/cgi-bin/koha/reports/guided_reports.pl?reports=15&amp;phase=Run%20this%20report" rel="noopener"><span style="color: green;">Item Type Wise Number of Books</span></a><br /></strong></td>

</tr>

</tbody>

</table>

</div>

<div style="text-align: justify;"><br />

<table border="0" cellspacing="1" cellpadding="1" style="border-collapse: collapse; width: 279px; height: 110px; margin-left: auto; margin-right: auto;">

<tbody>

<tr style="height: 18px;">

<td style="height: 18px; width: 275px; text-align: center;" colspan="2">

<h3>?? Circulation Report</h3>

</td>

</tr>

<tr style="height: 18px;">

<td style="height: 18px; width: 9.03125px; text-align: center;"><strong>1</strong></td>

<td style="height: 18px; width: 262.969px;"><strong style="text-align: center;"><a title="Check Out List of Books (Date wise)" href="/cgi-bin/koha/reports/guided_reports.pl?reports=13&amp;phase=Run%20this%20report" rel="noopener"><span style="color: green;">Check Out List of Books (Date wise)</span></a></strong></td>

</tr>

<tr style="height: 18px;">

<td style="height: 18px; width: 9.03125px; text-align: center;"><strong>2</strong></td>

<td style="height: 18px; width: 262.969px;">

<strong style="text-align: center;"><a href="/cgi-bin/koha/reports/guided_reports.pl?reports=7&amp;phase=Run%20this%20report" rel="noopener"><span style="color: green;">Check in List of Books (Date&nbsp;

</span></a></strong>

<strong style="text-align: center;"><a href="/cgi-bin/koha/reports/guided_reports.pl?reports=7&amp;phase=Run%20this%20report" rel="noopener"><span style="color: green;"> wise)</span></a></strong>

<strong style="text-align: center;"><a href="/cgi-bin/koha/reports/guided_reports.pl?reports=7&amp;phase=Run%20this%20report" rel="noopener"><span style="color: green;"></span></a></strong>

<strong style="text-align: center;"><a href="/cgi-bin/koha/reports/guided_reports.pl?reports=7&amp;phase=Run%20this%20report" rel="noopener"><span style="color: green;"><br /></span></a></strong></td>

</tr>

<tr>

<td style="width: 9.03125px; text-align: center;"><strong>3</strong></td>

<td style="width: 262.969px;"><strong style="text-align: center;"><span style="color: green;"><strong style="text-align: center;"><a href="/cgi-bin/koha/reports/guided_reports.pl?reports=30&amp;phase=Run%20this%20report" rel="noopener">Item Type Wise (Check Out Books)</a></strong><br /></span></strong></td>

</tr>

<tr style="height: 18px;">

<td style="height: 18px; width: 9.03125px; text-align: center;"><strong>4</strong></td>

<td style="height: 18px; width: 262.969px;"><span style="color: #e67e23;">

<strong style="text-align: center;"><a href="/cgi-bin/koha/reports/guided_reports.pl?reports=9&amp;phase=Run%20this%20report" rel="noopener" style="color: #e67e23;">Overdues Book List</a></strong></span><strong><br /></strong></td>

</tr>

<tr style="height: 18px;">

<td style="height: 18px; width: 9.03125px; text-align: center;"><strong>5</strong></td>

<td style="height: 18px; width: 262.969px;"><strong style="text-align: center;"><a href="/cgi-bin/koha/reports/guided_reports.pl?reports=24&amp;phase=Run%20this%20report" rel="noopener"><span style="color: green;">Circulation Daily Transaction</span></a></strong><strong><br /></strong></td>

</tr>

<tr style="height: 18px;">

<td style="height: 18px; width: 9.03125px; text-align: center;"><strong>6</strong></td>

<td style="height: 18px; width: 262.969px;"><strong style="text-align: center;"><a href="/cgi-bin/koha/reports/guided_reports.pl?reports=20&amp;phase=Run%20this%20report" rel="noopener"><span style="color: green;">Month Wise Circulation Report</span></a></strong><strong><br /></strong></td>

</tr>

</tbody>

</table>

</div>

<div style="text-align: justify;"><br />

<table border="0" cellspacing="1" cellpadding="1" style="border-collapse: collapse; width: 280px; height: 25px; margin-left: auto; margin-right: auto;">

<tbody>

<tr style="height: 18px;">

<td style="height: 18px; width: 276px; text-align: center;" colspan="2">

<h3 style="text-align: center;">?? Accounts Report</h3>

</td>

</tr>

<tr style="height: 18px;">

<td style="height: 18px; width: 13.7969px; text-align: center;"><strong>1</strong></td>

<td style="width: 259.203px; height: 18px;"><strong><a href="/cgi-bin/koha/reports/guided_reports.pl?reports=5&amp;phase=Run%20this%20report" rel="noopener"><span style="color: green;">Paid Fine for Students</span></a></strong></td>

</tr>

<tr style="height: 18px;">

<td style="height: 18px; width: 13.7969px; text-align: center;"><strong>2</strong></td>

<td style="width: 259.203px; height: 18px;"><strong><a title="Writeoff Fine" href="/cgi-bin/koha/reports/guided_reports.pl?reports=14&amp;phase=Run%20this%20report" rel="noopener"><span style="color: red;">Writeoff Fine for Students</span></a></strong></td>

</tr>

<tr style="height: 18px;">

<td style="height: 18px; width: 13.7969px; text-align: center;"><strong>3</strong></td>

<td style="width: 259.203px; height: 18px;"><strong><a title="A/C Type of Fine" href="/cgi-bin/koha/reports/guided_reports.pl?reports=16&amp;phase=Run%20this%20report" rel="noopener"><span style="color: green;">A/C Type of Fine<br /></span></a></strong></td>

</tr>

<tr style="height: 18px;">

<td style="height: 18px; width: 13.7969px; text-align: center;"><strong>4</strong></td>

<td style="width: 259.203px; height: 18px;"><strong><a title="Fine Details" href="/cgi-bin/koha/reports/guided_reports.pl?reports=17&amp;phase=Run%20this%20report" rel="noopener"><span style="color: green;">Fine Details<br /></span></a></strong></td>

</tr>

</tbody>

</table>

</div>

<div style="text-align: justify;"><br />

<table border="0" cellspacing="1" cellpadding="1" style="border-collapse: collapse; width: 280px; height: 25px; margin-left: auto; margin-right: auto;">

<tbody>

<tr style="height: 18px;">

<td style="height: 18px; width: 276px; text-align: center;" colspan="2">

<h3 style="text-align: center;">??&zwj;??<strong> Library Membership Report</strong></h3>

</td>

</tr>

<tr style="height: 18px;">

<td style="height: 18px; width: 13.7969px; text-align: center;"><strong>1</strong></td>

<td style="width: 259.203px; height: 18px;"><strong> <a title="Membership Staff " href="/cgi-bin/koha/reports/guided_reports.pl?reports=11&amp;phase=Run%20this%20report" rel="noopener"><span style="color: green;">Membership Staff &amp; Students</span></a></strong></td>

</tr>

</tbody>

</table>

</div>

<div style="text-align: justify;"></div>

Step - 3

Go to: Home Page (Successfully Your report displaying)

Koha master login username and password is same as MySQL database (e.g. koha_library), where data stored.

First change the password of koha_library database.

Then put new password in /etc/koha/sites/library/koha-conf.xml

Apply following commands in Applications > Accessories > Terminal

sudo mysql -uroot -p  

[enter the MySQL Root password]

use mysql;

SET PASSWORD FOR 'koha_library'@'localhost' = PASSWORD('mamcet@66');

flush privileges;

quit;

Need to change new password in Koha configuration file.

Open the configuration file using any text editor. Use any text editor, mousepad/leafpad. Install mousepad.

sudo apt-get install mousepad 

sudo mousepad /etc/koha/sites/library/koha-conf.xml 

The file will open. Scroll to bottom part of the file and find the line number 271 for password.

Reference: http://kohageek.blogspot.com/

The Koha Staff Experience July 14, 2022

In this 30 minute, The Koha Staff Experience, we will cover the basics of the Koha Staff interface and how staff can intuitively navigate through the models

Registration Link: https://us02web.zoom.us/webinar/register/WN_BN0k0VrSSm6ykhwHLSgRpQ?timezone_id=Asia%2FKolkata

Discover the Koha OPAC on August 9, 2022

In this 30-minute webinar, Discover the Koha OPAC, we will cover how patrons can intuitively navigate through the Koha OPAC, access their account information, and browse all materials!

Registration Link: https://us02web.zoom.us/webinar/register/WN_VtjLAB1pTGO7kQn0inK9lA?timezone_id=Asia%2FKolkata

Technical Services Overview September 15, 2022

In this 30-minute webinar, Technical Services Overview, we will cover the basics of cataloging, acquisitions, serials, and the tools for technical services workflows in Koha!

Registration Link: https://us02web.zoom.us/webinar/register/WN_9P5y1AWFQQ-4et1v2UqChQ?timezone_id=Asia%2FKolkata

The Koha Staff Experience October 18, 2022

In this 30-minute, The Koha Staff Experience, we will cover the basics of the Koha Staff interface and how staff can intuitively navigate through the models.

Registration Link: https://us02web.zoom.us/webinar/register/WN_MHW5H9DCQbm1jOuF1JV-gw?timezone_id=Asia%2FCalcutta

The Basics of Circulation November 16, 2022

In this 30-minute webinar, The basics of circulation, we will cover how staff can utilize the circulation functionality and integrate it into their daily workflows for a successful customer experience.

Registration Link: https://us02web.zoom.us/webinar/register/WN_qAxK67LATByqxRulY9ZBQQ?timezone_id=Asia%2FCalcutta

An Administrators Overview December 8, 2022

In this 30-minute webinar, An Administrators Overview, we will cover how Koha’s administration functionality can help users easily perform their day-to-day jobs at the library.

Registration Link: https://us02web.zoom.us/webinar/register/WN_cRK3MarjQny_ZuJlKye3qA?timezone_id=Asia%2FKolkata

The error aka “zor ka jhatkaa”

Last week a client partner raised a rather interesting support ticket: when they are checking in overdue items with fines, the fines seem to be vanishing. No, they were not waiving anything, the fines were simply going away and no record of there being ever a fine or its waiver were showing up in the Accounting tab of the patron.

The investigation

Turns out this was indeed happening. The instance was Koha 21.05.07 running on Debian 10.11 using MariaDB 10.3 running without plack. The evidence the fines been reset to zero and removed was available in the “Log viewer” under the Tools menu.

The solution

Doing a diff on the database backup of the table circulation_rules between the database backup from 2 days before and the one from that day, revealed that the day before, the client had re-jigged their circulation rules during which they had inadvertently changed the Fine interval aka chargeperiod setting from “1” to blank.

As the user manual says :

Enter the ‘Fine charging interval’ in the unit you set (ex. charge fines every 1 day, or every 2 hours). The finesCalendar system preference controls whether the days the library is closed will be taken into account or not.

In this specific instance, not only was the finesMode system preference set to “Calculate and charge” with fines being charged by the daily cron job, it also had CalculateFinesOnReturn system preference set to “Do”. Thus, while the cron job was creating and then updating fines once a day, the CalculateFinesOnReturn triggered at the time of check-in was resetting the fines to “0” as the chargeperiod was not set. This was why the fines were disappearing.

The simple fix was to ensure that for all the circulation rules the chargeperiod was set to “1”. And immediately the problem went away.

KISS, an acronym for “keep it simple, stupid” or “keep it stupid simple”, is a design principle noted by the U.S. Navy in 1960. The KISS principle states that most systems work best if they are kept simple rather than made complicated; therefore, simplicity should be a key goal in design, and unnecessary complexity should be avoided. The phrase has been associated with aircraft engineer Kelly Johnson. Variations on the phrase include: “Keep it simple, silly”, “keep it short and simple”, “keep it simple and straightforward”, “keep it small and simple”, or “keep it stupid simple”. [1]

Earlier today we received a request to add a new SQL report to generate a list of all students with their email ids from the librarian at our client partner Sister Nivedita University. The request prima facie was simple. However, when we looked at the patron categories for students under Administration, the first reaction was “Uh oh!”.

Let me explain. There were 8 patron categories for students (of all types) and all these student patron categories had different mnemonic codes that were as follows:

Still, just to fulfill the service request, all we needed to do was to create an SQL query like

SELECT
   cardnumber, firstname, surname, email
FROM borrowers 
WHERE categorycode IN 
('DIP', 'GNM-3', 'RS', 'SPG-2', 'SPG-3', 'SUG-3', 'SUG-4', 'SUG-5')

The ‘problem’

There was no way to know from the mnemonic values that all these codes designated a student patron category, as there was no uniform standardization of the values used for student categories. To put the problem in a perspective that library professionals will understand easily – e.g. if we saw a DDC class number that started with 004, we’ll immediately know that it belongs to “computer science“, but what if the computer science documents were marked out with numbers that did not denote computer science under DDC???

Further, if in the future, the library added another student patron category, the SQL report would need to be updated in order to give the correct output that will include members belonging to this newly added category.

The ‘solution’

Luckily the solution was both simple and straightforward. We had to standardize and re-code the student patron categories and update the affected patrons. To do that we prefixed every student patron category with “STD_“. And thus, the student patron categories became:

This was followed by updating the categorycode in the borrowers table to reflect the new changes. As a result the SQL query became much simplified:

SELECT
   cardnumber, firstname, surname, email
FROM borrowers 
WHERE categorycode LIKE 'STD_%'

If the library added a new student patron category in the future, all they would need to do is prefix the code with “STD_” and this query would continue to work without any change with this simple and straightforward update.

Legalese

This solution required us to directly access the production database with MySQL’s foreign key check turned off with SET FOREIGN_KEY_CHECKS=0;. If you get inspired to follow this, please ensure you have a complete database backup before you attempt this. And if by chance, you manage to mess it up or damage your database while attempting to do this, we are NOT responsible in any manner.

References [1] https://en.wikipedia.org/wiki/KISS_principle

We are pleased to welcome our newest client partner ESI-PGIMSR (Joka) Library to our cloud-hosted Koha ILS platform.

About ESI-PGIMSR

ESI-PGIMSR, Kolkata, also known by its full name Employees State Insurance Post Graduate Institute of Medical Sciences and Research & Employees State Insurance Corporation Medical College, Kolkata, is a MCI recognised medical college established in 2013 under the aegis of the ESI Corporation, an autonomous body under the Ministry of Labour and Employment, Government of India.

About the library

The library is located at the 2nd Floor of the Academic Building with floor area of more than 3000 sq. ft. Users have facility of for easy browsing, reading and borrowing of Books and Journals. The library caters to the need of M.B.B.S. students, Research Scholars, Post Graduate Students, Senior Residents, Junior Residents, Medical Teaching Faculty and other Doctors and Paramedical Staff of the Institute. The library follows open access system with books arranged using the Decimal Classification (D.D.C.) scheme.

The Problem

Recently there was a request from IDSK – they wanted the accession register SQL report for their Rabindranath Tagore Grant collection books to be listed in a natural sort. Documents of this collection carry the prefix “RT” which is fine and dandy. The “problem” started after that. In their earlier legacy system (SOUL v1) when these books had been accessioned, they did not use an fixed uniform length accession no for this collection. For example, instead of RT00001, it was entered RT1, RT2 and so on. Further, their problem was compounded by another glitch. In several of these accession nos, there were spaces inserted between “RT” and the actual numerical part. When they migrated to Koha with L2C2 Technologies, these problems were carried over to the new system as data curation and correction was not part of the deliverables. Now, three years later, when reports were being asked for, these issues had come back to haunt them.

The “Solution”

The RT collection has over 4000+ books and a manual fix was not feasible at this time. So using the ORDER BY keyword in the report’s SQL like this: ORDER BY LPAD(REPLACE(REPLACE(TRIM(items.barcode)," ",""),"RT",""), 10, ' ') ASC we at least managed to hide the problem and also got natural sorting to work. The first REPLACE() took out any space in the accession no, and the second REPLACE() stripped off the “RT” prefix, leaving us with only the number. Finally using LPAD() we zero prefixed the number so that each one was exactly 10 characters long. And we had our naturally sorted list of accession numbers in the report as we can see below.

The 126-year old heritage library of Bangiya Sahitya Parishat (aka Bangiya Sahitya Parishad) chooses L2C2 Technologies as their Koha hosting service provider, and it is with great joy admixed with a sense of greater responsibility that we welcome our newest client-partner. The OPAC is available at https://library.bangiyasahityaparishat.org/

About Bangiya Sahitya Parishat

Originally founded on 23 July, 1893 as the “Bengal Academy of Literature” literary society, the institution renamed itself as “Bangiya Sahitya Parishat” in 1894 with Romesh Chunder Dutt as it’s first president and Rabindranath Tagore and Navinchandra Sen as vice presidents. With the study and development of the Bengali language and literature as its main objective, the society has over the years, has delved into the cultural, historical, archaeological, sociological and other scientific studies and researches with special reference to Bengal. The society moved into its present address in 1908. The land the building stands on was donated by Maharaja Manindra Chandra Nandy of Cossimbazar Raj. In 1997, Kolkata Municipal Corporation notified the building as a Grade-I heritage building.

About the library

Established in 1894, the Bangiya Sahitya Parishat Library was the brainchild of Archarya Ramendra Sundar Tribedi. From its early beginning with a handful of donated books and periodicals, the library today in its collection has 1,01,719 books and 17,558 journals. The collection includes very rare and valuable books as well as many rare 19th century periodicals in Bengali and English such as ‘Digdarshan’, ‘Samachar Darpan’, ‘Samachar Chandrika’, ‘Friend of India’ etc. [1] The library has several important collections, the most important highlight being the “Vidyasagar Collection” donated by the erstwhile Maharajah of Lalgola. Given the richness of its collections, the library attracts readers and researchers from both India and abroad.

References: [1] https://bangiyasahityaparishat.org/library/

What is kohadevbox?

As the README.md at https://gitlab.com/koha-community/kohadevbox says – “Create a development environment for the Koha ILS project. It uses Vagrant and Ansible to set up a VirtualBox.” Basically it automates the long and somewhat complex process of manually setting up a development system for #kohails.

Why PuTTY?

From the website – PuTTY is an SSH and telnet client, developed originally by Simon Tatham for the Windows platform. PuTTY is open source software that is available with source code and is developed and supported by a group of volunteers. It is our go-to tool on Windows for accessing physical Koha boxes or VMs via SSH.

Vagrant sets up SSH service on the VM to use public-key authentication. Therefore our PuTTY instance needs to know the private key that Vagrant had setup inside the VM, in order to login into it. As many posts in Stackoverflow indicates, this is a point where many people get stuck. Usually they try with %USERPROFILE%\.vagrant.d\insecure_private_key and that typically fails.

Steps for kohadevbox

Using git-bash go to the directory where you had cloned kohadevbox. Be default it will be %USERPROFILE%/git/kohadevbox if you have simply followed the instructions from kohadevbox README.md file. In our case, it was %USERPROFILE%/gitdev/kohadevbox as we had changed it.

Run the command

vagrant ssh-config

You should see something like this:

The line to note in the output is IdentityFile. That’s the private key you need to grab and feed to PuTTYGen for it to convert it into a PuTTY compatible .ppk format private key.

NOTE: This path to the key is going to be different for different users, so do not attempt to copy-paste what you see here, instead use your own IdentityFile value.

Now we convert the vagrant_private_key from IdentityFile and save it as a .ppk file.

And lastly we import it into PuTTY like this and we are good to go!

Finally we are logged in into the VM

NOTES: The versions of software used – (a) PuTTY.exe – 0.71 (b) Vagrant – 2.2.7 (c) Git Bash – 2.25.0 (d) VirtualBox – 6.1.2

We are happy to announce that Nirmala College, Muvattupuzha has chosen to L2C2 Technologies for migration from a legacy proprietary software to Koha on our hosted Koha on the cloud platform.

About Nirmala College

Established in 1953, Nirmala College, Muvattupuzha is a first-grade college affiliated to Mahatma Gandhi University, Kottayam. It is a minority Christian institution governed and managed by the Corporate Educational Agency, Syrian Catholic Diocese of Kothamangalam. In strict compliance with the vision of the founding fathers, the college has served the community, irrespective of caste, creed and colour and has contributed to the world quite large a number of value-based Nirmalites. Her performance in academic and non-academic activities has been acknowledged by the NIRF rankings 2017 in the form of its position on the 91st among the list of colleges in the country. In addition, the college has been bestowed with the prestigious ‘Star College’ status by the Department of Bio-Technology (DBT), Government of India, in recognition of the advancements made by the college in the field of science education, with a handsome financial grant. All science departments of the college are supported by the DST- FIST scheme.

The college is located on a hill top at the doorstep of high ranges in the western ghats. The campus is spread over 53 acres of land with state of the art facilities for a constructive learning experience. The college has now grown to become a centre of learning that offers graduation in 16 disciplines, post-graduation in 14 and research facility in six. The college also runs 17 certificate/ diploma programmes. The IGNOU Study Centre, functioning in the college, offers 11 UG and 04 PG Programmes. The Nirmala Civil Service Academy, functioning in the college, caters to the needs of civil service aspirants.

From : http://nirmalacollege.ac.in/welcome-to-nirmala-college/

About the Library

The Library has a collection of over 80,000 volumes. The Library subscribes to 190 journals and periodicals both national and international. The entire legacy data was migrated over to Koha ILS. The OPAC is available at https://nirmala-opac.l2c2.co.in/

This video shares the idea about how to turbo-charge the sort1 and sort2 fields for patron records in Koha by utilizing Koha’s very own reports web service in tandem with a bit of JQuery.

If you are feeling impatient because you already know the background, feel free to jump to 3 minutes 10 seconds into the playtime, to see the actual action in progress.

Runtime: 14 mins 35 sec.

The Problem

Earlier this morning, Pranab Roy who manages the Library at the Karnavati University‘s UnitedWorld School of Business‘s Kolkata campus popped up on WhatsApp with a question – “Sir, why is Koha not showing the barcode / accession number of a borrowed document when an user logs in into their own account via the OPAC?”

This is what he meant. And this is actually the expected behaviour, with Koha doing exactly what it was asked to do. I could understand his confusion since the OPAC search’s details view showed the barcode quite nicely, then why not for the users themselves?

A bit of backstory

Karnavati University Libraries had shifted to L2C2 Technologies‘ cloud platform from a pre-existing Koha instance maintained by a 3rd party. As such the system had quite a few issues. While we had fixed a larger number of these during the initial on-boarding stage, some of these are getting ironed out only now as the librarians hit these “bumps on the road”. Pranab’s problem was one such.

The Solution

The option to display the barcodes for a logged-in OPAC user’s checkouts (issues) is driven by the SHOW_BARCODE patron attribute. In Koha, patron attributes or more correctly ExtendedPatronAttributes are library-defined custom fields that can be applied to patron records e.g. voter / aadhaar card number, registration number etc.

SHOW_BARCODE is a boolean variable that is defined as either Yes or No. and it is loaded into Koha usually during the web-installer phase of Koha’s installation from the optional SQL dump file: /usr/share/koha/intranet/cgi-bin/installer/data/mysql/en/optional/patron_atributes.sql in Debian package based installations. The tiny file contains a single SQL INSERT statement:

INSERT INTO `borrower_attribute_types` (`code`, `description`, `repeatable`, `unique_id`, `opac_display`, `staff_searchable`, `authorised_value_category`) VALUES (‘SHOW_BCODE’, ‘Show barcode on the summary screen items listings’, 0, 0, 1, 0, ‘YES_NO’);

In the case of Karnavati University this optional patron attribute was not imported during the *original* installation done by the 3rd party support provider at the time. And without “SHOW_BARCODE” being set, Koha had no way of displaying the barcodes of checked out books to patrons logged in via the OPAC.

In the end, the following two lines followed by enabling the ExtendedPatronAttributes system preference cleared off the issue for Karnavati:
$ cd /usr/share/koha/intranet/cgi-bin/installer/data/mysql/en/optional
$ mysql -uroot -p koha_karnavati .

A memcached restart later (to be safe rather than sorry) the OPAC started showing the barcodes to logged-in patrons.

LEGAL DISCLAIMAR: This tutorial is strictly meant for educational purpose. We are in no way responsible if you attempt to follow these steps and end up messing up your production Koha installation somehow.

Setting up yearly calendars is an important task in Koha. Especially in a country like India where we also use other calendars including lunar calendars. Since the religious festivals / holidays usually use these other calendars, the holidays often fall on different days in different years in the Gregorian calendar that Koha uses.

As support providers, we are often asked to setup the calendar for our client-partners. While Koha provides a rather useful user-interface to setup calendars under the Tools menu, we have often found that not only setting up the long list of Indian holidays a tedious affair, it is also quite prone to operator error. So for the Unique holidays we usually use a LibreOffice (a Free Software Office Suite) Calc spreadsheet to quickly generate the batch of SQL statements that can be directed imported into the special_holidays table of Koha using the SQL backend.

We ask our client-partners to send us a spreadsheet that lists the holidays and the days they fall on according to the Gregorian calendar (see the columns marked in yellow above). And then we use a couple of simple formulae to generate the necessary SQL. This approach has two advantages : (a) it’s very fast and (b) completely free of errors from our end.

In this present case, it took us less than 2 minute to upload all the 25 holidays for 2020 into this particular Koha instance.

Caveat The only risk here is that we are going to access the database directly from the command-line and that, unless you know what you are doing, can end up badly, *if* you mess things up.

Adding auto-complete feature to Koha’s MARC21 biblioitems field (Imprint – place, name of publisher, ISBN,edition, etc) as a cataloging aid.

Step - 1

Go to : Koha administration/Global system preferences/Staff interface/IntranetUserJS

Below the Java script  enable of the auto completed in four columns for ISBN, Place of publication, Name of the Publisher, Edition

Copy and paste the bellow JS Coding.

//**Autocomplete support to MARC21 catalogue**//  

$(document).ready(function(){

$( '[id^="tag_260_subfield_a"]' ).autocomplete({

    source: function(request, response) {

      $.ajax({

        url: "/cgi-bin/koha/cataloguing/ysearch.pl",

        dataType: "json",

        data: {

          term: request.term,

          table: "biblioitems",

          field: "place"

        },

        success: function(data) {

          response( $.map( data, function( item ) {

            return {

              label: item.fieldvalue,

              value: item.fieldvalue

            };

          }));

        }

      });

    },

    minLength: 1,

  });

 $( '[id^="tag_020_subfield_a"]' ).autocomplete({

    source: function(request, response) {

      $.ajax({

        url: "/cgi-bin/koha/cataloguing/ysearch.pl",

        dataType: "json",

        data: {

          term: request.term,

          table: "biblioitems",

          field: "ISBN"

        },

        success: function(data) {

          response( $.map( data, function( item ) {

            return {

              label: item.fieldvalue,

              value: item.fieldvalue

            };

          }));

        }

      });

    },

    minLength: 1,

  });

  

  $( '[id^="tag_260_subfield_b"]' ).autocomplete({

    source: function(request, response) {

      $.ajax({

        url: "/cgi-bin/koha/cataloguing/ysearch.pl",

        dataType: "json",

        data: {

          term: request.term,

          table: "biblioitems",

          field: "publishercode"

        },

        success: function(data) {

          response( $.map( data, function( item ) {

            return {

              label: item.fieldvalue,

              value: item.fieldvalue

            };

          }));

        }

      });

    },

    minLength: 1,

  });

 $( '[id^="tag_250_subfield_a"]' ).autocomplete({

    source: function(request, response) {

      $.ajax({

        url: "/cgi-bin/koha/cataloguing/ysearch.pl",

        dataType: "json",

        data: {

          term: request.term,

          table: "biblioitems",

          field: "Editionstatement"

        },

        success: function(data) {

          response( $.map( data, function( item ) {

            return {

              label: item.fieldvalue,

              value: item.fieldvalue

            };

          }));

        }

      });

    },

    minLength: 1,

  });

});

Click Save Button.

Step - 2

Go to : Home/Cataloging/New Record (Enter the all bibliographies details )