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

Sharing news about KohaCon12
by Paul Poulain 09 May '12

09 May '12

Hello koha-devel, Just to share: 6 ppl of BibLibre comes at the KohaCon. We should arrive on monday 4th and leave on tuesday, 12th. We will stay at > StayEdinburgh - West End Apartments > 11 Brandfield Street Haymarket > Edinburgh -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

1 0

KohaCon 2013 Wiki Reminder
by BWS Johnson 08 May '12

08 May '12

Salvete! A while back, a mess of folks expressed interest over the listserv in bidding for KohaCon 2013. This is great. :) What is not great is that the folks that proclaimed their love of hosting over the listserv do not match with this wiki page: http://wiki.koha-community.org/wiki/Kohacon2013 So if you're earnest, please edit it, and soonish that way we can generate a proper ballot. Cheers, Brooke

1 0

rel_3_10 version created on bugzilla / usage of rel_3_8 changed
by Paul Poulain 07 May '12

07 May '12

Hello koha-devel, As Koha 3.8 is now released, I've created rel_3_10 that I'll use for all enhancements I'll push for next major release. 3.10 is "reserved use" for the Release Manager, don't use it please. If you find a bug in "master", use "master" version. If you find a bug in a stable version, use the "version" you're running. -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

1 0

Brasilian portuguese is near complete
by Tiago Murakami 07 May '12

07 May '12

Hi, The translation of version 3.8 is near complete. I would be happy if you could cite my name and that of Rafael Saad in about Koha. Thanks. -- Tiago Murakami Librarian Biblioteca Pública Municipal Manuel Bandeira São Bernardo do Campo - São Paulo - Brasil

1 0

Re: [Koha-devel] Feedback from staff with plack?
by Dobrica Pavlinusic 04 May '12

04 May '12

On Fri, May 04, 2012 at 12:18:20PM +0200, Paul Poulain wrote: > Hi Dobrica, > > You said during the hackfest that you wanted to plackify staff interface > after the hackfest. Did you make it ? Do you have some feedback to give > to us ? With all patches from hackfest and aftewards, staff interface works quite well. To be honest, I used plack for all my development ever since with great success :-) Just this week I found small problem with Z39.50 copy cataloguing which mungles encodig. This is somewhat important beacuse we are in persistant enviroment and once encoding gets corrupted it stays this way. I will investigate this more and submit approriate bug. I still haven't put plack staff interface in production at our library, but I do intend to do it before KohaCon 2012 so I can report my expiriences. > Thanks for this feedback ! Sorry for silence, I was quite busy lately. -- Dobrica Pavlinusic 2share!2flame dpavlin(a)rot13.org Unix addict. Internet consultant. http://www.rot13.org/~dpavlin

1 0

Solr demo - current BibLibre solr and stetienne devs (updated)
by Claire Hernandez 03 May '12

03 May '12

Hi all, I updated the solr-demo install. We provided it for kohacon11 demo but it seems it could be usefull sometimes. This is the current stetienne version (solr devs + acquisitions and serials you can find here with "STE" library code https://docs.google.com/a/biblibre.com/spreadsheet/ccc?key=0AuZF5Y_c4pIxdHE… ) Professional interface is here: http://solr-demo.biblibre.com <http://solr-demo.biblibre.com/> There is a "demo" account, you could see for example the current admin interface for indexes preferences http://solr-demo.biblibre.com/cgi-bin/koha/solr/indexes.pl We are re-doing work for the future abstract layer. I will setup a new install to show what we have. Stay tuned :) Claire; (other close subject: you can see the progress for april month for rebase work at BibLibre: https://docs.google.com/a/biblibre.com/spreadsheet/ccc?key=0AuZF5Y_c4pIxdHE…)

1 1

Bug 5572 (refinements to function merge sub merge in C4::AuthoritiesMarc)
by Marcel de Rooy 03 May '12

03 May '12

Hi, This patch from Janusz Kaczmarek dates from Jan 3, 2011 already. And still needs signoff. I have marked it as In Discussion now, hoping for some feedback from you. Please have a look at the report and patch. Do you agree that subfields at the biblio side should be cleared for an active empty authority subfield? Or could that result in unexpected data loss too easily? What is your opinion? Other QA team members are also welcome to respond. Thanks for doing so, Marcel

2 1

Bugzilla component categories
by Marcel de Rooy 02 May '12

02 May '12

Hi all, Recently we discussed in the QA team to make the default QA contact empty. (Ian cleared this field for all components now [for new reports].) In the process the QA team member that starts QA on a report now, enters his name in the QA contact field. This informs reporter, patch writer, etc. that QA started and is also helpful for other QA team members in order to prevent duplication of work. My question now is: Should we do something similar with the default Assignee per component? In practice, the current default assignees will (most of the time) not be working on reports entered by someone else. Having someone in the Assignee field who is not working on that report, could be a misleading signal for an unaware Bugzilla user. If the default assignee wants to be informed on reports of that category, moving him/her to the default CC list of that component would perhaps be better? The current default assignees are (for one or more components): nengard(a)gmail.com<mailto:nengard@gmail.com> henridamien(a)koha-fr.org<mailto:henridamien@koha-fr.org> gmcharlt(a)gmail.com<mailto:gmcharlt@gmail.com> oleonard(a)myacpl.org<mailto:oleonard@myacpl.org> chris(a)bigballofwax.co.nz<mailto:chris@bigballofwax.co.nz> kyle.m.hall(a)gmail.com<mailto:kyle.m.hall@gmail.com> koha.sekjal(a)gmail.com<mailto:koha.sekjal@gmail.com> frederic(a)tamil.fr<mailto:frederic@tamil.fr> cnighswonger(a)foundations.edu<mailto:cnighswonger@foundations.edu> robin(a)catalyst.net.nz<mailto:robin@catalyst.net.nz> colin.campbell(a)ptfs-europe.com<mailto:colin.campbell@ptfs-europe.com> paul.poulain(a)biblibre.com<mailto:paul.poulain@biblibre.com> wizzyrea(a)gmail.com<mailto:wizzyrea@gmail.com> Would you agree with this move? (We need of course consensus before doing so.) Would you like to be added as default CC for one or more components? Please respond. Thanks, Marcel

5 5

Bugzilla component categories
by Chris Nighswonger 02 May '12

02 May '12

On Wed, May 2, 2012 at 8:10 AM, Marcel de Rooy <M.de.Rooy(a)rijksmuseum.nl>wrote: > > My question now is: Should we do something similar with the default > Assignee per component? In practice, the current default assignees will > (most of the time) not be working on reports entered by someone else. > Having someone in the Assignee field who is not working on that report, > could be a misleading signal for an unaware Bugzilla user. If the default > assignee wants to be informed on reports of that category, moving him/her > to the default CC list of that component would perhaps be better? > Like Owen, I try to address most label/card related bugs of which I am the default assignee. I am not convinced that blanking the default assignee would result in much good. Probably a better move would be to encourage developers who decide to work on a bug to do two things: 1. Click the "take" link next to the assignee field. 2. Set the status to "Assigned." Probably any current confusion is due to one of two things: 1. Bugs currently being worked on, but the developer doing the work has failed to do the two things mentioned above. 2. Lack of understanding on the "unaware Bugzilla user's" part which is better remedied by becoming "aware" of how bugzilla works rather than trying to build a better mouse trap. If things were really this difficult, I suspect that Bugzilla would be swamped with enhancement requests or out of business, one. Kind Regards, Chris

4 3

SQL reports [error]
by Paul 30 Apr '12

30 Apr '12

Good morning all: I have no problem with the philosophy of the following (bright yellow) pop-up error message: "The following error was encountered: This report contains the SQL keyword UPDATE. Use of this keyword is not allowed in Koha reports due to security and data integrity risks." and would not even consider suggesting a "bug." However, it would be most helpful to staff for a very specific but repetitive job that we do at year end (batch changing items.accessiondate after Tax Receipts have been issued for donations) to be able to use Koha from a work station, rather than getting me to work directly on the production server (I've already been asked 50 or 60 times, and there's another 400+ to go ...!) Can anyone point me rapidly to the portion of script that I should have a look at? For the record, the CLI mysql in question is: UPDATE items SET dateaccessioned='2011-12-31' WHERE price IS NOT NULL and price != '0.00' AND booksellerid = 'xxx' AND DATE(dateaccessioned) BETWEEN '2011-01-01' AND '2011-12-31'; Obviously for a report, I would use a construct for the last two conditions along the lines of: AND booksellerid = <<Pick your donor>> AND DATE(dateaccessioned) BETWEEN <<Accessioned BETWEEN (yyyy-mm-dd)>> AND <<and (yyyy-mm-dd)>>; Thanks and best regards, Paul

4 5