- Koha - lists.katipo.co.nz

Database size
by Paul Yachnes 24 Jul '08

24 Jul '08

Can anyone give me ballpark averages for database size, such as so many bibliographic records per megabyte/gigabyte, and so many patrons records per megabyte/gigabyte? Paul

1 0

Merge Bib Records
by David Schuster 24 Jul '08

24 Jul '08

Is there a way to easily merge bib records if for some reason 2 records accidentally are loaded into the system. What are the steps. Thanks! Sorry for all the questions but am looking at several of my process steps and what may need to be changed moving to Koha. David Schuster -- View this message in context: http://www.nabble.com/Merge-Bib-Records-tp18611514p18611514.html Sent from the Koha - Discuss mailing list archive at Nabble.com.

2 1

Re: [Koha] Koha 2.29, HTTP 500 internal server error with Amazon AWS
by Magnus Enger 24 Jul '08

24 Jul '08

Hi! Looks like you need to provide Koha with two pieces of information in the preferences: AmazonAssocTag and AWSAccessKeyID (Access Key ID - if you do not provide this you will not be getiting the Amazon Reviews). See http://aws.amazon.com/ for info on how to get these. Regards, Magnus Enger collib.info ----- Original Message ----- From: "Charles N Burns" <charlesnburns(a)gmail.com> To: koha(a)lists.katipo.co.nz Sent: Tue, 22 Jul 2008 22:33:21 -0600 Subject: [Koha] Koha 2.29, HTTP 500 internal server error with Amazon AWS > Hello all, > > Please cc this email to my email address as I am not subscribed to the > list. I would subscribe, but I am setting up Koha for a friend's > community elementary school's library, but have no library of my own. > :) > > Problem is: > When I enable AWS (Amazon Web Services) with "AmazonContent = 1", any > attempt to view a book from search is met with the familiar: > > "Internal Server Error > > The server encountered an internal error or misconfiguration and was > unable to complete your request." > (etc.) > > An example of a URL that crashes Koha is this: > http://KOHA_SERVER/cgi-bin/koha/opac-detail.pl?bib=5338 > > (So the problem seems to be in opac-detail.pl) > > ---------- > > When I execute opac-detail.pl directly in the command line: > > # export PERL5LIB=/usr/local/koha/intranet/modules > # /usr/local/koha/opac/cgi-bin/opac-detail.pl > > I get: > > could not retrieve > http://xml.amazon.com/onca/xml3?t=&dev-t=(My_amazon_qws_id)&type=heavy&f=xm… > AsinSearch= > at /usr/local/koha/intranet/modules/C4/Amazon.pm line 64. > Could not find opac-detail.xml in /usr/local/koha/opac/cgi-bin/ at > /usr/local/koha/intranet/modules/C4/Amazon.pm line 66 > > ---------- > > No log files mention anything special other than the access log, which > is pretty worthless: > > # cat opac-access_log > (...) > 10.0.0.196 - - [22/Jul/2008:22:22:25 -0600] "GET > /cgi-bin/koha/opac-detail.pl?bib=5338 HTTP/1.1" 500 663 > > ---------- > > The setup: > Ubuntu Hardy 8.04 with most recent updates > Koha 2.2.9 > Apache ID string: "Apache/2.2.8 (Ubuntu) PHP/5.2.4-2ubuntu5.2 with > Suhosin-Patch Server at 10.0.0.161 Port 80" > Perl v5.8.8 > > ---------- > > So it looks like either Amazon isn't providing some XML file, or the > request generated by Koha is not correct. > Either way, I think it's extremely bad that the results of a request > to an external website (Amazon.com) had the effect of basically > "crashing" Koha. I think Koha really ought to handle this, though I > don't actually know if it's something Koha can prevent. > > > So the question is: > How do I get AWS to work with Koha? > > Best regards, > > Charles Burns > > -- > "Be who you are and say what you feel, because those who mind don't > matter and those who matter don't mind." --Dr. Seuss > _______________________________________________ > Koha mailing list > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha

3 2

Error 109
by Henry Lam 24 Jul '08

24 Jul '08

Dear all We have just installed the Koha 3. My technical support told me when he enable the Zebra plugin, there was an error message: "Search biblios ERROR 109". Because of this, we are unable to do any search. Can anyone englight us what does this mean? Regards Henry

2 1

Test Post, gmane dropping posts
by Darrell Ulm 24 Jul '08

24 Jul '08

This is a test post. Gmane seems to be dropping my posts. -D.Ulm

1 0

Re: [Koha] Purpose of this list? - Adding more lists?
by Zeno Tajoli 24 Jul '08

24 Jul '08

Hi to all, At 15.14 21/07/2008, Joshua Ferraro wrote: >I don't think we've necessarily had a problem of the developer's list >not moderating, >more that there was some concern that the Koha User's list has a mix >of both Usage and >'How do I Install Koha' type questions that get pretty technical. The >fear I've heard expressed >is that librarians who would normally feel comfortable posting >questions about Usage >are scarred off by all of the system-level technical talk relating to >'how do I install Koha'. I >can't verify this personally ... I've never had anyone tell me that >specifically, but it does have >the ring of truth :-) > >So I see two options: > >1. create another list (we have far more than two already folks) >specifically for Usage, or specifically for 'How do I Install Koha' >2. do a better job of moderating the Koha user's list (this one) to >help it focus on less technical, more Usage questions. > >I personally favor #2. in fact on Koha User's list [this list] there is a a mixì of both Usage and 'How do I Install Koha' type questions that get pretty technical. But I think that we NEED to teach to the librarian that install Koha is (now) a quite technical and complex question. In fact, now, without a Win32 auto-install, Koha 3.0 is not for librarian without Linux tecnical skills. So, my opinion is to mantain only two main mailing lists, Koha User's list and Koha Dev. With also specific mailing list (transaltion, language specific, etc.) Cheers Zeno Tajoli Zeno Tajoli CILEA - Segrate (MI) tajoliAT_SPAM_no_prendiATcilea.it (Indirizzo mascherato anti-spam; sostituisci quanto tra AT con @)

1 0

ImageMagick
by Marcel de Rooy 24 Jul '08

24 Jul '08

Upgrading to 3RC1 indeed solved the problem below. While doing that, I had a problem installing a newer version of ImageMagick (and PerlMagick). Koha needs 6.2. Installation of version 6.4.2 (from source) [on FC6] did not work: dl'open errors on libMagick.so and libgomp.so. Experimenting with options as -disable-openmp and --enable-shared=yes etc. did not make a difference. After uninstalling it *completely*, installing version 6.2.3.6 from source went fine right away. Of course, this is just a Koha-related problem. But could be of interest for others installing Koha ... Marcel de Rooy ________________________________ Van: koha-bounces(a)lists.katipo.co.nz [mailto:koha-bounces@lists.katipo.co.nz] Namens Ryan Higgins Verzonden: donderdag 17 juli 2008 19:38 Aan: koha(a)lists.katipo.co.nz CC: Marcel de Rooy Onderwerp: Re: [Koha] Bug? Yes, this was a known bug involving the system preference 'BiblioAddsAuthorities' and is fixed in RC1 . Ryan On Thu, Jul 17, 2008 at 8:41 AM, Frederic Demians <frederic(a)tamil.fr<mailto:frederic@tamil.fr>> wrote: > When modifying and saving a biblio record, MARC fields with a popup > get overwritten with the value of only one letter or digit. (These > include 100, 110, 111, 130 / 440 / 600 610 630 648 650 651 654 655 662 > 690 / 700 710 711.) The previous value is lost. Try upgrading to version 3RC1. I get the same error in the past during a while and solve it that way. -- Frédéric _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz<mailto:Koha@lists.katipo.co.nz> http://lists.katipo.co.nz/mailman/listinfo/koha -- Ryan Higgins LibLime * Open-Source Solutions for Libraries Featuring KohaZOOM ILS 888-564-2457 x704

1 0

Itemtype not displaying in OPAC correctly
by Heather Braum 24 Jul '08

24 Jul '08

I am working with a standalone system that was just installed, version 2.2. In the cataloging module through the staff client the item type (y field) displays correctly as what is set when the item is added. But in the OPAC, the item type displays as what is defaulted in the 942 field of the MARC record (currently audio cassette). If we edit the 942 field and set it as the proper item type, it displays correctly in the OPAC. How do we change the 942 default? Or is it a bug/issue with our install? et me know if you need more information. Sorry if I'm wording this confusingly. I'm new to Koha :) Thanks for the help in advance, Heather Braum Northeast Kansas Library System

2 1

Re: [Koha] Koha 2.29, HTTP 500 internal server error with Amazon AWS
by Charles N Burns 24 Jul '08

24 Jul '08

Thank you. Now all I need help with is figuring out how on earth I completely missed the "AmazonAssocTag" field when it's right there under the OPAC tab. On Wed, Jul 23, 2008 at 4:07 PM, Magnus Enger <magnus(a)enger.priv.no> wrote: > Hi! > > Looks like you need to provide Koha with two pieces of information in the > preferences: AmazonAssocTag and AWSAccessKeyID (Access Key ID - if you do > not > provide this you will not be getiting the Amazon Reviews). See > http://aws.amazon.com/ for info on how to get these. > > Regards, > Magnus Enger > collib.info > > ----- Original Message ----- > From: "Charles N Burns" <charlesnburns(a)gmail.com> > To: koha(a)lists.katipo.co.nz > Sent: Tue, 22 Jul 2008 22:33:21 -0600 > Subject: [Koha] Koha 2.29, HTTP 500 internal server error with Amazon AWS > > > Hello all, > > > > Please cc this email to my email address as I am not subscribed to the > > list. I would subscribe, but I am setting up Koha for a friend's > > community elementary school's library, but have no library of my own. > > :) > > > > Problem is: > > When I enable AWS (Amazon Web Services) with "AmazonContent = 1", any > > attempt to view a book from search is met with the familiar: > > > > "Internal Server Error > > > > The server encountered an internal error or misconfiguration and was > > unable to complete your request." > > (etc.) > > > > An example of a URL that crashes Koha is this: > > http://KOHA_SERVER/cgi-bin/koha/opac-detail.pl?bib=5338 > > > > (So the problem seems to be in opac-detail.pl) > > > > ---------- > > > > When I execute opac-detail.pl directly in the command line: > > > > # export PERL5LIB=/usr/local/koha/intranet/modules > > # /usr/local/koha/opac/cgi-bin/opac-detail.pl > > > > I get: > > > > could not retrieve > > > > http://xml.amazon.com/onca/xml3?t=&dev-t=(My_amazon_qws_id)&type=heavy&f=xm…<http://xml.amazon.com/onca/xml3?t=&dev-t=%28My_amazon_qws_id%29&type=heavy&…> > > > AsinSearch= > > at /usr/local/koha/intranet/modules/C4/Amazon.pm line 64. > > Could not find opac-detail.xml in /usr/local/koha/opac/cgi-bin/ at > > /usr/local/koha/intranet/modules/C4/Amazon.pm line 66 > > > > ---------- > > > > No log files mention anything special other than the access log, which > > is pretty worthless: > > > > # cat opac-access_log > > (...) > > 10.0.0.196 - - [22/Jul/2008:22:22:25 -0600] "GET > > /cgi-bin/koha/opac-detail.pl?bib=5338 HTTP/1.1" 500 663 > > > > ---------- > > > > The setup: > > Ubuntu Hardy 8.04 with most recent updates > > Koha 2.2.9 > > Apache ID string: "Apache/2.2.8 (Ubuntu) PHP/5.2.4-2ubuntu5.2 with > > Suhosin-Patch Server at 10.0.0.161 Port 80" > > Perl v5.8.8 > > > > ---------- > > > > So it looks like either Amazon isn't providing some XML file, or the > > request generated by Koha is not correct. > > Either way, I think it's extremely bad that the results of a request > > to an external website (Amazon.com) had the effect of basically > > "crashing" Koha. I think Koha really ought to handle this, though I > > don't actually know if it's something Koha can prevent. > > > > > > So the question is: > > How do I get AWS to work with Koha? > > > > Best regards, > > > > Charles Burns > > > > -- > > "Be who you are and say what you feel, because those who mind don't > > matter and those who matter don't mind." --Dr. Seuss > > _______________________________________________ > > Koha mailing list > > Koha(a)lists.katipo.co.nz > > http://lists.katipo.co.nz/mailman/listinfo/koha -- "Be who you are and say what you feel, because those who mind don't matter and those who matter don't mind." --Dr. Seuss

1 0

Koha 2 to Koha 3 upgrade scripts/process, experiences
by Darrell Ulm 23 Jul '08

23 Jul '08

Hi All, I was fooling around with the Koha version 2.2 to 3.0 upgrade scripts on the new Koha 3 release, as somewhat of a hobby, and I was wondering if any of you had any success with the scripts. So far I have made partial success. The end result works, except when accessing screens with biblio details, I get the following error: The following fatal error has occurred: Can't call method "field" on an undefined value at /root/kohaclone/C4/Biblio.pm line 968. Apache Server version: Apache/2.2.3 Server built: Jan 27 2008 18:13:21 Koha 3.00.00.101 Koha DB 3.0000101 MySQL mysql Ver 14.12 Distrib 5.0.32, for pc-linux-gnu (i486) using readline 5.2 OS Linux koha 2.6.18-6-686 #1 SMP Fri Jun 6 22:22:11 UTC 2008 i686 GNU/Linux Perl 5.008008 This looks like a trace back to something that happened because of missing field data. If I use bulkmarcimport to load the bib, everything searches fine and there are no errors, but of course, the bib records are not lined up. Since this has been my latest hobby, has anyone else been playing with the 22_to_30 upgrade? Any luck? :) Thanks! Darrell Ulm

1 0