- Koha - lists.katipo.co.nz

Monthly ILL report
by Scott Zollars 18 Aug '09

18 Aug '09

Thanks to whoever devised the SQL for my report request. I need to tweak it a little though. This is the current SQL Scotty Zollars Circulation List interlibrary loan materials check out to other libraries, by month SELECT monthname(datesent) month,COUNT(*) FROM branchtransfers where frombranch="MMM" and YEAR(datesent)=YEAR(NOW())-1 GROUP BY month ORDER by month(datesent) We are just one branch . We treat our ILL customers like community patrons and that is our patron type for them. We put ILL as the surname for all of our ILL patrons, for example, Surname: ILL, First Name: Erie Public Library. How should I adapt this to take this into account and to also show the titles. Sorry to be a pain, Scotty Zollars Director of Library Services Labette Community College 200 S. 14th Parsons, KS 67357 620-820-1168 620-421-1469 FAX Four things you can't recover: The stone after the throw, the word after it's said, the occasion after it's missed and the time after it's gone.

1 0

Problems with rebuild_zebra.pl -z
by Stefano Bargioni 18 Aug '09

18 Aug '09

Hi, in my Koha 3.00.3 (a new Debian-Lenny testing installation), everytime I modify or delete a record, the zebraqueue table registers the changes with the "done" field=1. The update of Zebra will be unuseful, since rebuild_zebra.pl -z can't select records. Is there something wrong in my Zebra config? Or this is a bug? Thanks. Stefano

2 2

Re: [Koha] MySQL Problem
by Erik Lewis 18 Aug '09

18 Aug '09

Okay I'm officially spooked. It's back after restarting mysql again but this is worrisome. On Aug 18, 2009, at 9:15 AM, Erik Lewis wrote: > Okay, plowing around with the MySql gui. Getting a bunch of > "incorrect information in file" on every file > > > On Aug 18, 2009, at 9:05 AM, Erik Lewis wrote: > >> Did the latest updates to my Ubuntu 9.04 machine and restarted. >> >> Went to my Koha Opac and got the maintenance page >> >> That was odd so I checked and MySQL wasn't running. >> >> Went to start it manually >> >> sudo mysql start >> >> and got this: >> >> ERROR 2002 (HY000): Can't connect to local MySQL server through >> socket >> '/var/run/mysqld/mysqld.sock' (2) >> >> hmmm... >> Thought about it for a moment and decided that maybe I should try >> mysqld >> >> That worked but I got this >> >> 090818 8:41:40 [ERROR] mysqld: Incorrect information in file: './ >> koha/ >> systempreferences.frm' >> >> Now, here are the last things I did that would have effected mysql. >> >> Yesterday I was playing with adding Owen's tables for the new items >> php. I have also been playing with the CSS for the Opac, header, >> credits, navigation, etc.. as I work on trying to merge the library >> webpage with the Opac. >> >> Any thoughts? Do I just need to restore my koha database? >> >> _______________________________________________ >> Koha mailing list >> Koha(a)lists.katipo.co.nz >> http://lists.katipo.co.nz/mailman/listinfo/koha

1 0

Re: [Koha] MySQL Problem
by MJ Ray 18 Aug '09

18 Aug '09

Erik Lewis <elewis(a)ngrl.org> [...] > sudo mysql start > and got this: > ERROR 2002 (HY000): Can't connect to local MySQL server through socket > '/var/run/mysqld/mysqld.sock' (2) > > hmmm... > Thought about it for a moment and decided that maybe I should try mysqld > > That worked but [...] Any thoughts? I think running mysqld directly won't start the server with the same parameters as the script /etc/init.d/mysqld does, so it might not find your databases and settings. Try using the init script and if it fails to start with some error message, check the /var/log files for a fuller description of the problem. This is more of a general sysadmin or ubuntu question than a Koha problem, so you might find a local sysadmin or LUG who could explain it more fully. Hope that helps, -- MJ Ray (slef) LMS developer and webmaster at | software www.software.coop http://mjr.towers.org.uk | .... co IMO only: see http://mjr.towers.org.uk/email.html | .... op

1 0

MySQL Problem
by Erik Lewis 18 Aug '09

18 Aug '09

Did the latest updates to my Ubuntu 9.04 machine and restarted. Went to my Koha Opac and got the maintenance page That was odd so I checked and MySQL wasn't running. Went to start it manually sudo mysql start and got this: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) hmmm... Thought about it for a moment and decided that maybe I should try mysqld That worked but I got this 090818 8:41:40 [ERROR] mysqld: Incorrect information in file: './koha/ systempreferences.frm' Now, here are the last things I did that would have effected mysql. Yesterday I was playing with adding Owen's tables for the new items php. I have also been playing with the CSS for the Opac, header, credits, navigation, etc.. as I work on trying to merge the library webpage with the Opac. Any thoughts? Do I just need to restore my koha database?

1 0

Invalid Login on SIP2 Server... why?
by Luigi Ipsa 18 Aug '09

18 Aug '09

Hi, now i have corrected start SIP2Server but when i try to login, server reply me invalid login: telnet localhost 8023 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. login: sipterm1 password: term1 Invalid login login: password: Invalid login login: password: Invalid login Login OK. Initiating SIP 9300CNsipterm1|COterm1|CPMAIN 940 Connection closed by foreign host. but my SIPServer.xml is the same to this on: https://sites.google.com/a/liblime.com/koha-manual/Home/Table-of-Contents/A… https://sites.google.com/a/liblime.com/koha-manual/Home/Table-of-Contents/A… What is the possible problem? Thanks -- View this message in context: http://www.nabble.com/Invalid-Login-on-SIP2-Server...-why--tp21951242p21951… Sent from the Koha - Discuss mailing list archive at Nabble.com.

6 9

110 (corporate author) doesn't show on OPAC normal view
by PasiK 17 Aug '09

17 Aug '09

How can I make the field 110a show as author in OPAC "normal view" in Koha3? -- View this message in context: http://www.nabble.com/110-%28corporate-author%29-doesn%27t-show-on-OPAC-nor… Sent from the Koha - Discuss mailing list archive at Nabble.com.

1 0

Re: [Koha] Apache bandwidth tuning in default config
by MJ Ray 17 Aug '09

17 Aug '09

"Pablo A. Bianchi" <pbianchi(a)fi.uba.ar> > The purpose also was to know if someone think there is not a good idea > to made those changes, because is strange that being so simple nobody > say something about before. > Furthermore, this simples changes seems to be a very interesting > improve with an small effort, I was surprise no one responds (perhaps > it was a good reason). I didn't see it until now because it was sent to the wrong list (should have gone to koha-devel) and two copies soon together may have been misdetected as bulk mail. deflate - I think enabling this would mean that we end support for Apache 1.3. Is that OK? expires - I think this may mess up pre-production testing. PageSpeed - mentioned but I don't know where to get the mentioned files from. I think we should put deflate and expires into the default config file, but commented out with notes that the deflate is only for Apache httpd 2.x and that expires should only be enabled once you're finished messing with CSS and images. Does that sound right? -- MJ Ray (slef) LMS developer and webmaster at | software www.software.coop http://mjr.towers.org.uk | .... co IMO only: see http://mjr.towers.org.uk/email.html | .... op

3 2

Mahalya Havard est absente.
by Mahalya_Havard＠ssss.gouv.qc.ca 17 Aug '09

17 Aug '09

Je serai absent(e) du Lun 17-08-2009 au Mar 18-08-2009. Je répondrai à votre message dès mon retour, mercredi, le 19 août 2009. Merci.

1 0

Another 229 to 30 migration, again - items... a new twist?
by Andrew Séguin 17 Aug '09

17 Aug '09

I'm trying to do the migration from Koha 229 to Koha 30, and haven't yet experienced full success. First, upgrading in place didn't work out so well for some reason - I had copied the virtual machine's disk, so was able to revert quickly. After looking through the mailing lis, I then tried just running a Koha 30 system; imported the database of the 229 system and ran the upgrade scripts... this also didn't work out so well, "lazy me" just moved on once again. Finally, I took a koha 30 prebuilt virtual machine (time constraints, surely not because I'm a "lazy" system admin, right?) and imported the bibliographic entries. Through the web interface, it worked so-so, rejecting some "slices" (read: independent files with 1000 exported records from the 229 system) of the exported data... tried the bulkimport.pl script which rejected certain records as bad marc ... which I took (combined with some combing of the mail-group archives) as the reason behind the failure of the web interface. In the end, imported by the web interface or bulkimport.pl, I would end up with some biblios with the items all proper, some with the items not showing up properly (without call number). The Koha 30 system I'm using is the pre-built virtualbox machine 3.0 release -- version "Koha 3.0001005". Before running bulkimport, I recreated the same item-types and branches. Both systems are set to MARC21. I'm turning to the community here for some advice how to proceed / what to consider (I'm not afraid of research, scripting, or SQL... but a bit lost at the moment): * My first question would be, is there any trick, quick way, of knowing which biblios were rejected by bulkimport.pl ? I tried with "-v", "-v 2" without success to get more details. (sample/full command: nohup /home/koha/kohaclone/misc/migration_tools/bulkmarcimport.pl -d -v 2 -file ~/Koha20090811_02.mrc -commit 1 | tee ~/bulkimport_KOP20090811_2.log after having set PERL5LIB and KOHA_CONF) * My second question, is - are there any pointers/ideas concerning the import of items? Items that I consider properly imported have the call number displayed; where not, the call number is missing. In either case at least the barcode is correctly imported. Maybe somebody has a quick moment to look at the difference between the two and sees something obvious I don't? * Imported correctly: http://161.53.212.104/cgi-bin/koha/opac-detail.pl?biblionumber=820 * Not imported correctly: http://161.53.212.104/cgi-bin/koha/opac-detail.pl?biblionumber=9880 (was biblio 11874) I just (while writing this mail) found a difference looking at the records from Koha 229 and Koha 30: bibid 820 had under Koha 229 the "call number prefix" set to the same value as "call number" where 9880 doesn't. Maybe somebody has a comment about this (did I ignore something basic with the frameworks)? - I'll test the call number / call number prefix issue (either with marc-edit or directly in 229's database, for each item, copying the call-number to the call-number-prefix subfield value ...) within a day or two... Many thanks for all those in general who take the time work on Koha, even more to those who patiently read this entire email! Andrew

1 1