<!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 13956 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 2<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. My dev list for 22.05 (Jonathan Druart)<br> 2. Re: My dev list for 22.05 (dcook@prosentient.com.au)<br> 3. Proofreading request of Koha's Wikipedia article release<br> history table (Victor Grousset/tuxayo)<br> 4. Re: [Changed topic] Action hooks (Marcel de Rooy)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Wed, 1 Dec 2021 12:55:44 +0100<br>From: Jonathan Druart <jonathan.druart@bugs.koha-community.org><br>To: koha-devel <koha-devel@lists.koha-community.org><br>Subject: [Koha-devel] My dev list for 22.05<br>Message-ID:<br> <CAJzKNY621YiBKdQvc2wsb1QBVjUOBa05VTkgiu6+nvdFb32F3w@mail.gmail.com><br>Content-Type: text/plain; charset="UTF-8"<br><br>Hello everybody,<br><br>I have been listing some tasks I would like to work on during the next<br>development cycle.<br>I suggest a give and take approach. Help me on one or more of those<br>topics and I will help you as I can on whichever topic(s) you decide.<br><br>1. Add more sample data to misc4dev<br>It can be sometimes painful to recreate some situations when using the<br>data provided by misc4dev. I would like to extend the data set to make<br>some patches easier to test out of the box.<br>We could, for instance, have:<br> - big records<br> - records with many items<br> - records and items with cover images<br> - more acquisition data<br> - etc?<br><br>Just tell me what kind of data you miss on a regular basis and I will<br>try to add them to misc4dev. If you have such records/data, send them<br>to me for inclusion!<br><br>2. Remove item-level_itype<br>We have been discussing this one for a long time already, is it the<br>time to tackle it down?<br>See<br> - https://lists.koha-community.org/pipermail/koha-devel/2015-December/042114.html<br> - Bug 10385 - item-level_itypes checks need to be refactored<br> - Bug 29106 - Can we get rid of Koha::Item->effective_itemtype<br><br>The work would consist in providing a plan to go ahead then provide a patch.<br><br>3. Merge biblio and biblioitem<br>Self-explanatory, merge the 2 tables to remove the unneeded 1-1<br>relation between them<br><br>4. Improve action logs<br>We have had several changes and reports in this area lately. We could<br>improve the way we log changes for easy tracking and comparaison.<br>See<br> - Bug 28714 - Bib record change tracking action log<br> - Bug 29451 - Merging records and authorities - log details for the<br>delete action so it could be recreated<br> - Bug 28692 - Reduce DB action_log table size<br><br>I think we should add 2 new columns to log before and after the object<br>is updated, serialized in JSON. We could then generate the diff on<br>display.<br><br>5. Patron searches (holds and checkouts)<br>Those two patron searches do not use the same code as the other patron searches.<br>We should uniformize them.<br> - Bug 29136 - Patron search on request.pl has performance and display issues<br> - comment 37 of Bug 15812 - Checkout search with too many results<br>(single character search) causes poor performance or timeout<br>There is also bug 29125 (Use Koha::Patron object in<br>C4:Utils::DataTables::Members.pm) that is removing the SQL query to<br>use Koha::Patrons.<br><br>5. Async ES indexation<br>Now that we have the task queue we should use it to index the records<br>and don't index them in a synchronous way.<br>Bug 27344 - Implement Elastic's update_index_background using<br>Koha::BackgroundJob<br>If we don't want to use the task queue for that purpose we should<br>provide another solution.<br>To be discussed and implemented (or validate and test the patches that<br>are already on bug 27344)<br><br>6. mailman2discourse<br>It seems that people are willing to move from our historical mailing<br>list to something more modern like discourse.<br>I would like to get back to this job, who is willing to help me?<br><br>7. Split and shrink git repo<br>I've already done several iterations in this area and I would like to<br>get back to it. However I need someone with good git knowledge to<br>continue and focus on this.<br><br>8. Move C4 and Koha to lib<br>We discussed that earlier and I even attached patches to bug 28589. I<br>don't think it's top priority but I can dedicate some hours if some of<br>you think it is a move we must do now.<br><br>9. Improve our strings for translators<br>See<br> - Bug 29602 - We must be nicer with translators<br> - Bug 20988 - [OMNIBUS] Internationalization: wrap all translatable<br>text inside t() calls<br>I had to spend some time in the PO when I was releasing 21.11, and<br>really we are not nice with translators. The %s everywhere make things<br>very hard to maintain, read and translate.<br>We should help them, and even if a big move is needed it will be a win<br>in the long term, for us (developers) and for them.<br><br>There are some other topics I have in mind, but those ones need to be<br>done in small teams as they are quite big.<br><br>Let me know what you think and if you are willing to give me a hand!<br><br>And also, what's on your list for 22.05?<br><br>Cheers,<br>Jonathan<br><br><br>------------------------------<br><br>Message: 2<br>Date: Thu, 2 Dec 2021 11:39:59 +1100<br>From: <dcook@prosentient.com.au><br>To: "'Jonathan Druart'" <jonathan.druart@bugs.koha-community.org>,<br> "'koha-devel'" <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] My dev list for 22.05<br>Message-ID: <0cff01d7e715$22f9ba80$68ed2f80$@prosentient.com.au><br>Content-Type: text/plain; charset="utf-8"<br><br>Hey Jonathan,<br><br>Thanks for reaching out.<br><br>We recently did a phpBB to Discourse move that's been live about a week now, so I'm happy to share my recent knowledge and experience for the "mailman2discourse" task. <br><br>Other than that, I'm not sure how much help I have to give. I have a small interest in "Move C4 and Koha to lib", also small interest in "Improve action logs" since I use them quite a bit (although usually from the koha-mysql CLI rather than the web UI). <br><br>--<br><br>As for my work... I haven't compiled a real list yet but...<br>- Improving authentication generally (especially modularity via 24539, maybe 28507) (will hopefully be sponsored)<br>- holds enhancements 15565 and 15516 (will hopefully be sponsored)<br>- Replacing CGI scripts with Mojolicious controllers (28325, 26791) (I doubt anyone would sponsor this, especially as core module like C4/Auth.pm and C4/Template.pm need refactoring to make this work 100% correctly, so very very unlikely to happen, which is a bit unfortunate.)<br><br>I also have a use case where I want to send Koha biblio data elsewhere on create/update/delete, but Koha plugins won't be suitable. I've been thinking that it would be good to publish a message to a RabbitMQ topic on biblio create/update/delete. In fact, that could potentially replace the existing C4::Biblio::_after_biblio_action_hooks and Koha::Item::_after_item_action_hooks functions, and then the background_jobs_worker.pl or some other work could invoke the plugins.<br><br>Currently, I'm planning to modify the C4::Biblio::_after_biblio_action_hooks and Koha::Item::_after_item_action_hooks functions to push those create/update/delete messages to RabbitMQ. I probably won't use the Koha::BackgroundJob system, since I want the integration to be loosely coupled - the custom worker will just listen to the RabbitMQ topic and that's all Koha core will have to know about it. <br><br>That's probably all for now heh.<br><br>David Cook<br>Senior Software Engineer<br>Prosentient Systems<br>Suite 7.03<br>6a Glen St<br>Milsons Point NSW 2061<br>Australia<br><br>Office: 02 9212 0899<br>Online: 02 8005 0595<br><br>-----Original Message-----<br>From: Koha-devel <koha-devel-bounces@lists.koha-community.org> On Behalf Of Jonathan Druart<br>Sent: Wednesday, 1 December 2021 10:56 PM<br>To: koha-devel <koha-devel@lists.koha-community.org><br>Subject: [Koha-devel] My dev list for 22.05<br><br>Hello everybody,<br><br>I have been listing some tasks I would like to work on during the next development cycle.<br>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.<br><br>1. Add more sample data to misc4dev<br>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.<br>We could, for instance, have:<br> - big records<br> - records with many items<br> - records and items with cover images<br> - more acquisition data<br> - etc?<br><br>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!<br><br>2. Remove item-level_itype<br>We have been discussing this one for a long time already, is it the time to tackle it down?<br>See<br> - https://lists.koha-community.org/pipermail/koha-devel/2015-December/042114.html<br> - Bug 10385 - item-level_itypes checks need to be refactored<br> - Bug 29106 - Can we get rid of Koha::Item->effective_itemtype<br><br>The work would consist in providing a plan to go ahead then provide a patch.<br><br>3. Merge biblio and biblioitem<br>Self-explanatory, merge the 2 tables to remove the unneeded 1-1 relation between them<br><br>4. Improve action logs<br>We have had several changes and reports in this area lately. We could improve the way we log changes for easy tracking and comparaison.<br>See<br> - Bug 28714 - Bib record change tracking action log<br> - Bug 29451 - Merging records and authorities - log details for the delete action so it could be recreated<br> - Bug 28692 - Reduce DB action_log table size<br><br>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.<br><br>5. Patron searches (holds and checkouts) Those two patron searches do not use the same code as the other patron searches.<br>We should uniformize them.<br> - Bug 29136 - Patron search on request.pl has performance and display issues<br> - 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<br>C4:Utils::DataTables::Members.pm) that is removing the SQL query to use Koha::Patrons.<br><br>5. Async ES indexation<br>Now that we have the task queue we should use it to index the records and don't index them in a synchronous way.<br>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.<br>To be discussed and implemented (or validate and test the patches that are already on bug 27344)<br><br>6. mailman2discourse<br>It seems that people are willing to move from our historical mailing list to something more modern like discourse.<br>I would like to get back to this job, who is willing to help me?<br><br>7. Split and shrink git repo<br>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.<br><br>8. Move C4 and Koha to lib<br>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.<br><br>9. Improve our strings for translators<br>See<br> - Bug 29602 - We must be nicer with translators<br> - 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.<br>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.<br><br>There are some other topics I have in mind, but those ones need to be done in small teams as they are quite big.<br><br>Let me know what you think and if you are willing to give me a hand!<br><br>And also, what's on your list for 22.05?<br><br>Cheers,<br>Jonathan<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/ git : https://git.koha-community.org/ bugs : https://bugs.koha-community.org/<br><br><br><br><br>------------------------------<br><br>Message: 3<br>Date: Thu, 2 Dec 2021 05:28:37 +0100<br>From: Victor Grousset/tuxayo <victor@tuxayo.net><br>To: koha-devel <koha-devel@lists.koha-community.org><br>Subject: [Koha-devel] Proofreading request of Koha's Wikipedia article<br> release history table<br>Message-ID: <1f558fa6-018f-b2ee-587e-1b16c0bfedf7@tuxayo.net><br>Content-Type: text/plain; charset=UTF-8; format=flowed<br><br>Hi :)<br><br>https://en.wikipedia.org/wiki/Koha_(software)#Releases<br>Let me know if something is wrong.<br><br>For 19.11 being oldoldoldoldstable , it's getting ridiculous but it <br>should be correct.<br>20.11 is oldoldstable<br>20.05 even though it's EOL it's now oldoldoldstable<br>So 19.11 must be oldoldoldoldstable XD<br><br>Cheers,<br><br>-- <br>Victor Grousset/tuxayo<br><br><br>------------------------------<br><br>Message: 4<br>Date: Thu, 2 Dec 2021 07:15:07 +0000<br>From: Marcel de Rooy <M.de.Rooy@rijksmuseum.nl><br>To: 'koha-devel' <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] [Changed topic] Action hooks<br>Message-ID:<br> <AM9PR05MB8436B05FA60C03D866663AFBCE699@AM9PR05MB8436.eurprd05.prod.outlook.com><br> <br>Content-Type: text/plain; charset="utf-8"<br><br>> I also have a use case where I want to send Koha biblio data elsewhere on create/update/delete, but Koha plugins won't be suitable. I've been thinking that it would be good to publish a message to a RabbitMQ topic on biblio create/update/delete. In fact, that could potentially replace the existing C4::Biblio::_after_biblio_action_hooks and Koha::Item::_after_item_action_hooks functions, and then the background_jobs_worker.pl or some other work could invoke the plugins.<br><br>I am running plugins to do the same for some time already. They are pushing these crud actions to a message queue. Works fine for me. Could you tell what makes plugins not suitable for that task?<br><br><br> <br><br>Ook in het Rijksmuseum:<br>Document Nederland 2021: Afstand. Henk Wildschut fotografeert corona<br><br><br><br>xxx<br><br>Please think before you print<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211202/8fb31af1/attachment.htm><br>-------------- next part --------------<br>A non-text attachment was scrubbed...<br>Name: image794917.jpg<br>Type: image/jpeg<br>Size: 100487 bytes<br>Desc: image794917.jpg<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211202/8fb31af1/attachment.jpg><br>-------------- next part --------------<br>A non-text attachment was scrubbed...<br>Name: image361663.png<br>Type: image/png<br>Size: 910 bytes<br>Desc: image361663.png<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211202/8fb31af1/attachment.png><br>-------------- next part --------------<br>A non-text attachment was scrubbed...<br>Name: image467923.png<br>Type: image/png<br>Size: 737 bytes<br>Desc: image467923.png<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211202/8fb31af1/attachment-0001.png><br>-------------- next part --------------<br>A non-text attachment was scrubbed...<br>Name: image371543.png<br>Type: image/png<br>Size: 799 bytes<br>Desc: image371543.png<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211202/8fb31af1/attachment-0002.png><br>-------------- next part --------------<br>A non-text attachment was scrubbed...<br>Name: image182672.png<br>Type: image/png<br>Size: 804 bytes<br>Desc: image182672.png<br>URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20211202/8fb31af1/attachment-0003.png><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 2<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>