- Koha - lists.katipo.co.nz

Koha version 21.05.10 released
by Andrew Fuerste-Henry 10 Feb '22

10 Feb '22

Hello Koha! The Koha community is proud to announce the release of version 21.05.10. This is a maintenance release to correct an error in 21.05.09. You can see the release notes here: https://koha-community.org/koha-21-05-10-released/ Or you can see the bug detailing the error here: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30065 Thanks! Andrew -- Andrew Fuerste-Henry Educator (he/they) ByWater Solutions bywatersolutions.com Phone:(888)900-8944 <(888)%20900-8944> What is Koha? <http://bywatersolutions.com/what-is-koha/>

2 1

Elasticsearch sorting broken
by Thomas Klausner 09 Feb '22

09 Feb '22

Hi! (I did not want to file a bug yet, because maybe we're doing something stupid on our side...) We're using Elasticsearch for searching, but when using a non-default sort, the results are not really sorted: https://katalog.landesbibliothek.steiermark.at/cgi-bin/koha/opac-search.pl?… This should sort by author, and it seems to be partly sorted, but several results are completly out of place. Here's another example, sorted by publication date: https://katalog.landesbibliothek.steiermark.at/cgi-bin/koha/opac-search.pl?…... We get the weirdest results when sorting by author: https://libelle.stmk.gv.at/cgi-bin/koha/opac-search.pl?idx=&q=wald&sort_by=…... I dumped the query from Koha and sent it directly to Elasticsearch, and found some weird data in the result: curl http://es:9200/index/_search?pretty -X GET -H 'Content-Type: application/json' -d '{"sort":[{"issues__sort":{"order":"asc"}}],"query":{"query_string":{"default_operator":"AND","query":"(arisophanes)","lenient":true,"type":"cross_fields","fields":["title"],"fuzziness":"auto","analyze_wildcard":true}}}' "hits" : { "hits" : [ { "_source" : { .... "sort" : [ "ށA†倀\u0001" ] }, Now I'm not sure if the weird binary data in sort ("ށA†倀\u0001") is some ES-internal representation, or if there's something wrong with our index or our data? Does anybody else has any experience with using the non-default sort methods and elasticsearch? I doubt that this is a bug in Koha, because it's a very obvious and often-used feature, so I fear we might have a problem with some data / ES-Mappings / etc. Any ideas / input? Greetings, domm -- #!/usr/bin/perl https://domm.plix.at for(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/}

1 0

ISSUE with Umlaut
by Russel G. P. Shihepo 09 Feb '22

09 Feb '22

Dear Community I have a prepared data set in excel format (.xlsx), some of it contains umlaut (German texts) and click sounds symbols of African languages such as field 245, and 260. But whenever I import the file to MARC editor through the Delimited Text Translator, I lose all the umlaut and punctuation marks for click sounds in the data. Does anybody have a clue or alternative method that can be used to take records from excel files to MARC editor without losing umlaut? Regards Russel Shihepo *Librarian* *Africa/Namibia*

3 2

HOW TO IMPORT MARC RECORDS INTO KOHA ILS
by Russel G. P. Shihepo 09 Feb '22

09 Feb '22

Dear Community I have been attempting to stage import MARC records into Koha ILS with no success. The MARC records were an export from our old ABCD system. Below is the MARC view of the records, perhaps I'm missing something, please advise. =LDR 00000nam 2200000Ia 4500 =008 220206s9999||||xx\||||||||||||||\||und|| =020 \\$aNA$cJahresbericht der SWA Wissenschaftlichen Gesellschaft Otavi Bergland, Ortsgruppe Tsumeb =022 \\$a Windhoek =942 \\$cBK =952 \\$aNAMSC$bNAMSC$p451a$nMitteilungen =082 \\$aErnst Wilhelm =100 \\$aSWA Wissenschaftliche Gesellschaft$cOrtsgruppe Tsumeb =110 \\$bSerieScientific Society =245 \0$a1989 =250 \\$a3 pages =260 \\$b30 cm =600 \\$qSouth West Africa$dAnnual meetings =650 \\$bAlbat$vPER =852 \\$nJohn Meinert Am I perhaps missing something in the records, because i can't seem to go past the final step, import this batch into the catalog. Best regards Russel Shihepo Notitia Systems cc Africa, Namibia

4 4

koha-US General Meeting reminder: Wednesday, February 9, 2022
by Jennifer Marlatt 08 Feb '22

08 Feb '22

The next koha-US general meeting is *tomorrow, *Wednesday, February 9, 2022. When: 8:30a PT / 11:30a ET / 16:30 UTC (time converter <https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.timea…> ) Where: https://us02web.zoom.us/j/648572897?pwd=TUpsRE1TYlFPWWxTWFl4TVovSTJ3Zz09 <https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fus02web.z…> Agenda: https://docs.google.com/document/d/17GDfBSFp2qnWS5UW4Z-Mb2psI78r8-K5dfLJaYT… 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 <https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsupport.z…> These meetings are always free and open to any and all. Jennifer Marlatt koha-US Secretary secretary(a)koha-us.org

1 0

The Terrific Every-Other-Thursday Training Video - S2E9 - jQuery: Print Slip Descriptions
by BRANNON, CHRISTOPHER 08 Feb '22

08 Feb '22

I was so ahead of the game in preparing our last video, I forgot to put the word out when it was actually available! Sorry about that! It's time to slip into another iconic episode where George shares how to modify the print slip descriptions for easier identification. He'll even throw in another quick modification to change which slip is printed with the print/close icon<https://youtu.be/e9s3bLPyFUQ>.

1 0

Multiple IDs or card numbers per user
by Andy Boze 08 Feb '22

08 Feb '22

Hi, all. My campus is starting to investigate implementation of digital IDs for students. This would allow them to use their android, iphone, or apple watch digital wallet in place of their standard ID card. They would have up to three unique credentials that act like barcode numbers — the ID card number itself, a phone credential and a watch credential. If this is implemented essentially we would have to store up to three “barcodes” per patron. Is there any way to accommodate this in Koha? Thanks! Andy -- Andy Boze, Associate Librarian University of Notre Dame 271H Hesburgh Library (574) 631-8708

4 8

Re: [Koha] Can't Define or display libraries in staff client
by Abdulsalam Yousef 07 Feb '22

07 Feb '22

Solved! On Sun, 6 Feb 2022, 2:00 am , <koha-request(a)lists.katipo.co.nz> wrote: > Send Koha mailing list submissions to > koha(a)lists.katipo.co.nz > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.katipo.co.nz/mailman/listinfo/koha > or, via email, send a message with subject or body 'help' to > koha-request(a)lists.katipo.co.nz > > You can reach the person managing the list at > koha-owner(a)lists.katipo.co.nz > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Koha digest..." > > > Today's Topics: > > 1. Can't Define or display libraries in staff client > (Abdulsalam Yousef) > 2. Importing encrypted patron passwords (Mark Alexander) > 3. Re: Importing encrypted patron passwords (Tomas Cohen Arazi) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 5 Feb 2022 12:00:48 +0300 > From: Abdulsalam Yousef <ayousef(a)kwareict.com> > To: koha(a)lists.katipo.co.nz > Subject: [Koha] Can't Define or display libraries in staff client > Message-ID: > <CADRHuh37tuxsaHGJuUxewjKmOGwG5A= > Pp1YD-jsJDQ+m7oyRVw(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Hello All, > I'm trying to Define new branches from Koha basic parameters in staff > client (http://localhost/cgi-bin/koha/admin/branches.pl) but there are no > branches displayed, I guess it's fetched through the API, and the http Get > request for > http://subdomain.com/api/v1/libraries?_page=1&_per_page=20&q=[]&_match= > contains&_order_by=+me.name > <http://subdomain.com/api/v1/libraries?_page=1&_per_page=20&q=[]&_match=cont…> > returned 500 Internal server error! > All configurations seem to be good. > Is it a compatibility issue? > > My current env vars are: > OS: Debian10 > Koha version: 21.11.01.000 > Perl Version: 5.02800 > Mojoliciou: 9.22 > Mojolicious::Plugin::OpenAPI: 5.02 > JSON::Validator: 5.05 > > Has anyone faced this problem before? > Thanks in advance. > > > ------------------------------ > > Message: 2 > Date: Sat, 05 Feb 2022 08:30:45 -0500 > From: Mark Alexander <marka(a)pobox.com> > To: koha <koha(a)lists.katipo.co.nz> > Subject: [Koha] Importing encrypted patron passwords > Message-ID: <1644067026-sup-2295@t450s> > Content-Type: text/plain; charset=UTF-8 > > > I'm in the process of upgrading a library's Debian 7/Koha 3.16 setup. > This installation is so old that an in-place upgrade can't be done. > My plan is to first create a test VM with Debian 10 and the latest > stable koha-common. Then after manually setting up various admin > things (library, item types, ccode, loc, patron types), I'll import > the catalog and the patron list. Finally, I'll move the resulting > database to the real (live) server. > > The snag here is the patron passwords. I'll use a report from the SQL > library to export the patron list from the old installation, but the > passwords will be encrypted. My understanding is that when importing > the patron list, the passwords must be unencrypted. So I'll need to > remove the password column from the CSV file, and as a result, > every patron password will have to be reset manually. > > Is there any workaround for this? I would just like to move the > encrypted passwords from the old installation to the new one. I am > comfortable doing some hand-crafted SQL updates to accomplish this. > But before I make the attempt, is there any reason why this wouldn't > work or why it's a bad idea? > > -- > Single-handedly, I have fought my way > into this hopeless mess. --Ashleigh Brilliant > > > ------------------------------ > > Message: 3 > Date: Sat, 5 Feb 2022 10:42:12 -0300 > From: Tomas Cohen Arazi <tomascohen(a)gmail.com> > To: Mark Alexander <marka(a)pobox.com> > Cc: koha <koha(a)lists.katipo.co.nz> > Subject: Re: [Koha] Importing encrypted patron passwords > Message-ID: > <CABZfb= > UZhzT5MCj2jh5oLg+kUFxXmxpznokEGk6AER9_+d92zQ(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > You should do all you mention, but instead of creating things, you should > just paste the old db and trigger the upgrade process. > > El sáb., 5 feb. 2022 10:31, Mark Alexander <marka(a)pobox.com> escribió: > > > > > I'm in the process of upgrading a library's Debian 7/Koha 3.16 setup. > > This installation is so old that an in-place upgrade can't be done. > > My plan is to first create a test VM with Debian 10 and the latest > > stable koha-common. Then after manually setting up various admin > > things (library, item types, ccode, loc, patron types), I'll import > > the catalog and the patron list. Finally, I'll move the resulting > > database to the real (live) server. > > > > The snag here is the patron passwords. I'll use a report from the SQL > > library to export the patron list from the old installation, but the > > passwords will be encrypted. My understanding is that when importing > > the patron list, the passwords must be unencrypted. So I'll need to > > remove the password column from the CSV file, and as a result, > > every patron password will have to be reset manually. > > > > Is there any workaround for this? I would just like to move the > > encrypted passwords from the old installation to the new one. I am > > comfortable doing some hand-crafted SQL updates to accomplish this. > > But before I make the attempt, is there any reason why this wouldn't > > work or why it's a bad idea? > > > > -- > > Single-handedly, I have fought my way > > into this hopeless mess. --Ashleigh Brilliant > > _______________________________________________ > > > > Koha mailing list http://koha-community.org > > Koha(a)lists.katipo.co.nz > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Koha mailing list > Koha(a)lists.katipo.co.nz > https://lists.katipo.co.nz/mailman/listinfo/koha > > > ------------------------------ > > End of Koha Digest, Vol 196, Issue 6 > ************************************ >

1 0

Importing encrypted patron passwords
by Mark Alexander 06 Feb '22

06 Feb '22

I'm in the process of upgrading a library's Debian 7/Koha 3.16 setup. This installation is so old that an in-place upgrade can't be done. My plan is to first create a test VM with Debian 10 and the latest stable koha-common. Then after manually setting up various admin things (library, item types, ccode, loc, patron types), I'll import the catalog and the patron list. Finally, I'll move the resulting database to the real (live) server. The snag here is the patron passwords. I'll use a report from the SQL library to export the patron list from the old installation, but the passwords will be encrypted. My understanding is that when importing the patron list, the passwords must be unencrypted. So I'll need to remove the password column from the CSV file, and as a result, every patron password will have to be reset manually. Is there any workaround for this? I would just like to move the encrypted passwords from the old installation to the new one. I am comfortable doing some hand-crafted SQL updates to accomplish this. But before I make the attempt, is there any reason why this wouldn't work or why it's a bad idea? -- Single-handedly, I have fought my way into this hopeless mess. --Ashleigh Brilliant

5 10

Can't Define or display libraries in staff client
by Abdulsalam Yousef 05 Feb '22

05 Feb '22

Hello All, I'm trying to Define new branches from Koha basic parameters in staff client (http://localhost/cgi-bin/koha/admin/branches.pl) but there are no branches displayed, I guess it's fetched through the API, and the http Get request for http://subdomain.com/api/v1/libraries?_page=1&_per_page=20&q=[]&_match= contains&_order_by=+me.name returned 500 Internal server error! All configurations seem to be good. Is it a compatibility issue? My current env vars are: OS: Debian10 Koha version: 21.11.01.000 Perl Version: 5.02800 Mojoliciou: 9.22 Mojolicious::Plugin::OpenAPI: 5.02 JSON::Validator: 5.05 Has anyone faced this problem before? Thanks in advance.

1 0