dhis2-devs team mailing list archive

[Aamer Mohammed <aamerm@xxxxxxxxxxxxxxxx>]

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@xxxxxxxxxxxxxxxx> wrote:

> Thanks for the permission :)
>
> 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:
>
> [image: Inline image 1]
>
>
> 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@xxxxxxxxx>
> wrote:
>
>>
>>
>> On Tue, Jun 14, 2016 at 2:56 PM, Vanya Seth <vanyas@xxxxxxxxxxxxxxxx>
>> 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
>>>
>>> On Mon, Jun 13, 2016 at 3:52 PM, Lars Helge Øverland <lars@xxxxxxxxx>
>>> 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?
>>>>
>>>>
>>>>
>>>> On Fri, Jun 10, 2016 at 11:48 AM, Vanya Seth <vanyas@xxxxxxxxxxxxxxxx>
>>>> 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.
>>>>>
>>>>> [image: Inline image 1]
>>>>>
>>>>> 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:28Time since last
>>>>> analytics table generation:4 h, 43 m, 46 sLast analytics table
>>>>> runtime:5 m, 15 s
>>>>> Let me know what you think about this?
>>>>> RegardsVanya
>>>>>
>>>>> On Fri, Jun 10, 2016 at 1:19 PM, Lars Helge Øverland <lars@xxxxxxxxx>
>>>>> 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.
>>>>>>
>>>>>>
>>>>>> [image: Inline image 1]
>>>>>>
>>>>>> regards,
>>>>>>
>>>>>> Lars
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Thu, Jun 9, 2016 at 3:10 PM, Vanya Seth <vanyas@xxxxxxxxxxxxxxxx>
>>>>>> 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@xxxxxxxxx
>>>>>> http://www.dhis2.org <https://www.dhis2.org/>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> With Regards
>>>>> ThoughtWorks Technologies
>>>>> Hyderabad
>>>>>
>>>>> --Stay Hungry Stay Foolish!!
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Lars Helge Øverland
>>>> Lead developer, DHIS 2
>>>> University of Oslo
>>>> Skype: larshelgeoverland
>>>> lars@xxxxxxxxx
>>>> http://www.dhis2.org <https://www.dhis2.org/>
>>>>
>>>>
>>>
>>>
>>> --
>>> With Regards
>>> ThoughtWorks Technologies
>>> Hyderabad
>>>
>>> --Stay Hungry Stay Foolish!!
>>>
>>
>>
>>
>> --
>> Lars Helge Øverland
>> Lead developer, DHIS 2
>> University of Oslo
>> Skype: larshelgeoverland
>> lars@xxxxxxxxx
>> http://www.dhis2.org <https://www.dhis2.org/>
>>
>>
>
>
> --
> With Regards
> ThoughtWorks Technologies
> Hyderabad
>
> --Stay Hungry Stay Foolish!!
>