<!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 13989 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 5<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 (Marcel de Rooy)<br> 2. Re: My dev list for 22.05 (Paul Poulain)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Fri, 3 Dec 2021 09:43:29 +0100<br>From: Marcel de Rooy <rooy.de.m@gmail.com><br>To: Jonathan Druart <jonathan.druart@bugs.koha-community.org><br>Cc: koha-devel <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] My dev list for 22.05<br>Message-ID:<br> <CAGv4ghYnfwCtDdf-U3+5qsk3Kq25LLBOg5H=ncVAgkXC_j=K=g@mail.gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>A first reply on the points you mention. I would like to add a few on my<br>second reply ;)<br><br>> 2. Remove item-level_itype<br>I agree. Happy to support that one.<br><br>> 3. Merge biblio and biblioitem<br>I understand that you want that. But just feeling that it might be harder<br>to swallow..<br><br>The other points are surely interesting.<br><br>Op wo 1 dec. 2021 om 16:24 schreef Jonathan Druart <<br>jonathan.druart@bugs.koha-community.org>:<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>> -<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<br>> 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<br>> searches.<br>> We should uniformize them.<br>> - Bug 29136 - Patron search on request.pl has performance and display<br>> 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>> 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/20211203/df34ad1e/attachment-0001.htm><br><br>------------------------------<br><br>Message: 2<br>Date: Fri, 3 Dec 2021 11:00:36 +0100<br>From: Paul Poulain <paul.poulain@biblibre.com><br>To: koha-devel@lists.koha-community.org<br>Subject: Re: [Koha-devel] My dev list for 22.05<br>Message-ID: <de4b1d47-d368-f43b-60e2-3850d331288f@biblibre.com><br>Content-Type: text/plain; charset=utf-8; format=flowed<br><br>Hello all,<br><br>Regarding this topic : why not also investigate the new data models that <br>will replace MARC ?<br><br>We store the data in original form (marcxml) and move to <br>biblio/biblioitems a part of the data that is useful for basic operation <br>(like getting the title and the author).<br><br>We could import different data models with the same mechanism (RDA, DC, <br>...). The biblio_metadata.format and schema fields were created with <br>this idea in mind. That would require an additional layer for <br>transforming format/schema to internal Koha and many more things, it's a <br>long term goal.<br><br>Le 01/12/2021 à 12:55, Jonathan Druart a écrit :<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>-- <br>Paul Poulain, Associé-gérant / co-owner<br>BibLibre, Services en logiciels libres pour les bibliothèques<br>BibLibre, Open Source software and services for libraries<br><br><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 5<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>