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

KohaCon11 hackfest: discussion
by Paul Poulain 10 Jun '11

10 Jun '11

Hello everybody, 3 weeks ago we had our 1st IRC meeting about the next KohaCon in India. It seems I've been selected to start the discussion about the Hackfest ! We've had 3 KohaCon already : one in France (2006) one in USA (2009), one in NZ (2010). In Marseille, it lasted one week and was mostly about hacking. In USA it lasted 3 days, we had one day (and a half ?) teaching new developers how to hack, then one day hacking In NZ it lasted 3 days too. the 1st day was dedicated to some -technical- lightning talks (http://www.kohacon10.org.nz/2010/hackfest/index.html) then teaching new hackers, then doing a few hacking What should be the hackfest in India then ? We have two goals during those meetings: welcome new developers, and do some real hacking: it's very efficient to work in the same room and without clock/time differences ! I proposed during the first IRC meeting to split the hackfest in 2 sub-parts, each of them dealing with one goal: * Hackfest part 1 = "become a Koha developper" * Hackfest part 2 = "do some hacking". We could say part1 is about theory, and part2 is about practising what we've learned on part1 ;-) (and of course, ppl coming for part1 would/should/could stay for part2 !) The 1st part would be dedicated to teaching Koha to ppl wanting to know how to join: things like using git, Koha source code organisation, Koha database, working with templates, dealing with translations, submitting patches. kmkale suggested to have 2 days for this part, just before sunday (that would be a day-off) The 2nd part would be dedicated to hacking: showing what is underway, showing POC if applicable (Proof of Concept), playing with bugzilla, writing unit tests,... How long could/should it last ? There are 2 opinions here: - staying & taking time is expensive, so not too long - once you're here, we must make the trip worth, so as long as possible What's your opinion on this matter ? Mine is that once we're here, we must stay as long as possible, those meetings are precious. So how long should this part last ? kmkale said there will be a room available for us for as long as we want. My proposition would be to say 3 days (mon-wed): not too short, we will be able to do useful things, not too long, we'll be back home on tuesday, before or for the next week-end, back to work next monday. What's your opinion on those ideas ? anything to add ? Feel free to give your opinion, nothing has been decided yet ! -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

6 12

Koha Version 3.4.1
by Louise_Towers＠hugoboss.com 09 Jun '11

09 Jun '11

Dear Sir/Madam, We need some answers and support based on Koha Version 3.4.1. We have installed and are using here at Hugo Boss Ticino but now we have some questions and require some support for a number of things - would it be possible to organise a conference call with one of your technicians or documentation managers? We know the time difference may be a problem as we are based in Switzerland but we can stay later to compensate for this - maybe 6pm our time, 9am your time tomorrow morning Friday 10th June or Tuesday 14th June? We are having problems like, if two people reserve the same book at the same time, there is no circulation email. Also, does the support for Koha have a cost for the service?? I look forward to hearing from you as soon as possible to help us use your product most effectively and efficiently, With Regards, Louise HUGO BOSS Ticino SA Louise Towers Project and Service Management Knitwear ------------------------------------------------------- Via Sant'Apollonia 32 6877 Coldrerio - CH Phone : +41 91 6966875 Fax : +41 91 6966816 e-mail: Louise_Towers(a)hugoboss.com www.hugoboss.com This e-mail (and/or attachments) is confidential and may be privileged. Use or disclosure of it by anyone other than a designated addressee is unauthorized. If you are not an intended recipient, please delete this e-mail from the computer on which you received it. We thank you for notifying us immediately.

2 1

Bug 3013 - 006 and 008 for non book material
by Stefano Bargioni 09 Jun '11

09 Jun '11

Hi, as I commented in http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3013 the latest patch seems ok to me (tested in Koha 3.2.3). I signed it off (in Bugzilla only, I'm not able to use git up to now, sorry). Hope it could be included in Koha 3.2.10. Bye. Stefano

1 0

Items not added to Zebra in field 952
by Salvador Zaragoza Rubio 09 Jun '11

09 Jun '11

Hi all, On my git master updated version when adding an item I can't see the item added in the 952 field of the Zebra database, it's only added to the MySQL items table. I've checked the Items.pm script and in the sub AddItem this is what we had before: # create MARC tag representing item and add to bib my $new_item_marc = _marc_from_item_hash($item, $frameworkcode, $unlinked_item_subfields); _add_item_field_to_biblio($new_item_marc, $item->{'biblionumber'}, $frameworkcode ); And now: ModZebra( $item->{biblionumber}, "specialUpdate", "biblioserver", undef, undef ); The sub _add_item_field_to_biblio is missing and the 952 is not added to the biblio record (field marcxml, filed marc in biblioitems) and the ModZebra doesn't update the record with the new 952 field. Am I missing something? Is that correct and is a planned modification about Items? I can't find a bug related with this issue. Regards Salva

3 3

KOHA version 3.0, my question is about the advantages of KOHA 4
by Christian Calle Jahuira 08 Jun '11

08 Jun '11

It is a pleasure to find KOHA community greatly strengthened. Write to La Paz Bolivia, I have implemented KOHA version 3.0, my question is about the advantages of KOHA 4 and LibLime, which presents differences. Atte -- Christian Jhonny Calle Jahuira TUTOR ELEARNING - UMSA Consultor Sistemas de Informacion de Bibliotecas de la UMSA Email: christianjcj(a)gmail.com Cel: 73017301 - 65151595

13 32

Koha More regarding local call number search/barcodes
by Linda Culberson 08 Jun '11

08 Jun '11

All, At Chris's suggestion, I'm moving this to the development list. It seems to me that Henri-Damien is correct in that exact would be better for the sn and bc indexes but that the phrase might work better for call numbers. Since I am very much a newbie at this, I'd like to hear from those more experienced about the best way to proceed. Do I need to put this discussion on bugzilla or just the outcome of the discussion when we're ready to proceed? We are very interested in contributing but don't want to create any problems when trying to fix something. Thanks, Linda On 1:59 PM, LAURENT Henri-Damien wrote: > Le 06/06/2011 20:57, Chris Cormack a Ã©crit : >> > On 7 June 2011 06:53, Linda Culberson<lculber(a)mdah.state.ms.us> wrote: >>> >> The problem, at least in 3.4, does exist, but changing the query from >>> >> sn,wrdl to sn,phr and bc,wrdl to bc,phr seems to fix it. >>> >> >>> >> But I'm still wondering if there are others - besides call numbers - >>> >> for which this applies. >>> >> >>> >> I apologize for the multiple emails. I should do more research before I >>> >> email. I'll try to keep quiet now. >>> >> >> > >> > Hi Linda >> > Multiple emails are fine, but perhaps this discussion is better on the >> > koha-devel list. >> > I think its not a new problem (i think 3.0.x up did this) but that >> > doesn't mean its right. >> > >> > I think phr for barcode, sn, etc makes more sense and I would >> > encourage you to widen the scope of your bug to include them. >> > The fix is simply changes in the template so should be relatively >> > straightforward to implement and would be a welcome fix for many >> > libraries I think. >> > >> > Chris > Well, it all depends on what you search, but ext could be really what > you are looking for. > With phr you could look for : > AAAA/BB > And find > AAAA/BB C > AAAA/BB D > or even > C AAAA/BB > where ext would match the exact subfield... > But one default for that is that you cannot search both ext and * afaik > (could be quite easy to test if anyone interested. In a yaz-client : > f @attr 4=1 @attr 6=3 @attr 5=2 "your callnumber" > ) > > and that ext search requires the completeness set to 1 on the index type > you use in default.idx ... Which is commonly the case when you use p... > Moreoved, consider that using p should not replace w indexing, but be added. > Since there are places in the code or in database settings where lcn can > be searched directly without using phr modifier. And if you donot have > indexed with word... Then the search will always fail which would be > worse than the problem it fixed. > Hope that helps. > -- Henri-Damien LAURENT -- Linda Culberson lculber(a)mdah.state.ms.us Archives and Records Services Division Ms. Dept. of Archives & History P. O. Box 571 Jackson, MS 39205-0571 Telephone: 601/576-6873 Fax: 601/576-6824

2 1

Global sign off day, 2011-06-15
by Magnus Enger 07 Jun '11

07 Jun '11

Dear all! (And sorry for cross posting... At least a little bit ;-) We had such great fun in Marseilles earlier this year, signing off patches, that I have been wondering if it would be possible to re-create some of that experience without incurring the costs of travel. I broached the subject on IRC earlier today and after the briefest and least democratic of processes, "we" decided to declare 15th June 2011 as a Global Sign Off Day: http://wiki.koha-community.org/wiki/Global_sign_off_day,_2011-06-15 The hope is that as many people as possible will be able to set aside as much other work as possible on this day, and concentrate on signing off patches, to reduce the queue of bugs that are currently waiting for sign-off (66 at this moment: http://bugs.koha-community.org/bugzilla3/buglist.cgi?bug_status=NEW&bug_sta…) We will try to visualise and document the progress that is made, to make it more fun and maybe even tickle the competitive instincts a little bit... ;-) And who knows, if this day is a success, maybe we could turn it into a regular tradition? * If you have not signed off on a patch before, now is the perfect time to do it! The more the merrier! The process is outlined here: http://wiki.koha-community.org/wiki/Sign_off_on_patches And there will be people on IRC that you can ask for help and guidance! Best regards, Magnus Enger * On the other hand, let's hope we can keep the queue as short as possible...

1 0

RFCs
by Nicole Engard 07 Jun '11

07 Jun '11

Hello developers, On looking at the wiki I see that the 3.4 RFCs have some things that didn't make it in to 3.4 and the 3.6 RFCs page is empty. We should probably move the devs that didn't make it to 3.4 from this page: http://wiki.koha-community.org/wiki/Category:Koha_3.4_RFCs to a page for 3.6 Nicole

1 0

Circulation Improvements
by Chris Cormack 06 Jun '11

06 Jun '11

Hi All Biblibre have done some good circulation improvements (bug 5872) but this is currently blocked by bug 5436 http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5436 Work is being done on Hourly loans http://bugs.koha-community.org/bugzilla3/showdependencytree.cgi?id=5549&hid… And I want all of the changes in 5872 in with that. Would someone be able to look at 5436 and fix it up (the other 2 bugs 5872 depends on have made their way through sign off already). Thanks in advance Chris -- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand

1 0

Re: [Koha-devel] EAN-13 barcode support
by Chris Nighswonger 06 Jun '11

06 Jun '11

Hi Dobrica, On Mon, Jun 6, 2011 at 1:08 PM, Dobrica Pavlinusic <dpavlin(a)rot13.org> wrote: >> The scaling foo really follows no logic that I've be able to figure >> out yet. It is definitely not a "one size fits all" situation. Right >> now it is optimized for longer barcodes. Feel free to improve upon it >> if you are able. > > I was wondering what units are used for $bar_length, and I haven't > figured it out. IIRC all at that level are points. I'm pretty sure that I refactored the entire creator code to use points as its base unit. > > However, without scaling, barcodes are correct size (at least for > EAN-13/UPC-a which have "standard" size), so it's not a show-stoppper. I suspect this is true for the average user, which is why it has not been high on my list to work on (sorry everyone). If I can help by answering questions, please feel free to ask. My time right now is tight, so I can't do much more. Kind Regards, Chris

1 0