- Koha - lists.katipo.co.nz

fatal error
by bariki.kamara＠out.ac.tz 19 May '10

19 May '10

Hi, Am trying to add some data into Koha ILS but I end up with the following error below; The following fatal error has occurred: Can't call method "append_fields" on an undefined value at /usr/local/share/perl/5.10.0/MARC/File/SAX.pm line 92. what might be a problem, please I need some help on this. Regards, Bariki G. Kamara ---------------------- CONFIDENTIALITY NOTICE -------------------------------- PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS E-MAIL This email is intended only for the person to whom it is addressed and may contain confidential information and may be legally privileged. If you are not the intended recipient, you are notified that you may not use, distribute or copy this document in any manner whatsoever. Kindly also notify the sender by email and/or delete this e-mail. Any views or opinions expressed in this e-mail are those of the sender and do not necessarily coincide with those of the Open University of Tanzania. --------------------THE OPEN UNIVERSITY OF TANZANIA--------------------------

1 0

Koha virtualhost on apache2 (openSUSE 11.2) Issue
by Andi Sugandi 19 May '10

19 May '10

Hi Listmates. Let me introduce my self, my name is Andi Sugandi. I work at a university and also help some friends in Asian-African Conference Museum[0] in Bandung (Indonesia). As this e-mail's signature, I'm also helping (local) openSUSE community in my country. I successfully installed Koha[1] (last Saturday) on openSUSE 11.2, feels wonderful of the how-to[2], may be i could help on this wiki so it keeps up-to-date. My issue ATM is I can not access my phpMyAdmin page anymore[3]. I usually access it by typing 'localhost/phpMyAdmin' on the address-bar of the web-browser. It probably not a Koha issue, but my apache2 configuration which I'm (relatively) new in this area. This is my .../.../vhosts.d/koha-httpd.conf file (I temporary disabled OPAC session in this file): -----------------BOL Listen 8080 ## Intranet <VirtualHost *:8080> ServerAdmin webmaster@oS-kmkaa DocumentRoot /usr/share/koha/intranet/htdocs ServerName oS-kmkaa:8080 # ServerAlias intranet.mydomain.com ScriptAlias /cgi-bin/koha/ "/usr/share/koha/intranet/cgi-bin/" ScriptAlias /index.html "/usr/share/koha/intranet/cgi-bin/mainpage.pl" ScriptAlias /search "/usr/share/koha/intranet/cgi-bin/search.pl" ErrorLog /var/log/koha/koha-error_log # TransferLog /var/log/koha/koha-access_log SetEnv KOHA_CONF "/etc/koha/koha-conf.xml" SetEnv PERL5LIB "/usr/share/koha/lib" Options +FollowSymLinks ErrorDocument 400 /cgi-bin/koha/errors/400.pl ErrorDocument 401 /cgi-bin/koha/errors/401.pl ErrorDocument 403 /cgi-bin/koha/errors/403.pl ErrorDocument 404 /cgi-bin/koha/errors/404.pl ErrorDocument 500 /cgi-bin/koha/errors/500.pl RewriteEngine On # Uncomment to turn on rewrite logging # RewriteLog /var/log/koha/koha-intranet-rewrite.log # RewriteLogLevel 1 RewriteCond %{QUERY_STRING} (.*?)(?:[A-Za-z0-9_-]+)=&(.*) RewriteRule (.+) $1?%1%2 [N,R,NE] RewriteRule ^/bib/([^\/]*)/?$ /cgi-bin/koha/detail\.pl?bib=$1 [PT] RewriteRule ^/isbn/([^\/]*)/?$ /search?q=isbn:$1 [PT] </VirtualHost> -----------------EOL Is anyone can help this issue? Thanks in advance. [0] http://asianafrican-museum.org/ [1] > grep INSTALLED /usr/share/koha/misc/koha-install-log KOHA_INSTALLED_VERSION=3.00.05.003 [2] http://wiki.koha.org/doku.php?id=opensuse_11.0 [3] http://picasaweb.google.com/andisugandi/FOSSAtAACMuseumBandung#547211326523… Best regards, -- Andi Sugandi, openSUSE-Id Team, openSUSE Ambassador Bandung, Indonesia

2 1

Caroline Loh/lib/staff/npnet is out of the office.
by Caroline Loh 19 May '10

19 May '10

I will be out of the office starting 19/05/2010 and will not return until 20/05/2010. Mrs Lim Ben Wai/Senior Manager (6460 6369) will cover my duties. For matters relating to copyright laws, please refer to Ms Lim Bee Ang/Reference Manager (6460 6551). If you need to reach me, please call my Secretary, Mdm Teo at 6460 6280 . With best regards Caroline Loh (Mrs) | Director | Lien Ying Chow Library Ngee Ann Polytechnic, 535 Clementi Road, Singapore 599489 DID: 6460 6288 | FAX: 6466 8274 | EMAIL: lck4(a)np.edu.sg | http://www.np.edu.sg/library/library.html Our Mission: Advancing People With Information NP Vision: Connecting Minds. Unlocking Talents. Creating Value NOTICE: This message may contain privileged/confidential information. If you are not the intended recipient of this email, please delete it immediately and notify the sender .

1 0

Fwd: Re: Koha-3.0.6 Stable release
by Chris Cormack 17 May '10

17 May '10

Whoops forgot to cc the list -------- Original Message -------- Subject: Re: [Koha] Koha-3.0.6 Stable release From: "Chris Cormack" <chrisc(a)catalyst.net.nz> To: "Andi Sugandi" <andisugandi(a)gmail.com> CC: Hi Andi Do not use the tarball from download.koha.org, it is an old prerelease. The one at download.koha-communtiy.org is the right one. (You'll notice the dates are different too) Official releases are made at download.koha-community.org. Chris "Andi Sugandi" <andisugandi(a)gmail.com> wrote: >On 5/17/10, LAURENT Henri-Damien <henridamien.laurent(a)biblibre.com> wrote: > >> I am happy to announce Koha3.0.6 Stable, which fixes >> bugs from 3.0.5 has been released on http://download.koha-community.org/ >> Its name is koha-3.00.06.tar.gz You can download file and signatures > >Hat offs to Koha developers. > >Btw, I am just curious on the package provided by these different >download pages which each has different size: > >http://download.koha.org/koha-3.00.06.tar.gz 182M > >http://download.koha-community.org/koha-3.00.06.tar.gz 20M > >what is the difference of both packages? > >Thanks in advance. > >Best regards, >-- >Andi Sugandi >_______________________________________________ >Koha mailing list >Koha(a)lists.katipo.co.nz >http://lists.katipo.co.nz/mailman/listinfo/koha -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.

1 0

updatedatabase.pl: DBD::mysql::db do failed
by Vimal Kumar 17 May '10

17 May '10

Dear Friends, I got following message while trying to upgrade Koha 3.00.05 t0 3.00.06. I got this error message in the stage, "Updating database structure", web installer step-3. Update errors : [Mon May 17 23:15:10 2010] updatedatabase.pl: DBD::mysql::db do failed: Duplicate column name 'finedays' at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase30.plline 755. Is it a serious error? -- Vimal Kumar V. Asst. Librarian Asian School of Business Technopark, Trivandrum-695 581 Web: http://www.vimalkumar.co.nr Blog: http://vimalkumar.oksociety.in OK Society Volunteer. http://oksociety.in --------------------------------------------------------------------------- "I forget what I was taught. I only remember what I have learnt" -Patrick White

2 1

Undo Import function
by Stacy Pober 17 May '10

17 May '10

Are there any serious problems in official Koha with the "undo import" (batch revert) function? We're using LLEK and have had no serious problems with the Undo Import function so far. However, someone from PTFS told me that there is a plan to remove that function from LLEK. I'm concerned because our library has put tens of thousands of records into our catalog for e-books that are not really 'owned' by us but rather are on annual subscriptions. Without the "Undo Import" function, it doesn't seem like there would be an easy method of removing these records if (or more likely, when) we cancel any of the subscriptions in the future. We also find that ebook vendors like to change their offerings on a regular basis, and undoing batch imports makes the updates a breeze. Right now, updating the subscription coverage is an easy matter of undoing the import of the current batch and then uploading a new one. I don't know of any alternative method for easily removing batch uploads from the system using the web interface. There is likely some way to do it if you're a programmer running your own system, but we're in a hosted situation. So, I checked Bugzilla and did notice any significant problem reports for the Undo Import (revert batch) function. Is Undo Import working well in official Koha? And are many libraries making use of this function? -- Stacy Pober Information Alchemist Riverdale, NY 10471 stacy.pober(a)manhattan.edu

1 0

Search Results Codes
by Anselm Olweny 17 May '10

17 May '10

Dear Colleagues, I would like to change the codes that are displayed with the search results, eg *“kw,wrdl: health ” *returned 216 results, *“kw,wrdl: health branch: KENLIB” *returned 71 results. I would like to change *kw, wrdl *to something the user understands or something more meaningful. I would like to change *branch: *to Library. Kindly offer any assistance on how I might achieve this. Thanks and stay well Anselm Olweny

1 0

Introduction - Sean McIntyre
by Sean T. McIntyre 17 May '10

17 May '10

Hello Koha Community! I wanted to take a few minutes to introduce myself. My name is Sean McIntyre and I was brought on board PTFS, after they acquired LibLime on March 15th, to manage all of the software development work related to their ILS / Koha business. This is an exciting opportunity for me and I wanted to share a bit of my background with all of you, as I expect to be an active participant in this Open Source Community as it moves forward (if you'll have me). My family and I live in Northern Virginia, outside of Washington D.C. and have been here since 1981; which is a very long time for this area of the United States. After graduating high school I went on to earn a B.S. in Computer Science & Engineering at MIT in Cambridge, Massachusetts. Over the next 20+ years, I held a variety of positions in the D.C. Metropolitan area in government contracting as well as commercial software ventures. My resume includes two start-ups and the last 6 years of my career at AOL; the last 3 of which I ran all the technology on the AOL News site, the 4th largest in the world. My background includes a dozen or more programming languages and consistent use of open source software since the mid-90s. In my role here at LibLime, I am involved in all of our software activities, particularly our large sponsored development projects. It is my intent that my team and I will work effectively with the community, building upon some of the collaboration that pre-dated the acquisition in March. Most of our clients are strong advocates of their sponsored development benefiting the open source community as a whole and we intend to honor our clients desires in this area, even encouraging those who feel less strongly about this. Our client base has grown substantially since the acquisition and we have inherited two very large, demanding software development activities that are on a tight schedule. I mention this, as it has an impact on my resources in the near term. Obviously, we have to place a priority on meeting the needs of our paying clients and their time lines. At no time however would I want that to cast a doubt on our overall goal to work effectively with the community and make contributions. It just may be the case that given our current resourcing and economics that features built for our clients will be available to them first to test and flesh out. This will allow our contributions to be of a higher quality then if we released them immediately and to meet the demanding schedules we have inherited. We are looking at different mechanisms to share with the broad community what we are working on, with the thought of reducing the duplication of effort on significant software enhancements and I'd love to hear your thoughts on how we might do this most effectively. Soon I'll be joining the IRC chat on a regular basis and welcome any and all comments or thoughts. If you perceive my team or I are doing something that is not as beneficial to the community as it could be, please let me know. I'd be happy to talk about it and am optimistic that many of these perceptions are based on mis-understandings that are easily cleared up. Sincerely, Sean McIntyre Engineering Mgr, ILS LibLime, a Division of PTFS

6 10

Koha (was Introduction - Sean McIntyre)
by Christopher Nighswonger 17 May '10

17 May '10

Heya Sean, It's nice to have you on board. We certainly look forward to having you as a regular in the community. As a common point of interest, I moved to the Northern VA area in 1974 and left when I graduated from High School in 1988. I did return to work for VDOT in Fairfax, VA as an HCI for a short stint in 90 and 91. On Fri, May 14, 2010 at 9:30 PM, Sean McIntyre <smcintyre(a)ptfs.com> wrote: <snip> > Your suggestions on language that might have been received better than > what we chose seem quite good to me. It was a bit of a struggle for us > as what we were describing had inherent complexities as noted above. We > felt good about labeling the release 'Harley', as that had no intrinsic > meaning. As you say however, the language we used has caused some > confusion. In fact, our own customers are a bit confused as to which > "flavor" (deliberately trying to use a term that is not overloaded) of > Koha has the most features. For us, there are three choices we can > offer. The community supported 3.2 alpha Koha, 'Harley' or the LibLime > Enterprise Koha; each of which have some unique features that could make > them attractive options. Overtime, we would like these to come together > in some fashion for a whole variety of reasons, not the least of which > is to eliminate potential confusion. > > As we go forward, how would you and others like the Koha 3.2 alpha > software referred to? Does the phrase you have used here, "community > supported Koha" work for the majority? How do other vendors deal with > this terminology challenge? Our preference would be to use terms that > everyone is comfortable with across the board, the greater value here is > in the software not the labels affixed to that software. I think one of the fundamental problems with choosing a "name" is that there has been no vendor within the community to release a flavor of Koha separate from that released by the community elected Release Manager. (Someone step in and correct me if I'm wrong.) Up until a year or so ago, the Koha community worked together as a fairly well oiled machine. There was the broad understanding and general consensus that everyone waited on the Release Manager for the next official Koha release. Now I know that there were some "internal" variations of Koha running around, but the code changes represented by them were by and large already submitted to the RM and simply awaiting integration, testing, and release in the official code base. But I digress... Probably the best route to have taken would have been for LL/PTFS to have simply pushed the Harley code base to their public git repo and simply announced via the mailing lists/websites that they were beginning to maintain an open public git repo and outline the features contained in the Harley code base as an offering for inclusion into the official code base. This is how every other vendor has accomplished this same thing in the past. As it is, there is now the confusion which you mention over which "flavor" should be used by the end user. Very frankly: We have never had that problem prior to the introduction by LL of their three flavors about a year ago. (Now, you at least have the consolation of knowing that this most recent move was not really the origin of this confusion.) So the entire concept of having to choose a "name" now for what has always been the only official Koha release revolves around this matter of now having multiple flavors of Koha. I would kindly suggest that the real and final solution to the entire issue is to be found in your last statement of the first quoted paragraph above: > Overtime, we would like these to come together > in some fashion for a whole variety of reasons, not the least of which > is to eliminate potential confusion. Getting both the Harley and LLEK code bases merged back into the official Koha code base and returning to a single, official release is the best possible solution to all problems, issues, confusions, or <your_favorite_term_goes_here>, etc. So, to answer your naming question: We should continue to refer to the official code base simply as "Koha" because that is what it is. Vendors should simply make their code base available via public git repos and refer to them as such. (I know... everyone has the "right" to "release" their own "version." But strength is had in unity in this case. Diversity of "released versions" will inevitably drain resources from the official code base and the products will be the poorer for it. One such example is given in the next paragraph.) I would trespass a bit further on your good will and say that the fastest way to get both the Harley and LLEK code bases re-integrated into the official code base is to push them both to public repos and allow the team of developers to begin merging immediately. LL/PTFS has done this with the Harley code base. Kudos!!! This is a *very* positive step. Let's bring this along with the publishing of the LLEK code base as well. (A case in point demonstrating the urgency of this need is the fact that one vendor has already begun work on hourly loans. IIRC LLEK already has this feature. So said vendor is wasting both time and money developing a feature which is already in existence. That time and money could be spent developing another new feature which, in turn, LL/PTFS would benefit from at really no development cost to themselves. This is one of the *many* pluses of the FOSS model; no one entity bears the full cost of R&D.) All of this is kindly meant, and I hope has been well said. Kind Regards, Chris Nighswonger Koha 3.2 Release Maintainer

5 5

Retraction - Koha
by Bob Birchall ＠ Calyx 17 May '10

17 May '10

I want to retract part of my previous post. The words in brackets following 'fork' may not be correct, and in any event do not help to resolve the issues. I apologise for clouding the discussion. My concluding remark may also be unhelpful. I do not seek to question any one's motives, but rather to suggest that some further action is necessary, beyond the (acknowledged) positive steps that have recently been taken. Bob Birchall

2 1