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

stocknumber and invertory books in Koha
by Dobrica Pavlinusic 18 Jan '12

18 Jan '12

I need help from people who use stocknumbers in their Koha's installs. I assume this is mostly Europe-specific since we are required by low to keep invetory books with each item in our library but I hope that other people might have similar legal requirements. For a start, why is index defined on items.stocknumber non-unique? I would assume that it has to be unique like barcode is (at least that's our legal requirement). Other than that, we need to have some representation of "inventory book" which I plan to implement using additional local table in which I will record stocknumber, biblionumber and various other fields required for invertory book reporting. This duplicates data (which is bad if you ever heard for normal forms in RDBMS), but it's required to cover case of erasing items. If we don't have a copy of item, erased it would also erase entry from invetory book which is very, very bad. During implementation of this feature, I stumbled upon bug 7451[1] which breaks AJAX value_builder in which I plan to implement assigment of next invetory number and copying of data into separate invetory audit table. Would this value_builder be useful to other Koha users, or is it too specific for our use-case? 1: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7451 -- Dobrica Pavlinusic 2share!2flame dpavlin(a)rot13.org Unix addict. Internet consultant. http://www.rot13.org/~dpavlin

3 5

3.6.x String Freeze [WAS: 3.6.3 Update]
by Chris Nighswonger 18 Jan '12

18 Jan '12

Ok, in spite of my worst fears, the issues mentioned below have been resolved and the 3.6.x branch is now in a string freeze. I'm planning to release on 25 Jan 2012, giving the translators a week to update translations. See you in a week! :-) Kind Regards, Chris Koha 3.4.x/3.6.x Release Maintainer On Tue, Jan 17, 2012 at 10:50 PM, Chris Nighswonger < cnighswonger(a)foundations.edu> wrote: > 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

Bug-enhancement patch Workflow
by Marcel de Rooy 18 Jan '12

18 Jan '12

Hi All, See http://wiki.koha-community.org/wiki/Bug-enhancement-patch_Workflow What should we add to this page about the new Pushed to Master / Pushed to Stable status? How can we prevent that further development on a report (followups etc.) interferes with the process of selecting patches for the maintenance branch? Example: If I have a new followup 2 after patch 1 has been pushed to master, I would like to change status directly to Needs Signoff for patch 2. (But in the meantime Chris N may select patch 1 for maintenance. How? ) Any input is welcome, especially from Chris N here, I suppose.. Marcel

2 1

Bugzilla (small) change
by Paul Poulain 18 Jan '12

18 Jan '12

Hello all, The changes made by Ian last week-end are great, but someone made a small mistake with "PATCH sent" priority that was still visible. This field should not be used anymore, as it's replaced by the bug status "needs signoff". I made a small change in bugzilla parameters: * the priority "patch sent" is now invisible for new bugs * all open bugs still have the "patch sent" priority, but i've updated the description, and it's not "patch sent (DO NOT USE)", and it's at the end of the list. We could also repeat what Ian did last week: * suspend any mail * bulkupdate priority to set "Priority 3 (medium)" for all entries * remove "Patch sent" priority * restore mail sending but I'm not sure it's worth it, as this change has a small but nasty side effect= all bugs would have the same "last modification date", and this information is sometimes usefull (at least for me) : if a bug stays for a long time in a given status, then I tend to take care of it 1st ! -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

2 2

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