A new request with request id 15267 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is :
Title : Koha-devel Digest, Vol 190, Issue 20
Category :
Description : Send Koha-devel mailing list submissions to
koha-devel@lists.koha-community.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
or, via email, send a message with subject or body 'help' to
koha-devel-request@lists.koha-community.org
You can reach the person managing the list at
koha-devel-owner@lists.koha-community.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Koha-devel digest..."
Today's Topics:
1. New Koha minor versions released - security fixes included,
UPGRADE! (Jonathan Druart)
2. Klaro (dcook@prosentient.com.au)
3. Koha Improvement idea for the Task scheduler feature
(Ola Andersson)
----------------------------------------------------------------------
Message: 1
Date: Mon, 27 Sep 2021 14:52:31 +0200
From: Jonathan Druart <jonathan.druart@bugs.koha-community.org>
To: koha <koha@lists.katipo.co.nz>, koha-devel
<koha-devel@lists.koha-community.org>
Subject: [Koha-devel] New Koha minor versions released - security
fixes included, UPGRADE!
Message-ID:
<CAJzKNY4zh7L60MpDP9=+3Q8iNj3pyNdWHfjEDxqWG1FQvfJgiQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Hello everybody,
I am announcing, on behalf of the whole Koha release team,
synchronised releases for the four release versions we are currently
supporting.
The release notes are available below:
21.05.04 - https://koha-community.org/koha-21-05-04-released-%e2%9a%a0-security-release/
20.11.10 - https://koha-community.org/koha-20-11-10-released-%e2%9a%a0-security-release/
20.05.16 - https://koha-community.org/koha-20-05-16-released-%e2%9a%a0-security-release/
19.11.22 - https://koha-community.org/koha-19-11-22-released-%e2%9a%a0-security-release/
As they contain security bug fixes we suggest you upgrade all the Koha
instances you are in charge of as soon as possible.
Let us know if you have any questions.
Regards,
Jonathan
------------------------------
Message: 2
Date: Tue, 28 Sep 2021 10:18:49 +1000
From: <dcook@prosentient.com.au>
To: "'koha-devel'" <koha-devel@lists.koha-community.org>
Subject: [Koha-devel] Klaro
Message-ID: <027801d7b3fe$68dc4490$3a94cdb0$@prosentient.com.au>
Content-Type: text/plain; charset="utf-8"
Hi all,
Does anyone have any experience with Klaro? https://heyklaro.com/
I've noticed that DSpace uses it, and I think that I've noticed other
projects using it in the past for things like cookie consent.
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20210928/058377f5/attachment-0001.htm>
------------------------------
Message: 3
Date: Tue, 28 Sep 2021 08:13:58 +0000
From: Ola Andersson <ola.andersson@ltu.se>
To: "koha-devel@lists.koha-community.org"
<koha-devel@lists.koha-community.org>
Subject: [Koha-devel] Koha Improvement idea for the Task scheduler
feature
Message-ID:
<AM9P191MB195378BDF6D334B5612EC80D9EA89@AM9P191MB1953.EURP191.PROD.OUTLOOK.COM>
Content-Type: text/plain; charset="utf-8"
Kia ora Everyone,
I had a look at the Task scheduler in our version of Koha (20.11) and have a few improvements in mind:
[cid:image001.png@01D78F90.E83EC790]
By Adding a "when to send" dimension it would become possible to use the Task scheduler for repetitive (cron) reports.. E.g. We use our local task scheduler to send picking lists to staff to have books picked that have reservations/holds and that are to be transferred from the library to another branch.
These below are the main "when to send" values available to pick from in our local service doing similar job as Task scheduler:
case "OnRequest":
case "OnContentChange":
case "OnContentChangeOnceDaily":
case "OnContentChangeEveryHour":
case "WDOnContentChangeEveryHour": (WD = Week days - Mon-Fri)
case "WDOnContentChangeEveryHour0717":
case "OnContentChangeEveryHour0720":
case "OnContentChangeEveryMonday":
case "FirstDayEveryMonth":
case "FirstDayEveryQuarter":
case "EveryMonday":
case "EveryTuesday":
case "EveryWednesday":
case "EveryThursday":
case "EveryFriday":
case "EverySaturday":
case "EverySunday":
case "EveryWorkDay":
case "EveryDay":
The options using "OnContentChange" all uses crc32 checksums of the report content to validate if the report content has changed from last run or not.
These are the database field we use for our local version of "Task scheduler":
[cid:image003.png@01D78F91.39FCFCF0]
It would be great if we could extend the task scheduler in line with this above.! I am here mainly submitting an idea and will not be able to develop the features..
Ola Andersson
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20210928/b98733dc/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 15705 bytes
Desc: image001.png
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20210928/b98733dc/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 46688 bytes
Desc: image003.png
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20210928/b98733dc/attachment-0001.png>
------------------------------
Subject: Digest Footer
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/
------------------------------
End of Koha-devel Digest, Vol 190, Issue 20
*******************************************
NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.