- Koha-devel - lists.koha-community.org

Koha::Z3950Responder doesn't support authentication?
by David Cook 12 Oct '23

12 Oct '23

Hi all, Does anyone know if Koha::Z3950Responder supports authentication? As far as I know, it doesn't, so I've raised "Bug 35038 - Koha::Z3950Responder has no authentication" to flag that. Overall, I don't think I see the point of using z3950responder.pl in front of Zebra, but happy to be corrected. 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

1 0

Seeking comments on Bug 34745: ThingISBN broken
by Owen Leonard 11 Oct '23

11 Oct '23

I noticed recently that requests to LibraryThing's ThingISBN service are being blocked. Koha tries to access a url like this: https://www.librarything.com/api/thingISBN/0439139600 ...which opens fine in a browser, but triggers the response "WARNING: URL Request Failed 403 Forbidden" when Koha tries it. Koha is currently sending the user agent "libwww-perl/6.52" and if I use Firefox's developer tools to load the page with that set as a custom user agent I get a CloudFlare-generated "access denied" message. I see other CloudFlare customers complaining about this, so it may just be a default. Should we ask LibraryThing to change their configuration? Should we send a less obtrusive user agent with the request? -- Owen -- Web Developer Athens County Public Libraries (740) 737-6006 https://www.myacpl.org

3 3

Keycloak extension for using Koha as user storage backend
by David Cook 11 Oct '23

11 Oct '23

Hi all, Last year, I wrote a Keycloak extension for older Keycloak versions that uses Koha as a user storage backend. It allowed me to set up Keycloak as a shared IdP for Koha and other services, which allowed users to use their Koha credentials to log in. I'm almost finished writing an updated extension that works with the latest Keycloak 22+ (presumably Keycloak 20+ but I tested on Keycloak 22). I had to build a simple custom Docker image for Keycloak to include the extension, but I was able to get it to work in koha-testing-docker. If folk are interested in this work, I would be happy to look at sharing it. I have an increasing number of libraries who want an Identity Provider to provide SSO across Koha and other library services (like EBSCO's EDS), but they don't have an existing organisational Identity Provider. Keycloak fits well, and this extension makes it so easy for libraries and their users, since all the user management stays in Koha. 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

1 0

I suggest an update to last version of perltidy
by Zeno Tajoli 10 Oct '23

10 Oct '23

Hi all, I suggest everyone update their version of perltidy to the last one on CPAN. Why ? Because from 20230909 there is this option: Formatting a Limited Range of Lines A command --line-range-tidy=n1:n2 is available to pass just a selected range of lines to perltidy. It is quite useful with our decision on this topic: https://wiki.koha-community.org/wiki/Perltidy#Only_perltidy_modified_code Cheers Zeno Tajoli

1 0

Re: [Koha-devel] REST API and new defaults (Zeno Tajoli)
by Olli-Antti Hypernova 06 Oct '23

06 Oct '23

Good idea. Anything to disband the "SmartUI"-antipattern is good for me. We should add a new endpoint following established nomenclature. eg. PUT /biblios/123/merge/456 (PUT as it is modifying existing records) regarding b) We should separate Mojololicious from Plack, because Plack prevents the use of websockets and more advanced Mojolicious features. It is not such a biggie to implement. We can control two processes from the same koha-plack -script, so the CLI management API doesnt need to change either. On 6.10.2023 13.00, koha-devel-request(a)lists.koha-community.org wrote: > Message: 1 > Date: Fri, 6 Oct 2023 10:01:18 +0200 > From: Zeno Tajoli<ztajoli(a)gmail.com> > To: koha-devel<koha-devel(a)lists.koha-community.org> > Subject: [Koha-devel] REST API and new defaults > Message-ID: > <CACwhcG0R2BUPM+X0NSkiA4d7em2vzgyb0yuWrR-gGpx=rPOEdw(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Hi to all, > thinking about BZ 33036, the basic idea is to change a part of > ../cataloguing/merge.pl > to create a 'merge' verb inside Koha/REST/V1/Biblios.pm then use this > new verb in a new version of ./cataloguing/merge.pl > > But if we use REST inside standard scripts, I think we need to change > those defaults: > a)RESTBasicAuth: from 'Not enabled' to 'Enabled' > b)Plack as mandatory > > As I see also ERM needs those defaults > > So is it a direction to take? > > In .. ../cataloguing/merge.pl I insert a check on the environment. > > Cheers > Zeno Tajoli

3 3

REST API and new defaults
by Zeno Tajoli 06 Oct '23

06 Oct '23

Hi to all, thinking about BZ 33036, the basic idea is to change a part of ../cataloguing/merge.pl to create a 'merge' verb inside Koha/REST/V1/Biblios.pm then use this new verb in a new version of ./cataloguing/merge.pl But if we use REST inside standard scripts, I think we need to change those defaults: a)RESTBasicAuth: from 'Not enabled' to 'Enabled' b)Plack as mandatory As I see also ERM needs those defaults So is it a direction to take? In .. ../cataloguing/merge.pl I insert a check on the environment. Cheers Zeno Tajoli

1 0

ILL ISO18626 implementation to Koha
by Olli-Antti Hypernova 04 Oct '23

04 Oct '23

Top of the evening Koha! I am working on ISO18626 with Koha and have been designing how to provide that feature for Koha. The RFC so far: https://wiki.koha-community.org/wiki/ISO18626_RFC If somebody is interested in joining our ISO18626 discussion this Friday the 6th, 15:00 UTC+0, please email me for the meet.jit.si-link. We will be discussing various issues regarding how to "make it happen". Best regards, Olli-Antti Kivilahti CTO Hypernova Oy

1 0

Add a Usage Statistics module to ERM
by Field, Jonathan 03 Oct '23

03 Oct '23

Hi all, I just wanted to bring your attention to Bug 34587 which is another enhancement to the ERM module to introduce Data Providers, COUNTER and SUSHI to Koha. There is no formal test plan to this (as it is a big feature) but you can watch my video at KohaCon 23 this year which shows how all of the features work (and the workflow). It's about 30 minutes long. We have provided a permanent sandbox here - http://staff-usagestats.sandboxes.ptfs-europe.co.uk/cgi-bin/koha/erm/eusage… which we will leave live and it would be great if anyone who has an interest in this topic/feature could do some testing and feedback any comments/issues on the bug. We'd love to add it to the next version as it is of interest to many libraries. Credentials will be required for testing, please check if your organisation has access to any valid SUSHI credentials in order to test. Other details can be found at the Project Counter registry - https://registry.projectcounter.org/ All credentials are redacted in the sandbox and will not be visible to other users. In the released version, credentials will be visible in the ERM module. I'm also happy to answer any specific questions about this feature directly if anyone has any. Many thanks Jonathan -- Jonathan Field Managing Director PTFS Europe [image: Phone icon] M: +44 7919 372002 | T: +44 1483 378728 ext. 1000 [image: Email icon] jonathan.field(a)ptfs-europe.com [image: Link icon] www.ptfs-europe.com [image: Click to open Twitter] <https://twitter.com/PTFSEurope> [image: Click to open YouTube] <https://www.youtube.com/@PTFSEurope> [image: Click to open PTFS Europe webpage] <https://www.ptfs-europe.com>

1 0

Koha Community Newsletter: September 2023
by Koha Newsletter 29 Sep '23

29 Sep '23

The Koha Community Newsletter for September 2023 is here: https://koha-community.org/koha-community-newsletter-september-2023/ Many thanks to everyone who submitted articles and news to this newsletter! Please feel free to email me with any corrections or suggestions. -- Michael Kuhn Editor, Koha Community Newsletter

1 0

Re: [Koha-devel] cannot display branchname and patron category description in card layout
by Michael Hafen 26 Sep '23

26 Sep '23

I have in the past also made many customizations to Koha, but I was working in 3.2 then. After trying to port forward my customizations when there was a Koha release, I decided I needed to learn code revision control to make it easier to manage my changes. The Koha Community Wiki has a nice page on using Git for tracking code changes and making patch files: https://wiki.koha-community.org/wiki/Version_Control_Using_Git There is also a Bug Reporting Guidelines page: https://wiki.koha-community.org/wiki/Bug_Reporting_Guidelines And a Coding Guidelines page: https://wiki.koha-community.org/wiki/Coding_Guidelines That should be of interest as you continue working on Koha. To use the Bugzilla you need to have an account first, so you'll have to make one if you haven't already. Then pick the Koha project. In components there is a 'label / patron card printing' component that I think this change would fall under. The rest of the options should be fine with the defaults, just need to enter a summary and a description. Once you have the enhancement bug, you can take the bug number, as explained in the wiki page, and use that in the patch title when adding the patch to the bug. We are expected to have a test plan, which in this case is as easy as: create patron card layout with <categorycode> in one of the text fields. run a batch with that layout and see the categorycode. apply patch run a batch with that layout and see that the category description now appears Let us know if you have any more questions. On Mon, Sep 25, 2023 at 11:52 PM Zahid Iqbal <zahidiqbal.isb(a)gmail.com> wrote: > Michael i really appreciate the suggestion and your time to communicate. > but thing is that i have not use koha bugzilla. > 2. how to create an enhancement request? > 3. how can i set my code revision tracking? > 4. the PATCH how to create patch (currently using Koha 22.11.07 version) > sorry i have no experience in creating patch > > i want to learn new technologies and tools. > can you guide me the steps 2 3 4 that i have no experience. > > Currently our library is using Koha 22.11.07 version. The older version > which was version 2.2.9 and recently (4 months ago) i > have transfer data(books,patrons,circulation) from Koha 2.2.9 to Koha > 22.11.07 > i have done customization, report generation, create new modules in PHP if > not present in koha according to library needs. > > thanks and regards, > > On Mon, Sep 25, 2023 at 9:51 PM Michael Hafen <michael.hafen(a)washk12.org> > wrote: > >> I'm glad you got that figured out. >> Be aware that you will have to make that change again if that file is >> ever updated in a Koha release. I would say it's not likely, but certainly >> it can happen. >> I suggest at this point either getting that into a patch and create an >> enhancement request on the Koha Bugzilla, or set up your own code revision >> tracking to make it easier to watch that file for changes. I've done both >> for the variety of changes I've made to the code, and I recommend trying >> the enhancement request for this change. >> >> >> On Sat, Sep 23, 2023 at 1:33 AM Zahid Iqbal <zahidiqbal.isb(a)gmail.com> >> wrote: >> >>> I have completed the patron category description and it is correctly >>> showing in pdf file from patron card creator. >>> anyone that needs help for patron category description is not showing in >>> pdf please do the following. >>> In *C4/Patroncards/Lib.pm *file. >>> >>> search for line "*$get_branch = 1 if grep{$_ eq 'branchcode'} @fields;*" >>> after, add following lines >>> >>> my $get_patroncategory = 0; >>> $get_patroncategory = 1 if grep{$_ eq 'categorycode'} @fields; >>> >>> search for line "*return $borrower_attributes;*" before this line, add >>> following lines >>> >>> if ($get_patroncategory) { >>> $query = "SELECT description FROM categories WHERE categorycode >>> = ?"; >>> $sth = C4::Context->dbh->prepare($query); >>> $sth->execute($borrower_attributes->{'categorycode'}); >>> if ($sth->err) { >>> warn sprintf('Database returned the following error: %s', >>> $sth->errstr); >>> return 1; >>> } >>> $borrower_attributes->{'categorycode'} = >>> $sth->fetchrow_hashref()->{'description'}; >>> } >>> >>> >>> Thanks for the help Michael, it really helps me. At least I do not have >>> to track this file. >>> >>> >>> >>> On Fri, Sep 22, 2023 at 10:31 AM Zahid Iqbal <zahidiqbal.isb(a)gmail.com> >>> wrote: >>> >>>> Thanks Michael that will be very helpful. I will look into the code >>>> and get back to you. For now i am working on picture uploading (restrict >>>> image not more than 4KB and not more then 150 Height Width dimension) so >>>> the database does not get heavy. >>>> >>>> On Thu, Sep 21, 2023 at 9:38 PM Michael Hafen < >>>> michael.hafen(a)washk12.org> wrote: >>>> >>>>> If you are looking at the code, look at C4/Patroncards/Lib.pm in the >>>>> get_borrower_attributes() function. That's where the branchcode to >>>>> branchname conversion is handled, I figure that would be the place to do a >>>>> categorycode to category description conversion. >>>>> >>>>> On Thu, Sep 21, 2023 at 12:17 AM Zahid Iqbal <zahidiqbal.isb(a)gmail.com> >>>>> wrote: >>>>> >>>>>> thanks for the response. >>>>>> i have checked the branchcode, it is displaying correctly in patron >>>>>> card as you told. 👍 >>>>>> but i cannot find any solution for categorycode. I will still look >>>>>> into code. Maybe I will find a solution for that. >>>>>> >>>>>> On Wed, Sep 20, 2023 at 9:08 PM Michael Hafen < >>>>>> michael.hafen(a)washk12.org> wrote: >>>>>> >>>>>>> I have a layout using "<sort2>" in the text box for field 2. Looks >>>>>>> like the code will change "<branchcode>" into the library name. No such >>>>>>> luck in current code for patron category though. >>>>>>> >>>>>>> On Tue, Sep 19, 2023 at 11:17 PM Zahid Iqbal < >>>>>>> zahidiqbal.isb(a)gmail.com> wrote: >>>>>>> >>>>>>>> Hi, In koha 22.11 can someone guide to print branchname and patron >>>>>>>> category description on pdf file for patron card creator >>>>>>>> >>>>>>>> 1. print branchname not branchcode >>>>>>>> 2. print patron-category-description not categorycode >>>>>>>> >>>>>>>> >>>>>>>> what are the values i have to type in text box for field1 and >>>>>>>> field2 in patron card layout for printing branchname and >>>>>>>> patron-category-description? >>>>>>>> >>>>>>>> i am stuck with this problem and cannot find any other solution >>>>>>>> Can anyone suggest that i have to change the code or is there any >>>>>>>> other way that it can be solved? >>>>>>>> I am not an expert in coding, any help will be appreciated. >>>>>>>> >>>>>>>> Best Regards >>>>>>>> -- >>>>>>>> *Zahid Iqbal* >>>>>>>> _______________________________________________ >>>>>>>> Koha-devel mailing list >>>>>>>> Koha-devel(a)lists.koha-community.org >>>>>>>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >>>>>>>> website : https://www.koha-community.org/ >>>>>>>> git : https://git.koha-community.org/ >>>>>>>> bugs : https://bugs.koha-community.org/ >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Michael Hafen >>>>>>> Washington County School District Technology Department >>>>>>> Systems Analyst >>>>>>> >>>>>>> >>>>>> >>>>>> -- >>>>>> *Zahid* >>>>>> >>>>> >>>>> >>>>> -- >>>>> Michael Hafen >>>>> Washington County School District Technology Department >>>>> Systems Analyst >>>>> >>>>> >>>> >>>> -- >>>> *Zahid* >>>> >>> >>> >>> -- >>> *Zahid Iqbal* >>> >>> >> >> -- >> Michael Hafen >> Washington County School District Technology Department >> Systems Analyst >> >> > > -- > *Zahid Iqbal* > -- Michael Hafen Washington County School District Technology Department Systems Analyst

1 0