- Koha - lists.katipo.co.nz

permission problem upon upgrade from 2.2.9 to 3.04
by shahab bohlooli 29 Apr '10

29 Apr '10

Dear all we faced a new problem after upgrading from koha 2.2.9 to 3.0.4 and it is a permission break. whenever we create a new patron for one of our libraries in its default setting, this new account has a full privileges on all staff interfaces. I checked the permissions flags and all were unchecked, but new patron has complete permission. this problem is severely restricting us in using our new and wonderful Koha 3.0.4 system. so I appreciate anyone in the list for any help on this. --------------------- Sincerely Yours Shahab Bohlooli IT devision Ardabil University of Medical Sciences, University Street, 56197, Ardabil, IRAN.

1 0

sounds in koha for holds
by Lola McKee 28 Apr '10

28 Apr '10

Does anyone use sounds in Koha for hold alerts when checking in items if that is even possible? If so what program event is used? We are using Firefox 3.6.3 and I have the add on Navigational Sounds 1.2.1. Any help would be greatly appreciated! -- Thanks, Lola McKee Tech Systems Specialist Salina Public Library 785-825-4624 Ext. 239

2 1

Re: [Koha] Koha Digest, Vol 54, Issue 64
by John 28 Apr '10

28 Apr '10

Hallo Philip, Kein Problem. Machen wir 13:30 Uhr. Vielen Dank. Gruss John -----Ursprüngliche Nachricht----- Von: koha-bounces(a)lists.katipo.co.nz [mailto:koha-bounces@lists.katipo.co.nz] Im Auftrag von koha-request(a)lists.katipo.co.nz Gesendet: Mittwoch, 28. April 2010 14:18 An: koha(a)lists.katipo.co.nz Betreff: Koha Digest, Vol 54, Issue 64 Send Koha mailing list submissions to koha(a)lists.katipo.co.nz To subscribe or unsubscribe via the World Wide Web, visit http://lists.katipo.co.nz/mailman/listinfo/koha or, via email, send a message with subject or body 'help' to koha-request(a)lists.katipo.co.nz You can reach the person managing the list at koha-owner(a)lists.katipo.co.nz When replying, please edit your Subject line so it is more specific than "Re: Contents of Koha digest..." Today's Topics: 1. marc import fails (Joel Cornuz) 2. Fwd: Printing Patron Cards with Names (Chris Cormack) 3. Re: Koha Open Day (savitra sirohi) 4. Re: Fwd: Printing Patron Cards with Names (Scott Daniels) 5. Help Getting Overdue Notices to Print (Richard Forristall) 6. Re: Help Getting Overdue Notices to Print (savitra sirohi) 7. Re: Help Getting Overdue Notices to Print (Susan Bennett) ---------------------------------------------------------------------- Message: 1 Date: Tue, 27 Apr 2010 21:38:24 -0400 From: Joel Cornuz <jcornuz(a)gmail.com> Subject: [Koha] marc import fails To: koha(a)lists.katipo.co.nz Message-ID: <t2idb56d2681004271838zf153587crc1d64298c44207b4(a)mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1" Hello. I contacted you a few months ago regarding a Koha installation I did for a small school. Everything is going well, we are now in production with only a few minor hicups. Great stuff, thanks for Koha - it is a great tool and it helps this little institution a lot. There is however one thing our librarian would like to be able to do: import files from Bookwhere (his favorite Z39.50 client) with new notices. I managed to import a Bookwhere-generated file via bulkmarcimport.pl but the web interface wouldn't work: I can load my file, find my records under "manage staged Marc import" but the "import into catalog" step always results in 0 records added - the records aren't in the database and the "Bib" cell stays empty. I don't get anything in the koha_error_log - I googled around, checked the bugzilla but nothing conclusive. Anyone has an idea what is going on - or where to start looking? Thanks a lot. By the way I am using koha 3.00.04_fixed. Best regards, Joel

1 0

Re: [Koha] Fwd: Printing Patron Cards with Names
by Marty 28 Apr '10

28 Apr '10

As I understand it, some people are still working on the label tool, for now it leaves something to be desired. On the other hand, I think we do not need absolutely everything in one program, as there are other programs well capable of taking over some functions. If you are running on Linux (which I think you do, cause you have Koha 3) take a look at kbarcode (kbarcode.net) It is (obviously) designed for kde, but it works great on my gnome desktop. Once you have installed it, make sure you can connect to your koha database. Then you can just enter queries, like SELECT branchcode FROM borrowers WHERE borrowernumber = ##; SELECT firstname, surname FROM borrowers WHERE borrowernumber = ##; SELECT borrowernumber FROM borrowers WHERE borrowernumber = ##; Where the ## means a number. If you want to do a range (like existing patrons) you can use something similar to the following we use for printing barcodes for existing items in our library, taking data from an extra table in our dbase called interim which exists of id, barcode, usually filled with a LOAD DATA INFILE statement from a .cvs file. [sqlquery: SELECT barcode FROM interim WHERE id = '[index]' + 1;] Hope this helps, Marty --- On Wed, 4/28/10, Chris Cormack <chris(a)bigballofwax.co.nz> wrote: From: Chris Cormack <chris(a)bigballofwax.co.nz> Subject: [Koha] Fwd: Printing Patron Cards with Names To: "koha-user" <koha(a)lists.katipo.co.nz> Received: Wednesday, April 28, 2010, 12:06 AM Forwarding to the mailing list ---------- Forwarded message ---------- From: John <john.winter(a)neverseen.ch> Date: 28 April 2010 06:49 Subject: Printing Patron Cards with Names To: koha-owner(a)lists.katipo.co.nz Hello, I try to print patron Cards with koha3.00.06 Label creator Tool. I searched how to print the cards with the name of the patron on it. But I did not find the function to do it. I searched the internet and wiki. But couldn’t find any hint to do this. Is there a possibility to do that or where can I configure it? I am new to Koha. Perhaps I did not see the function? The Format of the Card should be like this: |-------------------------------------------------------------------- | | Libraryname | | Firstname + Surname of Patron | | | | Barcode | | | |-------------------------------------------------------------------- | Thanks a lot for your help. Greetings John _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha

1 0

Re: [Koha] bulk patron import - specifying borrowernumber?
by jason sherman 28 Apr '10

28 Apr '10

I forgot to cc the list... On Wed, Apr 28, 2010 at 10:13 AM, jason sherman <jsherman(a)usao.edu> wrote: > Jane, > > Thanks for the fast response! I understand that the borrowernumber is > the unique id as opposed to the cardumber which is the patron's > barcode. I was hoping to simply carry over the known unique ids from > the old system to Koha, because it would allow me to migrate patron > data and checkout data in one fell swoop, without having to ask koha > for the id of each patron as I'm importing checkouts. > > On Wed, Apr 28, 2010 at 9:45 AM, Jane Wagner <jwagner(a)ptfs.com> wrote: >> borrowernumber is the internal database unique identifier and it is >> sequential. I think you probably want to migrate your current numbers >> into the cardnumber field. That's the patron barcode. >> >> Jane Wagner >> Library Systems Analyst >> PTFS Inc. >> Content Management and Library Solutions >> 6400 Goldsboro Road, Suite 200 >> Bethesda, MD 20817 >> (301) 654-8088 x 151 >> jwagner(a)ptfs.com >> >> >> -----Original Message----- >> From: koha-bounces(a)lists.katipo.co.nz >> [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of jason sherman >> Sent: Wednesday, April 28, 2010 9:41 AM >> To: koha(a)lists.katipo.co.nz >> Subject: [Koha] bulk patron import - specifying borrowernumber? >> >> Hi all, >> >> I am in the process of preparing our library for migration to Koha >> 3.00.04.019. After examining the patron import starter file from my >> test server as well as the issues database table, I thought it made >> sense to specify the borrowernumber based on values in our old system >> to make moving current borrower checkouts easier. The problem is that >> even though I specify borrowernumbers in the patron import file, Koha >> keeps using auto_increment for the value. I've been fussing around >> with various settings in Koha to try to get it to take my values, but >> I can't get it it to do so. If this isn't going to happen without >> hacking koha's scripts or db config, I can write my checkouts >> migration script to find each user's Koha borrowernumber by checking >> their cardnumber, but I thought I would do a sanity check first. >> >> So, my questions are: >> Is there a setting that I'm missing or something that I've misconfigured? >> Is this a bug in my version of Koha, either by including fields that I >> can't use in the patron import starter file, or by not accepting data >> that it should? >> Or is this just intended behavior that I should expect? >> >> Thanks in advance for any advice you can share, >> >> -- >> Jason Sherman >> Systems Librarian >> University of Science and Arts of Oklahoma >> 405.574.1340 >> _______________________________________________ >> Koha mailing list >> Koha(a)lists.katipo.co.nz >> http://lists.katipo.co.nz/mailman/listinfo/koha >> > > > > -- > Jason Sherman > Systems Librarian > University of Science and Arts of Oklahoma > 405.574.1340 > -- Jason Sherman

1 0

bulk patron import - specifying borrowernumber?
by jason sherman 28 Apr '10

28 Apr '10

Hi all, I am in the process of preparing our library for migration to Koha 3.00.04.019. After examining the patron import starter file from my test server as well as the issues database table, I thought it made sense to specify the borrowernumber based on values in our old system to make moving current borrower checkouts easier. The problem is that even though I specify borrowernumbers in the patron import file, Koha keeps using auto_increment for the value. I've been fussing around with various settings in Koha to try to get it to take my values, but I can't get it it to do so. If this isn't going to happen without hacking koha's scripts or db config, I can write my checkouts migration script to find each user's Koha borrowernumber by checking their cardnumber, but I thought I would do a sanity check first. So, my questions are: Is there a setting that I'm missing or something that I've misconfigured? Is this a bug in my version of Koha, either by including fields that I can't use in the patron import starter file, or by not accepting data that it should? Or is this just intended behavior that I should expect? Thanks in advance for any advice you can share, -- Jason Sherman Systems Librarian University of Science and Arts of Oklahoma 405.574.1340

2 1

koha duplicate zebra indexes problem
by Linda Culberson 28 Apr '10

28 Apr '10

I am getting duplicate results in my searches, and tried to use the instructions at http://koha-community.org/documentation/faq/searching/ but I am still getting duplicate results. So you don't have to look up the link, the instructions on the FAQ are to: zebraidx -c /path/to/zebra-biblios.cfg drop biblios Then zebraidx -c /path/to/zebra-biblios.cfg commit Then rebuild_zebra.pl -b -r -v I did get the following warnings: 17:30:51-21/04 zebraidx(8231) [warn] zebra_lock_create fail fname=__ZEBRA_LOCK_DIR__/biblios/norm..LCK [No such file or directory] 17:30:51-21/04 zebraidx(8231) [warn] zebra_lock_create fail fname=__ZEBRA_LOCK_DIR__/biblios/shadow..LCK [No such file or directory] 17:30:51-21/04 zebraidx(8231) [log] zebra_stop: 0.00 0.00 0.01 We are on version 3.00.05.003 PERL version 5.008008 and Zebra 2.0.43 (C) Thanks in advance Linda Culberson lculber(a)mdah.state.ms.us Archives and Records Services Division Ms. Dept. of Archives & History P. O. Box 571 Jackson, MS 39205-0571 Telephone: 601/576-6873 Facsimile: 601/576-6824

5 5

Koha Open Day
by Andrea Chandler 28 Apr '10

28 Apr '10

3 2

Re: [Koha] PTFS Koha Community Support and the Koha.org Website
by Christopher Nighswonger 27 Apr '10

27 Apr '10

Hi John, It is good to hear from you. > As you know, PTFS acquired LibLime and is integrating the LibLime operation into our existing open source software business unit. With this acquisition, PTFS inherited quite a few tasks, all to be performed simultaneously, and our work is not near complete. However, we want to increase our involvement within the community now, at this early phase of the transition. > We all appreciate the incredibly complex task of merging two companies. No doubt this task is greatly complicated by PTFS being fairly new to the FOSS concept as well. > As promised, PTFS will continue to support the Koha open source community. We understand that the http://koha-community.org/ website was set up as a temporary measure before our purchase of LibLime, out of concerns that the content of koha.org was out of date and was not under the control of official members of the community. To resolve this issue PTFS would like help in updating and supporting koha.org. The time for updating and supporting koha.org as an independent site is past. There is nothing else to be said in that regard. One of the very issues that PTFS appears to be concerned about is at stake here: instability in governance. Make no mistake. There is no instability here. To move "back" to koha.org would indeed be a sign of instability and indecision on the community's part. We have learned a hard and sorrowful lesson in the trust betrayed by LibLime and its former management. Surely you understand the need of ensuring that never again can a single for-profit interest threaten the existence of Koha. The clearest and best indication that PTFS is willing and desirous to participate in the Koha community on the common ground of the term set forth by the community would be to turn all Koha related assets over to the community appointed trustee HLT. You would be surprised what a grateful response this would receive from the community *as well as* many of the former LibLime customers. > PTFS looks forward to continuing our work with the community to mutually advance the goal of producing the world’s best open source ILS system that can truly go head-to-head with the legacy proprietary systems. PTFS has a wonderful opportunity at this point in its own history and that of Koha. Furthermore, PTFS stands a good chance of wide acceptance in the Koha community if it chooses to enter the community on the terms common to all who come this way: those set forth by the community. To my knowledge, no one has shunned, belittled, ostracized, or otherwise discriminated (to use a currently politically hot term) against either of the two PTFS developers who regularly frequent the list and irc channel. To the contrary, many of us have invested our *valuable* time FREE OF CHARGE to assist them in issue directly related to PTFS client work. To this degree and further, PTFS has received invaluable benefit from this community. In return we are only asking that PTFS be honorable and transparent in its dealings with the community. Let's leave the smoke and mirrors to the politicians. I am personally looking forward to greater involvement of PTFS in the Koha community. I have enjoyed interaction with the two PTFS employees who are currently involved and appreciate their valuable contributions to the community as well. Kind Regards, Chris Nighswonger Koha 3.2 Release Maintainer

7 7

Working of koha zebra search.
by arun j 27 Apr '10

27 Apr '10

Hello, Koha Newbie here, can somebody plz explain, how the search works in koha using zebra? *ie after typing the keyword in the OPAC how the stuff i koha database is sent to zebra and searched..* thanks a lot..

1 0