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

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

Re: [Koha-devel] Koha 3.4.1 upgarde - failed: Access denied for user 'kohaadmin'@'localhost' (using password: YES)
by Fridolyn SOMERS 30 May '11

30 May '11

Your welcome. On Mon, May 30, 2011 at 10:56 AM, ISM KIS <Ism(a)kis.in> wrote: > Yes, thanks, got it. > There was a spelling mistake for the password in the .xml > > I guess I installed it too many times. > The remove_items_from_biblioitems.pl is now running. > > Thanks again for pointing me to the right file. > > Rudy Wuthrich > > > >>> Fridolyn SOMERS <fridolyn.somers(a)gmail.com> 5/30/2011 2:04 PM >>> > Hie, > > Database name, host, port, user ... > are stored into Koha main configuration file koha-conf.xml (mostly in > /etc/koha/) > look at the end of the XML. > > On Fri, May 27, 2011 at 11:01 AM, ISM KIS <ism(a)kis.in> wrote: > > > Yes, I can access mysql -u -p -Dkoha > > Where does remove_items_from_biblioitems.pl --run take the username and > > password from? > > > > Rudy > > > > > > >>> Fridolyn SOMERS <fridolyn.somers(a)gmail.com> 5/27/2011 1:55 PM >>> > > Check if kohaadmin can access (via mysql -u -p -D<base name>) the Koha > > database. > > > > Regards, > > > > On Thu, May 26, 2011 at 12:44 PM, ISM KIS <Ism(a)kis.in> wrote: > > > > > I am still in the process of upgrading our Koha from 3.00.06 to 3.4.1 > > > > > > Installation is ok. I could import the data from 3.0.6 and did the > > database > > > update from the :8080 interface. > > > > > > But then when I run the script to remove the biblioitems I get the > > > following error message: > > > > > > koha34:/opt/kohaclone/misc/maintenance # perl > > > remove_items_from_biblioitems.pl --run > > > DBI connect('dbname=koha;host=localhost;port=3306','kohaadmin',...) > > failed: > > > Access denied for user 'kohaadmin'@'localhost' (using password: YES) > at > > > /opt/kohaclone/koha-tmpl/lib/C4/Context.pm line 692 > > > Access denied for user 'kohaadmin'@'localhost' (using password: YES) > at > > > /opt/kohaclone/koha-tmpl/lib/C4/Context.pm line 692. > > > > > > What does that mean? > > > ( By the way: I' m able to access mysql -ukohaadmin -pxxxxx ) > > > > > > Any ideas? > > > > > > Rudy Wuthrich > > > Kodaikanal International School > > > > > > _______________________________________________ > > > 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/ > > > > > > > > > > > -- > > Fridolyn SOMERS > > ICT engineer > > PROGILONE - Lyon - France > > fridolyn.somers(a)gmail.com > > > > > > > -- > Fridolyn SOMERS > ICT engineer > PROGILONE - Lyon - France > fridolyn.somers(a)gmail.com > > -- Fridolyn SOMERS ICT engineer PROGILONE - Lyon - France fridolyn.somers(a)gmail.com

1 0

Re: [Koha-devel] Koha 3.4.1 upgarde - failed: Access denied for user 'kohaadmin'@'localhost' (using password: YES)
by Fridolyn SOMERS 30 May '11

30 May '11

Hie, Database name, host, port, user ... are stored into Koha main configuration file koha-conf.xml (mostly in /etc/koha/) look at the end of the XML. On Fri, May 27, 2011 at 11:01 AM, ISM KIS <ism(a)kis.in> wrote: > Yes, I can access mysql -u -p -Dkoha > Where does remove_items_from_biblioitems.pl --run take the username and > password from? > > Rudy > > > >>> Fridolyn SOMERS <fridolyn.somers(a)gmail.com> 5/27/2011 1:55 PM >>> > Check if kohaadmin can access (via mysql -u -p -D<base name>) the Koha > database. > > Regards, > > On Thu, May 26, 2011 at 12:44 PM, ISM KIS <Ism(a)kis.in> wrote: > > > I am still in the process of upgrading our Koha from 3.00.06 to 3.4.1 > > > > Installation is ok. I could import the data from 3.0.6 and did the > database > > update from the :8080 interface. > > > > But then when I run the script to remove the biblioitems I get the > > following error message: > > > > koha34:/opt/kohaclone/misc/maintenance # perl > > remove_items_from_biblioitems.pl --run > > DBI connect('dbname=koha;host=localhost;port=3306','kohaadmin',...) > failed: > > Access denied for user 'kohaadmin'@'localhost' (using password: YES) at > > /opt/kohaclone/koha-tmpl/lib/C4/Context.pm line 692 > > Access denied for user 'kohaadmin'@'localhost' (using password: YES) at > > /opt/kohaclone/koha-tmpl/lib/C4/Context.pm line 692. > > > > What does that mean? > > ( By the way: I' m able to access mysql -ukohaadmin -pxxxxx ) > > > > Any ideas? > > > > Rudy Wuthrich > > Kodaikanal International School > > > > _______________________________________________ > > 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/ > > > > > > -- > Fridolyn SOMERS > ICT engineer > PROGILONE - Lyon - France > fridolyn.somers(a)gmail.com > > -- Fridolyn SOMERS ICT engineer PROGILONE - Lyon - France fridolyn.somers(a)gmail.com

1 0

How to gather better popularity data?
by MJ Ray 27 May '11

27 May '11

We're often asked for better data on who is using Koha. For full disclosure listings, there are good places (like wiki.koha-community.org, when account registration works again) and so-so places (like libwebcats with its incomplete representation of library-support relationships and potential for helping Social Engineering attacks), but what about collecting basic usage data? A side-effect of the use of debian packages is that koha appears on http://popcon.debian.org/ (14 installations) and http://popcon.ubuntu.com/ (3 installations). Do other distributions have similar things? Have many koha package users installed and activated the popularity-contest package? Can we get more data consensually? How should we do this? A question in the web installer/upgrader? Plus a weekly heartbeat cronjob? What data should we ask for? Can we leave it up to libraries how anonymous they will be? Basic return is "Koha in use" with some generated unique identifier, semi-anonymous response adds which country they are in and how many branches they have, full response includes catalogue name? I assume this can go in 3.6. Would the 3.4 RM accept it? Thanks for any feedback, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. http://koha-community.org supporter, web and LMS developer, statistician. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire for Koha work http://www.software.coop/products/koha

9 16

FW: Code simplicity document
by Marcel de Rooy 27 May '11

27 May '11

Liked that article! As relative new member of the community, I am wondering if the current signoff/passed_qa procedure really encourages new members to keep sending patches. It could happen easily now that a patch does not get any attention. What makes someone now select a patch for signoff? Coincidence, contacts, application feature? imo we need some more structure at the signoff side. We have the Bugzilla categories that define the default assignment for a new bug. Would it be useful to assign a default signer per category too? Such assignments could be evaluated regularly to see if they still work. Marcel ________________________________________ Van: koha-devel-bounces(a)lists.koha-community.org [koha-devel-bounces(a)lists.koha-community.org] namens Paul Poulain [paul.poulain(a)biblibre.com] Verzonden: maandag 9 mei 2011 15:46 Aan: koha-devel(a)lists.koha-community.org Onderwerp: [Koha-devel] Document to read Hello, chris gave this url on IRC, I think it's worth sharing : http://www.codesimplicity.com/post/open-source-community-simplified/ it's a great document. I think it's worth asking ourself : "what are we doing well, what could we improve" This question is specifically sent to new contributors: what did we well, what could be improve for new/future newbies ? -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 _______________________________________________ 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/

7 7