- Koha - lists.katipo.co.nz

Can the Koha Mailing List and DMARC become friends?
by David Liddle 09 Mar '23

09 Mar '23

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.

5 5

Modify Patron Transaction Invoices and Fee Receipts
by Ms. Naveen Ali 09 Mar '23

09 Mar '23

Dear members, I'd like to modify the Patron Transaction Invoices and Fee Receipts. In fact all the print options available on the Patron Screen (Summary, Slip, Quick Slip, Overdues, Check In Slip) I can't identify them in the Notices and Slips Tool Please provide support. With best regards, Naveen Ali ITM-JE (EAKL) Inst Representative for HEC Digital Library Resources. NEDUET, Karachi.

5 7

koha-US General Meeting reminder: Wednesday, March 8, 2023
by Jennifer Marlatt 07 Mar '23

07 Mar '23

The next koha-US General Meeting is Wednesday, March 8, 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/1XuJBDP47HshDvlSGjIk1xJROgSd-Q2ii6lUsRJn… 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

Reminder: Request for proposals to host KohaCon 2024
by Caroline Cyr La Rose 07 Mar '23

07 Mar '23

Hello dear community! This is a reminder that proposals to host KohaCon 2024 are due in one month (*4 April 2023 23:59 UTC*). You can read the original request here: https://lists.katipo.co.nz/public/koha/2023-February/059031.html If you have any questions regarding hosting the conference, how do make the proposal, etc. don't hesitate to ask here on this mailing list, or on IRC (https://koha-community.org/get-involved/irc/) where there are usually people at all times in all time zones. Best regards, Caroline <https://inLibro.com/en> Caroline Cyr-La-Rose, M.L.I.S. Librarian | Product Manager P 833-INLIBRO (465-4276) <tel:833-465-4276>, poste 221 E caroline.cyr-la-rose(a)inlibro.com www.inLibro.com <https://inLibro.com/en>

1 0

Re: [Koha] Setting folders for access_dir
by David Liddle 07 Mar '23

07 Mar '23

Hello Aida, I just had my first experience with the “access_dir” function today. I’m experimenting with using it to expose the files that I have put into the following new directory on the server: /var/lib/koha/libraryname/web/ The idea is to put files in this directory that can be referenced by URLs that are manually entered in system preferences, e.g. the favicon.ico image shown in the browser tab. The location of this directory was suggested to me in Bug 33115, https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33115, because I was looking for a directory that would be included in the Koha backup routine and koha-dump and could be served through the web. Back to the use of “access_dir”. By listing the files in that directory, a staff user with the access_files permission can see what files are available for logos and icons, for example, and enter the appropriate URL in the system preferences by putting the file name after the base URL and /web/ (as set up according to the bug commenter’s suggestion). I don’t expect it to be used this way very much, but doing this can enabled authorized staff to make changes to the site’s appearance without asking a system administrator to do everything. The feature only lists the files in the staff interface and allows the staff user to download them. They can’t be edited or deleted, so they’re safe.

2 1

Transfer Issue Related to Item Type
by Evan Lembke 06 Mar '23

06 Mar '23

Hello, Two years ago we (2 site school) migrated from Follett to Koha on-prem. During the migration, the imported item records did not come with an item type but they still imported. This now causes a "Return to Home Library" notification when items are being checked in. However, I noticed that this error was not happening to new items that were being entered (because they had an item type from the start). When I figured out it was an item type issue, I did a batch edit and assigned all my items an item type. After this, I am still getting the "Return to Home Library" message on those items with the following exception: If I click on the item, click Edit, then immediately click save, the issue no longer affects that particular item. It is almost like the batch modification changes the value but the system doesn't recognize it yet until I edit/save it. I really don't want to have to manually edit/save each item if possible. I saw there was a touch_all_items script but I can't find any documentation to see if that is what I need. Does anyone have any ideas or suggestions? Thank you for any help you may be willing to offer. Evan Lembke "Creativity is intelligence having fun." - Albert Einstein

2 2

Replacing existing images in Koha with our own
by library＠ssst.edu.ba 06 Mar '23

06 Mar '23

Hi all, Another thing I don't understand is how to replace images (logos in the OPAC and the login etc.) with our own images. I have tried following instructions on https://www.vijenderkumar.com/2022/05/beautify-koha-staff-login-page.html >>Create an image for the logo or copy it from the institute's website. Save it in the home folder with the name 'logo.jpg' >>Open the terminal and run the following command to paste the logo image in htdocs folder from the home folder >>sudo cp logo.jpg /usr/share/koha/opac/htdocs >>Now Open koha Staff Interface >>koha administration➞ Global System Preferences➞Staff Client➞StaffLoginInstructions >>Add the following html scripts in the StaffLoginInstructions... How do I even save something to the home folder in the terminal?? When I tried using it to copy the image to /usr/share/koha/opac/htdocs nothing happened, so I asked one of our IT staff to install Filezilla for me so that I can at least move the files to these locations. I proceeded with the instructions and pasted the code to the StaffLoginInstructions, changed the IP: http://127.0.1.1 with our Koha OPAC IP but there's just a broken image where the logo is supposed to be. How in the world are others making these changes? Best regards Aida Đikić -----Original Message----- From: Koha <koha-bounces(a)lists.katipo.co.nz> On Behalf Of koha-request(a)lists.katipo.co.nz Sent: Friday, March 3, 2023 12:00 AM To: koha(a)lists.katipo.co.nz Subject: Koha Digest, Vol 209, Issue 3 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..."

4 11

Adding pages to Koha OPAC - Koha as a CMS
by library＠ssst.edu.ba 06 Mar '23

06 Mar '23

Hello all, I need some help with adding new pages to Koha. From what I gathered, we can use additional pages available through the Administration > System preferences > OPAC to add information about the library, libguides, etc. However, when I tried adding pages, I got the error 404 when I tried opening the newly added page in OPAC (both default and current language), but the page is visible in the Librarian interface. I googled Koha pages, found instructions on using Koha as a CMS on "KohaGeek" https://kohageek.blogspot.com/2016/09/koha-as-cms.html and on "Solution For Library Management" blogs https://atulhbch.wordpress.com/2019/05/24/koha-as-a-web-page-koha-as-cms/, followed those but I still get an error message. [The reason I used those blogs instead of say, https://koha-community.org/manual/21.11/en/html/extending_koha.html#using-k… is because they list what commands to use instead of just saying copy this file to here. I then have to google which command is used to copy something using the terminal, which makes it *very frustrating* to follow any instructions on the official pages. I think there's a lot of users such as myself who have no Linux or programming experience and no support. It would be useful to already have the commands listed in the instructions.] Also, I just realized that Koha as a CMS instructions are missing from the manual for 22.11, which is the version I'm testing (Koha 22.11.01 on my work server, and Koha 22.11.02 on my personal laptop). Is there a reason this was removed, and how do I get pages to show up in the OPAC? Thank you in advance! Best regards Aida Đikić -----Original Message----- From: Koha <koha-bounces(a)lists.katipo.co.nz> On Behalf Of koha-request(a)lists.katipo.co.nz Sent: Friday, March 3, 2023 12:00 AM To: koha(a)lists.katipo.co.nz Subject: Koha Digest, Vol 209, Issue 3 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..."

3 3

subscribe to mail list
by Torma, Rozália 04 Mar '23

04 Mar '23

*Rozalia TORMA* *Bibliothekarin* | Könyvtáros *Bibliothek *| Könyvtár _______________________________ *Andrássy Universität Budapest* | * Andrássy Gyula Budapesti Német Nyelvű Egyetem**H-1088 Budapest |** Pollack Mihály tér 3*. Tel | (+36) 1-8158-133 Fax | (+36) 1-266-3099 www.andrassyuni.eu/bibliothek -- Diese Mitteilung erfolgt vertraulich und nur zur Kenntnisnahme durch die hierfür vorgesehenen Personen. Ihr Inhalt kann durch gesetzliche Berufs- oder Geschäftsgeheimnisse oder in sonstiger Weise geschützte Informationen enthalten. Sollte die Mitteilung irrtümlich zu Ihnen gelangt sein, ist jede Weitergabe, Kopie oder Nutzung des Inhalts unzulässig. Bitte benachrichtigen Sie den Absender gegebenenfalls telefonisch oder mit Antwortmail und löschen Sie diese Nachricht und alle Anhänge dazu unverzüglich. This message is confidential and may contain privileged, undisclosed or confidential information protected by law or regulation intended only for the exclusive use by particular persons. If you have received it by mistake, any review, copying, use or dissemination in whole or in part is strictly prohibited. Please notify the sender by return e-mail and delete this message and all its attachments from your system. Az ebben az e-mailben közölt információ bizalmas, törvény védi és csak a fent nevezett személynek vagy cégnek szól. Amennyiben nem Ön a címzett, tájékoztatjuk Önt, hogy ezen e-mail tartalmának nyilvánosságra hozatala, sokszorosítása, mások részére történő átadása és minden vele kapcsolatos cselekvés szigorúan tilos. Ha Ön ezt az e-mailt tévedésből kapta meg, kérjük, a lehető leggyorsabban lépjen velünk kapcsolatba.

1 0

KOHA upgrade error
by zen zenitram 03 Mar '23

03 Mar '23

Good morning all, we are trying to upgrade our koha database but too many duplicate entry shows. ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Duplicate entry 'ar' for key 'PRIMARY' at /usr/share/koha/lib/C4/Installer.pm line 739 This is the first error i encountered when upgrading koha from v20.05 to the latest version that is 22.11 and i already found the fix. The next error is " ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Duplicate entry '20534' for key 'import_biblios.PRIMARY' at /usr/share/koha/lib/C4/Installer.pm line 739". we tried to locate this duplicate entry and it points to biblios in reservoir entry. Anyone of you encountered this kind of error while upgrading? I need help on how we gonna fix it. Thank you!

2 1