- Koha - lists.katipo.co.nz

A useful script to compress patron images to upload
by Vimal Kumar V. 02 Sep '13

02 Sep '13

Dear Friends, Here is a python script, which is very helpful to compress bulk patron images without any hassle. Details of bulk patron image option is available in Koha documentation. http://manual.koha-community.org/3.12/en/tools.html#uploadpatronimages In academic libraries, every year hundreds of photos arrive from office to library to upload in Koha. Using this script, you can compress images in batch mode and create id link for entire images. This script created by Mr. A.J. Tomson, Librarian, Devagiri College, Kozhikode. He had implemented Koha in 2000 itself. He is an active resource person of Koha in Kerala state. Recently he completed 100 Koha training programmes as resource person. How to use the script? Arrange your photos in a folder. Ensure that photo name must be card number of patrons. Goto the following link and click on Download button. http://kohageek.pbworks.com/w/file/68630026/idlink.py Put idlink.py script in photo folder. Open a terminal and enter inside photo folder and apply following commands, chmod -R 777 idlink.py ./idlink.py After the process, you can see zip file, where all your photos compressed. Goto Koha > Tools > Upload Patron Images Upload the zip file. I once again express my thanks to Mr. A.J. Tomson on behalf of Koha community. -- Vimal Kumar V. Technical Assistant Mahatma Gandhi University Library Kottayam, Kerala- 686 560 Web: http://www.vimalkumar.info Blog: http://linuxhalwa.blogspot.com http://kohageek.blogspot.in --------------------------------------------------------------------------- "I forget what I was taught. I only remember what I have learnt" -Patrick White

2 1

Zebra Indexing Issue ( Records does not appear in the catalog)
by Sarwar421 02 Sep '13

02 Sep '13

Dear All, I am facing an issue in koha. I have successfully imported the marc records in koha . But when i try to search them it wont appear in the result . But i can see these records in reservoir. My zebra file is running properly (I have checked it using this command 'ps -ef | grep zebrasrv' ). When it try to run this command for indexing 'perl/home/koha/kohaclone/misc/migration_tools/*rebuild_zebra.pl –a –b –z' * it just take few seconds to execute ( only 33 records were imported) but no output comes in return. But when i change parameters as * 'rebuild_zebra.pl -b -r -v' * it gives me the following output. Zebra configuration information ================================ Zebra biblio directory = /var/lib/koha/zebradb/biblios Zebra authorities directory = /var/lib/koha/zebradb/authorities Koha directory = /usr/share/koha/intranet/cgi-bin BIBLIONUMBER in : 999$c BIBLIOITEMNUMBER in : 999$d ================================ skipping authorities ==================== exporting biblio ==================== 1................................ Records exported: 33 ==================== REINDEXING zebra ==================== ==================== CLEANING ==================== It seems like the script performs the indexing but i don't know why i am still not be able to see my records .. Any help on this would be appreciate able.As i am stuck in this and could not find any proper solution. Regards Sarwar -- View this message in context: http://koha.1045719.n5.nabble.com/Zebra-Indexing-Issue-Records-does-not-app… Sent from the Koha-general mailing list archive at Nabble.com.

1 0

Import MARC record error: utf8 "\xE0"
by Pongtawat Chippimolchai 02 Sep '13

02 Sep '13

Hello all, I got the following error while importing MARC records into Koha 3.12.3 (on Ubuntu 12.04 amd64 via Debian package): utf8 "\xE0" does not map to Unicode at /usr/lib/perl/5.14/Encode.pm line 174. The record staged fine but it couldn't be imported. When clicking to view it in staging area, the same error appear. I checked the imported file, and it seem to look fine to me. The MARCXML in the database look ok too. But if I save the MARC BLOB and use marcdump on it, I got the same error. The imported file is here: https://www.dropbox.com/s/u25mf4dqk69wtgx/error.mrc The saved MARC BLOB is here: https://www.dropbox.com/s/soawpzmnuy5j7zr/import_records-marc.bin Running perl -d commit_file.pl show something like this: ------------- utf8 "\xE0" does not map to Unicode at /usr/lib/perl/5.14/Encode.pm line 174. at /usr/lib/perl/5.14/Encode.pm line 174 Encode::decode('UTF-8', 'ha\x{1e}0 \x{1f}a\x{e0}\x{b9}\x{84}\x{e0}\x{b8}\x{9e}\x{e0}\x{b8}\x{a8}\x{e0}\x{b8}\x{b2}\x{e0}\x{b8}\x{a5} \x{e0}\x{b8}\x{81}\x{e0}\x{b8}\x{a4}\x{e0}\x{b8}\x{a9}\x{e0}\x{b8}\x{8e}\x{e0}\x{b8}\x{b2}\x{e0}\x{b8}\x{98}\x{e0}\x{b8}\x{b4}\x{e0}\x{b8}\x{a7}\x{e0}\x{b8}\x{b8}\x{e0}\x{b8}\x{92}\x{e0}\x{b8}', 1) called at /usr/share/perl5/MARC/File/Encode.pm line 35 MARC::File::Encode::marc_to_utf8('ha\x{1e}0 \x{1f}a\x{e0}\x{b9}\x{84}\x{e0}\x{b8}\x{9e}\x{e0}\x{b8}\x{a8}\x{e0}\x{b8}\x{b2}\x{e0}\x{b8}\x{a5} \x{e0}\x{b8}\x{81}\x{e0}\x{b8}\x{a4}\x{e0}\x{b8}\x{a9}\x{e0}\x{b8}\x{8e}\x{e0}\x{b8}\x{b2}\x{e0}\x{b8}\x{98}\x{e0}\x{b8}\x{b4}\x{e0}\x{b8}\x{a7}\x{e0}\x{b8}\x{b8}\x{e0}\x{b8}\x{92}\x{e0}\x{b8}') called at /usr/share/perl5/MARC/File/USMARC.pm line 172 MARC::File::USMARC::decode('00932nas0a220021700045000050017000000080043000170200014000600...') called at /usr/share/perl5/MARC/Record.pm line 81 MARC::Record::new_from_usmarc('MARC::Record', '00932nas0a220021700045000050017000000080043000170200014000600...') called at /usr/share/koha/lib/C4/ImportBatch.pm line 585 C4::ImportBatch::BatchCommitRecords(13, '', 100, 'CODE(0x5227d58)') called at /usr/share/koha/bin/commit_file.pl line 85 main::process_batch(13) called at /usr/share/koha/bin/commit_file.plline 57 ------------- I really don't get the way Perl (and Koha) handle UTF8 at all. If I print that escaped string out, some character will be readable but the others appear as ?. For the records that could be imported, if I print out their data from Perl I see the same pattern (readable char mixed with ?). But they somehow end up correct in the database. I have no idea what's wrong here. If you have any clue, please help. Thank you very much, Pongtawat

3 2

Re: [Koha] RDA framework
by Chris Meech 02 Sep '13

02 Sep '13

Thanks David and Chris, The RDA framework has saved me a lot of time. I've adjusted the xslt stylesheet for OPAC details to display publisher information from the 264 What I would like to do is use the RDA framework as a default framework as this would save us identifying RDA records on Z39.50 import and having to select the RDA framework. Is anyone using an RDA framework as default? Cheers Chris Christopher Meech Reference and Heritage Librarian Waitaki District Libraries P.O. Box 134,Oamaru 9444 62 Thames St, Oamaru 9400 03 433 0850 cmeech(a)waitaki.govt.nz www.library.waitaki.govt.nz -----Original Message----- From: David Cook [mailto:dcook@prosentient.com.au] Sent: Friday, 30 August 2013 1:25 p.m. To: koha(a)lists.katipo.co.nz Cc: Chris Meech; chris(a)bigballofwax.co.nz Subject: RE: RDA framework Hi Chris and Chris: I've actually added another RDA framework on the wiki (superseding the last two which were still missing some RDA fields, I believe). It uses the latest "marc21_framework_DEFAULT.sql" (which should be current up to Update No. 16 (April 2013), plus some slight modifications by an actual cataloguing library (More info the changes to MARC with each update available here: http://www.loc.gov/marc/status.html) Special thanks to the amazing efforts of Bernardo Gonzalez Kriegel, Mason James, Marcel de Rooy, et al. for putting that framework together! The framework might still need some alterations, but it should include all the fields and subfields available. David Cook Systems Librarian (BA,FRLS,MLIS) Prosentient Systems P/L ABN 31 078 409 168 72/330 Wattle St, Ultimo NSW 2007 tel: 02 92120899 fax: 02 92120885 dcook(a)prosentient.com.au -----Original Message----- Date: Thu, 29 Aug 2013 13:26:29 +1200 From: Chris Meech <cmeech(a)waitaki.govt.nz> To: "koha(a)lists.katipo.co.nz" <koha(a)lists.katipo.co.nz> Subject: [Koha] RDA framework Message-ID: <988CFBF8CA18774A819D6157BACB27F90736585546(a)WDCEX1.waitakidc.govt.nz> Content-Type: text/plain; charset="us-ascii" Hi, The Koha RDA framework here http://wiki.koha-community.org/wiki/MARC_frameworks#RDA_Framework seems to be lacking a 264 field. Has anyone got an RDA framework that includes 264? Cheers Chris Christopher Meech Reference and Heritage Librarian Waitaki District Libraries P.O. Box 134,Oamaru 9444 62 Thames St, Oamaru 9400 03 433 0850 cmeech(a)waitaki.govt.nz<mailto:cmeech@waitaki.govt.nz> www.library.waitaki.govt.nz ------------------------------ Message: 2 Date: Thu, 29 Aug 2013 13:55:37 +1200 From: Chris Cormack <chris(a)bigballofwax.co.nz> To: Chris Meech <cmeech(a)waitaki.govt.nz> Cc: "koha(a)lists.katipo.co.nz" <koha(a)lists.katipo.co.nz> Subject: Re: [Koha] RDA framework Message-ID: <CA+95qVTrb+gjKPHEh_=gkFGs4xwS6jbHh9en6MiYAwSNxZGjhQ(a)mail.gmail.com> Content-Type: text/plain; charset=UTF-8 On 29 August 2013 13:26, Chris Meech <cmeech(a)waitaki.govt.nz> wrote: > Hi, > The Koha RDA framework here > http://wiki.koha-community.org/wiki/MARC_frameworks#RDA_Framework > seems to be lacking a 264 field. > > Has anyone got an RDA framework that includes 264? > We could have pretty fast, If you grab that, import it, add the 264, export the framework and add it to the wiki :) Chris

1 0

Thank you - Circulation Rules Help needed - 1) Hard Time Proposal - 2) Query on Overnight/Weekend Loans
by Matthew Charlesworth, S.J. 01 Sep '13

01 Sep '13

Dear all, I used to use an earlier version of Koha in 2007/8 but then moved out of library work (though I worked with Chrispin Sitali in Zambia who sometimes posts here (wave)), and have always remained a fan of Koha - but recently after moving to Nairobi, I had the opportunity to install a Koha installation using the more updated version (what a lot of work has gone on behind the scenes in the interim! Well done). In the last month or two we transitioned approx. 90,000 records from InMagic and, beginning this academic year (August), have started using Koha as our main OPAC and staff client. So far, we are getting very positive results - thank you for creating such a wonderful product. I have two questions though and I don't know if I'm just not seeing it or if I must submit a bug or feature request? I thought I'd ask here before I do - perhaps someone could let me know how best to proceed. I am using Koha 3.12.03.000 on Ubuntu 12.04.3 LTS (for some reason I can't get apt-get update|upgrade to see the new 3.12.04 version - but perhaps it's because I'm in Kenya and it'll take a while to filter to whatever repositories are mirrored here). We have circulation rules that allow for students to keep books for 2 weeks and staff for a month. The email they receive correctly acknowledges check-out and check-ins with a date/time stamp, but always puts the time to 23:59. I do not want to have the Circulation Librarian manually enter the date and time (by sliding those indicators) depending on the patron; I would prefer for the system to automatically calculate, as it does, whether the check-out is for 2 or 4 weeks. But if our library closes at 17h30 I don't want the due-time to be at 23h59. Is there a way - or could there be a way created - to set a closing time for the library, so that hourly loans (for our Reserve Section) can still be calculated, but if it falls past closing-time, e.g. 17h30 (for instance 23h59 or 22h00) it is reduced to 17h30 (so the students don't tell our library staff that they came at midnight but no-one was around)? I hope you understand what I'm trying to say. Another way of wording it might be to think about it in terms of the current 'Hard Date' in the Circulation and Fine Rules section in Administration in the Staff client. There is an option in the rules for a 'Hard Date' - but I would like to propose a 'Hard Time', i.e. whatever day is arrived at by the rules - the latest possible time would be the 'Hard Time'. This would work for us as we have two branches, one whose books must be returned by 17h30 of that day, and another whose books must be returned by 11h00. If there was a hard-time preference in the circulation rule it would be possible to specify it on a branch-by-branch basis. My second question is not so much a feature request (or if it's already there, a plea to have it pointed out to me) as it is to ask for some guidance from someone who has more experience in setting the circulation rules. Our library has a reserve section. Currently we allow books to be borrowed for a short-term period - a few hours during the day, the book not to be removed from the library (but we want the book checked-out and checked-in from the Reserve section so we can track usage and which students are actually accessing the material); But the reserved books may leave the library if it is borrowed between 17h00-17h30 - then it may be kept overnight, to be returned by 08h30. Currently I'm setting the rules up so that books from the Reserve section (an itemtype) have a 16 hour loan period so that if it's loaned at 17h00 the system calculates that it must be due back by 08h00 (though they receive an email saying it's due back 16 hours later - which ideally I'd like it to be 3 or 4 hours). But I need it so that if it's loaned on Friday it will be due on Monday 08h00. If I set holiday dates in the Calendar of the Library - it will ignore weekends - but that means for our 'normal loans (as explained in the previous problem) the 14 or 28 day rules (which used to include weekends) becomes more of an 18 or 32 day rule - but if that's the only way to get the Reserve Section check-outs working, then I will request our Librarian to change the rules to exclude weekends from all circulation check-in calculations... (I have individual rules for each branch, itemptype, and patron category - with the only 'All' rule being for the Reserve section.) Another idea I had was that fines would not accrue for Reserved books until 3 days - (i.e. Sat 08h30-Sun-08h30-Mon-08h30) - but that means a book could be taken out on Monday and the patron only show up in our morning emailed fine report on Wed, which given that we only have 1 copy of every book, would badly inconvenience our students. I think the 'Hard Time' feature could be extended to have an option that if it falls on 'end of week' then it is due 'beginning of following week' might solve it - but I don't know if that would be of interest to the wider community - or perhaps there is a way of solving this already which I haven't seen.... I'm happy to be lectured to :) as I learn more and more about Koha :) I hope that makes some sense and once again want to thank you. With my best wishes, Matthew

1 0

Re: [Koha] Import MARC record error: utf8 "\xE0"
by Paul 01 Sep '13

01 Sep '13

At 01:17 PM 8/31/2013 +0700, Pongtawat Chippimolchai wrote: >Hello all, > >I got the following error while importing MARC records into Koha 3.12.3 (on >Ubuntu 12.04 amd64 via Debian package): > >utf8 "\xE0" does not map to Unicode at /usr/lib/perl/5.14/Encode.pm line >174. > >The record staged fine but it couldn't be imported. When clicking to view >it in staging area, the same error appear. Perhaps a "long shot", but I remember having a similar problem which turned out to be (not Unicode) but simply including hyphens in ISBN numbers -- you have put an apparent ISSN with hyphen into 020$a, and my verification script shows: "020 - Invalid data found: 8057-7730. Only [^(97(8|9))?\d{9}(\d|X)$] is valid within this field." (I realize that MARC purists will object that more - e.g. "(pbk)" - can be added, but bulk imports seem to be touchy on this subject, so I added the "$" at the end of the regex.) Best - Paul >I checked the imported file, and it seem to look fine to me. The MARCXML in >the database look ok too. But if I save the MARC BLOB and use marcdump on >it, I got the same error. > >The imported file is here: >https://www.dropbox.com/s/u25mf4dqk69wtgx/error.mrc >The saved MARC BLOB is here: >https://www.dropbox.com/s/soawpzmnuy5j7zr/import_records-marc.bin > >Running perl -d commit_file.pl show something like this: > >------------- >utf8 "\xE0" does not map to Unicode at /usr/lib/perl/5.14/Encode.pm line >174. > at /usr/lib/perl/5.14/Encode.pm line 174 > Encode::decode('UTF-8', 'ha\x{1e}0 >\x{1f}a\x{e0}\x{b9}\x{84}\x{e0}\x{b8}\x{9e}\x{e0}\x{b8}\x{a8}\x{e0}\x{b8}\x{b2}\x{e0}\x{b8}\x{a5} >\x{e0}\x{b8}\x{81}\x{e0}\x{b8}\x{a4}\x{e0}\x{b8}\x{a9}\x{e0}\x{b8}\x{8e}\x{e0}\x{b8}\x{b2}\x{e0}\x{b8}\x{98}\x{e0}\x{b8}\x{b4}\x{e0}\x{b8}\x{a7}\x{e0}\x{b8}\x{b8}\x{e0}\x{b8}\x{92}\x{e0}\x{b8}', >1) called at /usr/share/perl5/MARC/File/Encode.pm line 35 > MARC::File::Encode::marc_to_utf8('ha\x{1e}0 >\x{1f}a\x{e0}\x{b9}\x{84}\x{e0}\x{b8}\x{9e}\x{e0}\x{b8}\x{a8}\x{e0}\x{b8}\x{b2}\x{e0}\x{b8}\x{a5} >\x{e0}\x{b8}\x{81}\x{e0}\x{b8}\x{a4}\x{e0}\x{b8}\x{a9}\x{e0}\x{b8}\x{8e}\x{e0}\x{b8}\x{b2}\x{e0}\x{b8}\x{98}\x{e0}\x{b8}\x{b4}\x{e0}\x{b8}\x{a7}\x{e0}\x{b8}\x{b8}\x{e0}\x{b8}\x{92}\x{e0}\x{b8}') >called at /usr/share/perl5/MARC/File/USMARC.pm line 172 > > >MARC::File::USMARC::decode('00932nas0a220021700045000050017000000080043000170200014000600...') >called at /usr/share/perl5/MARC/Record.pm line 81 > MARC::Record::new_from_usmarc('MARC::Record', >'00932nas0a220021700045000050017000000080043000170200014000600...') called >at /usr/share/koha/lib/C4/ImportBatch.pm line 585 > C4::ImportBatch::BatchCommitRecords(13, '', 100, 'CODE(0x5227d58)') >called at /usr/share/koha/bin/commit_file.pl line 85 > main::process_batch(13) called at > /usr/share/koha/bin/commit_file.plline 57 >------------- > >I really don't get the way Perl (and Koha) handle UTF8 at all. If I print >that escaped string out, some character will be readable but the others >appear as ?. For the records that could be imported, if I print out their >data from Perl I see the same pattern (readable char mixed with ?). But >they somehow end up correct in the database. > >I have no idea what's wrong here. If you have any clue, please help. > >Thank you very much, >Pongtawat >_______________________________________________ >Koha mailing list http://koha-community.org >Koha(a)lists.katipo.co.nz >http://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>

1 0

"Exported Selected Items'' || no selection option in SERIAL> CLAIMS l<'Late Selections list
by HRS 01 Sep '13

01 Sep '13

Checkboxes are missing in Serial > Claims > 'Late Selections list'' . So I cannot do "Exported selected items"" in my installations(v 3.12.0 and 3.12.3) In Koha Demo, I have observed same But Manual shows there are check box to do the section I am new to KOHA and we, Open university, Sri Lanka testing the system feasibility this is a drawback to us as we have ample amount to Serials Please help me ,Thanks in advance Harsha Balasooriya Senior Assistant Librarian, System Main Library The Open University of Sri Lanka

1 0

Fwd: Help In Koa Report
by Rachel Hamilton-Williams 31 Aug '13

31 Aug '13

-------- Original Message -------- Subject: Help In Koa Report Date: Fri, 30 Aug 2013 12:38:41 +0530 From: Raja Manikyam <raja.manikyam20(a)gmail.com> To: koha-owner(a)lists.katipo.co.nz Hi All, Need some help koha report. we want to Generate report containing below details Barcode Title author edition year publisher subject call number Location Collection code please help me to generate this report copyrightdate Thanks in advance *Raja Manikyam.A* ***/Go Greeen, Save Earth./* **

1 0

Seeking new community newsletter editor
by Daniel Grobani 31 Aug '13

31 Aug '13

Hi, A combination of changing work duties and our library preparing to migrate away from Koha has made it increasingly challenging for me to dedicate time to editing the newsletter. So, after tipping my hand in the July newsletter, I'm now formally and sadly announcing my resignation as community newsletter editor effective December 31, or sooner if a new editor steps forth and takes over before then. Preparing the newsletter requires about 4-8 hours a month. I've found it to be an excellent way to stay informed about the community and to make great connections with Koha folks. I'd be happy to share my list of RSS feeds and other news sources with the next editor, as well as to work with that person during a transition period. Please email me if you might be interested in taking on this role. Many thanks, Daniel Grobani

1 0

August 2013 Koha Community Newsletter has been published
by Daniel Grobani 31 Aug '13

31 Aug '13

Hi, The August 2013 edition of the Koha Community Newsletter has been posted to http://koha-community.org/koha-community-newsletter-august-2013/. Cheers, Daniel Grobani Koha Community Newsletter Editor

1 0