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

perl: symbol lookup error:Koha 3
by Partha Mukhopadhyay 01 Aug '08

01 Aug '08

Dear members I'm still in the middle of installation of Koha 3 (RC1) on Fedora 7 and facing the same error reporting. Let me tell you in details - 1. I installed Net::Z3950::ZOOM through CPAN utility. 2. Then after completion of all the required PERL modules, YAZ and Zebra, I started Koha installation by giving command Perl Makefile.PL in the /usr/share/Koha-3-xxx (where I unzipped the Koha RC1) 3. Koha installesr asked me a series of questions and I answered them all (as instructed in Koha on Fedora 7 installation guide packed with RC1, except I selected dom in place of grs1) 3. Koha installer gave me no waring interms of missing PERL and repored -- Checking if your kit is complete...> > Looks good 4. Then in the next line it reported perl: symbol lookup error: > > > /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi/auto/Net/Z3950/ZOOM/ZOOM.so: > > undefined symbol: > > yaz_version 5. It failed to create any Make file and thereby make, make test and make install commands what I issued one after another all failed. 6. Interestingly when I remove Net:Z3950:ZOOM (ver 1.24 instaleld through CPAN) perl module through an utility programme packed with Koha (under misc folder), the Koha installer reported that Net:Z3950:ZOOM module is missing but created make file. And I'm able to run subsequently the make, make test and make install commands. 7. But this created problem during starting of Zebra-daemon (again surprisingly zebrasrv started properly) by reporting the missing Yaz version. 8. I tried to overcome this problem by removing Net:Z3950:ZOOM version 1.24 and installing Net:Z3950:ZOOM ver 1.16 (as koha installer givemn warning that it requires Net:Z3950:ZOOM ver 1.16) but result is the same. 9. In this context I have another question that - are the steps of configuring apache as given in the installion guide on Fedora 7 sufficient. Thanks and regards, Partha Dr. Parthasarathi Mukhopadhyay Department of Library and Information Science University of Burdwan, Burdwan, West Bengal, India = -- _______________________________________________ Search for products and services at: http://search.mail.com

2 1

Re: [Koha-devel] warnings (was: [Koha-patches] [PATCH] kohabug 2345: bad comparisons pervade reports)
by Andrew Moore 01 Aug '08

01 Aug '08

On Thu, Jul 31, 2008 at 8:06 AM, Galen Charlton <galen.charlton(a)liblime.com> wrote: > Now imagine what would happen if we (as we should) turn on warnings in > Koha. I'll make a proper 3.2 RFC for it shortly, but IMO we really > need to start putting in 'use warnings' in a all scripts. Many bugs > have already been fixed that were based on undef scalars that should > have had a value, and many more undoubtedly lurk. Hi Galen - I'm looking forward to that RFC and hearing any resulting discussion. At the risk of opening up the discussion too early, I'll say that I'm glad to hear that I'm not the only one with that opinion on 'use warnings' (and 'use strict'!). -Andy

4 5

Spine Label Wrapping in 2.2.x
by Chris Nighswonger 01 Aug '08

01 Aug '08

Hi all, Can anyone confirm or deny that the labels code in Koha 2.2.x had a decent, working algorithm for wrapping the text on spine labels? A quick look at the code seems to indicate that the text was just wrapped at 14 columns without consideration of where that might fall in the text. Kind Regards, -- Chris Nighswonger LibLime www.liblime.com chris.nighswonger(a)liblime.com

3 2

Database Revision Tracking
by Jesse Weaver 01 Aug '08

01 Aug '08

As part of a process improvement effort we're doing at LibLime, I've created the following wiki proposal: http://wiki.koha.org/doku.php?id=en:development:dbrevs:start Please read it and let me know what you think. This is intended as a simple replacement for IRC conversations like this: < random_dev> I'm pushing a patch with database version 105. Anybody else using that?

6 6

RFC 3.2 - put item hold request flag in circulation policy matrix
by Galen Charlton 01 Aug '08

01 Aug '08

At present, if a patron is allowed to place hold requests, they can request any item that is not on loan or doesn't have the binding, lost, or notforloan statuses set. However, some LibLime customers to need more precisely control which items are available for hold requests. For example, a library may want to permit loans for certain item types but not hold requests. To meet this requirement, LibLime proposes to add a "holdability" flag to the circulation matrix (i.e., issuingrules). This would allow a library to specify for each branch which patron categories are allowed to place holds on which item types. This holdability flag would be the hold request equivalent of the recall flag proposed in the recalls RFC. Adding this setting will influence: * what item records are available to fill a title-level hold request * what items a patron is allowed to place an item-level hold request for During database upgrade, the holdability flag would be turned on for all existing issuingrules rows, thus preserving the current behavior of allowing all available items to be the target of hold requests. A copy of this RFC is available on the Koha wiki at http://wiki.koha.org/doku.php?id=en:development:rfcs3.2:rfc32_holdability_f… Thanks in advance for comments. Regards, Galen -- Galen Charlton Koha Application Developer LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel

3 2

RFC 3.2 - email checkout slips
by Galen Charlton 31 Jul '08

31 Jul '08

A LibLime customer wants to be able to send emails or SMS messages to a patron whenever the patron checks out or returns an item. The proposed feature would include the following elements * A patron will be able to control when and how to receive checkout and return alerts via the OPAC patron profile interface. * The library will be able to specify which patron categories and items are eligible for these notices. * Emailed notices will try to group together all of the items loaned or returned during a single session. This will build upon the existing C4::Letters infrastructure. For more information on this proposal, please consult the Koha wiki at http://wiki.koha.org/doku.php?id=en:development:rfcs3.2:rfc32_email_checkou… Thanks in advance for comments. Regards, Galen -- Galen Charlton Koha Application Developer LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel

3 3

patches & bugs.koha.org
by Paul POULAIN 31 Jul '08

31 Jul '08

Hello world, I see a change in the wiki : " Contributors to Koha are encouraged to reference a bug number with every commit. This helps us determine the purpose of the commit and establishes a more searchable and understandable history. If there is no bug open at [[http://bugs.koha.org|bugs.koha.org]] that addresses your contribution, please feel free to open one and describe the bug or enhancement. Then, include the bug number in your commit message and set the "priority" field to "patch-sent". This helps us keep track of patches that have been contributed but not yet applied. " I fully agree with the idea of pointing the bug if there is one. But I strongly disagree about adding a bug if there is none. For at least 2 reasons : - it is an obviously "long" process to add a bug. If we have found a small & quickly fixed bug, then there is no need to add a bug imo. Having a complete patch comment is necessary for the ppl reviewing/validating the patch. But the need of a bug.koha.org is unclear to me (the PATCH-sent thing is not enough imo) - we (BibLibre) have a specific internal (& french) tool for our customer requests. When we fix a bug discovered by a client, frankly, it's a loss of time to translate it to english & rewrite it to bugs.koha.org Comments welcomed. -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc NOUVEAU TELEPHONE : 04 91 81 35 08

5 15

GBS terms of services
by Nicolas Morin 31 Jul '08

31 Jul '08

Hi all, I went to the French Library Association's Congress last week, and had an interesting talk with the representative for Google Book Search in France. I inquired about the new Terms of Services and what they meant for libraries. He was positive that using the GBS API to fetch cover images was crossing the red line: Google doesn't own those cover images, which are "third party material" and shouldn't be used in opacs through the APIs. That's what I was told in no uncertain terms. Nicolas _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel

3 2

RFC 3.2 - hourly circulation policies
by Galen Charlton 31 Jul '08

31 Jul '08

Koha 3's circulation loans are currently measured only in units of days. However, because some libraries perform loans that are measured in minutes or hours, particularly for course reserves and short loans, LibLime proposes to add support for measuring loan periods in time intervals shorter than a day. This support will be a new feature, although it may draw on work that Near Eastern University has done for Koha 2. The main changes will include: * adding columns to issuingrules to specify whether the loan time, grace period, and charging (fining) interval are measure in units of days, hours, or minutes * adding the ability to define a policy for an overnight loan, i.e., a loan that is due the following day at a defined time. * adding display of due times * adding the ability to calculate overdue fines on an hourly basis This RFC refers to several other RFCs that have been sent or will be sent soon, including * System groups * Opening hours * Recalls For more information on this proposal, please consult the Koha wiki at http://wiki.koha.org/doku.php?id=en:development:rfcs3.2:rfc32_hourly_circ Thanks in advance for comments. Regards, Galen -- Galen Charlton Koha Application Developer LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel

3 2

Insert return into templates (for transaltion)
by Zeno Tajoli 31 Jul '08

31 Jul '08

Hi to all, working on translation I have found templase with very few returns (Unix, Win or Mac). For example the template authorised_values.tmpl (dir /koha-tmpl/intranet-tmpl/prog/en/modules/help/admin) is only in 3 lines and the text is only one line (6000 char long). Using poedit we can jump to the template at the start of the line, but if the line is too long, it is very difficult to find the words that we want to check. For the transator is better more lines that one only line. Cheers Zeno Tajoli Zeno Tajoli CILEA - Segrate (MI) tajoliAT_SPAM_no_prendiATcilea.it (Indirizzo mascherato anti-spam; sostituisci quanto tra AT con @)

2 2