<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body>A new request with request id 8625 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is : <br><br>Title : Koha-devel Digest, Vol 200, Issue 12<br>Category : <br>Description : <div>Send Koha-devel mailing list submissions to<br> koha-devel@lists.koha-community.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>or, via email, send a message with subject or body 'help' to<br> koha-devel-request@lists.koha-community.org<br><br>You can reach the person managing the list at<br> koha-devel-owner@lists.koha-community.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of Koha-devel digest..."<br><br><br>Today's Topics:<br><br> 1. Re: Help needed (dcook@prosentient.com.au)<br> 2. Re: Can we set arbitrary due date via SIP2 end-point<br> (dcook@prosentient.com.au)<br> 3. QAing OpenID Connect SSO implementation (dcook@prosentient.com.au)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Mon, 11 Jul 2022 11:31:52 +1000<br>From: <dcook@prosentient.com.au><br>To: "'Tomas Cohen Arazi'" <tomascohen@gmail.com>, "'koha-devel'"<br> <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] Help needed<br>Message-ID: <046001d894c6$07823980$1686ac80$@prosentient.com.au><br>Content-Type: text/plain; charset="utf-8"<br><br>I’m away most of this week (still catching up on leave from last week), but I could look at this sometime next week if no one has time before then. <br><br> <br><br>David Cook<br><br>Senior Software Engineer<br><br>Prosentient Systems<br><br>Suite 7.03<br><br>6a Glen St<br><br>Milsons Point NSW 2061<br><br>Australia<br><br> <br><br>Office: 02 9212 0899<br><br>Online: 02 8005 0595<br><br> <br><br>From: Koha-devel <koha-devel-bounces@lists.koha-community.org> On Behalf Of Tomas Cohen Arazi<br>Sent: Saturday, 9 July 2022 10:18 AM<br>To: koha-devel <koha-devel@lists.koha-community.org><br>Subject: [Koha-devel] Help needed<br><br> <br><br>Hi all, I've been trying to track down a problem with TestBuilder tests. The are failing (almost) randomly but I narrow it down to:<br><br> <br><br>- Koha::Checkouts::Renewals<br><br>- Koha::Biblio::ItemGroup::Items<br><br><br> <br><br>I ran out of fuel today, but it would be great if some more eyes were put on this, so I can move on with pushing new stuffs with a happy test suite. This is the subset of TestBuilder.t that I'm looking at (put it in t/db_dependent/test.t):<br><br> <br><br>https://paste.koha-community.org/10864<br><br> <br><br>My feeling is TestBuilder->_should_be_fk is not working as it should (for Koha::Checkouts::Renewals) and about Koha::Biblio::ItemGroup::Items, all I can say is that the table is a linking table, pretty much like the club holds one.<br><br> <br><br>Thanks in advance and have a great weekend!<br><br> <br><br>-- <br><br>Tomás Cohen Arazi<br><br>Theke Solutions (http://theke.io <http://theke.io/> )<br>✆ +54 9351 3513384<br>GPG: B2F3C15F<br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220711/d668bf39/attachment-0001.htm><br><br>------------------------------<br><br>Message: 2<br>Date: Mon, 11 Jul 2022 11:32:39 +1000<br>From: <dcook@prosentient.com.au><br>To: "'Indranil Das Gupta'" <indradg@l2c2.co.in>, "'Koha-devel'"<br> <koha-devel@lists.koha-community.org><br>Cc: "'Kyle Hall'" <kyle@bywatersolutions.com><br>Subject: Re: [Koha-devel] Can we set arbitrary due date via SIP2<br> end-point<br>Message-ID: <046501d894c6$248dd520$6da97f60$@prosentient.com.au><br>Content-Type: text/plain; charset="utf-8"<br><br>Alas, I’d have to dig through the code to figure it out. I think Bywater do a fair bit with SIP so Kyle might know. <br><br> <br><br>David Cook<br><br>Senior Software Engineer<br><br>Prosentient Systems<br><br>Suite 7.03<br><br>6a Glen St<br><br>Milsons Point NSW 2061<br><br>Australia<br><br> <br><br>Office: 02 9212 0899<br><br>Online: 02 8005 0595<br><br> <br><br>From: Koha-devel <koha-devel-bounces@lists.koha-community.org> On Behalf Of Indranil Das Gupta<br>Sent: Sunday, 10 July 2022 5:32 PM<br>To: Koha-devel <koha-devel@lists.koha-community.org><br>Subject: [Koha-devel] Can we set arbitrary due date via SIP2 end-point<br><br> <br><br>Hi all,<br><br> <br><br>The case: Koha 21.05.x on Debian 10.12 (standard package installation). Circ rules are defined, 15 days per checkout. SIP2 is also working. The RFID vendor wants to provide options of "1 day" / "15 days" / "365 days" to any itemtype from the SC RFID kiosk (based on the fact that from Koha's checkout page we can set arbitrary due dates overriding the calendar and issuelength rules.<br><br> <br><br>This is what I have tried so far from the server CLI telnetting to port 8023:<br><br>INPUT - 11NY20220710 02583620230710 000000AOMAIN|AA1|AB22918|AC|CH|<br><br> <br><br>RESPONSE - 121NNY20220710 124122AOMAIN|AA1|AB22918|AJECOLOGICAL METHODS|AH20220725 235900|<br><br>As can be seen from AH in response it is being set at 15 days (instead of 365 days as supplied with "nb due date" in the CHECKOUT msg)<br><br> <br><br>Looking at the SIP2 code i see $overriden_duedate is going in as undef<br><br>Am I missing something OR is it how it is atm?<br><br>thanks in advance<br><br> <br><br>Indranil Das Gupta<br>L2C2 Technologies<br><br>Phone : +91-98300-20971<br><br>WWW : http://www.l2c2.co.in<br>Blog : http://blog.l2c2.co.in<br>IRC : indradg on irc://irc.freenode.net <http://irc.freenode.net> <br>Twitter : indradg<br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220711/0d0d6cde/attachment-0001.htm><br><br>------------------------------<br><br>Message: 3<br>Date: Mon, 11 Jul 2022 11:38:02 +1000<br>From: <dcook@prosentient.com.au><br>To: "'Koha-devel'" <koha-devel@lists.koha-community.org><br>Subject: [Koha-devel] QAing OpenID Connect SSO implementation<br>Message-ID: <046a01d894c6$e57c3e70$b074bb50$@prosentient.com.au><br>Content-Type: text/plain; charset="utf-8"<br><br>Hi all,<br><br> <br><br>Is there a QA person with some time to QA the OpenID Connect SSO<br>implementation at<br>https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30988? <br><br> <br><br>I'm happy to provide additional advice on how to test it using the Keycloak<br>IdP docker image, if the steps I provide at<br>https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30988#c26 aren't<br>enough. <br><br> <br><br>I'm not the patch author; Shi Yao Yang at inLibro wrote it, but I'm keen to<br>get it into core Koha. With Shibboleth/SAML and OpenID Connect, we'd have<br>the 2 major SSO authentication protocols supported in Koha. <br><br> <br><br>I've been maintaining a OpenID Connect implementation in Koha locally since<br>2014, so I'd love to be able to use the core code instead of my custom code.<br><br><br> <br><br>David Cook<br><br>Senior Software Engineer<br><br>Prosentient Systems<br><br>Suite 7.03<br><br>6a Glen St<br><br>Milsons Point NSW 2061<br><br>Australia<br><br> <br><br>Office: 02 9212 0899<br><br>Online: 02 8005 0595<br><br> <br><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20220711/f02fd54b/attachment-0001.htm><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org<br>https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>website : https://www.koha-community.org/<br>git : https://git.koha-community.org/<br>bugs : https://bugs.koha-community.org/<br><br><br>------------------------------<br><br>End of Koha-devel Digest, Vol 200, Issue 12<br>*******************************************<br></div><br><br>NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.<br></body></html>