Send Koha-devel mailing list submissions to
koha-devel@lists.koha-community.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
or, via email, send a message with subject or body 'help' to
koha-devel-request@lists.koha-community.org
You can reach the person managing the list at
koha-devel-owner@lists.koha-community.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Koha-devel digest..."
Today's Topics:
1. Time to translate: string freeze to prepare Koha 20.11.13 has
begun (Victor Grousset/tuxayo)
2. Re: My dev list for 22.05 (Renvoize, Martin)
3. Re: My dev list for 22.05 (Marcel de Rooy)
----------------------------------------------------------------------
Message: 1
Date: Fri, 17 Dec 2021 03:25:26 +0100
From: Victor Grousset/tuxayo <victor@tuxayo.net>
To: koha-translate@lists.koha-community.org, koha-devel
<koha-devel@lists.koha-community.org>, Koha <Koha@lists.katipo.co.nz>
Subject: [Koha-devel] Time to translate: string freeze to prepare Koha
20.11.13 has begun
Message-ID: <2db98535-93cc-5165-42f8-b6f014b306f3@tuxayo.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi,
String freeze is into effect as of now for the 20.11.x maintenance branch.
This means it's the right time to head over to the translation platform:
https://translate.koha-community.org/projects/
Reminder: if you add or change a translation in version 20.11,
then you must also copy it to 21.05 and 21.11.
Otherwise your work will be lost for future versions.
Happy translating :)
--
Victor Grousset/tuxayo
------------------------------
Message: 2
Date: Fri, 17 Dec 2021 09:52:45 +0000
From: "Renvoize, Martin" <martin.renvoize@ptfs-europe.com>
To: dcook@prosentient.com.au
Cc: Nick Clemens <nick@bywatersolutions.com>, koha-devel
<koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] My dev list for 22.05
Message-ID:
<CAB7SL8BDwgryfAcO3iL+0Q_ybaQ7uN4fNsUxgLWk46icTefaGA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
I'm sorry, I've been struggling to find a moment to reply to this one.
I'm currently working through 'Bundles'. 'Bookings' and a 'Logistics
Plugin' for a new customer and they've taking up a lot of headspace and
time... I'd love to get the Bundles code into the community this cycle,
and with any luck, I'll have enough of the Bookings piece to submit early
in the new year too.
As for the rest of the cycle,
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.
2. Remove item-level_itype, I'm interested to see where this goes and can
help test.
3. Mergeing biblio and biblioitem, I'd love to see this happen.. I always
find the two tables confusing.. I can help test and QA.
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.
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?
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.
6. Looking forward to seeing the results, but not an area I have any
expertise in.. so will happily defer to others on this one.
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 :(
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.
*Martin Renvoize, MPhys (Hons)*
<https://www.ptfs-europe.com>
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/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211217/e279234e/attachment-0001.htm>
------------------------------
Message: 3
Date: Fri, 17 Dec 2021 10:28:56 +0000
From: Marcel de Rooy <M.de.Rooy@rijksmuseum.nl>
To: koha-devel <koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] My dev list for 22.05
Message-ID:
<AM9PR05MB8436FF4CD34E1E6EFA934FA6CE789@AM9PR05MB8436.eurprd05.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"
Sorry for the delay. I already responded to your points. But here are a few points from me. Note that a list like this is just like a photograph.
I need help on the following bugs (signoffs):
Without advertizing them, some even very small patches unfortunately may be in the NSO queue for months. Or totally ignored; i regularly remove code after 3 or 4 months.
28962 Koha Command- m.de.rooy@rijksmuseum.nl Need --- nor Unverified self registrations should be removed shortly 2021-10-07
28943 Koha Command- m.de.rooy@rijksmuseum.nl Need --- nor Lower the risk of accidental patron deletion by cleanup_database.pl 2021-10-11
29554 Koha Acquisit m.de.rooy@rijksmuseum.nl Need --- min neworderempty.pl may create records with biblioitems.itemtype NULL 2021-11-22
29542 Koha sec Koha m.de.rooy@rijksmuseum.nl Need --- nor User with 'catalogue' permission can view everybody's (private) virtualshelves 2021-12-03
29592 Koha Catalogi m.de.rooy@rijksmuseum.nl Need --- min Imported records should not be completed with defaultvalues 2021-12-06
29658 Koha Acquisit m.de.rooy@rijksmuseum.nl Need --- min Crash on cancelling cancelled order 2021-12-08
29673 Koha Installa m.de.rooy@rijksmuseum.nl Need --- enh Allow an English sql localization script 2021-12-10
29336 Koha Architec m.de.rooy@rijksmuseum.nl Need --- nor Some authorised_value FKs are too short 09:09:21
29314 Koha Architec m.de.rooy@rijksmuseum.nl Need --- enh Move some OpenURL code to Koha::Biblio 09:21:22
I want to submit some patches for at least these reports:
Bug 29412 - Fix uncertain years before 1000 AD in copyrightdate
=> See also 19206 Koha Architec koha-bugs@lists.koha-commun... NEW --- How should we sort 19xx when order is pubdate?
Bug 29144 - Make branches.opac_info suitable for multi language use
=> NOTE: The current status of news/HTML customizations is not very stable! It needs more attention.
=> See also: 29190 Koha OPAC koha-bugs@lists.koha-commun... NEW --- Allow cached news pages by code from opac-main
29687 Koha Architec m.de.rooy@rijksmuseum.nl ASSI --- Get rid of a few OPAC warnings Mon 13:29
And perhaps:
20570 Koha Command- m.de.rooy@rijksmuseum.nl ASSI --- Add script to complete scanned article requests 2021-07-13
28990 Koha System A koha-bugs@lists.koha-commun... NEW --- Allow changes for a configurable subset of systempreferences by superlibrarian only 2021-09-14
And a few reports from other people:
Bug 19532 Recalls for Koha
Bug 2237 / Bug 29480 Add email address as a method for generating the userid
Furthermore I want to mention patches for Two Factor Authentication. We are investigating possiblities to sponsor development on that front.
And also I wrote two security patches recently. Not listing them here.
Look at Bugzilla for the things I forgot 🙂
Marcel
________________________________
Van: Koha-devel <koha-devel-bounces@lists.koha-community.org> namens Jonathan Druart <jonathan.druart@bugs.koha-community.org>
Verzonden: woensdag 1 december 2021 12:55
Aan: koha-devel <koha-devel@lists.koha-community.org>
Onderwerp: [Koha-devel] My dev list for 22.05
Hello everybody,
I have been listing some tasks I would like to work on during the next
development cycle.
I suggest a give and take approach. Help me on one or more of those
topics and I will help you as I can on whichever topic(s) you decide.
1. Add more sample data to misc4dev
It can be sometimes painful to recreate some situations when using the
data provided by misc4dev. I would like to extend the data set to make
some patches easier to test out of the box.
We could, for instance, have:
- big records
- records with many items
- records and items with cover images
- more acquisition data
- etc?
Just tell me what kind of data you miss on a regular basis and I will
try to add them to misc4dev. If you have such records/data, send them
to me for inclusion!
2. Remove item-level_itype
We have been discussing this one for a long time already, is it the
time to tackle it down?
See
- https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.koha-community.org%2Fpipermail%2Fkoha-devel%2F2015-December%2F042114.html&data=04%7C01%7Cm.de.rooy%40rijksmuseum.nl%7Cc7b728897c38400f18ad08d9b4c18c0b%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637739566148650299%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=0xA%2BGM5kBJBvCdXsQeo7fK8xux5%2B1mrobPxgzu32lFo%3D&reserved=0
- Bug 10385 - item-level_itypes checks need to be refactored
- Bug 29106 - Can we get rid of Koha::Item->effective_itemtype
The work would consist in providing a plan to go ahead then provide a patch.
3. Merge biblio and biblioitem
Self-explanatory, merge the 2 tables to remove the unneeded 1-1
relation between them
4. Improve action logs
We have had several changes and reports in this area lately. We could
improve the way we log changes for easy tracking and comparaison.
See
- Bug 28714 - Bib record change tracking action log
- Bug 29451 - Merging records and authorities - log details for the
delete action so it could be recreated
- Bug 28692 - Reduce DB action_log table size
I think we should add 2 new columns to log before and after the object
is updated, serialized in JSON. We could then generate the diff on
display.
5. Patron searches (holds and checkouts)
Those two patron searches do not use the same code as the other patron searches.
We should uniformize them.
- Bug 29136 - Patron search on request.pl has performance and display issues
- comment 37 of Bug 15812 - Checkout search with too many results
(single character search) causes poor performance or timeout
There is also bug 29125 (Use Koha::Patron object in
C4:Utils::DataTables::Members.pm) that is removing the SQL query to
use Koha::Patrons.
5. Async ES indexation
Now that we have the task queue we should use it to index the records
and don't index them in a synchronous way.
Bug 27344 - Implement Elastic's update_index_background using
Koha::BackgroundJob
If we don't want to use the task queue for that purpose we should
provide another solution.
To be discussed and implemented (or validate and test the patches that
are already on bug 27344)
6. mailman2discourse
It seems that people are willing to move from our historical mailing
list to something more modern like discourse.
I would like to get back to this job, who is willing to help me?
7. Split and shrink git repo
I've already done several iterations in this area and I would like to
get back to it. However I need someone with good git knowledge to
continue and focus on this.
8. Move C4 and Koha to lib
We discussed that earlier and I even attached patches to bug 28589. I
don't think it's top priority but I can dedicate some hours if some of
you think it is a move we must do now.
9. Improve our strings for translators
See
- Bug 29602 - We must be nicer with translators
- Bug 20988 - [OMNIBUS] Internationalization: wrap all translatable
text inside t() calls
I had to spend some time in the PO when I was releasing 21.11, and
really we are not nice with translators. The %s everywhere make things
very hard to maintain, read and translate.
We should help them, and even if a big move is needed it will be a win
in the long term, for us (developers) and for them.
There are some other topics I have in mind, but those ones need to be
done in small teams as they are quite big.
Let me know what you think and if you are willing to give me a hand!
And also, what's on your list for 22.05?
Cheers,
Jonathan
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.koha-community.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fkoha-devel&data=04%7C01%7Cm.de.rooy%40rijksmuseum.nl%7Cc7b728897c38400f18ad08d9b4c18c0b%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637739566148650299%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=1tqT75ALoW7Hrw9FbmMVpRLbzFk0ARVlU3%2BRluSB%2Bp8%3D&reserved=0
website : https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.koha-community.org%2F&data=04%7C01%7Cm.de.rooy%40rijksmuseum.nl%7Cc7b728897c38400f18ad08d9b4c18c0b%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637739566148650299%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=WfzFBAGvS%2FO9U5BFoELXsUB%2FHk69bNAe9vDVSOJ0zuo%3D&reserved=0
git : https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.koha-community.org%2F&data=04%7C01%7Cm.de.rooy%40rijksmuseum.nl%7Cc7b728897c38400f18ad08d9b4c18c0b%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637739566148650299%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=LeSG7jiRaUcfrXnH7cEu6ynC5OyuTNPnBM89wzI2loA%3D&reserved=0
bugs : https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.koha-community.org%2F&data=04%7C01%7Cm.de.rooy%40rijksmuseum.nl%7Cc7b728897c38400f18ad08d9b4c18c0b%7C635b05eb66c748e1a94fb4b05a1b058b%7C0%7C0%7C637739566148650299%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=0PniFO9CE09li2e2aj4wA5lfoUJh28GOMLo56QBKePU%3D&reserved=0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211217/5a1eb6da/attachment.htm>
------------------------------
Subject: Digest Footer
_______________________________________________
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/
------------------------------
End of Koha-devel Digest, Vol 193, Issue 13
*******************************************