- Koha - lists.katipo.co.nz

Arabic speaker(s) needed to fix a translation issue
by Victor Grousset/tuxayo 20 Jul '21

20 Jul '21

Hello, If someone can reach a speaker, this should be simple. If something about the translation process is unclear, ask in the list or directly, I'll be glad to help. So, as part of the work to release this month's minor Koha versions, a few string translations have been found to generate errors. These errors on even small pieces of text can lead to major translation breakage not just on the invalid string. But no worries, they are manually marked for exclusion each month when releasing but the best thing would be to have the string correct. Here they are: https://translate.koha-community.org/ar/20.05/translate/ar-Arab-messages.po… https://translate.koha-community.org/ar/20.05/translate/ar-Arab-messages.po… https://translate.koha-community.org/ar/20.11/translate/ar-Arab-messages.po… https://translate.koha-community.org/ar/21.05/translate/ar-Arab-messages.po… Cheers, -- Victor Grousset/tuxayo

1 0

Time to translate: string freeze to prepare Koha 20.05.14 has begun
by Victor Grousset/tuxayo 16 Jul '21

16 Jul '21

Hi, saluton, hola, bonjour, String freeze is into effect as of now for the 20.05.x maintenance branch. The minor release is scheduled for around the 23th. This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Reminder: if you add or change a translation in version 20.05, then you must also copy it to 20.11 and 21.05. Otherwise your work will be lost for future versions. (We've had a recent significant case of that!) Happy translating, -- Victor Grousset/tuxayo

1 0

Re: [Koha] Add separator from fields 245a and 245c
by Charles Kelley 16 Jul '21

16 Jul '21

Hello, there! In our latest exchange, on 15 July 2021 at 09:01 [JST], I received the following: Many thanks for your reply. > > In our case the solution was a simple edition in .xls file. > > From: > > <span > class="title_resp_stmt"><xsl:apply-templates/> <xsl:text> </xsl:text> > </span> > > To: > > <span class="title_resp_stmt"> | > <xsl:apply-templates/> <xsl:text> </xsl:text> </span> > > Cheers. > > Javier > We're glad it worked it for you. -- 気を付けて。 /ki wo tukete/ = Take care. -- Charles. Charles Kelley, MLS PSC 704 Box 1029 APO AP 96338 Charles Kelley Tsukimino 1-Chome 5-2 Tsukimino Gaadenia #210 Yamato-shi, Kanagawa-ken 〒242-0002 JAPAN +1-301-741-7122 [US cell] +81-80-4356-2178 [JPN cell] mnogojazyk(a)aol.com [h] cmkelleymls(a)gmail.com [p] linkedin.com/in/cmkelleymls <http://www.linkedin.com/in/cmkelleymls> Meeting Your Information Needs. Virtually.

1 0

fresh installation issue
by Hugo Páscoa 15 Jul '21

15 Jul '21

Hi koha community I'm trying a koha fresh install with a remote sql server (debian10 + mariadb. I already have a pre-determined DB/User and Password. How can I use it to request-db and populate-db? Thanks for your advice Best regards Hugo Páscoa

1 0

Re: [Koha] Title search works, but Library catalog search fails in OPAC
by Bales (US), Tasha R 14 Jul '21

14 Jul '21

Thanks Katrin, We've determined that toggling OpacSuppression from "Hide" to "Don't Hide" "fixes" our inability to search the OPAC for phrases containing punctuation when using the "Library catalog" search option. However, the bibliographic records that are hidden are *not* coded to be suppressed and I don't believe OpacSuppression should have any bearing on their display.* Also, thanks for the info about the bug. I can reproduce that error, but so far, only when my search contains a forward slash. I'll keep an eye on it. I will keep testing. Being new to Koha, maybe I am misunderstanding or not seeing something. Thanks again for the help so far! *Example 942 field: 942 _ _ ‡n0 I've verified that 942 is populated in every record in the system, with either 0 or 1, using the "SUPPRESS" Authorized Value, which came out-of-the-box on our system. Incidentally, I see these errors in plack-opac-error.log: [2021/07/13 09:23:04] [WARN] Use of uninitialized value $f in pattern match (m//) at /usr/share/koha/lib/Koha/SearchEngine/Elasticsearch/QueryBuilder.pm line 725. [2021/07/13 09:23:04] [WARN] Use of uninitialized value $f in exists at /usr/share/koha/lib/Koha/SearchEngine/Elasticsearch/QueryBuilder.pm line 729. Tasha Bales Business Support Team | Information Services -----Original Message----- From: Koha [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of Katrin Fischer Sent: Sunday, June 27, 2021 1:38 AM To: koha(a)lists.katipo.co.nz Subject: [EXTERNAL] Re: [Koha] Title search works, but Library catalog search fails in OPAC EXT email: be mindful of links/attachments. Hi Tasha, there is currently a bug about some punctuation leading to no results in Elasticsearch that might relate to your problem: *Bug 28316* <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28316> - Fix ES crashes related to various punctuation characters Hope this helps, Katrin On 24.06.21 23:55, Bales (US), Tasha R wrote: > Follow-up to my problem searching the OPAC for phrases containing punctuation (i.e., Electroactive polymer (EAP) actuators). This Bywater Solutions<https://bywatersolutions.com/education/elastic-searching> article suggests that the problem is a feature of Elasticsearch. > > > > FYI, we are using Elasticsearch 6.1.1 on its own dedicated server, and I don’t believe we’ve installed the ICU Analysis plug-in (looks like it’s required for Zebra, but I can’t tell if it’s required for Elasticsearch), which could be a factor. I couldn’t replicate all aspects of my experience in a sandbox, although searches for phrases containing punctuation still failed in an OPAC “Library Catalog” sandbox search. I concluded that I needed to review our configuration. > > > > I’ve been reviewing the Koha Wiki and elastic.co documentation, and comparing to our index_config.yaml. > > By chance does anyone know how to interpret the syntax below? The documentation describes the parameters below, but I don’t see any usage of “-“ before options. Does the option “- punctuation“ mean “yes, remove punctuation”, or “no, don’t remove punctuation”, or does the phrase refer to some additional configuration file, or perhaps it’s commented out? > > > > analyzer_phrase: > > tokenizer: keyword > > filter: > > - icu_folding > > char_filter: > > - punctuation > > > > Thanks for your time and consideration, > > > > > > Tasha Bales > > Business Support Team | Information Services > > Enterprise Services | Enterprise Operations, Finance and > Sustainability > > > > > > -----Original Message----- > > From: Bales (US), Tasha R > > Sent: Tuesday, June 22, 2021 7:54 AM > > To: 'Jonathan Druart' <jonathan.druart(a)bugs.koha-community.org> > > Cc: Discussion Group Koha <koha(a)lists.katipo.co.nz> > > Subject: RE: [EXTERNAL] Re: [Koha] Title search works, but Library > catalog search fails in OPAC > > > > Jonathan, thank you! > > > > It does work without the parentheses. > > > > I would suspect an encoding problem, but for that the problem only manifests in the OPAC, and not the intranet. > > > > I came across this issue while testing after migrating from MariaDB to Percona MySQL. Your reply prompted me to check the encoding of the new database, and it's unfortunately Latin-1. Since these are parentheses and not diacritics, I’m not sure what my expectations should be, but changing to UTF-8 is a place to start. Httpd.conf does have UTF-8 set as the default. > > > > FWIW, my source records were encoded in MARC-8. I used MarcEdit to convert them to UTF-8, and it appears that Koha automatically converts anyway on import. When I loaded these records into Koha, I used bulkmarcimport.pl on the command line. > > > > I'll ask that the default character set of the database be changed, > and see if that helps. Thanks again. I'm embarrassed that I didn't > think to omit the parentheses, or rather was belligerently insisting > to myself that they should not have been a problem, > > > > > > Tasha Bales > > Business Support Team | Information Services Enterprise Services | > Enterprise Operations, Finance and Sustainability > > (480) 509-5415 > > https://is.web.boeing.com > > > > > > -----Original Message----- > > From: Jonathan Druart [mailto:jonathan.druart@bugs.koha-community.org] > > Sent: Tuesday, June 22, 2021 12:01 AM > > To: Bales (US), Tasha R <tasha.r.bales(a)boeing.com> > > Cc: Discussion Group Koha <koha(a)lists.katipo.co.nz> > > Subject: [EXTERNAL] Re: [Koha] Title search works, but Library catalog > search fails in OPAC > > Importance: High > > > > EXT email: be mindful of links/attachments. > > > > > > > > Hello Tasha, > > > > I've created 2 records with > > 245$a Electroactive polymer (EAP) actuators as artificial muscles and the following query returns the 2 results. > > /opac-search.pl?idx=&q=Electroactive%20polymer%20%28EAP%29%20actuators > &weight_search=1 > > > > Tried on master and 20.11.06. > > > > Maybe a silly idea: does it work without the parenthesis? > > > > Could you try and recreate it on a sandbox > > (https://wiki.koha-community.org/wiki/Sandboxes) and provide us a step by step plan to reproduce the problem? > > > > Regards, > > Jonathan > > > > Le mar. 22 juin 2021 à 00:46, Bales (US), Tasha R <tasha.r.bales(a)boeing.com> a écrit : > >> Good afternoon, >> I’m having trouble with Title vs. Library catalog keyword searching with several example titles. Searching the same phrase with either method yields different results. This problem occurs only in the OPAC. I hope to confirm whether the behavior I’m seeing is intended (i.e., the problem is me) or not. Thanks in advance. >> For example, given the ebook title, Electroactive polymer (EAP) >> actuators as artificial muscles, a Title keyword search in the OPAC is successful, but a plain, Library catalog (i.e., no index specified), keyword search fails. >> For reference, the title is recorded in the MARC record as: >> 245 00 - TITLE STATEMENT >> a Title Electroactive polymer (EAP) actuators as artificial muscles : >> Below I’ve copied in my search history as well as the tail of the search URL that shows the search parameters. >> · Library catalog keyword search with 0 results >> o 2021-06-21 02:34 PM  Electroactive polymer (EAP) actuators, suppress:false 0 >> o …opac-search.pl?idx=&q=Electroactive%20polymer%20%28EAP%29%20actuators&weight_search=1 >> · Title keyword search with 2 results >> o 2021-06-21 02:34 PM  Electroactive polymer (EAP) actuators, suppress:false 2 >> o …opac-search.pl?idx=ti&q=Electroactive+polymer+%28EAP%29+actuators&weight_search=1 >> As a test, I decided to enclose my Library catalog search terms in quotes, which yielded the desired results. However, I did not at all anticipate that quotes would be required to get hits: >> · Library catalog quoted keyword search with 2 results >> o 2021-06-21 02:46 PM  "Electroactive polymer (EAP) actuators", suppress:false 2 >> o … opac-search.pl?idx=&q=%22Electroactive+polymer+%28EAP%29+actuators%22&weight_search=1 >> On comparing the above URL query strings, it appears that the unquoted terms in the Library catalog keyword search aren’t “anded” together with a “+” the way other searches are, but I’m not sure what the implications are, if any. Also, the Koha manual indicates the following, which suggests to me that I ought to get hits on the unquoted string: >> When you have more than one word in the search box, Koha will still do a keyword search, but a bit differently. Each word will be searched on its own, then the Boolean connector ‘and’ will narrow your search to those items with all words contained in matching records. >> I understand and can predict pretty well the way our old ILS (Millennium, if context helps) will perform a keyword search, but I’m a little confused here. My expectation for this particular case is that all of the above methods would yield results. If there are any pointers to be had, I thank you if might point me to them so that I may be better poised to help users. >> I’m using Elasticsearch with Koha 20.11.06. I reindexed both authorities and biblios today, but that didn’t impact my experience. The records are not newly added. >> Thanks! >> Tasha Bales >> Business Support Team | Information Services Enterprise Services | >> Enterprise Operations, Finance and Sustainability >> _______________________________________________ >> Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz >> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > _______________________________________________ > > Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha _______________________________________________ Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

1 0

Re: [Koha] Add separator from fields 245a and 245c
by Charles Kelley 14 Jul '21

14 Jul '21

Hello, Javi et al! In our latest exchange, on 30 June 2021 at 9:01 [JST] I received the following from you: We have below XML: > > <datafield tag="245" ind1=" " ind2=" "> > <subfield code="a">Gestión empresarial. El caso de dieciocho > cooperativas</subfield> > <subfield code="b"></subfield> > <subfield code="c">Consultores Asociados (Coord.)</subfield> > </datafield> > > Which leads to below string both in admin and OPAC: > > Gestión empresarial. El caso de dieciocho cooperativas Consultores Asociados > (Coord.) > > Question: how to add a string (let's say " | ") between fiedls 245a and > 245c? > > Thanks. > > Javier > My library faced this problem when we migrated from one machine to another. It turned out that it was original records were missing the punctuation marks and they had to be instroduced. We exported the entire catalog from Koha in MARC format and fixed the problem -- or at least most of the problem -- with MarcEdit. MarcEdit has a tool called "Build New Field." It allows one to copy or replace fieldsin a group with a new version. After fixing the records, we imported them back into Koha. It worked like a charm for us. Mind you, it wasn't perfect: we had to be especially watchful of parallel titles in 245 $b since they are preceded by an equal sign. And we had to make sure every subfield was copied, and then empty subfields deleted. But overall it worked, and worked well; and it save a lot of staff matter, energy, time, and space. Terry Reese presents a few tutorials online about MarcEdit. That may be your best way if you want to avoid a painstaking top-to-bottom record-by-record correction in records. I don't know enough about XML to advise about that. Hope that helps. -- 気を付けて。 /ki wo tukete/ = Take care. -- Charles. Charles Kelley, MLS PSC 704 Box 1029 APO AP 96338 Charles Kelley Tsukimino 1-Chome 5-2 Tsukimino Gaadenia #210 Yamato-shi, Kanagawa-ken 〒242-0002 JAPAN +1-301-741-7122 [US cell] +81-80-4356-2178 [JPN cell] mnogojazyk(a)aol.com [h] cmkelleymls(a)gmail.com [p] linkedin.com/in/cmkelleymls <http://www.linkedin.com/in/cmkelleymls> Meeting Your Information Needs. Virtually.

2 1

koha-US General Meeting reminder: Wednesday, July 14th, 2021
by Jason Robb 13 Jul '21

13 Jul '21

The next koha-US general meeting is *tomorrow, *Wednesday, July 14th, 2021. When: 8:30a PT / 11:30a ET / 16:30 UTC (time converter <https://www.timeanddate.com/worldclock/fixedtime.html?msg=koha-US+July+Gene…> ) Where: https://us02web.zoom.us/j/648572897?pwd=TUpsRE1TYlFPWWxTWFl4TVovSTJ3Zz09 Agenda: https://docs.google.com/document/d/1S-VzGJEeyk3JzeHNL9N4gC97ELJSUviiotH_Dwo… If you have additional topics for the agenda, please send them to secretary(a)koha-us.org Meetings are held via Zoom video conferencing. A microphone and webcam are recommended but not required. Zoom is available for Windows, Mac, and Linux on desktops, and Android and iOS on mobile devices. For help getting started, visit: https://support.zoom.us/hc/en-us/categories/200101697 These meetings are always free and open to any and all. Jason Robb koha-US secretary secretary(a)koha-us.org

1 0

Call for news - Newsletter July 2021
by Michael Kuhn 13 Jul '21

13 Jul '21

Hi I'm collecting news for the July 2021 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 -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik(a)adminkuhn.ch · W www.adminkuhn.ch

1 0

Add separator from fields 245a and 245c
by Javi Legido 12 Jul '21

12 Jul '21

Hi there. We have below XML: <datafield tag="245" ind1=" " ind2=" "> <subfield code="a">Gestión empresarial. El caso de dieciocho cooperativas</subfield> <subfield code="b"></subfield> <subfield code="c">Consultores Asociados (Coord.)</subfield> </datafield> Which leads to below string both in admin and OPAC: Gestión empresarial. El caso de dieciocho cooperativas Consultores Asociados (Coord.) Question: how to add a string (let's say " | ") between fiedls 245a and 245c? Thanks. Javier

2 2

Access denied after try to run batchRebuildBiblioTables.pl
by DHIM IT 11 Jul '21

11 Jul '21

Dear colleagues, I will try to rebuild the biblioitems table after mapping a new value in “Koha to MARC mapping”, but I get this error: /usr/share/koha/bin/batchRebuildBiblioTables.pl -c DBI connect('database=koha;host=localhost;port=3306','',...) failed: Access denied for user 'root'@'localhost' (using password: NO) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1517. DBI connect('database=koha;host=localhost;port=3306','',...) failed: Access denied for user 'root'@'localhost' (using password: NO) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1517. DBI connect('database=koha;host=localhost;port=3306','',...) failed: Access denied for user 'root'@'localhost' (using password: NO) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1517. DBI connect('database=koha;host=localhost;port=3306','',...) failed: Access denied for user 'root'@'localhost' (using password: NO) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1517. DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: Access denied for user 'root'@'localhost' (using password: NO) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1520. at /usr/share/koha/lib/Koha/Database.pm line 117 Koha version: 20.11.05.000 I can connect to MySQL without problems without password like: mysql -u root What am I doing wrong? Eugen Bastron

2 2