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