- Koha - lists.katipo.co.nz

Translators - Do not wrap strings in PO files
by Jonathan Druart 11 Oct '23

11 Oct '23

Hello, I have a question for translators: do you like how strings are wrapped in PO files? In the context of moving our translations server to weblate we will have to reorder the PO files, and maybe we could take that opportunity for other changes. One of them could be to not wrap lines, and have a single long line instead. For instance: Now: msgid "" "%s %sSpring%s %s %sSummer%s %s %sFall%s %s %sWinter%s %s %sSpr%s %s %sSum%s " "%s %sFal%s %s %sWin%s %s %s %s " msgstr "" "%s %sPrintemps%s %s %sÉté%s %s %sAutomne%s %s %sHiver%s %s %sPrtps%s %s " "%sÉté%s %s %sAut%s %s %sHiv%s %s %s %s" After: msgid "%s %sSpring%s %s %sSummer%s %s %sFall%s %s %sWinter%s %s %sSpr%s %s %sSum%s %s %sFal%s %s %sWin%s %s %s %s " msgstr "%s %sPrintemps%s %s %sÉté%s %s %sAutomne%s %s %sHiver%s %s %sPrtps%s %s %sÉté%s %s %sAut%s %s %sHiv%s %s %s %s" For those who translate directly in the PO files, which version do you like more? Regards, Jonathan Context: https://wiki.koha-community.org/wiki/Translation_server_migration_weblate https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35024

2 3

Restrict suggestions shown on OPAC
by Ms. Naveen Ali 11 Oct '23

11 Oct '23

Greetings!! We are using Koha 22.11 on Ubuntu. https://eakl.neduet.edu.pk I was wondering if there is a way to restrict the suggestions shown on the OPAC. Currently we see all the suggestions that have been entered in the system. I see an option to purge suggestions. If I purge suggestions based on date, it will remove the related information of Requesting patron and Funds, etc which is required for reporting purpose because th e suggestions are endorsed by Department Chairpersons. I only want to restrict display on OPAC. With best regards, Naveen Ali ITM-JE (EAKL) Inst Representative for HEC Digital Library Resources. NEDUET, Karachi.

1 0

koha-US General Meeting reminder: Wednesday, October 11, 2023
by Jennifer Marlatt 10 Oct '23

10 Oct '23

Hello! The next koha-US General Meeting is Wednesday, October 11, 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/1mU8nt9PG7FvvWZBuzxuvKCSpRTZ02qADYbwHAC6… 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

October Koha-US Circulation Special Interest Group ("CircSIG")
by Lauren Denny 09 Oct '23

09 Oct '23

Hi everyone, Join us for the next Koha-US Circulation meeting this Thursday, October 12, at 8 PT / 9 MT / 10 CT / 11 ET / 15 UTC You don't have to be a member of Koha-US to join us, we're hoping you'll come! Bring topics on anything to do with patrons, circulation, notices, OPAC, etc. Here is the link to the Zoom meeting and https://us02web.zoom.us/j/962703559?pwd=SjJWcW9CRDJvMy8ycVIyTzIzOUdSUT09 Can't make it? No worries--it will be recorded and available on the Koha-US YouTube Channel: https://www.youtube.com/c/kohaUS/playlists (See the Circulation Special Interest Group's playlist for past circulation topics!) Feel free to send me any questions or topics for discussion ahead of time! Jon and I will be gone at other conferences but the famous Georgette Rogers, who spoke on circulation workflows at the most recent Koha-US Conference, has offered to step in for us. Thank you so much! I'm looking forward to watching the recording. :) Lauren Denny

1 0

Koha-US System Administration SIG
by Andrew Fuerste-Henry 09 Oct '23

09 Oct '23

Time continues to hurtle forward in a manner both terrifying and inescapable, which means we're due for another meeting of the Koha-US System Administration Special Interest Group! Join us to discuss the Administration module, system preferences, reports & SQL, and any other topics of great universal import. Our next meeting will to tomorrow, 10/10, at 8 PT / 9 MT / 10 CT / 11 ET. Join us on Zoom here: https://us02web.zoom.us/j/955473977?pwd=S3RGaW90SmxVVkRSaHk3ZERMOExBZz09 See more details here: https://koha-us.org/event/system-administration-special-interest-group/?ins… Andrew Fuerste-Henry Assistant Library Director Dubuque County Library District www.dubcolib.org | 563-582-0008 he|they<https://www.mypronouns.org/>

1 0

Working with nginx and installing on URL prefixes
by Daniel Bünzli 09 Oct '23

09 Oct '23

Hello, I’m trying to make an install of koha to consider migrating to it from another ILS. Given our existing infrastructure the setup scheme of koha on different domains is not entirely convenient for us nor is using apache (even if only proxied by nginx we rather not add more moving part to our infrastructure). Ideally we would like to be able to have: 1. The opac on say example.org/koha/catalogue 2. The staff interface on say example.org/koha/intranet 3. Use the official debian packages 4. Use nginx directly instead of apache I haven’t been succeeding so far. But I’m at a point where I can `koha-plack —start mylib` and convince nginx to talk to plack on the prefixes by having: location /koha/intranet { include proxy_params; proxy_pass unix:/var/run/koha/mylib/plack.sock:/intranet/mainpage.pl; proxy_buffer_size 8k; } location /koha/catalogue { include proxy_params; proxy_pass unix:/var/run/koha/mylib/plack.sock:/opac; proxy_buffer_size 8k; } I gather there’s an additional bunch of rewrites rules in the the apache configuration files that I will have to port at some point but one thing I’m stuck on is that when I try to access `example.org/koha/intranet` it redirects to the root of the domain `example.org/cgi-bin…` rather than `example.org/koha/intranet/cgi-bin…` to trigger the install procedure. So here are two questions: a) Is there an easy way to convince koha to root its URLs w.r.t. to the prefix we’d like them to be on ? Maybe an environment variable or a launch parameter or an http header to set in the nginx configuration ? (I’m a bit unfamiliar with the whole plack/starman eco-system) b) Is there any strong problem I’m not seeing in trying to setup koha the way I outlined above and use nginx rather than apache to serve the app ? Thanks, Daniel P.S. I also vaguely considered the `app.psgi` part of the source distribution but this workflow doesn’t seem to be documented or supported in the debian packages from which I rather not deviate too much.

3 5

Virtual patron card in Koha
by Laurence Rault 09 Oct '23

09 Oct '23

Hi, Has someone already implemented a virtual patron card in Koha ? e.g. no printed card, only virtual one that patron can import in one app. Is it enough to send ACCTDETAILS with the barcode inside ? Is it possible to insert the barcode in the notice ? Thank you, Greetings, Laurence Rault -- ------------------------ Laurence Rault Responsable Pôle Développement BibLibre http://www.biblibre.com laurence.rault(a)biblibre.com p. 06 27 85 46 49

4 4

Re: [Koha] Email for suggestion book
by Toni Afandi 09 Oct '23

09 Oct '23

Yesterday, one of my patrons thanked me for the availability of the book he suggested. He got an email from the library. That meant the system worked again. Well, I did nothing for this. *Toni Afandi* *Librarian* *STT SAAT* *(Southeast Asia Bible Seminary)* Jl. Bukit Hermon No 1, Tidar Atas Malang, Jawa Timur 65151 Indonesia www.seabs.ac.id On Wed, Sep 20, 2023 at 8:03 AM Toni Afandi <toni.afandi(a)gmail.com> wrote: > Dear Katrin > > *please keep the discussion on the list.** ... **Oo.. Sorry, * > *The pref should only inform the library about new suggestions - could > this be what you are seeing? **Yes. I think so.* > > > > *Toni Afandi* > *Librarian* > *STT SAAT* > *(Southeast Asia Bible Seminary)* > Jl. Bukit Hermon No 1, Tidar Atas > Malang, Jawa Timur 65151 > Indonesia > www.seabs.ac.id > > > On Wed, Sep 20, 2023 at 3:09 AM Katrin Fischer <katrin.fischer.83(a)web.de> > wrote: > >> Hi Tony, >> >> please keep the discussion on the list. >> >> The pref should only inform the library about new suggestions - could >> this be what you are seeing? >> >> Katrin >> On 19.09.23 04:06, Toni Afandi wrote: >> >> Dear Katrin, >> >> * Did you set the SendAllEmailsTo system preference? *No* >> >> * Do you have multiple addresses in your library patrons? Maybe one being >> the library? Maybe check EmaiFieldPrimary .. *No* >> >> * Do the notices show in the notices tab of the patron? *Yes* >> >> >> Can this setting gives the unusual behaviour >> >> [image: image.png] >> >> What should I choose? >> >> Thanks, >> >> *Toni Afandi* >> *Librarian* >> *STT SAAT* >> *(Southeast Asia Bible Seminary)* >> Jl. Bukit Hermon No 1, Tidar Atas >> Malang, Jawa Timur 65151 >> Indonesia >> www.seabs.ac.id >> >> >> On Tue, Sep 19, 2023 at 1:48 AM Katrin Fischer <katrin.fischer.83(a)web.de> >> wrote: >> >>> Hi Tony, >>> >>> that sounds unusual. Some things to check: >>> >>> * Did you set the SendAllEmailsTo system preference? >>> >>> * Do you have multiple addresses in your library patrons? Maybe one >>> being the library? Maybe check EmaiFieldPrimary >>> >>> * Do the notices show in the notices tab of the patron? >>> >>> There are 2 versions each year, so there is no version 20 or 23 - the >>> last release was 23.05 in May and the next will be 23.11 in November. >>> >>> Hope this helps, >>> >>> Katrin >>> >>> On 18.09.23 10:48, Toni Afandi wrote: >>> > Dear all, >>> > >>> > After upgrading to Koha 23 from koha 20, I noticed something strange >>> about >>> > the suggestion notification email. Now I receive email when a patron >>> > suggestion is received or declined, but no to the patron who suggests. >>> So >>> > where should I set the email so they would receive it? >>> > >>> > I noticed that koha made a notification, but it is set to me not to the >>> > patrons. >>> > >>> > Thank you >>> > >>> > *Toni Afandi* >>> > *Librarian* >>> > *STT SAAT* >>> > *(Southeast Asia Bible Seminary)* >>> > Jl. Bukit Hermon No 1, Tidar Atas >>> > Malang, Jawa Timur 65151 >>> > Indonesia >>> > www.seabs.ac.id >>> > _______________________________________________ >>> > >>> > 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

The "one manual" idea
by Charillon, Aude 06 Oct '23

06 Oct '23

Hello, In the Koha Documentation team, we have been discussing whether we still need one version of the manual per Koha version. The idea being mooted is that having only one manual for all versions in the future may be better. It's an idea that is still at the exploration stage; at this point we would like to get feedback from a wider group of people, hence this message! I included further down a summary of what has been raised so far. We are particularly interested in your thoughts on the following: - What would be impacted if we decided to move to one manual - that we haven't considered yet (see summary)? What issues may arise, who would they affect, what are your suggestions to solve them? - Are there any specific considerations for translated versions of the manual? - Are there any technical considerations that us non-developers haven't thought of? If you have questions, concerns or just think it's a good idea, it would also be nice to hear from you :-) Thanks, Aude [aude_c on Koha IRC] Documentation Manager for the 23.11 cycle Issues with the current situation - The documentation cycle doesn't match the Koha development cycle. It is near impossible for the Documentation team to document all the new features before the new Koha version is released. The manual published alongside the new Koha version is always behind. - When the manual is updated, the update is made to the master branch - the one that matches the numbering of the Koha version currently in development. This master branch isn't visible (unless you know where to find it). It is possible to "backport" updates to older versions of the manual but this is not straightforward. Because we are behind with documenting features, some updates would have to go back through several older versions of the manual, making the process even less straightforward. I'll be honest: it's rare these days when we backport to older versions. - For library teams, that means the explanation of a feature in their Koha version is more likely to be in a newer version of the manual (than in the one they'll land on when clicking the Help button). One manual - why it would be beneficial - Everything in one place: all the latest additions and improvements to the manual available straight away to everyone everywhere. - Translated manuals: only one version to keep on top of. - Easier to manage by the community. How it could work; questions and concerns identified - What if something changes in a newer version of Koha / only exists in some versions but not others? Wouldn't that be confusing in one manual? We would need to clearly mark sections with the Koha versions it applies to, e.g. "until 22.11", "from 23.05". Aude Charillon Customer Services Consultant PTFS Europe aude.charillon(a)ptfs-europe.com

4 4

bulkmarcimport.pl with Record Matching Rules?
by Thomas Klausner 06 Oct '23

06 Oct '23

Hi! Is there a way to run bulkmarcimport.pl together with some Record Matching Rules (like they are available in the Staff interface via "Stage MARC records for import") ? The param "-match" seems related, but from --help I cannot figure out what this actually does.. Background: We want to import authorities from the GND/DNB (German National Libray) but do not want to create duplicate auths for those we already have in the DB. We can match the auths via 024$a (so if we have a local record with the same value in 024$a as the one we're currently importing, it's a match and should update the old record instead of creating a new one) Greetings, domm -- Thomas Klausner domm https://domm.plix.at Just another ( Perl | Postgres | Bicycle | Food | Photo | Vinyl ) Hacker A not-so-short list of things I learned at PerlKohaCon #Perl #Koha [ 2023-08-19 10:00 > https://domm.plix.at/perl/2023_08_things_i_learned_at_perlkohacon.html ] Long and good read: http://bit-player.org/2023/ai-and-the-end-of-programming [ 2023-09-14 12:01 > https://domm.plix.at/microblog.html ]

2 2