From chris at bigballofwax.co.nz  Mon Aug  1 00:19:51 2011
From: chris at bigballofwax.co.nz (Chris Cormack)
Date: Mon, 1 Aug 2011 10:19:51 +1200
Subject: [Koha-devel] Patch format
In-Reply-To: <0634FFC5-3822-4AF3-9B08-5F63E2769B6A@math.uni-bonn.de>
References: <20110727141103.GA24413@gumme.math.uni-bonn.de>
	<1311808432.2552.19.camel@zarathud>
	<8113E6DC-5C86-4113-B06A-A7516EC20809@math.uni-bonn.de>
	<CA+95qVQ+uq+nz_bH4o-fVuXzW9J7cCrayHGScM7wiT6xvv9peA@mail.gmail.com>
	<0634FFC5-3822-4AF3-9B08-5F63E2769B6A@math.uni-bonn.de>
Message-ID: <CA+95qVQiRGBGoFQF5ZqCLh0ZWfZ46Ng4iGue9pEO6XE3AJdY0w@mail.gmail.com>

On 1 August 2011 10:17, Edgar Fu? <ef at math.uni-bonn.de> wrote:
>> If you use git format-patch and then git send-email to send it to the
>> koha-patches mailing list.
> Oh well, I'll try this tomorrow. It's past midnight in my timezone now.
>
>> that's not as nessecary the mailing list is the main place
> Is that information somehow pushed back to bugzilla? Or how do I know someone already posted a patch to the list for a bug I would start to work on?
>
>> This is the way the other 147 developers do it
> I don't quite think I would regard myself a Koha developer.
> I'm sort of hopping from one Open Source project to another. So it's sometimes difficult for me to get accustomed to the project's bug reporting policy. However, Koha seems to be the first project I met preferring git patches git format-patch'ed git send-email'ed to a patches list. I'll try to get accustomed to that.

Here are some good resources
http://wiki.koha-community.org/wiki/Version_Control_Using_Git
http://wiki.koha-community.org/wiki/Set_an_email_alias_for_Koha_patches
http://wiki.koha-community.org/wiki/Sign_off_on_patches
http://wiki.koha-community.org/wiki/Bug-enhancement-patch_Workflow

Chris

From pianohacker at gmail.com  Mon Aug  1 01:54:53 2011
From: pianohacker at gmail.com (Jesse)
Date: Sun, 31 Jul 2011 17:54:53 -0600
Subject: [Koha-devel] Perl scripts not ending in .pl
In-Reply-To: <1C7A8B7B-E343-4396-AEA9-387FDC452FBC@math.uni-bonn.de>
References: <178AB0C6-3CEB-4F28-9016-C27BFD8ABED1@math.uni-bonn.de>
	<4E35761A.3090800@ptfs-europe.com>
	<1C7A8B7B-E343-4396-AEA9-387FDC452FBC@math.uni-bonn.de>
Message-ID: <CAEjTV=-+SvqORCtgBhBXf4S2fmXVUTbGHMv22k3f-QQz-Qg-Zg@mail.gmail.com>

There are reasons that these scripts lack that extension. koha-preferences
doesn't have the extension since it's a utility intended to be run from the
command line, as opposed to a cronjob or CGI script. Services just lack the
extension to distinguish them from user-facing CGI scripts. Besides, if
we're exposing APIs, it's nice to keep the underlying technology out of the
URL.

It's convention, not law, but it would be a bit of a pain to change it.

2011/7/31 Edgar Fu? <ef at math.uni-bonn.de>

> > There's no reason for a perl program to end in .pl beyond convention
> Yes, of course.
> But if you have nearly all of the scripts ending in .pl and a
> fix-perl-path.PL that seems to suggest all the scripts do end in .pl, that's
> confusing.
>
> Let me elaborate on how this hit me:
> I was working for a fix to 6390, introducing a new syspref. Changing the
> syspref failed with ``internal server error'' (not the real one, the
> JavaScript popup).
> After hours of searching and tracing my web server, I found out that
> svc/config/systempreferences was not executed, but delivered, because a) I
> had configured my lighttpd to only execute .pl scripts and b) it had
> /usr/bin/perl, not /usr/pkg/bin/perl in it.
>
> So the problem was that this one script was different from the others.
> I was misled because I thought I had broken the setting of preferences with
> my patch, while really it never worked for me with this version of Koha. I
> just never tried since the upgrade.
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>



-- 
Jesse Weaver
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110731/464ebcfa/attachment-0001.htm>

From mtj at kohaaloha.com  Mon Aug  1 02:49:30 2011
From: mtj at kohaaloha.com (Mason James)
Date: Mon, 1 Aug 2011 12:49:30 +1200
Subject: [Koha-devel] Patch format
In-Reply-To: <CA+95qVQiRGBGoFQF5ZqCLh0ZWfZ46Ng4iGue9pEO6XE3AJdY0w@mail.gmail.com>
References: <20110727141103.GA24413@gumme.math.uni-bonn.de>
	<1311808432.2552.19.camel@zarathud>
	<8113E6DC-5C86-4113-B06A-A7516EC20809@math.uni-bonn.de>
	<CA+95qVQ+uq+nz_bH4o-fVuXzW9J7cCrayHGScM7wiT6xvv9peA@mail.gmail.com>
	<0634FFC5-3822-4AF3-9B08-5F63E2769B6A@math.uni-bonn.de>
	<CA+95qVQiRGBGoFQF5ZqCLh0ZWfZ46Ng4iGue9pEO6XE3AJdY0w@mail.gmail.com>
Message-ID: <21C8F2BD-C595-4871-BC7B-61BABB2302E1@kohaaloha.com>


On 2011-08-1, at 10:19 AM, Chris Cormack wrote:

> On 1 August 2011 10:17, Edgar Fu? <ef at math.uni-bonn.de> wrote:
>>> If you use git format-patch and then git send-email to send it to the
>>> koha-patches mailing list.
>> Oh well, I'll try this tomorrow. It's past midnight in my timezone now.
>> 
>>> that's not as nessecary the mailing list is the main place
>> Is that information somehow pushed back to bugzilla? Or how do I know someone already posted a patch to the list for a bug I would start to work on?

every patch should have a bug ticket created in bugzilla, *before* the patch is sent to the patches mailing-list

so... i search bugzilla to see if someone has already posted a patch to my problem



>> However, Koha seems to be the first project I met preferring git patches git format-patch'ed git send-email'ed to a patches list. I'll try to get accustomed to that.


i think an little improvement to our current patch workflow, would be to just attach the patch to a bug, in bugzilla
an automated bugzilla script could then send that new patch to the patches list

this proposed method removes the double-handling of a patch (sending to patches-list and attaching to bugzilla)

and would help encourage people to use bugzilla to track their patches, rather than sending the patch to the list, and the patch getting lost

a good idea, or not?


Mason

From M.de.Rooy at rijksmuseum.nl  Mon Aug  1 08:44:39 2011
From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy)
Date: Mon, 1 Aug 2011 06:44:39 +0000
Subject: [Koha-devel] FW:  Patch format
Message-ID: <809BE39CD64BFD4EB9036172EBCCFA31308CC5@S-MAIL-1B.rijksmuseum.intra>

+1 for removing redundancy ;)

-----Oorspronkelijk bericht-----
Van: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org] Namens Mason James
Verzonden: maandag 1 augustus 2011 02:50
CC: koha-devel at lists.koha-community.org
Onderwerp: Re: [Koha-devel] Patch format


i think an little improvement to our current patch workflow, would be to just attach the patch to a bug, in bugzilla
an automated bugzilla script could then send that new patch to the patches list

this proposed method removes the double-handling of a patch (sending to patches-list and attaching to bugzilla)

and would help encourage people to use bugzilla to track their patches, rather than sending the patch to the list, and the patch getting lost

a good idea, or not?


Mason
_______________________________________________
Koha-devel mailing list
Koha-devel at lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

From magnus at enger.priv.no  Mon Aug  1 09:03:57 2011
From: magnus at enger.priv.no (Magnus Enger)
Date: Mon, 1 Aug 2011 09:03:57 +0200
Subject: [Koha-devel] Patch format
In-Reply-To: <21C8F2BD-C595-4871-BC7B-61BABB2302E1@kohaaloha.com>
References: <20110727141103.GA24413@gumme.math.uni-bonn.de>
	<1311808432.2552.19.camel@zarathud>
	<8113E6DC-5C86-4113-B06A-A7516EC20809@math.uni-bonn.de>
	<CA+95qVQ+uq+nz_bH4o-fVuXzW9J7cCrayHGScM7wiT6xvv9peA@mail.gmail.com>
	<0634FFC5-3822-4AF3-9B08-5F63E2769B6A@math.uni-bonn.de>
	<CA+95qVQiRGBGoFQF5ZqCLh0ZWfZ46Ng4iGue9pEO6XE3AJdY0w@mail.gmail.com>
	<21C8F2BD-C595-4871-BC7B-61BABB2302E1@kohaaloha.com>
Message-ID: <CABg6UYHt+O34GrV38J08G3i6XiN8CJGNpccbUazfvHnvL-v_kw@mail.gmail.com>

On 1 August 2011 02:49, Mason James <mtj at kohaaloha.com> wrote:
> i think an little improvement to our current patch workflow, would be to just attach the patch to a bug, in bugzilla
> an automated bugzilla script could then send that new patch to the patches list

+1 yay!

Best regards,
Magnus Enger
libriotech.no

From chris at bigballofwax.co.nz  Mon Aug  1 09:06:46 2011
From: chris at bigballofwax.co.nz (Chris Cormack)
Date: Mon, 1 Aug 2011 19:06:46 +1200
Subject: [Koha-devel] Patch format
In-Reply-To: <CABg6UYHt+O34GrV38J08G3i6XiN8CJGNpccbUazfvHnvL-v_kw@mail.gmail.com>
References: <20110727141103.GA24413@gumme.math.uni-bonn.de>
	<1311808432.2552.19.camel@zarathud>
	<8113E6DC-5C86-4113-B06A-A7516EC20809@math.uni-bonn.de>
	<CA+95qVQ+uq+nz_bH4o-fVuXzW9J7cCrayHGScM7wiT6xvv9peA@mail.gmail.com>
	<0634FFC5-3822-4AF3-9B08-5F63E2769B6A@math.uni-bonn.de>
	<CA+95qVQiRGBGoFQF5ZqCLh0ZWfZ46Ng4iGue9pEO6XE3AJdY0w@mail.gmail.com>
	<21C8F2BD-C595-4871-BC7B-61BABB2302E1@kohaaloha.com>
	<CABg6UYHt+O34GrV38J08G3i6XiN8CJGNpccbUazfvHnvL-v_kw@mail.gmail.com>
Message-ID: <CA+95qVQsNfNbpT3i6WE+DgHLh04szKjT08m84WBEjMQBe9MJvw@mail.gmail.com>

On 1 August 2011 19:03, Magnus Enger <magnus at enger.priv.no> wrote:
> On 1 August 2011 02:49, Mason James <mtj at kohaaloha.com> wrote:
>> i think an little improvement to our current patch workflow, would be to just attach the patch to a bug, in bugzilla
>> an automated bugzilla script could then send that new patch to the patches list
>
> +1 yay!
>
Patch for said script gratefully accepted, until then can we keep
sending to the mailing list please.

Chris

From M.de.Rooy at rijksmuseum.nl  Mon Aug  1 09:17:50 2011
From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy)
Date: Mon, 1 Aug 2011 07:17:50 +0000
Subject: [Koha-devel] Bug 6584
Message-ID: <809BE39CD64BFD4EB9036172EBCCFA31308D2B@S-MAIL-1B.rijksmuseum.intra>

Hi Owen [and all],


From M.de.Rooy at rijksmuseum.nl  Mon Aug  1 09:23:46 2011
From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy)
Date: Mon, 1 Aug 2011 07:23:46 +0000
Subject: [Koha-devel] FW: Bug 6584
Message-ID: <809BE39CD64BFD4EB9036172EBCCFA31308D3E@S-MAIL-1B.rijksmuseum.intra>

Oops,
Discovered that Katrin already signed it off.
But it still needs some time to mature on the Signed list ;)

Marcel

Van: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org] Namens Marcel de Rooy
Verzonden: maandag 1 augustus 2011 09:18
Aan: koha-devel at lists.koha-community.org
Onderwerp: [Koha-devel] Bug 6584

Hi Owen [and all],


From chris at bigballofwax.co.nz  Mon Aug  1 09:45:38 2011
From: chris at bigballofwax.co.nz (Chris Cormack)
Date: Mon, 1 Aug 2011 19:45:38 +1200
Subject: [Koha-devel] FW: Bug 6584
In-Reply-To: <809BE39CD64BFD4EB9036172EBCCFA31308D3E@S-MAIL-1B.rijksmuseum.intra>
References: <809BE39CD64BFD4EB9036172EBCCFA31308D3E@S-MAIL-1B.rijksmuseum.intra>
Message-ID: <CA+95qVSdO=zC2Zb+_H48ae2dmcOokWPEqozPSbYcmCvWSuacBg@mail.gmail.com>

2011/8/1 Marcel de Rooy <M.de.Rooy at rijksmuseum.nl>:
> Oops,
>
> Discovered that Katrin already signed it off.
>
> But it still needs some time to mature on the Signed list ;)
>
>
Yep, its awaiting QA, (testing things like code quality as well as regressions)

http://wiki.koha-community.org/wiki/Bug-enhancement-patch_Workflow

Chris

From ef at math.uni-bonn.de  Mon Aug  1 11:55:46 2011
From: ef at math.uni-bonn.de (=?iso-8859-1?Q?Edgar_Fu=DF?=)
Date: Mon, 1 Aug 2011 11:55:46 +0200
Subject: [Koha-devel] Perl scripts not ending in .pl
In-Reply-To: <CAEjTV=-+SvqORCtgBhBXf4S2fmXVUTbGHMv22k3f-QQz-Qg-Zg@mail.gmail.com>
References: <178AB0C6-3CEB-4F28-9016-C27BFD8ABED1@math.uni-bonn.de>
	<4E35761A.3090800@ptfs-europe.com>
	<1C7A8B7B-E343-4396-AEA9-387FDC452FBC@math.uni-bonn.de>
	<CAEjTV=-+SvqORCtgBhBXf4S2fmXVUTbGHMv22k3f-QQz-Qg-Zg@mail.gmail.com>
Message-ID: <1E48DAC9-36A5-4719-A09E-2E87D5FCFD50@math.uni-bonn.de>

> it would be a bit of a pain to change it.
I've a patch for that in my pkgsrc Koha source package.
However, that doesn't cover the case of unapi being used externally.


From ef at math.uni-bonn.de  Mon Aug  1 15:26:16 2011
From: ef at math.uni-bonn.de (=?iso-8859-1?Q?Edgar_Fu=DF?=)
Date: Mon, 1 Aug 2011 15:26:16 +0200
Subject: [Koha-devel] Perl scripts not ending in .pl
In-Reply-To: <CAEjTV=-+SvqORCtgBhBXf4S2fmXVUTbGHMv22k3f-QQz-Qg-Zg@mail.gmail.com>
References: <178AB0C6-3CEB-4F28-9016-C27BFD8ABED1@math.uni-bonn.de>
	<4E35761A.3090800@ptfs-europe.com>
	<1C7A8B7B-E343-4396-AEA9-387FDC452FBC@math.uni-bonn.de>
	<CAEjTV=-+SvqORCtgBhBXf4S2fmXVUTbGHMv22k3f-QQz-Qg-Zg@mail.gmail.com>
Message-ID: <A2306810-D4F8-42DC-8F77-2B90B0D4FD79@math.uni-bonn.de>

> It's convention, not law
I think there's an additional benefit in having Perl scripts end in .pl: Automated queries. It's not only replacing the shebang line. Think of ``who used module Foo::Bar'' or ``does anyone still call Foo::Bar::deprecated''. You would otherwise need a manually maintained list for that.

From vdanjean.ml at free.fr  Mon Aug  1 19:57:30 2011
From: vdanjean.ml at free.fr (Vincent Danjean)
Date: Mon, 01 Aug 2011 19:57:30 +0200
Subject: [Koha-devel] Perl scripts not ending in .pl
In-Reply-To: <A2306810-D4F8-42DC-8F77-2B90B0D4FD79@math.uni-bonn.de>
References: <178AB0C6-3CEB-4F28-9016-C27BFD8ABED1@math.uni-bonn.de>	<4E35761A.3090800@ptfs-europe.com>	<1C7A8B7B-E343-4396-AEA9-387FDC452FBC@math.uni-bonn.de>	<CAEjTV=-+SvqORCtgBhBXf4S2fmXVUTbGHMv22k3f-QQz-Qg-Zg@mail.gmail.com>
	<A2306810-D4F8-42DC-8F77-2B90B0D4FD79@math.uni-bonn.de>
Message-ID: <4E36E90A.60203@free.fr>

On 01/08/2011 15:26, Edgar Fu? wrote:
>> It's convention, not law
> I think there's an additional benefit in having Perl scripts end in .pl:
> Automated queries. It's not only replacing the shebang line. Think of
> ``who used module Foo::Bar'' or ``does anyone still call Foo::Bar::deprecated''.
> You would otherwise need a manually maintained list for that.

For information, using an extension for a script in the system PATH
must be avoided for a Debian package (see Policy 10.4)

  Regards,
    Vincent

From paul.a at aandc.org  Mon Aug  1 23:05:28 2011
From: paul.a at aandc.org (Paul)
Date: Mon, 01 Aug 2011 17:05:28 -0400
Subject: [Koha-devel] 64-bit versions
Message-ID: <5.2.1.1.2.20110801165323.03139010@stormy.ca>

Some time ago yaz -- and possibly other Koha components -- may have proven 
problematic in a 64-bit server environment.  I'm getting ready to do a 
fresh install of Koha 3.4.3 on a new server using Intel Xeon 64-bit 
architecture, and am looking for reassurance that this will not be a hang-up.

I'll then migrate our current db from 3.2 (on a 32-bit machine) and again 
would appreciate any words of wisdom from any of you as to best 
practices.  The new server will use Ubuntu 10.04LTS rather than 10.10 
(current server) just for the long-term maintenance schedule in a 
production environment.

tnx and br

Paul
Tired old sys-admin 


From chris at bigballofwax.co.nz  Mon Aug  1 23:07:42 2011
From: chris at bigballofwax.co.nz (Chris Cormack)
Date: Tue, 2 Aug 2011 09:07:42 +1200
Subject: [Koha-devel] 64-bit versions
In-Reply-To: <5.2.1.1.2.20110801165323.03139010@stormy.ca>
References: <5.2.1.1.2.20110801165323.03139010@stormy.ca>
Message-ID: <CA+95qVSJw11KujPNY6gu655WtBQ-vtLMjub200vM4ht3bFwM2g@mail.gmail.com>

On 2 August 2011 09:05, Paul <paul.a at aandc.org> wrote:
> Some time ago yaz -- and possibly other Koha components -- may have proven
> problematic in a 64-bit server environment. ?I'm getting ready to do a fresh
> install of Koha 3.4.3 on a new server using Intel Xeon 64-bit architecture,
> and am looking for reassurance that this will not be a hang-up.
>
> I'll then migrate our current db from 3.2 (on a 32-bit machine) and again
> would appreciate any words of wisdom from any of you as to best practices.
> ?The new server will use Ubuntu 10.04LTS rather than 10.10 (current server)
> just for the long-term maintenance schedule in a production environment.
>
We run our production systems on 64bit debian squeeze, with no issues

Chris

From paul.poulain at biblibre.com  Tue Aug  2 03:57:32 2011
From: paul.poulain at biblibre.com (Paul Poulain)
Date: Tue, 02 Aug 2011 03:57:32 +0200
Subject: [Koha-devel] 64-bit versions
In-Reply-To: <CA+95qVSJw11KujPNY6gu655WtBQ-vtLMjub200vM4ht3bFwM2g@mail.gmail.com>
References: <5.2.1.1.2.20110801165323.03139010@stormy.ca>
	<CA+95qVSJw11KujPNY6gu655WtBQ-vtLMjub200vM4ht3bFwM2g@mail.gmail.com>
Message-ID: <4E37598C.3050704@biblibre.com>

Le 01/08/2011 23:07, Chris Cormack a ?crit :
>> I'll then migrate our current db from 3.2 (on a 32-bit machine) and again
>> would appreciate any words of wisdom from any of you as to best practices.
>>  The new server will use Ubuntu 10.04LTS rather than 10.10 (current server)
>> just for the long-term maintenance schedule in a production environment.
>>
> We run our production systems on 64bit debian squeeze, with no issues
Same thing for us: 64bits debian squeeze, with no issues

-- 
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08


From paul.poulain at biblibre.com  Tue Aug  2 11:04:54 2011
From: paul.poulain at biblibre.com (Paul Poulain)
Date: Tue, 02 Aug 2011 11:04:54 +0200
Subject: [Koha-devel] Roles for 3.8
Message-ID: <4E37BDB6.3070501@biblibre.com>

Hi everybody,

Chris suggested in one of his recent blog post that we should start
thinking about positions for next release (starting october)

I've added the page on the wiki:
http://wiki.koha-community.org/wiki/Roles_for_3.8

During the last IRC meeting, we decided :
* Nomination  sept, 22th
* Vote at the next IRC general meeting (beginning of october)


You'll also notice that I've thrown my hat for the Release Manager
responsibility, and put my proposal accordingly. It's something I'm
thinking for some weeks/months now. During last chat session, Chris
said: " volunteer if you are crazy". I'm crazy, I'm still volunteer, and
we're organizing BibLibre to let me having time dedicated to the RM task.
If you have some questions when reading my application, feel free to ask
me (on the mailing list / irc - paul_p - / pm). I will probably refine
my application, and will let you know everytime I make a noticeable change.

Have a good day (or night)

-- 
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08


From paul.poulain at biblibre.com  Tue Aug  2 11:55:05 2011
From: paul.poulain at biblibre.com (Paul Poulain)
Date: Tue, 02 Aug 2011 11:55:05 +0200
Subject: [Koha-devel] Bugzilla & default assignee
Message-ID: <4E37C979.8070500@biblibre.com>

Hi all,

Looking at what is assigned to me, I see that there are things, old or
very old, that I don't plan to deal with, even if, in some case, it's a
valid entry.

For example : http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=444

This is an enhancement. It's still a good idea, still not implemented afaik.
OTOH : It is 7 years old, I discover it now, and don't plan to do
anything about that. The reporter (Ingrid Lacis) has left the project so
she won't do anything too.
What I want is a clear view of what I have to do, and I have nothing to
do with this entry.

My question : what should I do to discard this entry from my list ? I
tried to remove me as assignee, but bz don't want "no assignee". Should
we have a virtual assignee for this kind of entry ? Should I close the
bug entry as it's an enhancement, no-one plan to take care of it ? Other
idea ?


-- 
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08


From ian.walls at bywatersolutions.com  Tue Aug  2 13:07:27 2011
From: ian.walls at bywatersolutions.com (Ian Walls)
Date: Tue, 2 Aug 2011 07:07:27 -0400
Subject: [Koha-devel] 64-bit versions
In-Reply-To: <4E37598C.3050704@biblibre.com>
References: <5.2.1.1.2.20110801165323.03139010@stormy.ca>
	<CA+95qVSJw11KujPNY6gu655WtBQ-vtLMjub200vM4ht3bFwM2g@mail.gmail.com>
	<4E37598C.3050704@biblibre.com>
Message-ID: <CAE2wdZyPQgJxNcMC5jV=-wyOH2i_z_mf7hcZuyY332vnA4CcYg@mail.gmail.com>

ByWater Solutions also runs 64 bit Debian Squeeze, and we are quite pleased
with it.


-Ian

On Mon, Aug 1, 2011 at 9:57 PM, Paul Poulain <paul.poulain at biblibre.com>wrote:

> Le 01/08/2011 23:07, Chris Cormack a ?crit :
> >> I'll then migrate our current db from 3.2 (on a 32-bit machine) and
> again
> >> would appreciate any words of wisdom from any of you as to best
> practices.
> >>  The new server will use Ubuntu 10.04LTS rather than 10.10 (current
> server)
> >> just for the long-term maintenance schedule in a production environment.
> >>
> > We run our production systems on 64bit debian squeeze, with no issues
> Same thing for us: 64bits debian squeeze, with no issues
>
> --
> Paul POULAIN
> http://www.biblibre.com
> Expert en Logiciels Libres pour l'info-doc
> Tel : (33) 4 91 81 35 08
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>



-- 
Ian Walls
Lead Development Specialist
ByWater Solutions
Phone # (888) 900-8944
http://bywatersolutions.com
ian.walls at bywatersolutions.com
Twitter: @sekjal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110802/aa44a87c/attachment.htm>

From paul.a at aandc.org  Tue Aug  2 15:23:22 2011
From: paul.a at aandc.org (Paul)
Date: Tue, 02 Aug 2011 09:23:22 -0400
Subject: [Koha-devel] 64-bit versions
In-Reply-To: <CAE2wdZyPQgJxNcMC5jV=-wyOH2i_z_mf7hcZuyY332vnA4CcYg@mail.g
	mail.com>
References: <4E37598C.3050704@biblibre.com>
	<5.2.1.1.2.20110801165323.03139010@stormy.ca>
	<CA+95qVSJw11KujPNY6gu655WtBQ-vtLMjub200vM4ht3bFwM2g@mail.gmail.com>
	<4E37598C.3050704@biblibre.com>
Message-ID: <5.2.1.1.2.20110802090823.10ac5d48@localhost>

At 07:07 AM 8/2/2011 -0400, Ian Walls wrote:
>ByWater Solutions also runs 64 bit Debian Squeeze, and we are quite 
>pleased with it.

Tnx to all for your replies.  A follow-up if I may?  How much RAM are you 
using?  My current "sand-box server" is very slow (4-7 seconds for 
searches, admin saves, etc) with only 2 gigs; we are refining our new specs 
and hesitating between 8 and 16 gigs for the new box. Our users and 
cataloguers are really looking for more or less instantaneous responses to 
OPAC searches and I'm looking for all the hardware design help I can get.

Best regards - Paul

>-Ian
>
>On Mon, Aug 1, 2011 at 9:57 PM, Paul Poulain 
><<mailto:paul.poulain at biblibre.com>paul.poulain at biblibre.com> wrote:
>Le 01/08/2011 23:07, Chris Cormack a ??crit :
> >> I'll then migrate our current db from 3.2 (on a 32-bit machine) and again
> >> would appreciate any words of wisdom from any of you as to best practices.
> >> ? The new server will use Ubuntu 10.04LTS rather than 10.10 (current 
> server)
> >> just for the long-term maintenance schedule in a production environment.
> >>
> > We run our production systems on 64bit debian squeeze, with no issues
>Same thing for us: 64bits debian squeeze, with no issues

Paul
Tired old sys-admin 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110802/bc97a969/attachment.htm>

From ef at math.uni-bonn.de  Tue Aug  2 16:47:54 2011
From: ef at math.uni-bonn.de (=?iso-8859-1?Q?Edgar_Fu=DF?=)
Date: Tue, 2 Aug 2011 16:47:54 +0200
Subject: [Koha-devel] Extending message queue (was: Sending orders by email)
In-Reply-To: <1311808432.2552.19.camel@zarathud>
References: <20110727141103.GA24413@gumme.math.uni-bonn.de>
	<1311808432.2552.19.camel@zarathud>
Message-ID: <F2C8723A-C044-4EED-9754-C81134C90809@math.uni-bonn.de>

> it would be worth extending the message queue stuff to allow it to happen
I don't see how that could be done. It looks like its whole concept is centred about sending messages to patrons (``borrowers'').

From paivakil at gmail.com  Tue Aug  2 16:56:03 2011
From: paivakil at gmail.com (Mahesh T Pai)
Date: Tue, 02 Aug 2011 20:26:03 +0530
Subject: [Koha-devel] Bugzilla & default assignee
References: <4E37C979.8070500@biblibre.com>
Message-ID: <87zkjr277g.fsf@nandini.localhost>

Paul Poulain <paul.poulain at biblibre.com>
writes:

 > My question : what should I do to discard this entry from my list ? I
 > tried to remove me as assignee, but bz don't want "no assignee". Should
 > we have a virtual assignee for this kind of entry ? Should I close the
 > bug entry as it's an enhancement, no-one plan to take care of it ? Other
 > idea ?

How about the devel list as default assignee? 

Several projects have it that way, afaict. 

-- 
Mahesh T. Pai   ||
L'homme est libre au moment qu'il veut l'etre.
    * Man is free at the instant he wants to be.


From paivakil at gmail.com  Tue Aug  2 17:00:34 2011
From: paivakil at gmail.com (Mahesh T Pai)
Date: Tue, 02 Aug 2011 20:30:34 +0530
Subject: [Koha-devel] 64-bit versions
References: <4E37598C.3050704@biblibre.com>
	<5.2.1.1.2.20110801165323.03139010@stormy.ca>
	<CA+95qVSJw11KujPNY6gu655WtBQ-vtLMjub200vM4ht3bFwM2g@mail.gmail.com>
	<4E37598C.3050704@biblibre.com>
	<5.2.1.1.2.20110802090823.10ac5d48@localhost>
Message-ID: <87vcuf26zx.fsf@nandini.localhost>

Paul <paul.a at aandc.org> writes:


 > Tnx to all for your replies.  A follow-up if I may?  How much RAM are you
 > using?  My current "sand-box server" is very slow (4-7 seconds for searches,
 > admin saves, etc) with only 2 gigs; we are refining our new specs and
 > hesitating between 8 and 16 gigs for the new box. Our users and cataloguers are
 > really looking for more or less instantaneous responses to OPAC searches and
 > I'm looking for all the hardware design help I can get.


1gig ram <tries to hide> for a 7.2K volumes library. 

Not exactly instantaneous responses, but neither so slow. 

3.4.2 is visibly faster than 3.4.1 anyway - especially in staff client
searches. 

-- 
Mahesh T. Pai   ||
Half knowledge is worse than ignorance.
    --Thomas B. Macaulay


From paul.poulain at biblibre.com  Tue Aug  2 17:09:34 2011
From: paul.poulain at biblibre.com (Paul Poulain)
Date: Tue, 02 Aug 2011 17:09:34 +0200
Subject: [Koha-devel] Bugzilla & default assignee
In-Reply-To: <87zkjr277g.fsf@nandini.localhost>
References: <4E37C979.8070500@biblibre.com> <87zkjr277g.fsf@nandini.localhost>
Message-ID: <4E38132E.9060809@biblibre.com>

Le 02/08/2011 16:56, Mahesh T Pai a ?crit :
> Paul Poulain <paul.poulain at biblibre.com>
> writes:
>
>  > My question : what should I do to discard this entry from my list ? I
>  > tried to remove me as assignee, but bz don't want "no assignee". Should
>  > we have a virtual assignee for this kind of entry ? Should I close the
>  > bug entry as it's an enhancement, no-one plan to take care of it ? Other
>  > idea ?
>
> How about the devel list as default assignee? 
>
> Several projects have it that way, afaict. 
>
Maybe not as the default assignee, but as a possible assignee, it's a
good idea.
It would mean "ok guys, I won't deal with this one, anyone
voluntering/concerned can take it !)
We could then add a public filter "bugs to assign" on bugzilla saved
queries.

-- 
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08


From paul.poulain at biblibre.com  Tue Aug  2 17:10:27 2011
From: paul.poulain at biblibre.com (Paul Poulain)
Date: Tue, 02 Aug 2011 17:10:27 +0200
Subject: [Koha-devel] 64-bit versions
In-Reply-To: <87vcuf26zx.fsf@nandini.localhost>
References: <4E37598C.3050704@biblibre.com>	<5.2.1.1.2.20110801165323.03139010@stormy.ca>	<CA+95qVSJw11KujPNY6gu655WtBQ-vtLMjub200vM4ht3bFwM2g@mail.gmail.com>	<4E37598C.3050704@biblibre.com>	<5.2.1.1.2.20110802090823.10ac5d48@localhost>
	<87vcuf26zx.fsf@nandini.localhost>
Message-ID: <4E381363.2000301@biblibre.com>

Le 02/08/2011 17:00, Mahesh T Pai a ?crit :
> 3.4.2 is visibly faster than 3.4.1 anyway - especially in staff client
> searches. 
really ? anyone has a technical explanation to this boost ?

-- 
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08


From tomascohen at gmail.com  Tue Aug  2 17:46:15 2011
From: tomascohen at gmail.com (tomascohen at gmail.com)
Date: Tue, 02 Aug 2011 15:46:15 +0000
Subject: [Koha-devel] 64-bit versions
In-Reply-To: <4E381363.2000301@biblibre.com>
Message-ID: <20cf3054a095e8580804a987a55f@google.com>

El , Paul Poulain <paul.poulain at biblibre.com> escribi?:
> Le 02/08/2011 17:00, Mahesh T Pai a ?crit :

> > 3.4.2 is visibly faster than 3.4.1 anyway - especially in staff client

> > searches.

> really ? anyone has a technical explanation to this boost ?

Maybe they've just installed memcached which they didn't when installing  
3.4.1

Regards
To+
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110802/25782232/attachment.htm>

From ef at math.uni-bonn.de  Tue Aug  2 18:12:27 2011
From: ef at math.uni-bonn.de (=?iso-8859-1?Q?Edgar_Fu=DF?=)
Date: Tue, 2 Aug 2011 18:12:27 +0200
Subject: [Koha-devel] Restricting access to acquisition baskets
Message-ID: <548E26A0-4443-4AB9-B514-8FACEE57D758@math.uni-bonn.de>

Currently, while booksellers.pl tries to restrict a user's ability to view baskets, that's easily circumvented simply by altering the basketno CGI parameter to, e.g. baket.pl.

I can think of three ways to close this security hole:

1. Check permissions in every script that deals with baskets. This would probably require an addition to C4::Auth.
2. Randomise basket numbers.
3. Add a random key to each basket that must be given as a CGI parameter (in addition to basketno) in order for a script to allow access to that basket.

Please note that for my own part, I'm unaffected by this problem. I have only a single branch and allow access to all that branches' baskets anyway.
Nevertheless, I would give implementing a fix a try if there is consensus on which way to go.

From magnus at enger.priv.no  Tue Aug  2 18:25:48 2011
From: magnus at enger.priv.no (Magnus Enger)
Date: Tue, 2 Aug 2011 18:25:48 +0200
Subject: [Koha-devel] Bugzilla & default assignee
In-Reply-To: <4E38132E.9060809@biblibre.com>
References: <4E37C979.8070500@biblibre.com> <87zkjr277g.fsf@nandini.localhost>
	<4E38132E.9060809@biblibre.com>
Message-ID: <CABg6UYFLFyPRTpa6b385=efT8Yc7sKq3GD2Xjj3RmSYY9tp+eA@mail.gmail.com>

On 2 August 2011 17:09, Paul Poulain <paul.poulain at biblibre.com> wrote:
> Le 02/08/2011 16:56, Mahesh T Pai a ?crit :
>> Paul Poulain <paul.poulain at biblibre.com>
>> writes:
>>
>> ?> My question : what should I do to discard this entry from my list ? I
>> ?> tried to remove me as assignee, but bz don't want "no assignee". Should
>> ?> we have a virtual assignee for this kind of entry ? Should I close the
>> ?> bug entry as it's an enhancement, no-one plan to take care of it ? Other
>> ?> idea ?
>>
>> How about the devel list as default assignee?
>>
>> Several projects have it that way, afaict.
>>
> Maybe not as the default assignee, but as a possible assignee, it's a
> good idea.
> It would mean "ok guys, I won't deal with this one, anyone
> voluntering/concerned can take it !)
> We could then add a public filter "bugs to assign" on bugzilla saved
> queries.

+1 from me!

Best regards,
Magnus Enger
libriotech.no

From ian.walls at bywatersolutions.com  Tue Aug  2 18:36:36 2011
From: ian.walls at bywatersolutions.com (Ian Walls)
Date: Tue, 2 Aug 2011 12:36:36 -0400
Subject: [Koha-devel] 64-bit versions
In-Reply-To: <5.2.1.1.2.20110802090823.10ac5d48@localhost>
References: <5.2.1.1.2.20110801165323.03139010@stormy.ca>
	<CA+95qVSJw11KujPNY6gu655WtBQ-vtLMjub200vM4ht3bFwM2g@mail.gmail.com>
	<4E37598C.3050704@biblibre.com>
	<5.2.1.1.2.20110802090823.10ac5d48@localhost>
Message-ID: <CAE2wdZxk3VG9SvQ5-1BmfLPgpu1pa6QNZV1iDQtAVc7Z6jAyeg@mail.gmail.com>

The guideline we've followed is to have as much RAM as you do MySQL
database.  For a very large system, that's not always possible, and isn't
even necessary with the right tuning, but RAM more than anything is the key
resource to throw at Koha for snappier response.


-Ian

2011/8/2 Paul <paul.a at aandc.org>

>  At 07:07 AM 8/2/2011 -0400, Ian Walls wrote:
>
> ByWater Solutions also runs 64 bit Debian Squeeze, and we are quite pleased
> with it.
>
>
> Tnx to all for your replies.  A follow-up if I may?  How much RAM are you
> using?  My current "sand-box server" is very slow (4-7 seconds for searches,
> admin saves, etc) with only 2 gigs; we are refining our new specs and
> hesitating between 8 and 16 gigs for the new box. Our users and cataloguers
> are really looking for more or less instantaneous responses to OPAC searches
> and I'm looking for all the hardware design help I can get.
>
> Best regards - Paul
>
> -Ian
>
> On Mon, Aug 1, 2011 at 9:57 PM, Paul Poulain <paul.poulain at biblibre.com>
> wrote:
>  Le 01/08/2011 23:07, Chris Cormack a ??crit :
> >> I'll then migrate our current db from 3.2 (on a 32-bit machine) and
> again
> >> would appreciate any words of wisdom from any of you as to best
> practices.
> >> ? The new server will use Ubuntu 10.04LTS rather than 10.10 (current
> server)
>
> >> just for the long-term maintenance schedule in a production environment.
> >>
> > We run our production systems on 64bit debian squeeze, with no issues
> Same thing for us: 64bits debian squeeze, with no issues
>
> **
>
> ** Paul
> Tired old sys-admin
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>



-- 
Ian Walls
Lead Development Specialist
ByWater Solutions
Phone # (888) 900-8944
http://bywatersolutions.com
ian.walls at bywatersolutions.com
Twitter: @sekjal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110802/dbff2e59/attachment.htm>

From paul.poulain at biblibre.com  Tue Aug  2 18:42:10 2011
From: paul.poulain at biblibre.com (Paul Poulain)
Date: Tue, 02 Aug 2011 18:42:10 +0200
Subject: [Koha-devel] 64-bit versions
In-Reply-To: <CAE2wdZxk3VG9SvQ5-1BmfLPgpu1pa6QNZV1iDQtAVc7Z6jAyeg@mail.gmail.com>
References: <5.2.1.1.2.20110801165323.03139010@stormy.ca>	<CA+95qVSJw11KujPNY6gu655WtBQ-vtLMjub200vM4ht3bFwM2g@mail.gmail.com>	<4E37598C.3050704@biblibre.com>	<5.2.1.1.2.20110802090823.10ac5d48@localhost>
	<CAE2wdZxk3VG9SvQ5-1BmfLPgpu1pa6QNZV1iDQtAVc7Z6jAyeg@mail.gmail.com>
Message-ID: <4E3828E2.7050204@biblibre.com>

Le 02/08/2011 18:36, Ian Walls a ?crit :
> The guideline we've followed is to have as much RAM as you do MySQL
> database.  For a very large system, that's not always possible, and
> isn't even necessary with the right tuning, but RAM more than anything
> is the key resource to throw at Koha for snappier response.
>
good point Ian.

Paul, you can look at
http://www.biblibre.com/en/blog/entry/mysql-default-config-and-very-large-koha-database
to see which configuration we use.

-- 
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08


From ian.walls at bywatersolutions.com  Tue Aug  2 19:04:54 2011
From: ian.walls at bywatersolutions.com (Ian Walls)
Date: Tue, 2 Aug 2011 13:04:54 -0400
Subject: [Koha-devel] Proposal for Assistance with QA Testing for Koha 3.6
Message-ID: <CAE2wdZw4=6Dja9FWx3uHc2uBOCoOMR6rNpuZVBp3+pPtgGucNg@mail.gmail.com>

Dear Community,


As you are likely aware, I am the elected Quality Assurance Manager for the
3.6 release.  As you may also be aware, there are currently 96 patches in
Bugzilla that are signed off and ready for QA testing (at the time of this
writing).  My goal for my term as QAM was to keep this list under 10, but as
we can see, that's not the current state of things.

I do not want to become a bottleneck against good code getting into Koha.
Quality Assurance is by it's nature a painstaking process, especially with
more complex patches, to ensure that there are no regressions of
functionality, or massive, unexpected shifts in default behavior.  Often,
numerous configurations of data need to checked against, to make sure fixing
a bug for one possible setup doesn't cause a new bug in another.  So far,
we've not had to pull any code from master due to a regression, so it seems
this process is working.  But, that said, we've still got nearly a hundred
patches waiting in the queue.

Paul Poulain has offered to assist me with QA for the remainder of the Koha
3.6 release cycle.  He's got the hours to dedicate towards this, and can
help put some of these patches through their paces.  While anyone can test
any patch that's been published (and everyone is encouraged to do so), Paul
is asking for the additional power to mark the patches he's tested as
"Passed QA" if they do indeed pass his tests.  Here are the exact terms of
the proposal:

a) he would not mark any patch he himself has written as Passed QA
b) any patch written by BibLibre would need a signoff from another, external
person before he'd test it
c) he would start with the patches that have been waiting the longest
d) the QAM and RM could reject any "Passed QA" patch if they feel it's not
sufficient for whatever reason (which would need to be noted in the bug
report)

I do not feel that I necessarily have the right to transfer the "mark
patches as Passed QA" power over to another person without the community's
consent.  So, I bring this to the group.  Is this an acceptable proposal?
Does the QAM have the right to "deputize" community members and transfer
this particular power, or does the community need to vote on it?  Are there
any aspects of the issue that I'm missing?

Thanks for your consideration and attention on this matter,



-Ian



-- 
Ian Walls
Lead Development Specialist
ByWater Solutions
Phone # (888) 900-8944
http://bywatersolutions.com
ian.walls at bywatersolutions.com
Twitter: @sekjal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110802/84b5c227/attachment.htm>

From swills at beyond-print.com  Tue Aug  2 19:39:12 2011
From: swills at beyond-print.com (Stephen Wills)
Date: Tue, 2 Aug 2011 13:39:12 -0400
Subject: [Koha-devel] Proposal for Assistance with QA Testing for Koha
	3.6
In-Reply-To: <CAE2wdZw4=6Dja9FWx3uHc2uBOCoOMR6rNpuZVBp3+pPtgGucNg@mail.gmail.com>
References: <CAE2wdZw4=6Dja9FWx3uHc2uBOCoOMR6rNpuZVBp3+pPtgGucNg@mail.gmail.com>
Message-ID: <63355664-5EF9-4FED-A7F6-C5F6594F31AC@beyond-print.com>

+1, QAM is not the same as carry the yolk alone!

On Aug 2, 2011, at 1:04 PM, Ian Walls wrote:

> Dear Community,
>
>
> As you are likely aware, I am the elected Quality Assurance Manager  
> for the 3.6 release.  As you may also be aware, there are currently  
> 96 patches in Bugzilla that are signed off and ready for QA testing  
> (at the time of this writing).  My goal for my term as QAM was to  
> keep this list under 10, but as we can see, that's not the current  
> state of things.
>
> I do not want to become a bottleneck against good code getting into  
> Koha.  Quality Assurance is by it's nature a painstaking process,  
> especially with more complex patches, to ensure that there are no  
> regressions of functionality, or massive, unexpected shifts in  
> default behavior.  Often, numerous configurations of data need to  
> checked against, to make sure fixing a bug for one possible setup  
> doesn't cause a new bug in another.  So far, we've not had to pull  
> any code from master due to a regression, so it seems this process  
> is working.  But, that said, we've still got nearly a hundred  
> patches waiting in the queue.
>
> Paul Poulain has offered to assist me with QA for the remainder of  
> the Koha 3.6 release cycle.  He's got the hours to dedicate towards  
> this, and can help put some of these patches through their paces.   
> While anyone can test any patch that's been published (and everyone  
> is encouraged to do so), Paul is asking for the additional power to  
> mark the patches he's tested as "Passed QA" if they do indeed pass  
> his tests.  Here are the exact terms of the proposal:
>
> a) he would not mark any patch he himself has written as Passed QA
> b) any patch written by BibLibre would need a signoff from another,  
> external person before he'd test it
> c) he would start with the patches that have been waiting the longest
> d) the QAM and RM could reject any "Passed QA" patch if they feel  
> it's not sufficient for whatever reason (which would need to be  
> noted in the bug report)
>
> I do not feel that I necessarily have the right to transfer the  
> "mark patches as Passed QA" power over to another person without the  
> community's consent.  So, I bring this to the group.  Is this an  
> acceptable proposal?  Does the QAM have the right to "deputize"  
> community members and transfer this particular power, or does the  
> community need to vote on it?  Are there any aspects of the issue  
> that I'm missing?
>
> Thanks for your consideration and attention on this matter,
>
>
>
> -Ian
>
>
>
> -- 
> Ian Walls
> Lead Development Specialist
> ByWater Solutions
> Phone # (888) 900-8944
> http://bywatersolutions.com
> ian.walls at bywatersolutions.com
> Twitter: @sekjal
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110802/d82cabb9/attachment.htm>

From M.de.Rooy at rijksmuseum.nl  Tue Aug  2 21:49:40 2011
From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy)
Date: Tue, 2 Aug 2011 19:49:40 +0000
Subject: [Koha-devel] Proposal for Assistance with QA Testing for Koha
 3.6
In-Reply-To: <CAE2wdZw4=6Dja9FWx3uHc2uBOCoOMR6rNpuZVBp3+pPtgGucNg@mail.gmail.com>
References: <CAE2wdZw4=6Dja9FWx3uHc2uBOCoOMR6rNpuZVBp3+pPtgGucNg@mail.gmail.com>
Message-ID: <809BE39CD64BFD4EB9036172EBCCFA31309328@S-MAIL-1B.rijksmuseum.intra>

FWIW:
I personally would welcome Paul as assistant QAM.
But I do not think that QAM should "deputize" others without consent of the community.
QAM and assistants could be elected on a meeting.
In this case I would suggest to let Paul start and make it formal on the next meeting.
________________________________
Van: koha-devel-bounces at lists.koha-community.org [koha-devel-bounces at lists.koha-community.org] namens Ian Walls [ian.walls at bywatersolutions.com]
Verzonden: dinsdag 2 augustus 2011 19:04
Aan: koha-devel at lists.koha-community.org
Onderwerp: [Koha-devel] Proposal for Assistance with QA Testing for Koha 3.6

Dear Community,


As you are likely aware, I am the elected Quality Assurance Manager for the 3.6 release.  As you may also be aware, there are currently 96 patches in Bugzilla that are signed off and ready for QA testing (at the time of this writing).  My goal for my term as QAM was to keep this list under 10, but as we can see, that's not the current state of things.

I do not want to become a bottleneck against good code getting into Koha.  Quality Assurance is by it's nature a painstaking process, especially with more complex patches, to ensure that there are no regressions of functionality, or massive, unexpected shifts in default behavior.  Often, numerous configurations of data need to checked against, to make sure fixing a bug for one possible setup doesn't cause a new bug in another.  So far, we've not had to pull any code from master due to a regression, so it seems this process is working.  But, that said, we've still got nearly a hundred patches waiting in the queue.

Paul Poulain has offered to assist me with QA for the remainder of the Koha 3.6 release cycle.  He's got the hours to dedicate towards this, and can help put some of these patches through their paces.  While anyone can test any patch that's been published (and everyone is encouraged to do so), Paul is asking for the additional power to mark the patches he's tested as "Passed QA" if they do indeed pass his tests.  Here are the exact terms of the proposal:

a) he would not mark any patch he himself has written as Passed QA
b) any patch written by BibLibre would need a signoff from another, external person before he'd test it
c) he would start with the patches that have been waiting the longest
d) the QAM and RM could reject any "Passed QA" patch if they feel it's not sufficient for whatever reason (which would need to be noted in the bug report)

I do not feel that I necessarily have the right to transfer the "mark patches as Passed QA" power over to another person without the community's consent.  So, I bring this to the group.  Is this an acceptable proposal?  Does the QAM have the right to "deputize" community members and transfer this particular power, or does the community need to vote on it?  Are there any aspects of the issue that I'm missing?

Thanks for your consideration and attention on this matter,



-Ian



--
Ian Walls
Lead Development Specialist
ByWater Solutions
Phone # (888) 900-8944
http://bywatersolutions.com
ian.walls at bywatersolutions.com<mailto:ian.walls at bywatersolutions.com>
Twitter: @sekjal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110802/e7d08659/attachment-0001.htm>

From chris at bigballofwax.co.nz  Tue Aug  2 21:56:43 2011
From: chris at bigballofwax.co.nz (Chris Cormack)
Date: Wed, 3 Aug 2011 07:56:43 +1200
Subject: [Koha-devel] Proposal for Assistance with QA Testing for Koha
	3.6
In-Reply-To: <63355664-5EF9-4FED-A7F6-C5F6594F31AC@beyond-print.com>
References: <CAE2wdZw4=6Dja9FWx3uHc2uBOCoOMR6rNpuZVBp3+pPtgGucNg@mail.gmail.com>
	<63355664-5EF9-4FED-A7F6-C5F6594F31AC@beyond-print.com>
Message-ID: <CA+95qVTEONL9TBbeHjNuusS-FPGg+45DQD7cTRGYY1be-tbBTw@mail.gmail.com>

On 3 Aug 2011 05:39, "Stephen Wills" <swills at beyond-print.com> wrote:
>
> +1, QAM is not the same as carry the yolk alone!

Indeed, and like Marcel I have no issues in this case. But I do think he is
right about it being a community decision.

Having said that, I think paul will do fine.

But everyone can help, it still shouldn't be left to Ian and Paul. How can
you help you ask.
Write a how to test on your bug
Write a good description of what the patch should do, remember the more you
tell, the easier it is to test
Write accompanying tests.
And even though a patch has been signed off, there is no reason you can't
add your signoff too. To strengthen the confidence we have that the patch
will work.

It is a law of the universe, immutable even.
Release Managers Law : In no circumstances ever can a patch have too many
sign offs

Chris
>
> On Aug 2, 2011, at 1:04 PM, Ian Walls wrote:
>
>> Dear Community,
>>
>>
>> As you are likely aware, I am the elected Quality Assurance Manager for
the 3.6 release.  As you may also be aware, there are currently 96 patches
in Bugzilla that are signed off and ready for QA testing (at the time of
this writing).  My goal for my term as QAM was to keep this list under 10,
but as we can see, that's not the current state of things.
>>
>> I do not want to become a bottleneck against good code getting into
Koha.  Quality Assurance is by it's nature a painstaking process, especially
with more complex patches, to ensure that there are no regressions of
functionality, or massive, unexpected shifts in default behavior.  Often,
numerous configurations of data need to checked against, to make sure fixing
a bug for one possible setup doesn't cause a new bug in another.  So far,
we've not had to pull any code from master due to a regression, so it seems
this process is working.  But, that said, we've still got nearly a hundred
patches waiting in the queue.
>>
>> Paul Poulain has offered to assist me with QA for the remainder of the
Koha 3.6 release cycle.  He's got the hours to dedicate towards this, and
can help put some of these patches through their paces.  While anyone can
test any patch that's been published (and everyone is encouraged to do so),
Paul is asking for the additional power to mark the patches he's tested as
"Passed QA" if they do indeed pass his tests.  Here are the exact terms of
the proposal:
>>
>> a) he would not mark any patch he himself has written as Passed QA
>> b) any patch written by BibLibre would need a signoff from another,
external person before he'd test it
>> c) he would start with the patches that have been waiting the longest
>> d) the QAM and RM could reject any "Passed QA" patch if they feel it's
not sufficient for whatever reason (which would need to be noted in the bug
report)
>>
>> I do not feel that I necessarily have the right to transfer the "mark
patches as Passed QA" power over to another person without the community's
consent.  So, I bring this to the group.  Is this an acceptable proposal?
Does the QAM have the right to "deputize" community members and transfer
this particular power, or does the community need to vote on it?  Are there
any aspects of the issue that I'm missing?
>>
>> Thanks for your consideration and attention on this matter,
>>
>>
>>
>> -Ian
>>
>>
>>
>> --
>> Ian Walls
>> Lead Development Specialist
>> ByWater Solutions
>> Phone # (888) 900-8944
>> http://bywatersolutions.com
>> ian.walls at bywatersolutions.com
>> Twitter: @sekjal
>> _______________________________________________
>> Koha-devel mailing list
>> Koha-devel at lists.koha-community.org
>> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>> website : http://www.koha-community.org/
>> git : http://git.koha-community.org/
>> bugs : http://bugs.koha-community.org/
>
>
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110803/acdfeb67/attachment.htm>

From mtj at kohaaloha.com  Tue Aug  2 23:02:34 2011
From: mtj at kohaaloha.com (Mason James)
Date: Wed, 3 Aug 2011 09:02:34 +1200
Subject: [Koha-devel] Patch format
In-Reply-To: <CA+95qVQsNfNbpT3i6WE+DgHLh04szKjT08m84WBEjMQBe9MJvw@mail.gmail.com>
References: <20110727141103.GA24413@gumme.math.uni-bonn.de>
	<1311808432.2552.19.camel@zarathud>
	<8113E6DC-5C86-4113-B06A-A7516EC20809@math.uni-bonn.de>
	<CA+95qVQ+uq+nz_bH4o-fVuXzW9J7cCrayHGScM7wiT6xvv9peA@mail.gmail.com>
	<0634FFC5-3822-4AF3-9B08-5F63E2769B6A@math.uni-bonn.de>
	<CA+95qVQiRGBGoFQF5ZqCLh0ZWfZ46Ng4iGue9pEO6XE3AJdY0w@mail.gmail.com>
	<21C8F2BD-C595-4871-BC7B-61BABB2302E1@kohaaloha.com>
	<CABg6UYHt+O34GrV38J08G3i6XiN8CJGNpccbUazfvHnvL-v_kw@mail.gmail.com>
	<CA+95qVQsNfNbpT3i6WE+DgHLh04szKjT08m84WBEjMQBe9MJvw@mail.gmail.com>
Message-ID: <0A54B74E-9554-413D-B674-5C433B32C287@kohaaloha.com>


On 2011-08-1, at 7:06 PM, Chris Cormack wrote:

> On 1 August 2011 19:03, Magnus Enger <magnus at enger.priv.no> wrote:
>> On 1 August 2011 02:49, Mason James <mtj at kohaaloha.com> wrote:
>>> i think an little improvement to our current patch workflow, would be to just attach the patch to a bug, in bugzilla
>>> an automated bugzilla script could then send that new patch to the patches list
>> 
>> +1 yay!
>> 
> Patch for said script gratefully accepted,

cool, i'll put my hand up to sort this script

From mtj at kohaaloha.com  Tue Aug  2 23:14:15 2011
From: mtj at kohaaloha.com (Mason James)
Date: Wed, 3 Aug 2011 09:14:15 +1200
Subject: [Koha-devel] Restricting access to acquisition baskets
In-Reply-To: <548E26A0-4443-4AB9-B514-8FACEE57D758@math.uni-bonn.de>
References: <548E26A0-4443-4AB9-B514-8FACEE57D758@math.uni-bonn.de>
Message-ID: <BC1E7D0D-79E3-46CE-A5E2-738F6A64B7D1@kohaaloha.com>


On 2011-08-3, at 4:12 AM, Edgar Fu? wrote:

> Currently, while booksellers.pl tries to restrict a user's ability to view baskets, that's easily circumvented simply by altering the basketno CGI parameter to, e.g. baket.pl.


hmmm, perhaps log this issue in bugzilla?
 
 -> http://bugs.koha-community.org/bugzilla3/

From robin at catalyst.net.nz  Wed Aug  3 03:03:26 2011
From: robin at catalyst.net.nz (Robin Sheat)
Date: Wed, 03 Aug 2011 13:03:26 +1200
Subject: [Koha-devel] FW:  Patch format
In-Reply-To: <809BE39CD64BFD4EB9036172EBCCFA31308CC5@S-MAIL-1B.rijksmuseum.intra>
References: <809BE39CD64BFD4EB9036172EBCCFA31308CC5@S-MAIL-1B.rijksmuseum.intra>
Message-ID: <1312333406.2552.90.camel@zarathud>

Marcel de Rooy schreef op ma 01-08-2011 om 06:44 [+0000]:
> i think an little improvement to our current patch workflow, would be
> to just attach the patch to a bug, in bugzilla
> an automated bugzilla script could then send that new patch to the
> patches list 

It's not quite the same, but I use 'git bz' to handle this. So my
workflow is along the lines of:

*work work code code*
git commit
git bz apply HEAD (this'll work out the bug number from the commit
message)
git send-email --to=kpatches HEAD^

It does save hassle on saving files and attaching them to bugs, and so
on.

Robin.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: </pipermail/koha-devel/attachments/20110803/eded2936/attachment.pgp>

From robin at catalyst.net.nz  Wed Aug  3 03:27:10 2011
From: robin at catalyst.net.nz (Robin Sheat)
Date: Wed, 03 Aug 2011 13:27:10 +1200
Subject: [Koha-devel] Extending message queue (was: Sending orders by
 email)
In-Reply-To: <F2C8723A-C044-4EED-9754-C81134C90809@math.uni-bonn.de>
References: <20110727141103.GA24413@gumme.math.uni-bonn.de>
	<1311808432.2552.19.camel@zarathud>
	<F2C8723A-C044-4EED-9754-C81134C90809@math.uni-bonn.de>
Message-ID: <1312334830.2552.92.camel@zarathud>

Edgar Fu? schreef op di 02-08-2011 om 16:47 [+0200]:
> > it would be worth extending the message queue stuff to allow it to
> happen
> I don't see how that could be done. It looks like its whole concept is
> centred about sending messages to patrons (``borrowers''). 

Without having looking at the code, I'd have an optional email address
field in the table, and that's used instead of the borrower email
address if it's supplied.

Robin.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: </pipermail/koha-devel/attachments/20110803/8b34834b/attachment.pgp>

From kmkale at anantcorp.com  Wed Aug  3 06:17:56 2011
From: kmkale at anantcorp.com (Koustubha Kale)
Date: Wed, 3 Aug 2011 09:47:56 +0530
Subject: [Koha-devel] Kohacon11 : Apologies for missing last few meetings
Message-ID: <CAP=kTZrQE0tdeyDtJzRW+zTQ-4+t=K+=qOSppevFw71XA5FZVg@mail.gmail.com>

Hi All,
First of all please accept my apologies for missing last few meetings. I
have multiple out of station projects on hand currently, most of them in
remote areas with very very patchy mobile networks let alone good internet
connectivity.

Having said that please rest assured that preparations for Kohacon11 are
well in hand. We need more presenters if anything. So if you are planning to
attend, please consider sharing your Koha, Library or even FOSS experiences
with us. Also as per IRC discussions yesterday, we are planning to have a
couple of panel discussions in the three day schedule. If you would like to
participate in this as a panelist or have an idea of a topic for discussion
please do share with us. Chris is going to do a remote presentation on 2nd
Nov 2011 9.30am IST :) Any of you, who can't make it to Kohacon11 for
whatever reasons please consider presenting through a similar means.

I will shape up the presentation proposals we have received so far into a
rough schedule over next couple of days and circulate on the list for
comments.

We have received sponsorship from Calyx, BibLibre and KohaAloha in addition
to Bharat Grahak. Thanks Bob & Irma, Paul and Mason.

Regards,
Koustubha Kale
Anant Corporation

Contact Details :
Address  : 103, Armaan Residency, R. W Sawant Road, Nr. Golden Dyes Naka,
Thane (w),
                Maharashtra, India, Pin : 400601.
TeleFax  : +91-22-21720108, +91-22-21720109
Mobile     : +919820715876
Website  : http://www.anantcorp.com
Blog : http://www.anantcorp.com/blog/?author=2
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110803/1d994035/attachment-0001.htm>

From paul.poulain at biblibre.com  Wed Aug  3 10:30:39 2011
From: paul.poulain at biblibre.com (Paul Poulain)
Date: Wed, 03 Aug 2011 10:30:39 +0200
Subject: [Koha-devel] Proposal for Assistance with QA Testing for Koha
 3.6
In-Reply-To: <CAE2wdZw4=6Dja9FWx3uHc2uBOCoOMR6rNpuZVBp3+pPtgGucNg@mail.gmail.com>
References: <CAE2wdZw4=6Dja9FWx3uHc2uBOCoOMR6rNpuZVBp3+pPtgGucNg@mail.gmail.com>
Message-ID: <4E39072F.2090903@biblibre.com>

Le 02/08/2011 19:04, Ian Walls a ?crit :
> c) he would start with the patches that have been waiting the longest
Just FYI : I can't find how to sort reliably  by "waiting the longest".
* Sorting by bug number is approximative but wrong : a bug can be 5
years old and the patch provided 5 days ago
* Sorting by "last modification" is worst : any comment update the "last
modification" field
* I can't find a "attachment date" sorting

I think I'll use the bug number (from oldest to newest). I think it's
the less worst solution, unless someone has another suggestion...

-- 
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08


From paul.poulain at biblibre.com  Wed Aug  3 18:16:13 2011
From: paul.poulain at biblibre.com (Paul Poulain)
Date: Wed, 03 Aug 2011 18:16:13 +0200
Subject: [Koha-devel] Proposal for Assistance with QA Testing for Koha
 3.6
In-Reply-To: <CAE2wdZw4=6Dja9FWx3uHc2uBOCoOMR6rNpuZVBp3+pPtgGucNg@mail.gmail.com>
References: <CAE2wdZw4=6Dja9FWx3uHc2uBOCoOMR6rNpuZVBp3+pPtgGucNg@mail.gmail.com>
Message-ID: <4E39744D.2020408@biblibre.com>

Hello everybody,

I started the work, here is a summary of my 1st day of QA-ing :
* I worked all the day on it (except a few distractions on IRC,
colleagues, or mail). Something like 7 hours probably.
* I've QA'ed 18 bugs (over 95 waiting) : 4002, 4222, 4415, 4518, 4839,
4959, 5072, 5079, 5098, 5131, 5166, 5429, 5433, 5436, 5468, 5602, 5630, 5633
* 8 have been set "passed QA"
* 2 have been set as "failed QA" (one by owen, answering to a question I
had)
* 1 does not apply anymore (sorry tcohen :\)
* 7 are still "signed-off" = I didn't wanted to endorse the "passed QA",
either because I signed-off the patch already, or I'm not sure (i've
added a comment for Ian though, with my opinion)

I'll continue tomorrow (probably not all the day)

HTH

-- 
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08


From chrisc at catalyst.net.nz  Wed Aug  3 03:08:52 2011
From: chrisc at catalyst.net.nz (Chris Cormack)
Date: Wed, 3 Aug 2011 13:08:52 +1200
Subject: [Koha-devel] FW:  Patch format
In-Reply-To: <1312333406.2552.90.camel@zarathud>
References: <809BE39CD64BFD4EB9036172EBCCFA31308CC5@S-MAIL-1B.rijksmuseum.intra>
	<1312333406.2552.90.camel@zarathud>
Message-ID: <20110803010852.GW3364@rorohiko.wgtn.cat-it.co.nz>

* Robin Sheat (robin at catalyst.net.nz) wrote:
> Marcel de Rooy schreef op ma 01-08-2011 om 06:44 [+0000]:
> > i think an little improvement to our current patch workflow, would be
> > to just attach the patch to a bug, in bugzilla
> > an automated bugzilla script could then send that new patch to the
> > patches list 
> 
> It's not quite the same, but I use 'git bz' to handle this. So my
> workflow is along the lines of:
> 
> *work work code code*
> git commit
> git bz apply HEAD (this'll work out the bug number from the commit
> message)

git bz attach maybe?


> git send-email --to=kpatches HEAD^
> 
> It does save hassle on saving files and attaching them to bugs, and so
> on.
> 
> Robin.


-- 
Chris Cormack
Catalyst IT Ltd.
+64 4 803 2238
PO Box 11-053, Manners St, Wellington 6142, New Zealand
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: </pipermail/koha-devel/attachments/20110803/c90c93bc/attachment.pgp>

From robin at catalyst.net.nz  Thu Aug  4 02:06:00 2011
From: robin at catalyst.net.nz (Robin Sheat)
Date: Thu, 04 Aug 2011 12:06:00 +1200
Subject: [Koha-devel] FW:  Patch format
In-Reply-To: <20110803010852.GW3364@rorohiko.wgtn.cat-it.co.nz>
References: <809BE39CD64BFD4EB9036172EBCCFA31308CC5@S-MAIL-1B.rijksmuseum.intra>
	<1312333406.2552.90.camel@zarathud>
	<20110803010852.GW3364@rorohiko.wgtn.cat-it.co.nz>
Message-ID: <1312416360.2552.137.camel@zarathud>

Chris Cormack schreef op wo 03-08-2011 om 13:08 [+1200]:
> > git bz apply HEAD (this'll work out the bug number from the commit
> > message)
> 
> git bz attach maybe? 

Err yes. I make that mistake on the command line almost every time, too.

Robin.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: </pipermail/koha-devel/attachments/20110804/76e17f45/attachment.pgp>

From robin at catalyst.net.nz  Thu Aug  4 10:30:58 2011
From: robin at catalyst.net.nz (Robin Sheat)
Date: Thu, 04 Aug 2011 20:30:58 +1200
Subject: [Koha-devel] [Koha-patches] [PATCH] [SIGNED-OFF] Bug 6553 :
 Follow up adding license statements
In-Reply-To: <809BE39CD64BFD4EB9036172EBCCFA31309E3B@S-MAIL-1B.rijksmuseum.intra>
References: <809BE39CD64BFD4EB9036172EBCCFA31309E3B@S-MAIL-1B.rijksmuseum.intra>
Message-ID: <1312446658.2552.164.camel@zarathud>

A fairly pedantic note, but to aid in getting things into distros (and
just all-round doing it right), licensing headers should have the
copyright lines for the people who have contributed to them, as well as
the GPL boilerplate.

Marcel de Rooy schreef op do 04-08-2011 om 08:10 [+0000]:
> From: Chris Cormack <chrisc at catalyst.net.nz>
> 
> http://bugs.koha-community.org/show_bug.cgi?id=6653
> 
> Signed-off-by: Marcel de Rooy <m.de.rooy at rijksmuseum.nl>
> Patch only adds license text.
> ---
>  rotating_collections/addItems.pl            |   17 +++++++++++++++++
>  rotating_collections/editCollections.pl     |   15 +++++++++++++++
>  rotating_collections/rotatingCollections.pl |   17 +++++++++++++++++
>  rotating_collections/transferCollection.pl  |   17 +++++++++++++++++
>  4 files changed, 66 insertions(+), 0 deletions(-)

Robin.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: </pipermail/koha-devel/attachments/20110804/1e134854/attachment.pgp>

From chrisc at catalyst.net.nz  Thu Aug  4 10:34:26 2011
From: chrisc at catalyst.net.nz (Chris Cormack)
Date: Thu, 4 Aug 2011 20:34:26 +1200
Subject: [Koha-devel] [Koha-patches] [PATCH] [SIGNED-OFF] Bug 6553 :
 Follow up adding license statements
In-Reply-To: <1312446658.2552.164.camel@zarathud>
References: <809BE39CD64BFD4EB9036172EBCCFA31309E3B@S-MAIL-1B.rijksmuseum.intra>
	<1312446658.2552.164.camel@zarathud>
Message-ID: <20110804083426.GF3364@rorohiko.wgtn.cat-it.co.nz>

Yep, If I knew who wrote them, I would have added them.

But the license info is better than nothing

Chris


* Robin Sheat (robin at catalyst.net.nz) wrote:
> A fairly pedantic note, but to aid in getting things into distros (and
> just all-round doing it right), licensing headers should have the
> copyright lines for the people who have contributed to them, as well as
> the GPL boilerplate.
> 
> Marcel de Rooy schreef op do 04-08-2011 om 08:10 [+0000]:
> > From: Chris Cormack <chrisc at catalyst.net.nz>
> > 
> > http://bugs.koha-community.org/show_bug.cgi?id=6653
> > 
> > Signed-off-by: Marcel de Rooy <m.de.rooy at rijksmuseum.nl>
> > Patch only adds license text.
> > ---
> >  rotating_collections/addItems.pl            |   17 +++++++++++++++++
> >  rotating_collections/editCollections.pl     |   15 +++++++++++++++
> >  rotating_collections/rotatingCollections.pl |   17 +++++++++++++++++
> >  rotating_collections/transferCollection.pl  |   17 +++++++++++++++++
> >  4 files changed, 66 insertions(+), 0 deletions(-)
> 
> Robin.



> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/


-- 
Chris Cormack
Catalyst IT Ltd.
+64 4 803 2238
PO Box 11-053, Manners St, Wellington 6142, New Zealand
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: </pipermail/koha-devel/attachments/20110804/56f75688/attachment.pgp>

From M.de.Rooy at rijksmuseum.nl  Thu Aug  4 11:36:35 2011
From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy)
Date: Thu, 4 Aug 2011 09:36:35 +0000
Subject: [Koha-devel] Testing updatedatabase.pl changes
Message-ID: <809BE39CD64BFD4EB9036172EBCCFA31309EAF@S-MAIL-1B.rijksmuseum.intra>

Hi all,

In order to test such changes, I normally make an edit like:

$DBversion = "3.05.00.xxx";
if (1||C4::Context->preference("Version") < TransformToNum($DBversion)) {
    $dbh->do("UPDATE marc_subfield_structure SET kohafield = NULL WHERE tagfield = 952 AND tagsubfield = 'f' AND kohafield = 'items.coded_location_qualifier'");
    print "Upgrade to $DBversion done (remove non-existant 'items.coded_location_qualifier' column)\n";
    #SetVersion($DBversion);
}

Note the 1 in the if and the # before SetVersion. This prevents an error on the wrong comparison (string comparison is: lt) and also an XXX in my Koha testversion.

I suppose that not everybody makes such changes and therefore some updatedatabase changes are not tested well ?? (I just had one at hand while signing off.)

In patch 6536 I included the following lines to eliminate such changes for testing:

@@ -4396,6 +4408,10 @@ sub TransformToNum {
     my $version = shift;
     # remove the 3 last . to have a Perl number
     $version =~ s/(.*\..*)\.(.*)\.(.*)/$1$2$3/;
+    # three X's at the end indicate that you are testing patch with dbrev
+    # change it into 999
+    # prevents error on a < comparison between strings (should be: lt)
+    $version =~ s/XXX$/999/;
     return $version;
 }

sub SetVersion {
-    my $kohaversion = TransformToNum(shift);
+    return if $_[0]=~ /XXX$/;
+      #you are testing a patch with a db revision; do not change version
+    my $kohaversion = TransformToNum($_[0]);
     if (C4::Context->preference('Version')) {
       my $finish=$dbh->prepare("UPDATE systempreferences SET value=? WHERE variable='Version'");
       $finish->execute($kohaversion);


My question is: Does anybody object to submitting this change as a separate patch in order to facilitate db rev testing?  I think it is an advantage to leave the version as is when you are only testing the db rev.


Thanks,
Marcel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110804/189f26ba/attachment-0001.htm>

From magnus at enger.priv.no  Thu Aug  4 12:40:43 2011
From: magnus at enger.priv.no (Magnus Enger)
Date: Thu, 4 Aug 2011 12:40:43 +0200
Subject: [Koha-devel] Global Bugs Squashing Day #3
Message-ID: <CABg6UYG1=tuc14i-OeiN0MTJRWTMD-5W1eYJ5BiNxOPTNW1_6g@mail.gmail.com>

Dear Community,

Just a gentle reminder that in Kiribati it's now August 5th, and time
for GBSD#3:
http://wiki.koha-community.org/wiki/2011-08-05_Global_bug_squashing_day

Not sure what to do? Get on the IRC channel and someone will most
likely point you in the right direction!
http://koha-community.org/get-involved/irc/

And remember: You don't have to be a programmer to help!

Want to add even more fun to the mix? Why not join "The Brave
Adventurers of Koha" and earn "Experience Points" for your efforts?
http://www.chorewars.com/party.php?name=Koha
Again, get on the IRC channel and ask about how to get in there.

Happy hunting!
Magnus Enger

From paul.poulain at biblibre.com  Fri Aug  5 10:12:49 2011
From: paul.poulain at biblibre.com (Paul Poulain)
Date: Fri, 05 Aug 2011 10:12:49 +0200
Subject: [Koha-devel] Removing sysprefs from language related installer ?
Message-ID: <4E3BA601.2040906@biblibre.com>

Hello koha-devel,

Since Koha 3.4, the text displayed for the sysprefs is stored in .pref
file. It means the sysprefs are no more "language dependant".
One of the pain one face when a syspref must be added into Koha is that
each language file must be updated, and there are now many (welcome to
the new ES one !)
It also means that is someone forget to add a syspref into a language,
then this language will have incomplete syspref in the DB when installed.

Here is what I propose:
* remove all syspref SQL files from language
(installer/data/mysql/LANGUAGE/mandatory/syspref.sql -or similar name-)
* insert them in the kohastructure.sql

The syspref is an absolute "must have" to have Koha working, so I think
it's correct to have them in the kohastructure.sql

If no-one object, i'm willing to write the patch for that. ( Please
confirm i'm not forgetting something ! )

-- 
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08


From paul.poulain at biblibre.com  Fri Aug  5 10:23:25 2011
From: paul.poulain at biblibre.com (Paul Poulain)
Date: Fri, 05 Aug 2011 10:23:25 +0200
Subject: [Koha-devel] Removing sysprefs from language related installer ?
In-Reply-To: <4E3BA601.2040906@biblibre.com>
References: <4E3BA601.2040906@biblibre.com>
Message-ID: <4E3BA87D.3060903@biblibre.com>

Le 05/08/2011 10:12, Paul Poulain a ?crit :
> Hello koha-devel,
OK, magnus pointed he already has suggested something like me, even a
little bit better, as he also suggested to let transated sysprefs as
UPDATED to have local values (for BorrowersTitle for example)

I endorse but 6537 !

-- 
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08


From David.W.Hartman at disney.com  Fri Aug  5 13:29:45 2011
From: David.W.Hartman at disney.com (Hartman, David W. - GBTS Library)
Date: Fri, 5 Aug 2011 07:29:45 -0400
Subject: [Koha-devel] Is there any way to delete recently added patrons?
Message-ID: <3E19441498923443B9DBE2FE1C0E70B60443E69891@SM-FLOR-VXMB04B.wdw.disney.com>

I made a mistake on a recent import of patrons that affected hundreds of records .. It looks like recently added patrons cannot be deleted .. So .. Can I delete the entire contents of the data file and start over with csv import.  How can this be done?

David W. Hartman
Global Business Technology Strategy Library
Team Disney 336N
407 828 4250 (8-222)
FAX 407 828 4868


-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110805/fd1e1d97/attachment.htm>

From David.W.Hartman at disney.com  Fri Aug  5 23:40:49 2011
From: David.W.Hartman at disney.com (Hartman, David W. - GBTS Library)
Date: Fri, 5 Aug 2011 17:40:49 -0400
Subject: [Koha-devel] One final question ... mapping holdings .... 4
	holdings??
Message-ID: <3E19441498923443B9DBE2FE1C0E70B60443E698CA@SM-FLOR-VXMB04B.wdw.disney.com>


  I am almost there .. I read online to use these mappings for local holdings (using MARCEDIT)  .... when I do I get 4 holdings (see below)

Barcode is mapped to 952$p
Call number 952$o
Item Type Code 952$y
Location (branch) code 952$b


From: David Hartman [mailto:hartmad at hotmail.com]
Sent: Friday, August 05, 2011 5:27 PM
To: Hartman, David W. - GBTS Library
Subject: 4 holdings??

JUnit in action
by Tahchiev, Peter</cgi-bin/koha/opac-search.pl?q=au:Tahchiev,%20Peter%20>
Series: . 1Physical details: xxiv, 360 p. : ill. ; 24 cm.Subject(s): 1. JAVA (COMPUTER PROGRAM LANGUAGE)</cgi-bin/koha/opac-search.pl?q=su:1.%20JAVA%20COMPUTER%20PROGRAM%20LANGUAGE> | 2. OBJECT-ORIENTED PROGRAMMING (COMPUTER SCIENCE )</cgi-bin/koha/opac-search.pl?q=su:2.%20OBJECT-ORIENTED%20PROGRAMMING%20COMPUTER%20SCIENCE%20>Year: 2011
Tags from this library:
No tags from this library for this title.
*         Holdings ( 4 )</cgi-bin/koha/opac-detail.pl?biblionumber=12601#holdings>
*         Title Notes</cgi-bin/koha/opac-detail.pl?biblionumber=12601#descriptions>
*         Comments ( 0 )</cgi-bin/koha/opac-detail.pl?biblionumber=12601#comments>
Item type

Location

Call Number

Status

Date Due


BT Library - FL

Available


005.7 JAVA H18 (Browse Shelf</cgi-bin/koha/opac-detail.pl?biblionumber=12601&shelfbrowse_itemnumber=37513#shelfbrowser>)

Available


Available

[/opac-tmpl/prog/itemtypeimg/bridge/book.gif] Books

Available

JUnit in action
by Tahchiev, Peter</cgi-bin/koha/opac-search.pl?q=au:Tahchiev,%20Peter%20>
Series: . 1Physical details: xxiv, 360 p. : ill. ; 24 cm.Subject(s): 1. JAVA (COMPUTER PROGRAM LANGUAGE)</cgi-bin/koha/opac-search.pl?q=su:1.%20JAVA%20COMPUTER%20PROGRAM%20LANGUAGE> | 2. OBJECT-ORIENTED PROGRAMMING (COMPUTER SCIENCE )</cgi-bin/koha/opac-search.pl?q=su:2.%20OBJECT-ORIENTED%20PROGRAMMING%20COMPUTER%20SCIENCE%20>Year: 2011
Tags from this library:
No tags from this library for this title.
*         Holdings ( 4 )</cgi-bin/koha/opac-detail.pl?biblionumber=12601#holdings>
*         Title Notes</cgi-bin/koha/opac-detail.pl?biblionumber=12601#descriptions>
*         Comments ( 0 )</cgi-bin/koha/opac-detail.pl?biblionumber=12601#comments>
Item type

Location

Call Number

Status

Date Due


BT Library - FL

Available


005.7 JAVA H18 (Browse Shelf</cgi-bin/koha/opac-detail.pl?biblionumber=12601&shelfbrowse_itemnumber=37513#shelfbrowser>)

Available


Available

[/opac-tmpl/prog/itemtypeimg/bridge/book.gif] Books

Available


-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110805/ece9f77e/attachment-0001.htm>

From David.W.Hartman at disney.com  Fri Aug  5 23:41:54 2011
From: David.W.Hartman at disney.com (Hartman, David W. - GBTS Library)
Date: Fri, 5 Aug 2011 17:41:54 -0400
Subject: [Koha-devel] One final question ... mapping holdings ....
	4	holdings??
In-Reply-To: <3E19441498923443B9DBE2FE1C0E70B60443E698CA@SM-FLOR-VXMB04B.wdw.disney.com>
References: <3E19441498923443B9DBE2FE1C0E70B60443E698CA@SM-FLOR-VXMB04B.wdw.disney.com>
Message-ID: <3E19441498923443B9DBE2FE1C0E70B60443E698CB@SM-FLOR-VXMB04B.wdw.disney.com>


  I am almost there .. I read online to use these mappings for local holdings (using MARCEDIT)  .... when I do I get 4 holdings (see below).  What am I doing wrong?  There should be just one book ..

Barcode is mapped to 952$p
Call number 952$o
Item Type Code 952$y
Location (branch) code 952$b


From: David Hartman [mailto:hartmad at hotmail.com]
Sent: Friday, August 05, 2011 5:27 PM
To: Hartman, David W. - GBTS Library
Subject: 4 holdings??

JUnit in action
by Tahchiev, Peter</cgi-bin/koha/opac-search.pl?q=au:Tahchiev,%20Peter%20>
Series: . 1Physical details: xxiv, 360 p. : ill. ; 24 cm.Subject(s): 1. JAVA (COMPUTER PROGRAM LANGUAGE)</cgi-bin/koha/opac-search.pl?q=su:1.%20JAVA%20COMPUTER%20PROGRAM%20LANGUAGE> | 2. OBJECT-ORIENTED PROGRAMMING (COMPUTER SCIENCE )</cgi-bin/koha/opac-search.pl?q=su:2.%20OBJECT-ORIENTED%20PROGRAMMING%20COMPUTER%20SCIENCE%20>Year: 2011
Tags from this library:
No tags from this library for this title.
*         Holdings ( 4 )</cgi-bin/koha/opac-detail.pl?biblionumber=12601#holdings>
*         Title Notes</cgi-bin/koha/opac-detail.pl?biblionumber=12601#descriptions>
*         Comments ( 0 )</cgi-bin/koha/opac-detail.pl?biblionumber=12601#comments>
Item type

Location

Call Number

Status

Date Due


BT Library - FL

Available


005.7 JAVA H18 (Browse Shelf</cgi-bin/koha/opac-detail.pl?biblionumber=12601&shelfbrowse_itemnumber=37513#shelfbrowser>)

Available


Available

[/opac-tmpl/prog/itemtypeimg/bridge/book.gif] Books

Available

JUnit in action
by Tahchiev, Peter</cgi-bin/koha/opac-search.pl?q=au:Tahchiev,%20Peter%20>
Series: . 1Physical details: xxiv, 360 p. : ill. ; 24 cm.Subject(s): 1. JAVA (COMPUTER PROGRAM LANGUAGE)</cgi-bin/koha/opac-search.pl?q=su:1.%20JAVA%20COMPUTER%20PROGRAM%20LANGUAGE> | 2. OBJECT-ORIENTED PROGRAMMING (COMPUTER SCIENCE )</cgi-bin/koha/opac-search.pl?q=su:2.%20OBJECT-ORIENTED%20PROGRAMMING%20COMPUTER%20SCIENCE%20>Year: 2011
Tags from this library:
No tags from this library for this title.
*         Holdings ( 4 )</cgi-bin/koha/opac-detail.pl?biblionumber=12601#holdings>
*         Title Notes</cgi-bin/koha/opac-detail.pl?biblionumber=12601#descriptions>
*         Comments ( 0 )</cgi-bin/koha/opac-detail.pl?biblionumber=12601#comments>
Item type

Location

Call Number

Status

Date Due


BT Library - FL

Available


005.7 JAVA H18 (Browse Shelf</cgi-bin/koha/opac-detail.pl?biblionumber=12601&shelfbrowse_itemnumber=37513#shelfbrowser>)

Available


Available

[/opac-tmpl/prog/itemtypeimg/bridge/book.gif] Books

Available


-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110805/8923ff10/attachment-0001.htm>

From chris at bigballofwax.co.nz  Fri Aug  5 23:42:52 2011
From: chris at bigballofwax.co.nz (Chris Cormack)
Date: Sat, 6 Aug 2011 09:42:52 +1200
Subject: [Koha-devel] One final question ... mapping holdings .... 4
	holdings??
In-Reply-To: <3E19441498923443B9DBE2FE1C0E70B60443E698CA@SM-FLOR-VXMB04B.wdw.disney.com>
References: <3E19441498923443B9DBE2FE1C0E70B60443E698CA@SM-FLOR-VXMB04B.wdw.disney.com>
Message-ID: <CA+95qVQsdn6jgt5_9F7yjGzNr+DGy2DJd9Zmd5kgyGM168nHkg@mail.gmail.com>

2011/8/6 Hartman, David W. - GBTS Library <David.W.Hartman at disney.com>
>
>
>
> ? I am almost there .. I read online to use these mappings for local holdings (using MARCEDIT) ??. when I do I get 4 holdings (see below)
>
>
>
> Barcode is mapped to 952$p
>
> Call number 952$o
> Item Type Code 952$y
> Location (branch) code 952$b
>
>
And it is just one 952, with 4 subfields, not 4 different 952's right?

Chris

From chris at bigballofwax.co.nz  Fri Aug  5 23:44:14 2011
From: chris at bigballofwax.co.nz (Chris Cormack)
Date: Sat, 6 Aug 2011 09:44:14 +1200
Subject: [Koha-devel] Is there any way to delete recently added patrons?
In-Reply-To: <3E19441498923443B9DBE2FE1C0E70B60443E69891@SM-FLOR-VXMB04B.wdw.disney.com>
References: <3E19441498923443B9DBE2FE1C0E70B60443E69891@SM-FLOR-VXMB04B.wdw.disney.com>
Message-ID: <CA+95qVQsZaQY-TS+Z2yLNpjqH+_XyeeZkB8nX=hdYYwE-rcUDg@mail.gmail.com>

2011/8/5 Hartman, David W. - GBTS Library <David.W.Hartman at disney.com>:
> I made a mistake on a recent import of patrons that affected hundreds of
> records .. It looks like recently added patrons cannot be deleted .. So ..
> Can I delete the entire contents of the data file and start over with csv
> import.? How can this be done?
>

Do you have access to the database?

And do I read right you want to deleted all patrons?

If so,
delete from borrowers;

Will get rid of all of them, I would back up first :)

Chris

From David.W.Hartman at disney.com  Fri Aug  5 23:48:16 2011
From: David.W.Hartman at disney.com (Hartman, David W. - GBTS Library)
Date: Fri, 5 Aug 2011 17:48:16 -0400
Subject: [Koha-devel] One final question ... mapping holdings .... 4
 holdings??
In-Reply-To: <CA+95qVQsdn6jgt5_9F7yjGzNr+DGy2DJd9Zmd5kgyGM168nHkg@mail.gmail.com>
References: <3E19441498923443B9DBE2FE1C0E70B60443E698CA@SM-FLOR-VXMB04B.wdw.disney.com>
	<CA+95qVQsdn6jgt5_9F7yjGzNr+DGy2DJd9Zmd5kgyGM168nHkg@mail.gmail.com>
Message-ID: <3E19441498923443B9DBE2FE1C0E70B60443E698CC@SM-FLOR-VXMB04B.wdw.disney.com>

Hey Chris!

  I must be exporting them as 4 different 952 ... I am expoerting from EXCEL into Marcedit then into Koha.  I have several fields in Excel (4 for 952) - how do I group my four 952 columns into one 952 with four subfields?  

-----Original Message-----
From: Chris Cormack [mailto:chris at bigballofwax.co.nz] 
Sent: Friday, August 05, 2011 5:43 PM
To: Hartman, David W. - GBTS Library
Cc: Koha-devel at lists.koha-community.org
Subject: Re: [Koha-devel] One final question ... mapping holdings .... 4 holdings??

2011/8/6 Hartman, David W. - GBTS Library <David.W.Hartman at disney.com>
>
>
>
> ? I am almost there .. I read online to use these mappings for local holdings (using MARCEDIT) ??. when I do I get 4 holdings (see below)
>
>
>
> Barcode is mapped to 952$p
>
> Call number 952$o
> Item Type Code 952$y
> Location (branch) code 952$b
>
>
And it is just one 952, with 4 subfields, not 4 different 952's right?

Chris

From chris at bigballofwax.co.nz  Fri Aug  5 23:51:20 2011
From: chris at bigballofwax.co.nz (Chris Cormack)
Date: Sat, 6 Aug 2011 09:51:20 +1200
Subject: [Koha-devel] One final question ... mapping holdings .... 4
	holdings??
In-Reply-To: <3E19441498923443B9DBE2FE1C0E70B60443E698CC@SM-FLOR-VXMB04B.wdw.disney.com>
References: <3E19441498923443B9DBE2FE1C0E70B60443E698CA@SM-FLOR-VXMB04B.wdw.disney.com>
	<CA+95qVQsdn6jgt5_9F7yjGzNr+DGy2DJd9Zmd5kgyGM168nHkg@mail.gmail.com>
	<3E19441498923443B9DBE2FE1C0E70B60443E698CC@SM-FLOR-VXMB04B.wdw.disney.com>
Message-ID: <CA+95qVQ+CZyTYbc4kmxsVn71-dHCAufhRz6+dUAJFCsXAj5=EA@mail.gmail.com>

On 6 August 2011 09:48, Hartman, David W. - GBTS Library
<David.W.Hartman at disney.com> wrote:
> Hey Chris!
>
> ?I must be exporting them as 4 different 952 ... I am expoerting from EXCEL into Marcedit then into Koha. ?I have several fields in Excel (4 for 952) - how do I group my four 952 columns into one 952 with four subfields?
>
Yeah that would do it, hmm someone who uses MarcEdit will have to help
you with that one. We have our own scripts (in our public repo) for
creating MARC from CSV files. (We try not to use proprietary software
whereever possible).

But Im sure someone here will know how to do it with MarcEdit.

Chris

From ef at math.uni-bonn.de  Sat Aug  6 18:20:04 2011
From: ef at math.uni-bonn.de (=?iso-8859-1?Q?Edgar_Fu=DF?=)
Date: Sat, 6 Aug 2011 18:20:04 +0200
Subject: [Koha-devel] koha-patches moderation (was: Patch format)
In-Reply-To: <CA+95qVQiRGBGoFQF5ZqCLh0ZWfZ46Ng4iGue9pEO6XE3AJdY0w@mail.gmail.com>
References: <20110727141103.GA24413@gumme.math.uni-bonn.de>
	<1311808432.2552.19.camel@zarathud>
	<8113E6DC-5C86-4113-B06A-A7516EC20809@math.uni-bonn.de>
	<CA+95qVQ+uq+nz_bH4o-fVuXzW9J7cCrayHGScM7wiT6xvv9peA@mail.gmail.com>
	<0634FFC5-3822-4AF3-9B08-5F63E2769B6A@math.uni-bonn.de>
	<CA+95qVQiRGBGoFQF5ZqCLh0ZWfZ46Ng4iGue9pEO6XE3AJdY0w@mail.gmail.com>
Message-ID: <E3067F03-2F0D-429F-BD44-E9B0F1CEA67F@math.uni-bonn.de>

> However, Koha seems to be the first project I met preferring git patches git format-patch'ed git send-email'ed to a patches list. I'll try to get accustomed to that.
FWIW, I did git-end-email git-format-patch'ed versions to koha-patches, where those messages of mine are humbly awaiting moderator's approval (I'm not subscribed to that list).

From mtj at kohaaloha.com  Sun Aug  7 01:45:41 2011
From: mtj at kohaaloha.com (Mason James)
Date: Sun, 7 Aug 2011 11:45:41 +1200
Subject: [Koha-devel] koha-patches moderation (was: Patch format)
In-Reply-To: <E3067F03-2F0D-429F-BD44-E9B0F1CEA67F@math.uni-bonn.de>
References: <20110727141103.GA24413@gumme.math.uni-bonn.de>
	<1311808432.2552.19.camel@zarathud>
	<8113E6DC-5C86-4113-B06A-A7516EC20809@math.uni-bonn.de>
	<CA+95qVQ+uq+nz_bH4o-fVuXzW9J7cCrayHGScM7wiT6xvv9peA@mail.gmail.com>
	<0634FFC5-3822-4AF3-9B08-5F63E2769B6A@math.uni-bonn.de>
	<CA+95qVQiRGBGoFQF5ZqCLh0ZWfZ46Ng4iGue9pEO6XE3AJdY0w@mail.gmail.com>
	<E3067F03-2F0D-429F-BD44-E9B0F1CEA67F@math.uni-bonn.de>
Message-ID: <4AAB6698-912B-4B16-ACBE-9BB8E3F5C25A@kohaaloha.com>


On 2011-08-7, at 4:20 AM, Edgar Fu? wrote:

>> However, Koha seems to be the first project I met preferring git patches git format-patch'ed git send-email'ed to a patches list. I'll try to get accustomed to that.
> FWIW, I did git-end-email git-format-patch'ed versions to koha-patches, where those messages of mine are humbly awaiting moderator's approval (I'm not subscribed to that list).


yeah, i would definitely subscribe to to that list, before mailing that list

From ef at math.uni-bonn.de  Sun Aug  7 11:42:26 2011
From: ef at math.uni-bonn.de (=?iso-8859-1?Q?Edgar_Fu=DF?=)
Date: Sun, 7 Aug 2011 11:42:26 +0200
Subject: [Koha-devel] koha-patches moderation
In-Reply-To: <4AAB6698-912B-4B16-ACBE-9BB8E3F5C25A@kohaaloha.com>
References: <20110727141103.GA24413@gumme.math.uni-bonn.de>
	<1311808432.2552.19.camel@zarathud>
	<8113E6DC-5C86-4113-B06A-A7516EC20809@math.uni-bonn.de>
	<CA+95qVQ+uq+nz_bH4o-fVuXzW9J7cCrayHGScM7wiT6xvv9peA@mail.gmail.com>
	<0634FFC5-3822-4AF3-9B08-5F63E2769B6A@math.uni-bonn.de>
	<CA+95qVQiRGBGoFQF5ZqCLh0ZWfZ46Ng4iGue9pEO6XE3AJdY0w@mail.gmail.com>
	<E3067F03-2F0D-429F-BD44-E9B0F1CEA67F@math.uni-bonn.de>
	<4AAB6698-912B-4B16-ACBE-9BB8E3F5C25A@kohaaloha.com>
Message-ID: <B8A3D4E6-2FB6-4F75-826E-4F1D8B8BACA6@math.uni-bonn.de>

> yeah, i would definitely subscribe to to that list, before mailing that list
Do I read this correctly as ``your moderation request will never be granted'', so I can (and am expected to) re-post after subscribing without the risk of my post appearing twice?

If so, someone may consider editing the email template being sent, which reads
> Either the message will get posted to the list, or you will receive
> notification of the moderator's decision.
to something better reflecting moderator's policy.

From chrisc at catalyst.net.nz  Sun Aug  7 11:51:53 2011
From: chrisc at catalyst.net.nz (Chris Cormack)
Date: Sun, 7 Aug 2011 21:51:53 +1200
Subject: [Koha-devel] koha-patches moderation
In-Reply-To: <B8A3D4E6-2FB6-4F75-826E-4F1D8B8BACA6@math.uni-bonn.de>
References: <20110727141103.GA24413@gumme.math.uni-bonn.de>
	<1311808432.2552.19.camel@zarathud>
	<8113E6DC-5C86-4113-B06A-A7516EC20809@math.uni-bonn.de>
	<CA+95qVQ+uq+nz_bH4o-fVuXzW9J7cCrayHGScM7wiT6xvv9peA@mail.gmail.com>
	<0634FFC5-3822-4AF3-9B08-5F63E2769B6A@math.uni-bonn.de>
	<CA+95qVQiRGBGoFQF5ZqCLh0ZWfZ46Ng4iGue9pEO6XE3AJdY0w@mail.gmail.com>
	<E3067F03-2F0D-429F-BD44-E9B0F1CEA67F@math.uni-bonn.de>
	<4AAB6698-912B-4B16-ACBE-9BB8E3F5C25A@kohaaloha.com>
	<B8A3D4E6-2FB6-4F75-826E-4F1D8B8BACA6@math.uni-bonn.de>
Message-ID: <20110807095153.GR3364@rorohiko.wgtn.cat-it.co.nz>

* Edgar Fu? (ef at math.uni-bonn.de) wrote:
> > yeah, i would definitely subscribe to to that list, before mailing that list
> Do I read this correctly as ``your moderation request will never be granted'', so I can (and am expected to) re-post after subscribing without the risk of my post appearing twice?

Nope, you don't. Mason is not a moderator of the list and there is no
such policy.
> 
> If so, someone may consider editing the email template being sent, which reads
> > Either the message will get posted to the list, or you will receive
> > notification of the moderator's decision.
> to something better reflecting moderator's policy.

It reflects reality, I'm sure one of the list moderators will let it
through when they have time. You can email Biblibre if you want to
nudge them along.

Chris

-- 
Chris Cormack
Catalyst IT Ltd.
+64 4 803 2238
PO Box 11-053, Manners St, Wellington 6142, New Zealand
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: </pipermail/koha-devel/attachments/20110807/e6620270/attachment.pgp>

From ef at math.uni-bonn.de  Sun Aug  7 12:30:56 2011
From: ef at math.uni-bonn.de (=?iso-8859-1?Q?Edgar_Fu=DF?=)
Date: Sun, 7 Aug 2011 12:30:56 +0200
Subject: [Koha-devel] koha-patches
In-Reply-To: <B8A3D4E6-2FB6-4F75-826E-4F1D8B8BACA6@math.uni-bonn.de>
References: <20110727141103.GA24413@gumme.math.uni-bonn.de>
	<1311808432.2552.19.camel@zarathud>
	<8113E6DC-5C86-4113-B06A-A7516EC20809@math.uni-bonn.de>
	<CA+95qVQ+uq+nz_bH4o-fVuXzW9J7cCrayHGScM7wiT6xvv9peA@mail.gmail.com>
	<0634FFC5-3822-4AF3-9B08-5F63E2769B6A@math.uni-bonn.de>
	<CA+95qVQiRGBGoFQF5ZqCLh0ZWfZ46Ng4iGue9pEO6XE3AJdY0w@mail.gmail.com>
	<E3067F03-2F0D-429F-BD44-E9B0F1CEA67F@math.uni-bonn.de>
	<4AAB6698-912B-4B16-ACBE-9BB8E3F5C25A@kohaaloha.com>
	<B8A3D4E6-2FB6-4F75-826E-4F1D8B8BACA6@math.uni-bonn.de>
Message-ID: <F6956ADB-4FDE-4E6F-8B95-5162D75D0277@math.uni-bonn.de>

So I spent the last half hour finding out how to re-generate a patch with git, subscribed to koha-patches, re-sent my patches and will probably immediately unsubscribe again.

As I actually do read ``Welcome to the foobar mailing list'' introductory mails: Someone may want to edit the mail sent upon koha-patches subscription:

> This is the general discussion list for librarians and others
> interested in the Koha FOSS (free & open-source software) LMS/ILS
> (library management system/integrated library system) and related
> activities.
This seems copy-pasted from the description of the koha list.

> Please feel free to use this list for announcements, questions and
> discussions on relevant topics
This probably doesn't apply either.

> Emails from non-subscribers (and other emails held for review) will
> usually be sent to this list in a batch once a day.
This definitely does not apply. At least not for my understanding of ``usually''.

From chrisc at catalyst.net.nz  Sun Aug  7 12:35:01 2011
From: chrisc at catalyst.net.nz (Chris Cormack)
Date: Sun, 7 Aug 2011 22:35:01 +1200
Subject: [Koha-devel] koha-patches
In-Reply-To: <F6956ADB-4FDE-4E6F-8B95-5162D75D0277@math.uni-bonn.de>
References: <20110727141103.GA24413@gumme.math.uni-bonn.de>
	<1311808432.2552.19.camel@zarathud>
	<8113E6DC-5C86-4113-B06A-A7516EC20809@math.uni-bonn.de>
	<CA+95qVQ+uq+nz_bH4o-fVuXzW9J7cCrayHGScM7wiT6xvv9peA@mail.gmail.com>
	<0634FFC5-3822-4AF3-9B08-5F63E2769B6A@math.uni-bonn.de>
	<CA+95qVQiRGBGoFQF5ZqCLh0ZWfZ46Ng4iGue9pEO6XE3AJdY0w@mail.gmail.com>
	<E3067F03-2F0D-429F-BD44-E9B0F1CEA67F@math.uni-bonn.de>
	<4AAB6698-912B-4B16-ACBE-9BB8E3F5C25A@kohaaloha.com>
	<B8A3D4E6-2FB6-4F75-826E-4F1D8B8BACA6@math.uni-bonn.de>
	<F6956ADB-4FDE-4E6F-8B95-5162D75D0277@math.uni-bonn.de>
Message-ID: <20110807103501.GS3364@rorohiko.wgtn.cat-it.co.nz>

* Edgar Fu? (ef at math.uni-bonn.de) wrote:
> So I spent the last half hour finding out how to re-generate a patch with git, subscribed to koha-patches, re-sent my patches and will probably immediately unsubscribe again.

Why? As I just said, the moderators will let your messages through

Im unsure why you have such a hostile attitude. Maybe it is just your
email manner. 

Anyway best of luck. 

Chris

-- 
Chris Cormack
Catalyst IT Ltd.
+64 4 803 2238
PO Box 11-053, Manners St, Wellington 6142, New Zealand
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: </pipermail/koha-devel/attachments/20110807/0815df3b/attachment.pgp>

From ef at math.uni-bonn.de  Sun Aug  7 12:59:29 2011
From: ef at math.uni-bonn.de (=?iso-8859-1?Q?Edgar_Fu=DF?=)
Date: Sun, 7 Aug 2011 12:59:29 +0200
Subject: [Koha-devel] eval "use Some::Module"
Message-ID: <0C86DB2D-B988-434A-A02A-98F6B146AF36@math.uni-bonn.de>

There are several places in Koha (I blindly copied one of them myself) that do
	eval "use Some::Module"
without checking $@ afterwards.

Not being a Perl expert myself, I thought that was some clever thing I didn't understand. I lately asked my personal Perl guru about it, and he replied is was plain broken.

In fact, it leads to strange errors when sending an email to a bookseller fails.

The relevant files are
acqui/addorderiso2709.pl, acqui/basketgroup.pl and tools/inventory.pl. There is one correct use in t/db_dependent/lib/KohaTest.pm

There is also this strange use of ``eval require'':

BEGIN {
    # find Koha's Perl modules
    # test carefully before changing this
    use FindBin;
    eval { require "$FindBin::Bin/kohalib.pl" };
}

all over the place. I can't make any sense out of this.

From ef at math.uni-bonn.de  Sun Aug  7 13:07:25 2011
From: ef at math.uni-bonn.de (=?iso-8859-1?Q?Edgar_Fu=DF?=)
Date: Sun, 7 Aug 2011 13:07:25 +0200
Subject: [Koha-devel] Restricting access to acquisition baskets
In-Reply-To: <BC1E7D0D-79E3-46CE-A5E2-738F6A64B7D1@kohaaloha.com>
References: <548E26A0-4443-4AB9-B514-8FACEE57D758@math.uni-bonn.de>
	<BC1E7D0D-79E3-46CE-A5E2-738F6A64B7D1@kohaaloha.com>
Message-ID: <AF48426B-0441-4250-AEAE-89B9D5E23D3B@math.uni-bonn.de>

> hmmm, perhaps log this issue in bugzilla?
I just filed 6676 for this.

However, I was used to discussing such issues on a developer list first.

From robin at catalyst.net.nz  Sun Aug  7 13:20:33 2011
From: robin at catalyst.net.nz (Robin Sheat)
Date: Sun, 07 Aug 2011 23:20:33 +1200
Subject: [Koha-devel] eval "use Some::Module"
In-Reply-To: <0C86DB2D-B988-434A-A02A-98F6B146AF36@math.uni-bonn.de>
References: <0C86DB2D-B988-434A-A02A-98F6B146AF36@math.uni-bonn.de>
Message-ID: <201108072320.33536.robin@catalyst.net.nz>

Op zondag 7 augustus 2011 22:59:29 schreef Edgar Fu?:
> Not being a Perl expert myself, I thought that was some clever thing I
> didn't understand. I lately asked my personal Perl guru about it, and he
> replied is was plain broken.

Koha is pretty old software by some standards, and has accepted contributions 
from people with a huge range of development skills over the years. As such, 
there are a number of places where the coding styles are out of date or not in 
line with best practices. We tend to fix them as we notice them, but it'll be 
a long while before everything is modernised (and by then, "modern" will have 
probably moved on.)

-- 
Robin Sheat
Catalyst IT Ltd.
? +64 4 803 2204
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: </pipermail/koha-devel/attachments/20110807/a6bcbd3c/attachment.pgp>

From mtj at kohaaloha.com  Sun Aug  7 23:16:56 2011
From: mtj at kohaaloha.com (Mason James)
Date: Mon, 8 Aug 2011 09:16:56 +1200
Subject: [Koha-devel] koha-patches moderation
In-Reply-To: <B8A3D4E6-2FB6-4F75-826E-4F1D8B8BACA6@math.uni-bonn.de>
References: <20110727141103.GA24413@gumme.math.uni-bonn.de>
	<1311808432.2552.19.camel@zarathud>
	<8113E6DC-5C86-4113-B06A-A7516EC20809@math.uni-bonn.de>
	<CA+95qVQ+uq+nz_bH4o-fVuXzW9J7cCrayHGScM7wiT6xvv9peA@mail.gmail.com>
	<0634FFC5-3822-4AF3-9B08-5F63E2769B6A@math.uni-bonn.de>
	<CA+95qVQiRGBGoFQF5ZqCLh0ZWfZ46Ng4iGue9pEO6XE3AJdY0w@mail.gmail.com>
	<E3067F03-2F0D-429F-BD44-E9B0F1CEA67F@math.uni-bonn.de>
	<4AAB6698-912B-4B16-ACBE-9BB8E3F5C25A@kohaaloha.com>
	<B8A3D4E6-2FB6-4F75-826E-4F1D8B8BACA6@math.uni-bonn.de>
Message-ID: <0496382D-E54F-44E6-8782-8F8739F33F96@kohaaloha.com>


On 2011-08-7, at 9:42 PM, Edgar Fu? wrote:

>> yeah, i would definitely subscribe to to that list, before mailing that list
> Do I read this correctly as ``your moderation request will never be granted'', so I can (and am expected to) re-post after subscribing without the risk of my post appearing twice?


if i were you, i would subscribe to the list - then re-post your email(s) 

whats the worst that can happen?



From mtj at kohaaloha.com  Mon Aug  8 04:24:12 2011
From: mtj at kohaaloha.com (Mason James)
Date: Mon, 8 Aug 2011 14:24:12 +1200
Subject: [Koha-devel] Restricting access to acquisition baskets
In-Reply-To: <AF48426B-0441-4250-AEAE-89B9D5E23D3B@math.uni-bonn.de>
References: <548E26A0-4443-4AB9-B514-8FACEE57D758@math.uni-bonn.de>
	<BC1E7D0D-79E3-46CE-A5E2-738F6A64B7D1@kohaaloha.com>
	<AF48426B-0441-4250-AEAE-89B9D5E23D3B@math.uni-bonn.de>
Message-ID: <46E713B8-A240-4664-BFF4-942197575040@kohaaloha.com>


On 2011-08-7, at 11:07 PM, Edgar Fu? wrote:

>> hmmm, perhaps log this issue in bugzilla?
> I just filed 6676 for this.

cool, thanx for that :)

> 
> However, I was used to discussing such issues on a developer list first.

i think this was discussed on the koha-devel list, about a week ago...






From paul.poulain at biblibre.com  Mon Aug  8 10:13:24 2011
From: paul.poulain at biblibre.com (Paul Poulain)
Date: Mon, 08 Aug 2011 10:13:24 +0200
Subject: [Koha-devel] Testing updatedatabase.pl changes
In-Reply-To: <809BE39CD64BFD4EB9036172EBCCFA31309EAF@S-MAIL-1B.rijksmuseum.intra>
References: <809BE39CD64BFD4EB9036172EBCCFA31309EAF@S-MAIL-1B.rijksmuseum.intra>
Message-ID: <4E3F9AA4.2010001@biblibre.com>

Le 04/08/2011 11:36, Marcel de Rooy a ?crit :
>
> Hi all,
>
Hi Marcel,
>
> My question is: Does anybody object to submitting this change as a
> separate patch in order to facilitate db rev testing?  I think it is
> an advantage to leave the version as is when you are only testing the
> db rev. 
>
If you look at my application as RM for 3.8, you'll see that I plan to
set-up sandboxes with each ENH, to have easier testing. I was wondering
how to deal with updatedatabase and the XXX.
You've answered my question. So : I like this idea a lot !!!

OTH : there is a small risk with this, that a forgotten XXX in a release
break things a lot. How could we avoid this/limit this risk ?

Just in case: I also had another idea = when setting up the sandbox, I
could add in the staff news the result of any git command. Thus anyone
testing the sandbox will also see what is to test on the left of the
staff-homepage. Maybe we could also use this idea with this XXX stuff :
if you detect a XXX during an UPDATEDATABASE, just add a news, with some
red, saying "YIKES, i've detected a XXX during an updatedatabase. If
you're testing a developer version, then no harm. If it's a production
server, bug the developers, something has failed during version building !"

-- 
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08


From chris at bigballofwax.co.nz  Mon Aug  8 10:18:18 2011
From: chris at bigballofwax.co.nz (Chris Cormack)
Date: Mon, 8 Aug 2011 20:18:18 +1200
Subject: [Koha-devel] Testing updatedatabase.pl changes
In-Reply-To: <4E3F9AA4.2010001@biblibre.com>
References: <809BE39CD64BFD4EB9036172EBCCFA31309EAF@S-MAIL-1B.rijksmuseum.intra>
	<4E3F9AA4.2010001@biblibre.com>
Message-ID: <CA+95qVQv8BTaWMgYCkhitm2pvd9QLyzCBuiT=nAPo97qrx-2+g@mail.gmail.com>

On 8 August 2011 20:13, Paul Poulain <paul.poulain at biblibre.com> wrote:
> Le 04/08/2011 11:36, Marcel de Rooy a ?crit :
>>
>> Hi all,
>>
> Hi Marcel,
>>
>> My question is: Does anybody object to submitting this change as a
>> separate patch in order to facilitate db rev testing? ?I think it is
>> an advantage to leave the version as is when you are only testing the
>> db rev.
>>
> If you look at my application as RM for 3.8, you'll see that I plan to
> set-up sandboxes with each ENH, to have easier testing. I was wondering
> how to deal with updatedatabase and the XXX.
> You've answered my question. So : I like this idea a lot !!!
>
> OTH : there is a small risk with this, that a forgotten XXX in a release
> break things a lot. How could we avoid this/limit this risk ?
>
> Just in case: I also had another idea = when setting up the sandbox, I
> could add in the staff news the result of any git command. Thus anyone
> testing the sandbox will also see what is to test on the left of the
> staff-homepage. Maybe we could also use this idea with this XXX stuff :
> if you detect a XXX during an UPDATEDATABASE, just add a news, with some
> red, saying "YIKES, i've detected a XXX during an updatedatabase. If
> you're testing a developer version, then no harm. If it's a production
> server, bug the developers, something has failed during version building !"
>
>
Or better use the tests and jenkins and never ever release with it set to XXX

There are lots of build tests already, and every push I do to master
runs them all, which means no conflict markers make it, no deprecated
code makes it in etc. I'm sure you plan to continue that process, if
so, theres no reason a release with XXX in it would ever get made

Chris

From paul.poulain at biblibre.com  Mon Aug  8 16:19:37 2011
From: paul.poulain at biblibre.com (Paul Poulain)
Date: Mon, 08 Aug 2011 16:19:37 +0200
Subject: [Koha-devel] KohaCon11, a visa for India, but which one
Message-ID: <4E3FF079.9040709@biblibre.com>

Hi Kousthuba & al,

I think many countries are like France and need a visa to come to the
KohaCon.

What kind of visa should we request ? A tourist visa, and we don't say
we're coming to a conference ? A conference visa (can you provide the
requested invitation to the conference ?) ? a business visa (I don't
think so: it's not related to any topic for the business visa)

Thanks for your feedback.

-- 
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08


From ruth at bywatersolutions.com  Mon Aug  8 16:24:24 2011
From: ruth at bywatersolutions.com (Ruth Bavousett)
Date: Mon, 8 Aug 2011 10:24:24 -0400
Subject: [Koha-devel] KohaCon11, a visa for India, but which one
In-Reply-To: <4E3FF079.9040709@biblibre.com>
References: <4E3FF079.9040709@biblibre.com>
Message-ID: <CAOEF2+S4mQDsD6X0gYTGPJ8umi85c7KAwSAsd_s_dfJR4W0_tw@mail.gmail.com>

Paul,

Brooke has been recommending to the Americans that they get a tourist visa,
which is what I am doing.  Probably the best bet for you, too, I imagine;
it's the easiest one to get.


*D Ruth Bavousett*
Lead Migration Specialist
ByWater Solutions
Support and Consulting for Open Source Software
Headquarters: Santa Barbara, CA
Office: Bird-In-Hand, PA
Phone/Fax (888)900-8944
http://bywatersolutions.com
ruth at bywatersolutions.com



On Mon, Aug 8, 2011 at 10:19, Paul Poulain <paul.poulain at biblibre.com>wrote:

> Hi Kousthuba & al,
>
> I think many countries are like France and need a visa to come to the
> KohaCon.
>
> What kind of visa should we request ? A tourist visa, and we don't say
> we're coming to a conference ? A conference visa (can you provide the
> requested invitation to the conference ?) ? a business visa (I don't
> think so: it's not related to any topic for the business visa)
>
> Thanks for your feedback.
>
> --
> Paul POULAIN
> http://www.biblibre.com
> Expert en Logiciels Libres pour l'info-doc
> Tel : (33) 4 91 81 35 08
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110808/268aabb5/attachment.htm>

From paul.poulain at biblibre.com  Mon Aug  8 16:25:12 2011
From: paul.poulain at biblibre.com (Paul Poulain)
Date: Mon, 08 Aug 2011 16:25:12 +0200
Subject: [Koha-devel] Testing updatedatabase.pl changes
In-Reply-To: <CA+95qVQv8BTaWMgYCkhitm2pvd9QLyzCBuiT=nAPo97qrx-2+g@mail.gmail.com>
References: <809BE39CD64BFD4EB9036172EBCCFA31309EAF@S-MAIL-1B.rijksmuseum.intra>
	<4E3F9AA4.2010001@biblibre.com>
	<CA+95qVQv8BTaWMgYCkhitm2pvd9QLyzCBuiT=nAPo97qrx-2+g@mail.gmail.com>
Message-ID: <4E3FF1C8.7030507@biblibre.com>

Le 08/08/2011 10:18, Chris Cormack a ?crit :
> Or better use the tests and jenkins and never ever release with it set to XXX
Right, I forgot this option, it's the best one, no doubt. Can you take
care of it chris, or could you give me some directions to learn how to
write a jenkins test (that would be usefull anyway) ?

-- 
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08


From paul.poulain at biblibre.com  Mon Aug  8 18:45:24 2011
From: paul.poulain at biblibre.com (Paul Poulain)
Date: Mon, 08 Aug 2011 18:45:24 +0200
Subject: [Koha-devel] email_in.pl feature
Message-ID: <4E4012A4.3040603@biblibre.com>

Hello,

I see on http://www.bugzilla.org/docs/3.0/html/api/email_in.html
that there is a feature to create a bug with an email, and this script
does that.

2 questions:
* is it activated on our bugzilla ?
* how/where can I find this script and set it up on my laptop ?

A 3rd question : is there such a feature for the wiki, that would let me
create a page from an email ?



How do I want that: I have a spreadsheet of 134 improvements being
sponsored by a library and developed by BibLibre, and it would be a
nightmare to enter all of this manually on both wiki & bugzilla !

-- 
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08


From paul.poulain at biblibre.com  Mon Aug  8 19:01:22 2011
From: paul.poulain at biblibre.com (Paul Poulain)
Date: Mon, 08 Aug 2011 19:01:22 +0200
Subject: [Koha-devel] email_in.pl feature
In-Reply-To: <4E4012A4.3040603@biblibre.com>
References: <4E4012A4.3040603@biblibre.com>
Message-ID: <4E401662.1040807@biblibre.com>

Le 08/08/2011 18:45, Paul Poulain a ?crit :
> Hello,
>
> I see on http://www.bugzilla.org/docs/3.0/html/api/email_in.html
> that there is a feature to create a bug with an email, and this script
> does that.
>
> 2 questions:
> * is it activated on our bugzilla ?
> * how/where can I find this script and set it up on my laptop ?
OK, forget my question, it's irrelevent : email_in.pl is how bugzilla
deals with incoming emails.
I have to write a script to generate emails, and just sent them.

thanks jcamins for explaining on IRC.

-- 
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08


From mtj at kohaaloha.com  Mon Aug  8 23:32:39 2011
From: mtj at kohaaloha.com (Mason James)
Date: Tue, 9 Aug 2011 09:32:39 +1200
Subject: [Koha-devel] Restricting access to acquisition baskets
In-Reply-To: <548E26A0-4443-4AB9-B514-8FACEE57D758@math.uni-bonn.de>
References: <548E26A0-4443-4AB9-B514-8FACEE57D758@math.uni-bonn.de>
Message-ID: <0CA99AAD-B17A-44B9-A4F6-55F6DE6D3321@kohaaloha.com>


On 2011-08-3, at 4:12 AM, Edgar Fu? wrote:

> Currently, while booksellers.pl tries to restrict a user's ability to view baskets, that's easily circumvented simply by altering the basketno CGI parameter to, e.g. baket.pl.
> 
> I can think of three ways to close this security hole:
> 
> 1. Check permissions in every script that deals with baskets. This would probably require an addition to C4::Auth.
> 2. Randomise basket numbers.
> 3. Add a random key to each basket that must be given as a CGI parameter (in addition to basketno) in order for a script to allow access to that basket.
> 
> Please note that for my own part, I'm unaffected by this problem. I have only a single branch and allow access to all that branches' baskets anyway.
> Nevertheless, I would give implementing a fix a try if there is consensus on which way to go.


there are 3 user-permission settings to control access to acq-baskets

?  group_manage Manage orders & basketgroups
?  order_manage Manage orders & basket
?  order_receive Manage orders & basket


have you tested accessing a basket, with all 3 settings 'off'?


From chrisc at catalyst.net.nz  Mon Aug  8 23:41:01 2011
From: chrisc at catalyst.net.nz (Chris Cormack)
Date: Tue, 9 Aug 2011 09:41:01 +1200
Subject: [Koha-devel] Testing updatedatabase.pl changes
In-Reply-To: <4E3FF1C8.7030507@biblibre.com>
References: <809BE39CD64BFD4EB9036172EBCCFA31309EAF@S-MAIL-1B.rijksmuseum.intra>
	<4E3F9AA4.2010001@biblibre.com>
	<CA+95qVQv8BTaWMgYCkhitm2pvd9QLyzCBuiT=nAPo97qrx-2+g@mail.gmail.com>
	<4E3FF1C8.7030507@biblibre.com>
Message-ID: <20110808214101.GI3364@rorohiko.wgtn.cat-it.co.nz>

* Paul Poulain (paul.poulain at biblibre.com) wrote:
> Le 08/08/2011 10:18, Chris Cormack a ?crit :
> > Or better use the tests and jenkins and never ever release with it set to XXX
> Right, I forgot this option, it's the best one, no doubt. Can you take
> care of it chris, or could you give me some directions to learn how to
> write a jenkins test (that would be usefull anyway) ?
> 
Hi Paul

I have sent a patch to the mailing list, if you could sign off, ill
push it up so jenkins starts using it

Chris

-- 
Chris Cormack
Catalyst IT Ltd.
+64 4 803 2238
PO Box 11-053, Manners St, Wellington 6142, New Zealand
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: </pipermail/koha-devel/attachments/20110809/c35e5525/attachment.pgp>

From David.W.Hartman at disney.com  Tue Aug  9 00:41:24 2011
From: David.W.Hartman at disney.com (Hartman, David W. - GBTS Library)
Date: Mon, 8 Aug 2011 18:41:24 -0400
Subject: [Koha-devel] Duplicate records remain after being unstaged, cleaned
Message-ID: <3E19441498923443B9DBE2FE1C0E70B60443E6990E@SM-FLOR-VXMB04B.wdw.disney.com>

Hello!

  I added book records (all original records), then when I imported some copy 2s, I noticed errors.  I reversed the import but the duplicate records remained.  They were supposed to be copy 2s, etc. but now they are in the catalog as multiple records.  I did reverse the record import but the records have remained.  When I try to manually delete them it says the record does not exist .. yet it shows up in the catalog... any ideas how to delete these records?  Any help would be great.

David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110808/32a06993/attachment-0001.htm>

From chrisc at catalyst.net.nz  Tue Aug  9 00:46:42 2011
From: chrisc at catalyst.net.nz (Chris Cormack)
Date: Tue, 9 Aug 2011 10:46:42 +1200
Subject: [Koha-devel] Duplicate records remain after being unstaged,
 cleaned
In-Reply-To: <3E19441498923443B9DBE2FE1C0E70B60443E6990E@SM-FLOR-VXMB04B.wdw.disney.com>
References: <3E19441498923443B9DBE2FE1C0E70B60443E6990E@SM-FLOR-VXMB04B.wdw.disney.com>
Message-ID: <20110808224642.GJ3364@rorohiko.wgtn.cat-it.co.nz>

* Hartman, David W. - GBTS Library (David.W.Hartman at disney.com) wrote:
>    Hello!
> 
>     
> 
>      I added book records (all original records), then when I imported some
>    copy 2s, I noticed errors.  I reversed the import but the duplicate
>    records remained.  They were supposed to be copy 2s, etc. but now they are
>    in the catalog as multiple records.  I did reverse the record import but
>    the records have remained.  When I try to manually delete them it says the
>    record does not exist .. yet it shows up in the catalog... any ideas how
>    to delete these records?  Any help would be great.
> 
Sounds like your index is confused.

Do a full reindex with zebra, and that will sort it out for you

http://koha-community.org/documentation/faq/searching/#20  (last
question)

Hope this helps

Chris

PS are you in the Anaheim area? I see that ALA next year is going to
be there.

-- 
Chris Cormack
Catalyst IT Ltd.
+64 4 803 2238
PO Box 11-053, Manners St, Wellington 6142, New Zealand
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: </pipermail/koha-devel/attachments/20110809/e2df2a0d/attachment.pgp>

From dearden at sarsf.org  Tue Aug  9 00:51:03 2011
From: dearden at sarsf.org (Doug Dearden)
Date: Mon, 8 Aug 2011 16:51:03 -0600
Subject: [Koha-devel] Duplicate records remain after being unstaged,
	cleaned
In-Reply-To: <3E19441498923443B9DBE2FE1C0E70B60443E6990E@SM-FLOR-VXMB04B.wdw.disney.com>
References: <3E19441498923443B9DBE2FE1C0E70B60443E6990E@SM-FLOR-VXMB04B.wdw.disney.com>
Message-ID: <EB1FA927F4970C429F73A7BF63B7F9FA230DDB538D@sar-mail>

Hi David,

I'm guessing this is a zebra thing.  Try running ../misc/migration_tools/rebuild_zebra.pl -r -b -a

That should replace your zebra indexes with new ones, and fix your search results if it is a zebra thing.

Best,

Doug

From: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org] On Behalf Of Hartman, David W. - GBTS Library
Sent: Monday, August 08, 2011 4:41 PM
To: Koha-devel at lists.koha-community.org
Subject: [Koha-devel] Duplicate records remain after being unstaged, cleaned

Hello!

  I added book records (all original records), then when I imported some copy 2s, I noticed errors.  I reversed the import but the duplicate records remained.  They were supposed to be copy 2s, etc. but now they are in the catalog as multiple records.  I did reverse the record import but the records have remained.  When I try to manually delete them it says the record does not exist .. yet it shows up in the catalog... any ideas how to delete these records?  Any help would be great.

David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110808/f8304e2f/attachment.htm>

From David.W.Hartman at disney.com  Tue Aug  9 02:41:07 2011
From: David.W.Hartman at disney.com (Hartman, David W. - GBTS Library)
Date: Mon, 8 Aug 2011 20:41:07 -0400
Subject: [Koha-devel] Importing checkout records into Koha
Message-ID: <3E19441498923443B9DBE2FE1C0E70B60443E69911@SM-FLOR-VXMB04B.wdw.disney.com>

Hello,

  I have what my patrons have checked out in CSV format ....

name, then barcode .. next line -
name then barcode .. etc.

is there a way to import this quickly into Koha?   Or do I need to manually input who has what checked out .. Thanks!

David W. Hartman
Global Business Technology Strategy Library
Team Disney 336N
407 828 4250 (8-222)
FAX 407 828 4868

FOLLOW MY RESEARCH on Backlot<http://backlot.disney.com/>  &   Yammer<http://www.yammer.com/>!
Learn about our research partners in the 2011 IT Research Competency Center<http://tink.corp.disney.com/?i=ko0>
GBTS CAST can click to request AV Equipment<http://tink.corp.disney.com/?i=jbo>, Books<http://tink.corp.disney.com/?i=jbp>,  & Research<http://tink.corp.disney.com/?i=jbn>
WATCH the GBTS Library (Video) Update<http://tink.corp.disney.com/?i=2f0> !
CLICK for the GBTS VIRTUAL LIBRARY<http://tink.corp.disney.com/?i=1wn>portal site!!
"This communication is confidential, intended only for the named recipients above and may contain trade secrets or other information that is exempt from disclosure under applicable law. Any use, dissemination, distribution or copying of this communication by anyone other than the named recipients is strictly prohibited. If you have received this communication in error, please immediately notify us by calling (407) 828-4250. Thank you."
[cid:image001.gif at 01CC560B.7F6FBCC0]Please consider your environmental responsibility before printing this e-mail [cid:image001.gif at 01CC560B.7F6FBCC0]
Think Environmentality!  Reduce!  Reuse!  Recycle!


-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110808/4caab719/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 2028 bytes
Desc: image001.gif
URL: </pipermail/koha-devel/attachments/20110808/4caab719/attachment-0001.gif>

From chrisc at catalyst.net.nz  Tue Aug  9 03:06:20 2011
From: chrisc at catalyst.net.nz (Chris Cormack)
Date: Tue, 9 Aug 2011 13:06:20 +1200
Subject: [Koha-devel] Importing checkout records into Koha
In-Reply-To: <3E19441498923443B9DBE2FE1C0E70B60443E69911@SM-FLOR-VXMB04B.wdw.disney.com>
References: <3E19441498923443B9DBE2FE1C0E70B60443E69911@SM-FLOR-VXMB04B.wdw.disney.com>
Message-ID: <20110809010620.GK3364@rorohiko.wgtn.cat-it.co.nz>

* Hartman, David W. - GBTS Library (David.W.Hartman at disney.com) wrote:
>    Hello,
> 
>      I have what my patrons have checked out in CSV format ....
> 
>     
> 
>    name, then barcode .. next line -
> 
>    name then barcode .. etc.
> 
>     
> 
>    is there a way to import this quickly into Koha?   Or do I need to
>    manually input who has what checked out .. Thanks!
> 
Hi David

Does it have date_due ? And is it name, not a unique identifier? Name
is ok, as long as no 2 people have the same name :)

Chris

-- 
Chris Cormack
Catalyst IT Ltd.
+64 4 803 2238
PO Box 11-053, Manners St, Wellington 6142, New Zealand
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: </pipermail/koha-devel/attachments/20110809/e6091143/attachment.pgp>

From robin at catalyst.net.nz  Tue Aug  9 03:09:29 2011
From: robin at catalyst.net.nz (Robin Sheat)
Date: Tue, 09 Aug 2011 13:09:29 +1200
Subject: [Koha-devel] Importing checkout records into Koha
In-Reply-To: <3E19441498923443B9DBE2FE1C0E70B60443E69911@SM-FLOR-VXMB04B.wdw.disney.com>
References: <3E19441498923443B9DBE2FE1C0E70B60443E69911@SM-FLOR-VXMB04B.wdw.disney.com>
Message-ID: <1312852169.21479.62.camel@zarathud>

Hartman, David W. - GBTS Library schreef op ma 08-08-2011 om 20:41
[-0400]:
>   I have what my patrons have checked out in CSV format ?.
> 
>  
> 
> name, then barcode .. next line ? 
> 
> name then barcode .. etc.
> 
>  
> 
> is there a way to import this quickly into Koha?   Or do I need to
> manually input who has what checked out .. Thanks!

Depending on the amount you have, it might be worth scripting. You'd
have to look up the name to get the borrowernumber, and the barcode for
the itemnumber, and then insert them in.

I have a script that does something similar:
http://git.catalyst.net.nz/gw?p=koha.git;a=blob;f=import/csv/waitaki_circ.pl;h=ed6fb2b3c595c3eeb142e4904126b7c2de560885;hb=waitaki_import
unfortunately it's a bit under-documented as it's for migrating from
specific software, and I edit it each time I need to change things, but
it may get you somewhere.

-- 
Robin Sheat
Catalyst IT Ltd.
? +64 4 803 2204
GPG: 5957 6D23 8B16 EFAB FEF8  7175 14D3 6485 A99C EB6D
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: </pipermail/koha-devel/attachments/20110809/7e657db1/attachment.pgp>

From David.W.Hartman at disney.com  Tue Aug  9 03:41:44 2011
From: David.W.Hartman at disney.com (Hartman, David W. - GBTS Library)
Date: Mon, 8 Aug 2011 21:41:44 -0400
Subject: [Koha-devel] Importing checkout records into Koha
In-Reply-To: <20110809010620.GK3364@rorohiko.wgtn.cat-it.co.nz>
References: <3E19441498923443B9DBE2FE1C0E70B60443E69911@SM-FLOR-VXMB04B.wdw.disney.com>
	<20110809010620.GK3364@rorohiko.wgtn.cat-it.co.nz>
Message-ID: <17E89776-071A-47FE-A67F-F68F2EC10B24@email.disney.com>

Yes, due date is provided and name - names are unique! :)

Sent from my iPhone! Pardon typos, etc.


On Aug 8, 2011, at 9:06 PM, "Chris Cormack" <chrisc at catalyst.net.nz> wrote:

> * Hartman, David W. - GBTS Library (David.W.Hartman at disney.com) wrote:
>>   Hello,
>> 
>>     I have what my patrons have checked out in CSV format ....
>> 
>> 
>> 
>>   name, then barcode .. next line -
>> 
>>   name then barcode .. etc.
>> 
>> 
>> 
>>   is there a way to import this quickly into Koha?   Or do I need to
>>   manually input who has what checked out .. Thanks!
>> 
> Hi David
> 
> Does it have date_due ? And is it name, not a unique identifier? Name
> is ok, as long as no 2 people have the same name :)
> 
> Chris
> 
> -- 
> Chris Cormack
> Catalyst IT Ltd.
> +64 4 803 2238
> PO Box 11-053, Manners St, Wellington 6142, New Zealand

From chrisc at catalyst.net.nz  Tue Aug  9 03:47:09 2011
From: chrisc at catalyst.net.nz (Chris Cormack)
Date: Tue, 9 Aug 2011 13:47:09 +1200
Subject: [Koha-devel] Importing checkout records into Koha
In-Reply-To: <17E89776-071A-47FE-A67F-F68F2EC10B24@email.disney.com>
References: <3E19441498923443B9DBE2FE1C0E70B60443E69911@SM-FLOR-VXMB04B.wdw.disney.com>
	<20110809010620.GK3364@rorohiko.wgtn.cat-it.co.nz>
	<17E89776-071A-47FE-A67F-F68F2EC10B24@email.disney.com>
Message-ID: <20110809014709.GL3364@rorohiko.wgtn.cat-it.co.nz>

* Hartman, David W. - GBTS Library (David.W.Hartman at disney.com) wrote:
> Yes, due date is provided and name - names are unique! :)
> 
Right, then a script like Robin's is probably the way to go.

Do you have perl skills (or someone on staff) who can help you out
with that? If not, hope on IRC sometime and we can talk you through
making the changes

Chris

-- 
Chris Cormack
Catalyst IT Ltd.
+64 4 803 2238
PO Box 11-053, Manners St, Wellington 6142, New Zealand
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: </pipermail/koha-devel/attachments/20110809/f08cdb38/attachment.pgp>

From magnus at enger.priv.no  Tue Aug  9 09:13:28 2011
From: magnus at enger.priv.no (Magnus Enger)
Date: Tue, 9 Aug 2011 09:13:28 +0200
Subject: [Koha-devel] Importing checkout records into Koha
In-Reply-To: <20110809014709.GL3364@rorohiko.wgtn.cat-it.co.nz>
References: <3E19441498923443B9DBE2FE1C0E70B60443E69911@SM-FLOR-VXMB04B.wdw.disney.com>
	<20110809010620.GK3364@rorohiko.wgtn.cat-it.co.nz>
	<17E89776-071A-47FE-A67F-F68F2EC10B24@email.disney.com>
	<20110809014709.GL3364@rorohiko.wgtn.cat-it.co.nz>
Message-ID: <CABg6UYGUw9CK4JCofxFVuYpyZ4sHaHbXdaC91-UJkQT_-YX+jw@mail.gmail.com>

2011/8/9 Chris Cormack <chrisc at catalyst.net.nz>:
> * Hartman, David W. - GBTS Library (David.W.Hartman at disney.com) wrote:
>> Yes, due date is provided and name - names are unique! :)
>>
> Right, then a script like Robin's is probably the way to go.

Here is my script for doing something similar:
https://github.com/MagnusEnger/LibrioTools/blob/master/tidem/loans.pl
Again, this is tailored to one specific system/situation (where the
data about current checkouts was in HTML format!), but it might give
some hints...

What I did was create a .koc-file with my script, which I could then
import using Home ? Circulation ? Offline Circulation File Upload. I
figured that would reduce the risk of putting data in the wrong place
or missing some field in some table that should have data in it...

The format of the .koc file is documented here:
http://wiki.koha-community.org/wiki/Koha_offline_circulation_file_format

Best regards,
Magnus Enger
libriotech.no

From ef at math.uni-bonn.de  Tue Aug  9 11:48:31 2011
From: ef at math.uni-bonn.de (=?iso-8859-1?Q?Edgar_Fu=DF?=)
Date: Tue, 9 Aug 2011 11:48:31 +0200
Subject: [Koha-devel] Restricting access to acquisition baskets
In-Reply-To: <0CA99AAD-B17A-44B9-A4F6-55F6DE6D3321@kohaaloha.com>
References: <548E26A0-4443-4AB9-B514-8FACEE57D758@math.uni-bonn.de>
	<0CA99AAD-B17A-44B9-A4F6-55F6DE6D3321@kohaaloha.com>
Message-ID: <5ADF47F5-1B9C-48CC-8EF8-E6F9E27F55D8@math.uni-bonn.de>

> have you tested accessing a basket, with all 3 settings 'off'?
No, of course I haven't. The other member of staff surely ought to have one of these permissions.

I'm talking about having two members of staff (let's call them A and B) which both have been granted the rights to handle acquisitions.
You may further imagine A and B working at different branches. You probably don't want one branches' staff to access another branches' acquisitions.
Now A creates an order, say that's basket number 42. In acqui/booksellers.pl, there is code to prevent B from being shown basket 42 (currently, that code is broken, but that's another issue).
But B can simply click on one of his own baskets (say 41), and in the URL being redirected to, edit ``basketno=41'' to ``basketno=42''. Voila, he can access A's basket he's supposedly not to do.

From m091225347 at yahoo.com  Tue Aug  9 12:28:24 2011
From: m091225347 at yahoo.com (Sangduen Pongput)
Date: Tue, 9 Aug 2011 03:28:24 -0700 (PDT)
Subject: [Koha-devel] cannot to configure/install Koha via the Admin Page
	and cannot open Client Page
Message-ID: <1312885704.34535.YahooMailClassic@web114403.mail.gq1.yahoo.com>

Dear All,
I had?done as follow http://wiki.koha-community.org/wiki/Koha_on_Ubuntu with fresh ubuntu 10.10 but it cannot run Admin Page or client page . 
?
When I use?http://127.0.1.1? it show -- It works as apache run ?but it don't have anything more than apache runing 
for?? http://127.0.1.1:8080?it show cannot find virtalhost 
?
How can?I fix it.
?
Thank for?all to?help?

Best regards,? 

Sangduen Pongput????
Librarian 
The Secretariat of the Senate, Bureau of Parliamentary Studies, Library and Museum Group 
4 U-Thong Nai Road, Dusit District, Bangkok 10300 THAILAND 
Tel +662 831 9313- 4????? Mobile Phone +66 89 122 5347? Fax +662 831 9308 ?or +662 831 9314 


?
m091225347 at yahoo.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110809/abfa556a/attachment.htm>

From dearden at sarsf.org  Tue Aug  9 19:02:18 2011
From: dearden at sarsf.org (Doug Dearden)
Date: Tue, 9 Aug 2011 11:02:18 -0600
Subject: [Koha-devel] cannot to configure/install Koha via the Admin
 Page	and cannot open Client Page
In-Reply-To: <1312885704.34535.YahooMailClassic@web114403.mail.gq1.yahoo.com>
References: <1312885704.34535.YahooMailClassic@web114403.mail.gq1.yahoo.com>
Message-ID: <EB1FA927F4970C429F73A7BF63B7F9FA230DDB538F@sar-mail>

Hi Sanqduen,

I think you have a couple of issues here.  First, I think the wiki page is wrong in using 127.0.1.1 as the IP address.  That is very similar to the common localhost address, 127.0.0.1 .  Try changing to that address and restart apache - from the command line enter: "sudo apache2ctl restart".  Also, did you do the other steps at the end of the wiki page?  You need to change from the example IP address of 123.123.123.123 to a valid address for your network.  For servers the address is usually a static address assigned by the network administrator.  In some cases it might be automatically assigned and in fact that may be the default behavior.  To see what the address is from the command line enter: "sudo ifconfig".  That should list the information for the network interface.  You are looking for the "inet addr" under "eth0".

Hope that helps.

Doug

From: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org] On Behalf Of Sangduen Pongput
Sent: Tuesday, August 09, 2011 4:28 AM
To: koha-devel at lists.koha-community.org
Cc: sangduen_p at hotmail.com
Subject: [Koha-devel] cannot to configure/install Koha via the Admin Page and cannot open Client Page

Dear All,
I had done as follow http://wiki.koha-community.org/wiki/Koha_on_Ubuntu with fresh ubuntu 10.10 but it cannot run Admin Page or client page .

When I use http://127.0.1.1  it show -- It works as apache run  but it don't have anything more than apache runing
for   http://127.0.1.1:8080<http://127.0.1.1:8080/> it show cannot find virtalhost

How can I fix it.

Thank for all to help

Best regards,

Sangduen Pongput
Librarian
The Secretariat of the Senate, Bureau of Parliamentary Studies, Library and Museum Group
4 U-Thong Nai Road, Dusit District, Bangkok 10300 THAILAND
Tel +662 831 9313- 4      Mobile Phone +66 89 122 5347  Fax +662 831 9308  or +662 831 9314

m091225347 at yahoo.com<mailto:m091225347 at yahoo.com>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110809/304b7bb1/attachment.htm>

From paul.poulain at biblibre.com  Wed Aug 10 11:25:54 2011
From: paul.poulain at biblibre.com (Paul Poulain)
Date: Wed, 10 Aug 2011 11:25:54 +0200
Subject: [Koha-devel] jquery plugin
Message-ID: <4E424EA2.1020403@biblibre.com>

Hello koha-devel,

On the bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6086
Alex proposes to add a new jquery filter for tables,
picnet.table.filter.min.js (An example of the filter is here:
http://www.picnet.com.au/resources/tablefilter/demo.htm )

We already have some jquery plugins for table:
* tablesorter = let you sort table columns. Widely used in Koha.
* tablesorterPager = automatically paginate long tables. Used in admin
section of Koha, and in readingrec
* uiTableFilter = add a generic filter to tables. Used only in serials
claims if i'm not mistaking.

uiTableFilter and tablefilter achieve almost the same goal:
* uiTableFilter propose just one filter, generic, outside of the table.
You enter something, and any cell with the entered value is kept, others
are hidden
* tablefilter add a line to the table, just below column names (see the
screenshot on bug 6086) the filter can be very detailled. It handles
filters from a list, not only from an entered value.

We have options:
* those 2 plugins are not exactly the same, let's go with both (at the
price of sometimes graphic inconsistencies or difficulties to choose one
or the other plugin)
* uiTableFilter is great, the other gives us too much detail, let's
stick with uiTableFilter, don't add another table plugin !
* tablefilter is great, it's better to have a lot of details, it's
easier to understand how it works (the uiTableFilter is outside the
table, it's strange...) switch to tablefilter and remote uiTableFilter !

What do you think we should do ?
Is there an other thing we should take care of ? Anyone knowing the
killing-plugin-for-table we should use for sorting/filtering/doing
everything on table ?

Personally, I think I prefer a little bit tablefilter, I already had
some usability questions from Owen about uiTableFilter used in a
smart-rules patch we've submitted (and has not been applied yet)

Depending on the conclusion, i'll QA the 6086 differently ;-)

-- 
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08


From reedwade at gmail.com  Wed Aug 10 11:51:36 2011
From: reedwade at gmail.com (Reed Wade)
Date: Wed, 10 Aug 2011 21:51:36 +1200
Subject: [Koha-devel] jquery plugin
In-Reply-To: <4E424EA2.1020403@biblibre.com>
References: <4E424EA2.1020403@biblibre.com>
Message-ID: <CAN-W4We-jBoaMkYUqsNdGtB02aEbuv5DMR3GQp3sjogkYt3+8A@mail.gmail.com>

Have you considered--
 http://www.datatables.net/
?

I did a little investigation of jquery table plugins a few months ago
and picked that as my favourite. I ended up not using any as my data
sets were very large and I didn't want to wire in their paging
solution (even though it might have been the right thing to do after
all).

-reed



On Wed, Aug 10, 2011 at 9:25 PM, Paul Poulain <paul.poulain at biblibre.com> wrote:
> Hello koha-devel,
>
> On the bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6086
> Alex proposes to add a new jquery filter for tables,
> picnet.table.filter.min.js (An example of the filter is here:
> http://www.picnet.com.au/resources/tablefilter/demo.htm )
>
> We already have some jquery plugins for table:
> * tablesorter = let you sort table columns. Widely used in Koha.
> * tablesorterPager = automatically paginate long tables. Used in admin
> section of Koha, and in readingrec
> * uiTableFilter = add a generic filter to tables. Used only in serials
> claims if i'm not mistaking.
>
> uiTableFilter and tablefilter achieve almost the same goal:
> * uiTableFilter propose just one filter, generic, outside of the table.
> You enter something, and any cell with the entered value is kept, others
> are hidden
> * tablefilter add a line to the table, just below column names (see the
> screenshot on bug 6086) the filter can be very detailled. It handles
> filters from a list, not only from an entered value.
>
> We have options:
> * those 2 plugins are not exactly the same, let's go with both (at the
> price of sometimes graphic inconsistencies or difficulties to choose one
> or the other plugin)
> * uiTableFilter is great, the other gives us too much detail, let's
> stick with uiTableFilter, don't add another table plugin !
> * tablefilter is great, it's better to have a lot of details, it's
> easier to understand how it works (the uiTableFilter is outside the
> table, it's strange...) switch to tablefilter and remote uiTableFilter !
>
> What do you think we should do ?
> Is there an other thing we should take care of ? Anyone knowing the
> killing-plugin-for-table we should use for sorting/filtering/doing
> everything on table ?
>
> Personally, I think I prefer a little bit tablefilter, I already had
> some usability questions from Owen about uiTableFilter used in a
> smart-rules patch we've submitted (and has not been applied yet)
>
> Depending on the conclusion, i'll QA the 6086 differently ;-)
>
> --
> Paul POULAIN
> http://www.biblibre.com
> Expert en Logiciels Libres pour l'info-doc
> Tel : (33) 4 91 81 35 08
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>

From paul.poulain at biblibre.com  Wed Aug 10 12:04:53 2011
From: paul.poulain at biblibre.com (Paul Poulain)
Date: Wed, 10 Aug 2011 12:04:53 +0200
Subject: [Koha-devel] jquery plugin
In-Reply-To: <CAN-W4We-jBoaMkYUqsNdGtB02aEbuv5DMR3GQp3sjogkYt3+8A@mail.gmail.com>
References: <4E424EA2.1020403@biblibre.com>
	<CAN-W4We-jBoaMkYUqsNdGtB02aEbuv5DMR3GQp3sjogkYt3+8A@mail.gmail.com>
Message-ID: <4E4257C5.6070301@biblibre.com>

Le 10/08/2011 11:51, Reed Wade a ?crit :
> Have you considered--
>  http://www.datatables.net/
> ?
I have considered nothing, i just see there is a patch that adds a
plugin that overlap with another one, maybe it's worth taking a chair,
have a talk, and choose one ;-)

I just took a look at datatables, and it seems it could be a good
candidate to replace all existing plugins, as it does filtering, sorting
and paging !
(and it's used by openlibrary...)

-- 
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08


From cnighswonger at foundations.edu  Wed Aug 10 15:06:19 2011
From: cnighswonger at foundations.edu (Chris Nighswonger)
Date: Wed, 10 Aug 2011 09:06:19 -0400
Subject: [Koha-devel] jquery plugin
In-Reply-To: <CAN-W4We-jBoaMkYUqsNdGtB02aEbuv5DMR3GQp3sjogkYt3+8A@mail.gmail.com>
References: <4E424EA2.1020403@biblibre.com>
	<CAN-W4We-jBoaMkYUqsNdGtB02aEbuv5DMR3GQp3sjogkYt3+8A@mail.gmail.com>
Message-ID: <CAP3yOoke5FENUkJJCJkKCpYXpZbN88-9mu_p2Vaz4pHuYQ6_Pw@mail.gmail.com>

On Wed, Aug 10, 2011 at 5:51 AM, Reed Wade <reedwade at gmail.com> wrote:

> Have you considered--
>  http://www.datatables.net/
> ?
>
> I did a little investigation of jquery table plugins a few months ago
> and picked that as my favourite. I ended up not using any as my data
> sets were very large and I didn't want to wire in their paging
> solution (even though it might have been the right thing to do after
> all).
>
>
+1 for datatables from me. I did some experimental work with this in Koha
quite a while back. (Owen may remember working with me a bit on it.) It
never went anywhere because I ran out of time.

Kind Regards,
Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110810/5098377a/attachment.htm>

From oleonard at myacpl.org  Wed Aug 10 16:15:46 2011
From: oleonard at myacpl.org (Owen Leonard)
Date: Wed, 10 Aug 2011 10:15:46 -0400
Subject: [Koha-devel] jquery plugin
In-Reply-To: <4E4257C5.6070301@biblibre.com>
References: <4E424EA2.1020403@biblibre.com>
	<CAN-W4We-jBoaMkYUqsNdGtB02aEbuv5DMR3GQp3sjogkYt3+8A@mail.gmail.com>
	<4E4257C5.6070301@biblibre.com>
Message-ID: <CAO4qe2Nuv8Xn6XJ0nPkSGzOhE3cgsHA785O_So5TqUu5uK45cg@mail.gmail.com>

> I just took a look at datatables, and it seems it could be a good
> candidate to replace all existing plugins, as it does filtering, sorting
> and paging !
> (and it's used by openlibrary...)

I think the datatables plugin looks very promising, and deserves
serious evaluation. I like that it offers the functionality we need in
a single plugin rather than in 2 or 3. I think the default
configuration isn't as minimal as we want in most cases, so it's going
to add a little bit more complexity in most cases (turning off the
features we don't always need).

I'd like to do some testing. Would Alex be willing to re-implement Bug
6086 using the datatables plugin to see if it fit that bug's
requirements?

  -- Owen

-- 
Web Developer
Athens County Public Libraries
http://www.myacpl.org

From M.de.Rooy at rijksmuseum.nl  Wed Aug 10 17:02:04 2011
From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy)
Date: Wed, 10 Aug 2011 15:02:04 +0000
Subject: [Koha-devel] Testing updatedatabase.pl changes
In-Reply-To: <20110808214101.GI3364@rorohiko.wgtn.cat-it.co.nz>
References: <809BE39CD64BFD4EB9036172EBCCFA31309EAF@S-MAIL-1B.rijksmuseum.intra>
	<4E3F9AA4.2010001@biblibre.com>
	<CA+95qVQv8BTaWMgYCkhitm2pvd9QLyzCBuiT=nAPo97qrx-2+g@mail.gmail.com>
	<4E3FF1C8.7030507@biblibre.com>,
	<20110808214101.GI3364@rorohiko.wgtn.cat-it.co.nz>
Message-ID: <809BE39CD64BFD4EB9036172EBCCFA3130CC42@S-MAIL-1B.rijksmuseum.intra>

I signed this patch of Chris. But still think that my idea on handling the XXX while testing a proposed (not pushed !) patch would be useful. 
Made a Bugzilla report for it: 6700. 
Please have a look at the second patch.
________________________________________
Van: koha-devel-bounces at lists.koha-community.org [koha-devel-bounces at lists.koha-community.org] namens Chris Cormack [chrisc at catalyst.net.nz]
Verzonden: maandag 8 augustus 2011 23:41
Aan: Paul Poulain
CC: koha-devel at lists.koha-community.org
Onderwerp: Re: [Koha-devel] Testing updatedatabase.pl changes

* Paul Poulain (paul.poulain at biblibre.com) wrote:
> Le 08/08/2011 10:18, Chris Cormack a ?crit :
> > Or better use the tests and jenkins and never ever release with it set to XXX
> Right, I forgot this option, it's the best one, no doubt. Can you take
> care of it chris, or could you give me some directions to learn how to
> write a jenkins test (that would be usefull anyway) ?
>
Hi Paul

I have sent a patch to the mailing list, if you could sign off, ill
push it up so jenkins starts using it

Chris

--
Chris Cormack
Catalyst IT Ltd.
+64 4 803 2238
PO Box 11-053, Manners St, Wellington 6142, New Zealand

From paul.poulain at biblibre.com  Wed Aug 10 17:13:07 2011
From: paul.poulain at biblibre.com (Paul Poulain)
Date: Wed, 10 Aug 2011 17:13:07 +0200
Subject: [Koha-devel] Testing updatedatabase.pl changes
In-Reply-To: <809BE39CD64BFD4EB9036172EBCCFA3130CC42@S-MAIL-1B.rijksmuseum.intra>
References: <809BE39CD64BFD4EB9036172EBCCFA31309EAF@S-MAIL-1B.rijksmuseum.intra>	<4E3F9AA4.2010001@biblibre.com>	<CA+95qVQv8BTaWMgYCkhitm2pvd9QLyzCBuiT=nAPo97qrx-2+g@mail.gmail.com>	<4E3FF1C8.7030507@biblibre.com>,
	<20110808214101.GI3364@rorohiko.wgtn.cat-it.co.nz>
	<809BE39CD64BFD4EB9036172EBCCFA3130CC42@S-MAIL-1B.rijksmuseum.intra>
Message-ID: <4E42A003.1020301@biblibre.com>

Le 10/08/2011 17:02, Marcel de Rooy a ?crit :
> I signed this patch of Chris. But still think that my idea on handling the XXX while testing a proposed (not pushed !) patch would be useful. 
I signed it as well, didn't the mailing list recieve my sign-off ?

> Made a Bugzilla report for it: 6700. 
> Please have a look at the second patch.
will do, thanks for reporting.

-- 
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08


From kmkale at anantcorp.com  Thu Aug 11 05:59:19 2011
From: kmkale at anantcorp.com (Koustubha Kale)
Date: Thu, 11 Aug 2011 09:29:19 +0530
Subject: [Koha-devel] Kohacon11 : Last date of paper submission is near!!!
	Its 15th August 2011.
Message-ID: <CAP=kTZprYseYUQBN3QoUBJ_69mv2QnHB0yLLExCz7PwrG9A4MA@mail.gmail.com>

Hi All,
The last date for paper submission for Kohacon11 is very near. So all you
who are still undecided, grab the moment and commit yourself.

I propose a kohacon11 volunteers meeting on 18th August 2011 at 16.00 UTC to
discuss and decide about the papers submitted and to discuss and decide the
program schedule.

Regards,
Koustubha Kale
Anant Corporation

Contact Details :
Address  : 103, Armaan Residency, R. W Sawant Road, Nr. Golden Dyes Naka,
Thane (w),
                Maharashtra, India, Pin : 400601.
TeleFax  : +91-22-21720108, +91-22-21720109
Mobile     : +919820715876
Website  : http://www.anantcorp.com
Blog : http://www.anantcorp.com/blog/?author=2
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110811/6a5bca46/attachment.htm>

From reed at catalyst.net.nz  Mon Aug  1 23:12:51 2011
From: reed at catalyst.net.nz (Reed Wade)
Date: Tue, 2 Aug 2011 09:12:51 +1200
Subject: [Koha-devel] 64-bit versions
In-Reply-To: <CA+95qVSJw11KujPNY6gu655WtBQ-vtLMjub200vM4ht3bFwM2g@mail.gmail.com>
References: <5.2.1.1.2.20110801165323.03139010@stormy.ca>
	<CA+95qVSJw11KujPNY6gu655WtBQ-vtLMjub200vM4ht3bFwM2g@mail.gmail.com>
Message-ID: <CAN-W4WfmYkR4-tpTRsKLuWacbuPbsdWAHrTxOQEmFv=qTnTApg@mail.gmail.com>

2nding Chris, though not so much Koha specific, I've been going all 64
with server and desktop and not seeing any problems from it.

I think that era has passed.

-reed

From ian.walls at bywatersolutions.com  Fri Aug 12 14:06:56 2011
From: ian.walls at bywatersolutions.com (Ian Walls)
Date: Fri, 12 Aug 2011 08:06:56 -0400
Subject: [Koha-devel] Access URL from opac-results.tt
In-Reply-To: <4E08B37F.5050200@senylrc.org>
References: <4E08B37F.5050200@senylrc.org>
Message-ID: <CAE2wdZz8umuq7JBw5Cd+DvGVOYpP-BjxPSNyOyxjWSDbW6_dbg@mail.gmail.com>

Zachary,


What is your OPACXSLTDetailsDisplay system preference set to?  If you're
using 'normal' view, and a very early version of Koha 3.4, there was a bug
in that mode that prevented URLs from displaying properly (a template scope
issue, trivial to fix, but boy was it an important patch!).

This is the bug report:
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6497

You can see the fix here:
http://git.koha-community.org/gitweb/?p=koha.git;a=commit;h=59ac64db973b3a0f4cebd6c5933c4f78bf0dbc2e

Cheers,


-Ian

On Mon, Jun 27, 2011 at 12:44 PM, Zachary Spalding <spalding at senylrc.org>wrote:

> In koha 3.2 I used to be able to access the 856$u filed with the <!--
> TMPL_VAR NAME="url" --> variable in the opac-results.tmpl file.
>
> Can someone give me a hint on how I can access it in 3.4, in the
> opac-results.tt file?
>
> Thanks
>
> --
> Zachary Spalding
> Systems Manager
> Southeastern NY Library Resources Council
> 21 S. Elting Corners Rd
> Highland, NY 12528
>
> Phone: 845-883-9065x11
> Fax: 845-883-9483
> Email: spalding at senylrc.org
>
> ______________________________**_________________
> Koha-devel mailing list
> Koha-devel at lists.koha-**community.org<Koha-devel at lists.koha-community.org>
> http://lists.koha-community.**org/cgi-bin/mailman/listinfo/**koha-devel<http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel>
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.**org/ <http://bugs.koha-community.org/>
>



-- 
Ian Walls
Lead Development Specialist
ByWater Solutions
Phone # (888) 900-8944
http://bywatersolutions.com
ian.walls at bywatersolutions.com
Twitter: @sekjal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110812/7e0ec367/attachment.htm>

From ian.walls at bywatersolutions.com  Fri Aug 12 14:08:39 2011
From: ian.walls at bywatersolutions.com (Ian Walls)
Date: Fri, 12 Aug 2011 08:08:39 -0400
Subject: [Koha-devel] RFC: Improved book covers
In-Reply-To: <CAJ1eDOTsfazJpLyTWFLjAV+dV1aJNprAYeAx8fihp+jWsFYGVA@mail.gmail.com>
References: <CAJ1eDOTsfazJpLyTWFLjAV+dV1aJNprAYeAx8fihp+jWsFYGVA@mail.gmail.com>
Message-ID: <CAE2wdZxR_KXy7MjaAyE-3VWm4TOq_r=b54MT3rx8oJJMrAYD1A@mail.gmail.com>

Nick,


Very interesting!  I look forward to poking around in it, and seeing what
could be integrated into Koha.  Thanks for sharing!


-Ian

2011/7/25 Nicholas van Rheede van Oudtshoorn <vanoudt at gmail.com>

> Hi all,
>
> We've been avid users of Koha here at Perth Bible College for quite a few
> years now. Recently, I've done some work to improve the book cover system
> here at PBC. A lot of our records lack ISBN records (BAD library practices
> in the old library system!), and I really wanted something nicer than a
> "cover not found" image. The result (attached) is an html/css book cover
> generating system - which also locally stores covers attained from
> librarything and openlibrary, redirecting to an amazon image if no cover is
> found. Unfortunately, it's in php - since I'm more familiar with that. :(
> The kernel for the system (though it's been *heavily* modified is courtesy a
> script by Art Zemon from 2008.
>
> We also put together a newbooks display. The results can be seen on the
> landing page: http://library.pbc.wa.edu.au/ - (and there you'll see that
> even some of our "new" books don't have ISBNs! <groan>)
>
> Hoping this might be of use to someone else. Something like the html/css
> book cover system could, in my opinion, be very useful...
>
> Nick van Oudtshoorn
> Perth Bible College
>
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>



-- 
Ian Walls
Lead Development Specialist
ByWater Solutions
Phone # (888) 900-8944
http://bywatersolutions.com
ian.walls at bywatersolutions.com
Twitter: @sekjal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110812/3ca88ca3/attachment.htm>

From vanoudt at gmail.com  Fri Aug 12 14:46:16 2011
From: vanoudt at gmail.com (Nicholas van Rheede van Oudtshoorn)
Date: Fri, 12 Aug 2011 20:46:16 +0800
Subject: [Koha-devel] RFC: Improved book covers
In-Reply-To: <CAE2wdZxR_KXy7MjaAyE-3VWm4TOq_r=b54MT3rx8oJJMrAYD1A@mail.gmail.com>
References: <CAJ1eDOTsfazJpLyTWFLjAV+dV1aJNprAYeAx8fihp+jWsFYGVA@mail.gmail.com>
	<CAE2wdZxR_KXy7MjaAyE-3VWm4TOq_r=b54MT3rx8oJJMrAYD1A@mail.gmail.com>
Message-ID: <CAJ1eDOS40Jw_yebOs71mi7vz6brZwqX3z2OmPXi9mmMwojZU7g@mail.gmail.com>

Thanks Ian! If you like, I can provide an updated version (running on
3.4.2 rather than 3.2) next week when I get back to the server...

Nick

On 8/12/11, Ian Walls <ian.walls at bywatersolutions.com> wrote:
> Nick,
>
>
> Very interesting!  I look forward to poking around in it, and seeing what
> could be integrated into Koha.  Thanks for sharing!
>
>
> -Ian
>
> 2011/7/25 Nicholas van Rheede van Oudtshoorn <vanoudt at gmail.com>
>
>> Hi all,
>>
>> We've been avid users of Koha here at Perth Bible College for quite a few
>> years now. Recently, I've done some work to improve the book cover system
>> here at PBC. A lot of our records lack ISBN records (BAD library practices
>> in the old library system!), and I really wanted something nicer than a
>> "cover not found" image. The result (attached) is an html/css book cover
>> generating system - which also locally stores covers attained from
>> librarything and openlibrary, redirecting to an amazon image if no cover
>> is
>> found. Unfortunately, it's in php - since I'm more familiar with that. :(
>> The kernel for the system (though it's been *heavily* modified is courtesy
>> a
>> script by Art Zemon from 2008.
>>
>> We also put together a newbooks display. The results can be seen on the
>> landing page: http://library.pbc.wa.edu.au/ - (and there you'll see that
>> even some of our "new" books don't have ISBNs! <groan>)
>>
>> Hoping this might be of use to someone else. Something like the html/css
>> book cover system could, in my opinion, be very useful...
>>
>> Nick van Oudtshoorn
>> Perth Bible College
>>
>>
>> _______________________________________________
>> Koha-devel mailing list
>> Koha-devel at lists.koha-community.org
>> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>> website : http://www.koha-community.org/
>> git : http://git.koha-community.org/
>> bugs : http://bugs.koha-community.org/
>>
>
>
>
> --
> Ian Walls
> Lead Development Specialist
> ByWater Solutions
> Phone # (888) 900-8944
> http://bywatersolutions.com
> ian.walls at bywatersolutions.com
> Twitter: @sekjal
>

-- 
Sent from my mobile device

From cnighswonger at foundations.edu  Fri Aug 12 15:30:00 2011
From: cnighswonger at foundations.edu (Chris Nighswonger)
Date: Fri, 12 Aug 2011 09:30:00 -0400
Subject: [Koha-devel] 3.4.x Status Update
Message-ID: <CAP3yOo=ap-Z4BJWkJcmDTLaXgmQRAsT-A_AK+BZDrbqLJsnURw@mail.gmail.com>

Hi all,

We are three days away from 3.4.x entering a string freeze pending the 3.4.4
release. If you have any work you want to make it into the 3.4.4 release,
please be sure it gets committed to master before 15 Aug 2011. Also if you
know of anything in master which should be in 3.4.x but is not, please speak
up and let me know.

Kind Regards,
Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110812/77eca131/attachment.htm>

From ian.walls at bywatersolutions.com  Fri Aug 12 15:32:27 2011
From: ian.walls at bywatersolutions.com (Ian Walls)
Date: Fri, 12 Aug 2011 09:32:27 -0400
Subject: [Koha-devel] RFC: Improved book covers
In-Reply-To: <CAJ1eDOS40Jw_yebOs71mi7vz6brZwqX3z2OmPXi9mmMwojZU7g@mail.gmail.com>
References: <CAJ1eDOTsfazJpLyTWFLjAV+dV1aJNprAYeAx8fihp+jWsFYGVA@mail.gmail.com>
	<CAE2wdZxR_KXy7MjaAyE-3VWm4TOq_r=b54MT3rx8oJJMrAYD1A@mail.gmail.com>
	<CAJ1eDOS40Jw_yebOs71mi7vz6brZwqX3z2OmPXi9mmMwojZU7g@mail.gmail.com>
Message-ID: <CAE2wdZzk6faNAUsr2ekqHSsT=N3DBmcShV950sm36nUq-FKTBA@mail.gmail.com>

Nick,


That'd be great; save us from having to do some rebasing for Template
Toolkit.


-Ian

On Fri, Aug 12, 2011 at 8:46 AM, Nicholas van Rheede van Oudtshoorn <
vanoudt at gmail.com> wrote:

> Thanks Ian! If you like, I can provide an updated version (running on
> 3.4.2 rather than 3.2) next week when I get back to the server...
>
> Nick
>
> On 8/12/11, Ian Walls <ian.walls at bywatersolutions.com> wrote:
> > Nick,
> >
> >
> > Very interesting!  I look forward to poking around in it, and seeing what
> > could be integrated into Koha.  Thanks for sharing!
> >
> >
> > -Ian
> >
> > 2011/7/25 Nicholas van Rheede van Oudtshoorn <vanoudt at gmail.com>
> >
> >> Hi all,
> >>
> >> We've been avid users of Koha here at Perth Bible College for quite a
> few
> >> years now. Recently, I've done some work to improve the book cover
> system
> >> here at PBC. A lot of our records lack ISBN records (BAD library
> practices
> >> in the old library system!), and I really wanted something nicer than a
> >> "cover not found" image. The result (attached) is an html/css book cover
> >> generating system - which also locally stores covers attained from
> >> librarything and openlibrary, redirecting to an amazon image if no cover
> >> is
> >> found. Unfortunately, it's in php - since I'm more familiar with that.
> :(
> >> The kernel for the system (though it's been *heavily* modified is
> courtesy
> >> a
> >> script by Art Zemon from 2008.
> >>
> >> We also put together a newbooks display. The results can be seen on the
> >> landing page: http://library.pbc.wa.edu.au/ - (and there you'll see
> that
> >> even some of our "new" books don't have ISBNs! <groan>)
> >>
> >> Hoping this might be of use to someone else. Something like the html/css
> >> book cover system could, in my opinion, be very useful...
> >>
> >> Nick van Oudtshoorn
> >> Perth Bible College
> >>
> >>
> >> _______________________________________________
> >> Koha-devel mailing list
> >> Koha-devel at lists.koha-community.org
> >> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> >> website : http://www.koha-community.org/
> >> git : http://git.koha-community.org/
> >> bugs : http://bugs.koha-community.org/
> >>
> >
> >
> >
> > --
> > Ian Walls
> > Lead Development Specialist
> > ByWater Solutions
> > Phone # (888) 900-8944
> > http://bywatersolutions.com
> > ian.walls at bywatersolutions.com
> > Twitter: @sekjal
> >
>
> --
> Sent from my mobile device
>



-- 
Ian Walls
Lead Development Specialist
ByWater Solutions
Phone # (888) 900-8944
http://bywatersolutions.com
ian.walls at bywatersolutions.com
Twitter: @sekjal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110812/c5c2bfb1/attachment.htm>

From chris at bigballofwax.co.nz  Sun Aug 14 22:20:30 2011
From: chris at bigballofwax.co.nz (Chris Cormack)
Date: Mon, 15 Aug 2011 08:20:30 +1200
Subject: [Koha-devel] [Koha] git bz setup question
In-Reply-To: <CAC0K6VEUGUqkCODhgnHTZd96rWUAKHtA-PbBa1p-X2fCWTGfoA@mail.gmail.com>
References: <CAC0K6VEUGUqkCODhgnHTZd96rWUAKHtA-PbBa1p-X2fCWTGfoA@mail.gmail.com>
Message-ID: <CA+95qVTeKifZfdtrrM97kL-wcsccYgAZ70xcQKrfXsHgkSLdkQ@mail.gmail.com>

On 15 August 2011 08:16, Nicole Engard <nengard at gmail.com> wrote:
> I have followed the instructions on the wiki, but every time I restart
> my virtual machine I need to repeat the path line before git bz will
> work. Is there a way to have tat path figured out automatically?
>
> nengard at debian:~/kohaclone$ git bz attach -e 6716 HEAD
> git: 'bz' is not a git command. See 'git --help'.
>
> Did you mean one of these?
> ? ? ? ?am
> ? ? ? ?gc
> ? ? ? ?mv
> ? ? ? ?rm
> nengard at debian:~/kohaclone$ PATH=$PATH:/usr/sbin:/usr/bin:/usr/local/bin
> nengard at debian:~/kohaclone$ git bz attach -e 6716 HEAD
>
What is in your .bashrc, or .bash_profile

I have things like
export PATH=$PATH:/var/lib/gems/1.8/bin


You did this bit eh?

To do that edit ~/.bash_profile with your favorite editor and add
:/usr/local/bin to the path.

PATH=$PATH:/usr/sbin:/usr/bin:/usr/local/bin
export PATH

And that file definitely has that those 2 lines in it?

Chris

From nengard at gmail.com  Sun Aug 14 23:07:01 2011
From: nengard at gmail.com (Nicole Engard)
Date: Sun, 14 Aug 2011 16:07:01 -0500
Subject: [Koha-devel] [Koha] git bz setup question
In-Reply-To: <CA+95qVTeKifZfdtrrM97kL-wcsccYgAZ70xcQKrfXsHgkSLdkQ@mail.gmail.com>
References: <CAC0K6VEUGUqkCODhgnHTZd96rWUAKHtA-PbBa1p-X2fCWTGfoA@mail.gmail.com>
	<CA+95qVTeKifZfdtrrM97kL-wcsccYgAZ70xcQKrfXsHgkSLdkQ@mail.gmail.com>
Message-ID: <CAC0K6VHCXgU6RErMcFv8KMvDgt518wfxi09ht+XatOu5H3WuZA@mail.gmail.com>

Where do I find my .bashrc file?

On Sun, Aug 14, 2011 at 3:20 PM, Chris Cormack <chris at bigballofwax.co.nz> wrote:
> On 15 August 2011 08:16, Nicole Engard <nengard at gmail.com> wrote:
>> I have followed the instructions on the wiki, but every time I restart
>> my virtual machine I need to repeat the path line before git bz will
>> work. Is there a way to have tat path figured out automatically?
>>
>> nengard at debian:~/kohaclone$ git bz attach -e 6716 HEAD
>> git: 'bz' is not a git command. See 'git --help'.
>>
>> Did you mean one of these?
>> ? ? ? ?am
>> ? ? ? ?gc
>> ? ? ? ?mv
>> ? ? ? ?rm
>> nengard at debian:~/kohaclone$ PATH=$PATH:/usr/sbin:/usr/bin:/usr/local/bin
>> nengard at debian:~/kohaclone$ git bz attach -e 6716 HEAD
>>
> What is in your .bashrc, or .bash_profile
>
> I have things like
> export PATH=$PATH:/var/lib/gems/1.8/bin
>
>
> You did this bit eh?
>
> To do that edit ~/.bash_profile with your favorite editor and add
> :/usr/local/bin to the path.
>
> PATH=$PATH:/usr/sbin:/usr/bin:/usr/local/bin
> export PATH
>
> And that file definitely has that those 2 lines in it?
>
> Chris
>

From chris at bigballofwax.co.nz  Sun Aug 14 23:14:52 2011
From: chris at bigballofwax.co.nz (Chris Cormack)
Date: Mon, 15 Aug 2011 09:14:52 +1200
Subject: [Koha-devel] [Koha] git bz setup question
In-Reply-To: <CAC0K6VHCXgU6RErMcFv8KMvDgt518wfxi09ht+XatOu5H3WuZA@mail.gmail.com>
References: <CAC0K6VEUGUqkCODhgnHTZd96rWUAKHtA-PbBa1p-X2fCWTGfoA@mail.gmail.com>
	<CA+95qVTeKifZfdtrrM97kL-wcsccYgAZ70xcQKrfXsHgkSLdkQ@mail.gmail.com>
	<CAC0K6VHCXgU6RErMcFv8KMvDgt518wfxi09ht+XatOu5H3WuZA@mail.gmail.com>
Message-ID: <CA+95qVTqsTQvsUuO8X3gSf0s0Jjgwngz5vbiqDocLyA60vg80g@mail.gmail.com>

On 15 August 2011 09:07, Nicole Engard <nengard at gmail.com> wrote:
> Where do I find my .bashrc file?
>
In your home directory .. did you make those changes to the
.bash_profile already?

Chris

From cnighswonger at foundations.edu  Mon Aug 15 04:12:31 2011
From: cnighswonger at foundations.edu (Chris Nighswonger)
Date: Sun, 14 Aug 2011 22:12:31 -0400
Subject: [Koha-devel] 3.4.x String Freeze
Message-ID: <CAP3yOokae06Ziuf20asHKJyoDBPiMyyhRAuPcz-b8e=hTS4UoA@mail.gmail.com>

Ok everybody... 3.4.x is presently in a string freeze. The only string
affecting patches that will be accepted at this point are blocker and
security related bugs. Other patches will be pushed up to the release date.

Kind Regards,
Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110814/397e7acb/attachment.htm>

From kmkale at anantcorp.com  Mon Aug 15 20:11:37 2011
From: kmkale at anantcorp.com (Koustubha Kale)
Date: Mon, 15 Aug 2011 23:41:37 +0530
Subject: [Koha-devel] Kohacon11 : Last date of paper submission extended
	till August 30 2011
Message-ID: <CAP=kTZrMKKF0G5c1tcXnOtqp4aQEMhR0efH3Z5OzBCQiGCN6dA@mail.gmail.com>

Hi All,
We have extended the last date of paper submission ( which was today 15th
August ) till 30th August 2011.

Request all of you who would like to present at Kohacon111 to step forward
and submit an abstract at
http://kohacon11.vpmthane.org/ocs/index.php/k/k11/schedConf/cfp  for review.

Also request all of you whose abstracts have been accepted to hurry up and
submit the full papers / presentations..

Regards,
Koustubha Kale
Anant Corporation

Contact Details :
Address  : 103, Armaan Residency, R. W Sawant Road, Nr. Golden Dyes Naka,
Thane (w),
                Maharashtra, India, Pin : 400601.
TeleFax  : +91-22-21720108, +91-22-21720109
Mobile     : +919820715876
Website  : http://www.anantcorp.com
Blog : http://www.anantcorp.com/blog/?author=2
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110815/11802d0c/attachment.htm>

From henridamien.laurent at biblibre.com  Tue Aug 16 12:32:58 2011
From: henridamien.laurent at biblibre.com (LAURENT Henri-Damien)
Date: Tue, 16 Aug 2011 12:32:58 +0200
Subject: [Koha-devel] jquery plugin
In-Reply-To: <CAP3yOoke5FENUkJJCJkKCpYXpZbN88-9mu_p2Vaz4pHuYQ6_Pw@mail.gmail.com>
References: <4E424EA2.1020403@biblibre.com>	<CAN-W4We-jBoaMkYUqsNdGtB02aEbuv5DMR3GQp3sjogkYt3+8A@mail.gmail.com>
	<CAP3yOoke5FENUkJJCJkKCpYXpZbN88-9mu_p2Vaz4pHuYQ6_Pw@mail.gmail.com>
Message-ID: <4E4A475A.7030605@biblibre.com>

Le 10/08/2011 15:06, Chris Nighswonger a ?crit :
> On Wed, Aug 10, 2011 at 5:51 AM, Reed Wade <reedwade at gmail.com
> <mailto:reedwade at gmail.com>> wrote:
> 
>     Have you considered--
>      http://www.datatables.net/
>     ?
> 
>     I did a little investigation of jquery table plugins a few months ago
>     and picked that as my favourite. I ended up not using any as my data
>     sets were very large and I didn't want to wire in their paging
>     solution (even though it might have been the right thing to do after
>     all).
> 
> 
> +1 for datatables from me. I did some experimental work with this in
> Koha quite a while back. (Owen may remember working with me a bit on
> it.) It never went anywhere because I ran out of time.
> 
> Kind Regards,
> Chris
ahem. In fact, as far as BibLibre is concerned, picnet was a first
attempt, and uitablefilter too (because of ease of implementation and
lack of time), but limits to those latest solutions prompted us into
datatables.net which is really better.
And we now have a quick guide for Koha integration. So that patch might
be worth rewriting.
-- 
Henri-Damien LAURENT
BibLibre

From chrisc at catalyst.net.nz  Tue Aug 16 13:29:37 2011
From: chrisc at catalyst.net.nz (Chris Cormack)
Date: Tue, 16 Aug 2011 23:29:37 +1200
Subject: [Koha-devel] [Koha] Kohacon11 : Last date of paper submission
 extended till August 30 2011
In-Reply-To: <CAP=kTZrMKKF0G5c1tcXnOtqp4aQEMhR0efH3Z5OzBCQiGCN6dA@mail.gmail.com>
References: <CAP=kTZrMKKF0G5c1tcXnOtqp4aQEMhR0efH3Z5OzBCQiGCN6dA@mail.gmail.com>
Message-ID: <20110816112937.GG2886@rorohiko.wgtn.cat-it.co.nz>

* Koustubha Kale (kmkale at anantcorp.com) wrote:
>    Hi All,
>    We have extended the last date of paper submission ( which was today 15th
>    August ) till 30th August 2011.
> 
>    Request all of you who would like to present at Kohacon111 to step forward
>    and submit an abstract at
>    http://kohacon11.vpmthane.org/ocs/index.php/k/k11/schedConf/cfp  for
>    review.
> 
>    Also request all of you whose abstracts have been accepted to hurry up and
>    submit the full papers / presentations..
>     
Hi Koustubha

I don't ever write full presentations, only notes for myself.
Submitting full papers is a very academic conference type of thing to
do, this would definitely be the first Kohacon that had written papers. 

Is this a must have, or just a 'it would be nice to have' condition?

Chris
-- 
Chris Cormack
Catalyst IT Ltd.
+64 4 803 2238
PO Box 11-053, Manners St, Wellington 6142, New Zealand
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: </pipermail/koha-devel/attachments/20110816/19682269/attachment.pgp>

From savitra.sirohi at osslabs.biz  Tue Aug 16 13:38:06 2011
From: savitra.sirohi at osslabs.biz (savitra sirohi)
Date: Tue, 16 Aug 2011 17:08:06 +0530
Subject: [Koha-devel] [Koha] Kohacon11 : Last date of paper submission
 extended till August 30 2011
In-Reply-To: <20110816112937.GG2886@rorohiko.wgtn.cat-it.co.nz>
References: <CAP=kTZrMKKF0G5c1tcXnOtqp4aQEMhR0efH3Z5OzBCQiGCN6dA@mail.gmail.com>
	<20110816112937.GG2886@rorohiko.wgtn.cat-it.co.nz>
Message-ID: <CAOC8d3Chb4fQXbqyLDGnBMsTBWrVd1-a+BQbL1t6k3AYYQbuVQ@mail.gmail.com>

Koustubha,

I agree with Chris. I can send over presentations and notes for review
but writing  a "paper" would be difficult.

Thanks,
Savitra

2011/8/16 Chris Cormack <chrisc at catalyst.net.nz>:
> * Koustubha Kale (kmkale at anantcorp.com) wrote:
>> ? ?Hi All,
>> ? ?We have extended the last date of paper submission ( which was today 15th
>> ? ?August ) till 30th August 2011.
>>
>> ? ?Request all of you who would like to present at Kohacon111 to step forward
>> ? ?and submit an abstract at
>> ? ?http://kohacon11.vpmthane.org/ocs/index.php/k/k11/schedConf/cfp ?for
>> ? ?review.
>>
>> ? ?Also request all of you whose abstracts have been accepted to hurry up and
>> ? ?submit the full papers / presentations..
>>
> Hi Koustubha
>
> I don't ever write full presentations, only notes for myself.
> Submitting full papers is a very academic conference type of thing to
> do, this would definitely be the first Kohacon that had written papers.
>
> Is this a must have, or just a 'it would be nice to have' condition?
>
> Chris
> --
> Chris Cormack
> Catalyst IT Ltd.
> +64 4 803 2238
> PO Box 11-053, Manners St, Wellington 6142, New Zealand
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>

From kmkale at anantcorp.com  Tue Aug 16 14:09:10 2011
From: kmkale at anantcorp.com (Koustubha Kale)
Date: Tue, 16 Aug 2011 17:39:10 +0530
Subject: [Koha-devel] [Koha] Kohacon11 : Last date of paper submission
 extended till August 30 2011
In-Reply-To: <20110816112937.GG2886@rorohiko.wgtn.cat-it.co.nz>
References: <CAP=kTZrMKKF0G5c1tcXnOtqp4aQEMhR0efH3Z5OzBCQiGCN6dA@mail.gmail.com>
	<20110816112937.GG2886@rorohiko.wgtn.cat-it.co.nz>
Message-ID: <CAP=kTZrAF8P11dXgouDgf_ETyT6qO+K4LqZn+Nz1hzVdwysdgg@mail.gmail.com>

On Tue, Aug 16, 2011 at 4:59 PM, Chris Cormack <chrisc at catalyst.net.nz>wrote:

> * Koustubha Kale (kmkale at anantcorp.com) wrote:
> >    Hi All,
> >    We have extended the last date of paper submission ( which was today
> 15th
> >    August ) till 30th August 2011.
> >
> >    Request all of you who would like to present at Kohacon111 to step
> forward
> >    and submit an abstract at
> >    http://kohacon11.vpmthane.org/ocs/index.php/k/k11/schedConf/cfp  for
> >    review.
> >
> >    Also request all of you whose abstracts have been accepted to hurry up
> and
> >    submit the full papers / presentations..
> >
> Hi Koustubha
>
> I don't ever write full presentations, only notes for myself.
> Submitting full papers is a very academic conference type of thing to
> do, this would definitely be the first Kohacon that had written papers.
>
> Is this a must have, or just a 'it would be nice to have' condition?
>
> Chris
> --
> Chris Cormack
> Catalyst IT Ltd.
> +64 4 803 2238
> PO Box 11-053, Manners St, Wellington 6142, New Zealand
>

Hi chris,
Actually we are planning to have all the presentations / papers published as
a  Souvenir plus CD. So in order to have the same ready for handing over to
participants during the conference itself, its necessary to have the papers
/ presentations in beforehand.

Still if the community feels this is not done. Let me know and I will
discuss with VPM.


Regards,
Koustubha Kale
Anant Corporation

Contact Details :
Address  : 103, Armaan Residency, R. W Sawant Road, Nr. Golden Dyes Naka,
Thane (w),
                Maharashtra, India, Pin : 400601.
TeleFax  : +91-22-21720108, +91-22-21720109
Mobile     : +919820715876
Website  : http://www.anantcorp.com
Blog : http://www.anantcorp.com/blog/?author=2
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110816/c3233cf8/attachment.htm>

From jransom at library.org.nz  Tue Aug 16 22:58:03 2011
From: jransom at library.org.nz (Joann Ransom)
Date: Wed, 17 Aug 2011 08:58:03 +1200
Subject: [Koha-devel] [Koha] Kohacon11 : Last date of paper submission
 extended till August 30 2011
In-Reply-To: <CAP=kTZrAF8P11dXgouDgf_ETyT6qO+K4LqZn+Nz1hzVdwysdgg@mail.gmail.com>
References: <CAP=kTZrMKKF0G5c1tcXnOtqp4aQEMhR0efH3Z5OzBCQiGCN6dA@mail.gmail.com>
	<20110816112937.GG2886@rorohiko.wgtn.cat-it.co.nz>
	<CAP=kTZrAF8P11dXgouDgf_ETyT6qO+K4LqZn+Nz1hzVdwysdgg@mail.gmail.com>
Message-ID: <CANMJezyvFdMzLQZ69GgoGKqRyKuMKg0RfWBAcGxFgdYznNxRJA@mail.gmail.com>

Hi Koustubha,

I am afraid I will not have time to submit written papers for publication
either. I have booked a week of annualleave immediately prior to KohaCon11
to get it done but even then was hoping to produce just written notes and a
powerpoint. I guess the organisers at your end need to make the call on how
to proceed. I would not be at all offended to be dropped from the programme
if it won't fit your plans for written conference papers.

Cheers Jo.

2011/8/17 Koustubha Kale <kmkale at anantcorp.com>

> On Tue, Aug 16, 2011 at 4:59 PM, Chris Cormack <chrisc at catalyst.net.nz>wrote:
>
>> * Koustubha Kale (kmkale at anantcorp.com) wrote:
>> >    Hi All,
>> >    We have extended the last date of paper submission ( which was today
>> 15th
>> >    August ) till 30th August 2011.
>> >
>> >    Request all of you who would like to present at Kohacon111 to step
>> forward
>> >    and submit an abstract at
>> >    http://kohacon11.vpmthane.org/ocs/index.php/k/k11/schedConf/cfp  for
>> >    review.
>> >
>> >    Also request all of you whose abstracts have been accepted to hurry
>> up and
>> >    submit the full papers / presentations..
>> >
>> Hi Koustubha
>>
>> I don't ever write full presentations, only notes for myself.
>> Submitting full papers is a very academic conference type of thing to
>> do, this would definitely be the first Kohacon that had written papers.
>>
>> Is this a must have, or just a 'it would be nice to have' condition?
>>
>> Chris
>> --
>> Chris Cormack
>> Catalyst IT Ltd.
>> +64 4 803 2238
>> PO Box 11-053, Manners St, Wellington 6142, New Zealand
>>
>
> Hi chris,
> Actually we are planning to have all the presentations / papers published
> as a  Souvenir plus CD. So in order to have the same ready for handing over
> to participants during the conference itself, its necessary to have the
> papers / presentations in beforehand.
>
> Still if the community feels this is not done. Let me know and I will
> discuss with VPM.
>
>
> Regards,
> Koustubha Kale
> Anant Corporation
>
> Contact Details :
> Address  : 103, Armaan Residency, R. W Sawant Road, Nr. Golden Dyes Naka,
> Thane (w),
>                 Maharashtra, India, Pin : 400601.
> TeleFax  : +91-22-21720108, +91-22-21720109
> Mobile     : +919820715876
> Website  : http://www.anantcorp.com
> Blog : http://www.anantcorp.com/blog/?author=2
>
>
> _______________________________________________
> Koha mailing list  http://koha-community.org
> Koha at lists.katipo.co.nz
> http://lists.katipo.co.nz/mailman/listinfo/koha
>
>


-- 
Joann Ransom RLIANZA
Head of Libraries,
Horowhenua Library Trust.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110817/4de23c85/attachment.htm>

From kmkale at anantcorp.com  Wed Aug 17 06:11:00 2011
From: kmkale at anantcorp.com (Koustubha Kale)
Date: Wed, 17 Aug 2011 09:41:00 +0530
Subject: [Koha-devel] [Koha] Kohacon11 : Last date of paper submission
 extended till August 30 2011
In-Reply-To: <1313537874.3396.9.camel@zarathud>
References: <CAP=kTZrMKKF0G5c1tcXnOtqp4aQEMhR0efH3Z5OzBCQiGCN6dA@mail.gmail.com>
	<20110816112937.GG2886@rorohiko.wgtn.cat-it.co.nz>
	<CAP=kTZrAF8P11dXgouDgf_ETyT6qO+K4LqZn+Nz1hzVdwysdgg@mail.gmail.com>
	<CANMJezyvFdMzLQZ69GgoGKqRyKuMKg0RfWBAcGxFgdYznNxRJA@mail.gmail.com>
	<1313537874.3396.9.camel@zarathud>
Message-ID: <CAP=kTZouM4U=ZgR_LBUCRrZbzhPeMdN5BTjEq6fUbVDzM8ZXiQ@mail.gmail.com>

2011/8/17 Robin Sheat <robin at catalyst.net.nz>

> Joann Ransom schreef op wo 17-08-2011 om 08:58 [+1200]:
> > I have booked a week of annualleave immediately prior to KohaCon11 to
> > get it done but even then was hoping to produce just written notes and
> > a powerpoint.
>
> I have to agree with this. For an academic thing, I'd have research done
> and papers written long before. However, for a less formal conference,
> like Kohacon, it tends to only really take form in the month previous,
> and I'm usually chopping and changing content right up to the day
> before. And certainly not writing a full paper for it.
>
> Or, perhaps more realistically, writing slides on the plane over, where
> I can see the deadline approaching at 900kph ;)
>
> It's not a bad idea to collect slides and other resources when you can,
> and putting them up online somewhere though.
>
> --
> Robin Sheat
> Catalyst IT Ltd.
> ? +64 4 803 2204
> GPG: 5957 6D23 8B16 EFAB FEF8  7175 14D3 6485 A99C EB6D
>
> _______________________________________________
> Koha mailing list  http://koha-community.org
> Koha at lists.katipo.co.nz
> http://lists.katipo.co.nz/mailman/listinfo/koha
>
>
Hi All,
So the consensus seems to be no written papers / presentations beforehand.
Ok will discuss with VPM but I dont see a problem with that. We can always
scramble and put together a collection on CD to be distributed on the last
day.

This means we have to drop the *"Advertisements in the conference
proceedings publication"* type of sponsorship. The largest sponsor we have
Bharat Grahak had opted for back page of the same and I would hate to lose
that sponsorship.  I hope the other sponsors who had opted for
advertisements will be ok with some of the other "at the venue" options
presented here http://www.vpmthane.org/payments/kohacon11/insert_cc.asp ?


Regards,
Koustubha Kale
Anant Corporation

Contact Details :
Address  : 103, Armaan Residency, R. W Sawant Road, Nr. Golden Dyes Naka,
Thane (w),
                Maharashtra, India, Pin : 400601.
TeleFax  : +91-22-21720108, +91-22-21720109
Mobile     : +919820715876
Website  : http://www.anantcorp.com
Blog : http://www.anantcorp.com/blog/?author=2
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110817/866f5341/attachment-0001.htm>

From bob at calyx.net.au  Wed Aug 17 08:34:55 2011
From: bob at calyx.net.au (Bob Birchall)
Date: Wed, 17 Aug 2011 16:34:55 +1000
Subject: [Koha-devel] [Koha] Kohacon11 : Last date of paper submission
 extended till August 30 2011
In-Reply-To: <CAP=kTZouM4U=ZgR_LBUCRrZbzhPeMdN5BTjEq6fUbVDzM8ZXiQ@mail.gmail.com>
References: <CAP=kTZrMKKF0G5c1tcXnOtqp4aQEMhR0efH3Z5OzBCQiGCN6dA@mail.gmail.com>	<20110816112937.GG2886@rorohiko.wgtn.cat-it.co.nz>	<CAP=kTZrAF8P11dXgouDgf_ETyT6qO+K4LqZn+Nz1hzVdwysdgg@mail.gmail.com>	<CANMJezyvFdMzLQZ69GgoGKqRyKuMKg0RfWBAcGxFgdYznNxRJA@mail.gmail.com>	<1313537874.3396.9.camel@zarathud>
	<CAP=kTZouM4U=ZgR_LBUCRrZbzhPeMdN5BTjEq6fUbVDzM8ZXiQ@mail.gmail.com>
Message-ID: <4E4B610F.5020002@calyx.net.au>

On 17/08/11 14:11, Koustubha Kale wrote:
> 2011/8/17 Robin Sheat <robin at catalyst.net.nz 
> <mailto:robin at catalyst.net.nz>>
>
>     Joann Ransom schreef op wo 17-08-2011 om 08:58 [+1200]:
>     > I have booked a week of annualleave immediately prior to
>     KohaCon11 to
>     > get it done but even then was hoping to produce just written
>     notes and
>     > a powerpoint.
>
>     I have to agree with this. For an academic thing, I'd have
>     research done
>     and papers written long before. However, for a less formal conference,
>     like Kohacon, it tends to only really take form in the month previous,
>     and I'm usually chopping and changing content right up to the day
>     before. And certainly not writing a full paper for it.
>
>     Or, perhaps more realistically, writing slides on the plane over,
>     where
>     I can see the deadline approaching at 900kph ;)
>
>     It's not a bad idea to collect slides and other resources when you
>     can,
>     and putting them up online somewhere though.
>
>     --
>     Robin Sheat
>     Catalyst IT Ltd.
>     ? +64 4 803 2204
>     GPG: 5957 6D23 8B16 EFAB FEF8  7175 14D3 6485 A99C EB6D
>
>     _______________________________________________
>     Koha mailing list http://koha-community.org
>     Koha at lists.katipo.co.nz <mailto:Koha at lists.katipo.co.nz>
>     http://lists.katipo.co.nz/mailman/listinfo/koha
>
>
> Hi All,
> So the consensus seems to be no written papers / presentations 
> beforehand. Ok will discuss with VPM but I dont see a problem with 
> that. We can always scramble and put together a collection on CD to be 
> distributed on the last day.

Most contributors will at least make their slide presentations 
available.  Will there be any recording of the presentations?
>
> This means we have to drop the *"Advertisements in the conference 
> proceedings publication"* type of sponsorship. The largest sponsor we 
> have Bharat Grahak had opted for back page of the same and I would 
> hate to lose that sponsorship.  I hope the other sponsors who had 
> opted for advertisements will be ok with some of the other "at the 
> venue" options presented here 
> http://www.vpmthane.org/payments/kohacon11/insert_cc.asp ?
Koustubha,
Its fine by us.  We're happy to be supporting the conference and you can 
use our contribution as you see fit.
What I would like to see is a table or display place where we can leave 
our brochures at the conference for anyone who is interested.  There was 
a table at KohaCon10 in Wellington with an interesting array of 
information handouts.
Regards,
Bob

-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110817/68654ba7/attachment.htm>

From kmkale at anantcorp.com  Wed Aug 17 09:47:21 2011
From: kmkale at anantcorp.com (Koustubha Kale)
Date: Wed, 17 Aug 2011 13:17:21 +0530
Subject: [Koha-devel] [Koha] Kohacon11 : Last date of paper submission
 extended till August 30 2011
In-Reply-To: <4E4B610F.5020002@calyx.net.au>
References: <CAP=kTZrMKKF0G5c1tcXnOtqp4aQEMhR0efH3Z5OzBCQiGCN6dA@mail.gmail.com>
	<20110816112937.GG2886@rorohiko.wgtn.cat-it.co.nz>
	<CAP=kTZrAF8P11dXgouDgf_ETyT6qO+K4LqZn+Nz1hzVdwysdgg@mail.gmail.com>
	<CANMJezyvFdMzLQZ69GgoGKqRyKuMKg0RfWBAcGxFgdYznNxRJA@mail.gmail.com>
	<1313537874.3396.9.camel@zarathud>
	<CAP=kTZouM4U=ZgR_LBUCRrZbzhPeMdN5BTjEq6fUbVDzM8ZXiQ@mail.gmail.com>
	<4E4B610F.5020002@calyx.net.au>
Message-ID: <CAP=kTZq3tVaK=FUj_eKGkm6yqM8cNdAnUd4a4xtxarLf9RCNmw@mail.gmail.com>

2011/8/17 Bob Birchall <bob at calyx.net.au>

> **
> On 17/08/11 14:11, Koustubha Kale wrote:
>
> 2011/8/17 Robin Sheat <robin at catalyst.net.nz>
>
>> Joann Ransom schreef op wo 17-08-2011 om 08:58 [+1200]:
>> > I have booked a week of annualleave immediately prior to KohaCon11 to
>> > get it done but even then was hoping to produce just written notes and
>> > a powerpoint.
>>
>>  I have to agree with this. For an academic thing, I'd have research done
>> and papers written long before. However, for a less formal conference,
>> like Kohacon, it tends to only really take form in the month previous,
>> and I'm usually chopping and changing content right up to the day
>> before. And certainly not writing a full paper for it.
>>
>> Or, perhaps more realistically, writing slides on the plane over, where
>> I can see the deadline approaching at 900kph ;)
>>
>> It's not a bad idea to collect slides and other resources when you can,
>> and putting them up online somewhere though.
>>
>> --
>> Robin Sheat
>> Catalyst IT Ltd.
>> ? +64 4 803 2204
>> GPG: 5957 6D23 8B16 EFAB FEF8  7175 14D3 6485 A99C EB6D
>>
>> _______________________________________________
>> Koha mailing list  http://koha-community.org
>> Koha at lists.katipo.co.nz
>> http://lists.katipo.co.nz/mailman/listinfo/koha
>>
>>
> Hi All,
> So the consensus seems to be no written papers / presentations beforehand.
> Ok will discuss with VPM but I dont see a problem with that. We can always
> scramble and put together a collection on CD to be distributed on the last
> day.
>
>
> Most contributors will at least make their slide presentations available.
> Will there be any recording of the presentations?
>

Yes there will be video recording of the entire conference.


>
>
> This means we have to drop the *"Advertisements in the conference
> proceedings publication"* type of sponsorship. The largest sponsor we have
> Bharat Grahak had opted for back page of the same and I would hate to lose
> that sponsorship.  I hope the other sponsors who had opted for
> advertisements will be ok with some of the other "at the venue" options
> presented here http://www.vpmthane.org/payments/kohacon11/insert_cc.asp ?
>
> Koustubha,
> Its fine by us.  We're happy to be supporting the conference and you can
> use our contribution as you see fit.
>

Thanks Bob.


>  What I would like to see is a table or display place where we can leave
> our brochures at the conference for anyone who is interested.  There was a
> table at KohaCon10 in Wellington with an interesting array of information
> handouts.
>

Yes we can do that.


Regards,
Koustubha Kale
Anant Corporation

Contact Details :
Address  : 103, Armaan Residency, R. W Sawant Road, Nr. Golden Dyes Naka,
Thane (w),
                Maharashtra, India, Pin : 400601.
TeleFax  : +91-22-21720108, +91-22-21720109
Mobile     : +919820715876
Website  : http://www.anantcorp.com
Blog : http://www.anantcorp.com/blog/?author=2
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110817/4c3114b7/attachment.htm>

From abesottedphoenix at yahoo.com  Wed Aug 17 14:34:37 2011
From: abesottedphoenix at yahoo.com (BWS Johnson)
Date: Wed, 17 Aug 2011 05:34:37 -0700 (PDT)
Subject: [Koha-devel] [Koha] Kohacon11 : Last date of paper submission
	extended till August 30 2011
In-Reply-To: <CAP=kTZouM4U=ZgR_LBUCRrZbzhPeMdN5BTjEq6fUbVDzM8ZXiQ@mail.gmail.com>
References: <CAP=kTZrMKKF0G5c1tcXnOtqp4aQEMhR0efH3Z5OzBCQiGCN6dA@mail.gmail.com>
	<20110816112937.GG2886@rorohiko.wgtn.cat-it.co.nz>
	<CAP=kTZrAF8P11dXgouDgf_ETyT6qO+K4LqZn+Nz1hzVdwysdgg@mail.gmail.com>
	<CANMJezyvFdMzLQZ69GgoGKqRyKuMKg0RfWBAcGxFgdYznNxRJA@mail.gmail.com>
	<1313537874.3396.9.camel@zarathud>
	<CAP=kTZouM4U=ZgR_LBUCRrZbzhPeMdN5BTjEq6fUbVDzM8ZXiQ@mail.gmail.com>
Message-ID: <1313584477.58875.YahooMailNeo@web114717.mail.gq1.yahoo.com>

Kia ora!

>This means we have to drop the "Advertisements in the conference????proceedings publication" type of sponsorship. The largest sponsor we have Bharat Grahak had opted for back page of the same and I would hate to lose that sponsorship.? I hope the other sponsors who had opted for advertisements will be ok with some of the other "at the venue" options presented here http://www.vpmthane.org/payments/kohacon11/insert_cc.asp ?
>


Not necessarily. Check and see if the compromise of having a collection of abstracts with advertising would be amenable to them. My gut tells me there would be very little difference to an average person in having their advert with an abstract v. a full paper.

Cheers,
Brooke

From vanoudt at gmail.com  Thu Aug 18 09:49:55 2011
From: vanoudt at gmail.com (Nicholas van Rheede van Oudtshoorn)
Date: Thu, 18 Aug 2011 15:49:55 +0800
Subject: [Koha-devel] RFC: Improved book covers
In-Reply-To: <CAE2wdZzk6faNAUsr2ekqHSsT=N3DBmcShV950sm36nUq-FKTBA@mail.gmail.com>
References: <CAJ1eDOTsfazJpLyTWFLjAV+dV1aJNprAYeAx8fihp+jWsFYGVA@mail.gmail.com>
	<CAE2wdZxR_KXy7MjaAyE-3VWm4TOq_r=b54MT3rx8oJJMrAYD1A@mail.gmail.com>
	<CAJ1eDOS40Jw_yebOs71mi7vz6brZwqX3z2OmPXi9mmMwojZU7g@mail.gmail.com>
	<CAE2wdZzk6faNAUsr2ekqHSsT=N3DBmcShV950sm36nUq-FKTBA@mail.gmail.com>
Message-ID: <CAJ1eDOTmAXyCR2pqv_huzUti+breWngA0SOXKdnSNOG1EhJ8Tw@mail.gmail.com>

Finally managed to get access to the library system again. Please find
attached a version of the cover system rebased to Koha 3.4.2. There are
still a few places where things can be tidied up. Thinking about it, moving
the cover caching system from php to perl would give some really nice
benefits - such as pre-normalised ISBNs.. Still, my perl fu is not *that*
strong. <grin>

Any questions etc. please let me know.

Fared thee well,
Nick

On Fri, Aug 12, 2011 at 9:32 PM, Ian Walls
<ian.walls at bywatersolutions.com>wrote:

> Nick,
>
>
> That'd be great; save us from having to do some rebasing for Template
> Toolkit.
>
>
> -Ian
>
>
> On Fri, Aug 12, 2011 at 8:46 AM, Nicholas van Rheede van Oudtshoorn <
> vanoudt at gmail.com> wrote:
>
>> Thanks Ian! If you like, I can provide an updated version (running on
>> 3.4.2 rather than 3.2) next week when I get back to the server...
>>
>> Nick
>>
>> On 8/12/11, Ian Walls <ian.walls at bywatersolutions.com> wrote:
>> > Nick,
>> >
>> >
>> > Very interesting!  I look forward to poking around in it, and seeing
>> what
>> > could be integrated into Koha.  Thanks for sharing!
>> >
>> >
>> > -Ian
>> >
>> > 2011/7/25 Nicholas van Rheede van Oudtshoorn <vanoudt at gmail.com>
>> >
>> >> Hi all,
>> >>
>> >> We've been avid users of Koha here at Perth Bible College for quite a
>> few
>> >> years now. Recently, I've done some work to improve the book cover
>> system
>> >> here at PBC. A lot of our records lack ISBN records (BAD library
>> practices
>> >> in the old library system!), and I really wanted something nicer than a
>> >> "cover not found" image. The result (attached) is an html/css book
>> cover
>> >> generating system - which also locally stores covers attained from
>> >> librarything and openlibrary, redirecting to an amazon image if no
>> cover
>> >> is
>> >> found. Unfortunately, it's in php - since I'm more familiar with that.
>> :(
>> >> The kernel for the system (though it's been *heavily* modified is
>> courtesy
>> >> a
>> >> script by Art Zemon from 2008.
>> >>
>> >> We also put together a newbooks display. The results can be seen on the
>> >> landing page: http://library.pbc.wa.edu.au/ - (and there you'll see
>> that
>> >> even some of our "new" books don't have ISBNs! <groan>)
>> >>
>> >> Hoping this might be of use to someone else. Something like the
>> html/css
>> >> book cover system could, in my opinion, be very useful...
>> >>
>> >> Nick van Oudtshoorn
>> >> Perth Bible College
>> >>
>> >>
>> >> _______________________________________________
>> >> Koha-devel mailing list
>> >> Koha-devel at lists.koha-community.org
>> >> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>> >> website : http://www.koha-community.org/
>> >> git : http://git.koha-community.org/
>> >> bugs : http://bugs.koha-community.org/
>> >>
>> >
>> >
>> >
>> > --
>> > Ian Walls
>> > Lead Development Specialist
>> > ByWater Solutions
>> > Phone # (888) 900-8944
>> > http://bywatersolutions.com
>> > ian.walls at bywatersolutions.com
>> > Twitter: @sekjal
>> >
>>
>> --
>> Sent from my mobile device
>>
>
>
>
> --
> Ian Walls
> Lead Development Specialist
> ByWater Solutions
> Phone # (888) 900-8944
> http://bywatersolutions.com
> ian.walls at bywatersolutions.com
> Twitter: @sekjal
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110818/414bc6ee/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: coversystem.tar
Type: application/x-tar
Size: 133632 bytes
Desc: not available
URL: </pipermail/koha-devel/attachments/20110818/414bc6ee/attachment-0001.tar>

From danielg.koha at gmail.com  Thu Aug 18 22:32:29 2011
From: danielg.koha at gmail.com (daniel g)
Date: Thu, 18 Aug 2011 13:32:29 -0700
Subject: [Koha-devel] News from the New Newsletter Editor
Message-ID: <CAOeKewiY5xagNxuuS4WKBV-2HdXkwgTx1SHb=5SYC9Me+ozFdQ@mail.gmail.com>

Hello,

As you may know, Nicole Engard has resigned the position of Koha
newsletter editor after a year and a half of splendid work. I?m
pleased the community has selected me to succeed her, and I look
forward to serving the community by producing the monthly account of
what?s new in the world of Koha.

But I need your help to do it! Please send me news of anything you
think the community might like to know about. It can be as short as a
sentence or as long as a paper.

I'm planning to add a gossip column (you call it a society column if
you prefer), which will be short blurbs about what folks in the
community are doing, like "Paul Poulain of BibLibre is assisting 3.6
Quality Assurance Manager Ian Walls in reducing the backlog of patches
waiting for QA testing" and "Melia Meggs joined ByWater Solutions as
their Operations Manager." I'll be harvesting material for this column
from the lists and blogs, but I encourage you to send me a sentence or
two about what you're currently working on.

I?ll also be adding a section on new Koha implementations in the past
month, so if you know of any go-lives that don?t get posted to the
list, please be sure to alert me.

I've already gathered a fair amount of material for the August
newsletter, including the August General IRC meeting, Global Bug
Squashing Day, the status of the releases, and the latest on KohaCon11
and KohaCon12. Please send directly to me (not to the list) anything
else you think might be newsworthy by next Thursday, August 25.

Thanks,
Daniel Grobani

From vanoudt at gmail.com  Fri Aug 19 08:44:51 2011
From: vanoudt at gmail.com (Nicholas van Oudtshoorn)
Date: Fri, 19 Aug 2011 14:44:51 +0800
Subject: [Koha-devel] RFC: Improved book covers
In-Reply-To: <CAE2wdZzk6faNAUsr2ekqHSsT=N3DBmcShV950sm36nUq-FKTBA@mail.gmail.com>
References: <CAJ1eDOTsfazJpLyTWFLjAV+dV1aJNprAYeAx8fihp+jWsFYGVA@mail.gmail.com>
	<CAE2wdZxR_KXy7MjaAyE-3VWm4TOq_r=b54MT3rx8oJJMrAYD1A@mail.gmail.com>
	<CAJ1eDOS40Jw_yebOs71mi7vz6brZwqX3z2OmPXi9mmMwojZU7g@mail.gmail.com>
	<CAE2wdZzk6faNAUsr2ekqHSsT=N3DBmcShV950sm36nUq-FKTBA@mail.gmail.com>
Message-ID: <4E4E0663.7080909@gmail.com>

Finally managed to get access to the library system again. Please find 
attached a version of my new cover system rebased to Koha 3.4.2. There 
are still a few places where things can be tidied up. Thinking about it, 
moving the cover caching system from php to perl would give some really 
nice benefits - such as pre-normalised ISBNs.. Still, my perl-fu is not 
*that* strong (yet!) <grin>

Any questions etc. please let me know.

Fare-ed thee well,
Nick

On Fri, Aug 12, 2011 at 9:32 PM, Ian Walls 
<ian.walls at bywatersolutions.com <mailto:ian.walls at bywatersolutions.com>> 
wrote:

    Nick,


    That'd be great; save us from having to do some rebasing for
    Template Toolkit.


    -Ian


    On Fri, Aug 12, 2011 at 8:46 AM, Nicholas van Rheede van Oudtshoorn
    <vanoudt at gmail.com <mailto:vanoudt at gmail.com>> wrote:

        Thanks Ian! If you like, I can provide an updated version
        (running on
        3.4.2 rather than 3.2) next week when I get back to the server...

        Nick

        On 8/12/11, Ian Walls <ian.walls at bywatersolutions.com
        <mailto:ian.walls at bywatersolutions.com>> wrote:
         > Nick,
         >
         >
         > Very interesting!  I look forward to poking around in it, and
        seeing what
         > could be integrated into Koha.  Thanks for sharing!
         >
         >
         > -Ian
         >
         > 2011/7/25 Nicholas van Rheede van Oudtshoorn
        <vanoudt at gmail.com <mailto:vanoudt at gmail.com>>
         >
         >> Hi all,
         >>
         >> We've been avid users of Koha here at Perth Bible College
        for quite a few
         >> years now. Recently, I've done some work to improve the book
        cover system
         >> here at PBC. A lot of our records lack ISBN records (BAD
        library practices
         >> in the old library system!), and I really wanted something
        nicer than a
         >> "cover not found" image. The result (attached) is an
        html/css book cover
         >> generating system - which also locally stores covers
        attained from
         >> librarything and openlibrary, redirecting to an amazon image
        if no cover
         >> is
         >> found. Unfortunately, it's in php - since I'm more familiar
        with that. :(
         >> The kernel for the system (though it's been *heavily*
        modified is courtesy
         >> a
         >> script by Art Zemon from 2008.
         >>
         >> We also put together a newbooks display. The results can be
        seen on the
         >> landing page: http://library.pbc.wa.edu.au/ - (and there
        you'll see that
         >> even some of our "new" books don't have ISBNs! <groan>)
         >>
         >> Hoping this might be of use to someone else. Something like
        the html/css
         >> book cover system could, in my opinion, be very useful...
         >>
         >> Nick van Oudtshoorn
         >> Perth Bible College
         >>
         >>
         >> _______________________________________________
         >> Koha-devel mailing list
         >> Koha-devel at lists.koha-community.org
        <mailto:Koha-devel at lists.koha-community.org>
         >>
        http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
         >> website : http://www.koha-community.org/
         >> git : http://git.koha-community.org/
         >> bugs : http://bugs.koha-community.org/
         >>
         >
         >
         >
         > --
         > Ian Walls
         > Lead Development Specialist
         > ByWater Solutions
         > Phone # (888) 900-8944
         > http://bywatersolutions.com
         > ian.walls at bywatersolutions.com
        <mailto:ian.walls at bywatersolutions.com>
         > Twitter: @sekjal
         >

        --
        Sent from my mobile device




    -- 
    Ian Walls
    Lead Development Specialist
    ByWater Solutions
    Phone # (888) 900-8944
    http://bywatersolutions.com
    ian.walls at bywatersolutions.com <mailto:ian.walls at bywatersolutions.com>
    Twitter: @sekjal



-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110819/59baa36b/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: coversystem.tar.bz2
Type: application/x-bzip2
Size: 81424 bytes
Desc: not available
URL: </pipermail/koha-devel/attachments/20110819/59baa36b/attachment-0001.bin>

From ef at math.uni-bonn.de  Fri Aug 19 13:00:57 2011
From: ef at math.uni-bonn.de (=?iso-8859-1?Q?Edgar_Fu=DF?=)
Date: Fri, 19 Aug 2011 13:00:57 +0200
Subject: [Koha-devel] Sending acquisition orders per email: confirmation
In-Reply-To: <bug-5260-145-A9xe8rmDT5@http.bugs.koha-community.org/bugzilla3/>
References: <bug-5260-145@http.bugs.koha-community.org/bugzilla3/>
	<bug-5260-145-A9xe8rmDT5@http.bugs.koha-community.org/bugzilla3/>
Message-ID: <8DA6ACE6-AE61-486B-901B-E7301691A3BC@math.uni-bonn.de>

Christophe Croullebois <christophe.croullebois at biblibre.com>  wrote (on bugzilla):
> Hello,
> sorry I have tested, and when you click on "Send Mail" no requester to ask you
> to confirm action, and more uncomfortable IMO no popup to say "operation
> successfull" or "mail sent" or other...
> regards.
Is it Koha practice to request confirmation for non-destructive actions and/or to report successful operations?

I personally usually tend to find these annoying, but if it's what people are used to, it surely should be added.

For the confirmation, that could be done in JavaScript; but for the report, I wouldn't know how to do that.
Could someone point me to examples (in Koha, I mean) where such confirmations/reports are being done?

From bshiundu at strathmore.edu  Sat Aug 20 12:07:57 2011
From: bshiundu at strathmore.edu (Bernard Shiundu)
Date: Sat, 20 Aug 2011 13:07:57 +0300
Subject: [Koha-devel] Use Item Location instead of BranchCode in Circulation
Message-ID: <CAHPESuQR4SoOp=WFK9Yt48Ep1aBz1S70OaYZd-8z4YPiNecFQQ@mail.gmail.com>

A koha library I manage has multiple branches but the lending rules are
based on sections within the library and all the branches have the same
sections. The way I see it, the way to manage this is to change the
circulation and issuing rules to use location rather than branchcode.

Is this a feasible project and any alternative ideas on how best to manage
this?

-- 
*Bernard Shiundu*
***------------------------------------------
**S**trathmore University Library*
*P.O.Box* 59857 - 00200 City Square - Nairobi, Kenya
*Tel*: +254 020 6006155
*Fax*: +254 020 6007498
*Mobile*: +254 733 618135/722 205 428
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110820/cf27ece4/attachment.htm>

From chrisc at catalyst.net.nz  Sun Aug 21 11:10:11 2011
From: chrisc at catalyst.net.nz (Chris Cormack)
Date: Sun, 21 Aug 2011 21:10:11 +1200
Subject: [Koha-devel] Key Dates for 3.6.0
Message-ID: <20110821091011.GX3746@rorohiko.wgtn.cat-it.co.nz>

We are rapidly closing in on the 3.6.0 release, so I thought it would
be good remind everyone of the key dates.

* Feature freeze ? 22 September 23:59 UTC ? From this point on, no new
features will be considered for inclusion into 3.6.0

* String freeze ? 8 October 23:59 UTC ? no bugs that change templates
accepted after this point. This allows the translators to translate
without things changing on them

* Translations finished 18 October 23:59 UTC ? Translations submitted,
so that they can be tested before release

* Release 22 October

Chris
-- 
Chris Cormack
Catalyst IT Ltd.
+64 4 803 2238
PO Box 11-053, Manners St, Wellington 6142, New Zealand
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: </pipermail/koha-devel/attachments/20110821/a895234b/attachment.pgp>

From ian.walls at bywatersolutions.com  Mon Aug 22 12:41:28 2011
From: ian.walls at bywatersolutions.com (Ian Walls)
Date: Mon, 22 Aug 2011 06:41:28 -0400
Subject: [Koha-devel] Use Item Location instead of BranchCode in
	Circulation
In-Reply-To: <CAHPESuQR4SoOp=WFK9Yt48Ep1aBz1S70OaYZd-8z4YPiNecFQQ@mail.gmail.com>
References: <CAHPESuQR4SoOp=WFK9Yt48Ep1aBz1S70OaYZd-8z4YPiNecFQQ@mail.gmail.com>
Message-ID: <CAE2wdZwmWGb7-y4g=Th0fYyooo1yAK-aJwPCZnydFoPzjy7Smg@mail.gmail.com>

Bernard,


My recommendation would be to assign all items in one 'section' of the
library to one item type, and base the rules on that.  Then, for your
patron's searching, use the Collection Code to designate item 'types' like
Book, DVD, VHS, Oversize, etc... you can make the Collection Codes appear as
the search limiter using the AdvancedSearchTypes system preference.


-Ian

2011/8/20 Bernard Shiundu <bshiundu at strathmore.edu>

> A koha library I manage has multiple branches but the lending rules are
> based on sections within the library and all the branches have the same
> sections. The way I see it, the way to manage this is to change the
> circulation and issuing rules to use location rather than branchcode.
>
> Is this a feasible project and any alternative ideas on how best to manage
> this?
>
> --
> *Bernard Shiundu*
> ***------------------------------------------
> **S**trathmore University Library*
> *P.O.Box* 59857 - 00200 City Square - Nairobi, Kenya
> *Tel*: +254 020 6006155
> *Fax*: +254 020 6007498
> *Mobile*: +254 733 618135/722 205 428
>
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>



-- 
Ian Walls
Lead Development Specialist
ByWater Solutions
Phone # (888) 900-8944
http://bywatersolutions.com
ian.walls at bywatersolutions.com
Twitter: @sekjal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110822/aa600c55/attachment.htm>

From fridolyn.somers at gmail.com  Mon Aug 22 15:36:32 2011
From: fridolyn.somers at gmail.com (Fridolyn SOMERS)
Date: Mon, 22 Aug 2011 15:36:32 +0200
Subject: [Koha-devel] 4221 and 6092 bugs
Message-ID: <CAN6cLAWEKWXao+hoCXjQ65uxUP7XPwXyLKB-GjvnySK4kbzzmw@mail.gmail.com>

Hie,

I'm working on both 4221 and 6092 bugs.

I think this bug are duplicates.
The two corrects the problem of default sort oder and field in sysprefs :

   - 4221 sets the default values in SQL database creation script.
   - 6092 sets the default values in Perl code.


We should choose wich one is the rigth solution.

In my opinion, it is more simple to set it in the code, like many other
preferences do, to make it work whatever is in database.

Regards,

-- 
Fridolyn SOMERS
ICT engineer
PROGILONE - Lyon - France
fridolyn.somers at gmail.com
-------------- section suivante --------------
Une pi?ce jointe HTML a ?t? nettoy?e...
URL: </pipermail/koha-devel/attachments/20110822/45327af1/attachment.htm>

From fridolyn.somers at gmail.com  Mon Aug 22 15:48:20 2011
From: fridolyn.somers at gmail.com (Fridolyn SOMERS)
Date: Mon, 22 Aug 2011 15:48:20 +0200
Subject: [Koha-devel] Importing checkout records into Koha
In-Reply-To: <CABg6UYGUw9CK4JCofxFVuYpyZ4sHaHbXdaC91-UJkQT_-YX+jw@mail.gmail.com>
References: <3E19441498923443B9DBE2FE1C0E70B60443E69911@SM-FLOR-VXMB04B.wdw.disney.com>
	<20110809010620.GK3364@rorohiko.wgtn.cat-it.co.nz>
	<17E89776-071A-47FE-A67F-F68F2EC10B24@email.disney.com>
	<20110809014709.GL3364@rorohiko.wgtn.cat-it.co.nz>
	<CABg6UYGUw9CK4JCofxFVuYpyZ4sHaHbXdaC91-UJkQT_-YX+jw@mail.gmail.com>
Message-ID: <CAN6cLAVZ6dS=3gzmE9hhNtjnM5xZznq8Jm72NVruEHLNTJGdbw@mail.gmail.com>

Hie,

For such data integrations, our company uses Talend Open Studio.
It is a business-oriented data modeling software (an open-source based on
Eclipse RCP).
This means that no programing is needed. It can use and produce many file
formats like SQL, XLS, CVS, ...

You may use it to transform your CVS file into a SQL injection script.

See :
http://www.talend.com/products-data-integration/talend-open-studio.php


-- 
Fridolyn SOMERS
ICT engineer
PROGILONE - Lyon - France
fridolyn.somers at gmail.com


On Tue, Aug 9, 2011 at 9:13 AM, Magnus Enger <magnus at enger.priv.no> wrote:

> 2011/8/9 Chris Cormack <chrisc at catalyst.net.nz>:
> > * Hartman, David W. - GBTS Library (David.W.Hartman at disney.com) wrote:
> >> Yes, due date is provided and name - names are unique! :)
> >>
> > Right, then a script like Robin's is probably the way to go.
>
> Here is my script for doing something similar:
> https://github.com/MagnusEnger/LibrioTools/blob/master/tidem/loans.pl
> Again, this is tailored to one specific system/situation (where the
> data about current checkouts was in HTML format!), but it might give
> some hints...
>
> What I did was create a .koc-file with my script, which I could then
> import using Home ? Circulation ? Offline Circulation File Upload. I
> figured that would reduce the risk of putting data in the wrong place
> or missing some field in some table that should have data in it...
>
> The format of the .koc file is documented here:
> http://wiki.koha-community.org/wiki/Koha_offline_circulation_file_format
>
> Best regards,
> Magnus Enger
> libriotech.no
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>
-------------- section suivante --------------
Une pi?ce jointe HTML a ?t? nettoy?e...
URL: </pipermail/koha-devel/attachments/20110822/955f6d15/attachment.htm>

From cnighswonger at foundations.edu  Tue Aug 23 03:39:17 2011
From: cnighswonger at foundations.edu (Chris Nighswonger)
Date: Mon, 22 Aug 2011 21:39:17 -0400
Subject: [Koha-devel] Koha 3.4.4 is now available
Message-ID: <CAP3yOokxkLuzeeDMfF4XopB_C6yJK+ngqGG-5DOa1wqqJSdp=g@mail.gmail.com>

It is with pleasure that I announce the release of Koha 3.4.4.

The package can be retrieved from:

http://download.koha-community.org/koha-3.04.04.tar.gz

You can use the following checksum and signature files to verify the download:

http://download.koha-community.org/koha-3.04.04.tar.gz.MD5
http://download.koha-community.org/koha-3.04.04.tar.gz.MD5.asc
http://download.koha-community.org/koha-3.04.04.tar.gz.sig

Release notes for 3.4.4 are below.

Come and get it!

RELEASE NOTES FOR KOHA 3.4.4 - 22 August 2011
========================================================================

Koha is the first free and open source software library automation package
(ILS). Development is sponsored by libraries of varying types and sizes,
volunteers, and support companies from around the world.
The website for the Koha project is

    http://koha-community.org/

Koha 3.4.4 can be downloaded from:

    http://download.koha-community.org/koha-3.04.03.tar.gz

Installation instructions can be found at:

    http://wiki.koha-community.org/wiki/Installation_Documentation

    OR in the INSTALL files that come in the tarball

Koha 3.4.4 is a bugfix/maintenance release.

Highlights of 3.4.4
======================

4415    critical    child record only using parent's info
6269    critical    can't undefine a printer profile
6611    critical    patron barcode removed when editing an attribute
6634    critical    manager_id not populated when paying fines
6635    critical    Can't page through results in label batch
6643    critical    Able to download patron card batches as an unauthorized user
6686    critical    Can't delete messages
6713    critical    marc import not matching
2629    major       Diacritics not being ignored when searching
4873    major       Debian packaging should avoid /var/run and
/var/lock in the package
5131    major       XSS vulnerability in the OPAC search results interface
5713    major       Intranet - Circulation - Fines : debug calculation
when fines are reversed then re-payed
6476    major       Baker & Taylor Content Not Working after Upgrade
6614    major       CSV Basket Export gives blank lines
6641    major       Specially crafted URL can allow unauthorized
download of MARC files from staff client
6642    major       Able to download label batches as an unauthorized user

Bugs fixed in 3.4.4
======================

1604    when doing a 'scan', "count" isn't displayed
1643    moredetail.pl allows item deletion with no warning and
irrespective of independentbranches
4002    Issues with borrowernumber set as NULL
4433    $a displayed in front of topical subjects in authority search
4497    Acq > Manage suggestions contains untranslated strings
5072    Filling an order page with no budget defined causes a 500 error
5098    overdue script and csv
5660    Webinstaller should check if KohaOpacLanguage exists in staff
5737    ZOOM connection problem in merge_authority.pl when trying to
do a batch merge.
6034    Shelving cart feature can wipe permanent shelving location in
certain circumstances
6139    Automatic incrementation of call number does not work if given
prefix contains a '
6181    Remove CGI::scrolling_list from C4:Budgets
6235    "Saved" message in sysprefs never gets hidden on IE8
6280    Invalid SQL being passed in circulation checkout
6291    Cart printing truncated in Firefox
6369    Formatting problems on some items when printing an order form (PDF).
6373    The mandatory fields validation popup doesn't appear in IE8
6410    Returns use wrong borrower number var name
6458    incorrect parsing result in translation processing
6461    BiblioDefaultView has no impact on how record are displayed
when going from results list
6468    Authorities browsing error in OPAC
6480    Koha produces a lot of apache logs for UNIMARC
6484    Due date sorter on 'my summary' missing
6521    Editing a patron fails with blank cardnumber
6578    serial items have misaligned columns in holdings table
6598    OPACFineNoRenewals syspreference does not stop user renewing in opac
6601    Dictionary items not adding to query
6632    [security] XXS on list name (on admin part)
6638    Columns misaligned on serials claims
6690    If multiple issues are received in serials-edit.pl, changing
the status of any issue changes the date of the first issue.
6701    language on timeout system preference is wrong
6714    opac.css uses files in the /en/ directory when using other languages
6743    displayFacetCount not working
3605    Invalid XHTML in z3950_search.tmpl
4959    Language inconsistencies on basket groups; skip confirmation
when closing basket.
5468    libyaz3 debian dependency
5662    Show control number without organization code in OPAC URLs
5663    Show control number without organization code in staff URLs
6057    Improve finding next stock number
6080    Total is wrong in acqui-home.pl
6116    Adding child patron: library not set
6135    Insert fields ordered in C4::Biblio::ModBiblioMarc
6144    Cant hide constraints when showed at subfield edition
6290    Fixing uninitialized warnings on homebranch in XSLT.pm
6311    end_patron_session always reports a non-existent error
6346    Patron search results should be valigned top
6412    notes on pay fine full of spaces
6474    Automatic incrementation of call number does not work if given
prefix contains a -
6503    Variable $sth is declared 3 times (with keyword "my") in
"makepayment" sub of "Accounts.pm"
6599    Don't show dictionary definition table if there are no definitions
6622    Remove closing style tag from staff-global.css
6626    Packages require sudo to work, but it's not a dependency.
6678    Fix some problems with the standard NORMARC framework
6260    Missing space in availability information of OPAC XSLT results
6527    Table striping not working on cataloguing search
6702    BiblioAddsAuthorities pref says too instead of to
5719    Update UNIMARC plugins
5922    Show waiting items for patron on return
6078    Patron with no checkout Report overload the server
6150    UNIMARC field 225 plugin: allow $a value data entry
6259    AllowHoldPolicyOverride ON causes every staff hold to require override
6309    subscription table sorter in the opac
6482    koha-create makes assumptions about the mysql username
6486    Need a quick way to access mysql as the user for a koha instance
6534    Duplicate opac renew buttons at the top of the checkouts list
6540    Add more options to koha-create
6553    Parentheses in corporate author break tracings
6612    Sort pulldown for messages in alphabetical order
6692    Change 'Set' to 'Set library'

System requirements
======================

    Changes since 3.2:

    * Template::Toolkit

Documentation
======================

As of Koha 3.2, the Koha manual is now maintained in DocBook.  The
home page for Koha documentation is

    http://koha-community.org/documentation/

As of the date of these release notes, only the english version of the
Koha manual is available:

    http://koha-community.org/documentation/3-4-manual/

The Git repository for the Koha manual can be found at

    http://git.koha-community.org/gitweb/?p=kohadocs.git;a=summary

Translations
======================

Complete or near-complete translations of the OPAC and staff
interface are available in this release for the following languages:

  * Chinese
  * Danish
  * English (New Zealand)
  * English (USA)
  * French (France)
  * French (Canada)
  * German
  * Greek
  * Hindi
  * Italian
  * Norwegian
  * Portuguese
  * Spanish
  * Turkish

Partial translations are available for various other languages.

The Koha team welcomes additional translations; please see

    http://wiki.koha-community.org/wiki/Translating_Koha

for information about translating Koha, and join the koha-translate
list to volunteer:

    http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-translate

The most up-to-date translations can be found at:

    http://translate.koha-community.org/

Release Team
======================

The release team for Koha 3.4 is

Release Manager:        Chris Cormack <chrisc at catalyst.net.nz>
Documentation Manager:  Nicole C Engard <nengard at gmail.com>
Translation Manager:    Fr??d??ric Demians <frederic at tamil.fr>
Release Maintainer (3.2.x):
                        Chris Nighswonger <cnighswonger at foundations.edu>
Release Maintainer (3.4.x):
                        Chris Nighswonger <cnighswonger at foundations.edu>
QA Manager:             Colin Campbell

Credits
======================

We thank the following individuals who contributed patches to
Koha 3.4.4

Alex Arnaud
Colin Campbell
Fr??d??rick Capovilla
Chris Cormack
Christophe Croullebois
St??phane Delaune
Fr??d??ric Demians
Nicole C. Engard
Magnus Enger
Katrin Fischer
Srdjan Jankovic
Janusz Kaczmarek
Owen Leonard
Fr??re S??bastien Marie
Ricardo Dias Marques
Julian Maurice
Sophie Meynieux
Chris Nighswonger
Paul Poulain
preprod34
MJ Ray
Liz Rea
Marcel de Rooy
Brice Sanchez
Jean-Andr?? Santoni
John Seymour
Robin Sheat
Juan Romay Sieira
Jane Wagner
Ian Walls

We regret any omissions.  If a contributor has been inadvertantly missed,
please send a patch against these release notes to
koha-patches at lists.koha-community.org.

Revision control notes
======================

The Koha project uses Git for version control.  The current development
version of Koha can be retrieved by checking out the master branch of

    git://git.koha-community.org/koha.git

The branch for Koha 3.4.x (i.e., this version of Koha and future bugfix
releases) is 3.4.x.

The next major feature release of Koha will be Koha 3.6.0.

Bugs and feature requests
======================

Bug reports and feature requests can be filed at the Koha bug
tracker at

    http://bugs.koha-community.org/

Ehara taku toa i te toa takitahi, engari he toa takitini

From henridamien.laurent at gmail.com  Tue Aug 23 08:35:52 2011
From: henridamien.laurent at gmail.com (LAURENT Henri-Damien)
Date: Tue, 23 Aug 2011 08:35:52 +0200
Subject: [Koha-devel] Koha 3.4.4 is now available
In-Reply-To: <CAP3yOokxkLuzeeDMfF4XopB_C6yJK+ngqGG-5DOa1wqqJSdp=g@mail.gmail.com>
References: <CAP3yOokxkLuzeeDMfF4XopB_C6yJK+ngqGG-5DOa1wqqJSdp=g@mail.gmail.com>
Message-ID: <4E534A48.7020509@gmail.com>

Le 23/08/2011 03:39, Chris Nighswonger a ?crit :
> It is with pleasure that I announce the release of Koha 3.4.4.
> 
> The package can be retrieved from:
> 
> http://download.koha-community.org/koha-3.04.04.tar.gz
> 
> You can use the following checksum and signature files to verify the download:
> 
> http://download.koha-community.org/koha-3.04.04.tar.gz.MD5
> http://download.koha-community.org/koha-3.04.04.tar.gz.MD5.asc
> http://download.koha-community.org/koha-3.04.04.tar.gz.sig
> 
> Release notes for 3.4.4 are below.
> 
> Come and get it!
> 
> RELEASE NOTES FOR KOHA 3.4.4 - 22 August 2011
> ========================================================================
> 
> Koha is the first free and open source software library automation package
> (ILS). Development is sponsored by libraries of varying types and sizes,
> volunteers, and support companies from around the world.
> The website for the Koha project is
> 
>     http://koha-community.org/
> 
> Koha 3.4.4 can be downloaded from:
> 
>     http://download.koha-community.org/koha-3.04.03.tar.gz
> 
> Installation instructions can be found at:
> 
>     http://wiki.koha-community.org/wiki/Installation_Documentation
> 
>     OR in the INSTALL files that come in the tarball
> 
> Koha 3.4.4 is a bugfix/maintenance release.
> 
> Highlights of 3.4.4
> ======================
> 
> 4415    critical    child record only using parent's info
> 6269    critical    can't undefine a printer profile
> 6611    critical    patron barcode removed when editing an attribute
> 6634    critical    manager_id not populated when paying fines
> 6635    critical    Can't page through results in label batch
> 6643    critical    Able to download patron card batches as an unauthorized user
> 6686    critical    Can't delete messages
> 6713    critical    marc import not matching
> 2629    major       Diacritics not being ignored when searching
> 4873    major       Debian packaging should avoid /var/run and
> /var/lock in the package
> 5131    major       XSS vulnerability in the OPAC search results interface
> 5713    major       Intranet - Circulation - Fines : debug calculation
> when fines are reversed then re-payed
> 6476    major       Baker & Taylor Content Not Working after Upgrade
> 6614    major       CSV Basket Export gives blank lines
> 6641    major       Specially crafted URL can allow unauthorized
> download of MARC files from staff client
> 6642    major       Able to download label batches as an unauthorized user
> 
> Bugs fixed in 3.4.4
> ======================
> 
> 1604    when doing a 'scan', "count" isn't displayed
> 1643    moredetail.pl allows item deletion with no warning and
> irrespective of independentbranches
> 4002    Issues with borrowernumber set as NULL
> 4433    $a displayed in front of topical subjects in authority search
> 4497    Acq > Manage suggestions contains untranslated strings
> 5072    Filling an order page with no budget defined causes a 500 error
> 5098    overdue script and csv
> 5660    Webinstaller should check if KohaOpacLanguage exists in staff
> 5737    ZOOM connection problem in merge_authority.pl when trying to
> do a batch merge.
> 6034    Shelving cart feature can wipe permanent shelving location in
> certain circumstances
> 6139    Automatic incrementation of call number does not work if given
> prefix contains a '
> 6181    Remove CGI::scrolling_list from C4:Budgets
> 6235    "Saved" message in sysprefs never gets hidden on IE8
> 6280    Invalid SQL being passed in circulation checkout
> 6291    Cart printing truncated in Firefox
> 6369    Formatting problems on some items when printing an order form (PDF).
> 6373    The mandatory fields validation popup doesn't appear in IE8
> 6410    Returns use wrong borrower number var name
> 6458    incorrect parsing result in translation processing
> 6461    BiblioDefaultView has no impact on how record are displayed
> when going from results list
> 6468    Authorities browsing error in OPAC
> 6480    Koha produces a lot of apache logs for UNIMARC
> 6484    Due date sorter on 'my summary' missing
> 6521    Editing a patron fails with blank cardnumber
> 6578    serial items have misaligned columns in holdings table
> 6598    OPACFineNoRenewals syspreference does not stop user renewing in opac
> 6601    Dictionary items not adding to query
> 6632    [security] XXS on list name (on admin part)
> 6638    Columns misaligned on serials claims
> 6690    If multiple issues are received in serials-edit.pl, changing
> the status of any issue changes the date of the first issue.
> 6701    language on timeout system preference is wrong
> 6714    opac.css uses files in the /en/ directory when using other languages
> 6743    displayFacetCount not working
> 3605    Invalid XHTML in z3950_search.tmpl
> 4959    Language inconsistencies on basket groups; skip confirmation
> when closing basket.
> 5468    libyaz3 debian dependency
> 5662    Show control number without organization code in OPAC URLs
> 5663    Show control number without organization code in staff URLs
> 6057    Improve finding next stock number
> 6080    Total is wrong in acqui-home.pl
> 6116    Adding child patron: library not set
> 6135    Insert fields ordered in C4::Biblio::ModBiblioMarc
> 6144    Cant hide constraints when showed at subfield edition
> 6290    Fixing uninitialized warnings on homebranch in XSLT.pm
> 6311    end_patron_session always reports a non-existent error
> 6346    Patron search results should be valigned top
> 6412    notes on pay fine full of spaces
> 6474    Automatic incrementation of call number does not work if given
> prefix contains a -
> 6503    Variable $sth is declared 3 times (with keyword "my") in
> "makepayment" sub of "Accounts.pm"
> 6599    Don't show dictionary definition table if there are no definitions
> 6622    Remove closing style tag from staff-global.css
> 6626    Packages require sudo to work, but it's not a dependency.
> 6678    Fix some problems with the standard NORMARC framework
> 6260    Missing space in availability information of OPAC XSLT results
> 6527    Table striping not working on cataloguing search
> 6702    BiblioAddsAuthorities pref says too instead of to
> 5719    Update UNIMARC plugins
> 5922    Show waiting items for patron on return
> 6078    Patron with no checkout Report overload the server
> 6150    UNIMARC field 225 plugin: allow $a value data entry
> 6259    AllowHoldPolicyOverride ON causes every staff hold to require override
> 6309    subscription table sorter in the opac
> 6482    koha-create makes assumptions about the mysql username
> 6486    Need a quick way to access mysql as the user for a koha instance
> 6534    Duplicate opac renew buttons at the top of the checkouts list
> 6540    Add more options to koha-create
> 6553    Parentheses in corporate author break tracings
> 6612    Sort pulldown for messages in alphabetical order
> 6692    Change 'Set' to 'Set library'
> 
> System requirements
> ======================
> 
>     Changes since 3.2:
> 
>     * Template::Toolkit
> 
Congratulations Chris.

From raosoma at gmail.com  Wed Aug 24 05:22:49 2011
From: raosoma at gmail.com (Somasekhar Rao K)
Date: Wed, 24 Aug 2011 08:52:49 +0530
Subject: [Koha-devel] [Koha] Koha 3.4.4 is now available
In-Reply-To: <CAP3yOokxkLuzeeDMfF4XopB_C6yJK+ngqGG-5DOa1wqqJSdp=g@mail.gmail.com>
References: <CAP3yOokxkLuzeeDMfF4XopB_C6yJK+ngqGG-5DOa1wqqJSdp=g@mail.gmail.com>
Message-ID: <CAPzijSuJBuP8shpmXT6BLo-qhqJDAeBbor1iSWFzfD_TcZ7iMA@mail.gmail.com>

Hi,

Looks like the installation procedure on debian has changed.
I tried to install on Debian 6.0 (squeeze) machine. I used
rackspace.comcloud server. It didn't work out. Many errors.

I was using 3.2.10 on rackspace.com debian 5 (lenny) server. It was perfect.


Any help please.

Regards,
Somasekhar Rao K

On Tue, Aug 23, 2011 at 7:09 AM, Chris Nighswonger <
cnighswonger at foundations.edu> wrote:

> It is with pleasure that I announce the release of Koha 3.4.4.
>
> The package can be retrieved from:
>
> http://download.koha-community.org/koha-3.04.04.tar.gz
>
> You can use the following checksum and signature files to verify the
> download:
>
> http://download.koha-community.org/koha-3.04.04.tar.gz.MD5
> http://download.koha-community.org/koha-3.04.04.tar.gz.MD5.asc
> http://download.koha-community.org/koha-3.04.04.tar.gz.sig
>
> Release notes for 3.4.4 are below.
>
> Come and get it!
>
> RELEASE NOTES FOR KOHA 3.4.4 - 22 August 2011
> ========================================================================
>
> Koha is the first free and open source software library automation package
> (ILS). Development is sponsored by libraries of varying types and sizes,
> volunteers, and support companies from around the world.
> The website for the Koha project is
>
>    http://koha-community.org/
>
> Koha 3.4.4 can be downloaded from:
>
>    http://download.koha-community.org/koha-3.04.03.tar.gz
>
> Installation instructions can be found at:
>
>    http://wiki.koha-community.org/wiki/Installation_Documentation
>
>    OR in the INSTALL files that come in the tarball
>
> Koha 3.4.4 is a bugfix/maintenance release.
>
> Highlights of 3.4.4
> ======================
>
> 4415    critical    child record only using parent's info
> 6269    critical    can't undefine a printer profile
> 6611    critical    patron barcode removed when editing an attribute
> 6634    critical    manager_id not populated when paying fines
> 6635    critical    Can't page through results in label batch
> 6643    critical    Able to download patron card batches as an unauthorized
> user
> 6686    critical    Can't delete messages
> 6713    critical    marc import not matching
> 2629    major       Diacritics not being ignored when searching
> 4873    major       Debian packaging should avoid /var/run and
> /var/lock in the package
> 5131    major       XSS vulnerability in the OPAC search results interface
> 5713    major       Intranet - Circulation - Fines : debug calculation
> when fines are reversed then re-payed
> 6476    major       Baker & Taylor Content Not Working after Upgrade
> 6614    major       CSV Basket Export gives blank lines
> 6641    major       Specially crafted URL can allow unauthorized
> download of MARC files from staff client
> 6642    major       Able to download label batches as an unauthorized user
>
> Bugs fixed in 3.4.4
> ======================
>
> 1604    when doing a 'scan', "count" isn't displayed
> 1643    moredetail.pl allows item deletion with no warning and
> irrespective of independentbranches
> 4002    Issues with borrowernumber set as NULL
> 4433    $a displayed in front of topical subjects in authority search
> 4497    Acq > Manage suggestions contains untranslated strings
> 5072    Filling an order page with no budget defined causes a 500 error
> 5098    overdue script and csv
> 5660    Webinstaller should check if KohaOpacLanguage exists in staff
> 5737    ZOOM connection problem in merge_authority.pl when trying to
> do a batch merge.
> 6034    Shelving cart feature can wipe permanent shelving location in
> certain circumstances
> 6139    Automatic incrementation of call number does not work if given
> prefix contains a '
> 6181    Remove CGI::scrolling_list from C4:Budgets
> 6235    "Saved" message in sysprefs never gets hidden on IE8
> 6280    Invalid SQL being passed in circulation checkout
> 6291    Cart printing truncated in Firefox
> 6369    Formatting problems on some items when printing an order form
> (PDF).
> 6373    The mandatory fields validation popup doesn't appear in IE8
> 6410    Returns use wrong borrower number var name
> 6458    incorrect parsing result in translation processing
> 6461    BiblioDefaultView has no impact on how record are displayed
> when going from results list
> 6468    Authorities browsing error in OPAC
> 6480    Koha produces a lot of apache logs for UNIMARC
> 6484    Due date sorter on 'my summary' missing
> 6521    Editing a patron fails with blank cardnumber
> 6578    serial items have misaligned columns in holdings table
> 6598    OPACFineNoRenewals syspreference does not stop user renewing in
> opac
> 6601    Dictionary items not adding to query
> 6632    [security] XXS on list name (on admin part)
> 6638    Columns misaligned on serials claims
> 6690    If multiple issues are received in serials-edit.pl, changing
> the status of any issue changes the date of the first issue.
> 6701    language on timeout system preference is wrong
> 6714    opac.css uses files in the /en/ directory when using other
> languages
> 6743    displayFacetCount not working
> 3605    Invalid XHTML in z3950_search.tmpl
> 4959    Language inconsistencies on basket groups; skip confirmation
> when closing basket.
> 5468    libyaz3 debian dependency
> 5662    Show control number without organization code in OPAC URLs
> 5663    Show control number without organization code in staff URLs
> 6057    Improve finding next stock number
> 6080    Total is wrong in acqui-home.pl
> 6116    Adding child patron: library not set
> 6135    Insert fields ordered in C4::Biblio::ModBiblioMarc
> 6144    Cant hide constraints when showed at subfield edition
> 6290    Fixing uninitialized warnings on homebranch in XSLT.pm
> 6311    end_patron_session always reports a non-existent error
> 6346    Patron search results should be valigned top
> 6412    notes on pay fine full of spaces
> 6474    Automatic incrementation of call number does not work if given
> prefix contains a -
> 6503    Variable $sth is declared 3 times (with keyword "my") in
> "makepayment" sub of "Accounts.pm"
> 6599    Don't show dictionary definition table if there are no definitions
> 6622    Remove closing style tag from staff-global.css
> 6626    Packages require sudo to work, but it's not a dependency.
> 6678    Fix some problems with the standard NORMARC framework
> 6260    Missing space in availability information of OPAC XSLT results
> 6527    Table striping not working on cataloguing search
> 6702    BiblioAddsAuthorities pref says too instead of to
> 5719    Update UNIMARC plugins
> 5922    Show waiting items for patron on return
> 6078    Patron with no checkout Report overload the server
> 6150    UNIMARC field 225 plugin: allow $a value data entry
> 6259    AllowHoldPolicyOverride ON causes every staff hold to require
> override
> 6309    subscription table sorter in the opac
> 6482    koha-create makes assumptions about the mysql username
> 6486    Need a quick way to access mysql as the user for a koha instance
> 6534    Duplicate opac renew buttons at the top of the checkouts list
> 6540    Add more options to koha-create
> 6553    Parentheses in corporate author break tracings
> 6612    Sort pulldown for messages in alphabetical order
> 6692    Change 'Set' to 'Set library'
>
> System requirements
> ======================
>
>    Changes since 3.2:
>
>    * Template::Toolkit
>
> Documentation
> ======================
>
> As of Koha 3.2, the Koha manual is now maintained in DocBook.  The
> home page for Koha documentation is
>
>    http://koha-community.org/documentation/
>
> As of the date of these release notes, only the english version of the
> Koha manual is available:
>
>    http://koha-community.org/documentation/3-4-manual/
>
> The Git repository for the Koha manual can be found at
>
>    http://git.koha-community.org/gitweb/?p=kohadocs.git;a=summary
>
> Translations
> ======================
>
> Complete or near-complete translations of the OPAC and staff
> interface are available in this release for the following languages:
>
>  * Chinese
>  * Danish
>  * English (New Zealand)
>  * English (USA)
>  * French (France)
>  * French (Canada)
>  * German
>  * Greek
>  * Hindi
>  * Italian
>  * Norwegian
>  * Portuguese
>  * Spanish
>  * Turkish
>
> Partial translations are available for various other languages.
>
> The Koha team welcomes additional translations; please see
>
>    http://wiki.koha-community.org/wiki/Translating_Koha
>
> for information about translating Koha, and join the koha-translate
> list to volunteer:
>
>    http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-translate
>
> The most up-to-date translations can be found at:
>
>    http://translate.koha-community.org/
>
> Release Team
> ======================
>
> The release team for Koha 3.4 is
>
> Release Manager:        Chris Cormack <chrisc at catalyst.net.nz>
> Documentation Manager:  Nicole C Engard <nengard at gmail.com>
> Translation Manager:    Fr??d??ric Demians <frederic at tamil.fr>
> Release Maintainer (3.2.x):
>                        Chris Nighswonger <cnighswonger at foundations.edu>
> Release Maintainer (3.4.x):
>                        Chris Nighswonger <cnighswonger at foundations.edu>
> QA Manager:             Colin Campbell
>
> Credits
> ======================
>
> We thank the following individuals who contributed patches to
> Koha 3.4.4
>
> Alex Arnaud
> Colin Campbell
> Fr??d??rick Capovilla
> Chris Cormack
> Christophe Croullebois
> St??phane Delaune
> Fr??d??ric Demians
> Nicole C. Engard
> Magnus Enger
> Katrin Fischer
> Srdjan Jankovic
> Janusz Kaczmarek
> Owen Leonard
> Fr??re S??bastien Marie
> Ricardo Dias Marques
> Julian Maurice
> Sophie Meynieux
> Chris Nighswonger
> Paul Poulain
> preprod34
> MJ Ray
> Liz Rea
> Marcel de Rooy
> Brice Sanchez
> Jean-Andr?? Santoni
> John Seymour
> Robin Sheat
> Juan Romay Sieira
> Jane Wagner
> Ian Walls
>
> We regret any omissions.  If a contributor has been inadvertantly missed,
> please send a patch against these release notes to
> koha-patches at lists.koha-community.org.
>
> Revision control notes
> ======================
>
> The Koha project uses Git for version control.  The current development
> version of Koha can be retrieved by checking out the master branch of
>
>    git://git.koha-community.org/koha.git
>
> The branch for Koha 3.4.x (i.e., this version of Koha and future bugfix
> releases) is 3.4.x.
>
> The next major feature release of Koha will be Koha 3.6.0.
>
> Bugs and feature requests
> ======================
>
> Bug reports and feature requests can be filed at the Koha bug
> tracker at
>
>    http://bugs.koha-community.org/
>
> Ehara taku toa i te toa takitahi, engari he toa takitini
> _______________________________________________
> Koha mailing list  http://koha-community.org
> Koha at lists.katipo.co.nz
> http://lists.katipo.co.nz/mailman/listinfo/koha
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110824/2aa04100/attachment.htm>

From mtj at kohaaloha.com  Wed Aug 24 08:34:23 2011
From: mtj at kohaaloha.com (Mason James)
Date: Wed, 24 Aug 2011 18:34:23 +1200
Subject: [Koha-devel] [Koha] Koha 3.4.4 is now available
In-Reply-To: <CAPzijSuJBuP8shpmXT6BLo-qhqJDAeBbor1iSWFzfD_TcZ7iMA@mail.gmail.com>
References: <CAP3yOokxkLuzeeDMfF4XopB_C6yJK+ngqGG-5DOa1wqqJSdp=g@mail.gmail.com>
	<CAPzijSuJBuP8shpmXT6BLo-qhqJDAeBbor1iSWFzfD_TcZ7iMA@mail.gmail.com>
Message-ID: <4219BA64-FA98-4408-A5CF-5949FF5F7F68@kohaaloha.com>


On 2011-08-24, at 3:22 PM, Somasekhar Rao K wrote:

> Hi,
> 
> Looks like the installation procedure on debian has changed. 
> I tried to install on Debian 6.0 (squeeze) machine. I used rackspace.com cloud server. It didn't work out.


> Many errors. 

and those many errors were...???


From raosoma at gmail.com  Thu Aug 25 04:32:18 2011
From: raosoma at gmail.com (Somasekhar Rao K)
Date: Thu, 25 Aug 2011 08:02:18 +0530
Subject: [Koha-devel] [Koha] Koha 3.4.4 is now available
In-Reply-To: <4219BA64-FA98-4408-A5CF-5949FF5F7F68@kohaaloha.com>
References: <CAP3yOokxkLuzeeDMfF4XopB_C6yJK+ngqGG-5DOa1wqqJSdp=g@mail.gmail.com>
	<CAPzijSuJBuP8shpmXT6BLo-qhqJDAeBbor1iSWFzfD_TcZ7iMA@mail.gmail.com>
	<4219BA64-FA98-4408-A5CF-5949FF5F7F68@kohaaloha.com>
Message-ID: <CAPzijStim=LBMg8eO4sKo=aOk4mimNM-cFBYrfKfbaF0bMtXpQ@mail.gmail.com>

Hi,

Operating system: Debian 6.0 (Squeeze) using rackspace.com cloud server

After execution of command
sudo apt-get dselect-upgrade

the output is something like this...


Get:284 http://http.us.debian.org/debian/ squeeze/main xfonts-utils amd64
1:7.5+2 [96.2
kB]
Get:285 http://http.us.debian.org/debian/ squeeze/main x-ttcidfont-conf all
32 [23.9
kB]
Get:286 http://http.us.debian.org/debian/ squeeze/main xml-core all 0.13
[23.4
kB]
Get:287 http://http.us.debian.org/debian/ squeeze/main wfinnish all 0.7-17.3
[2008
kB]
Fetched 183 MB in 34s (5244
kB/s)

perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_CTYPE = "UTF-8",
    LANG = (unset)
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
Extracting templates from packages: 100%
Preconfiguring packages ...
/usr/bin/locale: Cannot set LC_CTYPE to default locale: No such file or
directory
/usr/bin/locale: Cannot set LC_ALL to default locale: No such file or
directory
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
    LANGUAGE = (unset),
    LC_ALL = (unset),
    LC_CTYPE = "UTF-8",
    LANG = (unset)
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 155, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 155, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 155, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31.



Regards,
Sekhar




On Wed, Aug 24, 2011 at 12:04 PM, Mason James <mtj at kohaaloha.com> wrote:

>
> On 2011-08-24, at 3:22 PM, Somasekhar Rao K wrote:
>
> > Hi,
> >
> > Looks like the installation procedure on debian has changed.
> > I tried to install on Debian 6.0 (squeeze) machine. I used rackspace.comcloud server. It didn't work out.
>
>
> > Many errors.
>
> and those many errors were...???
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110825/424f9d66/attachment.htm>

From robin at catalyst.net.nz  Thu Aug 25 04:34:49 2011
From: robin at catalyst.net.nz (Robin Sheat)
Date: Thu, 25 Aug 2011 14:34:49 +1200
Subject: [Koha-devel] [Koha] Koha 3.4.4 is now available
In-Reply-To: <CAPzijStim=LBMg8eO4sKo=aOk4mimNM-cFBYrfKfbaF0bMtXpQ@mail.gmail.com>
References: <CAP3yOokxkLuzeeDMfF4XopB_C6yJK+ngqGG-5DOa1wqqJSdp=g@mail.gmail.com>
	<CAPzijSuJBuP8shpmXT6BLo-qhqJDAeBbor1iSWFzfD_TcZ7iMA@mail.gmail.com>
	<4219BA64-FA98-4408-A5CF-5949FF5F7F68@kohaaloha.com>
	<CAPzijStim=LBMg8eO4sKo=aOk4mimNM-cFBYrfKfbaF0bMtXpQ@mail.gmail.com>
Message-ID: <1314239689.3396.120.camel@zarathud>

Somasekhar Rao K schreef op do 25-08-2011 om 08:02 [+0530]:
> Operating system: Debian 6.0 (Squeeze) using rackspace.com cloud
> server
> 
> After execution of command 
> sudo apt-get dselect-upgrade
> 
> the output is something like this... 

Those errors are completely unrelated to Koha. 

Something like 'dpkg-reconfigure locale' may help with some of them
though.

-- 
Robin Sheat
Catalyst IT Ltd.
? +64 4 803 2204
GPG: 5957 6D23 8B16 EFAB FEF8  7175 14D3 6485 A99C EB6D
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: </pipermail/koha-devel/attachments/20110825/d6a7bf19/attachment.pgp>

From raosoma at gmail.com  Thu Aug 25 14:11:27 2011
From: raosoma at gmail.com (Somasekhar Rao K)
Date: Thu, 25 Aug 2011 17:41:27 +0530
Subject: [Koha-devel] Regarding locale setting on Debian 6.0
Message-ID: <CAPzijSut=gsVAKx2Gc40j1h6PT__PzG04c1+Tu1RA7=vazuHtQ@mail.gmail.com>

Hi,

I tried to set using 'dpkg-reconfigure locale'.
But still I got same errors.

Is there any alternative way of doing this?
alos what should be the values of these locale settings.
LANGUAGE = (unset),
   LC_ALL = (unset),
   LC_CTYPE = "UTF-8",
   LANG = (unset)

Thanks & Regards,
Somasekhar Rao K


------------------------------
----------------------------------------

Message: 1
Date: Thu, 25 Aug 2011 08:02:18 +0530
From: Somasekhar Rao K <raosoma at gmail.com>
Subject: Re: [Koha-devel] [Koha] Koha 3.4.4 is now available
To: Mason James <mtj at kohaaloha.com>
Cc: koha-devel at lists.koha-community.org
Message-ID:
       <CAPzijStim=LBMg8eO4sKo=aOk4mimNM-cFBYrfKfbaF0bMtXpQ at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

Hi,

Operating system: Debian 6.0 (Squeeze) using rackspace.com cloud server

After execution of command
sudo apt-get dselect-upgrade

the output is something like this...


Get:284 http://http.us.debian.org/debian/ squeeze/main xfonts-utils amd64
1:7.5+2 [96.2
kB]
Get:285 http://http.us.debian.org/debian/ squeeze/main x-ttcidfont-conf all
32 [23.9
kB]
Get:286 http://http.us.debian.org/debian/ squeeze/main xml-core all 0.13
[23.4
kB]
Get:287 http://http.us.debian.org/debian/ squeeze/main wfinnish all 0.7-17.3
[2008
kB]
Fetched 183 MB in 34s (5244
kB/s)

perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
   LANGUAGE = (unset),
   LC_ALL = (unset),
   LC_CTYPE = "UTF-8",
   LANG = (unset)
   are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
Extracting templates from packages: 100%
Preconfiguring packages ...
/usr/bin/locale: Cannot set LC_CTYPE to default locale: No such file or
directory
/usr/bin/locale: Cannot set LC_ALL to default locale: No such file or
directory
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
   LANGUAGE = (unset),
   LC_ALL = (unset),
   LC_CTYPE = "UTF-8",
   LANG = (unset)
   are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 155, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 155, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 155, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31.
Use of uninitialized value $classprefix in concatenation (.) or string at
/tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31.



Regards,
Sekhar




On Wed, Aug 24, 2011 at 12:04 PM, Mason James <mtj at kohaaloha.com> wrote:

>
> On 2011-08-24, at 3:22 PM, Somasekhar Rao K wrote:
>
> > Hi,
> >
> > Looks like the installation procedure on debian has changed.
> > I tried to install on Debian 6.0 (squeeze) machine. I used
rackspace.comcloud server. It didn't work out.
>
>
> > Many errors.
>
> and those many errors were...???
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110825/424f9d66/attachment.html>

------------------------------

Message: 2
Date: Thu, 25 Aug 2011 14:34:49 +1200
From: Robin Sheat <robin at catalyst.net.nz>
Subject: Re: [Koha-devel] [Koha] Koha 3.4.4 is now available
To: koha-devel at lists.koha-community.org
Message-ID: <1314239689.3396.120.camel at zarathud>
Content-Type: text/plain; charset="utf-8"

Somasekhar Rao K schreef op do 25-08-2011 om 08:02 [+0530]:
> Operating system: Debian 6.0 (Squeeze) using rackspace.com cloud
> server
>
> After execution of command
> sudo apt-get dselect-upgrade
>
> the output is something like this...

Those errors are completely unrelated to Koha.

Something like 'dpkg-reconfigure locale' may help with some of them
though.

--
Robin Sheat
Catalyst IT Ltd.
? +64 4 803 2204
GPG: 5957 6D23 8B16 EFAB FEF8  7175 14D3 6485 A99C EB6D
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL:
</pipermail/koha-devel/attachments/20110825/d6a7bf19/attachment-0001.pgp>

------------------------------

_______________________________________________
Koha-devel mailing list
Koha-devel at lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

End of Koha-devel Digest, Vol 69, Issue 35
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110825/eadd8997/attachment.htm>

From paivakil at gmail.com  Thu Aug 25 17:31:13 2011
From: paivakil at gmail.com (Mahesh T Pai)
Date: Thu, 25 Aug 2011 21:01:13 +0530
Subject: [Koha-devel] Regarding locale setting on Debian 6.0
References: <CAPzijSut=gsVAKx2Gc40j1h6PT__PzG04c1+Tu1RA7=vazuHtQ@mail.gmail.com>
Message-ID: <87k4a1h5j2.fsf@nandini.localhost>

Somasekhar Rao K <raosoma at gmail.com>
writes:

 > Hi,
>
 > I tried to set using 'dpkg-reconfigure locale'.
 > But still I got same errors.

It is "locales" not "locale". 




-- 
Mahesh T. Pai   ||
He is wise who knows the sources of knowledge --
who knows who has written and where it is to be found.
   --A.A. Hodge


From tdavis at uttyler.edu  Thu Aug 25 18:08:17 2011
From: tdavis at uttyler.edu (Elliott Davis)
Date: Thu, 25 Aug 2011 11:08:17 -0500
Subject: [Koha-devel] Notifications RFC
Message-ID: <8754F6E19960C249BB9C8FFECA62774001535D67D8@dogbert>

Hey Guys,

I have noticed of late that notifications is in quite a state of disarray.  At my library we have had to resort to running queries from a script and manually sending out mail because notifications just don't work in a usable way.  I am proposing an overhaul of the notifications system.  The only information I have to go on is what my library wants but since we are an academic library that may vary from what the vast majority of Koha wants.  Before I made an official wiki for this RFC I wanted to get a general feel for how everyone felt about this.  I also wanted to see if someone or a group was willing to pitch in and help me out with some coding.

Essentially what I would like to do is model notifications to do the following:


1.       Base notification rules on patron type, item type, and a new grouping I am hoping to write that I am calling the collection code

2.       Define a frequency for notifications based on the previously stated groupings

3.       Base the start time and end time for notifications on the due date rather than the checkout date

I am very open to other suggestions and I hope to get some.  I know that this idea is far from fully developed.

Best,

Elliott Davis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110825/ed5e61d6/attachment.htm>

From pianohacker at gmail.com  Thu Aug 25 21:00:09 2011
From: pianohacker at gmail.com (Jesse)
Date: Thu, 25 Aug 2011 13:00:09 -0600
Subject: [Koha-devel] Notifications RFC
In-Reply-To: <8754F6E19960C249BB9C8FFECA62774001535D67D8@dogbert>
References: <8754F6E19960C249BB9C8FFECA62774001535D67D8@dogbert>
Message-ID: <CAEjTV=_dbbz1xUzmXQrMMy0Qz0+P_o418Su5CMNnmC02F6eFiw@mail.gmail.com>

2011/8/25 Elliott Davis <tdavis at uttyler.edu>

> Hey Guys,****
>
> ** **
>
> I have noticed of late that notifications is in quite a state of disarray.
> At my library we have had to resort to running queries from a script and
> manually sending out mail because notifications just don?t work in a usable
> way.  I am proposing an overhaul of the notifications system.  The only
> information I have to go on is what my library wants but since we are an
> academic library that may vary from what the vast majority of Koha wants.
> Before I made an official wiki for this RFC I wanted to get a general feel
> for how everyone felt about this.  I also wanted to see if someone or a
> group was willing to pitch in and help me out with some coding.****
>
> ** **
>
> Essentially what I would like to do is model notifications to do the
> following: ****
>
> ** **
>
> **1.       **Base notification rules on patron type, item type, and a new
> grouping I am hoping to write that I am calling the collection code
>
This sounds like it's a bit up in the air at the moment, but how does this
relate to the item collection codes that are already in Koha?

> ****
>
> 2.       Define a frequency for notifications based on the previously
> stated groupings
>
> **3.       **Base the start time and end time for notifications on the due
> date rather than the checkout date****
>
> ** **
>
> I am very open to other suggestions and I hope to get some.  I know that
> this idea is far from fully developed.****
>
> ** **
>
> Best,****
>
> ** **
>
> Elliott Davis****
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>

Everything else sounds good. The notifications backend is pretty good,
really, but the UI at least needs some love and updates.

-- 
Jesse Weaver
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110825/273def54/attachment-0001.htm>

From tdavis at uttyler.edu  Thu Aug 25 21:59:43 2011
From: tdavis at uttyler.edu (Elliott Davis)
Date: Thu, 25 Aug 2011 14:59:43 -0500
Subject: [Koha-devel] Notifications RFC
In-Reply-To: <CAEjTV=_dbbz1xUzmXQrMMy0Qz0+P_o418Su5CMNnmC02F6eFiw@mail.gmail.com>
References: <8754F6E19960C249BB9C8FFECA62774001535D67D8@dogbert>
	<CAEjTV=_dbbz1xUzmXQrMMy0Qz0+P_o418Su5CMNnmC02F6eFiw@mail.gmail.com>
Message-ID: <8754F6E19960C249BB9C8FFECA62774001536986C9@dogbert>

Jesse,

In response to your first question, it will correspond directly to the collection codes that are currently in koha.  Essentially what I would like to do is give users another dimension of control when defining overdue rules.  For example, If I have 10 items with the collection code of ?media? then I would like to set a blanket rule for ?media? instead of having to set a rule for each separate item.

The thing I really want to get changed on the backend is the 3 notification limit.  Currently for our ILL?s we send out notices every day until the end of time or until the book is returned.

Let me know if that makes sense or if I am totally crazy.

Elliott Davis

From: Jesse [mailto:pianohacker at gmail.com]
Sent: Thursday, August 25, 2011 2:00 PM
To: Elliott Davis
Cc: koha-devel at lists.koha-community.org
Subject: Re: [Koha-devel] Notifications RFC


2011/8/25 Elliott Davis <tdavis at uttyler.edu<mailto:tdavis at uttyler.edu>>
Hey Guys,

I have noticed of late that notifications is in quite a state of disarray.  At my library we have had to resort to running queries from a script and manually sending out mail because notifications just don?t work in a usable way.  I am proposing an overhaul of the notifications system.  The only information I have to go on is what my library wants but since we are an academic library that may vary from what the vast majority of Koha wants.  Before I made an official wiki for this RFC I wanted to get a general feel for how everyone felt about this.  I also wanted to see if someone or a group was willing to pitch in and help me out with some coding.

Essentially what I would like to do is model notifications to do the following:


1.       Base notification rules on patron type, item type, and a new grouping I am hoping to write that I am calling the collection code
This sounds like it's a bit up in the air at the moment, but how does this relate to the item collection codes that are already in Koha?

2.       Define a frequency for notifications based on the previously stated groupings

3.       Base the start time and end time for notifications on the due date rather than the checkout date

I am very open to other suggestions and I hope to get some.  I know that this idea is far from fully developed.

Best,

Elliott Davis

_______________________________________________
Koha-devel mailing list
Koha-devel at lists.koha-community.org<mailto:Koha-devel at lists.koha-community.org>
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Everything else sounds good. The notifications backend is pretty good, really, but the UI at least needs some love and updates.

--
Jesse Weaver
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110825/3bade025/attachment.htm>

From danielg.koha at gmail.com  Thu Aug 25 23:47:19 2011
From: danielg.koha at gmail.com (Daniel Grobani)
Date: Thu, 25 Aug 2011 14:47:19 -0700
Subject: [Koha-devel] Official Koha Newsletter : Volume 2,
	Issue 8: August 2011
Message-ID: <CAOeKewgtBoMQ+rYRQNtBX9KZ0ZEOBJXDdm4hEzgravRY3C3qkQ@mail.gmail.com>

[Below is the text of the newsletter. For active links and a more readable
format, please visit
http://koha-community.org/koha-newsletter-volume-2issue-8-august-2011]

Official Koha Newsletter (ISSN 2153-8328)
Volume 2, Issue 8: August 2011

Edited by Daniel Grobani, Koha Community Newsletter Editor.

Table of Contents

    Koha Developments
        Koha 3.4.4 Available
        Koha 3.6 Update
        Koha 3.2 End-of-Life
    Koha Community
        New Koha Libraries
        Community Gossip
    Past Koha Events
        New Zealand Koha Users Group Meeting
        Global Bug Squashing Day #3
        August General IRC Meeting
    Upcoming Koha Events
        Global Bug Squashing Day #4
        September General IRC Meeting
        KohaCon11
        KohaCon12

Koha Developments

Koha 3.4.4 Available
by Chris Nighswonger

It is with pleasure that I announce the release of Koha 3.4.4.

The package can be retrieved from:

http://download.koha-community.org/koha-3.04.04.tar.gz

You can use the following checksum and signature files to verify the
download:

http://download.koha-community.org/koha-3.04.04.tar.gz.MD5
http://download.koha-community.org/koha-3.04.04.tar.gz.MD5.asc
http://download.koha-community.org/koha-3.04.04.tar.gz.sig

Release notes for 3.4.4 are below the fold.

Come and get it!

Continue reading ?Koha 3.4.4 Available?

Koha 3.6 Update
by Chris Cormack

We are rapidly closing in on the 3.6.0 release, so I thought it would be
good remind everyone of the key dates.

    Feature freeze ? 22 September 23:59 UTC ? From this point on, no new
features will be considered for inclusion into 3.6.0
    String freeze ? 8 October 23:59 UTC ? no bugs that change templates
accepted after this point. This allows the translators to translate without
things changing on them
    Translations finished ? 18 October 23:59 UTC ? Translations submitted,
so that they can be tested before release
    Release ? 22 October

Koha 3.2 End-of-Life

It was decided at the August general IRC meeting that Koha 3.2 has reached
the end of its life.
Koha Community

New Koha Libraries

    C.G. Jung Institute of New York (via ByWater Solutions)
    CAUSE (Comfort for America?s Uniformed Services) (via ByWater Solutions)
    Centenary College (via ByWater Solutions)
    Central Kansas Library System (via ByWater Solutions)
    All schools in the Canadian province of Prince Edward Island are now
using Koha.

Community Gossip

Paul Poulain of BibLibre is assisting 3.6 Quality Assurance Manager Ian
Walls in reducing the backlog of patches waiting for QA testing.

Lori Bowen Ayre is working on a spreadsheet comparing Evergreen & Koha
features.

Brenda Chawner asked community members several years ago to complete a
survey as part of her PhD research on factors affecting satisfaction with
the experience of a free/libre open source software project. Brenda recently
thanked the community and provided an abstract of her PhD thesis. For more
info, see http://markmail.org/message/gdofvpmbgseao2vb.

Joy Nelson joined ByWater Solutions as their Migration Support Specialist.

Melia Meggs joined ByWater Solutions as their Operations Manager.

Hal Bright reports that the Farmington Libraries has integrated its Koha
database into a mobile app powered by the Boopsie company in cooperation
with its vendor, ByWater Solutions. For more info and a demo, see
http://flct.boopsie.com.

Equinox Software is looking to hire a Library Data and Support Specialist.

ByWater Solutions is looking to hire a Perl developer for their support
desk.
Past Koha Events

New Zealand Koha Users Group Meeting
by Chris Cormack

Today I had the great fortune of attending the first New Zealand Koha users
group meeting, in the birthplace of Koha, Horowhenua. There were 51
attendees and even road closures and snow didn?t stop people attending.
There was a really good mix of Library types, I think 18 from Publics, 18
from specials, and the rest schools, corporate and academic.

It was run as an unconference so the first task of the day was to decide
what would be talked about the rest of the day. The programme that we came
up with was:

    The community ? How to get involved and make the most
    Installation/migration/training and why should we use Koha
    Features ? what?s there, and what would we like added
    Serials, acquisitions, cataloguing
    Managing digital resources
    Consortia
    And one other I have forgotten

The discussions went really well, with lots of participation. It definitely
won?t be the last meeting, I think we are leaning towards 2 a year but
that?s something that will be decided on the mailing lists.

While we were busy plotting plans to take over the world, (or at least New
Zealand) Koha 3.4.3 was released.

Global Bug Squashing Day #3
by Magnus Enger

Global bug squashing days are dedicated to getting bugs and patches moving
toward resolution.

The third GBSD coincided with holidays and other obligations for some
people, but we still managed to move a fair number of bugs along. These
numbers below show how many bugs were moved to a new status during the day:

    Needs Signoff: 13
    Signed Off: 12
    Passed QA: 6
    Pushed: 11
    Resolved: 30

For more info, see
http://wiki.koha-community.org/wiki/2011-08-05_Global_bug_squashing_day.

August General IRC Meeting

The August general IRC meeting was held on 2 August 2011. Highlights from
the meeting include:

    Koha 3.2 has reached its end of life.
    The bare minimum requirement for a vendor to be listed on the community
website is a visible link to the community website on the main Koha page of
the vendor?s website.
    Daniel Grobani is the new newsletter editor.
    Those interested in a role in 3.8 should express interest to the mailing
list by 22 September for an October election.

For more info, including links to the minutes, see
http://wiki.koha-community.org/wiki/General_IRC_Meeting,_2_August_2011.
Upcoming Koha Events

Global Bug Squashing Day #4

The next GBSD will occur on Friday, 2 September 2011. For more info, see
http://wiki.koha-community.org/wiki/2011-09-02_Global_bug_squashing_day.

September General IRC Meeting

The next general IRC meeting is 7 September 2011 1800 UTC. For more info,
see
http://wiki.koha-community.org/wiki/General_IRC_Meeting,_7_September_2011.

KohaCon11

KohaCon11 will be held 31 October 2011 to 6 November 2011 in Thane, India.

The organizers have extended the deadline for submitting papers from 15
August to 30 August 2011.

For more info, see http://wiki.koha-community.org/wiki/Category:KohaCon11 or
http://kohacon11.vpmthane.org/ocs/index.php/k/k11.

KohaCon12

Proposals for KohaCon12 are being accepted until 1 September 2011. Voting
will take place through 1 October 2011.

Proposals have been made by software.coop in the UK and Washoe County
Library System in Reno, Nevada, USA.

For more info, see http://wiki.koha-community.org/wiki/Category:KohaCon12.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110825/fba80c0e/attachment-0001.htm>

From chris at bigballofwax.co.nz  Thu Aug 25 23:49:57 2011
From: chris at bigballofwax.co.nz (Chris Cormack)
Date: Fri, 26 Aug 2011 09:49:57 +1200
Subject: [Koha-devel] Official Koha Newsletter : Volume 2,
	Issue 8: August 2011
In-Reply-To: <CAOeKewgtBoMQ+rYRQNtBX9KZ0ZEOBJXDdm4hEzgravRY3C3qkQ@mail.gmail.com>
References: <CAOeKewgtBoMQ+rYRQNtBX9KZ0ZEOBJXDdm4hEzgravRY3C3qkQ@mail.gmail.com>
Message-ID: <CA+95qVSO2CHGv5sXykKHqjc+6+0sUeWCLffGhtO1-y5iYMYFxA@mail.gmail.com>

2011/8/26 Daniel Grobani <danielg.koha at gmail.com>:
> [Below is the text of the newsletter. For active links and a more readable
> format, please visit
> http://koha-community.org/koha-newsletter-volume-2issue-8-august-2011]
>

Congrats on your first newsletter as Editor Daniel, good job, long may
it continue :)

Chris

From jransom at library.org.nz  Fri Aug 26 00:39:05 2011
From: jransom at library.org.nz (Joann Ransom)
Date: Fri, 26 Aug 2011 10:39:05 +1200
Subject: [Koha-devel] [Koha] Official Koha Newsletter : Volume 2,
	Issue 8: August 2011
In-Reply-To: <CAOeKewgtBoMQ+rYRQNtBX9KZ0ZEOBJXDdm4hEzgravRY3C3qkQ@mail.gmail.com>
References: <CAOeKewgtBoMQ+rYRQNtBX9KZ0ZEOBJXDdm4hEzgravRY3C3qkQ@mail.gmail.com>
Message-ID: <CANMJezzHuTCCU0h6Dox-9EJwcBLHq+RUfvWM5Bq0OY7BJmPheg@mail.gmail.com>

Great newsletter Daniel - you'lll have to frame it as your first one!

2011/8/26 Daniel Grobani <danielg.koha at gmail.com>

> [Below is the text of the newsletter. For active links and a more readable
> format, please visit
> http://koha-community.org/koha-newsletter-volume-2issue-8-august-2011]
>
> Official Koha Newsletter (ISSN 2153-8328)
> Volume 2, Issue 8: August 2011
>
> Edited by Daniel Grobani, Koha Community Newsletter Editor.
>
> Table of Contents
>
>     Koha Developments
>         Koha 3.4.4 Available
>         Koha 3.6 Update
>         Koha 3.2 End-of-Life
>     Koha Community
>         New Koha Libraries
>         Community Gossip
>     Past Koha Events
>         New Zealand Koha Users Group Meeting
>         Global Bug Squashing Day #3
>         August General IRC Meeting
>     Upcoming Koha Events
>         Global Bug Squashing Day #4
>         September General IRC Meeting
>         KohaCon11
>         KohaCon12
>
> Koha Developments
>
> Koha 3.4.4 Available
> by Chris Nighswonger
>
> It is with pleasure that I announce the release of Koha 3.4.4.
>
> The package can be retrieved from:
>
> http://download.koha-community.org/koha-3.04.04.tar.gz
>
> You can use the following checksum and signature files to verify the
> download:
>
> http://download.koha-community.org/koha-3.04.04.tar.gz.MD5
> http://download.koha-community.org/koha-3.04.04.tar.gz.MD5.asc
> http://download.koha-community.org/koha-3.04.04.tar.gz.sig
>
> Release notes for 3.4.4 are below the fold.
>
> Come and get it!
>
> Continue reading ?Koha 3.4.4 Available?
>
> Koha 3.6 Update
> by Chris Cormack
>
> We are rapidly closing in on the 3.6.0 release, so I thought it would be
> good remind everyone of the key dates.
>
>     Feature freeze ? 22 September 23:59 UTC ? From this point on, no new
> features will be considered for inclusion into 3.6.0
>     String freeze ? 8 October 23:59 UTC ? no bugs that change templates
> accepted after this point. This allows the translators to translate without
> things changing on them
>     Translations finished ? 18 October 23:59 UTC ? Translations submitted,
> so that they can be tested before release
>     Release ? 22 October
>
> Koha 3.2 End-of-Life
>
> It was decided at the August general IRC meeting that Koha 3.2 has reached
> the end of its life.
> Koha Community
>
> New Koha Libraries
>
>     C.G. Jung Institute of New York (via ByWater Solutions)
>     CAUSE (Comfort for America?s Uniformed Services) (via ByWater
> Solutions)
>     Centenary College (via ByWater Solutions)
>     Central Kansas Library System (via ByWater Solutions)
>     All schools in the Canadian province of Prince Edward Island are now
> using Koha.
>
> Community Gossip
>
> Paul Poulain of BibLibre is assisting 3.6 Quality Assurance Manager Ian
> Walls in reducing the backlog of patches waiting for QA testing.
>
> Lori Bowen Ayre is working on a spreadsheet comparing Evergreen & Koha
> features.
>
> Brenda Chawner asked community members several years ago to complete a
> survey as part of her PhD research on factors affecting satisfaction with
> the experience of a free/libre open source software project. Brenda recently
> thanked the community and provided an abstract of her PhD thesis. For more
> info, see http://markmail.org/message/gdofvpmbgseao2vb.
>
> Joy Nelson joined ByWater Solutions as their Migration Support Specialist.
>
> Melia Meggs joined ByWater Solutions as their Operations Manager.
>
> Hal Bright reports that the Farmington Libraries has integrated its Koha
> database into a mobile app powered by the Boopsie company in cooperation
> with its vendor, ByWater Solutions. For more info and a demo, see
> http://flct.boopsie.com.
>
> Equinox Software is looking to hire a Library Data and Support Specialist.
>
> ByWater Solutions is looking to hire a Perl developer for their support
> desk.
> Past Koha Events
>
> New Zealand Koha Users Group Meeting
> by Chris Cormack
>
> Today I had the great fortune of attending the first New Zealand Koha users
> group meeting, in the birthplace of Koha, Horowhenua. There were 51
> attendees and even road closures and snow didn?t stop people attending.
> There was a really good mix of Library types, I think 18 from Publics, 18
> from specials, and the rest schools, corporate and academic.
>
> It was run as an unconference so the first task of the day was to decide
> what would be talked about the rest of the day. The programme that we came
> up with was:
>
>     The community ? How to get involved and make the most
>     Installation/migration/training and why should we use Koha
>     Features ? what?s there, and what would we like added
>     Serials, acquisitions, cataloguing
>     Managing digital resources
>     Consortia
>     And one other I have forgotten
>
> The discussions went really well, with lots of participation. It definitely
> won?t be the last meeting, I think we are leaning towards 2 a year but
> that?s something that will be decided on the mailing lists.
>
> While we were busy plotting plans to take over the world, (or at least New
> Zealand) Koha 3.4.3 was released.
>
> Global Bug Squashing Day #3
> by Magnus Enger
>
> Global bug squashing days are dedicated to getting bugs and patches moving
> toward resolution.
>
> The third GBSD coincided with holidays and other obligations for some
> people, but we still managed to move a fair number of bugs along. These
> numbers below show how many bugs were moved to a new status during the day:
>
>     Needs Signoff: 13
>     Signed Off: 12
>     Passed QA: 6
>     Pushed: 11
>     Resolved: 30
>
> For more info, see
> http://wiki.koha-community.org/wiki/2011-08-05_Global_bug_squashing_day.
>
> August General IRC Meeting
>
> The August general IRC meeting was held on 2 August 2011. Highlights from
> the meeting include:
>
>     Koha 3.2 has reached its end of life.
>     The bare minimum requirement for a vendor to be listed on the community
> website is a visible link to the community website on the main Koha page of
> the vendor?s website.
>     Daniel Grobani is the new newsletter editor.
>     Those interested in a role in 3.8 should express interest to the
> mailing list by 22 September for an October election.
>
> For more info, including links to the minutes, see
> http://wiki.koha-community.org/wiki/General_IRC_Meeting,_2_August_2011.
> Upcoming Koha Events
>
> Global Bug Squashing Day #4
>
> The next GBSD will occur on Friday, 2 September 2011. For more info, see
> http://wiki.koha-community.org/wiki/2011-09-02_Global_bug_squashing_day.
>
> September General IRC Meeting
>
> The next general IRC meeting is 7 September 2011 1800 UTC. For more info,
> see
> http://wiki.koha-community.org/wiki/General_IRC_Meeting,_7_September_2011.
>
> KohaCon11
>
> KohaCon11 will be held 31 October 2011 to 6 November 2011 in Thane, India.
>
> The organizers have extended the deadline for submitting papers from 15
> August to 30 August 2011.
>
> For more info, see http://wiki.koha-community.org/wiki/Category:KohaCon11or
> http://kohacon11.vpmthane.org/ocs/index.php/k/k11.
>
> KohaCon12
>
> Proposals for KohaCon12 are being accepted until 1 September 2011. Voting
> will take place through 1 October 2011.
>
> Proposals have been made by software.coop in the UK and Washoe County
> Library System in Reno, Nevada, USA.
>
> For more info, see http://wiki.koha-community.org/wiki/Category:KohaCon12.
>
> _______________________________________________
> Koha mailing list  http://koha-community.org
> Koha at lists.katipo.co.nz
> http://lists.katipo.co.nz/mailman/listinfo/koha
>
>


-- 
Joann Ransom RLIANZA
Head of Libraries,
Horowhenua Library Trust.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110826/3c8b83de/attachment.htm>

From mtj at kohaaloha.com  Fri Aug 26 05:47:23 2011
From: mtj at kohaaloha.com (Mason James)
Date: Fri, 26 Aug 2011 15:47:23 +1200
Subject: [Koha-devel] Notifications RFC
In-Reply-To: <8754F6E19960C249BB9C8FFECA62774001535D67D8@dogbert>
References: <8754F6E19960C249BB9C8FFECA62774001535D67D8@dogbert>
Message-ID: <A86F3D4D-5287-491E-9890-2D95C7193332@kohaaloha.com>


On 2011-08-26, at 4:08 AM, Elliott Davis wrote:

> Hey Guys,
>  
> I have noticed of late that notifications is in quite a state of disarray.  

snip

>  
> Essentially what I would like to do is model notifications to do the following:
>  
> 1.       Base notification rules on patron type, item type, and a new grouping I am hoping to write that I am calling the collection code
> 2.       Define a frequency for notifications based on the previously stated groupings
> 3.       Base the start time and end time for notifications on the due date rather than the checkout date
>  

fyi, Koha's notifications not doing feature (x,y,z) does not equal 'in quite a state of disarray'

last time i looked the code was pretty clean and extendable?


From mtj at kohaaloha.com  Fri Aug 26 08:24:10 2011
From: mtj at kohaaloha.com (Mason James)
Date: Fri, 26 Aug 2011 18:24:10 +1200
Subject: [Koha-devel] Notifications RFC
In-Reply-To: <A86F3D4D-5287-491E-9890-2D95C7193332@kohaaloha.com>
References: <8754F6E19960C249BB9C8FFECA62774001535D67D8@dogbert>
	<A86F3D4D-5287-491E-9890-2D95C7193332@kohaaloha.com>
Message-ID: <22B53E46-A6F4-438B-8138-D4427850AC38@kohaaloha.com>


On 2011-08-26, at 3:47 PM, Mason James wrote:

> 
> On 2011-08-26, at 4:08 AM, Elliott Davis wrote:
> 
>> Hey Guys,
>> 
>> I have noticed of late that notifications is in quite a state of disarray.  
> 
> snip
> 
>> 
>> Essentially what I would like to do is model notifications to do the following:
>> 
>> 1.       Base notification rules on patron type, item type, and a new grouping I am hoping to write that I am calling the collection code
>> 2.       Define a frequency for notifications based on the previously stated groupings
>> 3.       Base the start time and end time for notifications on the due date rather than the checkout date
>> 
> 
> fyi, Koha's notifications not doing feature (x,y,z) does not equal 'in quite a state of disarray'
> 
> last time i looked the code was pretty clean and extendable?
> 

ooh, my last comment sounded a little condescending there :/ (friday brain)

but hey, my point still stands...
the notifications code could be modded to handle your 3 features without to much trouble, i reckon...

From ian.walls at bywatersolutions.com  Fri Aug 26 14:28:58 2011
From: ian.walls at bywatersolutions.com (Ian Walls)
Date: Fri, 26 Aug 2011 08:28:58 -0400
Subject: [Koha-devel] Notifications RFC
In-Reply-To: <22B53E46-A6F4-438B-8138-D4427850AC38@kohaaloha.com>
References: <8754F6E19960C249BB9C8FFECA62774001535D67D8@dogbert>
	<A86F3D4D-5287-491E-9890-2D95C7193332@kohaaloha.com>
	<22B53E46-A6F4-438B-8138-D4427850AC38@kohaaloha.com>
Message-ID: <CAE2wdZx7CYhHKc8qN_=VD+rwOWT_wQTP97a6Vs33iCHPArhrkA@mail.gmail.com>

Problems I see with Notices:

   - Overdues are limited to 3 per patron.  This needs to be unlimited, so a
   more robust triggering methodology needs to be put into place, along with
   tie-ins to fines and privilege restriction
   - Advance notices are limited to 1 predue and 1 due.
   - Overdues have two competing syntaxes for item information,
   <<items.content>> and <item></item>, neither of which are particularly
   good.
   - <item/> is only supported in Overdues, not in any of the Advance
      Notices or Hold notifications
      - <<items.content>> has to be specified on the commandline, adding
      sysadmin's to the customization process.
      - Predue and Due both have separate digest forms, instead of notation
   that could be flexible enough to handle one or multiple items at a time.
   - Advance Notices cannot be mandated by the library like Overdues are;
   what if you want to guarantee your patrons are being sent hold notices?
   - Overdues cannot be opted into by patrons (I can see no opt-out, but
   what if you've configured a patron category to not receive overdues, and
   someone within that category wants to be notified because they're
   responsible, if a little forgetful?)
   - Handling of notices to people without email addresses is inconsistent.
   - For overdues (and possibly advance notices as well) the Koha branch
      email or admin email are sent the document of all the
undeliverable message.
      - For holds, a completely different HOLD_PRINT notice form is used, as
      well as a separate script to gather the notices, in HTML, into a
directory
      somewhere on the Koha server.
      - Overdues and Advance Notices have an HTML option, which works
      completely differently, but produces the same net effect:
notices files on
      the server
      - Nothing for checking/checkout notices
   - Notices are mostly in plain text (except HOLD_PRINT).  Should have HTML
   option, with a WYSIWYG editor.
   - Message sending is sometimes handled by "process_message_queue", and
   other times the messages are sent directly
   - Overdue, Advance and Holds notices are completely incompatible with
   Hourly Loans at this time
   - Hold notices are broken out by Branch, Overdues can be too, but
   Advanced Notices are global.  The use of the <<branch>> token has proven
   quite buggy in my experience
   - Meaning of "branch" can be unclear in some notice circumstances.  Is it
   the patron's branch?  the item's branch?  The checkout branch?  The
   currently-logged in branch?  Should it follow CircControl?
   HomeOrHoldingBranch? HomeOrHoldBranchReturn?  None?  All, in different
   cases?
   - SMS is not sufficiently supported; there are character limits that need
   to be factored in.
   - Notices do not make use of "reply-to" headers, which would make it much
   easier for the conversation to continue, without having to fine-tune the
   mail server settings on the Koha machine to match the addresses of the
   branch administrators.


So, I'm with Elliott.  The system needs an overhaul.  The difficult now
comes with figuring out how to actually accomplish all this in the real
world.  I recommend:

   1. more discussions to nail down a complete specification that meets as
   many libraries' needs as possible
   2. a meeting of the development team (whoever is willing to help) to
   figure out the core architectural changes required, then allocating work
   3. filing separate bugs for each small component, with Depends On and
   Blocks links.
   4. Signoffs and QA on bugs 'in order', that is starting with those that
   form the baseline of dependencies, then building off them once they're in
   master.
   5. Public test server so that librarians can easily check that the
   specifications they laid out in the first place are actually met

Who's up for the challenge?


-Ian

On Fri, Aug 26, 2011 at 2:24 AM, Mason James <mtj at kohaaloha.com> wrote:

>
> On 2011-08-26, at 3:47 PM, Mason James wrote:
>
> >
> > On 2011-08-26, at 4:08 AM, Elliott Davis wrote:
> >
> >> Hey Guys,
> >>
> >> I have noticed of late that notifications is in quite a state of
> disarray.
> >
> > snip
> >
> >>
> >> Essentially what I would like to do is model notifications to do the
> following:
> >>
> >> 1.       Base notification rules on patron type, item type, and a new
> grouping I am hoping to write that I am calling the collection code
> >> 2.       Define a frequency for notifications based on the previously
> stated groupings
> >> 3.       Base the start time and end time for notifications on the due
> date rather than the checkout date
> >>
> >
> > fyi, Koha's notifications not doing feature (x,y,z) does not equal 'in
> quite a state of disarray'
> >
> > last time i looked the code was pretty clean and extendable?
> >
>
> ooh, my last comment sounded a little condescending there :/ (friday brain)
>
> but hey, my point still stands...
> the notifications code could be modded to handle your 3 features without to
> much trouble, i reckon...
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>



-- 
Ian Walls
Lead Development Specialist
ByWater Solutions
Phone # (888) 900-8944
http://bywatersolutions.com
ian.walls at bywatersolutions.com
Twitter: @sekjal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110826/5b0e2459/attachment.htm>

From laurenthdl at alinto.com  Fri Aug 26 14:39:05 2011
From: laurenthdl at alinto.com (LAURENT Henri-Damien)
Date: Fri, 26 Aug 2011 14:39:05 +0200
Subject: [Koha-devel] Notifications RFC
In-Reply-To: <CAE2wdZx7CYhHKc8qN_=VD+rwOWT_wQTP97a6Vs33iCHPArhrkA@mail.gmail.com>
References: <8754F6E19960C249BB9C8FFECA62774001535D67D8@dogbert>	<A86F3D4D-5287-491E-9890-2D95C7193332@kohaaloha.com>	<22B53E46-A6F4-438B-8138-D4427850AC38@kohaaloha.com>
	<CAE2wdZx7CYhHKc8qN_=VD+rwOWT_wQTP97a6Vs33iCHPArhrkA@mail.gmail.com>
Message-ID: <4E5793E9.5060506@alinto.com>

Le 26/08/2011 14:28, Ian Walls a ?crit :
> Problems I see with Notices:
> 
>     * Overdues are limited to 3 per patron.  This needs to be unlimited,
>       so a more robust triggering methodology needs to be put into
>       place, along with tie-ins to fines and privilege restriction
>     * Advance notices are limited to 1 predue and 1 due.
>     * Overdues have two competing syntaxes for item information,
>       <<items.content>> and <item></item>, neither of which are
>       particularly good. 
>           o <item/> is only supported in Overdues, not in any of the
>             Advance Notices or Hold notifications 
>           o <<items.content>> has to be specified on the commandline,
>             adding sysadmin's to the customization process.
>     * Predue and Due both have separate digest forms, instead of
>       notation that could be flexible enough to handle one or multiple
>       items at a time.
>     * Advance Notices cannot be mandated by the library like Overdues
>       are; what if you want to guarantee your patrons are being sent
>       hold notices?
>     * Overdues cannot be opted into by patrons (I can see no opt-out,
>       but what if you've configured a patron category to not receive
>       overdues, and someone within that category wants to be notified
>       because they're responsible, if a little forgetful?)
>     * Handling of notices to people without email addresses is
>       inconsistent.
>           o For overdues (and possibly advance notices as well) the Koha
>             branch email or admin email are sent the document of all the
>             undeliverable message.
>           o For holds, a completely different HOLD_PRINT notice form is
>             used, as well as a separate script to gather the notices, in
>             HTML, into a directory somewhere on the Koha server. 
>           o Overdues and Advance Notices have an HTML option, which
>             works completely differently, but produces the same net
>             effect: notices files on the server
>           o Nothing for checking/checkout notices
>     * Notices are mostly in plain text (except HOLD_PRINT).  Should have
>       HTML option, with a WYSIWYG editor.
>     * Message sending is sometimes handled by "process_message_queue",
>       and other times the messages are sent directly
>     * Overdue, Advance and Holds notices are completely incompatible
>       with Hourly Loans at this time
>     * Hold notices are broken out by Branch, Overdues can be too, but
>       Advanced Notices are global.  The use of the <<branch>> token has
>       proven quite buggy in my experience
>     * Meaning of "branch" can be unclear in some notice circumstances. 
>       Is it the patron's branch?  the item's branch?  The checkout
>       branch?  The currently-logged in branch?  Should it follow
>       CircControl?  HomeOrHoldingBranch? HomeOrHoldBranchReturn?  None? 
>       All, in different cases?
>     * SMS is not sufficiently supported; there are character limits that
>       need to be factored in.
>     * Notices do not make use of "reply-to" headers, which would make it
>       much easier for the conversation to continue, without having to
>       fine-tune the mail server settings on the Koha machine to match
>       the addresses of the branch administrators.
> 
> 
> So, I'm with Elliott.  The system needs an overhaul.  The difficult now
> comes with figuring out how to actually accomplish all this in the real
> world.  I recommend:
> 
>    1. more discussions to nail down a complete specification that meets
>       as many libraries' needs as possible
>    2. a meeting of the development team (whoever is willing to help) to
>       figure out the core architectural changes required, then
>       allocating work
>    3. filing separate bugs for each small component, with Depends On and
>       Blocks links.
>    4. Signoffs and QA on bugs 'in order', that is starting with those
>       that form the baseline of dependencies, then building off them
>       once they're in master.
>    5. Public test server so that librarians can easily check that the
>       specifications they laid out in the first place are actually met
> 
> Who's up for the challenge?
> 
> 
> -Ian
> 

Maybe it needs overhaul.
But some people already proposed something for that years ago
C4::Mailer.
It uses C4::Mailer for all the messages and a Template::Toolkit
definition for messaging. And tried to assign all the problems of the
Notification system.

One can see that there :
https://github.com/xercode/koha

has anyone tested it ?
About some of the problems raised by Elliot, it is not only notification
system but also issuing rules that would need overhaul... itemtypes, and
all that.
It would be nice to write some design with as many libraries as possible
and not only a few developers... Since those things are impacting Koha
as a whole.
My 2 cents.
-- 
Henri-Damien LAURENT
BibLibre

From cmurdock at ccfls.org  Fri Aug 26 16:56:35 2011
From: cmurdock at ccfls.org (Cindy Murdock Ames)
Date: Fri, 26 Aug 2011 10:56:35 -0400
Subject: [Koha-devel] Notifications RFC
In-Reply-To: <CAE2wdZx7CYhHKc8qN_=VD+rwOWT_wQTP97a6Vs33iCHPArhrkA@mail.gmail.com>
References: <8754F6E19960C249BB9C8FFECA62774001535D67D8@dogbert>	<A86F3D4D-5287-491E-9890-2D95C7193332@kohaaloha.com>	<22B53E46-A6F4-438B-8138-D4427850AC38@kohaaloha.com>
	<CAE2wdZx7CYhHKc8qN_=VD+rwOWT_wQTP97a6Vs33iCHPArhrkA@mail.gmail.com>
Message-ID: <4E57B423.1030907@ccfls.org>

Another thing that would be nice would be the ability to specify which 
level of notices to produce (First, Second, Third, etc).  I was fiddling 
around with notices yesterday, and if you produce an html file for them, 
you can tell which is which because of the differences in the notices 
template for each level.  But if you produce a csv file, you can't tell 
which is which because it just outputs the data into the file.  We have 
a library that wants to mail their overdue notices, and they're not 
entirely happy with how the html output prints, and they could use the 
csv file for mail merge in a word processor, but since it lumps all the 
levels together, there's no way to tell which level they are.

Cheers,
Cindy

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Cindy Murdock Ames
IT Services Director
Meadville Public Library    | CCFLS
http://meadvillelibrary.org | http://ccfls.org


From jwagner at liblime.com  Fri Aug 26 16:59:15 2011
From: jwagner at liblime.com (Wagner, Jane)
Date: Fri, 26 Aug 2011 10:59:15 -0400
Subject: [Koha-devel] Notifications RFC
In-Reply-To: <4E57B423.1030907@ccfls.org>
References: <8754F6E19960C249BB9C8FFECA62774001535D67D8@dogbert>
	<A86F3D4D-5287-491E-9890-2D95C7193332@kohaaloha.com>	<22B53E46-A6F4-438B-8138-D4427850AC38@kohaaloha.com>
	<CAE2wdZx7CYhHKc8qN_=VD+rwOWT_wQTP97a6Vs33iCHPArhrkA@mail.gmail.com>
	<4E57B423.1030907@ccfls.org>
Message-ID: <b85bdc5be622cc1ea2610c8b4e9a1d17@mail.gmail.com>

You should be able to select for that based on the letter_code field,
assuming you're using different notice files for each level.  For example:

select * from message_queue where letter_code = 'ODUE3' order by
time_queued desc

should produce only third overdue messages.

Jane Wagner
Senior Project Manager
LibLime, a division of PTFS
Content Management and Library Solutions
6400 Goldsboro Road, Suite 200
Bethesda, MD  20817
(301) 654-8088 x 151
jwagner at liblime.com


-----Original Message-----
From: koha-devel-bounces at lists.koha-community.org
[mailto:koha-devel-bounces at lists.koha-community.org] On Behalf Of Cindy
Murdock Ames
Sent: Friday, August 26, 2011 10:57 AM
To: koha-devel at lists.koha-community.org
Subject: Re: [Koha-devel] Notifications RFC

Another thing that would be nice would be the ability to specify which
level of notices to produce (First, Second, Third, etc).  I was fiddling
around with notices yesterday, and if you produce an html file for them,
you can tell which is which because of the differences in the notices
template for each level.  But if you produce a csv file, you can't tell
which is which because it just outputs the data into the file.  We have
a library that wants to mail their overdue notices, and they're not
entirely happy with how the html output prints, and they could use the
csv file for mail merge in a word processor, but since it lumps all the
levels together, there's no way to tell which level they are.

Cheers,
Cindy

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Cindy Murdock Ames
IT Services Director
Meadville Public Library    | CCFLS
http://meadvillelibrary.org | http://ccfls.org

_______________________________________________
Koha-devel mailing list
Koha-devel at lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

From ef at math.uni-bonn.de  Fri Aug 26 18:28:50 2011
From: ef at math.uni-bonn.de (=?iso-8859-1?Q?Edgar_Fu=DF?=)
Date: Fri, 26 Aug 2011 18:28:50 +0200
Subject: [Koha-devel] Sending acquisition orders per email: confirmation
In-Reply-To: <4E4E4C95.80106@koha-fr.org>
References: <bug-5260-145@http.bugs.koha-community.org/bugzilla3/>	<bug-5260-145-A9xe8rmDT5@http.bugs.koha-community.org/bugzilla3/>
	<8DA6ACE6-AE61-486B-901B-E7301691A3BC@math.uni-bonn.de>
	<4E4E4C95.80106@koha-fr.org>
Message-ID: <496A4651-09DB-4285-9494-7668E213CE9F@math.uni-bonn.de>

Regarding the feedback that the email has actually been sent, I can think of three ways to do that:

1. Add a field 'closeaction' to the basket hash complementing the 'closedate' field. Set that to empty, 'print' or 'email'. Display that information in acqui/booksellers.pl, acqui/basket.pl and acqui/bsketgroup.pl.

2. Use the message queue.

3. Don't send the email to the bookseller, but to yourself; forward it manually.

I'll probably look into implementing variant 1.

From laurenthdl at alinto.com  Fri Aug 26 18:55:25 2011
From: laurenthdl at alinto.com (LAURENT Henri-Damien)
Date: Fri, 26 Aug 2011 18:55:25 +0200
Subject: [Koha-devel] Sending acquisition orders per email: confirmation
In-Reply-To: <496A4651-09DB-4285-9494-7668E213CE9F@math.uni-bonn.de>
References: <bug-5260-145@http.bugs.koha-community.org/bugzilla3/>	<bug-5260-145-A9xe8rmDT5@http.bugs.koha-community.org/bugzilla3/>	<8DA6ACE6-AE61-486B-901B-E7301691A3BC@math.uni-bonn.de>	<4E4E4C95.80106@koha-fr.org>
	<496A4651-09DB-4285-9494-7668E213CE9F@math.uni-bonn.de>
Message-ID: <4E57CFFD.4010304@alinto.com>

Le 26/08/2011 18:28, Edgar Fu? a ?crit :
> Regarding the feedback that the email has actually been sent, I can think of three ways to do that:
> 
> 1. Add a field 'closeaction' to the basket hash complementing the 'closedate' field. Set that to empty, 'print' or 'email'. Display that information in acqui/booksellers.pl, acqui/basket.pl and acqui/bsketgroup.pl.
> 
> 2. Use the message queue.
> 
> 3. Don't send the email to the bookseller, but to yourself; forward it manually.
> 
> I'll probably look into implementing variant 1.
> _______________________________________________

I would have considered rather variant 2, but the thing is that the
status in message_queue donot actually mean it was received. It actually
mean Koha was able to send that, whether MTA rejected it, or failed to
process that or was considered as spam is out of its scope.
And we have some ongoing work on acquisitions you may want to see on
dev/stetienne.
feel free to test that branch on a development  environment.

From paul.a at aandc.org  Fri Aug 26 23:39:01 2011
From: paul.a at aandc.org (Paul)
Date: Fri, 26 Aug 2011 17:39:01 -0400
Subject: [Koha-devel] System design
Message-ID: <5.2.1.1.2.20110826163710.09932040@stormy.ca>

Our budget has finally allowed me a new "all singing, all dancing" server 
and it has physically arrived. Two questions if I may -- and if I'm off 
topic, plz say so:

1)  The system (Ubuntu 11.04) is being installed on a SSD (solid state 
drive) which recommends keeping "writes" to a minimum for longevity.  This 
obviously includes logs, etc, but not necessarily the sql database.  A 
quick "find / -iname" on the sandbox (Koha 3.02.05.000) for '*koha*' is 
enormous.

Does anyone have to hand a list of "system" versus "run-time" directories 
and files?  I'm particularly curious about Zebra (which I do not fully 
understand) as it appears to be proliferous and ubiquitous.

2)  I have stabilized a partially customized Koha 3.2.5 which is close to 
meeting our needs.  Koha 3.4 would be my choice on the new server (and I'm 
not worried about cosmetics -- CSS, etc) but how bullet-proof is the data 
conversion (as of now about 80,000 records)?

I truly want Koha to be our long term data solution for our holdings, but 
am still wet behind the ears with Koha, so all help would be appreciated.

Many thanks in advance for all suggestions.

Paul
Tired old sys-admin 


From ian.walls at bywatersolutions.com  Sat Aug 27 16:58:35 2011
From: ian.walls at bywatersolutions.com (Ian Walls)
Date: Sat, 27 Aug 2011 10:58:35 -0400
Subject: [Koha-devel] Maintenance on git.koha-community.org
Message-ID: <CAE2wdZz888cEgwoHL5xKRA21vW4KxP-Wx+x1VV3ibviZ6qTmBg@mail.gmail.com>

Dear community,


We have been experiencing downtime with community Git repo the last few
days, mainly from insufficient system resources.  ByWater Solutions, as the
maintainer of this server, has decided we need to allocate more resources to
the server in order to mitigate this issue and provide better uptime.

git.koha-community.org will be down for the next hour or so as we resize the
server.  We apologize for any inconvenience this may cause; please check the
wiki (http://wiki.koha-community.org/wiki/Public_Git_Repositories) for other
public repositories, including mirrors, if you need to obtain updated
patches in this downtime window.

I will notify everyone on this thread when the server is once again
available.

Thank you all for you patience and understanding.

Cheers,


-Ian

-- 
Ian Walls
Lead Development Specialist
ByWater Solutions
Phone # (888) 900-8944
http://bywatersolutions.com
ian.walls at bywatersolutions.com
Twitter: @sekjal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110827/affd3ebb/attachment.htm>

From ian.walls at bywatersolutions.com  Sat Aug 27 22:17:59 2011
From: ian.walls at bywatersolutions.com (Ian Walls)
Date: Sat, 27 Aug 2011 16:17:59 -0400
Subject: [Koha-devel] Maintenance on git.koha-community.org
In-Reply-To: <CAE2wdZz888cEgwoHL5xKRA21vW4KxP-Wx+x1VV3ibviZ6qTmBg@mail.gmail.com>
References: <CAE2wdZz888cEgwoHL5xKRA21vW4KxP-Wx+x1VV3ibviZ6qTmBg@mail.gmail.com>
Message-ID: <CAE2wdZxLAujdq9HSVhxm8jsJEBxMS=JcHuxLtqNCooa2o9cDkQ@mail.gmail.com>

The Koha community Git repository server is back up.

My apologies for the delay in update; it has actually been up and running
for a while now, but I've been pre-occupied with hurricane preparations.

Cheers,


-Ian

On Sat, Aug 27, 2011 at 10:58 AM, Ian Walls
<ian.walls at bywatersolutions.com>wrote:

> Dear community,
>
>
> We have been experiencing downtime with community Git repo the last few
> days, mainly from insufficient system resources.  ByWater Solutions, as the
> maintainer of this server, has decided we need to allocate more resources to
> the server in order to mitigate this issue and provide better uptime.
>
> git.koha-community.org will be down for the next hour or so as we resize
> the server.  We apologize for any inconvenience this may cause; please check
> the wiki (http://wiki.koha-community.org/wiki/Public_Git_Repositories) for
> other public repositories, including mirrors, if you need to obtain updated
> patches in this downtime window.
>
> I will notify everyone on this thread when the server is once again
> available.
>
> Thank you all for you patience and understanding.
>
> Cheers,
>
>
> -Ian
>
> --
> Ian Walls
> Lead Development Specialist
> ByWater Solutions
> Phone # (888) 900-8944
> http://bywatersolutions.com
> ian.walls at bywatersolutions.com
> Twitter: @sekjal
>



-- 
Ian Walls
Lead Development Specialist
ByWater Solutions
Phone # (888) 900-8944
http://bywatersolutions.com
ian.walls at bywatersolutions.com
Twitter: @sekjal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110827/0948a5ad/attachment.htm>

From robin at catalyst.net.nz  Mon Aug 29 01:37:48 2011
From: robin at catalyst.net.nz (Robin Sheat)
Date: Mon, 29 Aug 2011 11:37:48 +1200
Subject: [Koha-devel] System design
In-Reply-To: <5.2.1.1.2.20110826163710.09932040@stormy.ca>
References: <5.2.1.1.2.20110826163710.09932040@stormy.ca>
Message-ID: <1314574668.3396.125.camel@zarathud>

Paul schreef op vr 26-08-2011 om 17:39 [-0400]:
> 1)  The system (Ubuntu 11.04) is being installed on a SSD (solid state 
> drive) which recommends keeping "writes" to a minimum for longevity.  This 
> obviously includes logs, etc, but not necessarily the sql database.  

You aren't going to use up the write limit of a decent SSD any time
soon. 

> Does anyone have to hand a list of "system" versus "run-time" directories 
> and files?  I'm particularly curious about Zebra (which I do not fully 
> understand) as it appears to be proliferous and ubiquitous.

It depends how you install it. For the packages, all the changable stuff
goes in /var/lib/koha (zebra databases are in here), and /var/lib/mysql
if you use a local database. There's also /var/log/koha
and /var/spool/koha. But everything outside of /var is pretty static.

> 2)  I have stabilized a partially customized Koha 3.2.5 which is close to 
> meeting our needs.  Koha 3.4 would be my choice on the new server (and I'm 
> not worried about cosmetics -- CSS, etc) but how bullet-proof is the data 
> conversion (as of now about 80,000 records)?

80,000 isn't that big :) I'd say try it and find out, I've not noticed
many upgrade issues. Just keep a backup, but that's good advice anyway.
Also, upgrading to 3.4 will make you update your customisations, which
is good to do anyway.

-- 
Robin Sheat
Catalyst IT Ltd.
? +64 4 803 2204
GPG: 5957 6D23 8B16 EFAB FEF8  7175 14D3 6485 A99C EB6D
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: </pipermail/koha-devel/attachments/20110829/e260d01f/attachment.pgp>

From magnus at enger.priv.no  Tue Aug 30 08:35:45 2011
From: magnus at enger.priv.no (Magnus Enger)
Date: Tue, 30 Aug 2011 08:35:45 +0200
Subject: [Koha-devel] 2011-09-02 Global bug squashing day #4
Message-ID: <CABg6UYHQzfsL1FNb3jb4SLRmDwqf-qUmUjX7BZBy2C3BAcmQ1g@mail.gmail.com>

Dear Community!

Just a gentle reminder that GBSD#4 is approaching fast:
http://wiki.koha-community.org/wiki/2011-09-02_Global_bug_squashing_day

Please bear in mind that the Release Manager has declared the following dates:
* Feature freeze ? 22 September 23:59 UTC ? From this point on, no new
features will be considered for inclusion into 3.6.0
* String freeze ? 8 October 23:59 UTC ? no bugs that change templates
accepted after this point. This allows the translators to translate
without things changing on them
http://koha-community.org/key-dates-3-6-0/

That means we have about 3 weeks for getting any new features in! And
there are (at the moment) 83 (!) bugs/patches waiting to be signed
off:
http://bugs.koha-community.org/bugzilla3/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&field0-0-0=cf_patch_status&query_format=advanced&type0-0-0=equals&value0-0-0=needs%20signoff&order=bug_id&list_id=10641

See one in there that you would like to make sure makes it into Koha
3.6? YOU can help it along by signing off on it!
http://wiki.koha-community.org/wiki/Sign_off_on_patches

Of course, we should take every opportunity to sign off patches in the
coming weeks, but why not make a concerted effort on Friday September
2nd 2011 (in your timezone) and see how far we can get, as a team?
Could we cut the queue in half?

Happy hunting!
Magnus Enger

PS
And you don't have to be a developer to help either!

From kmkale at anantcorp.com  Wed Aug 31 14:35:22 2011
From: kmkale at anantcorp.com (Koustubha Kale)
Date: Wed, 31 Aug 2011 18:05:22 +0530
Subject: [Koha-devel] Kohacon11 : paper abstracts to arrange into a program.
Message-ID: <CAP=kTZq0VaPh9myjySq3YMCt1BStRU-jDjcHeee2EZK4Q1Y8mQ@mail.gmail.com>

Hi All,
Please find attached a CSV file with paper abstracts submitted for
Kohacon11.

Any apologies or last minute submissions before we finalize the program for
the three days using these?

Also please let me have your suggestions as to how to order these into a
program.


Regards,
Koustubha Kale
Anant Corporation

Contact Details :
Address  : 103, Armaan Residency, R. W Sawant Road, Nr. Golden Dyes Naka,
Thane (w),
                Maharashtra, India, Pin : 400601.
TeleFax  : +91-22-21720108, +91-22-21720109
Mobile     : +919820715876
Website  : http://www.anantcorp.com
Blog : http://www.anantcorp.com/blog/?author=2
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110831/bdcae73b/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Summary of abstracts as on 31-Aug-2011.csv
Type: text/csv
Size: 19344 bytes
Desc: not available
URL: </pipermail/koha-devel/attachments/20110831/bdcae73b/attachment.csv>

From kmkale at anantcorp.com  Wed Aug 31 14:57:06 2011
From: kmkale at anantcorp.com (Koustubha Kale)
Date: Wed, 31 Aug 2011 18:27:06 +0530
Subject: [Koha-devel] Kohacon11 : paper abstracts to arrange into a
	program.
In-Reply-To: <CAP=kTZq0VaPh9myjySq3YMCt1BStRU-jDjcHeee2EZK4Q1Y8mQ@mail.gmail.com>
References: <CAP=kTZq0VaPh9myjySq3YMCt1BStRU-jDjcHeee2EZK4Q1Y8mQ@mail.gmail.com>
Message-ID: <CAP=kTZo5REFT9p+cCyeJkjVakmVGPsQHF=3UqAKmYzLvLouZ+w@mail.gmail.com>

On Wed, Aug 31, 2011 at 6:05 PM, Koustubha Kale <kmkale at anantcorp.com>wrote:

> Hi All,
> Please find attached a CSV file with paper abstracts submitted for
> Kohacon11.
>
> Any apologies or last minute submissions before we finalize the program for
> the three days using these?
>
> Also please let me have your suggestions as to how to order these into a
> program.
>
>
>
Sorry,
Forgot to mention that we also have a  couple of remote presentations one
from Chris C on 2nd november 9.30am and another one from paulnz sharing a
video about there workshop on Koha ( this one is not scheduled yet and I
need final confirmation from paulnz )

Anybody else who can't make it to India but would like to make a interesting
remote presentation / talk please let me know.

Additionally we had discussed one panel discussion each day. So those of you
who are attending and will lime to be panelists, please let me know. Also
lets have topics for the three possible panel discussions. All suggestions
welcome..


Regards,
kmkale
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110831/ff7f552f/attachment-0001.htm>

From paul.poulain at biblibre.com  Wed Aug 31 16:04:56 2011
From: paul.poulain at biblibre.com (Paul Poulain)
Date: Wed, 31 Aug 2011 16:04:56 +0200
Subject: [Koha-devel] koha 4.0 / solR / Zebra  : A working group is born ?
Message-ID: <4E5E3F88.1070508@biblibre.com>

Hi,

As you all know, BibLibre has worked hard on integrating solR as search
engine into Koha. The resulting work is live in 2 french libraries, and
we plan to integrate it into Koha 4.0

Our preference went to do a in-depth work. It mean we changed the API a
lot, as well as most of the logic behind the search in Koha. It means we
can't keep zebra working as it is today.
Fortunately, the proposed structure is modularized, so it's possible to
re-implement zebra for those who want to stay with it. It's also
possible to reintegrate NoZebra or any other search engine.

Zeno Tajoli sent us a mail with some starting work about this
re-implementation of zebra. I catched tcohen on IRC today, his boss gave
him some time to investigate too. Claire Hernandez (our development
manager) is also helping.

Unless i'm mistaking, it's a draft of a "search engine working group".
If anyone else is interested, drop me (or claire) a mail, we could
organize an IRC session.

PS: i've submitted a presentation for KohaCon11 about what we did around
solR. But it will be librarian-oriented. We will/could/should probably
have a topic about that during HackFest as well ;-)

-- 
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08


From ian.walls at bywatersolutions.com  Wed Aug 31 16:15:23 2011
From: ian.walls at bywatersolutions.com (Ian Walls)
Date: Wed, 31 Aug 2011 10:15:23 -0400
Subject: [Koha-devel] koha 4.0 / solR / Zebra : A working group is born ?
In-Reply-To: <4E5E3F88.1070508@biblibre.com>
References: <4E5E3F88.1070508@biblibre.com>
Message-ID: <CAE2wdZx+kFgn_zMyQ9-tB8Wp3tozC4KtU_wnupq_09TBxTwdxw@mail.gmail.com>

Paul,


I'd very much like to be involved in the strategic planning for the
rebuilding of C4/Search to handle solR.  I'm eager to see it as a valid
option along side Zebra, for libraries who can support the heavier-weight
search system.  I think there is also a lot more we can milk out of Zebra
with a more generalized and otherwise cleaner search API.

I'm free for IRC meetings usually between 12:00 and 22:00 UTC, but could go
later if need be.

Cheers,


-Ian

On Wed, Aug 31, 2011 at 10:04 AM, Paul Poulain <paul.poulain at biblibre.com>wrote:

> Hi,
>
> As you all know, BibLibre has worked hard on integrating solR as search
> engine into Koha. The resulting work is live in 2 french libraries, and
> we plan to integrate it into Koha 4.0
>
> Our preference went to do a in-depth work. It mean we changed the API a
> lot, as well as most of the logic behind the search in Koha. It means we
> can't keep zebra working as it is today.
> Fortunately, the proposed structure is modularized, so it's possible to
> re-implement zebra for those who want to stay with it. It's also
> possible to reintegrate NoZebra or any other search engine.
>
> Zeno Tajoli sent us a mail with some starting work about this
> re-implementation of zebra. I catched tcohen on IRC today, his boss gave
> him some time to investigate too. Claire Hernandez (our development
> manager) is also helping.
>
> Unless i'm mistaking, it's a draft of a "search engine working group".
> If anyone else is interested, drop me (or claire) a mail, we could
> organize an IRC session.
>
> PS: i've submitted a presentation for KohaCon11 about what we did around
> solR. But it will be librarian-oriented. We will/could/should probably
> have a topic about that during HackFest as well ;-)
>
> --
> Paul POULAIN
> http://www.biblibre.com
> Expert en Logiciels Libres pour l'info-doc
> Tel : (33) 4 91 81 35 08
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>



-- 
Ian Walls
Lead Development Specialist
ByWater Solutions
Phone # (888) 900-8944
http://bywatersolutions.com
ian.walls at bywatersolutions.com
Twitter: @sekjal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110831/de5e42a2/attachment.htm>

From tajoli at cilea.it  Wed Aug 31 16:28:27 2011
From: tajoli at cilea.it (Zeno Tajoli)
Date: Wed, 31 Aug 2011 16:28:27 +0200
Subject: [Koha-devel] koha 4.0 / solR / Zebra : A working group is born ?
In-Reply-To: <4E5E3F88.1070508@biblibre.com>
References: <4E5E3F88.1070508@biblibre.com>
Message-ID: <4E5E450B.1080301@cilea.it>

Hi Paul and all,

Il 31/08/2011 16:04, Paul Poulain ha scritto:
> Zeno Tajoli sent us a mail with some starting work about this
> re-implementation of zebra. I catched tcohen on IRC today, his boss gave
> him some time to investigate too. Claire Hernandez (our development
> manager) is also helping.

I confirm my interest to re-implement Zebra.


> PS: i've submitted a presentation for KohaCon11 about what we did around
> solR. But it will be librarian-oriented. We will/could/should probably
> have a topic about that during HackFest as well ;-)

But I also confirm that I'm not in KohaConf11

Bye

-- 
Dott. Zeno Tajoli
tajoliAT_SPAM_no_prendiATcilea.it
fax +39 02 2135520
CILEA - Consorzio Interuniversitario
http://www.cilea.it/disclaimer

From paul.poulain at biblibre.com  Wed Aug 31 16:38:45 2011
From: paul.poulain at biblibre.com (Paul Poulain)
Date: Wed, 31 Aug 2011 16:38:45 +0200
Subject: [Koha-devel] tools should they be command line executable as well ?
Message-ID: <4E5E4775.5010904@biblibre.com>

Hello all,

On http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5636 Ian
asked a question last month no-one answered. So I ask it here:
> Style question to the community:  should core pages in the staff client (like
> tools/cleanborrowers.pl) have both a templated page in the staff client AND a
> command-line presence, or should the commandline tool be a separate script in
> misc/?
>
> At this time, there doesn't seem to be any precedent for inclusion in the core
> script.  Before passing this patch for QA, I'd like to get some feedback, as
> this may both open doors for us, as well as create additional work to create
> consistency of implementation for existing jobs.
My answer is:
* right, there is no precedent
* This feature to clean borrowers from command line is highly useful :
most libraries want to define a rule, and have it applied every week,
through a cronjob. But some want to clean manually. So it's meaningful
to have a script for both cases.
* I think it's fair to have this script run from both, and it's better
than having 2 scripts for that, it's easier to maintain
* I think a few other script could usefully have the same feature :
import_borrowers, batchMod (that does both mod and deletion of items),
and that's probably all.

So, overally, my choice is : let the need decide. If it's useful for
some, do it, but double check for security issues.

-- 
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08


From M.de.Rooy at rijksmuseum.nl  Wed Aug 31 16:49:39 2011
From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy)
Date: Wed, 31 Aug 2011 14:49:39 +0000
Subject: [Koha-devel] tools should they be command line executable as
 well ?
In-Reply-To: <4E5E4775.5010904@biblibre.com>
References: <4E5E4775.5010904@biblibre.com>
Message-ID: <809BE39CD64BFD4EB9036172EBCCFA3132700E@S-MAIL-1B.rijksmuseum.intra>

+1

Your conclusion is clear. I would agree with that. Add both choices only when useful. In case you have two scripts, it would be nice to prevent code duplication.

Marcel

________________________________________
Van: koha-devel-bounces at lists.koha-community.org [koha-devel-bounces at lists.koha-community.org] namens Paul Poulain [paul.poulain at biblibre.com]
Verzonden: woensdag 31 augustus 2011 16:38
Aan: koha-devel at lists.koha-community.org
Onderwerp: [Koha-devel] tools should they be command line executable as well ?

Hello all,

On http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5636 Ian
asked a question last month no-one answered. So I ask it here:
> Style question to the community:  should core pages in the staff client (like
> tools/cleanborrowers.pl) have both a templated page in the staff client AND a
> command-line presence, or should the commandline tool be a separate script in
> misc/?
>
> At this time, there doesn't seem to be any precedent for inclusion in the core
> script.  Before passing this patch for QA, I'd like to get some feedback, as
> this may both open doors for us, as well as create additional work to create
> consistency of implementation for existing jobs.
My answer is:
* right, there is no precedent
* This feature to clean borrowers from command line is highly useful :
most libraries want to define a rule, and have it applied every week,
through a cronjob. But some want to clean manually. So it's meaningful
to have a script for both cases.
* I think it's fair to have this script run from both, and it's better
than having 2 scripts for that, it's easier to maintain
* I think a few other script could usefully have the same feature :
import_borrowers, batchMod (that does both mod and deletion of items),
and that's probably all.

So, overally, my choice is : let the need decide. If it's useful for
some, do it, but double check for security issues.

--
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08

_______________________________________________
Koha-devel mailing list
Koha-devel at lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

From jcamins at cpbibliography.com  Wed Aug 31 16:54:56 2011
From: jcamins at cpbibliography.com (Jared Camins-Esakov)
Date: Wed, 31 Aug 2011 10:54:56 -0400
Subject: [Koha-devel] koha 4.0 / solR / Zebra : A working group is born ?
In-Reply-To: <4E5E450B.1080301@cilea.it>
References: <4E5E3F88.1070508@biblibre.com>
	<4E5E450B.1080301@cilea.it>
Message-ID: <CALVDfQzkZ0LXmiyLfiWe-KyyfB4AR5XKHVhcJzYwFaJpkfLNrg@mail.gmail.com>

Paul et. al.,

I'm not sure I can commit to being an official member of the working group,
but I hope you will publicize meetings loudly so that I (and others like me)
can attend, and offer my 2 cents (sixty dollars with inflation). Fixing
searching in Koha is a topic very near and dear to my heart, as many of you
know.

Regards,
Jared

On Wed, Aug 31, 2011 at 10:28 AM, Zeno Tajoli <tajoli at cilea.it> wrote:

> Hi Paul and all,
>
> Il 31/08/2011 16:04, Paul Poulain ha scritto:
> > Zeno Tajoli sent us a mail with some starting work about this
> > re-implementation of zebra. I catched tcohen on IRC today, his boss gave
> > him some time to investigate too. Claire Hernandez (our development
> > manager) is also helping.
>
> I confirm my interest to re-implement Zebra.
>
>
> > PS: i've submitted a presentation for KohaCon11 about what we did around
> > solR. But it will be librarian-oriented. We will/could/should probably
> > have a topic about that during HackFest as well ;-)
>
> But I also confirm that I'm not in KohaConf11
>
> Bye
>
> --
> Dott. Zeno Tajoli
> tajoliAT_SPAM_no_prendiATcilea.it
> fax +39 02 2135520
> CILEA - Consorzio Interuniversitario
> http://www.cilea.it/disclaimer
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>



-- 
Jared Camins-Esakov
Freelance bibliographer, C & P Bibliography Services, LLC
(phone) +1 (917) 727-3445
(e-mail) jcamins at cpbibliography.com
(web) http://www.cpbibliography.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110831/e61cd31c/attachment.htm>

From M.de.Rooy at rijksmuseum.nl  Wed Aug 31 16:55:12 2011
From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy)
Date: Wed, 31 Aug 2011 14:55:12 +0000
Subject: [Koha-devel] koha 4.0 / solR / Zebra : A working group is born ?
In-Reply-To: <4E5E3F88.1070508@biblibre.com>
References: <4E5E3F88.1070508@biblibre.com>
Message-ID: <809BE39CD64BFD4EB9036172EBCCFA3132701C@S-MAIL-1B.rijksmuseum.intra>

What is the status of SRU support with solR at this time? With Zebra, we can use it more or less rightaway. Since we use that functionality in several ways, I would regret it if we would loose SRU support "out-of-the-box" and need to do local tweaking first..

Marcel
________________________________________
Van: koha-devel-bounces at lists.koha-community.org [koha-devel-bounces at lists.koha-community.org] namens Paul Poulain [paul.poulain at biblibre.com]
Verzonden: woensdag 31 augustus 2011 16:04
Aan: koha-devel at lists.koha-community.org
Onderwerp: [Koha-devel] koha 4.0 / solR / Zebra  : A working group is born ?

Hi,

As you all know, BibLibre has worked hard on integrating solR as search
engine into Koha. The resulting work is live in 2 french libraries, and
we plan to integrate it into Koha 4.0

Our preference went to do a in-depth work. It mean we changed the API a
lot, as well as most of the logic behind the search in Koha. It means we
can't keep zebra working as it is today.
Fortunately, the proposed structure is modularized, so it's possible to
re-implement zebra for those who want to stay with it. It's also
possible to reintegrate NoZebra or any other search engine.

Zeno Tajoli sent us a mail with some starting work about this
re-implementation of zebra. I catched tcohen on IRC today, his boss gave
him some time to investigate too. Claire Hernandez (our development
manager) is also helping.

Unless i'm mistaking, it's a draft of a "search engine working group".
If anyone else is interested, drop me (or claire) a mail, we could
organize an IRC session.

PS: i've submitted a presentation for KohaCon11 about what we did around
solR. But it will be librarian-oriented. We will/could/should probably
have a topic about that during HackFest as well ;-)

--
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08

_______________________________________________
Koha-devel mailing list
Koha-devel at lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

From ian.walls at bywatersolutions.com  Wed Aug 31 17:03:46 2011
From: ian.walls at bywatersolutions.com (Ian Walls)
Date: Wed, 31 Aug 2011 11:03:46 -0400
Subject: [Koha-devel] koha 4.0 / solR / Zebra : A working group is born ?
In-Reply-To: <809BE39CD64BFD4EB9036172EBCCFA3132701C@S-MAIL-1B.rijksmuseum.intra>
References: <4E5E3F88.1070508@biblibre.com>
	<809BE39CD64BFD4EB9036172EBCCFA3132701C@S-MAIL-1B.rijksmuseum.intra>
Message-ID: <CAE2wdZzigiFrSp=3sJTLfzXKEKTavWxETCYMEb+DgrpHV559zQ@mail.gmail.com>

This project should not cause any regressions in Zebra functionality.  If a
function is available in Zebra that's not available in solR (or vice versa)
the reimplemented code should be flexible enough to accommodate that.  The
various features of each engine should be publicized to the community, and
then anyone can use that information to pick which engine best meets their
needs.  Hopefully Zebra and solR can both be grown in a way to bridge the
gap.

Cheers,


-Ian

On Wed, Aug 31, 2011 at 10:55 AM, Marcel de Rooy
<M.de.Rooy at rijksmuseum.nl>wrote:

> What is the status of SRU support with solR at this time? With Zebra, we
> can use it more or less rightaway. Since we use that functionality in
> several ways, I would regret it if we would loose SRU support
> "out-of-the-box" and need to do local tweaking first..
>
> Marcel
> ________________________________________
> Van: koha-devel-bounces at lists.koha-community.org [
> koha-devel-bounces at lists.koha-community.org] namens Paul Poulain [
> paul.poulain at biblibre.com]
> Verzonden: woensdag 31 augustus 2011 16:04
> Aan: koha-devel at lists.koha-community.org
> Onderwerp: [Koha-devel] koha 4.0 / solR / Zebra  : A working group is born
> ?
>
> Hi,
>
> As you all know, BibLibre has worked hard on integrating solR as search
> engine into Koha. The resulting work is live in 2 french libraries, and
> we plan to integrate it into Koha 4.0
>
> Our preference went to do a in-depth work. It mean we changed the API a
> lot, as well as most of the logic behind the search in Koha. It means we
> can't keep zebra working as it is today.
> Fortunately, the proposed structure is modularized, so it's possible to
> re-implement zebra for those who want to stay with it. It's also
> possible to reintegrate NoZebra or any other search engine.
>
> Zeno Tajoli sent us a mail with some starting work about this
> re-implementation of zebra. I catched tcohen on IRC today, his boss gave
> him some time to investigate too. Claire Hernandez (our development
> manager) is also helping.
>
> Unless i'm mistaking, it's a draft of a "search engine working group".
> If anyone else is interested, drop me (or claire) a mail, we could
> organize an IRC session.
>
> PS: i've submitted a presentation for KohaCon11 about what we did around
> solR. But it will be librarian-oriented. We will/could/should probably
> have a topic about that during HackFest as well ;-)
>
> --
> Paul POULAIN
> http://www.biblibre.com
> Expert en Logiciels Libres pour l'info-doc
> Tel : (33) 4 91 81 35 08
>
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>



-- 
Ian Walls
Lead Development Specialist
ByWater Solutions
Phone # (888) 900-8944
http://bywatersolutions.com
ian.walls at bywatersolutions.com
Twitter: @sekjal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/koha-devel/attachments/20110831/882cf2b5/attachment.htm>

From paul.a at aandc.org  Wed Aug 31 17:14:23 2011
From: paul.a at aandc.org (Paul)
Date: Wed, 31 Aug 2011 11:14:23 -0400
Subject: [Koha-devel] koha 4.0 / solR / Zebra : A working group is born ?
In-Reply-To: <4E5E450B.1080301@cilea.it>
References: <4E5E3F88.1070508@biblibre.com>
 <4E5E3F88.1070508@biblibre.com>
Message-ID: <5.2.1.1.2.20110831110956.04088690@localhost>

At 16:28 31/08/2011 +0200, Zeno Tajoli wrote:
>Hi Paul and all,
>
>Il 31/08/2011 16:04, Paul Poulain ha scritto:
> > Zeno Tajoli sent us a mail with some starting work about this
> > re-implementation of zebra. I catched tcohen on IRC today, his boss gave
> > him some time to investigate too. Claire Hernandez (our development
> > manager) is also helping.
>
>I confirm my interest to re-implement Zebra.

I am also very interested in this, and might be able to free up some spare 
time to assist -- if my somewhat antiquated abilities are at all suitable ;-}

Regards

Paul
Tired old sys-admin
---
Archives and Collections (ACS) Society
205, Main Street, Picton, Ontario, K0K 2T0, Canada
http://www.AandC.org
Canadian Charitable Organization 88721 9921 RR0001 


From paul.poulain at biblibre.com  Wed Aug 31 17:24:17 2011
From: paul.poulain at biblibre.com (Paul Poulain)
Date: Wed, 31 Aug 2011 17:24:17 +0200
Subject: [Koha-devel] koha 4.0 / solR / Zebra : A working group is born ?
In-Reply-To: <809BE39CD64BFD4EB9036172EBCCFA3132701C@S-MAIL-1B.rijksmuseum.intra>
References: <4E5E3F88.1070508@biblibre.com>
	<809BE39CD64BFD4EB9036172EBCCFA3132701C@S-MAIL-1B.rijksmuseum.intra>
Message-ID: <4E5E5221.1040606@biblibre.com>

Le 31/08/2011 16:55, Marcel de Rooy a ?crit :
> What is the status of SRU support with solR at this time?
I don't have the answer to this question, but, before someone else rise
the z3950 one => we have developped the z3950 layer for solR.

-- 
Paul POULAIN
http://www.biblibre.com
Expert en Logiciels Libres pour l'info-doc
Tel : (33) 4 91 81 35 08


From danielg.koha at gmail.com  Thu Aug 18 21:49:34 2011
From: danielg.koha at gmail.com (daniel g)
Date: Thu, 18 Aug 2011 19:49:34 -0000
Subject: [Koha-devel] News from the New Newsletter Editor
Message-ID: <CAOeKewizZH-oFLS8+LSrDVNOnr4qYRADjAZC9ghg1Z+O5JsMXw@mail.gmail.com>

Hello,

As you may know, Nicole Engard has resigned the position of Koha
newsletter editor after a year and a half of splendid work. I?m
pleased the community has selected me to succeed her, and I look
forward to serving the community by producing the monthly account of
what?s new in the world of Koha.

But I need your help to do it! Please send me news of anything you
think the community might like to know about. It can be as short as a
sentence or as long as a paper.

I'm planning to add a gossip column (you call it a society column if
you prefer), which will be short blurbs about what folks in the
community are doing, like "Paul Poulain of BibLibre is assisting 3.6
Quality Assurance Manager Ian Walls in reducing the backlog of patches
waiting for QA testing" and "Melia Meggs joined ByWater Solutions as
their Operations Manager." I'll be harvesting material for this column
from the lists and blogs, but I encourage you to send me a sentence or
two about what you're currently working on.

I?ll also be adding a section on new Koha implementations in the past
month, so if you know of any go-lives that don?t get posted to the
list, please be sure to alert me.

I've already gathered a fair amount of material for the August
newsletter, including the August General IRC meeting, Global Bug
Squashing Day, the status of the releases, and the latest on KohaCon11
and KohaCon12. Please send directly to me (not to the list) anything
else you think might be newsworthy by next Thursday, August 25.

Thanks,
Daniel Grobani