<!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 13400 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is : <br><br>Title : Koha-devel Digest, Vol 193, Issue 14<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: My dev list for 22.05 (Jonathan Druart)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Fri, 17 Dec 2021 11:33:45 +0100<br>From: Jonathan Druart <jonathan.druart@bugs.koha-community.org><br>To: "Renvoize, Martin" <martin.renvoize@ptfs-europe.com><br>Cc: David Cook <dcook@prosentient.com.au>, koha-devel<br> <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] My dev list for 22.05<br>Message-ID:<br> <CAJzKNY4ORwMAAE4agTdqQpmApXjqPwjMYGALqL-1tUxuXN8KWg@mail.gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>><br>> 1. misc4dev, I don't really have a boat in the race here.. I don't<br>> personally use it directly in any way and I'm not close enough to it to<br>> know what knock on effects it would have to help my workflows.<br>><br><br>It's used by koha-testing-docker, so you are using misc4dev daily. For<br>instance the items/biblios/authorities records you see when using ktd are<br>coming from this repo.<br><br><br>> 4. I agree with Tomas, I don't think we should be storing whole dumps,<br>> especially not twice. I would like to see a diff approach using one of the<br>> standard libraries out there.. as for what one, that's a harder call.<br>><br><br>What if we decide to change the libraries later? We could still have 2 new<br>(before/after) columns but with the diff only?<br>before { opac_note => 'a note' }<br>after { opac_note => 'modified note' }<br><br><br>> 5(1). Patron searches: My recent devs are all moving towards using the<br>> API's where possible and I try to create re-usable client side components..<br>> it's not easy with our current workflows. I'd need to look at your<br>> proposals in more depth again, but last I looked I felt we were opposed in<br>> our thoughts here?<br>><br><br>There are several things. The first one is making them all the current<br>system (15812 and 29136). Then making them all use the REST API.<br>I am sure you don't disagree with that :) What did you have in mind?<br><br><br>> 5(2). Async indexing, yup.. I'm in on this one.. and have been for a<br>> while.. just need to schedule some time to look at what the current state<br>> of affairs is.<br>><br><br>Oops, there were 2 5's!<br>It's ready for testing and QA actually, I updated the status accordingly.<br><br><br>> 7. As keen as I am to see something here, whilst things continue to work I<br>> have other higher priorities. It's taken so long to get to this stage I've<br>> forgotten the background reasons for doing it :(<br>><br><br>Repo size, from 2.4G (or 4G? I lost track) to ~200M<br><br><br>> 8. I like the idea here.. and agree it would be good to move intranet<br>> scripts into their own directory too (there's a security bug that started<br>> this long ago)<br>> 9. Translation is important and I do try to help where I can.. but as a<br>> native English speaker and one whose customers are majoritorily also native<br>> English I struggle to set enough time aside to help on these efforts.<br>> However.. I really would like to see the AV translations bugs move<br>> forward.. I find myself blocked on many things because we don't have a<br>> decent way to translate data that's in the database.<br>> 10. Add a way to prevent embedding objects that should not be allowed -<br>> This one is important to me, we need to make sure our API is secure,<br>> suitable and performant so we can push to using it more.<br>> 11. I'd love to see Koha's permissions working a little more clearly as a<br>> first step towards giving us OAuth scopes and a cleaner API<br>> authentication/authorization process.<br>> 12. I aim to continue to support the documentation team to help improve<br>> efficiencies there.<br>><br><br><br>Thanks for your reply!<br><br><br><br>> *Martin Renvoize, MPhys (Hons)*<br>><br>> <https://www.ptfs-europe.com><br>><br>> Head of Development and Community Engagement<br>><br>><br>><br>> *Phone:* +44 (0) 1483 378728<br>><br>> *Mobile:* +44 (0) 7725 985 636<br>><br>> *Email:* martin.renvoize@ptfs-europe.com<br>><br>> www.ptfs-europe.com<br>><br>><br>> *Sign up for our newsletters here <http://eepurl.com/dPjjkn> or by<br>> scanning the QR code*<br>><br>><br>><br>> Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30<br>><br>> The information contained in this email message may be privileged,<br>> confidential and protected from disclosure. If you are not the intended<br>> recipient, any dissemination, distribution or copying is strictly<br>> prohibited. If you think that you have received this email message in<br>> error, please email the sender at info@ptfs-europe.com<br>><br>><br>> On Wed, 8 Dec 2021 at 22:08, <dcook@prosentient.com.au> wrote:<br>><br>>> Hey Nick,<br>>><br>>><br>>><br>>> What do you mean by a more generic OAuth connector?<br>>><br>>><br>>><br>>> I’ve already done a lot of authentication work locally and hopefully will<br>>> do more in the community in the time to come, so happy to collaborate more<br>>> on that. (I find the hardest part of authentication work is not the code,<br>>> but rather getting community support for moving developments along, so<br>>> let’s pair up and get some AuthN work done!)<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<br>>> Behalf Of *Nick Clemens<br>>> *Sent:* Wednesday, 8 December 2021 11:37 PM<br>>> *To:* Owen Leonard <oleonard@myacpl.org><br>>> *Cc:* koha-devel <koha-devel@lists.koha-community.org><br>>> *Subject:* Re: [Koha-devel] My dev list for 22.05<br>>><br>>><br>>><br>>> Currently I am working on moving the OverDrive code into a plugin to<br>>> update for changes in their API, and to make it easier to adapt in the<br>>> future<br>>><br>>><br>>><br>>> I hope to continue working this cycle on performance in searching and<br>>> loading pages throughout Koha<br>>><br>>><br>>><br>>> ByWater at large is going to be working on improving the Koha2Koha ILL<br>>> plugin, developing a more generic OAuth connector, and other sponsored devs<br>>><br>>><br>>><br>>> Generally too, we have a number of devs in the community we would like to<br>>> complete and get into Koha.<br>>><br>>><br>>><br>>> We're happy to help where we can, please give a ping :-)<br>>><br>>><br>>><br>>><br>>><br>>> On Fri, Dec 3, 2021 at 10:51 AM Owen Leonard <oleonard@myacpl.org> wrote:<br>>><br>>> > And also, what's on your list for 22.05?<br>>><br>>> Some larger things I'm working on:<br>>><br>>> - Upgrading jQuery in the OPAC and staff client. This depends on<br>>> upgrading jQueryUI which depends on getting the last of the Flatpickr<br>>> patches in.<br>>> - Continue to replace jQueryUI widgets with alternatives, starting<br>>> with features available in Bootstrap<br>>> - Update Bootstrap in the staff client. It currently uses v.3 and<br>>> Bootstrap is currently on v.5.1. Not sure if this one is too big to<br>>> finish for 22.05!<br>>><br>>> -- Owen<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>>><br>>> Nick Clemens<br>>><br>>> ByWater Solutions<br>>><br>>> bywatersolutions.com<br>>><br>>> Phone: (888) 900-8944<br>>><br>>> Pronouns: (he/him/his)<br>>> Timezone: Eastern<br>>><br>>> Follow us:<br>>><br>>> <https://www.facebook.com/ByWaterSolutions/><br>>> <https://www.instagram.com/bywatersolutions/><br>>> <https://www.youtube.com/user/bywatersolutions><br>>> <https://twitter.com/ByWaterSolution><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>> 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>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211217/fb9bf00b/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 193, Issue 14<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>