<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body>A new request with request id 7486 has been created by koha-devel-request@lists.koha-community.org. Short info on the request is : <br><br>Title : Koha-devel Digest, Vol 203, Issue 6<br>Category : <br>Description : <div>Send Koha-devel mailing list submissions to<br> koha-devel@lists.koha-community.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>or, via email, send a message with subject or body 'help' to<br> koha-devel-request@lists.koha-community.org<br><br>You can reach the person managing the list at<br> koha-devel-owner@lists.koha-community.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of Koha-devel digest..."<br><br><br>Today's Topics:<br><br> 1. Re: an SMS Send issue - wondering if it is possible to do<br> with Koha (Indranil Das Gupta)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Thu, 6 Oct 2022 18:54:31 +0530<br>From: Indranil Das Gupta <indradg@l2c2.co.in><br>To: Tomas Cohen Arazi <tomascohen@gmail.com><br>Cc: Koha-devel <koha-devel@lists.koha-community.org><br>Subject: Re: [Koha-devel] an SMS Send issue - wondering if it is<br> possible to do with Koha<br>Message-ID:<br> <CAJ0y-DffKNAj5RFB5HUYCgZKS8ktR1O2-bc7DaCum8Pk35hFCw@mail.gmail.com><br>Content-Type: text/plain; charset="UTF-8"<br><br>Hi devs,<br><br>I have further explored the problem created by Indian federal rules<br>for SMS where each sms message template for every individual sender<br>requires to be pre-approved and registered with the country's SMS<br>anti-spam blockchain platform as DLT_TEMPLATE_IDs.<br><br>For Koha libraries in India this means each of our sms message<br>lettercodes e.g. CHECKOUT, CHECKIN, PDUE, ODUE, ODUE1 etc need to be<br>mapped against each library's DLT_TEMPLATE_ID for that specific<br>lettercode.<br><br>We can achieve this mapping using the YAML file (bug 13029).<br><br>I would like your advice as to which is the better option in the long term:<br><br>OPTION A :<br>Indicate lettercode to our custom send driver via C4::SMS->send_sms()<br>which being called from _send_message_by_sms($message) from<br>C4::Letters::SendQueuedMessages() and finally looking up the<br>DLT_TEMPLATE_ID for that lettercode from the YAML file.<br><br><br>OPTION B :<br>Place the DLT_TEMPLATE_ID (which are all equal length strings) with /<br>without an optional separator e.g. "^" before we start the actual<br>message template<br><br>Option A this will require C4/Letters.pm and C4/SMS.pm to be trivially<br>patched along with an additional syspref to enable / disable this<br>india specific feature and will require to undergo full bugzilla<br>workflow, but once/if accepted for release by the RM, it becomes part<br>of Koha. In case of option B, it's a quick-n-dirty hack without<br>requiring any bugzilla workflow but will remain susceptible to<br>possible code changes in Koha.<br><br><br>Indranil Das Gupta<br>L2C2 Technologies<br><br>Phone : +91-98300-20971<br>WWW : http://www.l2c2.co.in<br>Blog : http://blog.l2c2.co.in<br>IRC : indradg on irc://irc.freenode.net<br>Twitter : indradg<br><br>On Mon, 3 Oct 2022 at 03:17, Tomas Cohen Arazi <tomascohen@gmail.com> wrote:<br>><br>> I'd say we could add a hook for plugins to inject variables for notices.<br>><br>><br>><br>> El dom, 2 oct 2022 4:01, Indranil Das Gupta <indradg@l2c2.co.in> escribió:<br>>><br>>> Hi all,<br>>><br>>> I've written a new SMS::Send driver module for NIC SMS service (a<br>>> federal IT service provider to Govt agencies in India). It's working<br>>> fine on its own.<br>>><br>>> India's current anti-spam rules demands that every message template<br>>> (e.g. "Dear member {#var#} you have checked out {#var#}") must have to<br>>> its unique 19 digit identifier mapped against the designated sender<br>>> (e.g. the library) in the federal blockchain system for SMS<br>>><br>>> https://smsgw.sms.gov.in/failsafe/HttpLink?username=xxxx&pin=xxxxx&message=This<br>>> is a test message&mnumber=91XXXXXXXXXX&signature=sender_id&dlt_entity_id=xxxxxxx&dlt_template_id=xxxxxxx<br>>><br>>> That last part - dlt_template_id will be different for each message<br>>> template mapped against a specific dlt_entity_id. The sender_id and<br>>> dlt_entity_id is easily taken care of via yaml (bug 13029).<br>>><br>>> I can map the letter_code against dlt_template_id using the yaml, but<br>>> is there a way by which I can push it to SMS.pm?<br>>><br>>> thanks in advance.<br>>><br>>> --<br>>> Indranil Das Gupta<br>>> L2C2 Technologies<br>>><br>>> Phone : +91-98300-20971<br>>> WWW : http://www.l2c2.co.in<br>>> Blog : http://blog.l2c2.co.in<br>>> IRC : indradg on irc://irc.freenode.net<br>>> Twitter : indradg<br>>> _______________________________________________<br>>> Koha-devel mailing list<br>>> Koha-devel@lists.koha-community.org<br>>> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>>> website : https://www.koha-community.org/<br>>> git : https://git.koha-community.org/<br>>> bugs : https://bugs.koha-community.org/<br><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br>Koha-devel mailing list<br>Koha-devel@lists.koha-community.org<br>https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel<br>website : https://www.koha-community.org/<br>git : https://git.koha-community.org/<br>bugs : https://bugs.koha-community.org/<br><br><br>------------------------------<br><br>End of Koha-devel Digest, Vol 203, Issue 6<br>******************************************<br></div><br><br>NOTE: You are receiving this mail because, the Requester/Technician wanted you to get notified on this request creation.<br></body></html>