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

Koha Community Newsletter: June 2022
by Koha Newsletter 30 Jun '22

30 Jun '22

The Koha Community Newsletter for June 2022 is here: https://koha-community.org/koha-community-newsletter-june-2022/ Many thanks to everyone who submitted articles and news to this newsletter! Please feel free to email me with any corrections or suggestions. -- Michael Kuhn Editor, Koha Community Newsletter

1 0

Multilingual label printing in Koha (praise be to Bywater!)
by dcook＠prosentient.com.au 30 Jun '22

30 Jun '22

Hi all, I had a problem where I couldn't print Chinese and English on barcode labels using Koha's built-in Label Creator, since it uses individual font files and I couldn't find a free and open individual font that supports both European and Chinese scripts. Fortunately, I recalled that Kyle @ ByWater Solutions created this plugin: https://github.com/bywatersolutions/koha-plugin-label-maker. It uses HTML and CSS to generate labels in the browser, and the browser is already capable of using multiple different fonts to support multiple different scripts. The plugin did a great job of rendering barcodes with both Chinese and English written on them! Thanks, Bywater Solutions, for saving the day! -- Nerdy thoughts: If I look at the "Computed" styles in the F12 tools in Chrome on Windows 10, it says the English is rendered using the "Times New Roman" font, and it says that the Chinese is rendered using the "Microsoft YaHei" font. If I do the same thing in Microsoft Word, the English is in "Calibri" and the Chinese is in "DengXian". If you read https://fonts.google.com/noto/use#how-are-noto-fonts-organized it says "If you have text in multiple languages that use different scripts, either the app or the person who typesets the text needs to switch between the different fonts accordingly." I'm not an expert on fonts, so I'm not sure what would be involved with getting Koha's PDF libraries to use different fonts for different scripts. I don't know how Chrome and Word detect that they need to use a different font. I don't know if it's a map of Unicode codepoints to existing font mappings, or if it iterates through a list of fallbacks, or what. I probably won't go too far down this rabbit hole, since the ByWater Koha Plugin solved my immediate use case, but it's an interesting topic, and this is a major limitation with Koha's Label Creator, so we might want to think about a change in the future... 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 1

Koha Plugin for LibApps search source (LibraryGuides)
by dcook＠prosentient.com.au 30 Jun '22

30 Jun '22

Hi all, Has anyone done a Koha plugin for a LibApps search source? That is, adding Koha as a custom search source for LibGuides? https://ask.springshare.com/libapps/faq/700 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

Gitlab policy changes
by Tomas Cohen Arazi 29 Jun '22

29 Jun '22

Hi, we need to take a look at the upcoming changes and make a decision on enrolling as an Open Source project: https://about.gitlab.com/blog/2022/02/04/ultimate-perks-for-open-source-pro… Please read carefully so we can make a decision eventually. -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

5 17

Elasticsearch: Minor fix ?
by Marcel de Rooy 27 Jun '22

27 Jun '22

Hi all, Suddenly my D10 dev box does not install anymore. Reason: We now require Search::Elasticsearch to be 6.80. And under D10 I have 6.00. This is called a minor fix on bug 25669. Which is currently not my perspective. Not talking about further implications yet.. Can we fix this fix ? Marcel

3 5

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

26 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 23 Jun '22

23 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 22 Jun '22

22 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