- Koha - lists.katipo.co.nz

koha 3.14.13 released
by Fridolin SOMERS 03 Nov '15

03 Nov '15

The Koha community is proud to announce the release of 3.14.13. This is a security and maintenance release and contains 2 security bugfixes. As always you can download the release from http://download.koha-community.org. Have a look at release post : http://koha-community.org/koha-3-14-13-released "Get the pie while it's hot". Regards, -- Fridolin SOMERS Biblibre - Pôles support et système fridolin.somers(a)biblibre.com

1 4

Koha 3.18.12 released
by Liz Rea 02 Nov '15

02 Nov '15

The Koha community are pleased to announce the release of Koha 3.18.12, a maintenance and bugfix release of the popular open-source library management system. Packages for Debian will be available soon, or you can download the tarball from http://download.koha-community.org. Thanks to all contributors! Liz Rea

1 0

in which file is the term by
by tigran＠flib.sci.am 02 Nov '15

02 Nov '15

dear List, who can point the name(s) of the file(s) in which the term 'by' (being displayed before the author name) is present. I'm in charge for Armenian localisation, and direct translation of 'by' is not correct. The term should be replaced by spaces. So want to know the names, to remove Armenian translation of 'by' and replace with spaces. See attached files. Tigran

2 1

Zebra (Koha 3.20.05) - Run it as a cron job or use default daemon?
by Craig Butosi 02 Nov '15

02 Nov '15

Hi all, Koha 3.20.05 on Ubuntu 14.04 LTS x64 VPS (package install) Was just wondering if it is still recommended to run zebra as a cron job (/usr/share/koha/bin/migration_tools/rebuild_zebra.pl) rather than using the zebraqueue. I've read older posts saying that this was case (ca. 2008-2013). If it is recommended to run it as a cron job (as koha user of course), I read also that it is necessary to disable the zebraqueue to avoid conflicts. How would I do that? With <$ service koha-stop-zebra instancename>? Thanks all! C 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<http://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.

3 4

Hold fees expected functionality
by Joonas Kylmälä 02 Nov '15

02 Nov '15

Hello there, Since there has been discussion earlier in this mailing list and in Bugzilla <http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13592> about what should be the behaviour when charging a fee from a hold, I thought to ask you people here. At the moment if you have set a holding fee for X category of accounts the fee is only charged when there is no items available for loan or some other patron has placed a hold already in biblio or item level (correct me if I'm wrong, because I think I am..). This makes it impossible to charge a fee when someone makes a hold of a specific item (which might be because the specific item is not available in the patrons home branch but is in some other). So in that scenario no fee will be charged from the patron. I suggest that there would be some system preference where one could define if one wants to have the hold charge from an biblio record level or from an item level. Also I think some other scenarios should be taken in account. So, please, tell your opinions about this and how do you want it to be done. Note: you can find the setting to enable item level holds here: <http://10.0.3.132:8080/cgi-bin/koha/admin/smart-rules.pl> Best regard, Joonas Kylmälä

3 2

Records missing from data export
by David Liddle 02 Nov '15

02 Nov '15

I'm preparing to help a library switch to Koha over the next few months. In testing the "Export data" tool today, I discovered that 2 of the 4 bibliographic entries are missing from the export. (The entries are only samples used to test the import and linking of records.) The XML export file and the MARCXML files saved from the individual records are attached to this message, assuming they passed through any list filters. Can someone help me understand what causes the omission of these two records? Thank you! ------------------------------ *David Liddle* *IT Support Specialist* Wycliffe Global Alliance - Europe Area Siegenweg 30, 57299 Burbach, Germany *Direct:* david_liddle(a)wycliffe.net *Support:* sos_europe(a)wycliffe.net *Bomgar:* https://sos.wycliffe.net <https://sos.wycliffe.net/download_customer_connector.ns?id=65&name=David+Li…> *Office:* +49 2736 298 302, Ext. 107 *Mobile:* +49 176 421 473 69 *Skype:* dfliddle

4 7

Re: [Koha] Display question
by Paul A 02 Nov '15

02 Nov '15

At 04:29 PM 10/29/2015 -0400, Barton Chittenden wrote: >Off hand, I would say that you would run into errors if and when you >deleted the bib record a second time... Koha will want to copy the data >from biblio to deleted_biblio then remove the bib record, but it will get a >referential integrity check if it tries. My guess is that you would have to >remove the record via the database. I seem to remember (but can't easily find my notes -- previous sandbox, can't remember which version) that it just overwrites. But this brings up the question "how to restore a deleted biblio?" It's been mentioned a couple of times on this list, with people trying to use MySQL INSERT statements and failing without using MarcEdit as an intermediary. Is there any simple way to restore one? If not, why do we save them? Our experience is that we delete duplicates (which occasionally happen despite Koha trying to warn cataloguers), and twice in the last five years I've just wiped them from the db to save space in the back-up dumps. Best -- Paul >On Oct 29, 2015 3:41 PM, "Steve Sowder" <sowder(a)andrews.edu> wrote: > > > What kind of problems? > > > > Steve > > > > On 10/29/2015 3:23 PM, Katrin Fischer wrote: > > > >> The biblionumber is the unique database assigned key for Koha, but as > >> Chris has pointed out it is useless in another context and outside of > >> Koha. > >> > >> I'd argue that reusing a deleted biblionumber like how you described > >> sounds like a bug - it should not be possible to do that. One of the > >> reasons being that then you'd have the same biblionumber in biblio and > >> deletedbiblio and that would create problems. > >> > >> Katrin > >> > >> Am 29.10.2015 um 19:52 schrieb Steve: > >> > >>> The biblionumber can be used to match on if reloading records. I have > >>> exported MARC records, made some mass changes, and then reloaded the > >>> changed records by matching on the biblionumber. (Match points 10, if > >>> points > 5 then go.) Worked well. > >>> > >>> I have even loaded new records by assigning a biblionumber that I know > >>> had been deleted in Koha. > >>> They loaded fine and assumed the biblionumber that I assigned. > >>> > >>> > >>> Steve Sowder Systems Librarian > >>> sowder(a)andrews.edu Andrews University > >>> > >>> > >>> On 10/29/2015 2:15 PM, Chris Cormack wrote: > >>> > >>>> Hi Tim > >>>> > >>>> You could edit either the .tt file or make a custom XSLT file to do > >>>> that. > >>>> > >>>> But please do not make the mistake that was made with MARC and give a > >>>> machine used value any human significance. The biblionumber is the > >>>> primary key on a database row to allow Koha to identify a biblio. > >>>> It should not be given any human significance, accession numbers, > >>>> control numbers etc play that role for humans. > >>>> > >>>> Hope this helps > >>>> > >>>> Chris > >>>> > >>>> > >>>> > >>>> On 30 October 2015 7:05:55 am NZDT, Tim Skeers > >>>> <tim.skeers(a)lib.state.ia.us> wrote: > >>>> > >>>>> Is there an easy way to get the biblionumber of a record to display > >>>>> somewhere on the "normal" view for a record in the staff interface? Or > >>>>> would it require an actual programming change? > >>>>> > >>>>> As it is, it displays in the URL in the browser navigation window, but > >>>>> I would like to be able to print out a record with it showing on the > >>>>> printout. > >>>>> > >>>>> Thanks, > >>>>> > >>>>> Tim > >>>>> > >>>>> > >>>>> Timothy Skeers | Cataloger | Iowa Library Services/State Library of > >>>>> Iowa | 1112 E. Grand Avenue | Des Moines, Iowa | 50319 | > >>>>> tim.skeers(a)lib.state.ia.us | (515) 725-0605 > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> _______________________________________________ > >>>>> Koha mailing list http://koha-community.org > >>>>> Koha(a)lists.katipo.co.nz > >>>>> https://lists.katipo.co.nz/mailman/listinfo/koha > >>>>> > >>>> _______________________________________________ > >>> Koha mailing list http://koha-community.org > >>> Koha(a)lists.katipo.co.nz > >>> https://lists.katipo.co.nz/mailman/listinfo/koha > >>> > >> _______________________________________________ > >> Koha mailing list http://koha-community.org > >> Koha(a)lists.katipo.co.nz > >> https://lists.katipo.co.nz/mailman/listinfo/koha > >> > >> > >> > > _______________________________________________ > > Koha mailing list http://koha-community.org > > Koha(a)lists.katipo.co.nz > > https://lists.katipo.co.nz/mailman/listinfo/koha > > >_______________________________________________ >Koha mailing list http://koha-community.org >Koha(a)lists.katipo.co.nz >https://lists.katipo.co.nz/mailman/listinfo/koha --- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://NavalMarineArchive.com> and <http://UltraMarine.ca>

2 1

Error when staging MARC records for import
by Pedro Amorim 01 Nov '15

01 Nov '15

Hello, I have been banging my head with this problem for the past couple of days now and I have no idea what might be causing it. When I upload the .mrc file with the records to import all goes fine but when I press "Stage for import" it stays at 0% for a while, then fills the logs with errors (see below) and after that it goes to "manage staged records" as if everything went fine. It lists how many records were staged and 0 errors found. However, my imported records don't seem right: - The "citation" column is null for every record; - Some MARC fields don't seem to have been imported; I'm not sure if the problem is with the .mrc file or my Koha installation, or both. I've been focusing on the "binmode() on closed filehandle STDOUT" message, changing permissions in files, changing owners, changing the file permission before uploading it, but nothing. Error stack: [Sat Oct 31 13:06:24 2015] [error] [client 10.11.5.52] [Sat Oct 31 13:06:24 2015] stage-marc-import.pl: binmode() on closed filehandle STDOUT at /usr/share/koha/lib/C4/Templates.pm line 122., referer: http://10.13.54.70:8086/cgi-bin/koha/tools/stage-marc-import.pl [Sat Oct 31 13:06:24 2015] [error] [client 10.11.5.52] [Sat Oct 31 13:06:24 2015] stage-marc-import.pl: Filehandle STDOUT reopened as FH only for input at /usr/lib/perl5/Template/Provider.pm line 965., referer: http://10.13.54.70:8086/cgi-bin/koha/tools/stage-marc-import.pl Thanks, Pedro Amorim

2 4

Introduction
by John Sterbenz 01 Nov '15

01 Nov '15

Hi! My name is John Sterbenz and I am exploring joining the Koha community as my library examines its needs in a post-physical collection world. In May of 2013, we had 150,000 physical items across two facilities and six primary collections, with access to around 400,000 electronic titles. By July 2014, we had exactly 215 non-circulating physical items that fit in less than three average-size bookcases,with continued access to the electronic collections. Nearly all of our electronic collection access is provided by aggregators like EBSCO and ProQuest and electronic book packages. There is no more circulation of any sort, no need for patron records (we handle remote authentication via EZ-Proxy), and only a handful (ten) of print serial receipts--all annuals. We ran an Innovative ILS from 1992 until this year. I was hired by my current library back in 1992 to work in it given my background in retrospective conversion cleanup and was named its administrator in 1998. Given our new reality versus what Innovative wanted to continue to charge us for the one product we would actually need, the decision was made by administration to shut down the system and not replace it, causing me, my Technical Services staff, and the other systems librarian here fits. Therein began my examination of open-source solutions, which had actually begun around a year ago when I saw the writing on the wall. Unfortunately, this examination wasn't considered to be a priority by anyone but me, and there were far more pressing issues to handle. After a number of failed attempts since last October, I've gotten Koha 3.20 installed and configured on a Debian jessie VM and will get it to a "proof of concept" stage with our own records for others here to view before making a complete commitment to it. While I haven't made a final decision to make a go of this on my own or call on the expertise of one of the companies that offers support for Koha in various ways, I expect that unless I decide to do the former that I will not get approval to proceed. There are other open-source options for me to consider, of course, but from discussions I've had with others, Evergreen is essentially "too much" for what we need and Kuali, at this point, is a wildcard that requires further examination but also demands much more of my time than I can provide right now even with the promise of its ERM component. While we have lost a lot with the effective shutdown of our old server (especially the loss of ERM functionality), I've been very pleased with my examination of the breadth of features available "out of the box" on Koha, including things that our Innovative implementations never supported. No matter what happens with a public-facing interface, I'm going to use Koha to maintain a "legacy catalog" of what we did once have so that my staff and I can continue to answer questions about a collection we no longer have and exists only through the records and ancillary historic data I've exported from the old Millennium server. I'm sure I'll have questions but I also hope to be able to contribute back to this community in one capacity or another in due time. I look forward to "meeting" and interacting with this group! John -- -=<*>=- -=<*>=- -=<*>=- -=<*>=- -=<*>=- -=<*>=- -=<*>=- -=<*>=- -=<*>=- John E. Sterbenz, Jr. Associate Librarian Manager, Technical Services, Collections, and Library Automation 701 Tappan Street, Rm. K3359 Kresge Business Administration Library The University of Michigan Ann Arbor, Michigan, USA 48109-1234 TEL: (734) 764-5746 FAX: (734) 764-4162

2 1

Koha ILS authorites module missing interface
by schnydszch 01 Nov '15

01 Nov '15

Hi! On a test server Debian and Koha 3.20, in the Edit/Add authorities module, the interface does not show, please see below: <http://koha.1045719.n5.nabble.com/file/n5858824/weird_authorities_interface…> It's just so weird why I'm getting this. I have another test server with same specifications but it's working fine, can somebody lead me to where the weirdness is coming from? :P Thanks and cheers! -- View this message in context: http://koha.1045719.n5.nabble.com/Koha-ILS-authorites-module-missing-interf… Sent from the Koha-general mailing list archive at Nabble.com.

2 1