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

Embed see-from headings (authorities) into bibliographic records at OAI repository level
by Julien Sicot 27 Jun '22

27 Jun '22

Hi all, An enhancement idea : It could be interesting to enrich the bibliographic records exposed in OAI with see-from headings, this would allow users who use koha with a discovery tool to be able to manage, normalize and index some authorities data ? This is something that could be done directly in C4::Biblio::GetMarcBiblio following the same method used for embedding items. We could use an optional parameter like embed_items (embed_seefromheading) and a function similar to C4::Biblio::EmbedItemsInMarcBiblio by reusing what was made for zebra with EmbedSeeFromHeadings (bug #7417 <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7417>). What do you think about this? Thanks for feedback, Best -- Julien Sicot Systems Librarian Université Rennes 2 02 22 51 44 41

4 4

Distributing Koha Plugins efficiently
by dcook＠prosentient.com.au 24 Jun '22

24 Jun '22

Hi all, If I were to unpack 5 different Koha plugins to /opt/koha-plugins and then added "<pluginsdir>/opt/koha-plugins</pluginsdir>" to the koha-conf.xml for all my Koha instances, I should be able to just run "koha-foreach perl /usr/share/koha/bin/devel/install_plugins.pl" to install/upgrade all those plugins within Koha, right? Once "bug 21366 - add plack reload" is done, we could then do "koha-plack --reload $(koha-list --enabled --plack)" to gracefully reload all those Koha instances to have the freshest version of the plugin. -- If that's true, a person could bundle Koha plugins however they like, right? They could put them into koha-common, they could do their own koha-plugins package (included or separate to their Koha codebase), they could just use a Git repo, or whatever makes sense for distributing. The advantage of Debian packages would be adding that "koha-foreach" and "koha-plack" into package install hooks. I suppose a "install plugins" hook in "koha-create" would be wise too so that a new instance could auto install any centralized plugins. Does that all make sense? Am I missing anything? I'd really like to use plugins in lieu of Koha customizations but I find distributing the code across a large number of Koha instances to be prohibitive. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

2 3

SIP server only supporting 1 simultaneous connection (Bug 31033)
by dcook＠prosentient.com.au 24 Jun '22

24 Jun '22

Hi all, I was going through my emails when I noticed Bug 31033, which indicates that Koha's SIP server only supports 1 simultaneous connection of the box. I did some testing and confirmed Mark's findings. Honestly, I'd never thought about it. While we do run some SIP servers, it's never come up as an issue. Have folk noticed the same thing and do they just resolve the problem by updating their SIPconfig.xml files? I've added a patch to Bug 31033 to make Koha's default configuration more explicit, but curious what people's thoughts are. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

1 0

Pretty Plugin URLs
by dcook＠prosentient.com.au 23 Jun '22

23 Jun '22

Hi all, At the moment, in the Staff Interface, we have plugin URLs like this: http://localhost:8081/cgi-bin/koha/plugins/run.pl?class=Koha%3A%3APlugin%3A% 3ACom%3A%3AByWaterSolutions%3A%3ACoverFlow <http://localhost:8081/cgi-bin/koha/plugins/run.pl?class=Koha%3A%3APlugin%3A %3ACom%3A%3AByWaterSolutions%3A%3ACoverFlow&method=configure> &method=configure What if we had something prettier like the following? http://localhost:8081/cgi-bin/koha/plugin/coverflow/configure or http://localhost:8081/cgi-bin/koha/plugin/coverflow?method=configure I was thinking it would leverage a plugin_key of "__NAME__" in the "plugin_data" table. I suppose it increases the risk of name collisions, but to be honest those collisions can happen in Wordpress (as I recently learned) and it's fine overall. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

1 0

Effective circulation rule preview/tester
by dcook＠prosentient.com.au 22 Jun '22

22 Jun '22

Hi all, How good would it be if there were a preview/tester for effective circulation rules in the Admin module? I'm sure I'm not the only one who struggles to figure out what circulation rule is being applied in any given scenario at times. I imagine a lot of librarians could make use of it especially. Probably not something I would develop, but thought it was an interesting idea. David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

4 3

Replace git-filter-branch with git-filter-repo
by Jonathan Druart 16 Jun '22

16 Jun '22

Hi devs, [I sent this on Aug 26th 2021 but it never reached the list!] You may have seen the following warning when signing off on patches using the git alias """ WARNING: git-filter-branch has a glut of gotchas generating mangled history rewrites. Hit Ctrl-C before proceeding to abort, then use an alternative filtering tool such as 'git filter-repo' (https://github.com/newren/git-filter-repo/) instead. See the filter-branch manual page for more details; to squelch this warning, set FILTER_BRANCH_SQUELCH_WARNING=1. Proceeding with filter-branch... """ And yes, it's very slow, `time git so 1` takes around 10 sec for me. You can switch to git-filter-repo (https://github.com/newren/git-filter-repo) First, install it (`pip3 install git-filter-repo` should do it, otherwise read their install doc https://github.com/newren/git-filter-repo/blob/main/INSTALL.md) Then adjust the git alias (~/.gitconfig): so = "!f() { c=`expr $1 - 1`; git filter-repo --message-callback 'return message + b\"\\nSigned-off-by: Full Name <email>\"' --refs HEAD~$c^..; }; f" I am using 'so' but you may use something else as it's not what is on the wiki. "Completely finished after 0.20 seconds." Cheers, Jonathan

2 1

Call for news - Newsletter June 2022
by Koha Newsletter 13 Jun '22

13 Jun '22

Hi I'm collecting news for the June 2022 Koha Community Newsletter. Please send anything noteworthy to: kohanews (at) gmail (dot) com News criteria: * News items can be of any length. * Images are fine. * Anything and everything Koha. * Submit by the 26th of the month. Text format criteria: * Just structured plain text, or * HTML text to include tables or similar For events: * Consider adding your event to the Koha Community calendar at https://koha-community.org/calendar/ Thank you! Michael Kuhn Editor, Koha Community Newsletter

1 0

koha 22:05 elasticsearch
by Stowasser Rainer 13 Jun '22

13 Jun '22

Hy with the new version I thought I would give elasticsearch a try (zebra works ;-) new server Debian 5.10.106-1 10.5.15-MariaDB Apache/2.4.53 but koha-elasticsearch Preparing to unpack .../libmarc-xml-perl_1.0.5-1_all.deb ... Unpacking libmarc-xml-perl (1.0.5-1) ... dpkg: error processing archive /var/cache/apt/archives/libmarc-xml-perl_1.0.5-1_ all.deb (--unpack): trying to overwrite '/usr/bin/marc2xml', which is also in package libmarc-file- xml-perl 1.0.5-1~koha+1 Errors were encountered while processing: /var/cache/apt/archives/libmarc-xml-perl_1.0.5-1_all.deb apt --fix-broken install The following additional packages will be installed: libmarc-xml-perl dpkg: error processing archive /var/cache/apt/archives/libmarc-xml-perl_1.0.5-1_ all.deb (--unpack): trying to overwrite '/usr/bin/marc2xml', which is also in package libmarc-file- xml-perl 1.0.5-1~koha+1 Did anyone else encounter this problem ? Kind regards Hofrat Mag. Rainer Stowasser Head of Library and Archives ZAMG

4 8

opac-overdrive-search.tt translation bug
by Alex Buckley 13 Jun '22

13 Jun '22

Hi there, I see this line https://github.com/Koha-Community/Koha/blob/beb663836b45a77f45195774133cc9b… does not get translated correctly. The 0 in the ELSE is lost in the translated versions of opac-overdrive-search.tt, for example below: /var OD_password_required = [% IF Koha.Preference('OverDrivePasswordRequired') %]1[% ELSE %][% END %];/ This in turn throws a JavaScript error if a library does not have the /OverDrivePasswordRequired/ syspref enabled./ / I checked the en-NZ-opac-bootstrap.po <https://translate.koha-community.org/export/22.05/en_NZ/en-NZ-opac-bootstra…> and it has no translation for that JS line. Could someone please give me some pointers on how we could stop the 0 being lost? Any help gratefully received! Many thanks, Alex -- Alex Buckley (he/him) Koha Developer | Implementation Lead Catalyst IT - Expert Open Source Solutions www.catalyst.net.nz <http://www.catalyst.net.nz> CONFIDENTIALITY NOTICE: This email is intended for the named recipients only. It may contain privileged, confidential or copyright information. If you are not the named recipient, any use, reliance upon, disclosure or copying of this email or its attachments is unauthorised. If you have received this email in error, please reply via email or call +64 4 499 2267.

1 0

Datepicker: native vs jQuery vs Flatpickr
by dcook＠prosentient.com.au 10 Jun '22

10 Jun '22

Hi all, I found myself using the browser native datepicker[1] for a project, and I was wondering if that's something we would consider using, especially since Microsoft has EOLed Internet Explorer. I think we use a mix of jQuery date picker and Flatpickr, but I was curious what people though about using the native one. I used it on my project since it was simple and didn't have any added dependencies. While I haven't tried it, it looks like there is a date time option as well[2]. [1] https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/date [2] https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/datetime-loc al David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595

2 2