- Koha - lists.katipo.co.nz

Re: [Koha] Restrict suggestions shown on OPAC
by Zahid Iqbal 18 Oct '23

18 Oct '23

Hi, you have to *disable*/*do not allow* the AnonSuggestions in opac preferences Regards, -- *Zahid*

3 2

Koha as an identity provider
by Rupinder Singh 18 Oct '23

18 Oct '23

Hi, I am thinking I can use koha as an identity provider for other Librayr services like repository and off-campus remote access, etc. Because, In koha, we usually already have complete details of our patrons, and we also give koha login credentials to them, I was thinking if we use the borrower table from the database, and share the username and password fields for other external services. just a thought, please give your views on this possibility. Thank you Rupinder Singh

4 3

Single Item due mail
by JITHIN N 18 Oct '23

18 Oct '23

The Item due notice mail sending as individual mails to patron for each book. Is there any way to sent the details (Bibliographic Information) that are due in a single mail . With regards JITHIN N

2 3

Next Development Meeting - 18 October 2023, 12:00 UTC
by David Nind 18 Oct '23

18 Oct '23

Apologies for the late notice, it slipped between the cracks 8-( No meeting was held last week for the original scheduled meeting (11 October). However, an informal meeting was held later the same day. A meeting is now scheduled for 18 October 2023, 12:00 UTC. For information on how to attend and the agenda, see: https://wiki.koha-community.org/wiki/Development_Meeting_18_October_2023 Everyone who as available at that time is more than welcome to attend! David Nind | david(a)davidnind.com New Zealand

1 0

Re: [Koha] OAI-PMH Setup
by David Cook 18 Oct '23

18 Oct '23

Hi Joel, You don't need to give EBSCO Z39.50 access. Their front-line integration people often get this wrong. For RTAC, you can give them access to your ILS-DI API. They'll be able to give you a list of IP address ranges to add to your system preferences regarding ILS-DI access. EBSCO have done many EDS integrations with Koha, so one would've hoped they'd have a knowledge base article about it by now... David Cook Senior Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 -----Original Message----- From: Koha <koha-bounces(a)lists.katipo.co.nz> On Behalf Of koha-request(a)lists.katipo.co.nz Sent: Wednesday, October 18, 2023 10:00 AM To: koha(a)lists.katipo.co.nz Subject: Koha Digest, Vol 216, Issue 16 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. Re: Restrict suggestions shown on OPAC (Ms. Naveen Ali) 2. Re: Single Item due mail (JITHIN N) 3. Next Documentation team meeting 25 October (Charillon, Aude) 4. String freeze - 22.11.x (Blenkinsop, Matthew) 5. OAI-PMH Setup (Coehoorn, Joel) 6. Re: OAI-PMH Setup (Coehoorn, Joel) 7. Re: OAI-PMH Setup (Galen Charlton) ---------------------------------------------------------------------- Message: 1 Date: Tue, 17 Oct 2023 10:20:45 +0500 (PKT) From: "Ms. Naveen Ali" <naveen(a)neduet.edu.pk> To: Zahid Iqbal <zahidiqbal.isb(a)gmail.com>, Koha <koha(a)lists.katipo.co.nz> Subject: Re: [Koha] Restrict suggestions shown on OPAC Message-ID: <133730501.5658062.1697520045574.JavaMail.zimbra(a)neduet.edu.pk> Content-Type: text/plain; charset=utf-8 Dear Sir, Thank you for your response. I have updated this preference. Problem is still not resolved. Looking forward to support please. With best regards, Naveen Ali ITM-JE (EAKL) Inst Representative for HEC Digital Library Resources. NEDUET, Karachi. ----- Original Message ----- From: "Zahid Iqbal" <zahidiqbal.isb(a)gmail.com> To: naveen(a)neduet.edu.pk, "koha" <koha(a)lists.katipo.co.nz> Sent: Thursday, 12 October, 2023 7:30:51 PM Subject: Re: [Koha] Restrict suggestions shown on OPAC Hi, you have to disable / do not allow the AnonSuggestions in opac preferences Regards, -- Zahid ------------------------------ Message: 2 Date: Tue, 17 Oct 2023 15:22:46 +0530 From: JITHIN N <jithin984731(a)gmail.com> To: koha(a)lists.katipo.co.nz Subject: Re: [Koha] Single Item due mail Message-ID: <CAPLLyEUvEoptOA5khriUyEE6LGA3xxdDyipv8kC2Cg-X-_bZQA(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" I checked the "digest" checkbox in the messaging preference also verified in the patron page. The message of DUEDGST notice is customised as *The Following books in Due* *<<biblio.title>>Thank you,* *Librarian* But the result as below which does not have the bibliographic information(Book Titles ) *The Following books in Due* *Thank you,* *Librarian* Please Help With regards Jithin N On Sun, Oct 15, 2023 at 2:15 PM JITHIN N <jithin984731(a)gmail.com> wrote: > The Item due notice mail sending as individual mails to patron for > each book. Is there any way to sent the details (Bibliographic > Information) that are due in a single mail . > > > With regards > JITHIN N > ------------------------------ Message: 3 Date: Tue, 17 Oct 2023 13:55:17 +0100 From: "Charillon, Aude" <aude.charillon(a)ptfs-europe.com> To: Koha mailing list <koha(a)lists.katipo.co.nz> Subject: [Koha] Next Documentation team meeting 25 October Message-ID: <CAK-fTZH3L24p=U8to6yr2uUi2m8_5X05oxgyvmXGkz4nDTSYgA(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Hello, The next Koha Documentation team meeting will take place on Wednesday 25 October at 11:30 UTC (check the date and time in your timezone: https://greenwichmeantime.com/time-gadgets/event-time/share/?name=Koha%2520…) Once again, we will use the video conference tool Jitsi Meet for the discussions. Anyone with an interest in Koha Documentation is welcome to attend. The full agenda and meeting details are at: https://wiki.koha-community.org/wiki/Documentation_meeting_25_October_2023 On the agenda so far: - an update on the automated screenshots project; - latest news on the move to one Koha manual; - re-organising the Koha manual; - reviewing what we want the manual to contain and how it should appear. I look forward to seeing you there! Thanks, Aude [aude_c on Koha IRC] Documentation Manager for the 23.11 cycle PS: finding meeting times that work for everyone around the globe is impossible... That's why we are trying to alternate times and plan meetings in advance. The next next meeting on 29 November will be at 14:00 UTC (https://wiki.koha-community.org/wiki/Documentation_meeting_25_October_2023) If you have been wanting to attend but are unable because of meeting times, please contact me! Aude Charillon Customer Services Consultant PTFS Europe aude.charillon(a)ptfs-europe.com ------------------------------ Message: 4 Date: Tue, 17 Oct 2023 18:39:31 +0100 From: "Blenkinsop, Matthew" <matt.blenkinsop(a)ptfs-europe.com> To: Koha-release Team <koha-release-team(a)theke.io>, koha-translate-request(a)lists.koha-community.org, koha(a)lists.katipo.co.nz Subject: [Koha] String freeze - 22.11.x Message-ID: <CAEBU3AyiU_Nu2-=myi7+k1TrgdTgACkOasiGawdVZh+aEv_Myw(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Hi all, We are now on string freeze for 22.11.x ahead of a release planned for the middle of next week. Get translating! Kind Regards. Matt Blenkinsop Junior Software Engineer PTFS Europe [image: Phone icon] M: +44 7311382399 | T: +44 1483 378728 ext. 1020 [image: Email icon] matt.blenkinsop(a)ptfs-europe.com [image: Link icon] www.ptfs-europe.com [image: Click to open Twitter] [image: Click to open YouTube] <https://www.youtube.com/@PTFSEurope> [image: Click to open PTFS Europe webpage] ------------------------------ Message: 5 Date: Tue, 17 Oct 2023 16:19:05 -0500 From: "Coehoorn, Joel" <jcoehoorn(a)york.edu> To: koha <koha(a)lists.katipo.co.nz> Subject: [Koha] OAI-PMH Setup Message-ID: <CAMSeE4Zp7Z0_JKNWKZEPnWx7af9fnGHc_5iKrX_hJn=c4+5Vow(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" We're working with EBSCO to try to make our Koha catalog details available as part of their discovery service for our students, so search results can show our holdings along side items from places like Academic Search Premier. I can access our OAI-PMH data and see the OAI-PMH service is working in our Koha installation, and I can even find records by biblionumber. However, in order for EBSCO to ingest this information, they need to know a few things: First, they need a URL into our OPAC that can identify a record, so they can link users to our catalog. Normally I would suggest this: https://catalog.york.edu/cgi-bin/koha/opac-detail.pl?biblionumber={biblionu… But then for #2, they need to know where in the marc data to find the biblio number to complete the template for individual records. From what I can see, this item is *not included* in the marc data. Rather, it's an internal number that Koha only stores in the MySQL database. How are others handling this? *Joel Coehoorn* Director of Information Technology *York University* Office: 402-363-5603 | jcoehoorn(a)york.edu | york.edu *Please contact helpdesk(a)york.edu <helpdesk(a)york.edu> for technical assistance.* The mission of York University is to transform lives through Christ-centered education and to equip students for lifelong service to God, family, and society ------------------------------ Message: 6 Date: Tue, 17 Oct 2023 16:47:08 -0500 From: "Coehoorn, Joel" <jcoehoorn(a)york.edu> To: koha <koha(a)lists.katipo.co.nz> Subject: Re: [Koha] OAI-PMH Setup Message-ID: <CAMSeE4aTd1dS0BE335qJEZ4k80pgsVtpujqcC+Wpb3EsZj8fUg(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Part 2 We also need to give them z39.50 access to accurately show current shelving status of individual items. I believe our Koha installation is still using Zebra for this, so we should have a z39.50 service already working. I am able to handle port forwards through our external firewall without issue, but I need to know what to forward, and what kind of authentication information they will need. Any help is appreciated. *Joel Coehoorn* Director of Information Technology *York University* Office: 402-363-5603 | jcoehoorn(a)york.edu | york.edu On Tue, Oct 17, 2023 at 4:19 PM Coehoorn, Joel <jcoehoorn(a)york.edu> wrote: > We're working with EBSCO to try to make our Koha catalog details > available as part of their discovery service for our students, so > search results can show our holdings along side items from places like Academic Search Premier. > > I can access our OAI-PMH data and see the OAI-PMH service is working > in our Koha installation, and I can even find records by biblionumber. > However, in order for EBSCO to ingest this information, they need to > know a few things: > > First, they need a URL into our OPAC that can identify a record, so > they can link users to our catalog. Normally I would suggest this: > > > https://catalog.york.edu/cgi-bin/koha/opac-detail.pl?biblionumber={bib > lionumber} > > But then for #2, they need to know where in the marc data to find the > biblio number to complete the template for individual records. From > what I can see, this item is *not included* in the marc data. Rather, > it's an internal number that Koha only stores in the MySQL database. > > How are others handling this? > > *Joel Coehoorn* > Director of Information Technology > *York University* > Office: 402-363-5603 | jcoehoorn(a)york.edu | york.edu > > *Please contact helpdesk(a)york.edu <helpdesk(a)york.edu> for technical > assistance.* > > > The mission of York University is to transform lives through > Christ-centered education and to equip students for lifelong service > to God, family, and society > ------------------------------ Message: 7 Date: Tue, 17 Oct 2023 17:48:57 -0400 From: Galen Charlton <gmc(a)equinoxoli.org> To: jcoehoorn(a)york.edu Cc: koha <koha(a)lists.katipo.co.nz> Subject: Re: [Koha] OAI-PMH Setup Message-ID: <CAPLnt67cEER5fkrbaPgN+daTtNOUs7rJe1pbQgqVc-42JpqGyQ(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Hi Joel, On Tue, Oct 17, 2023 at 5:19 PM Coehoorn, Joel <jcoehoorn(a)york.edu> wrote: > But then for #2, they need to know where in the marc data to find the > biblio number to complete the template for individual records. From > what I can see, this item is *not included* in the marc data. Rather, > it's an internal number that Koha only stores in the MySQL database. > Unless your MARC frameworks are heavily customized, the Koha biblionumber can be found in the 999$c of the MARC record as retrieved from the OAI-PMH endpoint, assuming that the metadataPrefix is set to marc21 or marcxml. If the harvester is only using oai_dc, the numeric biblionumber is part of the record identifier (e.g., in your case, for OAI-PMH ID yuoai:2401, the biblionumber is 2401). Regards, Galen -- Galen Charlton Implementation and IT Manager Equinox Open Library Initiative gmc(a)equinoxOLI.org https://www.equinoxOLI.org phone: 877-OPEN-ILS (673-6457) direct: 770-709-5581 <http://evergreen-ils.org> ------------------------------ 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 216, Issue 16 *************************************

1 0

OAI-PMH Setup
by Coehoorn, Joel 17 Oct '23

17 Oct '23

We're working with EBSCO to try to make our Koha catalog details available as part of their discovery service for our students, so search results can show our holdings along side items from places like Academic Search Premier. I can access our OAI-PMH data and see the OAI-PMH service is working in our Koha installation, and I can even find records by biblionumber. However, in order for EBSCO to ingest this information, they need to know a few things: First, they need a URL into our OPAC that can identify a record, so they can link users to our catalog. Normally I would suggest this: https://catalog.york.edu/cgi-bin/koha/opac-detail.pl?biblionumber={biblionu… But then for #2, they need to know where in the marc data to find the biblio number to complete the template for individual records. From what I can see, this item is *not included* in the marc data. Rather, it's an internal number that Koha only stores in the MySQL database. How are others handling this? *Joel Coehoorn* Director of Information Technology *York University* Office: 402-363-5603 | jcoehoorn(a)york.edu | york.edu *Please contact helpdesk(a)york.edu <helpdesk(a)york.edu> for technical assistance.* The mission of York University is to transform lives through Christ-centered education and to equip students for lifelong service to God, family, and society

2 2

Next Documentation team meeting 25 October
by Charillon, Aude 17 Oct '23

17 Oct '23

Hello, The next Koha Documentation team meeting will take place on Wednesday 25 October at 11:30 UTC (check the date and time in your timezone: https://greenwichmeantime.com/time-gadgets/event-time/share/?name=Koha%2520…) Once again, we will use the video conference tool Jitsi Meet for the discussions. Anyone with an interest in Koha Documentation is welcome to attend. The full agenda and meeting details are at: https://wiki.koha-community.org/wiki/Documentation_meeting_25_October_2023 On the agenda so far: - an update on the automated screenshots project; - latest news on the move to one Koha manual; - re-organising the Koha manual; - reviewing what we want the manual to contain and how it should appear. I look forward to seeing you there! Thanks, Aude [aude_c on Koha IRC] Documentation Manager for the 23.11 cycle PS: finding meeting times that work for everyone around the globe is impossible... That's why we are trying to alternate times and plan meetings in advance. The next next meeting on 29 November will be at 14:00 UTC (https://wiki.koha-community.org/wiki/Documentation_meeting_25_October_2023) If you have been wanting to attend but are unable because of meeting times, please contact me! Aude Charillon Customer Services Consultant PTFS Europe aude.charillon(a)ptfs-europe.com

1 0

Cannot stage authority files in 22.11.
by Raymund Delahunty 15 Oct '23

15 Oct '23

We moved from 21.11 to 22.11 recently and since then attempts to stage and import authority record have failed. We are using the LC-card-number index as the matchpoint and have tried changing the normalisation rule from None to Remove spaces but the stage still fails. We can stage without matching, but when we change the matchpoint afterwards to LC-card-number (auth 010$a) we receive an Error 500. We have also had a problem with diacritics in authority searches when using Zebra and on our test server this is solved using Elasticsearch which we are testing out. But ES has not resolved our auth staging problem. Any ideas? Ray Delahunty University of the Arts London . This email and any attachments are intended solely for the addressee and may contain confidential information. If you are not the intended recipient of this email and/or its attachments you must not take any action based upon them and you must not copy or show them to anyone. Please send the email back to us and immediately and permanently delete it and its attachments. Where this email is unrelated to the business of University of the Arts London or of any of its group companies the opinions expressed in it are the opinions of the sender and do not necessarily constitute those of University of the Arts London (or the relevant group company). Where the sender's signature indicates that the email is sent on behalf of UAL Short Courses Limited the following also applies: UAL Short Courses Limited is a company registered in England and Wales under company number 02361261. Registered Office: University of the Arts London, 272 High Holborn, London WC1V 7EY

2 1

[translate] Migrate Pootle to Weblate
by Jonathan Druart 15 Oct '23

15 Oct '23

Hello everybody, If you are a translator of Koha you should read this. Pootle is dead and we should move to Weblate, which is an active and well maintained project. We have been setting up a test server to let translators see how it goes. THIS IS A TEST SERVER: none of the changes will be saved! There are some changes in how the projects are structured. We will now have 2 projects: "koha" and "koha-manual". Each will contain several "components". One component in Pootle can only track on po file, which means we need one component per po file: https://translate.test.koha-community.org/projects/koha/ shows https://snipboard.io/rtKdTS.jpg It can be a bit disturbing at first, but there is this view: https://translate.test.koha-community.org/languages/es/koha/ that shows the progress per language: https://snipboard.io/UCJ1Ky.jpg The big win are: * We should no longer get "Critical errors: Python brace placeholders" (to be confirmed) * Translation changes will be propagated between the components of a given project, and so between versions: if you modify a string for 23.05 it will also modify it for the other branches! (to be confirmed as well!) guest user (not logged in) can only make suggestions: https://translate.test.koha-community.org/ User reviewer/6Mx1&a2S$HU*1KNbzCZV can accept suggestions. You are welcome to test and provide feedback! There is still a lot of work before effectively doing the migration, but we need first to know if users/translators are happy with it! Let us know! Cheers, Jonathan PS: About the structure of the projects, I've contacted the author of Weblate: https://github.com/WeblateOrg/weblate/discussions/9556 Next version will add a mecanism to structure components within a project!

6 7

Connection timed out whenever I try a Z39.50 search
by Δημήτρης Δαλαγιώργος 14 Oct '23

14 Oct '23

Dear all, I have added several Z39.50 interfaces to my library but for some reason searching through Z39.50 no longer works; I get a connection timeout error message. Where should I start looking to remedy this? Kind regards, Dimitrios Dalagiorgos 3rd high school of Kozani Greece

3 3