- Koha - lists.katipo.co.nz

The Terrific Every-Other-Thursday Training Video
by BRANNON, CHRISTOPHER 23 May '24

23 May '24

You may or may not know that Koha has a great Self Check system. Let's just assume you don't know. Anyway, George and Christopher are going to talk about the self check, and some of the things they are doing to make it better, and some things that it still needs a little help on. Oh, and chances are, George's kids still doesn't like our videos. They'll come around someday. https://youtu.be/75C_o2Ox7zw Sincerely, Christopher Brannon koha-US Admin

1 0

koha-US consortia special interest group will meet Thursday
by George 21 May '24

21 May '24

Hello everyone, The koha-US Consortia Special Interest Group will meet this Thursday, May 23, at 16:00 UTC <https://www.timeanddate.com/worldclock/fixedtime.html?msg=koha-US+Consortia…> on Zoom at https://us02web.zoom.us/j/929501615?pwd=ZmkwaHFSTFZ5WHpXTGNHMkovMk5hZz09 That's 9:00 a.m. PT / 10:00 a.m.MT / 11:00 a.m.CT / 12:00 p.m. ET in the U.S. There is an agenda for this meeting at https://docs.google.com/document/d/1hOmVLfLhL67lKxPFBwvVa4mn0MqliFaMWco0Yxc… but currently there is nothing on it. If you'd like to add something, feel free. Anyone is welcome to attend. George -- George Williams Pronouns: he/him Next Search Catalog Coordinator Send NEXT support e-mails to nexthelp(a)nekls.org NEKLS Office: 785-838-4090 Toll Free: 888-296-6963 Fax: 785-838-3989 Next After-Hours: 785-813-1356 For specific support issues, please use: Next Catalog Support: nexthelp(a)nekls.org Courier Support: chandwork(a)nekls.org Technology Support: tech(a)nekls.org 4317 W 6th St, Lawrence, KS, 66049

1 0

[Fwd: Re: Koha Foundation Vote is open]
by Thomas Dukleth 16 May '24

16 May '24

Please, whenever we next have a community poll, we should go back to using FOSS software, such as LimeSurvey which we have used in the past. Using non-FOSS software, such as JotForm if I understand correctly, where the source code is not even available for audit is particularly problematic for community surveys. Some language furthering Koha as FOSS and the Koha community in a FOSS environment wherever practical should be in the organisational purpose of any Koha community foundation incorporation papers. FOSS should be the primary reason people choose Koha and we should avoid diluting that message wherever practical. [Previous reply with a minor word order correction is quoted below.] Thomas Dukleth Agogme 109 E 9th Street, 3D New York, NY 10003 USA http://www.agogme.com +1 212-674-3783 ---------------------------- Original Message ---------------------------- Subject: Re: [Koha] Koha Foundation Vote is open From: "Thomas Dukleth" <kohalist(a)agogme.com> Date: Thu, May 16, 2024 02:20 -------------------------------------------------------------------------- [Reply inline with a word order correction.] On Wed, May 15, 2024 21:47, Auld, Andrew wrote: > The Koha Foundation proposal vote is now open. You can place your vote on > the Koha Community website and there you will also find a link to the > proposal and background research. Votes must be placed by 5pm UTC on > Friday > 14 June. One vote per person please. If I remember correctly, previous survey software used for voting on Koha community concerns certainly had the principle of one vote per person but allowed vote reconsideration and changing the one counted voted by voting again with a different vote. > https://koha-community.org/koha-foundation-vote/ In https://ptfs-europe.com/koha-foundation-proposal/ , very little is stated about the intended governance structure of a foundation other than the legally required five member board of directors and two volunteers, and the unstated presumptive necessity that it has to avoid legal conflicts of interest to comply with Open Library Foundation and US non-profit 501c3 rules. For example, there is no statement considering a concern of historic discussions of a possible Koha foundation to geographically federate some input into foundation governance for such an internationally distributed project as Koha to avoid the foundation excessively serving US or Anglo-US interests based on the US location of the foundation other than "in the first instance, to keep the governance light". There is also no historical background explaining that the project had previously organised under Horowhenua Library Trust [HLT], subsequently THT. Upon the dissolution of THT for Horowhenua District Council [HDC] to directly run Horowhenua libraries directly, Koha community assets might have devolved to HDC which had created HLT and then THT as an administrative organisation for local libraries. I do not remember what happened if anything decisive subsequent to "THT and Koha: a new Trust Deed" - https://lists.katipo.co.nz/public/koha/2016-October/046346.html and https://wiki.koha-community.org/wiki/THT_and_Koha . The complication at the time was that there was no representative Koha community organisation to which THT or HDC could transfer Koha community assets other than THT which was being dissolved. [...] Thomas Dukleth Agogme 109 E 9th Street, 3D New York, NY 10003 USA http://www.agogme.com +1 212-674-3783

1 0

Koha Foundation Vote is open
by Auld, Andrew 16 May '24

16 May '24

The Koha Foundation proposal vote is now open. You can place your vote on the Koha Community website and there you will also find a link to the proposal and background research. Votes must be placed by 5pm UTC on Friday 14 June. One vote per person please. https://koha-community.org/koha-foundation-vote/ Andrew Auld Commercial Director PTFS Europe [image: Phone icon] M: +44 7811 370104 | T: +44 1483 378728 ext. 1010 [image: Email icon] andrew.auld(a)ptfs-europe.com [image: Link icon] www.ptfs-europe.com Sign up for our Newsletter. <http://eepurl.com/dPjjkn> <http://www.linkedin.com/company/ptfs-europe-limited> <http://youtube.com/@PTFSEurope> [image: Click to open PTFS Europe webpage] <https://www.ptfs-europe.com>

2 1

Question about inventory
by Ratliff, Ramona 14 May '24

14 May '24

Hello everyone, We are starting to do inventory, and the two of us working with it haven't done it before in Koha, so we have one question. When we ran a shelf list, some of the call numbers were out of order. We use Library of Congress classification. The problem looked like this: JUVE D 767..92 .M42 2002 JUVE DS 793 .G67 M33 1997 JUVE DT 63 .M35 1997 JUVE D 141 .V37 1991 All of the call numbers with only D instead of DS or DT should have come before anything with two letters for this line in the call numbers. Instead, there were Ds, then DFs, DGs, DKs, DSs and DTs and then 5 books with only D showed up after the DTs. *Ramona Ratliff * Information Specialist *York University* Office: (402) 363-5708 | rjratliff(a)york.edu <email(a)york.edu> | *york.edu <http://www.york.edu/>*

2 2

koha-US Board Meeting Minutes for May 08, 2024
by Kristi Krueger 13 May '24

13 May '24

Hello, Here's a link to the minutes from the koha-US board meeting on Wednesday, May 08, 2024- https://docs.google.com/document/d/1MhLDDAL-blIJ-vvT7XKInLgqYhSgBlD-zgs2cgG… koha-US meetings are open to all! Board meetings are held on the second Wednesday of each month at 8:30 PT / 9:30 MT / 10:30 CT / 11:30 ET. The next koha-US General Meeting will be on Wednesday, June 05 @ 8:30 PT / 9:30 MT / 10:30 CT / 11:30 ET (time converter <https://www.timeanddate.com/worldclock/fixedtime.html?msg=koha-US+February+…> ). If you have additional topics for the General Meeting agenda, please send them to secretary(a)koha-us.org. Kristi Krueger koha-US Secretary secretary(a)koha-us.org

1 0

Koha release with security fixes
by Frédéric Demians 13 May '24

13 May '24

Hello all, The Koha community is proud to announce the release of Koha maintenance versions: 23.11.05 23.05.11 22.11.17 22.05.21 It is a bugfix/maintenance release including a lot of security fixes. It is highly recommended to upgrade. The full release notes will soon be available here: https://koha-community.org/koha-23-11-05-released/ https://koha-community.org/koha-23-05-11-released/ https://koha-community.org/koha-22-11-17-released/ https://koha-community.org/koha-22-05-21-released/ Debian packages are available. Kind regards, -- Frédéric DEMIANS https://www.tamil.fr/user/fdemians

1 0

Call for news - Newsletter May 2024
by Koha Newsletter 13 May '24

13 May '24

Hi I'm collecting news for the May 2024 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

User instance-koha already exists
by Victor Barroso Oliveira 12 May '24

12 May '24

Good afternoon, Koha v. 22.05.16 Removed an instance $koha-remove instance Then I tried to create an instance with the same name $koha-create --create-db instance It displayed the following message "User instance-koha already exists" How can I resolve this?

3 2

Issue with updated_on in borrowers table and LDAP auth
by Betka, Corey A 12 May '24

12 May '24

Hello, I've inherited a really old install of koha (3.18.11) and I'm trying to get it migrated to current stable. I've figured out most of the database upgrade issues along the way thanks to the mailing list archives and old bug entries, but now I've run into something I can't find a solution for. Relevant versions: OS: Ubuntu 22.04 Koha: 23.11.04-4 MySQL: 8.0.36-0ubuntu0.22.04.1 Issue: When a user is created via LDAP auth to the OPAC, the updated_on field in the borrowers table is set to "0000-00-00 00:00:00" and this makes it fail to display in the Intranet interface, showing a 500 error for that page of Patrons or if you search directly for the patron. If I have the new patron request a change in their record via OPAC and approve it in the Intranet, the updated_on field changes to a current value and then things work as expected. That's obviously not scalable. We have LDAP auth configured to connect to our campus active directory with the following settings: <replicate>1</replicate> <update>1</update> <auth_by_bind>1</auth_by_bind> <mapping> <firstname is="givenName" ></firstname> <surname is="sn" ></surname> <userid is="sAMAccountName" ></userid> <email is="mail" ></email> <address is="streetAddress" ></address> <city is="l" >Champaign, IL</city> <privacy is="" >1</privacy> <branchcode is="" >TCC</branchcode> <categorycode is="" >ST</categorycode> </mapping> I've done some slight modification to the logging in Patron.pm and the values that are being logged for updated_on don't make much sense to me: "updated_on" : { "after" : "SCALAR(0x55fff641bca0)", "before" : "2024-05-03 21:59:40" } } Any suggestions? Is this a side effect of explicit_defaults_for_timestamp changing in MySQL? Does mariadb handle this differently? I had to use mysql to get past some foreign key issues early in the database upgrade scripts, but am open to migrating to mariadb now that the data can be brought forward. Thanks, Corey Betka Infrastructure Architect University of Illinois at Urbana-Champaign │ Student Affairs │ Student Affairs Technology 330 Clark Hall │ 1203 S 4th St │ M/C 548 │ Champaign, IL 61820

2 1