- Koha - lists.katipo.co.nz

Possible Batch Permissions Modification Plug-In broken with v23.05.04
by Rudy Hinojosa 23 Oct '23

23 Oct '23

I implemented the Bywater solution Batch Permissions Modification plug in with previous versions of Koha and had no issues, until I upgraded to v23.05.04. Suddenly I started receiving client tickets stating that librarians that were not super librarians could not edit their own library items. My client is configured in a consortium style on one database. I noticed there is more granular permissions that have been added with this new release. Maybe that has possibly created a mismatch in the bitvector logic for the plug in. My temporary solution was to make the normal staff template assign super librarian roles to everyone temporarily. Has anyone come across this issue yet? -- photo Rudy E. Hinojosa CEO/President,Lightwave Library +1 737-372-7779 <tel:+1 737-372-7779> | lightwavelibrary.com <https://lightwavelibrary.com> rudy.hinojosa(a)lightwavelibrary.com <mailto:rudy.hinojosa@lightwavelibrary.com> 25101 Ronald W. Reagan Blvd #49, Georgetown TX 78633 <https://maps.google.com/?q=25101 Ronald W. Reagan Blvd #49, Georgetown TX 78633>

2 1

koha-US 2024 Officer Nominations
by BRANNON, CHRISTOPHER 23 Oct '23

23 Oct '23

To all koha-US members and the Koha community, We are pleased to announce that nominations are now open for three board member positions on the koha-US board for 2024. We are currently seeking to fill the following positions: * Vice President * Secretary * Member at Large (Unsupported) For details about these positions, please visit https://koha-us.org/about/administration/bylaws/. This is a great opportunity for folks in the Koha community to contribute, and it also looks great on your resume. As stated in the Bylaws, nominees must be members in good standing at he time of the nomination. Members that have served on the board have found it education, and very rewarding. If you have any questions, please let me know. Otherwise, if you are interested for yourself, or know of someone that is willing, and is a good fit, please fill out the nomination form at https://docs.google.com/forms/d/e/1FAIpQLScg-2WCqOOxU8u3ZmQQDzwvS1MovpbAeh_…. Sincerely, Christopher Brannon 2023 koha-US President

1 0

errors on opac log
by Paulo Neto 20 Oct '23

20 Oct '23

Hello, I am getting lots of these errors on opac log -opac-error.log- [Thu Oct 19 17:24:15.428577 2023] [cgi:error] [pid 19289] [client xxx.xxx.xxx:35920] AH01215: [Thu Oct 19 17:24:15 2023] op ac-ISBDdetail.pl: Use of uninitialized value $holdingbrtagf in string eq at /usr/share/koha/lib/C4/Biblio.pm line 755.: /us r/share/koha/opac/cgi-bin/opac/opac-ISBDdetail.pl How can i solve this ? Paulo Neto DGADR DSIGA / DPGI Tel. (+351) 21 844 2200

2 1

Loan periods
by Wagner, Alexander 20 Oct '23

20 Oct '23

Hello! Being pretty new to Koha I still struggle to get a solution for our loan periods. I understand that Koha specifies loan periods based on `item types` and `patron types` and then calculates the loan period using the circulation matrix. I also believe I have an understanding of this matrix and I also know such concepts from other ILS. However, in our library we assume that all patrons are created equal. Now, we (currently) assume that not all books (just to take one item type) are created equal. IOW in our current system we have books with a loan period of 4 weeks (usual default) while we also have books with a loan period of 3 days (being open 24/7 with self service checkout this is our `not for loan`) and others with 2 years. Currently, any patron (they are all equal) can have items with any of these loan periods. Eg. I got Peskin/Schroeder as as desktop reference for 2 years. Then go to the library during my usual working hours (10pm or so ;) and up pick Bailin/Love from the open shelves to prepare the next lecture and while I am there I spot this interesting "new piece over there" and add it to the lot not noticing that it should stay there for a week or so. (Telling our SIP terminal "you can not take this" will not work well, especially as most of our patrons would not notice the red frownie and no-one would notice the beeps at the entrance in the middle of the night.) However, till here I can model most of it by creating an item type `book` along with `desktop reference` for the first two items. I do not yet see the new items shelve (a temporary location) where items stay for a week till they move to their permanent location with a regular loan period of 4 weeks. (IOW in our current system the loan period sometimes depends on temporary locations.) Still, this requires to add a new item type for each loan period. When it comes to databases we now have a number of different loan periods, as we model them as the subscription period minus some contract dependent time to allow for cancellation (or renewal). E.g. some are subscriptions for campus (real not for loan) with some contract running a year. The next contract runs 3 years with 4 month before it's end for cancellation. Then we have individually licensed accesses ranging from a monthly or bi-monthly period to years. Those are currently checked out to the patrons who have the access and we use the reminders as notification to our patrons ("should we renew?") and the renewals as a notification to us that the contract should indeed be renewed for another period. How would I model this in Koha? Do I really create a host of item types with funny names like 1 week, 2 weeks, 3 weeks, 4 weeks, 5 weeks, 6 weeks, 7 weeks, 8 weeks, 1 month, 2 months, 3 months, 4 months, 5 months, 6 months, 7 months, 8 months, 9 months, 10 months, 11 months, 12 months, 18 months, 24 months, 30 months, 36 months, 42 months, 48 months, 54 months, 60 months, 66 months, 72 months, 78 months It looks a bit messy in cataloguing but these would also show up in the OPAC (eg. in the advanced search limiters). In our current system I just had a subfield on item level where I could specify a loan period. Do I get it right that this concept does not exist and can not be modeled in Koha? How can I get around this? How do others handle this? Maybe I need a different angle to look at it... -- Kind regards, Alexander Wagner Deutsches Elektronen-Synchrotron DESY Library and Documentation Building 01d Room OG1.444 Notkestr. 85 22607 Hamburg phone: +49-40-8998-1758 e-mail: alexander.wagner(a)desy.de

3 6

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