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

Is there any way to delete recently added patrons?
by Hartman, David W. - GBTS Library 05 Aug '11

05 Aug '11

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

2 1

Removing sysprefs from language related installer ?
by Paul Poulain 05 Aug '11

05 Aug '11

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

1 1

Global Bugs Squashing Day #3
by Magnus Enger 04 Aug '11

04 Aug '11

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

1 0

Re: [Koha-devel] [Koha-patches] [PATCH] [SIGNED-OFF] Bug 6553 : Follow up adding license statements
by Robin Sheat 04 Aug '11

04 Aug '11

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(a)catalyst.net.nz> > > http://bugs.koha-community.org/show_bug.cgi?id=6653 > > Signed-off-by: Marcel de Rooy <m.de.rooy(a)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.

2 1

FW: Patch format
by Marcel de Rooy 04 Aug '11

04 Aug '11

+1 for removing redundancy ;) -----Oorspronkelijk bericht----- Van: koha-devel-bounces(a)lists.koha-community.org [mailto:koha-devel-bounces@lists.koha-community.org] Namens Mason James Verzonden: maandag 1 augustus 2011 02:50 CC: koha-devel(a)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(a)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/

3 3

Proposal for Assistance with QA Testing for Koha 3.6
by Ian Walls 03 Aug '11

03 Aug '11

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(a)bywatersolutions.com Twitter: @sekjal

5 5

Kohacon11 : Apologies for missing last few meetings
by Koustubha Kale 03 Aug '11

03 Aug '11

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

1 0

Sending orders by email
by Edgar Fuß 03 Aug '11

03 Aug '11

I've ported my order-by-email patch (first mentioned in Bug 5260) to 3.4.3. I attach two diffs, one for the CGI scripts and another for the templates, in a format hopefully acceptable to GIT people. Katrin Fischer suggested using the message queue for sending emails to booksellers, but, as I understand, C4::Letters::EnqueueLetter can send only to borrowers. I've changed the tab wording from ```Mail'' to ``Email'' as suggested by Katrin Fischer. Btw.: I'm also (with some help by Dan McMahill) importing Koha (currently 3.4.3) into the NetBSD Package Collection. Once this gets sorted out, you can just cd ${PKGSRCDIR}/databases/koha && make install (or pkg_add koha if someone has built the binaries for you) and you get Koha and all its dependencies installed on any system supported by pkgsrc (which is, in fact, nearly everything POSIX compatible, including most BSDs, SunOS, AIX, Darwin/OSX and even Linux).

3 6

Re: [Koha-devel] 64-bit versions
by Paul 02 Aug '11

02 Aug '11

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@biblibre.com>paul.poulain(a)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

5 5

Bugzilla & default assignee
by Paul Poulain 02 Aug '11

02 Aug '11

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

3 3