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

News from BibLibre
by Paul Poulain 27 Jan '14

27 Jan '14

Hi, Most of you probably saw it on twitter or google+, but for the others, there's an important announcement for BibLibre: http://www.biblibre.com/en/blog/afi-and-biblibre-are-getting-closer There won't be any visible change for the Koha community, except, maybe, some new developers submitting or testing patches, which is always good ;-) For libraries that could be interested in our services, that's an important change though: with a larger company, we can manage larger contracts. Until now, we focused on French libraries. 2014 will be the year where we focus on EU libraries. The 1st contract 2014 has been with a Swedish institute in Roma. Others coming soon, hopefully, so stay tuned ;-) Have a good day PS: AFI has some OpenSource (GPL v3) tools& softwares, french-centric, that we plan to promote after making them less french-centric ;-) Stay tuned here as well ! -- Paul POULAIN - BibLibre http://www.biblibre.com Free & Open Source Softwares for libraries Koha, Piwik, Jasper

1 0

git bz: UnicodeDecodeError
by Holger Meissner 24 Jan '14

24 Jan '14

Dear Koha devs, I just tried to attach a patch to a bug with git bz and got this error: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 561: ordinal not in range (128) How can I fix this? Thanks Holger

2 1

opac error logs filled with messages about 'UNIVERSAL->import is deprecated ...'
by Doug Kingston 24 Jan '14

24 Jan '14

Messages like this are appears nearly constantly from both 3.12 and 3.14 version of Koha. I checked cpan and it claims I have the latest version of Memoize::Memcached. Anyone else seeing this? [Mon Jan 20 17:42:32 2014] [error] [client 127.0.0.1] [Mon Jan 20 17:42:32 2014] Memcached.pm: UNIVERSAL->import is deprecated and will be removed in a future perl at /usr/local/share/perl/5.14.2/Memoize/Memcached.pm line 6., referer: http://catalogue.efdss.org/cgi-bin/koha/opac-basket.pl?bib_list=62755/63336/ Regards, -Doug-

2 1

Re: [Koha-devel] [Koha] Problems with frameworks
by Marcel de Rooy 23 Jan '14

23 Jan '14

It seems to me that 541$e should not map to an item field (in the first place). I checked my data, i do not have it mapped to a koha field. I have 952$i mapped to stocknumber (although we do not use it). Note also that there is a patch for stocknumber (bugzilla 10544) -----Oorspronkelijk bericht----- Van: koha-bounces(a)lists.katipo.co.nz [mailto:koha-bounces@lists.katipo.co.nz] Namens Mark Tompsett Verzonden: woensdag 22 januari 2014 18:14 Aan: koha(a)lists.katipo.co.nz Onderwerp: [Koha] Problems with frameworks Greetings, I am use 3.14.x and master, though I think this problem goes back a bit further. I am using MARC21. I log into the staff client. I click Koha administration. I click MARC bibliographic framework. In the left hand side, I scroll down to find MARC bibliographic framework test. I click it. I am then shown a pretty table, which tells me “You have 1 error(s) in your MARC configuration. Please fix them before using Koha”. I have back end access, so I figured I’d try to make sense of the message. I see it ran http://192.168.45.28:8080/cgi-bin/koha/admin/checkmarc.pl, so I take a look at the source for admin/checkmarc.pl to see if I can determine how the error was triggered. The second line in the table says “item fields”, so I figure it is talking about lines 87 to 110 in master. I see the SQL is: select tagfield,tab,kohafield from marc_subfield_structure where kohafield like "items.%" and tab >=0; So, I try running that in my backend mysql client. There are 447 rows, and most are on tab 10, but tag 541 isn’t always? It’s items.stocknumber and so I try a different query: select tagfield,tagsubfield, tab,kohafield,frameworkcode from marc_subfield_structure where kohafield like "items.stocknumber"; And here in begins the confusion. I see that 952$i and 541$e are sometimes mapping to the same kohafield items.stocknumber, and occasionally they are not. I also see 541$e sometimes on tag 5, 9, or 10. So, can anyone clear up what they should map to, if anything, and what tab they are supposed to be on? GPML, Mark Tompsett _______________________________________________ Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha

2 1

Splitting bugs into multiple patches
by Holger Meissner 23 Jan '14

23 Jan '14

Dear Koha devs, Another question. Is there any rule of thumb into how many parts a bug should be split? For example, if I add a few lines in a perl module, modify two intranet HTML templates and an OPAC HTML template. Should this be divided into three commits? Or just one, since you can't easily test the perl module without the templates? Or one part for the pm and intranet changes and another for the OPAC changes? Thank you! Holger

2 1

opac-user.tt
by Holger Meissner 23 Jan '14

23 Jan '14

Dear Koha devs, I'm working on Bug 7413 and one thing I want to do is modify opac-user.tt. I noticed that there are two versions of it: koha-tmpl/opac-tmpl/bootstrap/en/modules/opac-user.tt koha-tmpl/opac-tmpl/prog/en/modules/opac-user.tt The later doesn't seem to be used, at least by my install. Do I need to modify both, or just bootstrap? Is there a way to switch bootstrap off, so that I can test changes in the other one? Thanks Holger

3 2

Duplicating Records = Replacing Records?
by Andrea Furin 22 Jan '14

22 Jan '14

Hi. When I try to duplicate a record, koha overwrites the old one: searching for that title (opac and biblio) returns only the last modified record - with duble koha id. Some solutions? One is to delete fields: 000@ 001@ 005@ 100a --

1 0

Advice on syncing and DBIC
by Magnus Enger 21 Jan '14

21 Jan '14

Hi! I am working on Bug 11401 - Add support for Norwegian national library card: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11401 The goal is to sync patrons in Koha back and forth to the Norwegian national patron database. In order to do this I need to keep track of - which patrons should be synced (they can choose to opt out of the syncing) - a sync status, to see which patrons are new, which have been changed and which are already synced - the date of the last sync I am a bit undecided about whether I should use extended patron attributes for this, or add columns to the "borrowers" table. Some pros and cons: - Attributes are less intrusive, they only need to be added to systems that want to sync with the Norwegian national patron database. - New columns could be re-used by others, to implement other syncing schemes, and they are easier to work with, as far as I can see. I am currently leaning towards adding columns. Now the thing is that I want to change the "syncstatus" every time AddMember or ModMember is called, so I want to add some logic to these subroutines, perhaps like this ("..." indicates lines that have been edited out for clarity): use Koha::Database; ... sub AddMember { my (%data) = @_; ... $data{'borrowernumber'}=InsertInTable("borrowers",\%data); # If NorwegianPatronDBEnable is enabled, we set the nllastsync attribute to something that a # cronjob will use for syncing with NL if ( C4::Context->preference('NorwegianPatronDBEnable') == 1 ) { my $borrower = Koha::Database->new->schema->resultset('Borrower')->find( $data{'borrowernumber'} ); $borrower->update( { 'syncstatus' => 'new' } ); } ... } Would that be an OK way to do it? Or is mixing in DBIC in existing subroutines like this frowned upon? Would it be cleaner to add a module like Koha::Borrower::Sync (that could be re-used by other syncing schemes), with methods like SetBorrowerSyncstatus( $patronnumber, $value ) that would then look something like this: use Koha::Database; sub SetBorrowerSyncstatus { my ( $borrowernumber, $value ) = @_; my $borrower = Koha::Database->new->schema->resultset('Borrower')->find( $borrowernumber ); $borrower->update( { 'syncstatus' => 'new' } ); } Any advice on this would be much appreciated! Best regards, Magnus

3 2

SQL Query : multiple items
by Paul A 21 Jan '14

21 Jan '14

I'm going round in circles for what I thought would be easy, and will kick myself later. Trying to write a "report" that will give me all biblios with more than 1 item: SELECT biblionumber, CONCAT('<a href=\"/cgi-bin/koha/catalogue/detail.pl?biblionumber=',biblionumber,'\">',title,'</a>') AS Title, author AS Author FROM biblio b LEFT JOIN items i USING (biblionumber) GROUP BY i.ccode HAVING COUNT(i.itemnumber)>1; works syntactically, but certainly does not give me the right answers -- it produces biblios with 0, 1, 2, etc items, and only 83 total lines when I know that there are thousands... Logic seems to have deserted me. Help please? As a bonus, I'd appreciate how to add the items.ccode into the report. Adding SELECT ccode FROM items either before or after the JOIN fails. Thanks and br -- Paul

3 3

Suggestion for OPAC theme bug fix patches
by Galen Charlton 21 Jan '14

21 Jan '14

Hi, If you're writing a patch that fixes a bug with an OPAC template file, you'll need to at least touch the Bootstrap theme, but you may also want to touch the prog theme if you think the fix should be backported back to 3.12.x or earlier. Here's my suggestion: if you do that, please put your prog and Bootstrap template changes in separate patches. That way, it will be easier for the RMaints for 3.12.x, 3.10.x, and 3.8.x to cherry-pick the appropriate patches without having to manually disentangle out the Bootstrap theme bits that don't apply. This, in turn, will likely increase the chance of your bugfix being backported. Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc(a)esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org

3 2