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

3.6.3 Update
by Chris Nighswonger 18 Jan '12

18 Jan '12

Hi all, Just an update here on the status of 3.6.3. My schedule has been extremely busy since I returned to work the first of the month. As a result, I have been working in fits and starts to get commits picked out of master and into 3.6.x in preparation for the release of 3.6.3. After finally getting several hours today devoted to the work, I have royally screwed up my local maintenance branch from which I push to the main repo. As those who eat and drink git know, this is not a fatal disaster, but it is certainly one which will now require another large block of time to correct: a resource I am sadly short on at the moment. Long story short: 3.6.3 will not be released on time this month. Very likely it will be near the end of the month before I can get things sorted out and announce a string freeze for the translators. This pushes the release into the second week of February. Please accept my sincerest apologies for the delay. Kind Regards, Chris Koha 3.4.x/3.6.x Release Maintainer

1 0

Call for News for the January Newsletter
by Daniel Grobani 17 Jan '12

17 Jan '12

Dear Koha Kommunitarians, I'm harvesting news for the January newsletter. Please send me by the 25th anything you think your fellow community members might like to know about. "News" can be as short as a sentence or as long as a paper. I especially encourage you to send me a line or two about what you're currently working on for publication in the gossip/society column. And if you know of a go-live not announced on the list, please be sure to let me know about it. Thanks, Daniel Grobani

1 0

Tables from InnoDB to MYISAM
by Zeno Tajoli 17 Jan '12

17 Jan '12

Hi to all, to mantain a good Koha system is import to use the cron job 'cleanup_database.pl'. This script delete lines from tables message_queue need_merge_authorities sessions zebraqueue The engine of those tables is InnoDB. What do you think about change the engine to MYISAM ? I think that MYISAM is a better engine for table with many write/delete. For thi is an ehancement and I don't insert it in updatedatabase.pl. This a change only for new installations. Or to do by hand for update. Bye -- Dott. Zeno Tajoli tajoliAT_SPAM_no_prendiATcilea.it fax +39 02 2135520 CILEA - Consorzio Interuniversitario http://www.cilea.it/disclaimer

4 3

On memcached/memoize
by Tomas Cohen Arazi 17 Jan '12

17 Jan '12

We are using memcached in two different ways accross Koha code: 1) The traditional way, explicitly using memcached inside the method/function code (just a mock): sub get_key { my $data; if (C4::Context->ismemcached) { $data = C4::Context->memcached->get('key'); } $data = slow_routine_to_get_data_from_db && C4::Context->memcached->set('key',$data) unless defined $data; return $data; } 2) Using memoize/dynamic programming: eval { if (C4::Context->ismemcached) { require Memoize::Memcached; import Memoize::Memcached qw(memoize_memcached); memoize_memcached( 'get_key, memcached => C4::Context->memcached, expire_time => 600 ); #cache for 10 minutes } }; sub get_key { my $data slow_routine_to_get_data_from_db; return $data; } The second method is really handy, in the sense that we need to just need a new call to memoize_memcached to make get_key use memcached. The problem with this approach (and the reason of this writing) is data invalidation, that is sometimes needed. Setting expire_time seems not enough for several cases (for example preferences change). With the first method, we can use the the method 'delete' to invalidate data on the setter function. Using memoize on data we should be able to invalidate means we have to use flush_cache(get_key => qw( key )) on methods/functions that write data. But then we need to hook our methods and I can't decide if we should continue using memoize... as it is less transparent for us who read other peoples code... I wrote to the author of Memoize (who didn't actually answer me) to ask him if we could add a parameter to memoize_memcached: a list of references to functions that invalidate data for this memoized function. This way we could just continue using this. Otherwise I'd recommend just using memcache the classic way. Hope we have a discussion on this as there are plenty of places we can benefit from this. To+ julian.maurice(a)biblibre.com

1 0

I need to enter through a WebService data users who enroll in the University
by Christian Calle Jahuira 17 Jan '12

17 Jan '12

Dear Friends Congratulations on the 2012 and have plenty of glory. I have the following problem, I'm using Koha and need to incorporate data through a WebService users who enroll in college to my mysql database, I inject the Borrowers table. PD. We have updated users every management and is a constant problem. I would appreciate any help please. -- Christian Jhonny Calle Jahuira TUTOR ELEARNING - UMSA Consultor Sistemas de Informacion de Bibliotecas de la UMSA Email: christianjcj(a)gmail.com Cel: 73017301 - 65151595

2 1

Hackfest in Europe in march (reminder)
by Paul Poulain 17 Jan '12

17 Jan '12

Hello everybody, A reminder about the hackfest BibLibre organize in Marseille in March. It's in 2 months, it's time to book your flights/trains/car/horse/boat, and tell us if you're coming. We already have 6 ppl (+ all BibLibre, of course) that should come, from 4 different countries (France, Germany, Croatia and USA), we've a lot of chairs & desktops still available ! If you hope to come but still are not sure, don't hesitate to send me a mail with the information. I'm happy when I see my list growing ;-) (full details at: http://drupal.biblibre.com/en/blog/entry/2012-hackfest-in-europe) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

1 0

Bugzilla
by Marcel de Rooy 17 Jan '12

17 Jan '12

Hi all, I personally would like to have a wider Status column in Bugzilla. Now I have to know that e.g. "Patc" means Patch does not apply. The other terms like Need, Sign (meaning Signed off), Pass, etc. are somewhat cryptical too.. Is that possible? Regards, Marcel

5 8

Making bulk changes to bugs.koha-community.org; bug emails will be turned off briefly
by Ian Walls 16 Jan '12

16 Jan '12

Everyone, As I mentioned in my previous thread about updating Bugzilla to better make use of the Status field, I'll be taking bug emails offline for a period of time while I make bulk changes to the statuses. This is to prevent everyone from being horribly spammed. I will reactivate the emails once the changes are complete. I'll try to be on IRC for the duration of this maintenance job, in case anyone has any emergency questions. Cheers, -Ian -- Ian Walls Lead Development Specialist ByWater Solutions ALA Midwinter Booth #2048 Phone # (888) 900-8944 http://bywatersolutions.com ian.walls(a)bywatersolutions.com Twitter: @sekjal

6 8

Fwd: Koha 3.4.7. // additem.pl
by Alen Vodopijevec 16 Jan '12

16 Jan '12

Hi all! I suspect that changes in cataloguing/additem.pl caused problem with visibility of other fields on the form that have "hidden" value other then "0" (Marc bib framework). Please see detailed description sent on Koha users list below. Change that caused it: http://git.koha-community.org/gitweb/?p=koha.git;a=blobdiff;f=cataloguing/a… ---------- Forwarded message ---------- Hi! We have a strange behaviour on test upgrade 3.4.4 -> 3.4.7. with adding an item (additem.pl) Select options for all fields that have value >0 (2 or 4 for example) for "hidden" variable in subfield constraints in MARC bibliographic framework are not shown on Additem form. I'm not sure if this is a feature or bug. The only thing that I can see is an addition at around line 203 of additem.pl: if ($subfieldlib->{'hidden'}) { $subfield_data{marc_value} = qq(<input type="hidden" $attributes /> $authorised_lib{$value}); } else { $subfield_data{marc_value} =CGI::scrolling_list( # FIXME: factor out scrolling_list -name => "field_value", -values => \@authorised_values, -default => $value, -labels => \%authorised_lib, -override => 1, -size => 1, -multiple => 0, -tabindex => 1, -id => "tag_".$tag."_subfield_".$subfieldtag."_".$index_subfield, -class => "input_marceditor", ); } If I remove the first IF statement or if I set "hidden" to "0" in MARC bibliographic framework settings for that particular subfield, select options are shown. We have a same issue with 3.6.2 testing Koha. Any suggestions are welcome :). regards, alen -- Alen Vodopijevec (alen(a)irb.hr) Library, Rudjer Boskovic Institute tel.: +385 1 456 0954 (x1293) gsm: +385 98 584 045 http://lib.irb.hr http://katalog.irb.hr

1 0

Missing possibilities in bugzilla status
by Paul Poulain 16 Jan '12

16 Jan '12

As you've read, Ian has updated the workflow to add some dependancies in status (ie: you can't jump from assigned to patch pushed, for example) I've found that a usefull possibility was missing: we couldn't go back to "ASSIGNED" once we've moved forward. I've updated the workflow to re-enable this possibility. In some cases, like bug 7143, once a patch has been pushed, we just want to go back to assigned because another patch may have to be submitted, the 7143 is an omnibus. -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

1 0