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

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

Tipo fix (unimarc templates).
by Zeno Tajoli 31 Jul '08

31 Jul '08

Hi to all, I write here same tipo fix about english template for Unimarc. The dir is /koha-tmpl/intranet-tmpl/prog/en/modules/cataloguing/value_builder/ --file unimarc_field_116.tmpl rows 955, 1152, 1345: Litographie/option>, to fix in: Litographie</option> --file unimarc_field_140.tmpl row 644: Plans/, to fix in : Plans Cheers Zeno Tajoli Zeno Tajoli CILEA - Segrate (MI) tajoliAT_SPAM_no_prendiATcilea.it (Indirizzo mascherato anti-spam; sostituisci quanto tra AT con @)

2 1

Good Bye
by Dorian Meid 30 Jul '08

30 Jul '08

After long time silence from me I finally have to cease my comittment for Koha. Our small library has been taken over and also did I quit my honorary position as a librarian and sysadmin there. The new leadership has declared that they are not willing to continue using Koha which makes me sad and angry. My real Job didn't left me much room for additional efforts anyway and so I now want to say good bye to all of you and whish you all the best and good luck developing Koha to the best free ILS ever. Dorian Meid

2 1

Re: [Koha-devel] [Koha-patches] [PATCH] BUG-2393: ENHANCEMENT: SearchMember() uses "cardnumber%" wildcard - if other search-types fail
by Andrew Moore 30 Jul '08

30 Jul '08

(Note: moved to koha-devel from patches) Hi Paul - On Fri, Jul 25, 2008 at 1:57 AM, paul POULAIN <paul.poulain(a)biblibre.com> wrote: > Please note that the SQL "LIMIT" pragma is mySQL specific. So it must be > avoided. Is this a guideline we should be currently following? I'm not asking because i disagree with it, in fact I think it's an admirable goal. I just hadn't seen it documented anywhere like the developers' wiki, and I fear that I've probably been failing to abide by it. I think there are plenty of uses of "LIMIT" in the code, and if this is something we're working towards, I'll start eliminating them in any code I work on. Thanks! -Andy

3 2

About macles.pl
by Zeno Tajoli 30 Jul '08

30 Jul '08

Hi to all, checking the staff translation I have found a connection to the script ../cataloguing/value_builder/macles.pl. For me is not clea the use of the plugin for cataloguing. Is 'MACLES' a name for a specif type of keywords ? Or is it samething else ? Can you explain me the use of this plugin ? Thank you very much Cheers Zeno Tajoli Zeno Tajoli CILEA - Segrate (MI) tajoliAT_SPAM_no_prendiATcilea.it (Indirizzo mascherato anti-spam; sostituisci quanto tra AT con @)

3 2

Is aqorderdelivery table of any use?
by Chris Nighswonger 30 Jul '08

30 Jul '08

Hi all, I cannot see where the aqorderdelivery table is used except in some queries in a acquisitions_stats.pl. However, the table never appears to be populated. I'm wondering if it has any present or future purpose? If not, is there any objection to removing it? Kind Regards, -- Chris Nighswonger LibLime www.liblime.com chris.nighswonger(a)liblime.com

3 2