- Koha - lists.katipo.co.nz

Indexing for indic-arabic scripts in koha
by Rupinder Singh 18 Apr '23

18 Apr '23

Hi everyone, I am using Koha which hosts books in multiple languages other than English, including, Hindi, Punjabi, Bengali, Assamese and Urdu, The Bibliographic records for such books are multilingual (with Non-Roman characters in 880 fields). The system retrieves accurate results for English records, but for non-English books like Hindi, and Punjabi the results are not precise. I read somewhere that there is a specific command for zebra indexes that enables non-indic scripts more accurately retrievable. Could you guys help me out here, please? Thank You Rupinder Singh

2 1

UNIMARC cataloging plugins/value builders - help with how to setup and use specific ones for a bug fix
by David Nind 17 Apr '23

17 Apr '23

I've been testing a bug for cataloguing plugins/value builders (it is aimed at fixing the cloning of subfields that use a cataloguing plugin/value builder - see bug 30975 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30975 for more information (this is an omnibus bug, with individual bugs for each cataloguing plugin/value builder)). There are 8 UNIMARC related cataloguing plugins/value builders that I can't work out what they do, and how to set them up and use them: - unimarc_field_124.pl (bug 32850 - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32850) - unimarc_field_125.pl (bug 32853 - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32853) - unimarc_field_126.pl (bug 32856 - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32856) - unimarc_field_210c_bis.pl (bug 32868 - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32868) - unimarc_field_210c.pl (bug 32869 - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32869) - unimarc_field_225a_bis.pl (bug 32870 - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32870) - unimarc_field_225a.pl (bug 32871- https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32871) - unimarc_field_686a.pl (bug 32873 - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32873) If you know or have any ideas, I'd appreciate any information about them - either by adding to the bug or replying to the mailing list Thanks! David Nind david(a)davidnind.com

1 0

UNIMARC fields 440 and 444
by Сычев Игорь Алексеевич 17 Apr '23

17 Apr '23

Hello! What needs to be done so that UNIMARC fields 440 and 444 are displayed in opac-detail? Good Luck! Igor A. Sychev Tomsk Polytechnic University https://lib.tpu.ru<https://lib.tpu.ru/>

1 0

Sample data (acquisitions/circulation) for testing Koha analytics
by Anna Shields 16 Apr '23

16 Apr '23

Hey, all! I'm new around here, so I apologize if this isn't the best place to post this. In that case, I welcome recommendations for a more appropriate place to seek assistance. I'm currently managing a sandbox installation of Koha for a consortium so that our members can test it out as a potential future system. Currently, we have very little data in the system, but some of our analytics team would like to test out Koha's analytics features. I've searched a bit to see whether there's a way to bulk load sample acquisitions and circulation data to a new Koha install, but I haven't found anything helpful. I realize this is probably not an easy problem to solve, but if anyone has a suggestion for how to import this kind of data from another system (OCLC's WMS) or pointers on how I could create well-formed data to insert into the database for testing, I'd really appreciate it. Thank you! Anna ----- Anna Shields (she/they)

2 1

koha-US General Meeting Minutes for April 12, 2023
by Jennifer Marlatt 15 Apr '23

15 Apr '23

Hello, Here's a link to the minutes from the koha-US General Meeting held on Wednesday, April 12, 2023 - https://docs.google.com/document/d/1MxnUphwoulFcCzad1f73msuYQM5poIClYsZ_rFm…. The recording for the general meeting has been posted, there's a link to the record in the minutes. koha-US meetings are open to all! The next board meeting will be on May 3, 2023 at 8:30 PT / 9:30 MT / 10:30 CT / 11:30 ET. The next general meeting will be on May 10, 2023 at 8:30 PT / 9:30 MT / 10:30 CT / 11:30 ET. Jennifer Marlatt koha-US Secretary <secretary(a)koha-us.org>secretary(a)koha-us.org

1 0

TTEOTTV | S3E16 | Repurposed Library Fields
by BRANNON, CHRISTOPHER 13 Apr '23

13 Apr '23

https://youtu.be/o5NSQ8TKSlQ You thought the last video was bad. This is worse! Last week we talked about repurposing library fields. Now we actually DO something with it. Yes, that’s right. We make it MORE useful. Can you believe it? What will we come up with next? Christopher Brannon 2023 koha-US President

1 0

Call for news - Newsletter April 2023
by Koha Newsletter 13 Apr '23

13 Apr '23

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

Re: [Koha] Can the Koha Mailing List and DMARC become friends?
by Thomas Dukleth 12 Apr '23

12 Apr '23

[Resending to correct accidental paste in my message but adding consideration of use of Discourse as a partial workaround.] I added to the meeting agenda some brief consideration of implementation if we adopt DMARC for the Koha mailing list. These issues have had some discussion on the Koha mailing list. There is no problem free way to implement DMARC for mailing lists in part because email and mailing lists were designed before authentication of senders was considered a sufficiently concerning problem. 1. Mailman. Two implementation approaches to consider are the following. Quotations below are from the Mailman 3 section in https://wiki.list.org/DEV/DMARC but there are matching parts in the Mailman 2 section. One option: "Munge the From: header - The obvious way to avoid a DMARC rejection [...]" Alternative option: "Wrap the message - This involves MIME wrapping the original message [...] Users of MUAs that can't unwrap this MIME decoration would suffer." The suffering would be some users of the very wide variety of email clients people use from console, to desktop, to some old mobile device may not see any body message and merely have an attachment requiring extra processing outside of the user's email program. See "If MIMEs could talk: Email structures in the wild" / Bo Waggoner - https://bowaggoner.com/bomail/writeups/mimes.html for some perspective on the complexities of mime use in messages and how every email client has an individual implementation to cope. Limiting scope to affected users. It is reportedly possible to configure Mailman to limit the scope of DMARC mitigations to affected users such that the mailing list messages are unaltered for others, "Enable dmarc mitigations" - https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… . My current understanding leads me to prefer "munging the from header" as an implementation despite some RFC non-compliance. As stated above; email, mailing lists, and their associated RFCs long preceded considerations of authentication. Having problematic email clients for "MIME wrapping" in the wild seems to me to be a worse problem than some otherwise unavoidable RFC non-compliance with the very diverse subscriber base for the mailing list. Diverse subscribers have diverse computer systems and frequently restrictions on changing them where they actually read and reply to email on work systems and other systems as opposed to some major proprietary webmail intermediaries through which email may pass for many people. 2. Discourse. Does Discourse mailing list mode avoid problems with DMARC in a manner that is still sensible for offline use? Mailing lists are good for offline use. Does discourse provide something similar to Mailman "munging the from header" so that the message poster is identified in the email from header originating from the Discourse server allowing email clients to display lists of messages helpfully including by message poster in addition to subject and time? Thomas Dukleth Agogme 109 E 9th Street, 3D New York, NY 10003 USA http://www.agogme.com +1 212-674-3783 On Fri, March 3, 2023 17:43, David Liddle wrote: > Thank you for adding it to the discussion points! > > > On Fri, Mar 3, 2023 at 6:08 PM Katrin Fischer <katrin.fischer.83(a)web.de> > wrote: > >> I have added the DMARC issue to the agenda for the next developer IRC >> meeting, but we might need the people running our mailservers to weigh >> in: >> >> https://wiki.koha-community.org/wiki/Development_IRC_meeting_9_March_2023 >> >> Hope this helps, >> >> Katrin >> >> On 27.02.23 15:49, Coehoorn, Joel wrote: >> > FWIW, I'm seeing the same thing for our "york.edu" domain, but only >> for >> the >> > last couple of months. The list used to handle this correctly. >> > >> > *Joel Coehoorn* >> > Director of Information Technology >> > *York University* >> > Office: 402-363-5603 | jcoehoorn(a)york.edu | york.edu >> > >> > >> > >> > On Mon, Feb 27, 2023 at 8:00 AM David Liddle <david(a)liddles.net> >> wrote: >> > >> >> Greetings, all! >> >> >> >> At the encouragement of one of the mailing list administrators, I >> >> would like to present a situation and a proposal to you all. >> >> >> >> Normally, I would write from my work account, >> david.liddle(a)wycliff.de, >> >> since one of the hats I wear is that of a Koha system administrator. >> >> One of my other hats, however, is that of the email administrator for >> >> our corporate domains. And the latter hat has precedence over the >> >> former. >> >> >> >> To help protect our email domains from being used fraudulently, I >> have >> >> implemented DMARC policies according to current recommendations. You >> >> can read more about the Domain-based Message Authentication, >> Reporting >> >> & Conformance protocol at https://dmarc.org/. The policies direct >> that >> >> only messages from authorized sources should be allowed to send mail >> >> from wycliff.de and our other domains; messages from all unauthorized >> >> sources should be quarantined. >> >> >> >> With DMARC policies in place, messages that I send from my work >> >> account to the Koha mailing list get quarantined by email providers >> >> that comply with the policies' directives. Why? It happens because >> the >> >> Koha mailing list spoofs the email address of the original sender. As >> >> a result, there is a significant number of subscribers who did not >> >> receive the messages at all or had to fetch them from quarantine. >> Some >> >> unknown number will have been marked as spam. >> >> >> >> There are well-meaning reasons for this behavior within an honest, >> >> friendly community such as the Koha mailing list. However, email >> >> spoofing is one of the chief means by which fraudsters engage in >> >> phishing, data exfiltration, and ransomware attacks. In my opinion, >> >> the Koha community ought to avoid the practice of email spoofing. >> >> Therefore, I have a proposal to make: >> >> >> >> -- The Koha Mailing List is based on the Mailman list system. >> >> According to its release notes, Mailman 2.1 supports what the >> >> developers call "DMARC mitigations". >> >> -- Mailman DMARC Mitigations are described here: >> >> >> >> >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/handlers/d… >> >> ++ I PROPOSE that the mailing list subscribers support the >> >> implementation of DMARC mitigations to the Koha mailing list. >> >> -- The result of the implementation would be that messages submitted >> >> to the list would no longer spoof the sender's address, but rather be >> >> altered so that the messages come from the list's own address, >> >> koha(a)lists.katipo.co.nz. They *should* be delivered successfully to >> >> all recipients. A reply to the message would return to the list, and >> a >> >> reply to all could include the original sender's address explicitly. >> >> -- If you agree (or disagree) with this proposal, you'll need to >> >> indicate that in your own clever way, because there's no voting >> >> mechanism in a mailing list. >> >> >> >> Thank you for being so kind and forbearing as to read this far! I >> hope >> >> that you'll give my proposal your earnest consideration. >> >> >> >> Regards, >> >> >> >> David Liddle >> >> >> >> >> >> After-credits scene: >> >> >> >> For you intrepid readers, I would like to boldly suggest something >> >> even more daring than changing the list's sending practices. Please >> >> consider changing the platforms of the Koha email and chat >> discussions >> >> to one such as Discourse: >> >> >> >> -- The Discourse software and community seems to have a fair bit in >> >> common with the character and nature of Koha's. You can read more >> >> about the platform at https://www.discourse.org/. >> >> -- Not only is it a web forum, but it can handle email submissions, >> >> replies, notifications, and digests. (And it would always send from a >> >> legitimate address.) >> >> -- It has migration tools that appear able to import archives such as >> >> those used by this list. >> >> -- It has chat integration for real-time messaging that can also be >> >> perused later. >> >> -- It has functions for search, categorization, and groups that a >> >> mailing list does not. [...]

3 3

Upgrade Schema Issue
by Taimoor Memon 12 Apr '23

12 Apr '23

Hello everyone, I'm facing an issue in the upgradation of Koha, terminal is executing the following error: DBD::mysql::st execute failed: Table 'koha_library.systempreferences' doesn't exist at /usr/share/koha/lib/Koha/Database.pm line 152. DBD::mysql::st execute failed: Table 'koha_library.systempreferences' doesn't exist at /usr/share/koha/lib/Koha/Database.pm line 152. Use of uninitialized value in numeric lt (<) at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 78. DBD::mysql::db do failed: Table 'koha_library.bookshelf' doesn't exist at /usr/share/koha/lib/Koha/Database.pm line 152. DBD::mysql::db do failed: Table 'koha_library.shelfcontents' doesn't exist at /usr/share/koha/lib/Koha/Database.pm line 152. DBD::mysql::db do failed: Table 'koha_library.virtualshelfcontents' doesn't exist at /usr/share/koha/lib/Koha/Database.pm line 152. DBD::mysql::db do failed: Table 'koha_library.virtualshelfcontents' doesn't exist at /usr/share/koha/lib/Koha/Database.pm line 152. Undefined subroutine &main::DropAllForeignKeys called at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.pl line 86. -- Regards: *Irfan Taimoor Memon*

2 1

koha-US General Meeting reminder: Wednesday, April 12, 2023
by Jennifer Marlatt 10 Apr '23

10 Apr '23

The next koha-US General Meeting is Wednesday, April 12, 2023. When: 8:30a PT / 11:30a ET (time converter <https://www.timeanddate.com/worldclock/fixedtime.html?msg=koha-US+general+m…> ) Where: https://us02web.zoom.us/j/293750042?pwd=SGQzS2pmU3prNFhYRHNaeTFhOHN4QT09 Agenda: https://docs.google.com/document/d/1Jb6ET1xhfVWqigh0ifnr85IYnK6510fd_h55EqZ… 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. Jennifer Marlatt koha-US Secretary secretary(a)koha-us.org

1 0