Quantcast
Channel: Koha Geek
Viewing all 156 articles
Browse latest View live

Data migration (Unicode) from Excel to koha


Google Analytics with Koha

$
0
0
Many ways a library can track Koha OPAC usage. One method is that use any web analytics software like Matamo. Another method is that use any web analytics service like Google Analytics. Google Analytics can configure with Koha and get OPAC usage statistics. Configure Google Analytics with Koha is easy compared with other tools. This works with only OPAC available on the Internet.

1. First login with Google Analytics using a Google account.

2. Start to create an account by filling the details of your OPAC available on the Internet.

3. Get the site tag

4. Copy the site tag and paste into Koha > Administration > System Preferences > OPAC > opaccredits and Save.


5. Check Google analytics next day see the usage statistics.

Manage collections using Authorized values

$
0
0
Collection management is easy and very convenient with Authorized values feature with Koha. Libraries need to generate collections wise report of records. For example, an engineering college requires collection wise (Mechanical, Civil, Computer etc.) list of books. Such reports have to submit to accreditation agencies (e.g. AICTE, MCI) every year. The same way libraries can create various collections like biography, autobiography, and travelogue. It is found that users add collection codes into Item Type (942$c) mistakenly. They don't know the availability of Authorized values for the purpose. Here are the steps to create collections with Authorized values and generate a collection-wise report.

Add collections to Authorized Values
Go to Koha > Administration > Authorized Values and select CCODE


Select New authorized value for CCODE button.

Add a new Collection Code

1. Enter a shortcode for the new collection. Preferably in capital letter.
2. Enter the description
3. Enter the description for OPAC
4. Select the library branch code.
5. Save the new collection

Same way creates other collections.

Add collection to record
Create a catalogue record, Koha > Cataloguing
Add Biblio information (e.g. author, title, call number etc.)
Save the Biblio information of the catalogue.

The collection code appears in the Item Information part of the catalogue.
Select the appropriate collection code match with the record and save the record.

Generate collection wise report
Item wise search available at Koha > Advanced Search > Go to item search (This feature available with the Koha version 18.05.x onwards).
Select collection code and generate a report.

The collection-based report generates and can view on the browser. The report can download as spreadsheet formats.

Enable IntranetCatalogSearchPulldown menu

$
0
0
IntranetCatalogSearchPulldown gives an advanced search facility along with the universal search box in staff client. This feature is convenient for Koha users to do an extended search without visiting the Advanced Search option.

Search menu
How to enable the IntranetCatalogSearchPulldown

Koha > Administration > Global system preferences

Search for IntranetCatalogSearchPulldown

Select Show and Save.



Information courtesy: Nikesh Narayanan

Display of Amazon cover images

$
0
0
Koha offer book covers display from various enhanced content services (e.g. Amazon, Google). Book covers can display on staff client and OPAC of Koha. Amazon website offer more comprehensive details regarding books compare with Google Books. The display of book cover from Amazon Indian website available since the release of Koha version 18.11. The previous version had not listed Amazo Indian service. The bug 21403 reported by Prasanth Kumar, Library Trainee at IIITDM Kancheepuram. The bug resolved in Koha version 18.11. Here are the steps to display book cover from Amazon Indian service (http://amazon.in).


1. Obtain the Amazon Associate Tag 

Visit the https://affiliate-program.amazon.in site and register to get the tag. Note down the tag.

2. Make sure that your catalogue records have the ISBN number. Then the only book covers to display on OPAC and staff client.


3. Add Amazon tag to Koha System Preferences

Koha Administration > Global System preferences > Enhanced Content > Amazon
Change the preferences for Amazon the same as in the screenshot.
Change the preferences for Amazon the same as in the screenshot.
Save changes.

4. Remove the "No cover image" message on the OPAC

Koha Administration > Global System preferences Search for the item OPACUserJS

Copy and paste the following code into the OPACUserJS box and save.

$(document).ready(function(){
    $('.no-image').remove();
});

Goto the OPAC search for any book with ISBN number

Information courtesy: Prasanth Kumar, Library Trainee at IIITDM Kancheepuram

Show nothing when cover images are not found

Display barcode on OPAC Normal view

$
0
0


I tried this feature on Koha version 18.11.x.

Goto Koha > Administration > Additional Parameters > Configure columns > OPAC > Item_barcode

Uncheck it and Save. 


Information courtesy: Richard Vargas

Install MariaDB 10.4 on Debian 9 (Stretch)

$
0
0
Debian 9 (Stretch) install MariaDB 10.1 from it's repository. Its possible to install latest version of MariaDB on Debian 9 to get good database performance. Here is the method to install MariaDB 10.4 on Debian 9 when preparing system for Koha installation. This method can apply for a fresh installation of Koha. Don't try on existing installation of Koha.

Install dirmngr

sudo apt-get install software-properties-common dirmngr

Importing the MariaDB GPG Public Key and install MariaDB
Apply following commands,

sudo apt-key adv --recv-keys --keyserver hkp://keyserver.ubuntu.com:80 0xF1656F24C74CD1D8

sudo add-apt-repository 'deb [arch=amd64,i386,ppc64el] http://mirrors.accretive-networks.net/mariadb/repo/10.4/debian stretch main'

sudo apt update

sudo apt-get install mariadb-server

Assign Root password for MySQL

Apply following command,

sudo mysqladmin -u root password newpass       [Replace 'newpass' with new password]

References
https://mariadb.com/kb/en/library/installing-mariadb-deb-files/#importing-the-mariadb-gpg-public-key

https://downloads.mariadb.org/mariadb/repositories/#distro=Debian&distro_release=stretch--stretch&mirror=rise&version=10.4

Hardware selection for Koha installation

$
0
0
Library professionals need to acquire background knowledge on hardware selection before the installation/upgrade Koha ILS. Consider budget, the number of records and number of users handles by Koha before the hardware selection. Here are the various occasions and suitable hardware requirements.

Desktop PC: Majority of libraries in India install Koha on desktop PC. Library professionals switch off PC before closing the library and next day they switch on PC to use Koha. Libraries having budget constraints, lack of higher hardware resources and power backup would like to follow this method regardless of the number of records and transactions with Koha. Such libraries can't offer 24x7 OPAC services with Koha on a desktop PC.

Libraries with a small collection (e.g. up to 25000 books) consider a desktop with i5 processor and minimum 8 GB RAM. Buy desktop PC without preloaded Windows. It increases the cost of the PC. Buy PC without Operating System. Use Debian/Ubuntu with a lightweight desktop for the optimum performance of hardware. Ubuntu/Debian with GNOME desktop would eat a sizeable processing power of your PC. Choose Debian Linux with XFCE desktop/Xubuntu/Lubuntu as the operating system for Koha. Opt SSD (Solid State Drives) over traditional HDD as storage for fast performance. Desktop PCs not built for 24x7 performance like a server-class computer. 

Workstation PC: Libraries want heavy-duty performance machines can opt workstation PC. Workstation PC is better than desktop PC in terms of performance and durability. It can handle the library tasks with a large number of records, users, transactions and multiple library branches. Popular computer manufacturers produce workstation PC under separate brand names. For example, Dell Precision, Lenovo Thinkstation, and HP Z belong to the workstation category. 

Server computer: Libraries with excellent IT infrastructure would like to choose a server-class computer for Koha installation. Server computer built for 24x7 hours continuous working and offer static Koha service. I found that libraries with a small collection buy heavy-duty server computer and switch off at the evening when the office time over. This practice affects the performance and reduces the life span of the server computer.

Server class computers available with various specifications. Libraries with small size collections can choose entry-level servers computers for Koha installation. For example, HP Proliant ML series tower server computers cost below Rs. 80000.

Cloud computing: Cloud computing services became more convenient for these days. Libraries free from maintaining hardware for Koha service. Institutions can hire virtual servers from cloud service providers like Amazon, Google, and Microsoft. Libraries can choose virtual servers with a Linux (Debian/Ubuntu) operating system for Koha installation.

Accession Register report

$
0
0
Koha version: 19.05.3
Module: Catalogue
Purpose: Accession register with joined Title and subtitle, Authors and Editors
SELECT items.barcode,items.itemcallnumber,
CONCAT_WS('',biblio.author,'; ',ExtractValue(metadata,'//datafield[@tag="700"]/subfield[@code="a"]')) AS Author,CONCAT(biblio.title,'',ExtractValue(metadata,'//datafield[@tag="245"]/subfield[@code="b"]')) AS Title,biblioitems.publishercode
FROM items
LEFT JOIN biblioitems ON (items.biblioitemnumber=biblioitems.biblioitemnumber)
LEFT JOIN biblio ON (biblioitems.biblionumber=biblio.biblionumber)
LEFT JOIN biblio_metadata on (biblio_metadata.biblionumber=biblio.biblionumber)
WHERE items.homebranch =<<Branch|branches>> AND items.itype=<<Item type|itemtypes>> AND items.dateaccessioned BETWEEN <<Between Date (yyyy-mm-dd)|date>> and <<and (yyyy-mm-dd)|date>> ORDER BY items.barcode DESC

Data migration: importing of check-out entries from an old version of Koha

$
0
0
Restoration of an old version of a corrupted database to the latest version of Koha is a challenging task. Data migration from a running instance of an old version of Koha is comparatively easy. Porting of bibliographic records to MARC format, patron details and circulation details to CSV is possible. Then it can be imported into a new version of Koha.

This tutorial discusses the various stages in exporting of check-out (issue) details from the old version of Koha into latest version.


Background preparation

  • Export bibliographic details (MARC format), patron and circulation details.
  • Install a new version of Koha. Create branch code, Patron categories, Authorised values, circulation and fine rules same like the old version of Koha.
  • Import MARC file and patron details.

Exporting of checkout entries

Prepare a report of all books checked out

Koha > Report > Create from SQL Enter following SQL query.

SELECT issues.issuedate,borrowers.cardnumber,items.barcode 
FROM issues  
LEFT JOIN borrowers ON borrowers.borrowernumber=issues.borrowernumber   
LEFT JOIN items ON issues.itemnumber=items.itemnumber    
LEFT JOIN biblio ON items.biblionumber=biblio.biblionumber 
ORDER BY issues.issuedate DESC

Run the report and export it as CSV format.

Create offline circulation file


Open the All Book Checkout Out report in LibreOffice or any other spreadsheet application.

Add a new column between issuedate and cardnumber columns. Put the line 'issue' in all rows. Koha recognises that these entries for checkout of books. 


Transfer checkout entries from CSV file to .koc (Koha Offline Circulation) file.
Download a sample .koc file from here.
Open the .koc file using a text editor (e.g. leafpad. mousepad).
Copy the entire checkout entries from csv (except column names) to .koc file.


Save and close the .koc file.

Import .koc file into Koha

Make sure that all records, patron details imported into Koha before import .koc file. Circulation rules should be created.

Koha > Circulation > Offline circulation > Upload offline circulation file (.koc)



Choose the .koc file and upload.
The screen may show a timeout. The process will go on behind. Check the status after a few minutes.

Koha > Circulation > Offline circulation > Pending offline circulation actions

The check out entries successfully imported

Calculate the fine

Run the following commands to calculate the fines.

cd /etc/cron.daily/
sudo ./koha-common

Check the status of successful entries by visiting a patron account.

Data migration: bulk check-in

$
0
0
Bulk check-in using .koc (Koha Offline Circulation) file is easy to use the method. It is helpful while Koha trial runs for data migration from the old version of Koha or other software. This method also can apply to other contexts. The following steps discuss how to prepare the .koc file for bulk import of check-in entries.


1. Export report of desired checked out books

Koha > Report > Create from SQL

Use following SQL query to build a report for the purpose,

SELECT issues.issuedate,items.barcode 
FROM issues 
LEFT JOIN borrowers ON borrowers.borrowernumber=issues.borrowernumber 
LEFT JOIN items ON issues.itemnumber=items.itemnumber   
LEFT JOIN biblio ON items.biblionumber=biblio.biblionumber
WHERE items.homebranch =<<Branch|branches>> AND issues.issuedate BETWEEN <<Between Date (yyyy-mm-dd)|date>> and <<and (yyyy-mm-dd)|date>> ORDER BY issues.issuedate DESC

Download the report as a CSV or ODS (Open Document Spreadsheet) file.

2. Prepare the .koc file

Open the checked-out report file and add a new column to the mention transaction type.
Copy the contents in three columns. See the sample CSV file here.


Download and open the sample .koc file from here.
Copy and paste the contents below the first line in the .koc file.


Save and close the file.

3. Import the .koc file

Goto Koha > Circulation > Offline circulation > Upload offline circulation file (.koc) 
Find and upload the .koc file. Don't worry, if the screen show time out.

Goto Koha > Circulation > Offline circulation > Pending offline circulation actions
Select all the entries and click the Process button.

References

Firefox Addon for Koha Offline circulation
https://addons.mozilla.org/en-US/firefox/addon/koct/

Koha offline circulation file format
https://wiki.koha-community.org/wiki/Koha_offline_circulation_file_format

Add library location on OPAC using Google map

$
0
0
The location of the institute/library can be embed on OPAC interface. Users strange to the campus can find the location of the library using Google Maps app in mobile. Follow the steps below to add the location on OPAC interface.

Find the location from Google Maps

Visit https://www.google.com/maps

Search your institution/library name,

Click on the share button.


Click on embed a map tab.



Copy the code.

Display of location on OPAC

Copy and paste the code anywhere in OPAC.
For example, Koha > Administration > Global System Preferences > OPAC > OpacNav

The map can also display on the left side of the OPAC,
Tools > News > New Entry > Display location > OpacNavRight



How do change timezone

$
0
0
Many occasions the timezone of the Debian/Ubuntu maybe not be correct. Incorrect timezone might be happening at the time of Linux installation. It affects the due date setting and fine calculation with Koha. User can configure to the correct timezone later. Here are the steps to follow reconfigure the timezone.

1. First, check the default timezone with Koha, check at Koha > About Koha
2. Apply the following command in a terminal,

sudo dpkg-reconfigure tzdata

A configuration screen will appear. Change the timezone.

Select your geographic area.
Select the timezone
3. Check again the timezone information with Koha. Otherwise, apply the following command in a terminal.
date

Stay on with a Koha version

$
0
0
Koha releases a new version every six months (May and November). The current version is called stable and previous version is called oldstable. The code names stable or oldstable should be mention in the Koha Debian software repository line at the time of installation. For example,
After six months the current version of Koha changes to the latest release. Koha users can't stick on with a particular version by using the code name stable and oldstable in Koha repository. 

A Koha version has 18 months maintenance period. Koha users can stay with a specific version by using the version number (e.g. 19.11). Users can receive the updates during the period until the version expiry (18 months).

Add the version number in Debian Koha repository to stick on with the specific release; e.g.

echo 'deb http://debian.koha-community.org/koha 19.11 main' | sudo tee /etc/apt/sources.list.d/koha.list

References
Koha on Debian

Koha versioning

Manage bound volumes

$
0
0
Koha can handle bound volumes of periodicals. Users can know the availability of bound volumes of periodicals along with latest and previous issues.

First, create an item type for bound volume.
Administration > Item types > New item type


Create a journal subscription first. Search and find the journal details at staff client.


Create an item for the journal bound volume.
Enter the details regarding the bound volume.

1. Enter the volume and issues contained in the bound volume.
2. The accession number of the bound volume.
3. Add the item.

See the bound volume details of the periodical at online catalogue.


Serials management

$
0
0
Serials module assist in managing subscription of journals, magazines, newspapers etc. Serials module is helpful to inventory and tracks periodicals. Library users can quickly know the availability of periodicals through OPAC.

Create a subscription
Following are the steps to create a journal subscription.
Create a Biblio
First, create a Biblio from Koha > Cataloguing.
Enter the details of the journal including ISSN, title, publisher etc. Save the Biblio. No need to save the Item information.

Note:Adding a representative journal jacket to catalogue record will be more attractive and users can easily recognise the journal while searching from OPAC. Journal cover picture can be collected from the publisher website. The journal cover can be upload from Biblio details in the staff client.

Create a vendor
If the library subscribes the periodicals through a vendor, create a vendor/supplier. Koha > Acquisitions > New vendor
Create subscription
Go to the Serials module and create a subscription for the journal.
Koha > Serials > New subscription
Search and find both vendor and Biblio of the journal created.
Add caption
Call number: Item’s call number of the journal.
Library:  The branch subscribed the journal.
Public note: Information for the OPAC for the patrons (e.g. Discontinuation of a particular volume)
Nonpublic note: Notes that are only visible to the librarians via the staff client (e.g. Demand Draft details).
Patron notification: Notice sends to patrons on arrival of new issues (Routing list).
Location: Shelving location of the journal.
Grace period: The number of days before an issue automatically move from ‘Expected’ status to ‘Late’.
The Staff and OPAC display options allow you to control how many issues appear by default on bibliographic records in the Staff Client and the OPAC.

First issue publication date: First issue of the journal after the subscription starts. Frequency: Various frequency of the journal (e.g. Weekly, monthly, quarterly etc.) Subscription length: The number of issues or months in the subscription. Subscription start date: The date at which the subscription begins. Subscription end date: End date of the current subscription. Numbering pattern: The numbering pattern follows in the journal (e.g. Volume, Issue). Locale: To display days, months, the season in regional language (e.g. Persian). Click on Test prediction pattern to get an idea of the issue numbering of the journal. Save the subscription.

Receive the first issue of the journal
Receive the first issue of the journal after creating the subscription.
Change the status from Expected to Arrived.
The current issue of the journal received and waiting for the next issue.
Search and find the journal at an online catalogue. See the bibliographic and holding details of the journal.

Attach items into a single record

$
0
0

Items with discrete records are not convenient for users to find documents through OPAC. Koha users can attach items with separate Biblio into a single record. Here are the steps to attach items with discrete Biblio.

For example, bound volumes of Economic and Political Weekly catalogued as separate records with items. The search result shows many records of the journal bound volumes. If we merge all the records into one, users can find the journal bound volumes details by opening a single record.
Find the record to merge/attach.
Search and find the record to attach from Koha Staff Client.

Attach each item to the record
Select any record and select Edit > Attach item.

Find the sequence of barcode/accession number of the same records using by creating a report.

Enter the barcode of the first record,

Click on Submit button.

1. Delete the blank record after merge the item.
2. Enter another record to merge.
3. Click OK to confirm.

Search and find the details of the record after finishing the process.

DBIx::Class::Storage::DBI::catch (): DBI Connection failed

$
0
0
Many Koha users have reported following error when login for post installation configuration.

Software error:
DBIx::Class::Storage::DBI::catch (): DBI Connection failed: Access denied for user ikoha_librarylvlocalhost' (using password: YES)
For help, please send mail to the webmaster ([no address  given]), giving this error message and the time and date of the error.

Solution
Apply the following command and start Memcached service.

sudo service memcached restart

Refresh the browser window.

Upgrade/migration from a very old version of Koha

$
0
0
Libraries stick on with old versions of Koha facing difficulties while trying to upgrade to the new version. Upgrading from very old versions to the latest version may result in data loss. Koha stops the official support for older versions after a specific period. Same way, Koha support for old Ubuntu versions stops when it becomes obsolete. New versions of Koha introduce a lot of improvements and new features. Changes in database structure required to accommodate new features. For example, Koha version 3.18 released in 2014, and it has 168 tables. Version 19.05, released in 2019, has 204 tables. Koha developers strongly recommend for the regular up-gradation to recent versions. The database structure is also subject to changes during the upgrade process.

Direct up-gradation from old versions (e.g. versions before version 3.18) to the latest version probably ends in data loss. Restoration of an old version of Koha is a challenging task. Data migration from a running instance of an old version of Koha is comparatively easy. Porting of bibliographic records to MARC format, patron details, and circulation details to CSV is possible. Then it can be imported into a new version of Koha. Following steps can follow to export essential data:
  • Note down all configurations with Koha including branch code, item types codes, authorized values, circulation and rules. Take screenshots of all configurations.
  • Export bibliographic details (MARC format) into MARC.
  • Export patron and circulation details into CSV format using reports.
  • Install a new version of Koha. Create branch code, Patron categories, Authorised values, circulation match with the old version of Koha.
  • Import MARC file, patron, and circulation details.
Note: Consult Koha release notes and installation manual at Koha Wiki for regular updates on changes.
Viewing all 156 articles
Browse latest View live