Providing scheduling flexibility to other tasks

Hi Lars / Team,

Any thoughts on extending the scheduling options for other tasks as mentioned in below mails. Currently Data Sync task will attempt synchronization every minute. Is it a nice to have feature to extend that task for hourly, daily, weekly, monthly and yearly as well?

As of now the scheduling task has daily, weekly, monthly and yearly. We can extend the scheduling task to have hourly as well.

Thanks

Aamer.

image

image

image

···

On Tue, Jun 14, 2016 at 6:53 PM, Vanya Seth vanyas@thoughtworks.com wrote:

Thanks for the permission :slight_smile:

On a related note there are couple of other minor requirements that we are looking at.

We have designed the metadata sync task to be flexible in terms of the scheduling options.

Please look at this screenshot to understand the various options:

We were looking at the potential merits to extend this flexibility of scheduling to other tasks like “Data Sync” and “Analytics Export”.

What are your thoughts about this?

Regards

Vanya

On Tue, Jun 14, 2016 at 6:27 PM, Lars Helge Øverland lars@dhis2.org wrote:


With Regards
ThoughtWorks Technologies

Hyderabad

–Stay Hungry Stay Foolish!!

On Tue, Jun 14, 2016 at 2:56 PM, Vanya Seth vanyas@thoughtworks.com wrote:

Hi Lars

For the starters, there is a setting which needs to be enabled for Metadata versioning (also highlighted in the first email that I sent). So, only if this setting is enabled and there are actual versions in your DB (there is a separate relation called “metadataversion” for the same) will a normal user see this in the About section.

So, if some instance has enabled versioning they will see the version information otherwise not.

Okay nice, that’s a good point. If only visible when metadata version sync is enabled, then go ahead with this.

regards,

Lars

Regards

Vanya


Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

On Mon, Jun 13, 2016 at 3:52 PM, Lars Helge Øverland lars@dhis2.org wrote:

Okay thanks.

My concern is that this will be a bit confusing to users not using the meta-data feature, or having no knowledge about this. Also, this is not strictly meta-data versioning per se - rather a way to download meta-data packages - there is no guarantee that the entire database will be on a specific version. Is there any alternative location for this info?


With Regards
ThoughtWorks Technologies

Hyderabad

–Stay Hungry Stay Foolish!!

On Fri, Jun 10, 2016 at 11:48 AM, Vanya Seth vanyas@thoughtworks.com wrote:

Hi Lars

The information about the Last success will be shown just like the other tasks. This time relates to the successful running of the task.

Whereas the information that we are intending to add is not related to the scheduling.

This information is about the Metadata Version that the instance is currently at. And since, this is “About the” instance we believe it makes sense to be added in the “About” section.

Moreover, it is for users without advanced rights to still be able to see and communicate the version (e.g. for troubleshooting).

Other information that I see in the “About” are:

Last analytics table generation:
2016-06-10 04:28
Time since last analytics table generation:
4 h, 43 m, 46 s
Last analytics table runtime:
5 m, 15 s

Let me know what you think about this?

Regards
Vanya


Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

On Fri, Jun 10, 2016 at 1:19 PM, Lars Helge Øverland lars@dhis2.org wrote:

Hi Vanya,

could this perhaps be part of the scheduling screen (under data admin) ? Seems this could align with the “Last success” labels we have for other async jobs. Not exactly sure here, but it sounds a bit arbitrary to have status of one specific job under about while the others are in scheduling.

regards,

Lars


With Regards
ThoughtWorks Technologies

Hyderabad

–Stay Hungry Stay Foolish!!

On Thu, Jun 9, 2016 at 3:10 PM, Vanya Seth vanyas@thoughtworks.com wrote:

Hi Lars

We have been closing down on the final set of dev tasks before proposing for a merge to trunk.

One of the requirements that we have been considering is to show the following information in the “About” section.

  • Metadata Version of the instance (if versioning is enabled/or if the MetadataVersion table has data as in versions)
  • Last Metadata Version sync attempt

Would like to hear your thoughts about the same.

Thanks in advance.

With Regards

Vanya
ThoughtWorks Technologies

Hyderabad

–Stay Hungry Stay Foolish!!

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

Any comments on below please.

Thanks

Aamer.

image

image

image

···

On Fri, Jul 29, 2016 at 5:55 PM, Aamer Mohammed aamerm@thoughtworks.com wrote:

Hi Lars / Team,

Any thoughts on extending the scheduling options for other tasks as mentioned in below mails. Currently Data Sync task will attempt synchronization every minute. Is it a nice to have feature to extend that task for hourly, daily, weekly, monthly and yearly as well?

As of now the scheduling task has daily, weekly, monthly and yearly. We can extend the scheduling task to have hourly as well.

Thanks

Aamer.

On Tue, Jun 14, 2016 at 6:53 PM, Vanya Seth vanyas@thoughtworks.com wrote:

Thanks for the permission :slight_smile:

On a related note there are couple of other minor requirements that we are looking at.

We have designed the metadata sync task to be flexible in terms of the scheduling options.

Please look at this screenshot to understand the various options:

We were looking at the potential merits to extend this flexibility of scheduling to other tasks like “Data Sync” and “Analytics Export”.

What are your thoughts about this?

Regards

Vanya

On Tue, Jun 14, 2016 at 6:27 PM, Lars Helge Øverland lars@dhis2.org wrote:

With Regards
ThoughtWorks Technologies

Hyderabad

–Stay Hungry Stay Foolish!!

On Tue, Jun 14, 2016 at 2:56 PM, Vanya Seth vanyas@thoughtworks.com wrote:

Hi Lars

For the starters, there is a setting which needs to be enabled for Metadata versioning (also highlighted in the first email that I sent). So, only if this setting is enabled and there are actual versions in your DB (there is a separate relation called “metadataversion” for the same) will a normal user see this in the About section.

So, if some instance has enabled versioning they will see the version information otherwise not.

Okay nice, that’s a good point. If only visible when metadata version sync is enabled, then go ahead with this.

regards,

Lars

Regards

Vanya

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

On Mon, Jun 13, 2016 at 3:52 PM, Lars Helge Øverland lars@dhis2.org wrote:

Okay thanks.

My concern is that this will be a bit confusing to users not using the meta-data feature, or having no knowledge about this. Also, this is not strictly meta-data versioning per se - rather a way to download meta-data packages - there is no guarantee that the entire database will be on a specific version. Is there any alternative location for this info?


With Regards
ThoughtWorks Technologies

Hyderabad

–Stay Hungry Stay Foolish!!

On Fri, Jun 10, 2016 at 11:48 AM, Vanya Seth vanyas@thoughtworks.com wrote:

Hi Lars

The information about the Last success will be shown just like the other tasks. This time relates to the successful running of the task.

Whereas the information that we are intending to add is not related to the scheduling.

This information is about the Metadata Version that the instance is currently at. And since, this is “About the” instance we believe it makes sense to be added in the “About” section.

Moreover, it is for users without advanced rights to still be able to see and communicate the version (e.g. for troubleshooting).

Other information that I see in the “About” are:

Last analytics table generation:
2016-06-10 04:28
Time since last analytics table generation:
4 h, 43 m, 46 s
Last analytics table runtime:
5 m, 15 s

Let me know what you think about this?

Regards
Vanya


Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

On Fri, Jun 10, 2016 at 1:19 PM, Lars Helge Øverland lars@dhis2.org wrote:

Hi Vanya,

could this perhaps be part of the scheduling screen (under data admin) ? Seems this could align with the “Last success” labels we have for other async jobs. Not exactly sure here, but it sounds a bit arbitrary to have status of one specific job under about while the others are in scheduling.

regards,

Lars


With Regards
ThoughtWorks Technologies

Hyderabad

–Stay Hungry Stay Foolish!!

On Thu, Jun 9, 2016 at 3:10 PM, Vanya Seth vanyas@thoughtworks.com wrote:

Hi Lars

We have been closing down on the final set of dev tasks before proposing for a merge to trunk.

One of the requirements that we have been considering is to show the following information in the “About” section.

  • Metadata Version of the instance (if versioning is enabled/or if the MetadataVersion table has data as in versions)
  • Last Metadata Version sync attempt

Would like to hear your thoughts about the same.

Thanks in advance.

With Regards

Vanya
ThoughtWorks Technologies

Hyderabad

–Stay Hungry Stay Foolish!!

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

Hi Morten/Lars,

Any thoughts on below please.

Thanks

Aamer.

image

···

On Fri, Aug 5, 2016 at 2:35 PM, Aamer Mohammed aamerm@thoughtworks.com wrote:

Any comments on below please.

Thanks

Aamer.

On Fri, Jul 29, 2016 at 5:55 PM, Aamer Mohammed aamerm@thoughtworks.com wrote:

Hi Lars / Team,

Any thoughts on extending the scheduling options for other tasks as mentioned in below mails. Currently Data Sync task will attempt synchronization every minute. Is it a nice to have feature to extend that task for hourly, daily, weekly, monthly and yearly as well?

As of now the scheduling task has daily, weekly, monthly and yearly. We can extend the scheduling task to have hourly as well.

Thanks

Aamer.

On Tue, Jun 14, 2016 at 6:53 PM, Vanya Seth vanyas@thoughtworks.com wrote:

Thanks for the permission :slight_smile:

On a related note there are couple of other minor requirements that we are looking at.

We have designed the metadata sync task to be flexible in terms of the scheduling options.

Please look at this screenshot to understand the various options:

We were looking at the potential merits to extend this flexibility of scheduling to other tasks like “Data Sync” and “Analytics Export”.

What are your thoughts about this?

Regards

Vanya

Hi Aamer,

yes we have on our list making a better scheduling manager.

Note that the data sync will check if there are in fact any new data values since last sync, and if not, do nothing. So the 1 minute interval should not really be a problem in terms of network traffic.

regards,

Lars

image

···

On Fri, Sep 9, 2016 at 5:58 PM, Aamer Mohammed aamerm@thoughtworks.com wrote:

Hi Morten/Lars,

Any thoughts on below please.

Thanks

Aamer.

On Fri, Aug 5, 2016 at 2:35 PM, Aamer Mohammed aamerm@thoughtworks.com wrote:

Any comments on below please.

Thanks

Aamer.

On Fri, Jul 29, 2016 at 5:55 PM, Aamer Mohammed aamerm@thoughtworks.com wrote:

Hi Lars / Team,

Any thoughts on extending the scheduling options for other tasks as mentioned in below mails. Currently Data Sync task will attempt synchronization every minute. Is it a nice to have feature to extend that task for hourly, daily, weekly, monthly and yearly as well?

As of now the scheduling task has daily, weekly, monthly and yearly. We can extend the scheduling task to have hourly as well.

Thanks

Aamer.

On Tue, Jun 14, 2016 at 6:53 PM, Vanya Seth vanyas@thoughtworks.com wrote:

Thanks for the permission :slight_smile:

On a related note there are couple of other minor requirements that we are looking at.

We have designed the metadata sync task to be flexible in terms of the scheduling options.

Please look at this screenshot to understand the various options:

We were looking at the potential merits to extend this flexibility of scheduling to other tasks like “Data Sync” and “Analytics Export”.

What are your thoughts about this?

Regards

Vanya

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

Hi Lars

Thanks for the response.

So, its not entirely about the data sync task. We want to extend this flexibility to the other tasks as well. As of now all of them are hardcoded in the system. I am not sure if there is any strong value proposition in remaining so.

Please let know what are the repercussions that you see if the existing tasks are made user configurable in terms of scheduling.

Regards

Vanya

image

···

On Sat, Sep 24, 2016 at 5:56 PM, Lars Helge Øverland lars@dhis2.org wrote:

Hi Aamer,

yes we have on our list making a better scheduling manager.

Note that the data sync will check if there are in fact any new data values since last sync, and if not, do nothing. So the 1 minute interval should not really be a problem in terms of network traffic.

regards,

Lars

On Fri, Sep 9, 2016 at 5:58 PM, Aamer Mohammed aamerm@thoughtworks.com wrote:

Hi Morten/Lars,

Any thoughts on below please.

Thanks

Aamer.


Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

On Fri, Aug 5, 2016 at 2:35 PM, Aamer Mohammed aamerm@thoughtworks.com wrote:

Any comments on below please.

Thanks

Aamer.

On Fri, Jul 29, 2016 at 5:55 PM, Aamer Mohammed aamerm@thoughtworks.com wrote:

Hi Lars / Team,

Any thoughts on extending the scheduling options for other tasks as mentioned in below mails. Currently Data Sync task will attempt synchronization every minute. Is it a nice to have feature to extend that task for hourly, daily, weekly, monthly and yearly as well?

As of now the scheduling task has daily, weekly, monthly and yearly. We can extend the scheduling task to have hourly as well.

Thanks

Aamer.

On Tue, Jun 14, 2016 at 6:53 PM, Vanya Seth vanyas@thoughtworks.com wrote:

Thanks for the permission :slight_smile:

On a related note there are couple of other minor requirements that we are looking at.

We have designed the metadata sync task to be flexible in terms of the scheduling options.

Please look at this screenshot to understand the various options:

We were looking at the potential merits to extend this flexibility of scheduling to other tasks like “Data Sync” and “Analytics Export”.

What are your thoughts about this?

Regards

Vanya

With Regards
ThoughtWorks Technologies

Hyderabad

–Stay Hungry Stay Foolish!!

Hi all,

just to add that the justification of data synch scheduling for us, is not only about the bandwidth, but also about letting the offline instance users have some sense of control about when their data is being sent (every night, every week … ) or even to be triggered manually, depending on the context of the intervention.

cheers,

Marta

image

···

On 26 September 2016 at 07:26, Vanya Seth vanyas@thoughtworks.com wrote:

Hi Lars

Thanks for the response.

So, its not entirely about the data sync task. We want to extend this flexibility to the other tasks as well. As of now all of them are hardcoded in the system. I am not sure if there is any strong value proposition in remaining so.

Please let know what are the repercussions that you see if the existing tasks are made user configurable in terms of scheduling.

Regards

Vanya


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

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

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

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

On Sat, Sep 24, 2016 at 5:56 PM, Lars Helge Øverland lars@dhis2.org wrote:

Hi Aamer,

yes we have on our list making a better scheduling manager.

Note that the data sync will check if there are in fact any new data values since last sync, and if not, do nothing. So the 1 minute interval should not really be a problem in terms of network traffic.

regards,

Lars


With Regards
ThoughtWorks Technologies

Hyderabad

–Stay Hungry Stay Foolish!!

On Fri, Sep 9, 2016 at 5:58 PM, Aamer Mohammed aamerm@thoughtworks.com wrote:

Hi Morten/Lars,

Any thoughts on below please.

Thanks

Aamer.


Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

On Fri, Aug 5, 2016 at 2:35 PM, Aamer Mohammed aamerm@thoughtworks.com wrote:

Any comments on below please.

Thanks

Aamer.

On Fri, Jul 29, 2016 at 5:55 PM, Aamer Mohammed aamerm@thoughtworks.com wrote:

Hi Lars / Team,

Any thoughts on extending the scheduling options for other tasks as mentioned in below mails. Currently Data Sync task will attempt synchronization every minute. Is it a nice to have feature to extend that task for hourly, daily, weekly, monthly and yearly as well?

As of now the scheduling task has daily, weekly, monthly and yearly. We can extend the scheduling task to have hourly as well.

Thanks

Aamer.

On Tue, Jun 14, 2016 at 6:53 PM, Vanya Seth vanyas@thoughtworks.com wrote:

Thanks for the permission :slight_smile:

On a related note there are couple of other minor requirements that we are looking at.

We have designed the metadata sync task to be flexible in terms of the scheduling options.

Please look at this screenshot to understand the various options:

We were looking at the potential merits to extend this flexibility of scheduling to other tasks like “Data Sync” and “Analytics Export”.

What are your thoughts about this?

Regards

Vanya