From victor at tuxayo.net Wed Dec 1 04:03:33 2021 From: victor at tuxayo.net (Victor Grousset/tuxayo) Date: Wed, 1 Dec 2021 04:03:33 +0100 Subject: [Koha-devel] Koha 20.05.18 released (last release for 20.05.x) Message-ID: <28bd7d81-22d9-6dc4-e85c-cf94204dc39a@tuxayo.net> Hello! :) The Koha Community is happy to announce the release of Koha 20.05.18 This is the last release for the 20.05.x branch, you are strongly encouraged to upgrade to later releases in order to continue to get security and bugfix support as well as translation updates. The full release notes can be found at: https://koha-community.org/koha-20-05-18-released/ Debian packages should be available shortly. Thanks to everyone involved :) Cheers, -- Victor Grousset/tuxayo From jonathan.druart at bugs.koha-community.org Wed Dec 1 12:55:44 2021 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Wed, 1 Dec 2021 12:55:44 +0100 Subject: [Koha-devel] My dev list for 22.05 Message-ID: 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://lists.koha-community.org/pipermail/koha-devel/2015-December/042114.html - 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 From dcook at prosentient.com.au Thu Dec 2 01:39:59 2021 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Thu, 2 Dec 2021 11:39:59 +1100 Subject: [Koha-devel] My dev list for 22.05 In-Reply-To: References: Message-ID: <0cff01d7e715$22f9ba80$68ed2f80$@prosentient.com.au> Hey Jonathan, Thanks for reaching out. 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. 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). -- As for my work... I haven't compiled a real list yet but... - Improving authentication generally (especially modularity via 24539, maybe 28507) (will hopefully be sponsored) - holds enhancements 15565 and 15516 (will hopefully be sponsored) - 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.) 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. 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. That's probably all for now heh. 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 -----Original Message----- From: Koha-devel On Behalf Of Jonathan Druart Sent: Wednesday, 1 December 2021 10:56 PM To: koha-devel Subject: [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://lists.koha-community.org/pipermail/koha-devel/2015-December/042114.html - 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 at 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/ From victor at tuxayo.net Thu Dec 2 05:28:37 2021 From: victor at tuxayo.net (Victor Grousset/tuxayo) Date: Thu, 2 Dec 2021 05:28:37 +0100 Subject: [Koha-devel] Proofreading request of Koha's Wikipedia article release history table Message-ID: <1f558fa6-018f-b2ee-587e-1b16c0bfedf7@tuxayo.net> Hi :) https://en.wikipedia.org/wiki/Koha_(software)#Releases Let me know if something is wrong. For 19.11 being oldoldoldoldstable , it's getting ridiculous but it should be correct. 20.11 is oldoldstable 20.05 even though it's EOL it's now oldoldoldstable So 19.11 must be oldoldoldoldstable XD Cheers, -- Victor Grousset/tuxayo From M.de.Rooy at rijksmuseum.nl Thu Dec 2 08:15:07 2021 From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy) Date: Thu, 2 Dec 2021 07:15:07 +0000 Subject: [Koha-devel] [Changed topic] Action hooks In-Reply-To: <0cff01d7e715$22f9ba80$68ed2f80$@prosentient.com.au> References: <0cff01d7e715$22f9ba80$68ed2f80$@prosentient.com.au> Message-ID: > 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. 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? ​Ook in het Rijksmuseum: ​Document Nederland 2021: Afstand. Henk Wildschut fotografeert corona ​ ​ xxx ​Please think before you print -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image794917.jpg Type: image/jpeg Size: 100487 bytes Desc: image794917.jpg URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image361663.png Type: image/png Size: 910 bytes Desc: image361663.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image467923.png Type: image/png Size: 737 bytes Desc: image467923.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image371543.png Type: image/png Size: 799 bytes Desc: image371543.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image182672.png Type: image/png Size: 804 bytes Desc: image182672.png URL: From fridolin.somers at biblibre.com Thu Dec 2 09:35:51 2021 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Wed, 1 Dec 2021 22:35:51 -1000 Subject: [Koha-devel] Koha 21.12.00 is there In-Reply-To: <949662d9-c5d3-cdaf-902b-7bb0171eed07@web.de> References: <949662d9-c5d3-cdaf-902b-7bb0171eed07@web.de> Message-ID: Hi, Here it is, my first push to master. (Look at upgrade text) I've also pushed some Passed-QA. Like promised I will work as RM each morning. A big challenge is to keep communication the community world-wide while working in UTC-10. I start by email and be on IRC when possible. Maybe we can think of some tool later. Taiga may be useful for some todo list. Bugzilla as always our main tool. As for Dev meeting, it will be for me at 5 AM. I can manage so I propose not to change for the moment. Next one is 8 December 2021, 15:00 UTC. See you there. Best regards, -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France From dcook at prosentient.com.au Thu Dec 2 23:59:24 2021 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Fri, 3 Dec 2021 09:59:24 +1100 Subject: [Koha-devel] [Changed topic] Action hooks In-Reply-To: References: <0cff01d7e715$22f9ba80$68ed2f80$@prosentient.com.au> Message-ID: <0dc101d7e7d0$400df7b0$c029e710$@prosentient.com.au> That’s cool to hear, Marcel! Happy to share my thoughts. A couple reasons I don’t want to use plugins: 1. I don’t want to turn on Koha plugins for 100+ different Koha instances around the world. a. Overall, I think the Koha plugin system is insecure, and allows library staff too much control over the system. I typically keep it disabled with only a few exceptions. (I’ve opened a few bugs and provided a few patches for improving plugin security but they haven’t gone anywhere yet on Bugzilla.) b. I also wouldn’t want library staff to potentially meddle with the plugin I install. I think this plugin is really a system plugin rather than a user plugin. It should be invisible to library staff. 2. I’d be looking to install/upgrade plugin code on 100+ different Koha instances which presents a maintenance challenge a. While I think some vendors use Ansible to do this, I’m not currently satisfied with the CLI plugin tooling for install/upgrade/downgrade/uninstall. (I’ve done some work on this as well on Bugzilla but the work hasn’t progressed and it’s dropped down my priority list.) i. Using an Ansible push also isn’t an option in some security/operational contexts. In some contexts, you provide artifacts and leave deployment/operations up to a different team b. I rather install this “system plugin” 1 time on a server rather than X times. (I think this is something some other vendors have struggled with and worked around as well.) c. I’d need to change the instance creation process to install this plugin as well. (Not the end of the world but a bit annoying and introduces more room for errors.) That said, the hooks already exist, so I can see the appeal, and I can see how they’d work well for other people, especially with fewer Koha instances to manage. I suppose it mostly comes down to control, security, and maintenance/management. Also, other systems like Dspace and Fedora write out to message queues out of the box, and it makes it easy to add integrations to them without touching the core application at all. It would be great if Koha could do the same without needing a plugin. (If it were core functionality, we could use it for indexing as well and replace the “zebraqueue”.) 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 On Behalf Of Marcel de Rooy Sent: Thursday, 2 December 2021 6:15 PM To: 'koha-devel' Subject: Re: [Koha-devel] [Changed topic] Action hooks > 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. 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? ​ ​Ook in het Rijksmuseum: ​ Document Nederland 2021: Afstand. Henk Wildschut fotografeert corona ​ ​ x x x ​Please think before you print -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 910 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 737 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 799 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.png Type: image/png Size: 804 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image007.jpg Type: image/jpeg Size: 3552 bytes Desc: not available URL: From rooy.de.m at gmail.com Fri Dec 3 09:43:29 2021 From: rooy.de.m at gmail.com (Marcel de Rooy) Date: Fri, 3 Dec 2021 09:43:29 +0100 Subject: [Koha-devel] My dev list for 22.05 In-Reply-To: References: Message-ID: A first reply on the points you mention. I would like to add a few on my second reply ;) > 2. Remove item-level_itype I agree. Happy to support that one. > 3. Merge biblio and biblioitem I understand that you want that. But just feeling that it might be harder to swallow.. The other points are surely interesting. Op wo 1 dec. 2021 om 16:24 schreef Jonathan Druart < jonathan.druart at bugs.koha-community.org>: > 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://lists.koha-community.org/pipermail/koha-devel/2015-December/042114.html > - 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 at 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: From paul.poulain at biblibre.com Fri Dec 3 11:00:36 2021 From: paul.poulain at biblibre.com (Paul Poulain) Date: Fri, 3 Dec 2021 11:00:36 +0100 Subject: [Koha-devel] My dev list for 22.05 In-Reply-To: References: Message-ID: Hello all, Regarding this topic : why not also investigate the new data models that will replace MARC ? We store the data in original form (marcxml) and move to biblio/biblioitems a part of the data that is useful for basic operation (like getting the title and the author). We could import different data models with the same mechanism (RDA, DC, ...). The biblio_metadata.format and schema fields were created with this idea in mind. That would require an additional layer for transforming format/schema to internal Koha and many more things, it's a long term goal. Le 01/12/2021 à 12:55, Jonathan Druart a écrit : > 3. Merge biblio and biblioitem > Self-explanatory, merge the 2 tables to remove the unneeded 1-1 > relation between them -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries From arthur.suzuki at biblibre.com Fri Dec 3 12:03:21 2021 From: arthur.suzuki at biblibre.com (Arthur) Date: Fri, 3 Dec 2021 12:03:21 +0100 Subject: [Koha-devel] My dev list for 22.05 In-Reply-To: References: Message-ID: <97c4ccd8-2d96-a038-09ea-a67dab1cf58e@biblibre.com> Friday's stone in the pond :) Were you thinking like what is done today for MARC / UNIMARC / NORMAC, choosing upon installation and then using one model? Or more as "mixing different data-models in one Koha"? That would need a column for storing the data model ID for each record and somewhere to store each data-model definitions (linking to the forementionned id). This looks a bit like what we do for Bokeh. Since we import records from different systems, we store the relation between a record or item and it's system of origin. We also store a mapping configuration for each system Bokeh is connected to (be it several Koha of different configuration, several ILS, ILS + online ressources, whatever combination...). On 03/12/2021 11:00, Paul Poulain wrote: > Hello all, > > Regarding this topic : why not also investigate the new data models > that will replace MARC ? > > We store the data in original form (marcxml) and move to > biblio/biblioitems a part of the data that is useful for basic > operation (like getting the title and the author). > > We could import different data models with the same mechanism (RDA, > DC, ...). The biblio_metadata.format and schema fields were created > with this idea in mind. That would require an additional layer for > transforming format/schema to internal Koha and many more things, it's > a long term goal. > > Le 01/12/2021 à 12:55, Jonathan Druart a écrit : >> 3. Merge biblio and biblioitem >> Self-explanatory, merge the 2 tables to remove the unneeded 1-1 >> relation between them > From paul.poulain at biblibre.com Fri Dec 3 15:20:11 2021 From: paul.poulain at biblibre.com (Paul Poulain) Date: Fri, 3 Dec 2021 15:20:11 +0100 Subject: [Koha-devel] My dev list for 22.05 In-Reply-To: <97c4ccd8-2d96-a038-09ea-a67dab1cf58e@biblibre.com> References: <97c4ccd8-2d96-a038-09ea-a67dab1cf58e@biblibre.com> Message-ID: Hello, Le 03/12/2021 à 12:03, Arthur a écrit : > Friday's stone in the pond :) > > Were you thinking like what is done today for MARC / UNIMARC / NORMAC, > choosing upon installation and then using one model? nope > > Or more as "mixing different data-models in one Koha"? yes -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries From tomascohen at gmail.com Fri Dec 3 15:32:28 2021 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Fri, 3 Dec 2021 11:32:28 -0300 Subject: [Koha-devel] My dev list for 22.05 In-Reply-To: References: Message-ID: El mié, 1 dic 2021 a las 12:24, Jonathan Druart (< jonathan.druart at bugs.koha-community.org>) escribió: > 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. > Great! > 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://lists.koha-community.org/pipermail/koha-devel/2015-December/042114.html > - Bug 10385 - item-level_itypes checks need to be refactored > - Bug 29106 - Can we get rid of Koha::Item->effective_itemtype > I'm in! > 3. Merge biblio and biblioitem > Self-explanatory, merge the 2 tables to remove the unneeded 1-1 > relation between them > I'm in! > 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. > ^^ this goes against the target goal for 28692. We should actually store diffs! > 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. > I'm happy to help. I suggest we explore using the API, that has pretty efficient queries (it automatically prefetches related objects, etc). > 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) > We should move both ES and Zebra indexing to the task_queue. I'm in! > 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. > We could go crazy and put all the intranet stuffs together as well :-D > And also, what's on your list for 22.05? > We need help with the ongoing discussion on https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29523 and friends. We need a performant solution and consensus on the approach, as it will impact how the API is/can be used. I would like to see the holds table merge pushed early and help is needed there. I want to move more pages into using the API, especially those using DataTables. Best regards -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From magnus at libriotech.no Fri Dec 3 15:46:56 2021 From: magnus at libriotech.no (Magnus Enger) Date: Fri, 3 Dec 2021 15:46:56 +0100 Subject: [Koha-devel] My dev list for 22.05 In-Reply-To: References: Message-ID: <99e49387-9836-5501-e0d7-929830943f97@libriotech.no> Bonjour! Den 03.12.2021 11:00, skrev Paul Poulain: > Hello all, > > Regarding this topic : why not also investigate the new data models that > will replace MARC ? > > We store the data in original form (marcxml) and move to > biblio/biblioitems a part of the data that is useful for basic operation > (like getting the title and the author). > > We could import different data models with the same mechanism (RDA, DC, > ...). The biblio_metadata.format and schema fields were created with > this idea in mind. That would require an additional layer for > transforming format/schema to internal Koha and many more things, it's a > long term goal. Yeah, that would be an awesome development! Best regards, Magnus Libriotech From oleonard at myacpl.org Fri Dec 3 16:51:04 2021 From: oleonard at myacpl.org (Owen Leonard) Date: Fri, 3 Dec 2021 10:51:04 -0500 Subject: [Koha-devel] My dev list for 22.05 In-Reply-To: References: Message-ID: > 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 From michael.hafen at washk12.org Fri Dec 3 19:13:47 2021 From: michael.hafen at washk12.org (Michael Hafen (TECH)) Date: Fri, 3 Dec 2021 11:13:47 -0700 Subject: [Koha-devel] My dev list for 22.05 In-Reply-To: References: <97c4ccd8-2d96-a038-09ea-a67dab1cf58e@biblibre.com> Message-ID: If I may throw another stone in this pond... ;) I think it would be interesting to flip the relationship between the biblio/biblioitems/items tables and the marcxml data. Using the biblio_metadata table we could store every piece of information necessary to generate marcxml from there and the biblio/biblioitems/items tables. This would make those tables authoritative. We could even go as far as not storing the marcxml, but generating it on the fly as necessary. We could take this a step farther and use the marc_*_structure tables to represent which ever model we want to support by adding a format indicator; for example specifying a set of tag/subfield rows as being for UNIMARC, and then any data coming in to or going out from Koha in that format would go from the biblio/biblioitems/items/biblio_metadata through the marc_*_structure (koha to marc mappings) to UNIMARC, or visa-versa. The biblio and item edit screens would likewise use the biblio/items/biblio_metadata tables instead of the marcxml data. This would make imports, exports, and search engine updates more complicated, as the MARC format data would have to be generated on the fly. The trade off is that everything else in Koha could become less complicated as it would all reference the biblio/items/biblio_metadata tables directly without having to decode / encode MARC in the system format. The difference in complexity is small, but it is there. In addition, all the record data would be available directly through sql without having to go through extracting data from marcxml for some things. Admittedly, this is a very extreme idea compared to how Koha works now. But it bugs me a little that we have two copies of each record ( in the biblio/items tables and in the marcxml ), and have to take care to make sure they are kept up to date with each other. Anyway, there's an idea, since we're talking about future developments and supporting data formats besides MARC. On Fri, Dec 3, 2021 at 7:20 AM Paul Poulain wrote: > Hello, > > Le 03/12/2021 à 12:03, Arthur a écrit : > > Friday's stone in the pond :) > > > > Were you thinking like what is done today for MARC / UNIMARC / NORMAC, > > choosing upon installation and then using one model? > nope > > > > Or more as "mixing different data-models in one Koha"? > yes > > -- > Paul Poulain, Associé-gérant / co-owner > BibLibre, Services en logiciels libres pour les bibliothèques > BibLibre, Open Source software and services for libraries > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -- Michael Hafen Washington County School District Technology Department Systems Analyst -------------- next part -------------- An HTML attachment was scrubbed... URL: From M.de.Rooy at rijksmuseum.nl Mon Dec 6 12:01:36 2021 From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy) Date: Mon, 6 Dec 2021 11:01:36 +0000 Subject: [Koha-devel] Ignore this test Message-ID: Just testing if these signatures did not come along now anymore 😉 Have a great day, Koha. Marcel -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Mon Dec 6 12:19:22 2021 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Mon, 6 Dec 2021 08:19:22 -0300 Subject: [Koha-devel] Ignore this test In-Reply-To: References: Message-ID: Effectively ignored. Oh, wait. El lun, 6 dic 2021 a las 8:14, Marcel de Rooy () escribió: > Just testing if these signatures did not come along now anymore 😉 > > Have a great day, Koha. > > Marcel > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From david at davidnind.com Mon Dec 6 21:39:02 2021 From: david at davidnind.com (David Nind) Date: Tue, 7 Dec 2021 09:39:02 +1300 Subject: [Koha-devel] Documentation Team - IRC meeting this week and a general update Message-ID: Hi everyone. Thanks for those volunteering to be part of the documentation team for the 22.05 release cycle - It's great to have you as part of the team! *Next IRC meeting* I've set up a meeting for the end of this week, 9 December 2021, 16:00 UTC - this will be the first documentation meeting for a while. The agenda is available at https://wiki.koha-community.org/wiki/Documentation_IRC_meeting_2021-12-09 - please add any agenda items for things you would like to discuss. I found it a bit difficult to come up with a time that accommodates most people (from Europe, Canada, USA timezones) from what I know of the time zones team members are in - if having it earlier (or later) would mean that more could make it, I'm happy to change it (as long as I actually wake up!). If this week doesn't suit, I'm happy to move it to next week (although that might clash with any KohaCon 2021 events that are on).. Please let me know if you would like the date or time changed, otherwise I will go ahead with it as it is, and we can adjust the time for future meetings. *General update* Firstly, my apologies for the lack of activity and communication for the last release cycle (21.11) - I was originally going to have plenty of time available to work on the documentation, but unfortunately it didn't work out that way. So for this cycle we have the 21.11 changes to incorporate into the manual as a starting point. To identify what documentation changes are required I have setup a spreadsheet - linked from bug 29473 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29473 I'm progressively working my way through the list - there were quite a few architecture and other changes in this release that don't affect the documentation, so it is not as bad as it first appears. I have setup the same spreadsheet for 22.05 on bug 29460 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29640 Using a spreadsheet is probably not the best way to manage release documentation tasks, but I hope this will help initially. Other things I've been working on: 1. Tidying up the Documentation Team pages on the wiki linked from https://wiki.koha-community.org/wiki/Koha_Documentation_Team 2. Setting up tasks in Bugzilla for current GitLab issues, projects, and any other tasks I can think of - hopefully I will have this finished by the time of the meeting. 3. Working on my plan to change our approach from a monolith narrative style manual, to a more more modular, topic-based approach - the first step is for me to setup a prototype so you can see what I mean, and for us decide whether this is a better (but more challenging) approach, or not (see the documentation plan for initial details of this). I've talked about this in the past, but not made much actual progress (see my last presentation about this https://drive.google.com/file/d/1TWnsuh2Vts6wJA4PyEKh2Sio0AXaSrYR/view?usp=sharing ) 4. Thinking about adding a "What's new" section - basically a more "librarian friendly" list of new features, enhancements, and things fixed - that eventually links to the updated section(s) in the manual. I've created bugzilla task https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29649 - feel free to comment on whether you think this would be a good idea, or not. Hopefully it will make it easier for Koha Community members to identify what's new in a release, and save some of the work that is repeated by support providers (or at least create a good starting point!). 5. Setup "Office hours" or drop-in session times - this is an experiment to see if it will be useful having a time where you can drop-in and ask any questions, discuss or just cjhat about any issues to do with documentation - we'll see how it goes. For details see https://wiki.koha-community.org/wiki/Documentation_Team_-_Office_hours That's probably enough for this update - I intend to do a weekly (or perhaps fortnightly) update during the 22.05 release cycle, so let me know if this will be useful and anything you would like to see covered or included. David Nind | david at davidnind.com 387 Whartons Road, RD 10D, Oamaru 9492 p. +64 3 4395 306 | m. +64 21 0537 847 -------------- next part -------------- An HTML attachment was scrubbed... URL: From fridolin.somers at biblibre.com Tue Dec 7 09:34:21 2021 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Mon, 6 Dec 2021 22:34:21 -1000 Subject: [Koha-devel] Next dev meeting 8 dec Message-ID: Hi, Dev meeting in coming soon : 8 December 2021, 15:00 UTC https://wiki.koha-community.org/wiki/Development_IRC_meeting_8_December_2021 I've written a few points, I hope we will be productive. Like I said, schedule has not changed even if for Pacific users is will be really early in the morning. I'll have a litre of coffee to keep me awake :D Best regards, -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France From nick at bywatersolutions.com Wed Dec 8 13:37:27 2021 From: nick at bywatersolutions.com (Nick Clemens) Date: Wed, 8 Dec 2021 07:37:27 -0500 Subject: [Koha-devel] My dev list for 22.05 In-Reply-To: References: Message-ID: 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 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 at 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: -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Wed Dec 8 23:08:11 2021 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Thu, 9 Dec 2021 09:08:11 +1100 Subject: [Koha-devel] My dev list for 22.05 In-Reply-To: References: Message-ID: <01e901d7ec80$170f59d0$452e0d70$@prosentient.com.au> 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 On Behalf Of Nick Clemens Sent: Wednesday, 8 December 2021 11:37 PM To: Owen Leonard Cc: koha-devel 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 > 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 at 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: -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Thu Dec 9 06:55:27 2021 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Thu, 9 Dec 2021 16:55:27 +1100 Subject: [Koha-devel] [Changed topic] Action hooks In-Reply-To: <0dc101d7e7d0$400df7b0$c029e710$@prosentient.com.au> References: <0cff01d7e715$22f9ba80$68ed2f80$@prosentient.com.au> <0dc101d7e7d0$400df7b0$c029e710$@prosentient.com.au> Message-ID: <024b01d7ecc1$5e004c00$1a00e400$@prosentient.com.au> I’ve been thinking about this more today, and I think that I’m coming around to the plugin idea. I still think it would be a good idea to have an event-driven messaging system, but it seems to me that adding that system will take a lot more work/discussion/thinking/experimenting than just improving plugin security and plugin tooling… so I might return to looking at some of the following: Bug 28499 - Add support for no-UI / administrative plugins https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28499 Bug 25672 - Administrators should be able to disable client-side plugin upload https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25672 Bug 25370 - Create allowlist of plugins allowed to be installed by Web UI https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25370 Bug 24632 - Plugins should support simple signing for security/verifiability https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24632 Bug 25671 - Install 1 Koha plugin for X Koha instances using the CLI https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25671 Bug 28498 - Add CLI counterpart for plugin actions https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28498 At the moment, I’m more concerned with security than logistics I think. I think the most feasible option with the least amount of work is probably going to be Bug 25370. I’ll default to allowing all plugins to be loaded, and then locally I’ll just make sure that all instances have a restricted list. That should make everyone happy… 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 On Behalf Of dcook at prosentient.com.au Sent: Friday, 3 December 2021 9:59 AM To: 'Marcel de Rooy' ; 'koha-devel' Subject: Re: [Koha-devel] [Changed topic] Action hooks That’s cool to hear, Marcel! Happy to share my thoughts. A couple reasons I don’t want to use plugins: 1. I don’t want to turn on Koha plugins for 100+ different Koha instances around the world. a. Overall, I think the Koha plugin system is insecure, and allows library staff too much control over the system. I typically keep it disabled with only a few exceptions. (I’ve opened a few bugs and provided a few patches for improving plugin security but they haven’t gone anywhere yet on Bugzilla.) b. I also wouldn’t want library staff to potentially meddle with the plugin I install. I think this plugin is really a system plugin rather than a user plugin. It should be invisible to library staff. 2. I’d be looking to install/upgrade plugin code on 100+ different Koha instances which presents a maintenance challenge a. While I think some vendors use Ansible to do this, I’m not currently satisfied with the CLI plugin tooling for install/upgrade/downgrade/uninstall. (I’ve done some work on this as well on Bugzilla but the work hasn’t progressed and it’s dropped down my priority list.) i. Using an Ansible push also isn’t an option in some security/operational contexts. In some contexts, you provide artifacts and leave deployment/operations up to a different team b. I rather install this “system plugin” 1 time on a server rather than X times. (I think this is something some other vendors have struggled with and worked around as well.) c. I’d need to change the instance creation process to install this plugin as well. (Not the end of the world but a bit annoying and introduces more room for errors.) That said, the hooks already exist, so I can see the appeal, and I can see how they’d work well for other people, especially with fewer Koha instances to manage. I suppose it mostly comes down to control, security, and maintenance/management. Also, other systems like Dspace and Fedora write out to message queues out of the box, and it makes it easy to add integrations to them without touching the core application at all. It would be great if Koha could do the same without needing a plugin. (If it were core functionality, we could use it for indexing as well and replace the “zebraqueue”.) 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 > On Behalf Of Marcel de Rooy Sent: Thursday, 2 December 2021 6:15 PM To: 'koha-devel' > Subject: Re: [Koha-devel] [Changed topic] Action hooks > 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. 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? ​ ​Ook in het Rijksmuseum: ​ Document Nederland 2021: Afstand. Henk Wildschut fotografeert corona ​ ​ x x x ​Please think before you print -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 3552 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 910 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 737 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 799 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 804 bytes Desc: not available URL: From mik at adminkuhn.ch Mon Dec 13 10:15:17 2021 From: mik at adminkuhn.ch (Michael Kuhn) Date: Mon, 13 Dec 2021 10:15:17 +0100 Subject: [Koha-devel] Call for news - Newsletter December 2021 Message-ID: <0f70411a-7343-77de-f237-1937523c9a86@adminkuhn.ch> Hi I'm collecting news for the December 2021 Koha Community Newsletter. Please send anything noteworthy to: kohanews (at) gmail (dot) com News criteria: * News items can be of any length. * Images are fine. * Anything and everything Koha. * Submit by the 26th of the month. Text format criteria: * Just structured plain text, or * HTML text to include tables or similar For events: * Consider adding your event to the Koha Community calendar at https://koha-community.org/calendar/ Thank you! Michael Kuhn Editor, Koha Community Newsletter -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik at adminkuhn.ch · W www.adminkuhn.ch From paul.poulain at biblibre.com Mon Dec 13 16:11:05 2021 From: paul.poulain at biblibre.com (Paul Poulain) Date: Mon, 13 Dec 2021 16:11:05 +0100 Subject: [Koha-devel] Relooking staff interface (BibLibre sponsoring) Message-ID: Hello all, The staff interface design is something like 8 years old. It's worth being refreshed. We'd like to sponsor that work, with the idea to have a 22.05 beautiful and modern. With this idea in mind, we are planning to start (in january) a small group, with a designer we have hired. the goal of the group will be to define the global ideas/change we want to implement. Then, our designer will do a "UI kit" proposal. Then (starting in February), we have hired an internship to implement the proposal. Owen is happy to participate, who else would like to join us ? (our meetings will be made through BibLibre bigbluebutton instance, and recorded. Afternoon in Europe, morning in US East coast) Drop me an email -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries From jonathan.druart at bugs.koha-community.org Mon Dec 13 16:27:38 2021 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Mon, 13 Dec 2021 16:27:38 +0100 Subject: [Koha-devel] Relooking staff interface (BibLibre sponsoring) In-Reply-To: References: Message-ID: Great news! Should we ask end users for feedback, on the list for instance? We could also open an online form with questions. Le lun. 13 déc. 2021 à 16:11, Paul Poulain a écrit : > > Hello all, > > The staff interface design is something like 8 years old. It's worth > being refreshed. > > We'd like to sponsor that work, with the idea to have a 22.05 beautiful > and modern. > > With this idea in mind, we are planning to start (in january) a small > group, with a designer we have hired. the goal of the group will be to > define the global ideas/change we want to implement. Then, our designer > will do a "UI kit" proposal. > > Then (starting in February), we have hired an internship to implement > the proposal. > > Owen is happy to participate, who else would like to join us ? (our > meetings will be made through BibLibre bigbluebutton instance, and > recorded. Afternoon in Europe, morning in US East coast) > > Drop me an email > > -- > Paul Poulain, Associé-gérant / co-owner > BibLibre, Services en logiciels libres pour les bibliothèques > BibLibre, Open Source software and services for libraries > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ From dcook at prosentient.com.au Thu Dec 16 01:45:10 2021 From: dcook at prosentient.com.au (dcook at prosentient.com.au) Date: Thu, 16 Dec 2021 11:45:10 +1100 Subject: [Koha-devel] Relooking staff interface (BibLibre sponsoring) In-Reply-To: References: Message-ID: <001101d7f216$2dced150$896c73f0$@prosentient.com.au> This sounds awesome. I don't think that I'll be able to join the group due to timezone issues at a minimum, but happy to offer ideas/feedback or test things from time to time. 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 -----Original Message----- From: Koha-devel On Behalf Of Paul Poulain Sent: Tuesday, 14 December 2021 2:11 AM To: koha-devel Subject: [Koha-devel] Relooking staff interface (BibLibre sponsoring) Hello all, The staff interface design is something like 8 years old. It's worth being refreshed. We'd like to sponsor that work, with the idea to have a 22.05 beautiful and modern. With this idea in mind, we are planning to start (in january) a small group, with a designer we have hired. the goal of the group will be to define the global ideas/change we want to implement. Then, our designer will do a "UI kit" proposal. Then (starting in February), we have hired an internship to implement the proposal. Owen is happy to participate, who else would like to join us ? (our meetings will be made through BibLibre bigbluebutton instance, and recorded. Afternoon in Europe, morning in US East coast) Drop me an email -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries _______________________________________________ Koha-devel mailing list Koha-devel at 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/ From victor at tuxayo.net Fri Dec 17 03:25:26 2021 From: victor at tuxayo.net (Victor Grousset/tuxayo) Date: Fri, 17 Dec 2021 03:25:26 +0100 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> 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 From martin.renvoize at ptfs-europe.com Fri Dec 17 10:52:45 2021 From: martin.renvoize at ptfs-europe.com (Renvoize, Martin) Date: Fri, 17 Dec 2021 09:52:45 +0000 Subject: [Koha-devel] My dev list for 22.05 In-Reply-To: <01e901d7ec80$170f59d0$452e0d70$@prosentient.com.au> References: <01e901d7ec80$170f59d0$452e0d70$@prosentient.com.au> Message-ID: 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)* Head of Development and Community Engagement *Phone:* +44 (0) 1483 378728 *Mobile:* +44 (0) 7725 985 636 *Email:* martin.renvoize at ptfs-europe.com www.ptfs-europe.com *Sign up for our newsletters here 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 at ptfs-europe.com On Wed, 8 Dec 2021 at 22:08, 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 *On > Behalf Of *Nick Clemens > *Sent:* Wednesday, 8 December 2021 11:37 PM > *To:* Owen Leonard > *Cc:* koha-devel > *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 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 at 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: > > > > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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: From M.de.Rooy at rijksmuseum.nl Fri Dec 17 11:28:56 2021 From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy) Date: Fri, 17 Dec 2021 10:28:56 +0000 Subject: [Koha-devel] My dev list for 22.05 In-Reply-To: References: Message-ID: 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 at rijksmuseum.nl Need --- nor Unverified self registrations should be removed shortly 2021-10-07 28943 Koha Command- m.de.rooy at rijksmuseum.nl Need --- nor Lower the risk of accidental patron deletion by cleanup_database.pl 2021-10-11 29554 Koha Acquisit m.de.rooy at rijksmuseum.nl Need --- min neworderempty.pl may create records with biblioitems.itemtype NULL 2021-11-22 29542 Koha sec Koha m.de.rooy at rijksmuseum.nl Need --- nor User with 'catalogue' permission can view everybody's (private) virtualshelves 2021-12-03 29592 Koha Catalogi m.de.rooy at rijksmuseum.nl Need --- min Imported records should not be completed with defaultvalues 2021-12-06 29658 Koha Acquisit m.de.rooy at rijksmuseum.nl Need --- min Crash on cancelling cancelled order 2021-12-08 29673 Koha Installa m.de.rooy at rijksmuseum.nl Need --- enh Allow an English sql localization script 2021-12-10 29336 Koha Architec m.de.rooy at rijksmuseum.nl Need --- nor Some authorised_value FKs are too short 09:09:21 29314 Koha Architec m.de.rooy at 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 at 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 at lists.koha-commun... NEW --- Allow cached news pages by code from opac-main 29687 Koha Architec m.de.rooy at rijksmuseum.nl ASSI --- Get rid of a few OPAC warnings Mon 13:29 And perhaps: 20570 Koha Command- m.de.rooy at rijksmuseum.nl ASSI --- Add script to complete scanned article requests 2021-07-13 28990 Koha System A koha-bugs at 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 namens Jonathan Druart Verzonden: woensdag 1 december 2021 12:55 Aan: koha-devel 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 at 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: From jonathan.druart at bugs.koha-community.org Fri Dec 17 11:33:45 2021 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Fri, 17 Dec 2021 11:33:45 +0100 Subject: [Koha-devel] My dev list for 22.05 In-Reply-To: References: <01e901d7ec80$170f59d0$452e0d70$@prosentient.com.au> Message-ID: > > 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 at ptfs-europe.com > > www.ptfs-europe.com > > > *Sign up for our newsletters here 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 at ptfs-europe.com > > > On Wed, 8 Dec 2021 at 22:08, 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 *On >> Behalf Of *Nick Clemens >> *Sent:* Wednesday, 8 December 2021 11:37 PM >> *To:* Owen Leonard >> *Cc:* koha-devel >> *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 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 at 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: >> >> >> >> >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at 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 at 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: From katrin.fischer.83 at web.de Fri Dec 17 23:42:04 2021 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Fri, 17 Dec 2021 23:42:04 +0100 Subject: [Koha-devel] Relooking staff interface (BibLibre sponsoring) In-Reply-To: References: Message-ID: <4c8a9617-7377-75c8-d766-27931bf13bb6@web.de> +1 I think some early feedback loops with the wider community would be great. Sadly I won't have the time to participate in the group beginning of the next year, but really looking forward to see what you come up with! Katrin On 13.12.21 16:27, Jonathan Druart wrote: > Great news! > Should we ask end users for feedback, on the list for instance? > We could also open an online form with questions > Le lun. 13 déc. 2021 à 16:11, Paul Poulain a écrit : >> Hello all, >> >> The staff interface design is something like 8 years old. It's worth >> being refreshed. >> >> We'd like to sponsor that work, with the idea to have a 22.05 beautiful >> and modern. >> >> With this idea in mind, we are planning to start (in january) a small >> group, with a designer we have hired. the goal of the group will be to >> define the global ideas/change we want to implement. Then, our designer >> will do a "UI kit" proposal. >> >> Then (starting in February), we have hired an internship to implement >> the proposal. >> >> Owen is happy to participate, who else would like to join us ? (our >> meetings will be made through BibLibre bigbluebutton instance, and >> recorded. Afternoon in Europe, morning in US East coast) >> >> Drop me an email >> >> -- >> Paul Poulain, Associé-gérant / co-owner >> BibLibre, Services en logiciels libres pour les bibliothèques >> BibLibre, Open Source software and services for libraries >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at 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 at 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/ From tomascohen at gmail.com Sat Dec 18 21:28:12 2021 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Sat, 18 Dec 2021 17:28:12 -0300 Subject: [Koha-devel] Relooking staff interface (BibLibre sponsoring) In-Reply-To: References: Message-ID: This is great! Community involvement will be key to reach the release! El lun., 13 dic. 2021 12:11, Paul Poulain escribió: > Hello all, > > The staff interface design is something like 8 years old. It's worth > being refreshed. > > We'd like to sponsor that work, with the idea to have a 22.05 beautiful > and modern. > > With this idea in mind, we are planning to start (in january) a small > group, with a designer we have hired. the goal of the group will be to > define the global ideas/change we want to implement. Then, our designer > will do a "UI kit" proposal. > > Then (starting in February), we have hired an internship to implement > the proposal. > > Owen is happy to participate, who else would like to join us ? (our > meetings will be made through BibLibre bigbluebutton instance, and > recorded. Afternoon in Europe, morning in US East coast) > > Drop me an email > > -- > Paul Poulain, Associé-gérant / co-owner > BibLibre, Services en logiciels libres pour les bibliothèques > BibLibre, Open Source software and services for libraries > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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: From libsolisb at gmail.com Sun Dec 19 19:33:12 2021 From: libsolisb at gmail.com (FullStack Solutions) Date: Sun, 19 Dec 2021 23:33:12 +0500 Subject: [Koha-devel] Brief Report on KohaCon2021 International Conference held at National Library of Pakistan Message-ID: *Dear International Koha Community * KohaCon2021 International Conference is being held at the National Library of Pakistan from 13 to 18 December 2021. KohaCon is a yearly get together of the Koha Community. The first Koha Conference was held in Paris, France in 2006. This year, with the efforts of the Pakistani Koha Community (especially of its President, Mr. Sher Afzal Khan), Pakistan was voted to host the International Koha Conference. This is a moment of great pride for all Pakistanis, especially for Library Science professionals and academia, as it will not only improve the soft image of Pakistan, but it will also establish its credentials as a leader of the Free Open Source Software (FOSS) movement in the world. The inaugural session started on 13th December with the Recitation of the Holy Quran and National Anthem of Pakistan. The KohaCon2021, being held Hybridly, was attended by a large number of delegates from all over Pakistan and from around the world physically as well as through online mode. Mr. Zakria Qasmi, the Session Secretary, compared the whole event. Mr. Mudassar Mushtaq, the Director Genera*l* of the National Library of Pakistan (NLP), welcomed the delegates and briefed them about the NLP. Thereafter, Mr. Sher Afzal Khan, the Conference Secretary, briefed about the importance of FOSSs, especially Koha, and its pivotal role in modernizing the libraries around the world, especially in the resource constrained developing world. He said that the main purposes of these annual international KohaCons are exchanging experiences in new functionalities; training and bug squashing; promoting collaboration to enhance the use of open source integrated library system (ILS) Koha; and to encourage new developments in Koha. He also said that these conferences play a vital role to enhance regional, national and international cooperation in respect of knowledge and resource sharing. Afterwards, a recorded address of the Conference Chair, Prof. Dr. Khalid Mahmood (Dean, Faculty of Information and Media Studies, University of the Punjab, Lahore), was played. He also welcomed the delegates and paid tribute to Mr. Sher Afzal Khan for his tireless efforts in promoting Koha, us, saving millions of rupees that would have been needed to purchase commercial software. He also lauded his efforts to bring KohaCon2021 to Pakistan which will enhance our country’s image and standing in the world. Then, Chief Guest of the inaugural session, Honourable Ali Muhammad Khan (Minister of State for Parliamentary Affairs, Government of Pakistan), addressed the delegates. He stressed the need to take libraries to the users, especially to the youth, using ICT tools. He summed up his address in a point that “readers are leaders”, by giving his own example and sharing his experiences of libraries. More than 20 national and international researchers, practitioners, academicians, and Library & Information Science professionals presented their research papers; and shared their experiences regarding Koha during the conference. Around 200 people, including Library & Information Science professionals, IT professionals, educationists, dignitaries; and representatives from more than 18 countries including USA, Canada, India, Turkey, Philippines, Saudi Arabia, Nepal, Sri Lanka, New Zealand, Bangladesh and Cypress, participated in this conference. The closing session of the conference on 15th December also started with the recitation of the Holy Quran by Mr. Zakria Qasmi. The conference report was presented by Mr. Sher Afzal Khan. Thereafter, the guest of honor of the session Mr. Nasir Jamal Khan (Chief Operating Officer, COMSATS Internet Services) announced pro-bono provision of the internet as a gift to the NLP. Engr. Qaiser Nawab, Founder and Chief Executive Officer of “THE '' Society International - Together of Health and Education has participated as a Guest of Honour in the closing ceremony of the 1st ever International Conference “Kohacon21'' with a theme of Digitization of libraries in the developing world happened in Islamabad, Pakistan. In his address, Mr. Nawab urged the youth to take active part in readership for effective leadership to bring sustainability in the world. Today's world is a world of information and knowledge, therefore the young people must equip themselves with modern digital learning tools and open source technologies. Open Source applications provide easy access to the sources of knowledge. He added . Afterwards, Dr. Khalid Mahmood, the conference chair, candidly talked about the history of library automation in Pakistan, especially his own experiences, and the contributions made by Ms. Bushra Almas Jaswal (renowned and seasoned library professional of Pakistan) who was also present as a delegate. He, again, lauded the efforts of Mr. Sher Afzal Khan, and lluded him to Koha which is open source, freely accessible and always ready to help others. Thereafter, the chief guest of the closing session, Honourable Shandana Gulzar Khan (Member of the National Assembly of Pakistan & Chairperson of Commonwealth Women Parliamentarians) addressed the delegates. She also stressed the need to bring libraries to users, especially to women and to the people of far flung areas who cannot access physical libraries. She not only congratulated Mr. Sher Afzal Khan and the organizers of KohaCon2021, but also showed her surprise that such an international event is being organized by a few individuals without any financial support by the government of Pakistan. Then, Mr. Javed Iqbal (Deputy Director, NLP) briefed about the NLP, and talked about the demand of library users to make the NLP a 24/7 library which can be fulfilled if adequate funds and human resources can be provided by the government to the NLP. He also invited all the delegates to visit the NLP and explore its collections. The three-day conference concluded after shields to the guests, organizers, and the delegates. Mr. Sher Afzal Khan the organizer of the conference shared the details of the sessions and highlighted the outcomes of the conference. Mr. Nasir Jamal Khan COO, COMSATS Internet Services during his speech appreciated the organizers and announced to provide complimentary internet service to the National Library of Pakistan. In the end, certificates and shields were distributed among the participants of the conference and a group photograph was taken outside the library building. A two day Hackfest also held as part of KohaCon2021 from 16 to 17 December. The 1 and 2d day was observed as Heckfest day and the two days’ sessions were held at the computer lab of National Library. Different participants of the Kohacon2021 participated in both days. Mr Sher Afzal, President Koha Pakistan and conference chief organizer guided and trained all the participants about the Heackfest. The Koha Wikis, Librarian page, Koha Manuals, Koha translation, Koha newsletter, Bugzilla was introduced and guided with all of the Participants. We are very much thankful to all our sponsors especially Catalyst New Zealand for their great contribution and making this event successful. We are also very much thankful to the organizers , Participants, HODs, LIS community , Guest, Chief Guest and Guest of Honor for participants in the International Conference. The last day of the KohaCon2021 was celebrated as Cultural day but due to the extraordinary moment of the OIC conference in the capital the Cultural day was postponed, however the participants visited and explored the world's second most beautiful capital by their own arrangement. *For complete pictures, information, and other details please visit the following links: * *Conference website*: https://kohacon2021.org/ *Conference Blogs:* https://blog.fullstack.com.pk/international-conference-kohacon-2021/ *Facebook Group page ink:* https://www.facebook.com/groups/965873873493081 *Facebook page: Koha Pakistan Community:* https://www.facebook.com/kohacon20pk *Twitter link:* https://twitter.com/KohaPakistan *YouTube Link: *https://www.youtube.com/channel/UCD4OZY1NBKPwzUtqqtjy0Kg (All Lectures, PPT will be upload Soon) *Best Regards * *Sher Afzal Khan | President Koha Pakistan| Lead Consultant* *HEC & NUST Approved trainer * *Pioneer Country Ambassador DSpace MIT USA| Successfully done 50 + Modern libraries projects* *Web: www. Kohapaksitan.org | Email: kohapaksitan at gmail.com * *http://fullstack.com.pk/ | http://blog.fullstack.com.pk/ * -------------- next part -------------- An HTML attachment was scrubbed... URL: From wainuiwitikapark at catalyst.net.nz Mon Dec 20 03:52:18 2021 From: wainuiwitikapark at catalyst.net.nz (Wainui Witika-Park) Date: Mon, 20 Dec 2021 15:52:18 +1300 Subject: [Koha-devel] Time to translate: string freeze to prepare Koha 19.11.24 has begun Message-ID: <0b8d6000-7bf9-1701-e525-f3bbac0c5e13@catalyst.net.nz> Hello, String freeze is into effect as of now for the 19.11.x maintenance branch in preparation for the 19.11.24 release. This means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Wainui Witika-Park (she/her) From victor at tuxayo.net Fri Dec 24 16:11:08 2021 From: victor at tuxayo.net (Victor Grousset/tuxayo) Date: Fri, 24 Dec 2021 16:11:08 +0100 Subject: [Koha-devel] Koha 20.11.13 released Message-ID: Hello! :) The Koha Community is happy to announce the release of Koha 20.11.13 The full release notes can be found at: https://koha-community.org/koha-20-11-13-released/ Debian packages should be available shortly. Thanks to everyone involved :) Cheers, -- Victor Grousset/tuxayo From mtj at kohaaloha.com Sun Dec 26 03:02:30 2021 From: mtj at kohaaloha.com (Mason James) Date: Sun, 26 Dec 2021 15:02:30 +1300 Subject: [Koha-devel] =?utf-8?q?Koha_packages_are_available_=F0=9F=8E=81?= In-Reply-To: <00df4248-29d3-d4fa-4a6b-e584425d38c9@kohaaloha.com> References: <00df4248-29d3-d4fa-4a6b-e584425d38c9@kohaaloha.com> Message-ID: kia ora community, the latest Koha packages are available cheers, Mason From kohanews at gmail.com Sun Dec 26 18:23:06 2021 From: kohanews at gmail.com (Koha Newsletter) Date: Sun, 26 Dec 2021 18:23:06 +0100 Subject: [Koha-devel] Koha Community Newsletter: December 2021 Message-ID: The Koha Community Newsletter for December 2021 is here: https://koha-community.org/koha-community-newsletter-december-2021/ Many thanks to everyone who submitted articles and news to this newsletter! Please feel free to email me with any corrections or suggestions. -- Michael Kuhn Editor, Koha Community Newsletter -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Mon Dec 27 14:50:01 2021 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Mon, 27 Dec 2021 10:50:01 -0300 Subject: [Koha-devel] API error responses change Message-ID: Hi all, I wanted to mention that I've submitted patches for bug 28020 [1]. The change introduces a new attribute to the generic error response object that is reused everywhere in the spec. The new attribute is called 'error_code' and is intended to be adopted so API consumers have better means to deal with error responses. Remember that right now we return an error status (e.g. 409) and a (too) generic description in textual form (e.g. Conflict found). A good use case for this can be seen here [2], in which we already have a handy error string, but we translate it to some text, while we should be returning the error_code attribute, and have it documented on the spec as proposed on bug 28020. Early feedback is welcome, as I would base several things on top of this! THANKS! [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28020 [2] https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=128816 -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From fridolin.somers at biblibre.com Tue Dec 28 07:53:01 2021 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Mon, 27 Dec 2021 20:53:01 -1000 Subject: [Koha-devel] =?utf-8?q?=5BKoha=5D_Koha_packages_are_available_?= =?utf-8?b?8J+OgQ==?= In-Reply-To: References: <00df4248-29d3-d4fa-4a6b-e584425d38c9@kohaaloha.com> Message-ID: Hi, There has been a mail for 20.11.13 release : https://koha-community.org/koha-20-11-13-released/ For other versions I don't see emails. Here are the details : 20.11.01 release : https://koha-community.org/koha-21-11-01-released/ 21.05.08 release : https://koha-community.org/koha-21-05-08-released/ Best regards, Le 25/12/2021 à 16:02, Mason James a écrit : > kia ora community, > the latest Koha packages are available > > cheers, Mason > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France From fridolin.somers at biblibre.com Wed Dec 29 09:39:19 2021 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Tue, 28 Dec 2021 22:39:19 -1000 Subject: [Koha-devel] Development IRC meeting 5 January 2022 Message-ID: Hi See you at next dev meeting : https://wiki.koha-community.org/wiki/Development_IRC_meeting_5_January_2022 The calendar event is not yet created, will be soon. Best regards, -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France From fridolin.somers at biblibre.com Wed Dec 29 09:39:34 2021 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Tue, 28 Dec 2021 22:39:34 -1000 Subject: [Koha-devel] KohaCon22 proposals changes suggestions Message-ID: Hi, We are getting close to end date for KohaCon22 proposals, January 8. Unfortunately there is actually no proposal : https://wiki.koha-community.org/wiki/KohaCon22_Proposals This as been discussed in last dev meeting. https://wiki.koha-community.org/wiki/Development_IRC_meeting_22_December_2021 The world situation on Covid-19 virus is not helping, we hope it will be better soon. First we suggest to extend end date to mid-February. Second we suggest to allow proposals outside eligible continents, keeping priority to actual ones. We may have full-online proposals, we will see. If no oppositions on those changes, I will announce this beginning January. Best regards, -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France From tomascohen at gmail.com Wed Dec 29 10:34:08 2021 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Wed, 29 Dec 2021 06:34:08 -0300 Subject: [Koha-devel] KohaCon22 proposals changes suggestions In-Reply-To: References: Message-ID: +1 El mié., 29 dic. 2021 5:40, Fridolin SOMERS escribió: > Hi, > > We are getting close to end date for KohaCon22 proposals, January 8. > > Unfortunately there is actually no proposal : > https://wiki.koha-community.org/wiki/KohaCon22_Proposals > > This as been discussed in last dev meeting. > > https://wiki.koha-community.org/wiki/Development_IRC_meeting_22_December_2021 > > The world situation on Covid-19 virus is not helping, we hope it will be > better soon. > > First we suggest to extend end date to mid-February. > > Second we suggest to allow proposals outside eligible continents, > keeping priority to actual ones. > We may have full-online proposals, we will see. > > If no oppositions on those changes, I will announce this beginning January. > > Best regards, > > -- > Fridolin SOMERS > Software and system maintainer 🦄 > BibLibre, France > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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: From kyle.m.hall at gmail.com Wed Dec 29 16:07:04 2021 From: kyle.m.hall at gmail.com (Kyle Hall) Date: Wed, 29 Dec 2021 10:07:04 -0500 Subject: [Koha-devel] =?utf-8?q?=5BKoha=5D_Koha_packages_are_available_?= =?utf-8?b?8J+OgQ==?= In-Reply-To: References: <00df4248-29d3-d4fa-4a6b-e584425d38c9@kohaaloha.com> Message-ID: I sent out an email for 21.11, did it get blocked? Kyle --- http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) On Tue, Dec 28, 2021 at 1:53 AM Fridolin SOMERS < fridolin.somers at biblibre.com> wrote: > Hi, > > There has been a mail for 20.11.13 release : > https://koha-community.org/koha-20-11-13-released/ > > For other versions I don't see emails. > Here are the details : > > 20.11.01 release : > https://koha-community.org/koha-21-11-01-released/ > > 21.05.08 release : > https://koha-community.org/koha-21-05-08-released/ > > Best regards, > > Le 25/12/2021 à 16:02, Mason James a écrit : > > kia ora community, > > the latest Koha packages are available > > > > cheers, Mason > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel at 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/ > > -- > Fridolin SOMERS > Software and system maintainer 🦄 > BibLibre, France > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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: From egpetridis at gmail.com Wed Dec 29 16:12:02 2021 From: egpetridis at gmail.com (Manos PETRIDIS) Date: Wed, 29 Dec 2021 17:12:02 +0200 Subject: [Koha-devel] =?utf-8?q?=5BKoha=5D_Koha_packages_are_available_?= =?utf-8?b?8J+OgQ==?= In-Reply-To: References: <00df4248-29d3-d4fa-4a6b-e584425d38c9@kohaaloha.com> Message-ID: Can verify that I’ve received December’s 22nd message informing us on the release of version 21.11.01. Στις Τετ, 29 Δεκ 2021 στις 5:07 μμ ο χρήστης Kyle Hall < kyle.m.hall at gmail.com> έγραψε: > I sent out an email for 21.11, did it get blocked? > > Kyle > --- > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com ) > Meadville Public Library ( http://www.meadvillelibrary.org ) > Crawford County Federated Library System ( http://www.ccfls.org ) > > > On Tue, Dec 28, 2021 at 1:53 AM Fridolin SOMERS < > fridolin.somers at biblibre.com> wrote: > >> Hi, >> >> There has been a mail for 20.11.13 release : >> https://koha-community.org/koha-20-11-13-released/ >> >> For other versions I don't see emails. >> Here are the details : >> >> 20.11.01 release : >> https://koha-community.org/koha-21-11-01-released/ >> >> 21.05.08 release : >> https://koha-community.org/koha-21-05-08-released/ >> >> Best regards, >> >> Le 25/12/2021 à 16:02, Mason James a écrit : >> > kia ora community, >> > the latest Koha packages are available >> > >> > cheers, Mason >> > _______________________________________________ >> > Koha-devel mailing list >> > Koha-devel at 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/ >> >> -- >> Fridolin SOMERS >> Software and system maintainer 🦄 >> BibLibre, France >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at 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 at 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: From fridolin.somers at biblibre.com Thu Dec 30 08:41:36 2021 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Wed, 29 Dec 2021 21:41:36 -1000 Subject: [Koha-devel] =?utf-8?q?=5BKoha=5D_Koha_packages_are_available_?= =?utf-8?b?8J+OgQ==?= In-Reply-To: References: <00df4248-29d3-d4fa-4a6b-e584425d38c9@kohaaloha.com> Message-ID: <11f1a470-cc69-3fea-0231-e3d76dba1a08@biblibre.com> I'm looking at archives : https://lists.koha-community.org/pipermail/koha-devel/2021-December/date.html I dont see it. Can anyone confirm ? Le 29/12/2021 à 05:07, Kyle Hall a écrit : > I sent out an email for 21.11, did it get blocked? > > Kyle > --- > http://www.kylehall.info > ByWater Solutions ( http://bywatersolutions.com > ) > Meadville Public Library ( http://www.meadvillelibrary.org > ) > Crawford County Federated Library System ( http://www.ccfls.org > ) > > > On Tue, Dec 28, 2021 at 1:53 AM Fridolin SOMERS > > wrote: > > Hi, > > There has been a mail for 20.11.13 release : > https://koha-community.org/koha-20-11-13-released/ > > > For other versions I don't see emails. > Here are the details : > > 20.11.01 release : > https://koha-community.org/koha-21-11-01-released/ > > > 21.05.08 release : > https://koha-community.org/koha-21-05-08-released/ > > > Best regards, > > Le 25/12/2021 à 16:02, Mason James a écrit : > > kia ora community, > > the latest Koha packages are available > > > > cheers, Mason > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel at 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/ > > > -- > Fridolin SOMERS > > Software and system maintainer 🦄 > BibLibre, France > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > > -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France From fridolin.somers at biblibre.com Thu Dec 30 08:55:12 2021 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Wed, 29 Dec 2021 21:55:12 -1000 Subject: [Koha-devel] =?utf-8?q?=5BKoha=5D_Koha_packages_are_available_?= =?utf-8?b?8J+OgQ==?= In-Reply-To: <11f1a470-cc69-3fea-0231-e3d76dba1a08@biblibre.com> References: <00df4248-29d3-d4fa-4a6b-e584425d38c9@kohaaloha.com> <11f1a470-cc69-3fea-0231-e3d76dba1a08@biblibre.com> Message-ID: <2789d528-7c18-962b-db2c-26437e0317dc@biblibre.com> Oooooo my bad, it was in my "Katipo" folder. I see it in archives : https://lists.katipo.co.nz/pipermail/koha/2021-December/057162.html All is good. Le 29/12/2021 à 21:41, Fridolin SOMERS a écrit : > I'm looking at archives : > https://lists.koha-community.org/pipermail/koha-devel/2021-December/date.html > > I dont see it. > > Can anyone confirm ? > > Le 29/12/2021 à 05:07, Kyle Hall a écrit : >> I sent out an email for 21.11, did it get blocked? >> >> Kyle >> --- >> http://www.kylehall.info >> ByWater Solutions ( http://bywatersolutions.com >> ) >> Meadville Public Library ( http://www.meadvillelibrary.org >> ) >> Crawford County Federated Library System ( http://www.ccfls.org >> ) >> >> >> On Tue, Dec 28, 2021 at 1:53 AM Fridolin SOMERS >> > >> wrote: >> >>     Hi, >> >>     There has been a mail for 20.11.13 release : >>     https://koha-community.org/koha-20-11-13-released/ >>     >> >>     For other versions I don't see emails. >>     Here are the details : >> >>     20.11.01 release : >>     https://koha-community.org/koha-21-11-01-released/ >>     >> >>     21.05.08 release : >>     https://koha-community.org/koha-21-05-08-released/ >>     >> >>     Best regards, >> >>     Le 25/12/2021 à 16:02, Mason James a écrit : >>      > kia ora community, >>      > the latest Koha packages are available >>      > >>      > cheers, Mason >>      > _______________________________________________ >>      > Koha-devel mailing list >>      > Koha-devel at 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/ >>     >> >>     --     Fridolin SOMERS >     > >>     Software and system maintainer 🦄 >>     BibLibre, France >>     _______________________________________________ >>     Koha-devel mailing list >>     Koha-devel at 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/ >>     >> > -- Fridolin SOMERS Software and system maintainer 🦄 BibLibre, France