Notification - Deadline for data set submission

Hi,

Similar to Complete notification recipientes is there a way to notify user that deadline is being reached for data set submission?

Regards,

Paulo Grácio

1 Like

Hi Paulo,

We can definitely expand on our notification features.

Could you describe a bit more detailed what you would like here?
(and other readers feel free to contribute)

Some questions to get you started:

- Should the message be sent out x days before deadline, x days after
deadline or both?
- I assume you only want to notify the users that have not yet
submitted their data?
- To know who to send notifications to, would it be possible to create
a recipients list based on orgunit + user role, or simply to all users
assigned to the orgunit?
- Would you like to define notification rules per dataset or common
rules applicable to all data sets?

Feel free to describe all this in a blueprint:
https://blueprints.launchpad.net/dhis2/+addspec

Thanks.

Ola

···

---------

----------------------------------
Ola Hodne Titlestad (Mr)
HISP
Department of Informatics
University of Oslo

Mobile: +47 48069736
Home address: Eftasåsen 68, 0687 Oslo, Norway. Googlemaps link

On 13 May 2013 12:15, Paulo Grácio <pgracio@criticalsoftware.com> wrote:

Hi,

Similar to Complete notification recipientes is there a way to notify user
that deadline is being reached for data set submission?

Regards,

Paulo Grácio

_______________________________________________
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp

Hi Paulo,

sorry not at the moment.

However, messaging is exposed through the web API, so you could do
something like this:

- create a SQL view which gives you the ids of the users who have not
completed the form this month, using some clever SQL which joins
completedatasetregistration, organisationunit and user.

- set up a script which retrieves that sql view as json, parses it and uses
cURL to request the web api to dispatch messages to those user with a
descriptive message.

- run that script as a cron job, lets say two days before the dealine every
month.

See here for messaging api docs:

http://dhis2.org/doc/snapshot/en/user/html/ch25s11.html

And here for sql view api docs:

http://dhis2.org/doc/snapshot/en/user/html/ch25s17.html

regards,

Lars

Hi - I would like to support this idea. In regards to Ola’s question I will say:

  1. The notification could be send based on the DataSet ‘Expiry Days’ setting. If it is 0, no notifications are send (no way to write a logic…). Otherwise the notifications can be send X days before/after the Expiry Days. The messages will be different text, so they need to be defined independently. And yes, the assumption is to send messages to those with incomplete data sets. So notification rules should be data-set specific

  2. Who to send: this is difficult. Sending to all those users that have access to the Org Unit that the DataSet is active will be unnecessary. Perhaps it should be send to those users that have explicit access to the specific Org Unit that the DataSet is active.

  3. How to send it. I guess in most cases we want email, but in some cases we may want SMS. I guess this should be based on user settings, which are already in place.

I’m sure others will have other opinions. It will be nice to see this on a future release.

Rodolfo

···

On Mon, May 13, 2013 at 11:34 AM, Ola Hodne Titlestad olati@ifi.uio.no wrote:

Hi Paulo,

We can definitely expand on our notification features.

Could you describe a bit more detailed what you would like here?

(and other readers feel free to contribute)

Some questions to get you started:

  • Should the message be sent out x days before deadline, x days after

deadline or both?

  • I assume you only want to notify the users that have not yet

submitted their data?

  • To know who to send notifications to, would it be possible to create

a recipients list based on orgunit + user role, or simply to all users

assigned to the orgunit?

  • Would you like to define notification rules per dataset or common

rules applicable to all data sets?

Feel free to describe all this in a blueprint:

https://blueprints.launchpad.net/dhis2/+addspec

Thanks.

Ola



Ola Hodne Titlestad (Mr)

HISP

Department of Informatics

University of Oslo

Mobile: +47 48069736

Home address: Eftasåsen 68, 0687 Oslo, Norway. Googlemaps link

On 13 May 2013 12:15, Paulo Grácio pgracio@criticalsoftware.com wrote:

Hi,

Similar to Complete notification recipientes is there a way to notify user

that deadline is being reached for data set submission?

Regards,

Paulo Grácio


Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp


Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp


Rodolfo Meliá

Principal

rmelia@knowming.com

www.knowming.com

+1 708 872 7636

+44 777 576 4090

Skype: rod.melia

Twitter: @RodolfoMelia

Note: Please note my new email address, which I will be using for PSI related work: rmelia@knowming.com

At this moment I’m trying to define an approach to address a requirement about data set submissions deadlines between levels.

Imagine that you have 4 levels of Organization Units, National, Province, District and Health Units.

  •      Health Units send their aggregated data to District using paper forms till the end of the month for monthly cases.
    
  •      District Operator enters data on DHIS2. Defining expiry days to 5, we have the possibility to enter data till 5 days after the end date of the selected data entry period. In this case, would be interesting to notify Operators on day 1, deadline of Health Units, saying that they should enter data and one day before deadline telling that data submission will be locked for further entry.
    
  •      Province Operator has to import Data from District till 10 days after the end date of the selected data entry period.
    
  •      National Operator has to import Data from Province till 15 days after the end date of the selected data entry period.
    

We are planning to have a hybrid deployment, this scenario only applies when District and Province are Offline installations. Lars suggestion seems to be flexible enough, my question is what if in some districts I have to use DHIS2 Live because of hardware limitations?

Regards,

Paulo Grácio

···

From: Lars Helge Øverland [mailto:larshelge@gmail.com]
Sent: segunda-feira, 13 de Maio de 2013 12:35
To: Ola Hodne Titlestad
Cc: Paulo Grácio; dhis2-users@lists.launchpad.net
Subject: Re: [Dhis2-users] Notification - Deadline for data set submission

Hi Paulo,

sorry not at the moment.

However, messaging is exposed through the web API, so you could do something like this:

  • create a SQL view which gives you the ids of the users who have not completed the form this month, using some clever SQL which joins completedatasetregistration, organisationunit and user.

  • set up a script which retrieves that sql view as json, parses it and uses cURL to request the web api to dispatch messages to those user with a descriptive message.

  • run that script as a cron job, lets say two days before the dealine every month.

See here for messaging api docs:

http://dhis2.org/doc/snapshot/en/user/html/ch25s11.html

And here for sql view api docs:

http://dhis2.org/doc/snapshot/en/user/html/ch25s17.html

regards,

Lars

Hi Paulo,

my suggestion was only from the top of my head and it is only feasible when running on one/few online instances. In general I strongly recommend to have as few offline instances as possible, even if that means users will have to live with patchy connectivity for a while.

cheers

Lars

···

On Mon, May 13, 2013 at 2:37 PM, Paulo Grácio pgracio@criticalsoftware.com wrote:

At this moment I’m trying to define an approach to address a requirement about data set submissions deadlines between levels.

Imagine that you have 4 levels of Organization Units, National, Province, District and Health Units.

  •      Health Units send their aggregated data to District using paper forms till the end of the month for monthly cases.
    
  •      District Operator enters data on DHIS2. Defining expiry days to 5, we have the possibility to enter data till 5 days after the end date of the selected data entry period. In this case, would be interesting to notify Operators on day 1, deadline of Health Units, saying that they should enter data and one day before deadline telling that data submission will be locked for further entry.
    
  •      Province Operator has to import Data from District till 10 days after the end date of the selected data entry period.
    
  •      National Operator has to import Data from Province till 15 days after the end date of the selected data entry period.
    

We are planning to have a hybrid deployment, this scenario only applies when District and Province are Offline installations. Lars suggestion seems to be flexible enough, my question is what if in some districts I have to use DHIS2 Live because of hardware limitations?

Regards,

Paulo Grácio

From: Lars Helge Øverland [mailto:larshelge@gmail.com]

Sent: segunda-feira, 13 de Maio de 2013 12:35
To: Ola Hodne Titlestad
Cc: Paulo Grácio; dhis2-users@lists.launchpad.net
Subject: Re: [Dhis2-users] Notification - Deadline for data set submission

Hi Paulo,

sorry not at the moment.

However, messaging is exposed through the web API, so you could do something like this:

  • create a SQL view which gives you the ids of the users who have not completed the form this month, using some clever SQL which joins completedatasetregistration, organisationunit and user.
  • set up a script which retrieves that sql view as json, parses it and uses cURL to request the web api to dispatch messages to those user with a descriptive message.
  • run that script as a cron job, lets say two days before the dealine every month.

See here for messaging api docs:

http://dhis2.org/doc/snapshot/en/user/html/ch25s11.html

And here for sql view api docs:

http://dhis2.org/doc/snapshot/en/user/html/ch25s17.html

regards,

Lars

Continuing the discussion from Notification - Deadline for data set submission!
Did anyone find a way of tackling this down!

I need to send a reminder - notification to users who didn’t complete a weekly aggregated data form and submit these forms!
(Data Sets).

Any idea of how I can find a solution :palms_up_together: :pray:

Regards,
Josue

3 Likes