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

Z3950 search/UNIMARC
by Marcel de Rooy 06 Jun '11

06 Jun '11

Hi all, I am testing some changes in z3950_search.pl and I am wondering if the default Koha z3950 script correctly functions for unimarc targets (with marcflavor to unimarc as well of course). Could anyone of you using z3950 with unimarc reply on that? Is the MARC and Card view on the results screen correct too? Did you encounter problems with encodings? MARC-8, UTF-8, etc.? I tested with carmin.sudoc.abes.fr z3950 target? Could you recommend another one? Thanks for some feedback, Marcel

2 1

EAN-13 barcode support
by Dobrica Pavlinusic 06 Jun '11

06 Jun '11

I need to develop EAN-13 barcode support in next two weeks to migrate one university library from custom software. First step should be creation of RFC document, but I didn't receive confirmation e-mail from wiki, so I can't add it there directly. I tried with this and gmail.com e-mail address, so I would be greatful if somebody could help me with that. Basically, library now uses EAN-13[1] barcode which is zero-padded primary key in old system istead of ISBN or ISSN. Since books allready have barcodes on them, we can't change it. To make things more insteresting, at least one barcode reader reports it as UPC-A[2] without first leading zero, since EAN-13 has backwards compatibility with it. So, my first question is should I store barcodes padded with zeros in Koha? It seems that itemBarcodeInputFilter syspref and small change to barcodedecode in C4/Circulation.pm will support both solutions, and it seems to be that 13-digit EAN-13 with padded zeros is cleaner solution. Next, I would need to implement plugin which generates new barcodes in same format (with check digit). This would involve change to autoBarcode syspref in cataloguing/value_builder/barcode.pl and new C4/Barcode/EAN13.pm to support next barcode while ignoring last checksum digit. Finally, we need to print them. PDF::Reuse::Barcode allready supports EAN13, so it seems that small change to C4/Labels/Label.pm would be sufficiant. Am I missing something important other than tests? :-) 1: http://en.wikipedia.org/wiki/EAN-13 2: http://en.wikipedia.org/wiki/UPC-A -- Dobrica Pavlinusic 2share!2flame dpavlin(a)rot13.org Unix addict. Internet consultant. http://www.rot13.org/~dpavlin

3 4

Re: [Koha-devel] Koha-devel Digest, Vol 67, Issue 7
by massoud alshareef 04 Jun '11

04 Jun '11

I second Chris's thought. There is only one community-driven OSS Koha! Thanks Massoud M. AlShareef, KnowledgeWare On Sat, Jun 4, 2011 at 1:00 PM, <koha-devel-request(a)lists.koha-community.org > wrote: > Send Koha-devel mailing list submissions to > koha-devel(a)lists.koha-community.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > or, via email, send a message with subject or body 'help' to > koha-devel-request(a)lists.koha-community.org > > You can reach the person managing the list at > koha-devel-owner(a)lists.koha-community.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Koha-devel digest..." > > > Today's Topics: > > 1. Re: KOHA version 3.0, my question is about the advantages of > KOHA 4 (Chris Cormack) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 4 Jun 2011 19:32:09 +1200 > From: Chris Cormack <chris(a)bigballofwax.co.nz> > Subject: Re: [Koha-devel] KOHA version 3.0, my question is about the > advantages of KOHA 4 > To: Clay Fouts <cfouts(a)liblime.com> > Cc: koha-devel(a)lists.koha-community.org > Message-ID: <BANLkTinqDbmXc3JhvkkvZnKRKxC4GqvRog(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > 2011/6/4 Clay Fouts <cfouts(a)liblime.com>: > > Github makes patch submission very easy. The typical process is to fork > the > > repository, commit your changes to your own fork (often on a topic > branch), > > then submit a pull request to the maintainer of the forked project. The > web > > interface provides simple buttons for forking (e.g. the LK-4.2 fork link > is > > https://github.com/liblime/LibLime-Koha/fork) and issuing pull requests. > The > > maintainer receives notification of the pull request and can then opt to > > merge the new commits back into the original repository. > > The service offers a nice interface to the whole code management process > and > > provides additional features for discussing patches, providing > line-by-line > > commentary, basic issue tracking, docs wiki, and so on. They offer public > > repositories for free, so there's a very low barrier to entry for open > > source developers. > > > > Internally we have released LK-4.4 and 4.6 into production and are now > > working on development branch 4.7. These are not publicly accessible, and > > that makes development of larger features pretty tricky if you're working > on > > the 4.2 release as your base. Anyone interested in creating a more > involved > > feature and ensuring it can be easily ported to future releases should > > consult us for pointers as there are notable architectural and schema > > differences. > > Right, perhaps we should move this off the Koha lists, Liblime run > their own lists for their project. This discussion about how to > contribute to the Liblime project is better there. > > Its fairly clear from Clays message, and comments on my blog etc that > what Liblime is developing is not Koha, and has diverged > significantly. So I say lets just keep discussion about Koha here, and > unless the discussion turns to how to reconcile the fork with the Koha > project, leave discussion of Liblime's Project for their own lists. > We don't discuss Koha on the Evergreen lists, and OPALS don't discuss > their project on the Koha lists. Liblime have their own project with > their own lists, lets leave them to it and get back to focusing on > Koha. > > Chris > > > ------------------------------ > > _______________________________________________ > Koha-devel mailing list > Koha-devel(a)lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > > End of Koha-devel Digest, Vol 67, Issue 7 > ***************************************** >

1 0

Koha 3.2.x String Freeze
by Chris Nighswonger 02 Jun '11

02 Jun '11

Hi all, The 3.2.x branch is in a string freeze for the 3.2.10 release as of the time of this email. I'm a few hours late, but needed to catch up on pushing some changes to the main repo. Keep in mind that 3.2.10 will most likely be the final release of the 3.2.x branch. Kind Regards, Chris

1 0

Trouble with email in 3.4
by Magnus Enger 01 Jun '11

01 Jun '11

Hi all! I'm having some trouble with email in both current master and 3.4.1. * The setup - EnhancedMessagingPreferences is set to "Allow" - No circulation alerts are disabled under "Item Circulation Alerts" - Turning things off and on in the "Default messaging preferences for this patron category" does not affect the outcome - Emails for the patron I'm testing is enabled for check in/check out (and shows as enabled both in the OPAC and staff client) * The symptom When check ins and check outs are done for the patron I'm testing with, no emails show up, and no messages are ever put in the message_queue table in the database. The oldest circ message in there is dated 2011-03-18, but I'm not sure how much it has been used after that. I can see some HOLD messages from 2011-04-06 and one REJECTED purchase suggestion from today, so some things are working. The problem was reported after the upgrade from 3.2.6 to 3.4.1 this last weekend. I can reproduce it on a live system running 3.4.1 (+ the most recent batch of patches on the 3.4.x branch) and on a test system running current master. * The investigation I have tried diggin around in the code, and found that in SendCirculationAlert() in C4/Circulation.pm, $borrower_preferences is empty: sub SendCirculationAlert { my ($opts) = @_; my ($type, $item, $borrower, $branch) = ($opts->{type}, $opts->{item}, $opts->{borrower}, $opts->{branch}); my %message_name = ( CHECKIN => 'Item Check-in', CHECKOUT => 'Item Checkout', ); my $borrower_preferences = C4::Members::Messaging::GetMessagingPreferences({ borrowernumber => $borrower->{borrowernumber}, message_name => $message_name{$type}, }); ... This is in turn caused by the SQL GetMessagingPreferences() in C4/Members/Messaging.pm: SELECT borrower_message_preferences.*, borrower_message_transport_preferences.message_transport_type, message_attributes.message_name, message_attributes.takes_days, message_transports.is_digest, message_transports.letter_module, message_transports.letter_code FROM borrower_message_preferences LEFT JOIN borrower_message_transport_preferences ON borrower_message_transport_preferences.borrower_message_preference_id = borrower_message_preferences.borrower_message_preference_id LEFT JOIN message_attributes ON message_attributes.message_attribute_id = borrower_message_preferences.message_attribute_id JOIN message_transports ON message_transports.message_attribute_id = message_attributes.message_attribute_id AND message_transports.message_transport_type = borrower_message_transport_preferences.message_transport_type WHERE message_attributes.message_name = 'Item Check-in' AND borrower_message_preferences.borrowernumber = 51; not retuning anything: Empty set (0.00 sec) Now I must confess that all those JOINs are making my head spin... Here are the actual contents of the tables involved in that query: mysql> select * from borrower_message_preferences where borrowernumber = 51; +--------------------------------+----------------+--------------+----------------------+-----------------+--------------+ | borrower_message_preference_id | borrowernumber | categorycode | message_attribute_id | days_in_advance | wants_digest | +--------------------------------+----------------+--------------+----------------------+-----------------+--------------+ | 56 | 51 | NULL | 2 | 0 | 0 | | 57 | 51 | NULL | 6 | NULL | 0 | | 58 | 51 | NULL | 4 | NULL | 0 | | 59 | 51 | NULL | 1 | NULL | 0 | | 60 | 51 | NULL | 5 | NULL | 0 | +--------------------------------+----------------+--------------+----------------------+-----------------+--------------+ mysql> select * from message_attributes; +----------------------+----------------+------------+ | message_attribute_id | message_name | takes_days | +----------------------+----------------+------------+ | 1 | Item_Due | 0 | | 2 | Advance_Notice | 1 | | 4 | Hold_Filled | 0 | | 5 | Item_Check_in | 0 | | 6 | Item_Checkout | 0 | +----------------------+----------------+------------+ mysql> select * from message_transports; +----------------------+------------------------+-----------+---------------+-------------+ | message_attribute_id | message_transport_type | is_digest | letter_module | letter_code | +----------------------+------------------------+-----------+---------------+-------------+ | 5 | email | 0 | circulation | CHECKIN | | 5 | sms | 0 | circulation | CHECKIN | | 6 | email | 0 | circulation | CHECKOUT | | 6 | sms | 0 | circulation | CHECKOUT | | 1 | email | 0 | circulation | DUE | | 1 | sms | 0 | circulation | DUE | | 1 | email | 1 | circulation | DUEDGST | | 1 | sms | 1 | circulation | DUEDGST | | 2 | email | 0 | circulation | PREDUE | | 2 | sms | 0 | circulation | PREDUE | | 2 | email | 1 | circulation | PREDUEDGST | | 2 | sms | 1 | circulation | PREDUEDGST | | 4 | email | 0 | reserves | HOLD | | 4 | sms | 0 | reserves | HOLD | +----------------------+------------------------+-----------+---------------+-------------+ * The questions - Is anyone else seeing the same behaviour? - Can anyone spot what's going on? I'd be happy to create a bug for this, I just thought I'd try and figure out if it *is* a bug, or if I have done something silly (again), first... Best regards, Magnus Enger libriotech.no

1 0

sysprefs.sql Norway
by Marcel de Rooy 01 Jun '11

01 Jun '11

Magnus, I rebased a patch today for installing a pref. While adding this pref to the sysprefs.sql file in the norway directory, it seems that it has not yet been updated by a few recently pushed patches. Would you mind taking a look? Marcel

2 1

Kohacon : We would love to hear your ideas and achievements
by Koustubha Kale 01 Jun '11

01 Jun '11

Hi All, We would like you to share your knowledge, expertise and experience with us at Kohacon11 at VPM, Thane, India from 31st October 2011 to 2nd November 2011. Please send in your presentations. For your information please see the call for papers reproduced below.. Call for Papers The 2011 Koha Conference committee is requesting proposals for papers and presentations. Presentations should cover topics of interest to current and future users of Koha. The conference is expected to have a wide variety of attendees, including - Library administrators - Librarians - Programmers and system administrators Presentations should be approximately 45 minutes in length and allow time for questions. Presenters can expect to have Interest access and a computer projector for slides and, if necessary, a laptop computer with standard presentation software. When submitting your proposal, please include - The name and institutional affiliation of each presenter - Contact information, particularly email address - The target audience for your presentation (e.g. introductory, technical, administrative, etc.) - The proposed title of your presentation - A brief description suitable for publishing in the conference program. Descriptions should be no longer than 250 words. Author Guidelines The process for submission is Abstract followed by proposal (2 rounds of review required; first for abstract, second for proposal) Please try to submit your papers as early as possible. *The deadline forsubmissions is 15th August 2011. * Start here to submit a paper to this conference. STEP ONE OF THE SUBMISSION PROCESS<http://kohacon11.vpmthane.org/ocs/index.php/k/k11/author/submit?requiresAut…> ( http://kohacon11.vpmthane.org/ocs/index.php/k/k11/author/submit?requiresAut…) Please feel free to contact me for any assistance, queries, offers of help, sponsorship, comments etc. My contact information is given below. Regards, Koustubha Kale Anant Corporation Contact Details : Address : 103, Armaan Residency, R. W Sawant Road, Nr. Golden Dyes Naka, Thane (w), Maharashtra, India, Pin : 400601. TeleFax : +91-22-21720108, +91-22-21720109 Mobile : +919820715876 Website : http://www.anantcorp.com Blog : http://www.anantcorp.com/blog/?author=2

1 0

Hardware requirements and cluster scalability
by Olli-Antti Kivilahti 01 Jun '11

01 Jun '11

Good day to everybody at the devel-list. And greetings from Finland! The library of Joensuu has started a project to compare different open source library systems, mainly Koha and Evergreen, with the goal of moving from our current closed source system to open source. We are planning to create a consortium of minimum of a ~20 libraries, but if open ILS are found to be superrior, probably the consortium can easily grow to ~250 libraries with ~5 million articles and ~150 000 transactions/hour. I have been hard pressed to find answers to the hardware requirements of Koha and Evergreen and have been instructed to ask here on devel-list by your library managers. My main interests are the hardware requirements of the said large consortium mainframe. How well does it cluster? What sort of hard disk and ram requirements are there? How many pc units with for example 2GHz cpu, 2Gb RAM do we need? Could every library host their own databases or should they be centralized? What are the average search speeds using simple SELECTs and then complex JOINs. What are the system bottlenecks? Can the OPAC be integrated with Drupal/Liferay so it can be compatible with our new web-services strategy? Are there any publications I could read about these topics? Happy coding! -- Olli-Antti Kivilahti Open Library 2013 Library of Joensuu

3 2

Super-tiny script to check for record errors before upgrading to 3.4.x
by Tomas Cohen Arazi 31 May '11

31 May '11

Hi, being back to work after a few weeks abroad is a bit difficult, but here I am. Back to koha, and back to Perl suff. We are just planning our upgrade to 3.4 and face the problem that our install base (+30 libraries/koha deploys and growing) has several enconding (and posibly other) problems carried from the initial migration from different sources and encodings. Those problems obviously arise now that we have to access all the records to remove holdings information from them, and running remove_items_from_biblioitems.pl waiting for it to fail and discover "where" it failed is not suitable for us. So... I managed to get a script to tell me which records are "problematic" in the sense koha defines problematic. I'd like some other dev to take a look at it to check it. It can be obviously beautified and improved. There's a link here so anyone can read it: http://blogs.unc.edu.ar/koha/lang/en/2011/05/31/migracion-a-3-4-surgen-prob… Thanks in advance To+

1 0

Koha 3.2.x Roadmap Update
by Chris Nighswonger 30 May '11

30 May '11

Hi all, With the release of 3.2.10 fast approaching, there are a couple of things our attention needs to be drawn to: 1. Pending any consensus otherwise a the July 2011 IRC meeting, 3.2.10 will be the final release of the 3.2.x branch, and 3.2.x will be EOL after that point. 2. If you have bugfixes you want to go into 3.2.10, please be sure to get those into master before the string freeze date of 1 June 2011. That is two days away. I will push changes which do not affect strings up to the day before the release on 15 June 2011. 3. No bugfixes made to TT templates have been pushed to 3.2.x for obvious reasons. If you have a template change you want pushed into 3.2.x, you will have to submit a patch directly against 3.2.x and flag it with [3.2.x] in the subject line. Thanks for everyone's work in making 3.2.x the first of what we hope are many successes in timed releases! Kind Regards, Chris Nighswonger Koha 3.2.x/3.4.x Release Maintainer

1 0