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

EDI & X12 standard
by Mohamed zalabany 17 Jun '16

17 Jun '16

Hi AllDoes any one have any idea about using KOHA with EDI and x12 standard with acqusation moduleDoes KOHA support EDI or not and if there any documentation related to this issueAll Best Mohamed ElzalabanyEgyptian Prime Vision

2 1

Upgrading bugzilla server
by Chris Cormack 16 Jun '16

16 Jun '16

Hi all At some point today the bugzilla server is going to reboot and come back with more RAM. Hopefully everything else comes back fine too. If not please let me know Chris -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

1 0

Call for News: June 2016 Newsletter
by kohanews 15 Jun '16

15 Jun '16

Fellow Koha users ~ I'm collecting news for the June newsletter. Send anything noteworthy to: k o h a news AT gmail dot com News criteria: --------------------------- ** For events **: * - Please include dates for past events. If I can't find dates I may not add it. * - Announcements for future events with dates T.B.A. are fine ...Eg., Kohacon * - For past events -- **** one month back is the cut-off ***. * News items can be of any length. * Images are fine * Anything and everything Koha. * Submit by the 26th of the month. If you are working on an interesting project or development related to Koha, please let me know and I'll include it in the development section. -- Chad Roseburg Editor, Koha Community Newsletter

1 0

16.05 upgrade errors
by Barry Cannon 14 Jun '16

14 Jun '16

Hello, Has anyone had issues upgrading from 3.22.6/7 to 16.05 via deb packages? Fresh installs seem fine but I got a lot of errors when running the web installer upgrade, like below. There is a lot to go through so I end up rolling back and using 'oldstable'. Anyone noticed similar? I had to use pastebin for the output as it was too large to send to the list. http://pastebin.com/7TysWHM0 Thanks Regards Barry Cannon Interleaf Technology http://www.interleaf.ie Tel: +35312865855 Email: bc(a)interleaf.ie Skype: bar.cannon <http://conference.conul.ie/>

3 3

New intern at Biblibre, project : SharingDatasBetweenKohas
by morgane alonso 14 Jun '16

14 Jun '16

Good morning developers of the Koha Community. My name is Morgane Alonso and I'm a new intern at Biblibre for all summer. My project is to develop a webservice to centralize common informations between different libraries. It's based on crowd-sourcing, so librarian can search or send information to the central DB and say if the information is correct or not. For more information, I invite you to see the corresponding rfc <https://wiki.koha-community.org/wiki/SharingDatasBetweenKohas_rfc> (Paul already talks about it). We may used the same technologies implemented in Hea <http://hea.koha-community.org/>, which is a webservice to display statistics about Koha : - PerlDancer2 - JSON - Template Toolkit You can contact me by email, if you have comments or if you want more informations about the project. Have a nice day. Sincerely, Morgane Alonso

5 4

DBIx::Class and ONLY_FULL_GROUP_BY
by Jonathan Druart 09 Jun '16

09 Jun '16

Hi devs, Just to know if one of you already faced this issue: >From bug 16584, it seems that MySQL will now complained if the group by claused is not fully filled with the column we select. If you set ONLY_FULL_GROUP_BY in the sql_mode options of the my.cnf file, you will get Template process failed: undef error - DBIx::Class::Storage::DBI::_dbh_execute(): 'koha.me.shelfname' isn't in GROUP BY at /home/koha/src/Koha/Objects.pm line 204 at /home/koha/src/opac/opac-shelves.pl line 375 It's raised by one of the methods of Koha::Virtualshelves, because there is no 'select' defined. But if we define one, we will have to list of the column of the virtualshelves tables. This sounds a bit weird and I guess there is an alternative, but I have not found anything in the DBIx::Class doc. Any thoughts? Cheers, Jonathan

1 0

[NEW] What's on in Koha devel
by Jonathan Druart 09 Jun '16

09 Jun '16

Hi devs, First, sorry for the [NEW] flag, but it is to make sure everybody reading the ML will click :) I'd like to start a monthly "what's on" email which I will send to koha-devel. It comes after some discussions at the KohaCon16 with fellows that do not have the time to follow what's going on in the community and where they could help on important things. I used to send one to my partners every month to explain what I did and what I plan to do, but actually it sounds more a community report to send to the Koha developers. So here it is :) The goal is to resume in a (relatively) short email what has been developed in the previous month(s) and what testers/developers can focus on. It could be critical/major bugfixes, code refactoring/improvements or even big-but-amazing features waiting for signoff/QA. Over the last months I have mainly focused on refactoring stuffs, fix plack-related bugs and improvement issues, as well as my usual QA work. The refactoring part is not going very well, I have suspended it 2 months ago. The main problem is that the patches are no pushed as fast as I expected implying a lot of rebases which is time consuming. By refactoring I mean "moving code from old C4 modules to the new Koha namespace". The pattern I usually use in the bug report description is "Move the stuff related code to Koha::Stuff[s]" The plack-related bugs were minor, but to provide a full plack compatibility it was great to have them push quickly. Luckily they have been signed off and QAed quite quickly, only 2 are still waiting for QA. The pattern I used in the bug description was "This module is not plack safe". A few words about the performances: You have to know that since 16.05 (and maybe also 3.22) it's highly recommended to use Plack and Memcache to provide your user a good response time. We have profiled the code in several areas to find useless processing time. In some places, the code has been improved, in others it has completely been removed. Fixing plack bugs, we have found that we needed to improve our cache mechanism and we have introduced a L1 memory cache which should bring us performance gain between 3.22 and 16.05. Note that we do not have completely finished the work and some more has to been done, so stay tuned :) If you have any suggestions or leads on that, please open a bug report and assign it to me. There are 2 critical bugs waiting for signoff (bug 16554 and bug 16573), they fix the support of Ubuntu 16.04. So if you plan to install Koha on the latest Ubuntu, you should have a look at these 2 reports. A major enhancement is in the integration queue and it would be great to see some people (librarians would be awesome) involved in the testing process. It will allow a patron to place several holds on the same record (bug 14695). This feature has been expected for more than 3 years now and this is the third attempt. During the KohaCon16, I have organised a quick brainstorming about our implementation of Koha::Object[s] and how we use DBIx::Class. The goal was not to find a solution but to present the different issues we face. I'd like to bring again this discussion on koha-devel this month, listing the pros and cons of our current implementation, and gathering ideas to improve it. Hope this will be helpful for people not heavily involved on IRC or the bug tracker. Cheers, Jonathan References: Refactoring to Signoff Bug 15758 - Move the C4::Branch related code to Koha::Libraries - part 4 Bug 15803 - Koha::AuthorisedValues - Remove GetAuthorisedValueCategories Refactoring to QA Bug 15451 - Move the CSV related code to Koha::CsvProfile[s] Bug 15839 - Move the reviews related code to Koha::Reviews Bug 15801 - Move the framework related code to Koha::BiblioFramework[s] - part 2 Bug 15407 - Move the patron categories related code to Koha::Patron::Categories - part 2 Plack bugfixes to QA Bug 16441 - C4::Letters::getletter is not plack safe Bug 16443 - C4::Members::Statistics is not plack safe Performances entry points are (look at the related bugs using the show dependency graph): Bug 15342 - Performance 3.22 - Omnibus Bug 16044 - Define a L1 cache for all objects set in cache

4 3

KohaDevBox + MariaDB
by Tomas Cohen Arazi 07 Jun '16

07 Jun '16

Hi everyone, I wanted to share that we can now choose mariadb in KohaDevBox by setting mysql_engine: mariadb in the vars/user.yml file. Enjoy. -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F

2 3

SQL92 keywords and naming columns
by David Cook 31 May '16

31 May '16

I was wondering if we have any advice for naming columns, especially TIMESTAMP columns, so I looked on the wiki and found that we're not supposed to use SQL92 keywords: https://wiki.koha-community.org/wiki/Coding_Guidelines#SQL2:_SQL92_keywords I'm not super familiar with all the keywords, but I'm confident that "timestamp" is one of those keywords. Here's the distribution on a dev Koha I have: 'created', 1 'created_on', 2 'date', 1 'dateadded', 1 'date_uploaded', 2 'dtcreated', 1 'lastmodified', 1 'message_date', 1 'modification_time', 1 'needed', 1 'time', 2 'timestamp', 26 'time_queued', 1 'updated', 1 'upload_timestamp', 2 'validated', 1 'valid_until', 1 I thought I'd check out DATETIME as well. Interestingly, there is a DATETIME column named "timestamp" as well: 'datearrived', 1 'datereviewed', 1 'datesent', 1 'datetime', 1 'date_approved', 1 'date_created', 3 'date_due', 2 'date_modified', 1 'date_run', 1 'issuedate', 2 'itemlost_on', 2 'lastreneweddate', 2 'last_modified', 1 'last_run', 1 'returndate', 2 'sharedate', 1 'start_time', 1 'suspend_until', 2 'timeclicked', 1 'timestamp', 1 'withdrawn_on', 2 It seems undesirable to use timestamp for things like "upload_timestamp" and "message_date" as well, as TIMESTAMP will automatically update when that row is updated as per these conditions: http://dev.mysql.com/doc/refman/5.7/en/timestamp-initialization.html. Anyway, something to think about. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Office: 02 9212 0899 Direct: 02 8005 0595

2 1

More problems with MySQL 5.7
by Bernardo Gonzalez Kriegel 30 May '16

30 May '16

Hi, testing things on MySQL 5.7 - Koha 3.22, found a new problem: memberentry.pl: DBD::mysql::st execute failed: Expression #1 of SELECT list is not in GROUP BY clause and contains nonaggregated column 'kohadev.categories.categorycode' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by ... This comes trying to add a patron after fresh install, 3.22+marc21+all sample data Can we change sql_mode for Koha? Regards Bernardo -- Bernardo Gonzalez Kriegel bgkriegel(a)gmail.com

5 4