- Koha - lists.katipo.co.nz

Dspace vs Greenstone ...other???
by mohan pradhan 01 May '15

01 May '15

Regarding DSpace vs Greenstone, Dspace is better as it has lucene indexing and it is more stable. Let me know the issues of DSpace you would like to solve. I may help. Regards, Prof. Dr. Mohan Raj Pradhan Member-Secretary HealthNet Nepal Date: Thu, 30 Apr 2015 16:25:31 -0700 From: Chad Roseburg <croseburg(a)ncrl.org> To: "koha(a)lists.katipo.co.nz" <koha(a)lists.katipo.co.nz> Subject: [Koha] Dspace vs Greenstone ...other??? Message-ID: <CAEboqJNzwaMyUDJfqe6O6evyxVkizgL7AFdAOdA=mKfwizN5yg(a)mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Would anyone care to comment on why they chose Dspace over Greenstone ...vice versa, or went with something else like contentDM? >I just installed Dspace and am kicking the tires. Looking for experiences >maintaining, upgrades/updates ...ease of use ...etc. We do have experienced >onsite IT staff but if it requires a lot of hand holding that may be a >factor. We would likely get some type of support contract and host the >server ourselves. >Thank you! -- >Chad Roseburg >Automation Dept. >North Central Regional Library

1 0

Running koha on Debian Jessie.
by Alex King 01 May '15

01 May '15

I have been given the task of checking an install of koha running on a recently installed Debian server. The instance is a 3.19 snapshot installed from a deb from koha-community.org running on Debian 7.7 (Wheezy). I'd like to upgrade the OS to Debian 8 (Jessie), which has recently been released as stable. I came across a message from Robin, which I can't find now, to the effect that a dependency issue required a patch which was due to land in 3.18.06. So after I take a backup, I'm going to (up)grade koha to 3.18.06 and the OS to 8.0. Is anyone aware of outstanding issues running this configuration? The wiki documentation at http://wiki.koha-community.org/wiki/Koha_on_Debian seems out of date, further down the page it talks about squeeze and even lenny. I assume stable packages are targeted for wheezy or both wheezy and squeeze. If there are no objections, I'll update that page to refer to wheezy instead, and put a note to the effect that it should be possible to run it on jessie but as of April 2015 it's a less well tested configuration than running on Wheezy. Thanks, Alex

4 5

Jenkins & the Manual
by Nicole Engard 01 May '15

01 May '15

Hi all, I don't know who manages this so I'm sorry to email everyone, but the manual on Jenkins is a big screwy. http://jenkins.koha-community.org/ The 3.18 branch is missing and the master branch fails all the time but it generates the HTML and PDFs a-ok and shows no errors when I validate in Oxygen. Eventually the failures stop and it passes - so I know nothing is wrong with the manual itself, I wonder if something is screwy with the fact that the wrong branches are being checked. Nicole

1 0

Acquisitions Documentation Question
by Nicole Engard 30 Apr '15

30 Apr '15

I have been asked to define the columns on this page: cgi-bin/koha/admin/aqbudgets.pl?budget_period_id=34 I'm not sure what the base level columns are supposed to be. Can someone break down for me what each column is so I can update the manual? Thanks Nicole

2 3

updatedatabase.pl – 2nd request for help
by Jürgen Eichenbrenner 30 Apr '15

30 Apr '15

A few days ago I complained here about: updatedatabase.pl Sorry, for nagging again. I have to be more specific. It seems to me, there were changes of the database scheme, not reflected properly in the updatedatabase.pl script. It fails (with mysql error s150), when upgrading a database from 3.10 to any newer version of Koha, in creating the following three tables: - borrower_attributes_types_branches - categories_branches - authorised_values_branches For getting around this, I tried to create the (new 3.12) Koha scheme before I dump in the old 3.10 database dump into a new (3.12) installation. Even then I get errors (which I reported here a few days ago). If I don't create the newer Koha database scheme beforehand, the "Web installer" gives errors like this: updatedatabase.pl: DBD::mysql::db do failed: Can't create table 'koha312.categories_branches' (errno: 150) at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 6120. In fact, these statement, like the one from line 6120: CREATE TABLE categories_branches(categorycode VARCHAR(10), branchcode VARCHAR(10), FOREIGN KEY (categorycode) REFERENCES categories(categorycode) ON DELETE CASCADE, FOREIGN KEY (branchcode) REFERENCES branches(branchcode) ON DELETE CASCADE ) ENGINE=INNODB DEFAULT CHARSET=utf8; are failing with mysql error 150. Besides of the three additional table creations, there are 6 duplicate entries of PRIMARY keys in the tables: 'OPACNumbersPreferPhrase' 'IntranetNumbersPreferPhrase' 'UNIMARCAuthorityField100' 'l-overdues_report' 'UNIMARCAuthorsFacetsSeparator' 'CalculateFinesOnReturn' And a duplicate key name: 'batch_id_record_type' Because of this I'm stuck with 3.10 and appreciate any hints and help for getting this solved properly. Jürgen Eichenbrenner Int. School of Stuttgart

3 2

Zebra Status - Is Zebra active? + understanding cmd outputs
by Craig Butosi 30 Apr '15

30 Apr '15

Hi all, I just successfully migrated my koha system to a VPS (Ubuntu 14.04 LTS 64-bit + Koha 3.18.06), and restored the database via mysql. I'm in the process of activating the Z39.50 server and I noticed something odd (again!). When I ran koha-restart-zebra, the terminal returned the following: "Zebra does not appear to have been running for instance library" | "Starting Zebra server for instance library". This is odd, because each time I ran koha-restart-zebra, it returned the same message. I am interpreting this output as zebra not running at all, so now I'm a bit confused ( as OPAC and Staff search are working fine, though I haven't catalogued or imported any new records since the migration). So, I ran ps aux | grep zebra and it returned the following output koha 12183 0.0 0.0 10892 936 pts/0 S+ 10:10 0:00 grep zebra library+ 26249 0.0 0.0 19176 248 ? S Apr28 0:00 daemon --name=library-koha-zebra --pidfiles=/var/run/koha/library/ --errlog=/var/log/koha/library/zebra-error.log --stdout=/var/log/koha/library/zebra.log --output=/var/log/koha/library/zebra-output.log verbose=1 --respawn --delay=30 --user=library-koha.library-koha -- zebrasrv -v none,fatal,warn -f /etc/koha/sites/library/koha-conf.xml library+ 26250 0.0 0.0 113264 1248 ? S Apr28 0:00 zebrasrv -v none,fatal,warn -f /etc/koha/sites/library/koha-conf.xml I also ran ps -f -C zebrasrv which returned the following output UID PID PPID C STIME TTY TIME CMD library+ 26250 26249 0 Apr28 ? 00:00:00 zebrasrv -v none,fatal,warn -f /etc/koha/sites/library/koha-conf.xml Is there anything fishy going on with the above outputs? I modified the koha-conf.xml file on April 28th, but have since made sure that that file is correctly edited (April 29th). Do the above mean that Zebra is indeed running? Thanks everyone! Best, Craig Butosi, MA, MLIS, B Mus (Hons.) LIBRARY SERVICES MANAGER the royal conservatory TELUS Centre for Performance and Learning 273 Bloor Street West Toronto, ON M5S 1W2 416.408.2824 x338 www.rcmusic.ca Note: This email message and any attachments are intended only for the use of the individual to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the recipient of this email is not the intended recipient (or the employee or agent responsible for delivering the email to the intended recipient), you are hereby notified that any review, dissemination, distribution or copying or other use of this message is strictly prohibited. If you have received this communication in error, please notify the sender immediately by return email and delete this message and attachments from your system, thank you.

2 1

India specific Open source SMS::Send driver for Unicel released for use with Koha ILS
by Indranil Das Gupta 30 Apr '15

30 Apr '15

Dear all, Good news for Koha users in India who wish to use ‪SMS‬ notifications from Koha. I've published an ‪open-source‬ India specific SMS::Send driver that can be used with Koha if you are an ‪Unicel Technologies‬ customer. Unicel Technologies is a fast growing bulk messaging provider from Bangalore, India. Recently I found myself testing out their transactional SMS service (for alerts and notifications from ‪Koha‬). Initially I wrote a rudimentary driver for my own use. But seeing the demand for support of SMS notifications from Koha coming from Indian users on various fora, I decided to turn it into a formal SMS::Send driver and open source it by uploading it CPAN. http://search.cpan.org/~indradg/SMS-Send-IN-Unicel-0.01/lib/SMS/Send/IN/Uni… My thanks to Jonathan Druart for clearing my doubts on koha-devel, and to Galen Charlton and Chris Cormack for being kind enough to review the module on PrePAN. Thank you all :) Happy Texting! regards, -- Indranil Das Gupta L2C2 Technologies Phone : +91-98300-20971 / +91-98745-80971 Blog : http://indradg.randomink.org/blog IRC : indradg on irc://irc.freenode.net Twitter : indradg -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=- Please exchange editable Office documents only in ODF Format. Support Open Standards. For a free editor supporting ODF, please visit LibreOffice -

1 0

Recall: Items borrowed alert
by Hartman, David W. - Tech Library 29 Apr '15

29 Apr '15

Hartman, David W. - Tech Library would like to recall the message, "Items borrowed alert".

1 0

updatedatabase.pl failing from 3.10 to 3.12
by Jürgen Eichenbrenner 28 Apr '15

28 Apr '15

Upgrading from 3.10.13 to 3.12.15 or any higher version, the updatedatabase.pl script is broken. Does it work when I upgrade to a lower 3.12 version? Or do I have to fix this manually? Or is there a script to get it fixed? Thanks, Jürgen Eichenbrenner, International School Stuttgart. [Tue Apr 28 12:29:33 2015] updatedatabase.pl: DBD::mysql::db do failed: Table 'borrower_attribute_types_branches' already exists at /home/koha/koha312/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 6119. [Tue Apr 28 12:29:33 2015] updatedatabase.pl: DBD::mysql::db do failed: Table 'categories_branches' already exists at /home/koha/koha312/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 6121. [Tue Apr 28 12:29:33 2015] updatedatabase.pl: DBD::mysql::db do failed: Table 'authorised_values_branches' already exists at /home/koha/koha312/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 6123. [Tue Apr 28 12:29:33 2015] updatedatabase.pl: DBD::mysql::db do failed: Duplicate entry 'OPACNumbersPreferPhrase' for key 'PRIMARY' at /home/koha/koha312/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 6405. [Tue Apr 28 12:29:33 2015] updatedatabase.pl: DBD::mysql::db do failed: Duplicate entry 'IntranetNumbersPreferPhrase' for key 'PRIMARY' at /home/koha/koha312/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 6406. [Tue Apr 28 12:29:33 2015] updatedatabase.pl: DBD::mysql::db do failed: Duplicate entry 'UNIMARCAuthorityField100' for key 'PRIMARY' at /home/koha/koha312/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 6413. [Tue Apr 28 12:29:33 2015] updatedatabase.pl: DBD::mysql::db do failed: Table 'linktracker' already exists at /home/koha/koha312/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 6458. [Tue Apr 28 12:29:33 2015] updatedatabase.pl: DBD::mysql::db do failed: Duplicate key name 'batch_id_record_type' at /home/koha/koha312/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 6483. [Tue Apr 28 12:29:33 2015] updatedatabase.pl: DBD::mysql::db do failed: Duplicate entry '1-overdues_report' for key 'PRIMARY' at /home/koha/koha312/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 6492. [Tue Apr 28 12:29:33 2015] updatedatabase.pl: DBD::mysql::db do failed: Duplicate entry 'UNIMARCAuthorsFacetsSeparator' for key 'PRIMARY' at /home/koha/koha312/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 6538. [Tue Apr 28 12:31:08 2015] updatedatabase.pl: DBD::mysql::db do failed: Duplicate entry 'CalculateFinesOnReturn' for key 'PRIMARY' at /home/koha/koha312/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 6845.

3 2

3.18.06 Package Warning
by Renvoize, Martin 28 Apr '15

28 Apr '15

tl;dr Don't Upgrade Koha Packages to 3.18.06 yet! Hi All, Though I'd send a quick heads up that there's a nasty bug in the 3.18.06 package (available on the debian.koha-community.org repository). An upgrade will result in a couple of warning about unpacking some yui library files on the command line and in my experience so far, leave you with a rather nasty display in the staff client. I'm sure it's a trivial fix at this end once rangi or eythian is awake, but I'd hold off on upgrading until they give the go ahead ;) Martin Renvoize Software Engineer, PTFS Europe Ltd Content Management and Library Solutions Skype: Landline: 0203 286 8685 Mobile: 07725985636 http://www.ptfs-europe.com

6 8