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

Koha Community Newsletter: February 2020
by kohanews 27 Feb '20

27 Feb '20

The Koha Community Newsletter for February 2020 is here: https://koha-community.org/koha-community-newsletter-february-2020/ 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. -- Chad Roseburg Editor, Koha Community Newsletter

1 0

Give a try to RabbitMQ (background jobs rewrite) - POC!
by Jonathan Druart 26 Feb '20

26 Feb '20

Hi devs, I have submited a proof of concept (POC) on bug 22417 (Delegate background jobs execution). The idea would be to isolate our background jobs code (the one in the .pl) into module then use RabbitMQ to process them. More stuffs on the bug! https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417 Cheers, Jonathan

4 4

Koha 19.11.03 Release
by Joy Nelson 26 Feb '20

26 Feb '20

Greetings! The Koha community is proud to announce the release of Koha 19.11.03. This is a maintenance release containing 7 enhancements and 78 bugfixes The full release notes are available at https://koha-community.org/koha-19-11-03-release/ Debian packages will be updated within a few days Joy Nelson President, Koha Division ByWater Solutions <http://bywatersolutions.com> Support and Consulting for Open Source Software Phone/Fax (888)900-8944 What is Koha? <http://bywatersolutions.com/what-is-koha/>

2 2

Minimal docker images for Koha
by Julian Maurice 25 Feb '20

25 Feb '20

Hi all, I've been playing with docker lately, and I tried to build a minimal docker image for Koha. Here are the results. My goals were: * Install only required "things" to get Koha up and running, and nothing else (no testing or dev tools), * No external dependencies except CPAN * Follow Docker best practices as much as possible The resulting images are here: https://hub.docker.com/repository/docker/julianmaurice/koha and the Dockerfiles are here: https://github.com/jajm/koha-docker A few things worth mentioning: * I tried to build the smallest image possible by using alpine or perl slim images at first but it was not that great, because the perl version shipped with those images is missing some libs, which cause MARC::Charset to build a database of several hundreds MBs (which is only 5MBs with a standard perl version). So I chose a more standard image (debian:buster) as base. * Koha doesn't work well when running with a perl version different than the system perl installed in /usr/bin/perl. For example, the updatedatabase doesn't work when called from the web installer. This is because Perl scripts are called directly as executable files, and shebangs contain '/usr/bin/perl'. Same problem from misc/translator/translate which calls tmpl_process3.pl. * I tried to make the Koha installation as self-contained as possible. Almost everything is installed as a non-root user in /home/koha, including Perl dependencies. * It doesn't need a reverse proxy such as apache or nginx. The necessary URL rewriting is handled in PSGI file. The container expose two ports, one for intranet, the other one for OPAC. * Each Perl dependency is installed in its latest version, so expect things to break. I can only confirm that the webinstaller, basic cataloguing and search/indexation work. I did not test anything else. * There are docker-compose.yml files in the github repository to get Koha running quickly with mariadb, memcached and elasticsearch. * Zebra is not installed * Images weigh ~1.15GB uncompressed (koha sources included) If you made it this far, thanks for reading :) And if you want to use these docker images, you should start by reading https://github.com/jajm/koha-docker/blob/master/README.md -- Julian Maurice BibLibre

4 22

Problems when using multiple CGI objects in a CGI script
by dcook＠prosentient.com.au 25 Feb '20

25 Feb '20

Hi all, Just thought I'd share an issue I encountered today. You can see the details at https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24719, but it boils down to how using multiple CGI objects (using the CGI module) can lead to unexpected behaviour. In this case, file uploads were failing in /cgi-bin/koha/tools/stage-marc-import.pl because the CGI object created in a different function in the included C4::Auth was setting and clearing global variables behind the scenes just by calling CGI->new(). Just sharing this I suppose so that we're careful with our use of the CGI module? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

1 0

Looking for QA availability to pass 11299
by Philippe Blouin 19 Feb '20

19 Feb '20

Good morning/dinner/evening dear Koha developpers, We're looking for a QA to pass 11299. Jonathan and Cate have removed themselves, and the patch is big and has been rebased already too many times in its 7 years history. This has been by far the costliest development for our sponsor, CCSR/Collecto, that has already given much to the community over 10 years. Bouzid has played by the rules, and has put in every single damn request presented to him by QA/Testers. Including redoing it from ground up lately to match the ever changing coding requirements and architecture. So, anyone has some time? Regards, -- Philippe Blouin, Directeur de la technologie Tél. : (833) 465-4276, poste 230 philippe.blouin(a)inLibro.com <mailto:philippe.blouin@inLibro.com> inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com>

1 0

About SMS integration with KOHA 19.11 from Bangladesh.
by Sarowar Saklayan 18 Feb '20

18 Feb '20

Dear Sir, We are here trying to integrate SMS API with KOHA but failed. If there any suggestions for us or any alternative option. Please let us know. -- Regards Md. Sarowar Saklayan CRO & System Analyst Dhaka | Rajshahi | Chattogram | Kolkata | Pennsylvania Cell phone:+8801913800800, +8801729018635 Fax: +880 721 774373, E-mail: saklayan18(a)gmail.com Web: DesktopIT.com.bd <http://desktopit.com.bd/> | WebRajshahi.com | KhazaCorporation.com IM - "01729018635" (Skype & whatsApp)

2 1

Coding guidelines
by Marcel de Rooy 17 Feb '20

17 Feb '20

Referring to the dev meeting and bug 22407, I propose the following rewording: PERL15 Using Koha::Object[s] PERL15(a) Code added to the Koha:: namespace should be object-oriented unless there is a very good reason to do otherwise. In that case the reason should be documented clearly. PERL15(b) Code in Koha::Object[s] should normally not refer back to C4. Obviously, this cannot be enforced harshly until the refactoring has been completed. PERL15(c) Use DBIC relations to (pre)fetch a related Koha object rather than searching it explicitly. (See bug 22407) PERL28 Other object oriented code guidelines (in addition to PERL15) I think we need to move the Accessor and idiom for -> new rules from PERL15 to another rule. I opened rule 28 for that depending on discussing the following: Class::Accessor is a great way to provide access to member variables. => My suggestion would be to remove this rule. It is true but we do not say that it is the only way to do it. (We are not even using Class::Accessor in Koha objects.) Or just say PERL28(a) To provide access to member variables, there are several ways including but not limited to using Class::Accessor. A useful idiom for the ->new() routine in object-oriented classes that do not need to process the arguments passed in as a hashref but merely need to save them for future processing => This suggestion is fine. It says use a parameter hash for sub new. We normally do that. Reworded: PERL 28(b) Use a hashref as second parameter in sub new when passing arguments. Any feedback? Marcel Museumstraat 1 Postbus 74888 1070 DN Amsterdam Rijksmuseum.nl Nu te zien: Operatie Nachtwacht Verwacht: Caravaggio-Bernini. Barok in Rome Dankzij Waller 2010-2020 T/m 18 jaar gratis Please think before you print

3 2

Alternative views for search results and detail pages?
by dcook＠prosentient.com.au 17 Feb '20

17 Feb '20

Hi all, What do people think about replacing the XSLTs with Template Toolkit templates for search results and detail pages? Considering that the OPAC Detail XSLT is 2000 lines and the Search Result XSLT is 1500 lines (and that doesn't include the utility XSLT) maybe that's a bit ambitious. The Intranet Search results are 1000 lines and Intranet Detail is 1600 lines. I'm just trying to think of how we could do views for metadata that aren't MARC-centric. Actually, after reviewing the XSLTs, I suppose there's no reason we couldn't expand the XSLTs to include more metadata schema options. We could actually provide any XML and then just do an XSLT template to render it. (After looking at Koha::SearchEngine::Elasticsearch::Search, it looks like we're storing whole MARCXML records in Elasticsearch, and that's what we're fetching from Elasticsearch for Koha to render for views?) Looking at biblio-zebra-indexdefs.xsl and really we could hand that arbitrary XML to index as well. and then worry about C4::Search::getRecords() stuffing the Zebra raw record into the result data structure and C4::Search::searchResults assuming it's a MARCXML record. It's too bad MARC::Record::XML doesn't check for a XML::LibXML object before trying to parse, or we could parse the XML and then just hand the relevant XML to MARC::Record. I mean we could still do that but it would involve double-parsing, which would be a performance hit. Although I imagine Galen wouldn't necessarily be opposed to accepting an update. I mean it would basically be adding the same functionality to Zebra that we have with Elasticsearch, no? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

1 0

Adding peer review status to article records
by dcook＠prosentient.com.au 17 Feb '20

17 Feb '20

Hi all, I have a library interested in adding peer review status to their article records in Koha. The short-term solution is to use a local MARC field and do a code customization for it. However, peer review status is the kind of thing that the library industry will probably see more and more of going forward into the digital future. It seems to me that a long-term solution would be wiser. Sure enough, ExLibris Alma and OCLC WorldCat Discovery already have this functionality: https://help.oclc.org/Discovery_and_Reference/WorldCat_Discovery/Search_resu lts/How_item_bibliographic_data_is_displayed https://knowledge.exlibrisgroup.com/Alma/Release_Notes/010_2018/11_February_ 2018/Alma_February_2018_Release_Notes/02Resource_Management_-_February_2018_ Enhancements#Peer_Review_and_Open_Access OCLC uses a non-MARC method, whereas ExLibris rely on a magic string in a 500 field for peer review status. That being said, I'm not sure what the best long-term solution would be to add this metadata to a bibliographic record. What do you all think? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595

1 1