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

Koha 16.11.01 released
by Katrin 10 Jan '17

10 Jan '17

The Koha community is proud to announce the release of Koha 16.11.01 This is the first maintenance release of 16.11 and contains several bugfixes. The full release notes are available at https://koha-community.org/koha-16-11-01-released Packages will be available soon. Happy holidays!

1 1

What's on in koha-devel #9
by Jonathan Druart 09 Jan '17

09 Jan '17

Hello librarians and developers, I wish you a happy new year, 2017 will be awesome, I am sure :) At least it will be a great year for your favourite ILS - Koha is constantly improving and next releases will be even better than the last ones, as always :) = Hea = Some of us are still a bit hesitant about Hea because of the lack of communication around this project. It also seems that we would like to improve this tool and the way it displays data, to make it more attractive. To answer the first need, Chris wrote a privacy policy file [2]. You can send us feedback about it if things are not clear enough. To improve data collected by Hea, I have opened 3 bug reports (actually 1 was already opened): Bug 14608 will add an administration page for Hea, to make it more visible and understandable Bug 17802 will collect ideas (and patches?) about adding geolocation of Koha's installations Bug 17803 introduce the idea of collecting the number of libraries per installation. It will permit to know how many libraries are actually using Koha (vs the number of installations). If you are interested in these topics, get involved on the mailing list or the corresponding bug reports. = Benchmarks for 16.11 = I have compared Koha versions from 3.14.x to 16.11. The results have been posted on the wiki [3]. Everybody can replay these benchmarks easily, and some of you must do it to confirm (or not) these numbers. One important thing is that I noticed that the template caching system is not defined by default - however it brings a significant performance boost. I have opened a bug report (Bug 7533 - Add template_cache_dir to the koha-conf.xml file) to add the entry to the koha-conf file. This patch will also add a warning to the about page if the entry is not defined. If you are running a Koha install hosted by a (good) service provider, it should be correctly defined. But if you are self-hosted, you must definitely take a look at this configuration option. To play these benchmarks I needed to rebuild a database for each of these different versions of Koha. This job leads me to modify the scripts from the koha-misc4dev [4] repository. With these scripts I am now able to get a Koha installation fully testable (items, reindexation, psgi file, etc.) with any of these versions in a few minutes. That should be very useful for developers, especially to benchmark, bisect, archaeological digs or simply debug. = Important bugs waiting for love = Last month I have sent an email to koha-devel to list several important bugs waiting to be tested or QAed. It was very helpful as (almost) all of them got the expected love and have been boosted quickly. Note that we always have these kinds of important bugs, and I will try to think about a way to keep a list of them. A simple and naive approach would be to list the major, critical and blocker ones on the dashboard. Any thoughts? The one we want to see in quickly for now is Bug 17817 - Repeat this Tag (cloning) not working It is waiting for QA. Furthermore if you are confident with SIP you should take a look at the different SIP patches in the needs signoff (17758 Major, 17665, 17826, 16755, 15418, 13666) and signed off queues (16757, 16895 and 16899). = Refactoring = == Remove the biblioitems.marcxml field == This is the last call! Bug 17196 has now 4 independent signoffs, we need (at least) 1 QA guy to have a look at it. If it is not pushed quickly, I will block its integration into the next release. We do not want it to be pushed close to the release date. == Koha::Patrons == I have started to replace the C4::Member::GetMember subroutine with Koha::Patrons. You can take a look at bug 17829 to see the progress (check the remote branch on github). It's a massive change as it impacts a lot of file and it depends on lot of other patches not pushed yet to master. Using Koha::Patron will allow us to improve the REST API routes for the patron module. Moreover it will permit to manipulate patron objects and so to call the new methods recently added to our Koha::Patron module. That will make the code more readable than at the moment: only 1 patron structure will be manipulated and not 1 Koha::Patron object + the hashref returned by GetMember. Doing so the patron object will be sent to the templates and that will clean up a lot of scripts from the "members" module. = Standardize our EXPORT = Last month I talked about bug 17600. It did not get lot of attention. If nobody gets involved in the discussion I will put it aside. = Template Toolkit syntax for notices = Since Kyle's topic on the koha mailing list [1] did not receive any objections I will try and coordinate with him to move forward on this subject. The next general IRC meeting is on February 1st, 14 UTC. https://wiki.koha-community.org/wiki/General_IRC_meeting_1_February_2017 The next dev IRC meeting is on January 11th, 20 UTC. https://wiki.koha-community.org/wiki/Development_IRC_meeting_11_January_2017 In 2 days! Hope to see your there! Cheers, Jonathan [1] Template Toolkit syntax for notices - https://lists.katipo.co.nz/pipermail/koha/2016-December/046773.html [2] Hea Privacy policy - http://git.koha-community.org/gitweb/?p=hea.git;a=blob;f=Privacy_Policy.md;… [3] Benchmark for 16.11 - https://wiki.koha-community.org/wiki/Benchmark_for_16.11 [4] koha-misc4dev - http://lists.koha-community.org/pipermail/koha-devel/2016-November/043277.h…

2 1

DBIC > Swagger object definition
by Tomas Cohen Arazi 09 Jan '17

09 Jan '17

In the process of writing a script for generating swagger object definitions our of DBIC schemas (for sort-of scaffolding them making easier to add REST endpoints) I resumed some talks we had at Marseille, and also picked some previous work from Lari on automating the Koha::Object <-> Swagger translation. One thing that would be handy for this process, is to add the column descriptions to the schema files. This can be accomplished like this example (for Koha::Schema::Result::BorrowerAttributeType): +__PACKAGE__->add_columns( + "+code" => { + koha_description => "Unique key used to identify the attribute type" + }, + "+description" => + { koha_description => "Description for the attribute type" }, + "+repeatable" => { + koha_description => + "Defines if a patron can have multiple values for the attribute type" + }, + "+unique_id" => { + koha_description => "Defines if the assinged value need to be unique" + }, + "+opac_display" => { + koha_description => + "Defines if the attribute is visible to patrons on their account in the OPAC or not" + }, + "+opac_editable" => { + koha_description => + "Defines if the attribute is editable by patrons on their account in the OPAC or not" + }, + "+staff_searchable" => { + koha_description => + "Defines if the attribute is searchable via the patron search in the staff client" + }, + "+authorised_value_category" => { + koha_description => + "Foreign key from authorised_values that links this attribute to an authorized value category" + }, + "+display_checkout" => { + koha_description => + "Defines if the attribute is displayed in checkout screens" + }, + "+category_code" => { + koha_description => + "Defines a constraint on a patron category for the attribute type" + }, + "+class" => + { koha_description => "Defines a class for grouping attributes" } +); This way we can have really simple access to those descriptions we already have in kohastructure.sql: my $columns_info = Koha::Database->new->schema->resultset('BorrowerAttributeType') ->result_source->columns_info; foreach $key ( keys %{ $columns_info } ) { print "Column: $key | Description: " . $columns_info->{$key}->{koha_description}; } This could be an easy initial task for academy bugs. Opinions? We will need this at some point if we would change our workflow and have DB structure handled by DBIC. Anyway, I'll send a pull request to Jonathan so he adds this handy (and perfectible) script to his koha-misc4dev repository. This will make it available on kohadevbox right out-of-the-box. I'll then try to document it on Kyle's Koha Developer Handbook, which we all should add our bits of knowledge! Looking forward to your feedback! -- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F

3 3

KohaDevBox question...
by Mark Tompsett 06 Jan '17

06 Jan '17

Greetings, I was running a ‘prove t’ on the kohadevbox which I just vagrant up jessie’d from scratch the other night. I encountered a message about an uninitialized variable which led me to bug 13029. This added a configuration item to the koha-conf.xml file. Will this auto-correct with a vagrant destroy and vagrant up in the near future (before 17.05’s release)? I can add the item manually myself, but I’d hate to have to remember this the next time I might destroy and up. GPML, Mark Tompsett

4 6

SQL Reports
by SUZUKI Arthur 06 Jan '17

06 Jan '17

Hello Devs, Happy new year! My problem today is the following : I'm writing a Koha plugin to display recommendations on the OPAC: http://github.com/liliputech/koharecommenderengine The way I'm doing it involve modifying the web server configuration, which is *not so convenient*. I wanted to reformat part of my code to place the "SQL Select" part of my plugin in a public report to be able to access it with the following url : http://[koha-url]/cgi-bin/koha/svc/report?id=[reportId]&sqlparam=[biblionum… The problem is the first method gives good performance results while the second one is so damn slow. The "guidedreport.sql" is 100 times slower than "rawsql". Any advice? I used the tutorial here : https://wiki.koha-community.org/wiki/SQL_Reports_Library#Runtime_Variables Many thanks in advance. PS : Hi Baptiste, much welcomes to you! -- Arthur SUZUKI Service informatique des bibliothèques BIBLIOTHÈQUES UNIVERSITAIRES Université Jean Moulin Lyon 3 6 Cours Albert Thomas - B.P. 8242 – 69355 Lyon Cedex 08 ligne directe : +33 (0)4 78 78 79 16 | http://bu.univ-lyon3.fr L'Université Jean Moulin est membre fondateur de l'Université de Lyon

1 0

New intern arriving soon
by Paul Poulain 06 Jan '17

06 Jan '17

Hi all, Happy new year ! In less than 4 weeks (feb 1st), BibLibre will welcome a new intern, Baptiste Wojtkowski (French, as his name don't show ;-) ) that will work full time on Koha for the next 6 month. We plan to dedicate him on bugzilla, then the Mana project and some Elastic Search stuff. I'm sure you'll welcome him. -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries

1 0

Dashboard headings...
by Mark Tompsett 03 Jan '17

03 Jan '17

Greetings, http://dashboard.koha-community.org/ The month and year are wrong, but totals correct. [Smile] Who is able to correct those? GPML, Mark “#6 is out of the gate early” Tompsett

2 1

Benchmarks for 16.11
by Jonathan Druart 02 Jan '17

02 Jan '17

Hi devs, I have done some benchmarks for versions of Koha from 3.14 to the latest 16.11 You can find the results on the wiki: https://wiki.koha-community.org/wiki/Benchmark_for_16.11 To be able to go back in time, I had to modify the koha-misc4dev scripts. I am now able to get a Koha installations fully testable (items, reindexation, psgi file, etc.) with any of these versions in a few minutes, which is pretty awesome and will be very useful for debugging (and git bisecting). Note that not everything is clean at the moment and will still need some works (path in psgi file for instance). All of you should be able to replay the full benchmark script on your kohadevbox, so please do it. That way we will confirm (or not) these numbers. If you want to compare 3.8, feel free to adapt the different scripts (I can help for that) and post the results. Cheers, Jonathan

3 2

Koha Community Newsletter: December 2016
by kohanews 30 Dec '16

30 Dec '16

Fellow Koha users: The Koha Community Newsletter for December 2016 is here: https://koha-community.org/koha-community-newsletter-december-2016/ Many thanks to the folks who submitted articles and news to this month's newsletter. Please feel free to email me with any corrections or suggestions. Thanks! -- Chad Roseburg Editor, Koha Community Newsletter

1 0

Re: [Koha-devel] Koha Maps
by Marshall Breeding 28 Dec '16

28 Dec '16

Here is the version of Prosentient Systems Koha clients via Library Technology Guides: https://librarytechnology.org/libraries/map.pl?ILS=Koha%20--%20Prosentient%… List version: https://librarytechnology.org/libraries/search.pl?ILS=Koha%20--%20Prosentie… -marshall Marshall Breeding marshall.breeding(a)librarytechnology.org www.librarytechnology.org/ twitter.com/mbreeding http://www.linkedin.com/in/breeding http://scholar.google.com/citations?user=NnvfJ5cAAAAJ -----Original Message----- From: Edmund Balnaves [mailto:ebalnaves@prosentient.com.au] Sent: Wednesday, December 21, 2016 5:46 PM To: 'Chris Cormack'; Marshall Breeding Cc: 'koha'; 'Koha-devel' Subject: RE: [Koha-devel] Koha Maps Hi Marshall, Chris We already have a map of our libraries - http://www.prosentient.com.au/index.php/koha An API where we could push these details in bulk through to you would be great - we could send through the details of the library geocode details. Regards Edmund Edmund Balnaves, PhD Hosted Services Prosentient Systems P/L ABN 31 078 409 168 72/330 Wattle St, Ultimo NSW 2007 tel: 02 92120899 fax: 02 92120885 mobile: 0414737560 ejb(a)prosentient.com.au -----Original Message----- From: koha-devel-bounces(a)lists.koha-community.org [mailto:koha-devel-bounces@lists.koha-community.org] On Behalf Of Chris Cormack Sent: Wednesday, 21 December 2016 7:39 AM To: Marshall Breeding <marshall.breeding(a)librarytechnology.org> Cc: koha <koha(a)lists.katipo.co.nz>; Koha-devel <koha-devel(a)lists.koha-community.org> Subject: Re: [Koha-devel] Koha Maps * Marshall Breeding (marshall.breeding(a)librarytechnology.org) wrote: > I have been following the discussion about how the Koha community can > better market itself, including using a map display to emphasize its > global impact. > > > > Naturally, I would be happy to have the map generated from Library > Technology Guides to be used. Doing so would help me ensure that my > registry of libraries using Koha is more complete since libraries might > be more motivated to be included. Regardless of whether the Koha > community decides to rely more on my mapping tool, I will continue to try > to obtain data on the many libraries using Koha that are not yet > registered on my site or any other database. I continue to think that > Koha is most likely the most implemented ILS, but I do not yet have the > data to validate that assertion. > > > > The purity of working only with open source software and open access data > seems to me like an impossible goal. Richard Stallman, who I heard speak > last year, takes this concept to its logical conclusion, and ends up with > quite a limited realm of software or data which meet his tests for purity. > Is the Koha community comfortable using the Google Map API, for example, > since it is based on a closed and proprietary information infrastructure > and underlying software components that may or may not be open source? Or > does it plan to invent its own global mapping ecosystem? > That's what Open Street Maps is. Are you sure you want to get into a discussion about the ethics of open vs closed/proprietary on this mailing list? > > > I have looked at the Hea tool and I have a hard time imagining it gaining > the functionality of a global mapping visual and becoming well populated > by the mechanisms provided. Since it is generated mechanically through > each instance of Koha, it will be difficult to translate this data to > represent the libraries that are actually using Koha in production. Many > of the entries shown now (http://hea.koha-community.org/libraries) seem to > be duplicates or test implementations. Its single entry for the NExpress > Shared Catalog is represented by 53 libraries on my maps. I don’t see hea > as having the structure has the ability to represent the branches > associated with a library system or consortia and many other aspects of > tracking the libraries which use any given automation system. I think > that many, if not the majority, of Koha implementations globally are based > on older or forked versions of Koha, making it difficult or impossible for > them to automatically contribute their data to Hea. > > > > I also wonder why the Koha development community would divert resources > into re-creating such a tool from other efforts to develop and promote > Koha. Having maintained a registry of libraries for almost two decades, > my experience tells me that it is much more difficult to create and > maintain a well-organized list than others might imagine. > > > > I have also just re-written the map tool on Library Technology Guides to > generate the display more quickly when there are a very large number of > libraries. Although it depends on how quickly the Google API responds, it > now builds the maps in a few seconds, compared to almost a minute > previously. I have also added some basic search selection tools at the > bottom of the page: > > https://librarytechnology.org/libraries/map.pl?ILS=Koha > > > > I’ll be interested to hear further discussion on the topic. > The main thing I would be interested in hearing is that you have licensed the data in the tool under an open license. And then we could use it without issue. Chris > > > Marshall Breeding > > marshall.breeding(a)librarytechnology.org > > www.librarytechnology.org/ > > twitter.com/mbreeding > > http://www.linkedin.com/in/breeding > > http://scholar.google.com/citations?user=NnvfJ5cAAAAJ > > >_______________________________________________ >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/ -- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand

1 0