March 2009 - Koha-devel - lists.koha-community.org

bugs.koha.org upgrade 3/18/2009
by Galen Charlton 19 Mar '09

19 Mar '09

Hi, LibLime is moving the Koha bugs database to a new server tomorrow. In the process, we'll be upgrading the software to Bugzilla version 3. In order to copy the database and give time for a DNS change to propagate, we'll be freezing the bugs database between 18:00 and 20:00 UTC-4 (22:00 and 24:00 UTC) tomorrow. Thanks to Clay Fouts for performing the upgrade. Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 skype: gmcharlt

1 1

Fwd: Koha 3 vmware appliance download error
by Kyle Hall 18 Mar '09

18 Mar '09

I received this email, I'm not sure who is handling contribs.koha.org right now. Hi Kyle, I'm sorry to take a little bit of your time but i'm trying to download your vmware appliance of Koha 3 at this location : http://contribs.koha.org/revision_view.php?rid=14 And i'v got a 403 http error code. Do you know if i can download it from another location ? Thx in advance and sorry to disturb you, Laurent PERRIER http://www.kylehall.info Information Technology Crawford County Federated Library System ( http://www.ccfls.org ) ---------- Forwarded message ---------- From: <laurent.perrier(a)nimes.fr> Date: Wed, Mar 18, 2009 at 6:22 AM Subject: Koha 3 vmware appliance download error To: kyle.m.hall(a)gmail.com Hi Kyle, I'm sorry to take a little bit of your time but i'm trying to download your vmware appliance of Koha 3 at this location : http://contribs.koha.org/revision_view.php?rid=14 And i'v got a 403 http error code. Do you know if i can download it from another location ? Thx in advance and sorry to disturb you, Laurent PERRIER _______________________________________________ Koha-devel mailing list Koha-devel(a)nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel

2 2

Koha database installation
by Edisnel Carrazana Castro 18 Mar '09

18 Mar '09

Greetings, I have the fallowing question: How can I to install Koha (the aplication) in one server, with the database in other server. It is possible to do that?

4 3

LDAP replication without update
by Dobrica Pavlinusic 16 Mar '09

16 Mar '09

Let me quickly explain our situation: we want to get data from ldap for new users, but allow librarians to edit data in Koha, and preserve this changes. Logical solution would be to turn replication on, and update off in /etc/koha/koha-conf.xml with something like this: <replicate>1</replicate>  <update>0</update>  but that doesn't work. I tracked problem to || 1 in Auth_with_ldap.pm which always turn both options on no matter what user specifies in xml file. Attached patch fixes this problem. We also needed to augment data available in LDAP with data from CSV files generated by other systems, so I wrote ldap rewriter documented in following blog post: http://blog.rot13.org/2009/03/virtual_ldap_rewrite_or_augment_data_on_the_f… It's somewhat specific for our needs, but I hope that it will also be useful to other as food for thought if nothing else. -- Dobrica Pavlinusic 2share!2flame dpavlin(a)rot13.org Unix addict. Internet consultant. http://www.rot13.org/~dpavlin

2 1

Re: [Koha-devel] Bug#389876: ITP: koha -- web-based library catalogue (ILS/OPAC)
by Vincent Danjean 16 Mar '09

16 Mar '09

MJ Ray wrote: > "Trent W. Buck" <trentbuck(a)gmail.com> wrote: [...] >> Firstly, what is the status of the ITP? Chris (part of the upstream >> Koha team) told me in #koha that in Lenny the dependencies are all >> resolved, so I guess that all that remains is to package Koha itself. > > I've asked Chris Cormack about that on #koha just now. I thought > we're still two short: Class::Adapter and SMS::Send. It will be easy to put them in lenny-backport if needed. >> How far along are you with that? > > There's the collab-maint tree that you're probably aware of. > I'm currently testing a clean install at a client site. > > The thorny problems are the ones where the koha installation usually > "interferes" with mysqld and wider system settings. > >> I looked briefly at upstream yesterday, and it seems to me that at a >> minimum you will want a -common package (due to the large amount of >> architecture-independent data files) and as there are apparently 50MB >> of translation files, possible also seperate koha-language-<ISO 639> >> packages. > > Yes, I'd agree with that split as a minimum. I'm open to suggestions > about whether we want libkoha-perl and koha packages split or not. collab-maint tree is a work-in-progress I did and that I never had time to complete. It already splits koha into several packages more or less automatically (ie manual debian/rules target to (re-)create all language packages in debian/control, ...) For now, the koha is split in: Package: koha-config: koha-config provides several files and scripts used by the other koha package to handle its configuration. This package will be automatically pulled when needed. [see below for more information] Package: koha-common: This package include base-files of koha. Unless you have very specific needs, you would like to install koha-zebra or koha-nozebra that provides a default configuration. Package: koha-nozebra Koha-nozebra is dedicated to small libraries who need who do not need the power of the IDZebra search engine. Package: koha-zebra Koha with zebra Package: koha-zebra-pazpar2 Koha with zebra and pazpar2 (not ready at all since pazpar2 is not yet packaged) Package: koha-zebra-server This package configures an instance of IDZebra to be used with Koha. Package: koha-pazpar2-server This package configures an instance of PazPar2 to be used with Koha. Package: koha This metapackage install the full-featured koha system (koha-zebra) and all Koha localisation packages. Package: koha-l10n-XX This package contains the localization of Koha in XXXXXXX Idea: * koha-config and koha-common are helper packages (not really useful on their own) * koha-nozebra, koha-zebra, and koha-zebra-pazpar2 are mostly empty packages that only depends on koha-common and koha-config and provide a good default configuration. * koha-zebra-server and koha-pazpar2-server can be installed on other host than the koha web-application (so koha-zebra recommends koha-zebra-server but does not depend on it) Managing mysqld settings is not really a problem: dbconfig-common is here to help. But I hit several problems: - the perl parser must be selected system-wide. I already wrote on the Koha ML to ask them to manually select the parser directly in the Koha code. I do not know if all required modification have been done - several configuration files (in particular /etc/koha/koha.conf) are used by different programs that will be in different packages. I need to know a precise description of all settings (in particular all settings in /etc/koha/koha.conf) and I need to know which programs use each of them => note to koha developers: it would be easier if different programs have different configuration files - koha comes with a lot of scripts/utilities in /usr/share/koha/bin I need a description of their goal and of their use (how and when should we use them) I will try to setup a wiki page with all these questions. When they will be answered, it will be possible to finish the Debian Koha packaging. And any help is welcome of course. Regards, Vincent -- Vincent Danjean GPG key ID 0x9D025E87 vdanjean(a)debian.org GPG key fingerprint: FC95 08A6 854D DB48 4B9A 8A94 0BF7 7867 9D02 5E87 Unofficial pacakges: http://www-id.imag.fr/~danjean/deb.html#package APT repo: deb http://perso.debian.org/~vdanjean/debian unstable main

2 1

Possible bad patch to stable
by Joe Atzberger 16 Mar '09

16 Mar '09

A user ("imp") on IRC reported being unable to add patrons to a new installation of 3.00.01.005 because of the error "This patron does not exist." Of course that doesn't make any sense when one is trying to add a new patron. Their logs also showed: [Sun Mar 15 18:20:19 2009] [error] [client 172.16.1.164] [Sun Mar 15 18:20:19 2009] memberentry.pl: Use of uninitialized value in string eq at /mnt2/koha-install/intranet/cgi-bin/members/memberentry.pl line 139., referer: http://10.23.42.14:8080/cgi-bin/koha/members/memberentry.pl?op=add&cate… [Sun Mar 15 18:20:19 2009] [error] [client 172.16.1.164] [Sun Mar 15 18:20:19 2009] memberentry.pl: DBD::mysql::st execute failed: Column 'surname' cannot be null at /mnt2/koha-install/lib/C4/Members.pm line 768., referer: http://10.23.42.14:8080/cgi-bin/koha/members/memberentry.pl?op=add&cate… I have some problems with this patch introduced 8 days ago: http://git.koha.org/cgi-bin/gitweb.cgi?p=Koha;a=commit;h=239700d079ca6c33d3… Maybe it is unrelated, but that patch includes unnecessary changes to memberentry.pl (all whitespace... on a stable release?) and an apparently unconditional warn statement in Members.pm. I suggest it should be reverted and the addition of new patrons retested via STAFF interface. The symptoms as reported would seem to affect all users trying to add patrons w/ the current stable codebase. --Joe

3 2

Need to Modify Marc Import Tool
by savitra sirohi 16 Mar '09

16 Mar '09

Folks, One of our customers wants the ability to import Follett marc records without having to use Marc Edit (to change fields 852 to 952). We want to make this change generic such that it will work for any import file that has holdings in fields other than 952. This is what we were thinking, will appreciate feedback on this design: 1. Use marc_subfield_structure table to store field structure of the import file. So Follett would have records under its framework code. We could create frameworks for other vendors too. 2. Accept framework code as user input from stage-marc-import.pl. User could choose nothing which means input file already has holdings in 952. Or could choose Follett or some other vendor. 3. Pass framework code as parameter to BatchStageMarcRecords (C4/ImportBatch.pm) and from there to AddItemsToImportBiblio (C4/ImportBatch.pm). 4. In AddItemsToImportBiblio - Use the input framework code in GetMarcFromKohaField (C4/Biblio.pm) to fetch Follett holdings fields and subfields - Fetch default fields and subfields (952) using null framework code, as is currently done. - For each subfield set values appropriately (in the case of Follett 952s = 852s) before saving item record. 5. Initially the code will help with holdings tags, and later we could extend this to biblio tags as well. Thanks, Savitra Sirohi Nucsoft OSS Labs http://www.osslabs.biz

7 9

Add Biblio slow
by zang＠zang.co.za 13 Mar '09

13 Mar '09

We are using Koha on a hosted server, so it is accessed via the internet (broadband). Everything works fine, but in some cases the "Add Biblio" page takes about 5 min to load. Is there perhaps a way to speed it up? Maybe by removing the unused marc input fields?

2 1

Koha, Drupal and SOPAC
by paul POULAIN 12 Mar '09

12 Mar '09

Hello, I'm very pleased to announce that BibLibre has started working on a SOPAC connector for Koha. SOPAC is a module of drupal, written to have a perfectly integrated web2.0 catalogue over the CMS drupal. You can find information here : http://www.thesocialopac.net/ It's a new Biblibrian that works on that : jean-andré Santoni. He's still a student, working on this subject for 2 months. Hopefully, once he has finished his school, he will be hired by BibLibre. He will implement many new webservices, that will follow the DLF Discovery Interface scheme (http://diglib.org/architectures/ilsdi/) He started last week, and the 1st days are very encouraging. We will let you know once it can be opened. As usual, it will be GPL-ed, even if we still haven't decided how to distribute the code (use koha, sopac or BibLibre tools & repositories ?) happy day. -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

3 2

Change get_saved_reports order to alphabetical?
by Wagner, Jane 12 Mar '09

12 Mar '09

In C4::Reports::Guided (Guided.pm), the subroutine get_saved_reports() is sorting the saved reports list by date created. Would there be any interest in changing this to alphabetical by report name instead? That seems to be more functional. Is there some background or reason for the date sort? 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

3 3