Re: [Dhis2-devs] [Dhis2-users] Feature roadmap for the next releases

[Vanya Seth]

Thanks for the info Lars. 

Regards 
Vanya

Sent from my iPhone

> On 06-Feb-2017, at 11:10 PM, Lars Helge Øverland  wrote:
> 
> Hi Vanya,
> 
> we have created filters for features and improvements per upcoming release. 
> For each issue we now separate between those which are "internal" to the 
> system (like refactors) and those of "general interest" (functional 
> features), and in the mentioned filters we only include "external" features.
> 
> You can find links to those filters here, which should give you a decent 
> overview. We are still in the planning phase for the coming year.
> 
> https://www.dhis2.org/roadmap
> 
> 
> 
> best regards,
> 
> Lars
> 
> 
> 
>> On Sat, Feb 4, 2017 at 8:32 AM, Vanya Seth  wrote:
>> Hi Devs
>> 
>> Thanks for the 2.26 release and the great features. Congratulations once 
>> again!
>> 
>> Can you please point to the documentation for the upcoming releases? Wanted 
>> to get a sense of features that are lined up for the coming releases.
>> 
>> Thanks for the help.
>> -- 
>> With Regards
>> Vanya
>> ThoughtWorks Technologies
>> Hyderabad
>> 
>> --Stay Hungry Stay Foolish!!
>> 
>> ___
>> Mailing list: https://launchpad.net/~dhis2-users
>> Post to : dhis2-us...@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~dhis2-users
>> More help   : https://help.launchpad.net/ListHelp
>> 
> 
> 
> 
> -- 
> Lars Helge Øverland
> Lead developer, DHIS 2
> University of Oslo
> Skype: larshelgeoverland
> l...@dhis2.org
> http://www.dhis2.org
> 
___
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

[Dhis2-devs] Feature roadmap for the next releases

[Vanya Seth]

Hi Devs

Thanks for the 2.26 release and the great features. Congratulations once
again!

Can you please point to the documentation for the upcoming releases? Wanted
to get a sense of features that are lined up for the coming releases.

Thanks for the help.
-- 
With Regards
Vanya
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] Synchronisation URL not set

[Vanya Seth]

Hi Calle

This log is coming from the data synchronization module. It seems you have
enabled "Data Synchronization". Please check the "Data
Administration"-->"Scheduling" section if Data Synchronization is enabled.
And if the synchronization URL is not configured these logs would be
generated.

Regards
Vanya

On Sun, Jan 22, 2017 at 9:39 PM, Calle Hedberg 
wrote:

> Hi
>
> I've got a database recently upgraded from 2.22 to 2.25. In the tomcat
> log, the following comes up every single minute:
>
> * INFO  2017-01-22 18:00:00,011 Remote server URL not set (
> DefaultSynchronizationManager.java [taskScheduler-1])
> * INFO  2017-01-22 18:00:00,011 Aborting synch, server not available (
> DefaultSynchronizationManager.java [taskScheduler-1])
>
> I have not seen this on any other instance, and un-selecting "enable
> meta-data synchronisation" under Systems Setting -> Synchronisation does
> not remove this (other instances might have meta-data synchronisation
> enabled but with no URL specified - you still does not get this tomcat
> message).
>
> So: what else can trigger the above messages?
>
> I know it's just an info message, but I don't like having the server doing
> unnecessary checks every minute
>
> Regards
> Calle
>
> ***
>
> Calle Hedberg
>
> 46D Alma Road, 7700 Rosebank, SOUTH AFRICA
>
> Tel/fax (home): +27-21-685-6472
>
> Cell: +27-82-853-5352
>
> Iridium SatPhone: +8816-315-19119
>
> Email: calle.hedb...@gmail.com
>
> Skype: calle_hedberg
>
> ***
>
>
> ___
> 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
>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] 2.25 HighCharts Plugins

[Vanya Seth]

Oops sorry!! Yeah you are right  :)

perfect thanks :)

Regards
Vanya

On Thu, Nov 10, 2016 at 4:42 PM, Jan Henrik Øverland  wrote:

> Well, there is no need to use highcharts for pivot tables :-)
>
> But the current status for the plugins is that
>
> - pivot tables and charts (aggregate) have been improved in 2.25
>
> - event reports and event charts are currently receiving the same refactor
> and will be ready for 2.26
>
> On 10 November 2016 at 12:01, Vanya Seth  wrote:
>
>> I hope that the new highchart based plugins are available for all 4 types
>> of objects (Charts, Pivot Tables, Event Reports and Event Charts ) ?
>>
>> Regards
>> Vanya
>>
>> On Thu, Nov 10, 2016 at 4:22 PM, Jan Henrik Øverland 
>> wrote:
>>
>>> Hi Vanya,
>>>
>>> I recommend the new chart plugin based on Highcharts over the old one.
>>> Due to both looks and performance.
>>>
>>> Will try to write up the documentation as soon as possible, but apart
>>> from the instructions you read in the other email it works the same way.
>>>
>>> Jan
>>>
>>> On 10 November 2016 at 06:28, Vanya Seth 
>>> wrote:
>>>
>>>> Hi Jan
>>>>
>>>> Hope you are doing well.
>>>>
>>>> Going through one of the emails in the mailing list I noticed that the
>>>> highcarts based plugins for visualization objects are now available.
>>>>
>>>> I have two questions here:
>>>> - The level of maturity of these plugins as compared to the ExtJs ones.
>>>> - The level of documentation of these plugins. (For ExtJs ones we had
>>>> to investigate a lot because of lack of documentation).
>>>>
>>>> It would be good to know your thoughts about this. As of now we are
>>>> leveraging the ExtJs based plugins to render the visualization objects.
>>>>
>>>> --
>>>> With Regards
>>>> Vanya
>>>> ThoughtWorks Technologies
>>>> Hyderabad
>>>>
>>>> --Stay Hungry Stay Foolish!!
>>>>
>>>
>>>
>>>
>>> --
>>> Jan Henrik Øverland
>>> Software developer, DHIS 2
>>> University of Oslo
>>> http://www.dhis2.org <https://www.dhis2.org/>
>>>
>>
>>
>>
>> --
>> With Regards
>> ThoughtWorks Technologies
>> Hyderabad
>>
>> --Stay Hungry Stay Foolish!!
>>
>
>
>
> --
> Jan Henrik Øverland
> Software developer, DHIS 2
> University of Oslo
> http://www.dhis2.org <https://www.dhis2.org/>
>



-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] 2.25 HighCharts Plugins

[Vanya Seth]

I hope that the new highchart based plugins are available for all 4 types
of objects (Charts, Pivot Tables, Event Reports and Event Charts ) ?

Regards
Vanya

On Thu, Nov 10, 2016 at 4:22 PM, Jan Henrik Øverland  wrote:

> Hi Vanya,
>
> I recommend the new chart plugin based on Highcharts over the old one. Due
> to both looks and performance.
>
> Will try to write up the documentation as soon as possible, but apart from
> the instructions you read in the other email it works the same way.
>
> Jan
>
> On 10 November 2016 at 06:28, Vanya Seth  wrote:
>
>> Hi Jan
>>
>> Hope you are doing well.
>>
>> Going through one of the emails in the mailing list I noticed that the
>> highcarts based plugins for visualization objects are now available.
>>
>> I have two questions here:
>> - The level of maturity of these plugins as compared to the ExtJs ones.
>> - The level of documentation of these plugins. (For ExtJs ones we had to
>> investigate a lot because of lack of documentation).
>>
>> It would be good to know your thoughts about this. As of now we are
>> leveraging the ExtJs based plugins to render the visualization objects.
>>
>> --
>> With Regards
>> Vanya
>> ThoughtWorks Technologies
>> Hyderabad
>>
>> --Stay Hungry Stay Foolish!!
>>
>
>
>
> --
> Jan Henrik Øverland
> Software developer, DHIS 2
> University of Oslo
> http://www.dhis2.org <https://www.dhis2.org/>
>



-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

[Dhis2-devs] 2.25 HighCharts Plugins

[Vanya Seth]

Hi Jan

Hope you are doing well.

Going through one of the emails in the mailing list I noticed that the
highcarts based plugins for visualization objects are now available.

I have two questions here:
- The level of maturity of these plugins as compared to the ExtJs ones.
- The level of documentation of these plugins. (For ExtJs ones we had to
investigate a lot because of lack of documentation).

It would be good to know your thoughts about this. As of now we are
leveraging the ExtJs based plugins to render the visualization objects.

-- 
With Regards
Vanya
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] Testing upgrade of DHIS2 from 2.21 to 2.24

[Vanya Seth]

HI Morten

Hope you are doing well.

Can you please have a look at these issues as well?

Regards
Vanya

On Fri, Oct 21, 2016 at 3:15 PM, Aamer Mohammed 
wrote:

> Hi Lars/Morten,
>
> Recently we did a DHIS upgrade test to upgrade our instances from 2.21 to
> 2.24. We started with 2.21 instance having good amount of metadata. We
> sequentially upgraded that instance to 2.24 by following the upgrade
> scripts for each DHIS version.
> From that upgraded instance, an export was taken using the new exporter
> (/api/24/metadata). It was then imported to another fresh instance on 2.24
> using the new importer. Below are our findings.
>
> 1) Most of the blockers were due to introducing of new constraints across
> DHIS versions. The upgraded instance did not have these constraints but
> the new fresh instance had them so it was preventing the import.
> ex: shortName in dataelements table became unique
> numerator is required for all indicators
> dataelement_operand_unique_key (it is removed now)
> We manually corrected our data so it abides as per the constraints. *The
> list of constraints introduced in a DHIS version would be part of upgrade
> notes. Is this a right assumption?*
>
> 2) Allow for many-to-many between Group and GroupSet. If we have groups
> which are part of multiple group sets, Hibernate will create duplicate
> GroupSets and it results in database integrity issue when importing.
> We manually corrected the data and ensured one to one mapping between them
> to proceed further. *When do we plan to have the many-to-many mapping
> between Group and GroupSet?*
>
> 3) Error importing Charts, Report Tables, Event charts, Event reports.
> We excluded these metadata types from the export.json to continue further.
> We are unable to import these in 2.25 also. *Please do inform us once the
> fix is done in 2.25 so that we can retest.*
>
> 4) When we update a new DHIS war, the instance is migrated to new DHIS
> version. But if existing data in our instance does not abide by the new
> constraints, the new constraints are not applied in our upgraded instance.
> So effectively it is not pure DHIS upgrade. So ideally, before applying the
> war file we should modify our data to abide the new constraints. *Is this
> a right assumption?*
>
> Please suggest.
>
> Thanks
> Aamer.
>
> ___
> 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
>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] Upgrading DHIS2 from 2.21 to 2.24 and using new exporter/importer

[Vanya Seth]

Sure that makes sense.

But I am more curious to understand the following:

My existing Database (the data inside) does not follow the new constraints
that I am trying to add. Say I decide to make "shortName" unique by
altering the table to add this uniqueness constraint. But if the existing
short names column has repetitions then how does this get handled?

This is just one example but we have encountered so many such use cases.
The only part that I am unable to understand is "the new version war gets
deployed successfully" giving a false notion of version upgrade.

Thoughts?

Regards
Vanya

On Thu, Oct 6, 2016 at 6:34 PM, Lars Helge Øverland  wrote:

> Hi Vanya,
>
> yes agree, now we typically embed the upgrade statements within DHIS 2
> itself, as we have learnt that people often forget to run upgrade
> statements which causes all kinds of problems.
>
> regards,
>
> Lars
>
>
> On Tue, Oct 4, 2016 at 11:31 AM, Vanya Seth 
> wrote:
>
>> Hi Lars
>>
>> Thanks for the response.
>>
>> But have we only introduced not null constraints over different version
>> updates?
>>
>> But am still not sure how the constraints get applied if the data does
>> not abide by the rules.
>>
>> What looks like a reasonable process to me is :
>> - Update your database data to abide by the new constraints.
>> - Deploy the new war.
>>
>> Thought?
>>
>> Regards
>> Vanya
>>
>>
>> On Tue, Oct 4, 2016 at 1:27 PM, Lars Helge Øverland 
>> wrote:
>>
>>> Hi Vanya,
>>>
>>> sure. We definitely try to avoid this. See previous email in thread. The
>>> operand constraint has been removed. We will include not-null constraints
>>> in the upgrade notes.
>>>
>>> For 2.25 <https://www.dhis2.org/225-upgrade> we will set the "created"
>>> and "lastupdated" columns of tables of "identifiable objects" to not-null.
>>>
>>> best regards,
>>>
>>> Lars
>>>
>>>
>>> On Tue, Oct 4, 2016 at 9:39 AM, Vanya Seth 
>>> wrote:
>>>
>>>> Hi Morten and Lars
>>>>
>>>> There are certain key points highlighted in the above email. Whenever a
>>>> new DHIS2 version comes out there are new integrity constraints added but
>>>> thats not part of the release or the upgrade notes.  So, whats the right
>>>> way to get information about these constraints?
>>>>
>>>> When we deploy the new war we assume that the TableAlteror will take
>>>> care of modifying the schema and also take care of adding the new
>>>> constraints. But in case the existing data does not abide by these
>>>> constraints how do we apply them?
>>>>
>>>> So, principally after a successful redeploy of the war of a higher
>>>> version can we say that the DHIS instance has been upgraded in its true
>>>> sense.
>>>> As of now it seems the war does get updated but the underlying database
>>>> does not.
>>>>
>>>> Needless to say this breaks the export /import of metadata downstream.
>>>>
>>>> Any insights about this would be appreciated.
>>>>
>>>> Regards
>>>> Vanya
>>>>
>>>>
>>>> On Thu, Sep 29, 2016 at 5:01 PM, Aamer Mohammed <
>>>> aam...@thoughtworks.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> For continuation of testing, we changed the metadata to ensure that a
>>>>> Group can be part of only one GroupSet.
>>>>> 1) We got the below issue.
>>>>> {"status":"ERROR","stats":{"total":1,"created":0,"updated":0
>>>>> ,"deleted":0,"ignored":1},"typeReports":[{"klass":"org.hisp.
>>>>> dhis.indicator.Indicator","stats":{"total":1,"created":0,"up
>>>>> dated":0,"deleted":0,"ignored":1},"objectReports":[{"klass":
>>>>> "org.hisp.dhis.indicator.Indicator","index":277,"uid":"oMbEl
>>>>> S3lhOO","errorReports":[{"message":"Missing required property
>>>>> `numerator`.","mainKlass":"org.hisp.dhis.indicator.Indicator
>>>>> ","errorKlass":"java.lang.String","errorCode":"E4000"}]}]}]}
>>>>>

Re: [Dhis2-devs] Upgrading DHIS2 from 2.21 to 2.24 and using new exporter/importer

[Vanya Seth]

Hi Lars

Thanks for the response.

But have we only introduced not null constraints over different version
updates?

But am still not sure how the constraints get applied if the data does not
abide by the rules.

What looks like a reasonable process to me is :
- Update your database data to abide by the new constraints.
- Deploy the new war.

Thought?

Regards
Vanya


On Tue, Oct 4, 2016 at 1:27 PM, Lars Helge Øverland  wrote:

> Hi Vanya,
>
> sure. We definitely try to avoid this. See previous email in thread. The
> operand constraint has been removed. We will include not-null constraints
> in the upgrade notes.
>
> For 2.25 <https://www.dhis2.org/225-upgrade> we will set the "created"
> and "lastupdated" columns of tables of "identifiable objects" to not-null.
>
> best regards,
>
> Lars
>
>
> On Tue, Oct 4, 2016 at 9:39 AM, Vanya Seth 
> wrote:
>
>> Hi Morten and Lars
>>
>> There are certain key points highlighted in the above email. Whenever a
>> new DHIS2 version comes out there are new integrity constraints added but
>> thats not part of the release or the upgrade notes.  So, whats the right
>> way to get information about these constraints?
>>
>> When we deploy the new war we assume that the TableAlteror will take care
>> of modifying the schema and also take care of adding the new constraints.
>> But in case the existing data does not abide by these constraints how do we
>> apply them?
>>
>> So, principally after a successful redeploy of the war of a higher
>> version can we say that the DHIS instance has been upgraded in its true
>> sense.
>> As of now it seems the war does get updated but the underlying database
>> does not.
>>
>> Needless to say this breaks the export /import of metadata downstream.
>>
>> Any insights about this would be appreciated.
>>
>> Regards
>> Vanya
>>
>>
>> On Thu, Sep 29, 2016 at 5:01 PM, Aamer Mohammed 
>> wrote:
>>
>>> Hi,
>>>
>>> For continuation of testing, we changed the metadata to ensure that a
>>> Group can be part of only one GroupSet.
>>> 1) We got the below issue.
>>> {"status":"ERROR","stats":{"total":1,"created":0,"updated":0
>>> ,"deleted":0,"ignored":1},"typeReports":[{"klass":"org.hisp.
>>> dhis.indicator.Indicator","stats":{"total":1,"created":0,"
>>> updated":0,"deleted":0,"ignored":1},"objectReports":[{"klass
>>> ":"org.hisp.dhis.indicator.Indicator","index":277,"uid":"
>>> oMbElS3lhOO","errorReports":[{"message":"Missing required property
>>> `numerator`.","mainKlass":"org.hisp.dhis.indicator.Indicator
>>> ","errorKlass":"java.lang.String","errorCode":"E4000"}]}]}]}
>>>
>>> which means that Numerator is required field for an indicator. This was
>>> not the case in 2.21. This restriction was introduced in some version after
>>> 2.21. However, we modified the metadata for the indicator having this issue
>>> and proceeded further.
>>>
>>> 2) Now we got the below issue.
>>> {"httpStatus":"Internal Server Error","httpStatusCode":500,"s
>>> tatus":"ERROR","message":"ERROR: duplicate key value violates unique
>>> constraint \"dataelement_operand_unique_key\"\n  Detail: Key
>>> (dataelementid, categoryoptioncomboid)=(4497, 3576) already exists."}
>>>
>>> This means that you cannot have duplicate combination of (dataelementid,
>>> categoryoptioncomboid) in dataelementoperand table. This constraint was not
>>> present in 2.21 version.
>>> When we see dataelementoperand table, there are lot of such duplicates.
>>> We would like to understand more around this constraint and why it was
>>> introduced.
>>> *Is there any note which has the details about the constraints being
>>> introduced in a DHIS version?*
>>>
>>> 3) Also this constraint (dataelement_operand_unique_key) is not present
>>> in the instance which was upgraded from 2.21 to 2.24. But it is present in
>>> the instance which is directly on 2.24. Any thoughts on this. Did the
>>> constraint not get created in upgraded instance because the data was not
>>> abiding to the constraint rules? What happens in a dhi

Re: [Dhis2-devs] Upgrading DHIS2 from 2.21 to 2.24 and using new exporter/importer

[Vanya Seth]

if you need any information that you
>>>>>>> might require.
>>>>>>> >>>
>>>>>>> >>> Regards,
>>>>>>> >>> Sultan Ahamar.
>>>>>>> >>>
>>>>>>> >>> On Tue, Sep 6, 2016 at 6:14 PM, Sultanahamar Mohammad <
>>>>>>> >>> sult...@thoughtworks.com> wrote:
>>>>>>> >>>
>>>>>>> >>>> Hi Morten,
>>>>>>> >>>>
>>>>>>> >>>> We have pulled latest code from 2.24 and tried import /  export
>>>>>>> again.
>>>>>>> >>>> We have some interesting observations
>>>>>>> >>>>
>>>>>>> >>>> *DB snapshot:*
>>>>>>> >>>>
>>>>>>> >>>>
>>>>>>> >>>> ​
>>>>>>> >>>> There are no duplicate items in DB. We double checked.
>>>>>>> >>>>
>>>>>>> >>>>
>>>>>>> >>>>
>>>>>>> >>>>
>>>>>>> >>>> *Entity endpoint snapshot:*
>>>>>>>
>>>>>>> >>>>
>>>>>>> >>>> ​Interestingly we found few duplicate entities when we try to
>>>>>>> fetch
>>>>>>> >>>> this data through the API. In Maintenance app, we are not able
>>>>>>> to see these
>>>>>>> >>>> duplicate entities. Does it also explain why we get repeating
>>>>>>> entries (with
>>>>>>> >>>> same UID's) in the full export JSON as well?  Let us know on
>>>>>>> how to proceed
>>>>>>> >>>> and if you need more input.
>>>>>>> >>>>
>>>>>>> >>>> Thanks for all the help in advance.
>>>>>>> >>>>
>>>>>>> >>>> Regards,
>>>>>>> >>>> Sultan Ahamar.
>>>>>>> >>>>
>>>>>>> >>>>
>>>>>>> >>>> On Tue, Sep 6, 2016 at 9:34 AM, Morten Olav Hansen <
>>>>>>> mor...@dhis2.org>
>>>>>>> >>>> wrote:
>>>>>>> >>>>
>>>>>>> >>>>> Hi Vanya
>>>>>>> >>>>>
>>>>>>> >>>>> This should now have been fixed in master and 224. It will now
>>>>>>> do a
>>>>>>> >>>>> global UID check first, and report back any duplicates, if it
>>>>>>> finds a
>>>>>>> >>>>> duplicate it will remove them from the import and report back
>>>>>>> an
>>>>>>> >>>>> `ErrorReport` (as it would do with other validation issues).
>>>>>>> So if it finds
>>>>>>> >>>>> a duplicate, you will need to set atomic mode to NONE to have
>>>>>>> it import and
>>>>>>> >>>>> ignore the duplicates.
>>>>>>> >>>>>
>>>>>>> >>>>> (btw, there was several duplicates in your file, not sure how
>>>>>>> that
>>>>>>> >>>>> happened.. maybe something needs to be cleaned in your source
>>>>>>> instance)
>>>>>>> >>>>>
>>>>>>> >>>>> --
>>>>>>> >>>>> Morten Olav Hansen
>>>>>>> >>>>> Senior Engineer, DHIS 2
>>>>>>> >>>>> University of Oslo
>>>>>>> >>>>> http://www.dhis2.org
>>>>>>> >>>>>
>>>>>>> >>>>> On Mon, Sep 5, 2016 at 2:37 PM, Morten Olav Hansen <
>>>>>>> mor...@dhis2.org>
>>>>>>> >>>>> wrote:
>>>>>>> >>>>>
>>>>>>> >>>>>> Hi Vanya
>>>>>>> >>>>>>
>>>>>>> >>>>>> This should have been caught by the imp

Re: [Dhis2-devs] Inputs for new feature: Stopping sync on DHIS version difference between Central and field instance

[Vanya Seth]

Perfect. Thanks.

Regards
Vanya

On Mon, Sep 26, 2016 at 1:20 PM, Lars Helge Øverland  wrote:

>
> Thanks. Yes we will definitely check it out.
>
> Lars
>
> On Mon, Sep 26, 2016 at 9:47 AM, Vanya Seth 
> wrote:
>
>> Hi Lars
>>
>> Sure. This feature we can target for 2.26. But the other PR's that we
>> will send today you would consider them for 2.25 ?
>>
>> Regards
>> Vanya
>>
>> On Mon, Sep 26, 2016 at 1:11 PM, Lars Helge Øverland 
>> wrote:
>>
>>> Hi Vanya, we are having a code freeze tomorrow so that might be a bit
>>> late. Would be great if we can target this for 2.26.
>>>
>>> best regards,
>>>
>>> Lars
>>>
>>>
>>> On Mon, Sep 26, 2016 at 7:28 AM, Vanya Seth 
>>> wrote:
>>>
>>>> Thanks for the information.
>>>>
>>>> Could you also tell about the release timeline for 2.25? If we plan to
>>>> do this for 2.25 then whats the time frame that we are looking at?
>>>>
>>>> Regards
>>>> Vanya
>>>>
>>>> On Sat, Sep 24, 2016 at 5:58 PM, Lars Helge Øverland 
>>>> wrote:
>>>>
>>>>> Hi Vanya,
>>>>>
>>>>> yes this sounds like a good idea to me. Of course, if the metadata is
>>>>> in fact compatible it is unnecessary to abort, but since we do not have a
>>>>> solid way to define which DHIS 2 versions are metadata compatible I think
>>>>> this could be a good idea. Please go ahead.
>>>>>
>>>>> best regards,
>>>>>
>>>>> Lars
>>>>>
>>>>>
>>>>> On Tue, Sep 6, 2016 at 1:39 PM, Suresh Jaydev Kurumeti <
>>>>> skuru...@thoughtworks.com> wrote:
>>>>>
>>>>>> Where do we stand on this with priority for Implementation 1?
>>>>>>
>>>>>> On Tue, Aug 30, 2016 at 3:58 PM, Suresh Jaydev Kurumeti <
>>>>>> skuru...@thoughtworks.com> wrote:
>>>>>>
>>>>>>> Hi Lars, Morten, Let us know your inputs / Priority of this new
>>>>>>> feature. This would enable us plan our Implementation 1 work.
>>>>>>>
>>>>>>> On Fri, Aug 26, 2016 at 10:20 AM, Vanya Seth <
>>>>>>> van...@thoughtworks.com> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> Hello  Lars and Morten
>>>>>>>>
>>>>>>>> We are considering adding another feature to the metadata sync and
>>>>>>>> versioning.
>>>>>>>>
>>>>>>>> The idea is to stop sync if the Remote server (Central instance)
>>>>>>>> and the field instance are on different DHIS2 versions. This is 
>>>>>>>> important
>>>>>>>> as metadata created on one version of DHIS2 might not be compatible 
>>>>>>>> with
>>>>>>>> another version of DHIS2. This also ensures that instances tied up in 
>>>>>>>> this
>>>>>>>> ecosystem remain on the same DHIS2 version.
>>>>>>>>
>>>>>>>> We would like to make this change from the following standpoint:
>>>>>>>>
>>>>>>>> - Synchronization API   /api/metadata/sync  : spitting out relevant
>>>>>>>> http status code and message.
>>>>>>>>
>>>>>>>> - Metadata synchronization task: The task will send out an email
>>>>>>>> notification to the admin telling the reason of abort of sync.
>>>>>>>>
>>>>>>>> Please let us know how you feel about this feature (read
>>>>>>>> restriction :) ).
>>>>>>>>
>>>>>>>> We will be happy to pick it up as you give us a good to go!
>>>>>>>>
>>>>>>>> --
>>>>>>>> With Regards
>>>>>>>> Vanya
>>>>>>>> ThoughtWorks Technologies
>>>>>>>> Hyderabad
>>>>>>>>
>>>>>>>> --Stay Hungry Stay Foolish!!
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> *Suresh Jaydev kurumetiemailskuru...@thoughtworks.com
>>>>>>> Telephone+91 99018 99344
>>>>>>> <+91+99018+99344>[image: ThoughtWorks]
>>>>>>> <http://www.thoughtworks.com/?utm_campaign=suresh-jaydev%20kurumeti-signature&utm_medium=email&utm_source=thoughtworks-email-signature-generator>*
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Suresh Jaydev kurumetiemailskuru...@thoughtworks.com
>>>>>> Telephone+91 99018 99344
>>>>>> <+91+99018+99344>[image: ThoughtWorks]
>>>>>> <http://www.thoughtworks.com/?utm_campaign=suresh-jaydev%20kurumeti-signature&utm_medium=email&utm_source=thoughtworks-email-signature-generator>*
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Lars Helge Øverland
>>>>> Lead developer, DHIS 2
>>>>> University of Oslo
>>>>> Skype: larshelgeoverland
>>>>> l...@dhis2.org
>>>>> 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
>>> l...@dhis2.org
>>> 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
> l...@dhis2.org
> http://www.dhis2.org <https://www.dhis2.org/>
>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] Inputs for new feature: Stopping sync on DHIS version difference between Central and field instance

[Vanya Seth]

Hi Lars

Sure. This feature we can target for 2.26. But the other PR's that we will
send today you would consider them for 2.25 ?

Regards
Vanya

On Mon, Sep 26, 2016 at 1:11 PM, Lars Helge Øverland  wrote:

> Hi Vanya, we are having a code freeze tomorrow so that might be a bit
> late. Would be great if we can target this for 2.26.
>
> best regards,
>
> Lars
>
>
> On Mon, Sep 26, 2016 at 7:28 AM, Vanya Seth 
> wrote:
>
>> Thanks for the information.
>>
>> Could you also tell about the release timeline for 2.25? If we plan to do
>> this for 2.25 then whats the time frame that we are looking at?
>>
>> Regards
>> Vanya
>>
>> On Sat, Sep 24, 2016 at 5:58 PM, Lars Helge Øverland 
>> wrote:
>>
>>> Hi Vanya,
>>>
>>> yes this sounds like a good idea to me. Of course, if the metadata is in
>>> fact compatible it is unnecessary to abort, but since we do not have a
>>> solid way to define which DHIS 2 versions are metadata compatible I think
>>> this could be a good idea. Please go ahead.
>>>
>>> best regards,
>>>
>>> Lars
>>>
>>>
>>> On Tue, Sep 6, 2016 at 1:39 PM, Suresh Jaydev Kurumeti <
>>> skuru...@thoughtworks.com> wrote:
>>>
>>>> Where do we stand on this with priority for Implementation 1?
>>>>
>>>> On Tue, Aug 30, 2016 at 3:58 PM, Suresh Jaydev Kurumeti <
>>>> skuru...@thoughtworks.com> wrote:
>>>>
>>>>> Hi Lars, Morten, Let us know your inputs / Priority of this new
>>>>> feature. This would enable us plan our Implementation 1 work.
>>>>>
>>>>> On Fri, Aug 26, 2016 at 10:20 AM, Vanya Seth 
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> Hello  Lars and Morten
>>>>>>
>>>>>> We are considering adding another feature to the metadata sync and
>>>>>> versioning.
>>>>>>
>>>>>> The idea is to stop sync if the Remote server (Central instance) and
>>>>>> the field instance are on different DHIS2 versions. This is important as
>>>>>> metadata created on one version of DHIS2 might not be compatible with
>>>>>> another version of DHIS2. This also ensures that instances tied up in 
>>>>>> this
>>>>>> ecosystem remain on the same DHIS2 version.
>>>>>>
>>>>>> We would like to make this change from the following standpoint:
>>>>>>
>>>>>> - Synchronization API   /api/metadata/sync  : spitting out relevant
>>>>>> http status code and message.
>>>>>>
>>>>>> - Metadata synchronization task: The task will send out an email
>>>>>> notification to the admin telling the reason of abort of sync.
>>>>>>
>>>>>> Please let us know how you feel about this feature (read restriction
>>>>>> :) ).
>>>>>>
>>>>>> We will be happy to pick it up as you give us a good to go!
>>>>>>
>>>>>> --
>>>>>> With Regards
>>>>>> Vanya
>>>>>> ThoughtWorks Technologies
>>>>>> Hyderabad
>>>>>>
>>>>>> --Stay Hungry Stay Foolish!!
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Suresh Jaydev kurumetiemailskuru...@thoughtworks.com
>>>>> Telephone+91 99018 99344
>>>>> <+91+99018+99344>[image: ThoughtWorks]
>>>>> <http://www.thoughtworks.com/?utm_campaign=suresh-jaydev%20kurumeti-signature&utm_medium=email&utm_source=thoughtworks-email-signature-generator>*
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> *Suresh Jaydev kurumetiemailskuru...@thoughtworks.com
>>>> Telephone+91 99018 99344
>>>> <+91+99018+99344>[image: ThoughtWorks]
>>>> <http://www.thoughtworks.com/?utm_campaign=suresh-jaydev%20kurumeti-signature&utm_medium=email&utm_source=thoughtworks-email-signature-generator>*
>>>>
>>>
>>>
>>>
>>> --
>>> Lars Helge Øverland
>>> Lead developer, DHIS 2
>>> University of Oslo
>>> Skype: larshelgeoverland
>>> l...@dhis2.org
>>> 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
> l...@dhis2.org
> http://www.dhis2.org <https://www.dhis2.org/>
>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] scheduling in DHIS

[Vanya Seth]

We have couple of fixes ready. Will send the PR's shortly.

Regards
Vanya

On Sat, Sep 24, 2016 at 5:59 PM, Lars Helge Øverland  wrote:

> Thanks Vanya,
>
> this sounds good.
>
> regards,
>
> Lasr
>
>
> On Tue, Aug 23, 2016 at 9:05 AM, Vanya Seth 
> wrote:
>
>> Hi Halvdan
>>
>> We will extend the functionality and send a patch.
>>
>> Regards
>> Vanya
>>
>> On Mon, Aug 22, 2016 at 5:57 PM, Halvdan Hoem Grelland > > wrote:
>>
>>> Vanya,
>>>
>>> If you're talking about simply exposing 
>>> TaskExecutor.submitListenable(Runnable)
>>> in the Scheduler interface, it's not a big deal. I'd think you could just
>>> go ahead. Alternately you could wire the AsyncListenableTaskExecutor bean
>>> directly into the service, I suppose.
>>>
>>> On Mon, Aug 22, 2016 at 12:55 PM, Vanya Seth 
>>> wrote:
>>>
>>>> Hi Lars
>>>>
>>>> Any comments on this one?
>>>>
>>>> Regards
>>>> Vanya
>>>>
>>>> On Wed, Aug 17, 2016 at 12:44 PM, Vanya Seth 
>>>> wrote:
>>>>
>>>>> Hi Lars
>>>>>
>>>>> We are looking at extending org.hisp.dhis.system.scheduling.Scheduler to
>>>>> also have the ability to return the ListenableFuture for a Runnable as
>>>>> well. This will help us or any dev in the future to check the status of 
>>>>> the
>>>>> ongoing Runnables in the system and provide some user experience around 
>>>>> it.
>>>>>
>>>>> Please let know if you are ok with us taking it up? As we want to fix
>>>>> a bug wherein the "sync now" button should not be clickable if the task is
>>>>> already running.
>>>>>
>>>>> Regards
>>>>> Vanya
>>>>>
>>>>>
>>>>> On Mon, Aug 8, 2016 at 9:26 AM, Aamer Mohammed <
>>>>> aam...@thoughtworks.com> wrote:
>>>>>
>>>>>> Hi Lars/Morten,
>>>>>>
>>>>>> The scheduling page in DHIS 2.24 has ability to run tasks immediately
>>>>>> in below sections.
>>>>>>
>>>>>>- Metadata Synchronization - Using 'Sync Now' button
>>>>>>- SMS Scheduler - Using 'Run Now' button
>>>>>>
>>>>>> When the user clicks 'Sync Now' button, an asynchronous task is
>>>>>> triggered in the backend for metadata synchronization. The user can click
>>>>>> the button again before the synchronization task is even complete. We 
>>>>>> want
>>>>>> to prevent this as it can spawn multiple threads in the system all doing
>>>>>> the same job leading to race conditions in system.
>>>>>>
>>>>>> We can do the changes in SchedulingManager.executeTask so that it
>>>>>> will check the status of the previously submitted task. If it is not
>>>>>> running then it will start new task or otherwise not. These changes 
>>>>>> should
>>>>>> be applicable to any 'executeNow' type tasks in the system.
>>>>>>
>>>>>> Does DHIS2 already have such functionality available elsewhere in the
>>>>>> system? Any thoughts on this approach.
>>>>>>
>>>>>>
>>>>>> Thanks
>>>>>> Aamer.
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> With Regards
>>>>> ThoughtWorks Technologies
>>>>> Hyderabad
>>>>>
>>>>> --Stay Hungry Stay Foolish!!
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> With Regards
>>>> ThoughtWorks Technologies
>>>> Hyderabad
>>>>
>>>> --Stay Hungry Stay Foolish!!
>>>>
>>>> ___
>>>> 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
>>>>
>>>>
>>>
>>>
>>> --
>>> Halvdan Hoem Grelland
>>> Software developer, DHIS 2
>>> University of Oslo
>>> 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
> l...@dhis2.org
> http://www.dhis2.org <https://www.dhis2.org/>
>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] Inputs for new feature: Stopping sync on DHIS version difference between Central and field instance

[Vanya Seth]

Thanks for the information.

Could you also tell about the release timeline for 2.25? If we plan to do
this for 2.25 then whats the time frame that we are looking at?

Regards
Vanya

On Sat, Sep 24, 2016 at 5:58 PM, Lars Helge Øverland  wrote:

> Hi Vanya,
>
> yes this sounds like a good idea to me. Of course, if the metadata is in
> fact compatible it is unnecessary to abort, but since we do not have a
> solid way to define which DHIS 2 versions are metadata compatible I think
> this could be a good idea. Please go ahead.
>
> best regards,
>
> Lars
>
>
> On Tue, Sep 6, 2016 at 1:39 PM, Suresh Jaydev Kurumeti <
> skuru...@thoughtworks.com> wrote:
>
>> Where do we stand on this with priority for Implementation 1?
>>
>> On Tue, Aug 30, 2016 at 3:58 PM, Suresh Jaydev Kurumeti <
>> skuru...@thoughtworks.com> wrote:
>>
>>> Hi Lars, Morten, Let us know your inputs / Priority of this new feature.
>>> This would enable us plan our Implementation 1 work.
>>>
>>> On Fri, Aug 26, 2016 at 10:20 AM, Vanya Seth 
>>> wrote:
>>>
>>>>
>>>> Hello  Lars and Morten
>>>>
>>>> We are considering adding another feature to the metadata sync and
>>>> versioning.
>>>>
>>>> The idea is to stop sync if the Remote server (Central instance) and
>>>> the field instance are on different DHIS2 versions. This is important as
>>>> metadata created on one version of DHIS2 might not be compatible with
>>>> another version of DHIS2. This also ensures that instances tied up in this
>>>> ecosystem remain on the same DHIS2 version.
>>>>
>>>> We would like to make this change from the following standpoint:
>>>>
>>>> - Synchronization API   /api/metadata/sync  : spitting out relevant
>>>> http status code and message.
>>>>
>>>> - Metadata synchronization task: The task will send out an email
>>>> notification to the admin telling the reason of abort of sync.
>>>>
>>>> Please let us know how you feel about this feature (read restriction :)
>>>> ).
>>>>
>>>> We will be happy to pick it up as you give us a good to go!
>>>>
>>>> --
>>>> With Regards
>>>> Vanya
>>>> ThoughtWorks Technologies
>>>> Hyderabad
>>>>
>>>> --Stay Hungry Stay Foolish!!
>>>>
>>>
>>>
>>>
>>> --
>>> *Suresh Jaydev kurumetiemailskuru...@thoughtworks.com
>>> Telephone+91 99018 99344
>>> <+91+99018+99344>[image: ThoughtWorks]
>>> <http://www.thoughtworks.com/?utm_campaign=suresh-jaydev%20kurumeti-signature&utm_medium=email&utm_source=thoughtworks-email-signature-generator>*
>>>
>>
>>
>>
>> --
>> *Suresh Jaydev kurumetiemailskuru...@thoughtworks.com
>> Telephone+91 99018 99344
>> <+91+99018+99344>[image: ThoughtWorks]
>> <http://www.thoughtworks.com/?utm_campaign=suresh-jaydev%20kurumeti-signature&utm_medium=email&utm_source=thoughtworks-email-signature-generator>*
>>
>
>
>
> --
> Lars Helge Øverland
> Lead developer, DHIS 2
> University of Oslo
> Skype: larshelgeoverland
> l...@dhis2.org
> http://www.dhis2.org <https://www.dhis2.org/>
>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] Providing scheduling flexibility to other tasks

[Vanya Seth]

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



On Sat, Sep 24, 2016 at 5:56 PM, Lars Helge Øverland  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 
> wrote:
>
>> Hi Morten/Lars,
>>
>> Any thoughts on below please.
>>
>>
>> Thanks
>> Aamer.
>>
>>
>> On Fri, Aug 5, 2016 at 2:35 PM, Aamer Mohammed 
>> wrote:
>>
>>> Any comments on below please.
>>>
>>> Thanks
>>> Aamer.
>>>
>>> On Fri, Jul 29, 2016 at 5:55 PM, Aamer Mohammed >> > 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 
>>>> 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
>>>>>
>>>>>
>>>
>>
>
>
> --
> Lars Helge Øverland
> Lead developer, DHIS 2
> University of Oslo
> Skype: larshelgeoverland
> l...@dhis2.org
> http://www.dhis2.org <https://www.dhis2.org/>
>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] DHIS EventReport Plugin

[Vanya Seth]

Hi Jan

We are working with the eventchart plugin and want to understand the
following:

- When we specify the "startDate" and "endDate" config params and on the
favorite the relative period is "last 6 months", then we are always getting
the chart rendered with time axis between March and August. The data lying
between these months and also satisfying the 'startDate' and 'endDate'
 criterion gets displayed.
Is this is expected? Does modifying the startDate and endDate not modify
the period axis?

Although the analytics API is honoring the start and end dates properly.
The data that we get from the API call has all the data between the
specified start and end dates. It's the plugin which is not displaying the
data as returned by the API. But displays only between the configured
periodicity of the favorite.

Any help would be much appreciated.

Regards
Vanya

On Thu, Sep 22, 2016 at 2:25 PM, Vanya Seth  wrote:

> Thanks Jan.
>
> Regards
> Vanya
>
> On Thu, Sep 22, 2016 at 1:44 PM, Jan Henrik Øverland 
> wrote:
>
>> Hi Vanya,
>>
>> Agreed. I'm swamped with work though for 2.25, but let's see what we can
>> do as soon as it's out.
>>
>> Also, the plugin will be upgraded along with the ER refactor for 2.26, so
>> things like what you describe here will definitley be fixed by then.
>>
>> Jan
>>
>> On 22 September 2016 at 08:48, Vanya Seth 
>> wrote:
>>
>>> Hi Jan
>>>
>>> Thanks for adding the issue.
>>>
>>> Couple of interesting points that you might want to consider.
>>>
>>> Whenever there is an issue in the configuration of the viz object, say
>>> the "pe" dimension is missing. The plugin creates a web alert with the
>>> error message. But when we are using this plugin in the context of a custom
>>> app where on a single web page there might be lot of visualization objects.
>>> Then the web alert really falls out of place. It's nearly impossible for
>>> the end user to make out which chart or report is faulty.
>>>
>>> Ideally it would be good if the plugin could throw an exception or write
>>> the error message on the DOM element. That ways its more intuitive. And I
>>> believe we are doing the same when there are "no values in the system" for
>>> the given viz object config.
>>>
>>> Thoughts?
>>>
>>> Let me know if you need more information.
>>>
>>> Regards
>>> Vanya
>>>
>>>
>>
>>
>> --
>> Jan Henrik Øverland
>> Software developer, DHIS 2
>> University of Oslo
>> http://www.dhis2.org <https://www.dhis2.org/>
>>
>
>
>
> --
> With Regards
> ThoughtWorks Technologies
> Hyderabad
>
> --Stay Hungry Stay Foolish!!
>



-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] DHIS EventReport Plugin

[Vanya Seth]

Thanks Jan.

Regards
Vanya

On Thu, Sep 22, 2016 at 1:44 PM, Jan Henrik Øverland  wrote:

> Hi Vanya,
>
> Agreed. I'm swamped with work though for 2.25, but let's see what we can
> do as soon as it's out.
>
> Also, the plugin will be upgraded along with the ER refactor for 2.26, so
> things like what you describe here will definitley be fixed by then.
>
> Jan
>
> On 22 September 2016 at 08:48, Vanya Seth  wrote:
>
>> Hi Jan
>>
>> Thanks for adding the issue.
>>
>> Couple of interesting points that you might want to consider.
>>
>> Whenever there is an issue in the configuration of the viz object, say
>> the "pe" dimension is missing. The plugin creates a web alert with the
>> error message. But when we are using this plugin in the context of a custom
>> app where on a single web page there might be lot of visualization objects.
>> Then the web alert really falls out of place. It's nearly impossible for
>> the end user to make out which chart or report is faulty.
>>
>> Ideally it would be good if the plugin could throw an exception or write
>> the error message on the DOM element. That ways its more intuitive. And I
>> believe we are doing the same when there are "no values in the system" for
>> the given viz object config.
>>
>> Thoughts?
>>
>> Let me know if you need more information.
>>
>> Regards
>> Vanya
>>
>>
>
>
> --
> Jan Henrik Øverland
> Software developer, DHIS 2
> University of Oslo
> http://www.dhis2.org <https://www.dhis2.org/>
>



-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] DHIS EventReport Plugin

[Vanya Seth]

Hi Jan

Thanks for adding the issue.

Couple of interesting points that you might want to consider.

Whenever there is an issue in the configuration of the viz object, say the
"pe" dimension is missing. The plugin creates a web alert with the error
message. But when we are using this plugin in the context of a custom app
where on a single web page there might be lot of visualization objects.
Then the web alert really falls out of place. It's nearly impossible for
the end user to make out which chart or report is faulty.

Ideally it would be good if the plugin could throw an exception or write
the error message on the DOM element. That ways its more intuitive. And I
believe we are doing the same when there are "no values in the system" for
the given viz object config.

Thoughts?

Let me know if you need more information.

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

Re: [Dhis2-devs] DHIS EventReport Plugin

[Vanya Seth]

HI Jan

Thats true. For that favorite we can see both "ou"  and "pe" in the
columns. What you mentioned is exactly whats happening when we provide "pe"
as rows again.
"pe" on the columns is the relative time period of the event report and the
ones that we supply on the rows is the specific periods that we want to
fetch the data for.

Do you see any issue with this config?

Ideally I was hoping that the plugin would take care of appending the dim
items. Similar configs are working fine for other 3 types of viz objects.


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

[Dhis2-devs] Understanding the 'relativePeriodDate' property

[Vanya Seth]

Hello devs

We are leveraging the "relativePeriodDate" parameter on the DHIS2 chart
plugin.
Say we want data starting July 2016 for the last 3 months i.e. May, June
and July 2016.
Logically we think of 2016-07-31 as the relativePerioDate to fetch data for
the above example. But when we do so we get the data starting June and
backwards.

It's like sending "October 2016" to get data from September 2016 and
backwards.

Is this the way its supposed to work?

Any help would be appreciated.

-- 
With Regards
Vanya
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] DHIS EventReport Plugin

[Vanya Seth]

Hi Jan

We are working with DHIS 2.24 and the plugin has been copied from our fork
of dhis-core. So, its from the master branch.
Please let know in case you need more info.

Regards
Vanya

On Fri, Sep 16, 2016 at 3:36 PM, Jan Henrik Øverland  wrote:

> Hi Vanya,
>
> I will look at it, but I need to know the version of the plugin and the
> version of the dhis2 instance.
>
> Jan
>
> On 16 September 2016 at 11:58, Vanya Seth  wrote:
>
>> Hello Devs
>>
>> We are leveraging the eventreport plugin for rendering the event reports
>> in one of our custom apps.
>>
>> We want to get data for specific periods and these could very well be in
>> the past as well.
>> To achieve this we use the "pe" dimension and pass it as "rows" property
>> while making a call to the getEventReport function.
>>
>> The event report is fetched alright in the Event Report web app but while
>> we try to get it through the plugin (the API query string as created by
>> this plugin) we get a 409 Conflict.
>>
>> On further investigation we realize that there are two "pe" type
>> dimensions getting added which is apparently the cause of the conflict.
>>
>> This is the way we are trying to make a call to the plugin:
>>
>> DHIS.getEventReport({
>> url: dhisUrl, el: eventReport.id, id: eventReport.id,
>> *rows: [{dimension: "pe", items: dimensionPeriods}]*
>> });
>>
>> Here the items for the "pe" contains the iso periods for which we want
>> data.
>>
>>
>> And this is the API query that gets generated:
>>
>> http://localhost:8000/api/analytics/events/aggregate/FqtMkfZ
>> k93u.json?stage=SKQlKPszsak&dimension=ou:zOyMxdCLXBM&
>> *dimension=pe:LAST_12_MONTHS&dimension=pe:201510;201511;201512;201601;201602;201603;201604;201605;201606;201607;201608;201609*
>> &outputType=EVENT&displayProperty=NAME
>>
>> Can you help us identify the right way to invoke this plugin?
>>
>> Thanks for the help in advance.
>>
>>
>> --
>> With Regards
>> Vanya
>> ThoughtWorks Technologies
>> Hyderabad
>>
>> --Stay Hungry Stay Foolish!!
>>
>> ___
>> 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
>>
>>
>
>
> --
> Jan Henrik Øverland
> Software developer, DHIS 2
> University of Oslo
> http://www.dhis2.org <https://www.dhis2.org/>
>



-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

[Dhis2-devs] DHIS EventReport Plugin

[Vanya Seth]

Hello Devs

We are leveraging the eventreport plugin for rendering the event reports in
one of our custom apps.

We want to get data for specific periods and these could very well be in
the past as well.
To achieve this we use the "pe" dimension and pass it as "rows" property
while making a call to the getEventReport function.

The event report is fetched alright in the Event Report web app but while
we try to get it through the plugin (the API query string as created by
this plugin) we get a 409 Conflict.

On further investigation we realize that there are two "pe" type dimensions
getting added which is apparently the cause of the conflict.

This is the way we are trying to make a call to the plugin:

DHIS.getEventReport({
url: dhisUrl, el: eventReport.id, id: eventReport.id,
*rows: [{dimension: "pe", items: dimensionPeriods}]*
});

Here the items for the "pe" contains the iso periods for which we want data.


And this is the API query that gets generated:

http://localhost:8000/api/analytics/events/aggregate/FqtMkfZk93u.json?stage=SKQlKPszsak&dimension=ou:zOyMxdCLXBM&;
*dimension=pe:LAST_12_MONTHS&dimension=pe:201510;201511;201512;201601;201602;201603;201604;201605;201606;201607;201608;201609*
&outputType=EVENT&displayProperty=NAME

Can you help us identify the right way to invoke this plugin?

Thanks for the help in advance.


-- 
With Regards
Vanya
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] Upgrading DHIS2 from 2.21 to 2.24 and using new exporter/importer

[Vanya Seth]

Hi Morten

Thanks for the response.

We ran into another issue while trying to do a full export and import.

As per the previous conversations we took care of all data migrations (as
per the new constraints on the DB- pretty much caught by the Importer
during the validation phase itself).

Having done that we run into this issue:
The 'categoryoptiongroup' import is failing with constraint violation for
the UID. We checked the data and there is no repeating UID in the  database.

The error text is attached for your reference, as well the payload used for
the import.

Thanks for all the help in advance.

Regards
Vanya



On Thu, Sep 1, 2016 at 11:10 AM, Morten Olav Hansen 
wrote:

> Thanks Aamer, I'm looking at a similar bug right now.. seems some objects
> don't get their deps properly attached..
>
> --
> Morten Olav Hansen
> Senior Engineer, DHIS 2
> University of Oslo
> http://www.dhis2.org
>
> On Thu, Sep 1, 2016 at 12:36 PM, Aamer Mohammed 
> wrote:
>
>> Hi Morten,
>>
>> Please find the payload for below request
>> *curl -H "Content-Type: application/json" -X GET -u username:password
>> "http://localhost:/api/24/metadata?filter=created:gt:2016-07
>> " >
>> metadata.224.newapi.created.json*
>>
>> Import the payload in a fresh instance for import using
>>
>> *curl -H "Content-Type: application/json" -X POST --data
>> @metadata.224.newapi.created.json -u admin:district
>> “http://localhost:8080/api/24/metadata?atomicMode=NONE
>> ” >
>> output_created_besteffort.txt*
>>
>> If the same payload is run with atomicMode=ALL, I am getting 'Invalid
>> references' errors which is acceptable. But if it is run with
>> atomicMode=NONE, it is throwing the error for which the complete stack
>> trace is attached earlier. filename: '
>> *output_created_besteffort_trace.txt'*
>>
>> Let me know if the complete payload or any other details are required
>> from my end.
>>
>>
>> Thanks
>> Aamer.
>>
>>
>>
>> On Thu, Sep 1, 2016 at 8:52 AM, Morten Olav Hansen 
>> wrote:
>>
>>> Hi Aamer
>>>
>>> Could you please share the payload of the object where this happen?
>>>
>>> --
>>> Morten Olav Hansen
>>> Senior Engineer, DHIS 2
>>> University of Oslo
>>> http://www.dhis2.org
>>>
>>> On Fri, Aug 26, 2016 at 9:13 PM, Aamer Mohammed >> > wrote:
>>>
 Hi Morten,

 The Importer was run with atomicMode=ALL. Though the payload is huge,
 only few errors were shown in ImportSummary. As per errors in previous
 ImportSummary, I have done below.
 1) ensured the 'short name' field is unique for each of the 'data
 elements' and 'data element group' as well
 2) UID of admin, Super User, tracked entity was changed in payload to
 be same to where it is getting imported.
 I have manually resolved them and ran the importer again with
 atomicMode=ALL.

 I got exception as attached in trace file 'output_besteffort_trace.txt'
 Would these kind of issues be known only after the import has failed?
 and we need to resolve them one-by-one and as-and-when the importer throws
 them? Is there any note which has the details about the constraints being
 introduced in a new DHIS version?

 Alternatively, If we export a filtered set of metadata using '
 /api/24/metadata?filter=lastUpdated:gt:2016-05' and run the importer
 with atomicMode=NONE

 *curl -H "Content-Type: application/json" -X POST --data
 @metadata.224.newapi.json -u admin:district
 “http://localhost:8080/api/24/metadata?atomicMode=NONE
 ” >
 output_created_besteffort_trace.txt*

 Getting below exception in trace. Complete trace also attached.
 -
 * INFO 2016-08-26 15:58:38,217 (admin) Creating 57 object(s) of type
 ReportTable (DefaultObjectBundleService.java [qtp289378424-12])
 org.hibernate.TransientObjectException: object references an unsaved
 transient instance - save the transient instance before flushing:
 org.hisp.dhis.indicator.Indicator
 --
 Any suggestions please.


 Thanks
 Aamer.


 On Tue, Aug 23, 2016 at 11:19 AM, Morten Olav Hansen 
 wrote:

> Hi Aamer
>
> Probably what is happening is that the new database has some
> constraints that the old one doesn't. We have had some issues with
> hibernate in the past, and for certain databases that means that many of
> the constraints was not applied..
>
> If you look at the messages, you will see that e.g `shortName` must be
> unique for data elements.. the list of errors is not big though, probably
> you can go through the payload and manually update the objects which has
> issues?
>
> Another issue I see is that you are importing users, and those UIDs
> was only stabilized in 2.23.. so you might want to also manually update
>>>

Re: [Dhis2-devs] switching to github for server-side code on tuesday

[Vanya Seth]

Sounds GREAT!

Regards
Vanya

On Sun, Aug 28, 2016 at 4:59 PM, Lars Helge Øverland  wrote:

> Hi all,
>
> we will be transitioning the core source code branches from Launchpad to
> Github on Tuesday this week (Aug 30).
>
> For developers - please do not make commits to Launchpad on Tuesday. You
> will be notified when the new Github repo is available.
>
> We will migrate the trunk repo and the three latest stable release
> branches. More info will come later.
>
> regards,
>
> Lars
>
>
>
>
> --
> Lars Helge Øverland
> Lead developer, DHIS 2
> University of Oslo
> Skype: larshelgeoverland
> l...@dhis2.org
> http://www.dhis2.org 
>
>
> ___
> 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
>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] Application Security testing for DHIS 2

[Vanya Seth]

HI Greg

Thanks for the response.

I reckon when you say the development team you mean the DHIS2 development
team. Would it be possible to have a look at the kind of issues reported?

It would also be valuable to understand from the dhis devs how the aspects
of security are treated first hand during the course of development.

Regards
Vanya


On Tue, Aug 23, 2016 at 7:03 PM, Greg Wilson  wrote:

> Aamer:
>
> As part of the DATIM work, BAO is performing IBM AppScan vulnerability
> assessment and confirmation. The results of these assessments will be
> passed onto the development team for remediation. Due to the sensitive
> nature of security vulnerabilities, we will follow standard, responsible
> best practices regarding public disclosure. If critical, non-credentialed,
> remote vulnerabilities are discovered we will attempt to provide
> work-a-rounds until the devs can publish a remediated DHIS2 version.
>
> This scanning will only involve DHIS2 core and apps that DATIM uses. We
> are currently scanning v2.21 but will be jumping to 2.23 very soon. This
> will be an ongoing, regular process. If you have any questions feel free to
> contact me any time.
>
> Gregory Wilson, CSSLP
> BAO Systems, Inc.
> gwil...@baosystems.com
>
>
> On Tue, Aug 23, 2016 at 5:31 AM, Aamer Mohammed 
> wrote:
>
>> Hi dhis devs,
>>
>> We are looking for testing the application in areas which focus on "CIA
>> triad" (Confidentiality, Integrity, Availability) of DHIS users and
>> resources. Just wanted to check from DHIS devs if any kind of methodologies
>> are already inplace for testing the code for below vulnerabilities.
>> 1) Cross-site scripting attacks
>> 2) Broken authentication attacks
>> 3) Injection flaws
>> 4) malicious code
>>
>> Thanks
>> Aamer.
>>
>>
>> On Fri, Jul 29, 2016 at 5:37 PM, Aamer Mohammed 
>> wrote:
>>
>>> Hi Team,
>>>
>>> We are now beginning to look at application security of DHIS 2. We want
>>> to understand if there is already any security testing in place for DHIS
>>> and any guidelines around it. This will be helpful in security testing the
>>> features which we have already contributed and the ones which we are
>>> planning to.
>>> It would be helpful if you get us started around this.
>>>
>>> Thanks
>>> Aamer.
>>>
>>>
>>
>> ___
>> 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
>>
>>
>
>
> --
> Greg Wilson
> BAO Systems
>



-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

[Dhis2-devs] Inputs for new feature: Stopping sync on DHIS version difference between Central and field instance

[Vanya Seth]

Hello  Lars and Morten

We are considering adding another feature to the metadata sync and
versioning.

The idea is to stop sync if the Remote server (Central instance) and the
field instance are on different DHIS2 versions. This is important as
metadata created on one version of DHIS2 might not be compatible with
another version of DHIS2. This also ensures that instances tied up in this
ecosystem remain on the same DHIS2 version.

We would like to make this change from the following standpoint:

- Synchronization API   /api/metadata/sync  : spitting out relevant http
status code and message.

- Metadata synchronization task: The task will send out an email
notification to the admin telling the reason of abort of sync.

Please let us know how you feel about this feature (read restriction :) ).

We will be happy to pick it up as you give us a good to go!

-- 
With Regards
Vanya
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] Upgrading to 2.24 and /api/24/metadata issue

[Vanya Seth]

We can try that.

Regards
Vanya

On Tue, Aug 23, 2016 at 2:34 PM, Morten Olav Hansen 
wrote:

> Maybe you should turn of PG logging the DDL statements.. maybe there is
> startdate failed because of xyz, could be useful in hunting down the issue..
>
> --
> Morten Olav Hansen
> Senior Engineer, DHIS 2
> University of Oslo
> http://www.dhis2.org
>
> On Tue, Aug 23, 2016 at 3:55 PM, Vanya Seth 
> wrote:
>
>> Well its very strange as this works fine in our local machines.
>>
>> On the VM's even tried dropping the db, creating new and then deploying
>> the war. Still to no avail.
>>
>> Mostly this manual creation of columns should work. But what if there are
>> other such things that might have been missed and will only come up when we
>> try to do some operations.
>>
>> Regards
>> Vanya
>>
>> On Tue, Aug 23, 2016 at 1:06 PM, Morten Olav Hansen 
>> wrote:
>>
>>> That sounds strange Vanya, looked at the HBM files and there was nothing
>>> special about those fields.
>>>
>>> Could you try a manual add:
>>> alter table mapview add column startdate timestamp without time zone
>>> alter table mapview add column enddate timestamp without time zone
>>>
>>> and see if that fixes it (I haven't seen this issue anywhere else, so
>>> could be something very local)
>>>
>>> --
>>> Morten Olav Hansen
>>> Senior Engineer, DHIS 2
>>> University of Oslo
>>> http://www.dhis2.org
>>>
>>> On Tue, Aug 23, 2016 at 1:59 PM, Vanya Seth 
>>> wrote:
>>>
>>>>
>>>> Hello devs
>>>>
>>>> We were updating our test VM's to 2.24 from 2.21. We did it in an
>>>> incremental manner.
>>>> Apparently on few of the VM's after upgrade the /api/24/metadata (GET)
>>>> call is failing with the following error:
>>>>
>>>> WARN  2016-08-23 11:47:59,957 SQL Error: 0, SQLState: 42703
>>>> (SqlExceptionHelper.java [http-bio-8080-exec-8])
>>>> * ERROR 2016-08-23 11:47:59,957 ERROR: column this_.startdate does not
>>>> exist
>>>>   Position: 463 (SqlExceptionHelper.java [http-bio-8080-exec-8])
>>>> org.hibernate.exception.SQLGrammarException: could not extract
>>>> ResultSet
>>>>
>>>> We checked the startup logs and there was no specific error around
>>>> table update errors. It seems the mapview relation now has two new columns
>>>> 'startdate' and 'enddate'. These are not getting created during the
>>>> deployment and hence the metadata export call is failing.
>>>>
>>>> Tried stopping the server and restarting it multiple times but to no
>>>> avail.
>>>>
>>>> Can you please look into this and let know what could be causing this
>>>> strange issue.
>>>>
>>>> --
>>>> With Regards
>>>> Vanya
>>>>
>>>> ThoughtWorks Technologies
>>>> Hyderabad
>>>>
>>>> --Stay Hungry Stay Foolish!!
>>>>
>>>> ___
>>>> 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
>>>>
>>>>
>>>
>>
>>
>> --
>> With Regards
>> ThoughtWorks Technologies
>> Hyderabad
>>
>> --Stay Hungry Stay Foolish!!
>>
>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] Upgrading to 2.24 and /api/24/metadata issue

[Vanya Seth]

Well its very strange as this works fine in our local machines.

On the VM's even tried dropping the db, creating new and then deploying the
war. Still to no avail.

Mostly this manual creation of columns should work. But what if there are
other such things that might have been missed and will only come up when we
try to do some operations.

Regards
Vanya

On Tue, Aug 23, 2016 at 1:06 PM, Morten Olav Hansen 
wrote:

> That sounds strange Vanya, looked at the HBM files and there was nothing
> special about those fields.
>
> Could you try a manual add:
> alter table mapview add column startdate timestamp without time zone
> alter table mapview add column enddate timestamp without time zone
>
> and see if that fixes it (I haven't seen this issue anywhere else, so
> could be something very local)
>
> --
> Morten Olav Hansen
> Senior Engineer, DHIS 2
> University of Oslo
> http://www.dhis2.org
>
> On Tue, Aug 23, 2016 at 1:59 PM, Vanya Seth 
> wrote:
>
>>
>> Hello devs
>>
>> We were updating our test VM's to 2.24 from 2.21. We did it in an
>> incremental manner.
>> Apparently on few of the VM's after upgrade the /api/24/metadata (GET)
>> call is failing with the following error:
>>
>> WARN  2016-08-23 11:47:59,957 SQL Error: 0, SQLState: 42703
>> (SqlExceptionHelper.java [http-bio-8080-exec-8])
>> * ERROR 2016-08-23 11:47:59,957 ERROR: column this_.startdate does not
>> exist
>>   Position: 463 (SqlExceptionHelper.java [http-bio-8080-exec-8])
>> org.hibernate.exception.SQLGrammarException: could not extract ResultSet
>>
>> We checked the startup logs and there was no specific error around table
>> update errors. It seems the mapview relation now has two new columns
>> 'startdate' and 'enddate'. These are not getting created during the
>> deployment and hence the metadata export call is failing.
>>
>> Tried stopping the server and restarting it multiple times but to no
>> avail.
>>
>> Can you please look into this and let know what could be causing this
>> strange issue.
>>
>> --
>> With Regards
>> Vanya
>>
>> ThoughtWorks Technologies
>> Hyderabad
>>
>> --Stay Hungry Stay Foolish!!
>>
>> ___
>> 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
>>
>>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] scheduling in DHIS

[Vanya Seth]

Hi Halvdan

We will extend the functionality and send a patch.

Regards
Vanya

On Mon, Aug 22, 2016 at 5:57 PM, Halvdan Hoem Grelland 
wrote:

> Vanya,
>
> If you're talking about simply exposing 
> TaskExecutor.submitListenable(Runnable)
> in the Scheduler interface, it's not a big deal. I'd think you could just
> go ahead. Alternately you could wire the AsyncListenableTaskExecutor bean
> directly into the service, I suppose.
>
> On Mon, Aug 22, 2016 at 12:55 PM, Vanya Seth 
> wrote:
>
>> Hi Lars
>>
>> Any comments on this one?
>>
>> Regards
>> Vanya
>>
>> On Wed, Aug 17, 2016 at 12:44 PM, Vanya Seth 
>> wrote:
>>
>>> Hi Lars
>>>
>>> We are looking at extending org.hisp.dhis.system.scheduling.Scheduler to
>>> also have the ability to return the ListenableFuture for a Runnable as
>>> well. This will help us or any dev in the future to check the status of the
>>> ongoing Runnables in the system and provide some user experience around it.
>>>
>>> Please let know if you are ok with us taking it up? As we want to fix a
>>> bug wherein the "sync now" button should not be clickable if the task is
>>> already running.
>>>
>>> Regards
>>> Vanya
>>>
>>>
>>> On Mon, Aug 8, 2016 at 9:26 AM, Aamer Mohammed 
>>> wrote:
>>>
>>>> Hi Lars/Morten,
>>>>
>>>> The scheduling page in DHIS 2.24 has ability to run tasks immediately
>>>> in below sections.
>>>>
>>>>- Metadata Synchronization - Using 'Sync Now' button
>>>>- SMS Scheduler - Using 'Run Now' button
>>>>
>>>> When the user clicks 'Sync Now' button, an asynchronous task is
>>>> triggered in the backend for metadata synchronization. The user can click
>>>> the button again before the synchronization task is even complete. We want
>>>> to prevent this as it can spawn multiple threads in the system all doing
>>>> the same job leading to race conditions in system.
>>>>
>>>> We can do the changes in SchedulingManager.executeTask so that it will
>>>> check the status of the previously submitted task. If it is not running
>>>> then it will start new task or otherwise not. These changes should be
>>>> applicable to any 'executeNow' type tasks in the system.
>>>>
>>>> Does DHIS2 already have such functionality available elsewhere in the
>>>> system? Any thoughts on this approach.
>>>>
>>>>
>>>> Thanks
>>>> Aamer.
>>>>
>>>
>>>
>>>
>>> --
>>> With Regards
>>> ThoughtWorks Technologies
>>> Hyderabad
>>>
>>> --Stay Hungry Stay Foolish!!
>>>
>>
>>
>>
>> --
>> With Regards
>> ThoughtWorks Technologies
>> Hyderabad
>>
>> --Stay Hungry Stay Foolish!!
>>
>> ___
>> 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
>>
>>
>
>
> --
> Halvdan Hoem Grelland
> Software developer, DHIS 2
> University of Oslo
> http://www.dhis2.org <https://www.dhis2.org/>
>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

[Dhis2-devs] Upgrading to 2.24 and /api/24/metadata issue

[Vanya Seth]

Hello devs

We were updating our test VM's to 2.24 from 2.21. We did it in an
incremental manner.
Apparently on few of the VM's after upgrade the /api/24/metadata (GET) call
is failing with the following error:

WARN  2016-08-23 11:47:59,957 SQL Error: 0, SQLState: 42703
(SqlExceptionHelper.java [http-bio-8080-exec-8])
* ERROR 2016-08-23 11:47:59,957 ERROR: column this_.startdate does not
exist
  Position: 463 (SqlExceptionHelper.java [http-bio-8080-exec-8])
org.hibernate.exception.SQLGrammarException: could not extract ResultSet

We checked the startup logs and there was no specific error around table
update errors. It seems the mapview relation now has two new columns
'startdate' and 'enddate'. These are not getting created during the
deployment and hence the metadata export call is failing.

Tried stopping the server and restarting it multiple times but to no avail.

Can you please look into this and let know what could be causing this
strange issue.

-- 
With Regards
Vanya

ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] scheduling in DHIS

[Vanya Seth]

Hi Lars

Any comments on this one?

Regards
Vanya

On Wed, Aug 17, 2016 at 12:44 PM, Vanya Seth 
wrote:

> Hi Lars
>
> We are looking at extending org.hisp.dhis.system.scheduling.Scheduler to
> also have the ability to return the ListenableFuture for a Runnable as
> well. This will help us or any dev in the future to check the status of the
> ongoing Runnables in the system and provide some user experience around it.
>
> Please let know if you are ok with us taking it up? As we want to fix a
> bug wherein the "sync now" button should not be clickable if the task is
> already running.
>
> Regards
> Vanya
>
>
> On Mon, Aug 8, 2016 at 9:26 AM, Aamer Mohammed 
> wrote:
>
>> Hi Lars/Morten,
>>
>> The scheduling page in DHIS 2.24 has ability to run tasks immediately in
>> below sections.
>>
>>- Metadata Synchronization - Using 'Sync Now' button
>>- SMS Scheduler - Using 'Run Now' button
>>
>> When the user clicks 'Sync Now' button, an asynchronous task is triggered
>> in the backend for metadata synchronization. The user can click the button
>> again before the synchronization task is even complete. We want to prevent
>> this as it can spawn multiple threads in the system all doing the same job
>> leading to race conditions in system.
>>
>> We can do the changes in SchedulingManager.executeTask so that it will
>> check the status of the previously submitted task. If it is not running
>> then it will start new task or otherwise not. These changes should be
>> applicable to any 'executeNow' type tasks in the system.
>>
>> Does DHIS2 already have such functionality available elsewhere in the
>> system? Any thoughts on this approach.
>>
>>
>> Thanks
>> Aamer.
>>
>
>
>
> --
> With Regards
> ThoughtWorks Technologies
> Hyderabad
>
> --Stay Hungry Stay Foolish!!
>



-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] scheduling in DHIS

[Vanya Seth]

Hi Lars

We are looking at extending org.hisp.dhis.system.scheduling.Scheduler to
also have the ability to return the ListenableFuture for a Runnable as
well. This will help us or any dev in the future to check the status of the
ongoing Runnables in the system and provide some user experience around it.

Please let know if you are ok with us taking it up? As we want to fix a bug
wherein the "sync now" button should not be clickable if the task is
already running.

Regards
Vanya


On Mon, Aug 8, 2016 at 9:26 AM, Aamer Mohammed 
wrote:

> Hi Lars/Morten,
>
> The scheduling page in DHIS 2.24 has ability to run tasks immediately in
> below sections.
>
>- Metadata Synchronization - Using 'Sync Now' button
>- SMS Scheduler - Using 'Run Now' button
>
> When the user clicks 'Sync Now' button, an asynchronous task is triggered
> in the backend for metadata synchronization. The user can click the button
> again before the synchronization task is even complete. We want to prevent
> this as it can spawn multiple threads in the system all doing the same job
> leading to race conditions in system.
>
> We can do the changes in SchedulingManager.executeTask so that it will
> check the status of the previously submitted task. If it is not running
> then it will start new task or otherwise not. These changes should be
> applicable to any 'executeNow' type tasks in the system.
>
> Does DHIS2 already have such functionality available elsewhere in the
> system? Any thoughts on this approach.
>
>
> Thanks
> Aamer.
>



-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] dhis charts using highcharts and png downloads

[Vanya Seth]

Hi Mark

Would it be possible to provide some insights on this aspect as well? We
are getting inclined towards using highcharts based abstractions. But would
like to hear back from you as well.

Any help will be much appreciated.

Regards
Vanya

On Thu, Jun 30, 2016 at 5:23 PM, Vanya Seth  wrote:

> Hi Mark and Nicolay
>
> Could you please provide some information regarding this?
>
> Regards
> Vanya
>
> On Tue, Jun 28, 2016 at 5:14 PM, Srikanth Katta  > wrote:
>
>> Hi Dhis-devs,
>>
>> *Future plan of chart.js*
>>
>> Is there any future plan to rewrite chart.js using highcharts in place of
>> extJS.
>> Currently we have embedded chart service module from interactive
>> dashboard app into our custom app. To get the high chart object we need
>> analytical object. Currently we are generating the analytical object using
>> dash board controller.
>>
>> *Dhis api to download high chart as png*
>>
>> Currently in interactive dashboard app. When we download the high chart
>> image as PNG, it is calling to the *http://export.highcharts.com
>> <http://export.highcharts.com>* instead do we have any api which does
>> the download as png in the DHIS itself. Or do we have any plans in
>> improving quality of the api/charts/data which is giving a png now and is
>> not as good as the high charts generated chart.
>>
>>
>> Thanks,
>> Srikanth Katta.
>>
>>
>
>
> --
> With Regards
> ThoughtWorks Technologies
> Hyderabad
>
> --Stay Hungry Stay Foolish!!
>



-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] dhis charts using highcharts and png downloads

[Vanya Seth]

Hi Mark and Nicolay

Could you please provide some information regarding this?

Regards
Vanya

On Tue, Jun 28, 2016 at 5:14 PM, Srikanth Katta 
wrote:

> Hi Dhis-devs,
>
> *Future plan of chart.js*
>
> Is there any future plan to rewrite chart.js using highcharts in place of
> extJS.
> Currently we have embedded chart service module from interactive dashboard
> app into our custom app. To get the high chart object we need analytical
> object. Currently we are generating the analytical object using dash board
> controller.
>
> *Dhis api to download high chart as png*
>
> Currently in interactive dashboard app. When we download the high chart
> image as PNG, it is calling to the *http://export.highcharts.com
> * instead do we have any api which does the
> download as png in the DHIS itself. Or do we have any plans in improving
> quality of the api/charts/data which is giving a png now and is not as good
> as the high charts generated chart.
>
>
> Thanks,
> Srikanth Katta.
>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] Bugs in DHIS new importer.

[Vanya Seth]

On Tue, Jun 28, 2016 at 2:05 PM, Morten Olav Hansen 
wrote:

> - Sharing settings will sync only if you change any metadata of that
>> particular element along with change in sharing settings.
>>
>
> I'm not able to replicate this, was able to download objects, and change
> sharing settings (without changing anything else on the object), could you
> tell me more about the object you have been testing? could be specific to a
> particular type maybe
>
@vanyas:  will check again.

>
>
>> - When we create Custom attributes and make them mandatory and assign to
>> a data set (for example) and sync them to local instance, we get a run time
>> exception stating that attribute for dataset not given any value. This is
>> because even if it is mandatory we are not changing the dataset to set the
>> value to attribute.
>>
>
> You mean you are making a metadata attribute as mandatory, but not
> providing a attribute value for it? that should fail of course, but what
> kind of run time exeption do you get? It should have been caught by the
> import validation routines
>
@vanyas: Yes this was caught during the validation phase itself. The point
here would be to catch such issues during configuring metadata itself. The
use case was: We created some data set at HQ, synced to local. Then we
created a custom attribute for data set and made it mandatory. Then when
this version (with custom attribute info) syncs to local, we get this
validation issues with the importer. Any general guideline for such cases.

>
> - Data set - when updated with a data approval workflow - does not sync to
>> local. Everything syncs and association is not syncing
>>
>
> We do not support any data approval types at this point (at least nothing
> has been done to try and support them, it's untested)
>
@vanyas: Whats the plan for this in that case? If its part of metadata this
association should get synced.

>
> - when we updated the existing program with adding combination of
>> categories and synched.
>>
>
> This should be fixed now
>
> - while updating attributes in the program with registration.
>> * ERROR 2016-06-21 21:23:24,325 ERROR: duplicate key value violates
>> unique constraint ""programtrackedentityattribute_unique_key""
>>   Detail: Key (programid, trackedentityattributeid)=(255, 240) already
>> exists. (SqlExceptionHelper.java [taskScheduler-6])
>> * ERROR 2016-06-21 21:23:24,385 Exception occurred while trying to import
>> the metadata. could not execute statement (MetadataImportHandler.java
>> [taskScheduler-6])
>> org.hibernate.exception.ConstraintViolationException: could not execute
>> statement at
>> org.hibernate.exception.internal.SQLStateConversionDelegate.convert(SQLStateConversionDelegate.java:112)"Error
>> on Edit Program Stage page. Press cancel and exception is thrown. Analytics
>> Export Error. Process failed. null.
>>
>
> Please try again, I have done several fixes related to issues like this
> (at least similar issues)
>
@vanyas : Thanks. Sure will check.

>
> - Charts, pivot tables, Report Table/ Pivot Table, Event Report, Event
>> Chart, Validation Rule
>> Metadata Sync failed for the above metadata With the below runtime
>> exception.
>> --- Exception occurred while trying to import the metadata. object
>> references an unsaved transient instance - save the transient instance
>> before flushing: org.hisp.dhis.dataelement.DataElement
>> (MetadataSyncTask.java [taskScheduler-9])
>>
>
> This should be fixed
>
> - Admin user when added to dashboard item is not syncing with metadat sync.
>>
>
> Will look into it
>
> - When deleted a legend at HQ and synced to local. The legend at Local
>> also is deleted on UI (exists in DB). Also, legend is getting duplicated
>> with a different UID in DB.
>>
>
> Will look into it
>
>
>> - Metadata Filter (Import-Export --> Metadata Detailed Export)
>> modification to properties like name, description is successfully synced
>> but the selection is not synced, the payload also have the details of the
>> updated data when synced.
>>
>
> Not sure how much time we should spend on this, the metadata filter
> functionality should be replaced in future releases (it's not very stable,
> and has not been updated to support new types etc)
>
> - custom forms are synced properly when created, but while Updation of
>> custom form not reflecting on UI. However, payload has the full information
>> of updates.
>>
>
> Will look into it, is the issue present for both data set and program
> stages?
>
@vanya: This was tested with data sets only.

>
> --
> Morten
>
>
>>
>>
>>
>>
>>
>> --
>> Thanks & Regards,
>> Nalinikanth M
>> Quality Analyst
>> Email nali...@thoughtworks.com
>> Telephone +91 9052234588 <+91+9052234588>
>> [image: ThoughtWorks]
>> 
>>
>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!

Re: [Dhis2-devs] Bugs found in DHIS2 Application

[Vanya Seth]

Hi Halvdan 

Thanks for the response. We are also testing the new importer functionality . 
We have built metadata synchronisation which is leveraging the new importer 
that got introduced in 2.23. 

Apart from that, yes you are right and we understand that trunk can be OK 
volatile state. But we still wanted to share the issues in case they could have 
been of any help. 

Two issues for which I can provide clarification are :
When the data sync task runs and due to some reason the data import is ignored 
due to conflict. Example the user being used to sync the data is not assigned 
to the org unit for which the data is getting synced . This results in import 
conflicts. The bug here is, the overall Importstatus is success while the 
individual data values show conflict and are ignored. This results in the 
'lastsuccessdate' getting updated in the db. This is wrong. This ways the data 
that actually failed will never be retried . 

Secondly, last week on Friday when we were trying to run the analytics export, 
we were getting a npe.

Hope this helps !

Regards
Vanya
 


Sent from my iPhone

> On 24-Jun-2016, at 8:19 PM, Halvdan Hoem Grelland  wrote:
> 
> Hi,
> 
> As trunk is the development branch of DHIS2, the presence of bugs is to be 
> expected. In particular this last week we've had a few major ones which has 
> caused a range of breaking issues in the Maintenance app (among others).
> 
> That said, I've gone through your list. Some of the items I can reproduce 
> (and we are intending to fix them/they are currently being fixed), whilst for 
> other we require more information and an accurate scenario that we could use 
> to reproduce the issue.
> 
> The following items I cannot reproduce in the current version of trunk:
> - Unable to create more than one orgunit. The organisation unit after created 
> is not reflecting on UI. Existing orgunits also not showing in maintenance 
> app.
> - Unable to edit existing entities (org. units) - UI issue - maintenance app
> - Delete category option, maintenance app continuously reloads. See below in 
> server log org.hibernate.ObjectNotFoundException: No row with the given 
> identifier exists: 
> [org.hisp.dhis.dataelement.DataElementCategoryOptionCombo#116]
> - Error while clicking on Edit Program Stage page. Press cancel and exception 
> is thrown.
> 
> The following are confirmed bugs (currently being worked on):
> - Options sets have a value type - and when assigned to a custom attribute - 
> should take the value type as the value type of option set. But, this is not 
> happenening.
> - Translations behaving wierd. If we add a translation to a dataelement and 
> then updating while updating it is blanked out.
> Custom attributes - even if made mandatory and assigned to data element - the 
> mandatory sign doesn't appear and hence gets created without even giving the 
> attribute value.
> 
> The following has been fixed:
> - Traker capture is not working, The application is not showing up. It is 
> throwing 404 error
> 
> A few points:
> 
> For the Maintenance app we're currently fixing a range of issues and the 
> current version is not really in a testable state. You've touched upon a few 
> aspects such as UI bugs and translations displaying undesirable behaviour. 
> These are expected to be fixed for release. In general: for UI bugs with 
> attributes not showing up and so forth you at the current time have to reload 
> the page for the maintenance app to update the models internally. This is 
> being worked on.
> 
> The importer issues you are having are with the "old" importer which is being 
> phased out. The new one is available on api/24/ and should be used going 
> forwared. That said, the conflict you are describing is actually the expected 
> behaviour (we agree that it is not ideal). I believe Morten talked about this 
> in a separate email recently.
> 
> For the items I have not commented on (and the ones I cannot reproduce) I ask 
> you to do the following:
> Create a reproducible test case on https://play.dhis2.org/dev (or on demo, 
> after 2.24 release)
> Describe the test case in detailed steps so we can easily recreate the issue
> Describe the issue clearly.
> Provide any server log stack traces/errors or console errors IN FULL
> Register each confirmed issuse as a single bug report on launchpad (or as a 
> github issue for Maintenance). Consolidating them into a single list like 
> this makes the bugs a bit harder to track.
> I've added this conversation to the dhis2-devs list.
> 
> Thanks!
> 
> 
>> 
>> -- Forwarded message --
>> From: Nalinikanth Meesala 
>> Date: Thu, Jun 23, 2016 at 2:31 PM
>> Subject: Bugs found in DHIS2 Application
>> To: Lars Helge Øverland , Morten Olav Hansen 
>> 
>> Cc: Theo Krommydakis , twoca 
>> , dhis2-devs 
>> 
>> 
>> Hi Lars & Morten,
>> 
>> I am working for MSF-OCA project from ThoughtWorks. As you are aware that we 
>> are building a metadata synchronisation. We had a bug bash recently an

Re: [Dhis2-devs] [Bug 1538443] Re: Metadata import of users fails

[Vanya Seth]

Hi Morten

The plan to move the UI as well to the new importer functionality was
supposed to be out in 2.24. Is it not the right understanding?

Regards
Vanya

On Fri, Jun 24, 2016 at 4:56 AM, Morten Olav Hansen 
wrote:

> It's only available as a API at this point (probably will be changed in
> 2.25), and yes you can import multiple users at the same time.
>
> If you are using json you can use something like this:
> curl -X POST -d @file.json -H "Content-Type: application/json" -u
> username:password http://server/api/23/metadata
>
> Or xml:
> curl -X POST -d @file.xml -H "Content-Type: application/xml" -u
> username:password http://server/api/23/metadata
>
> You can read more about it here:
> http://dhis2.github.io/dhis2-docs/master/en/developer/html/ch01s14.html
>
> If you are using windows and don't have access to cURL, you can install
> this package:
> https://github.com/bmatzelle/gow
>
> --
> Morten Olav Hansen
> Senior Engineer, DHIS 2
> University of Oslo
> http://www.dhis2.org
>
> On Fri, Jun 24, 2016 at 5:05 AM,  wrote:
>
>> ‎Hello Morten,
>>
>> Would the upgrade to 2.23 allow me to do the import from the metadata
>> import app or I would have to do it from the API?
>> If I had to do it from the API, is there step-by-step guidance on how to
>> do this? I have to import 59 users and would I have to do that one after
>> the other or as a batch?
>>
>> Thank you.
>>
>> Regards,
>>
>>
>> Ifeanyi
>>
>>   Original Message
>> From: Morten Olav Hansen
>> Sent: Thursday, 23 June 2016 17:56
>> To: dhis2-devs@lists.launchpad.net
>> Reply To: Bug 1538443
>> Subject: Re: [Dhis2-devs] [Bug 1538443] Re: Metadata import of users fails
>>
>>
>> Hi
>>
>> Are you able to update to 2.23? in 2.23 we have a new importer at the
>> /api/23/metadata endpoint which has much better support for (among other
>> types) users
>>
>> --
>> Morten Olav Hansen
>> Senior Engineer, DHIS 2
>> University of Oslo
>> http://www.dhis2.org
>>
>> On Thu, Jun 23, 2016 at 6:13 PM, Ifeanyi Okoye <
>> 1538...@bugs.launchpad.net>
>> wrote:
>>
>> > Hello,
>> > I am trying to move data from one instance of DHIS2 (2.22) to another
>> > using metadata export and import. So far everything else has worked
>> except
>> > for importing users. It just goes on indefinitely.
>> >
>> > Please see the logs below:
>> >
>> > * ERROR 2016-06-23 01:31:31,479 Unexpected error occurred in scheduled
>> > task. (TaskUtils.java [taskScheduler-2])
>> > org.hibernate.TransientObjectException: object references an unsaved
>> > transient instance - save the transient instance before flushing:
>> > org.hisp.dhis.user.User
>> > at
>> >
>> org.hibernate.engine.internal.ForeignKeys.getEntityIdentifierIfNotUnsaved(ForeignKeys.java:249)
>> > at org.hibernate.type.EntityType.getIdentifier(EntityType.java:536)
>> > at org.hibernate.type.ManyToOneType.isDirty(ManyToOneType.java:311)
>> > at org.hibernate.type.ManyToOneType.isDirty(ManyToOneType.java:321)
>> > at org.hibernate.type.TypeHelper.findDirty(TypeHelper.java:294)
>> > at
>> >
>> org.hibernate.persister.entity.AbstractEntityPersister.findDirty(AbstractEntityPersister.java:4049)
>> > at
>> >
>> org.hibernate.event.internal.DefaultFlushEntityEventListener.dirtyCheck(DefaultFlushEntityEventListener.java:537)
>> > at
>> >
>> org.hibernate.event.internal.DefaultFlushEntityEventListener.isUpdateNecessary(DefaultFlushEntityEventListener.java:235)
>> > at
>> >
>> org.hibernate.event.internal.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:164)
>> > at
>> >
>> org.hibernate.event.internal.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:230)
>> > at
>> >
>> org.hibernate.event.internal.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:100)
>> > at
>> >
>> org.hibernate.event.internal.DefaultAutoFlushEventListener.onAutoFlush(DefaultAutoFlushEventListener.java:61)
>> > at
>> >
>> org.hibernate.internal.SessionImpl.autoFlushIfRequired(SessionImpl.java:1166)
>> > at org.hibernate.internal.SessionImpl.list(SessionImpl.java:1223)
>> > at org.hibernate.internal.QueryImpl.list(QueryImpl.java:101)
>> > at
>> >
>> org.hibernate.internal.AbstractQueryImpl.uniqueResult(AbstractQueryImpl.java:909)
>> > at
>> >
>> org.hisp.dhis.user.hibernate.HibernateUserCredentialsStore.getUserCredentialsByUsername(HibernateUserCredentialsStore.java:48)
>> > at
>> >
>> org.hisp.dhis.user.DefaultUserService.getUserCredentialsByUsername(DefaultUserService.java:567)
>> > at sun.reflect.GeneratedMethodAccessor204.invoke(Unknown Source)
>> > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>> > at java.lang.reflect.Method.invoke(Unknown Source)
>> > at
>> >
>> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
>> > at
>> >
>> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190)
>> > at
>> >
>> org.springframework.aop.framework.ReflectiveMet

Re: [Dhis2-devs] Plan for merging in trunk for 2.24

[Vanya Seth]

Awesome. Thanks a lot.

Will keep you posted.

Regards
Vanya

On Fri, Jun 17, 2016 at 4:16 PM, Lars Helge Øverland  wrote:

> Hi Vanya,
>
> that is great. Thanks for the effort.
>
> We have a code freeze on Monday 20th, but we can make an exception for
> this.
>
> Just let us know the link to your branch and when its time for us to
> review the code.
>
> best regards,
>
> Lars
>
>
>
>
> On Fri, Jun 17, 2016 at 12:36 PM, Vanya Seth 
> wrote:
>
>>
>> Hi Lars and Team,
>>
>> We are closing down on the metadata sync work. We are looking at 22 June
>> for being able to finish the remaining pieces.
>>
>> I wanted to understand as to how do we move ahead with the merge into
>> trunk?
>>
>> I see that we can propose for merging with in launchpad itself. Please
>> let know what makes sense and how to go about it?
>>
>> After the merge to trunk, we will continue to test it further and add
>> automation tests( we are working with Jason Pickering for the same).In the
>> event of any bugs that we uncover during that time, would we be able to
>> port those fixes back to trunk?
>>
>> It would be good if you could keep us in loop for the various milestone
>> dates that the  DHIS core team is going through.
>>
>> --
>> With Regards
>> Vanya
>> ThoughtWorks Technologies
>> Hyderabad
>>
>> --Stay Hungry Stay Foolish!!
>>
>
>
>
> --
> Lars Helge Øverland
> Lead developer, DHIS 2
> University of Oslo
> Skype: larshelgeoverland
> l...@dhis2.org
> http://www.dhis2.org <https://www.dhis2.org/>
>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

[Dhis2-devs] Plan for merging in trunk for 2.24

[Vanya Seth]

Hi Lars and Team,

We are closing down on the metadata sync work. We are looking at 22 June
for being able to finish the remaining pieces.

I wanted to understand as to how do we move ahead with the merge into trunk?

I see that we can propose for merging with in launchpad itself. Please let
know what makes sense and how to go about it?

After the merge to trunk, we will continue to test it further and add
automation tests( we are working with Jason Pickering for the same).In the
event of any bugs that we uncover during that time, would we be able to
port those fixes back to trunk?

It would be good if you could keep us in loop for the various milestone
dates that the  DHIS core team is going through.

-- 
With Regards
Vanya
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] Logging for Metadata sync feature

[Vanya Seth]

Hi Lars

We will make that change.

Regards
Vanya

On Wed, Jun 15, 2016 at 2:37 PM, Lars Helge Øverland  wrote:

>
> Hi Vanya,
>
> I understand your concerns here.
>
> However this is fine with me - this logging is not visible to users and
> there won't even be produced a log file if the sync isn't enabled, so I'm
> fine with you adding a new logger to Log4JLogConfigInitializer. Let me
> know what you think.
>
> best regards,
>
> Lars
>
>
> On Wed, Jun 15, 2016 at 9:37 AM, Vanya Seth 
> wrote:
>
>> Hi Lars
>>
>> The metadata versioning and sync is an optional feature. It totally
>> depends on the deployment strategy that we want to adopt and given that
>> whether we choose to do metadata sync or not.
>>
>> For these reasons adding the metadata sync log as a first class citizen
>> to the Log4JLogConfigInitializer does not sound like a good idea.
>>
>> Let me know your thoughts?
>>
>> Regards
>> Vanya
>>
>> On Wed, Jun 15, 2016 at 12:41 PM, Lars Helge Øverland 
>> wrote:
>>
>>> Hi there,
>>>
>>> okay. It would be great if we do not introduce another way of doing
>>> logging. The problem is that resolving the DHIS2_HOME directory is a bit
>>> complex - the system looks for the system property dhis2.home, the env
>>> variable DHIS2_HOME, then falls back to opt/dhis2. log4j 1 does not support
>>> this type of custom logic directly. Perhaps log4j 2 does it, not exactly
>>> sure, but the upgrade path is a bit tricky.
>>>
>>>
>>>
>>> Could you instead add a new logger in Log4JLogConfigInitializer for
>>> metadata sync? I.e.:
>>>
>>> /logs/dhis-metadata-sync.log
>>>
>>> If you need to set a custom location for your log4j properties for
>>> testing purposes you can already set a custom log4j.properties location,
>>> see docs here:
>>>
>>> http://dhis2.github.io/dhis2-docs/master/en/implementer/html/ch08s08.html
>>>
>>>
>>> regards,
>>>
>>> Lars
>>>
>>>
>>>
>>>
>>> On Wed, Jun 15, 2016 at 8:13 AM, Aamer Mohammed >> > wrote:
>>>
>>>> Hi Lars,
>>>>
>>>> We are using log4j.properties file instead of
>>>> 'Log4JLogConfigInitializer' for metadata sync logging purpose. The FILE
>>>> parameter of FileAppender in log4j.properties needs the value of DHIS2_HOME
>>>> environment variable to save the metadata sync log in the same folder
>>>> location as that of the other logs. We are creating a system property
>>>> specified in VM options when starting the DHIS server to get the value of
>>>> environment variable and log4j.properties file can use that property.
>>>>
>>>> We would be mentioning this in the documentation as well. Would like to
>>>> hear your thoughts regarding this.
>>>>
>>>> Thanks
>>>> Aamer.
>>>>
>>>>
>>>
>>>
>>> --
>>> Lars Helge Øverland
>>> Lead developer, DHIS 2
>>> University of Oslo
>>> Skype: larshelgeoverland
>>> l...@dhis2.org
>>> 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
> l...@dhis2.org
> http://www.dhis2.org <https://www.dhis2.org/>
>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] Logging for Metadata sync feature

[Vanya Seth]

Hi Lars

The metadata versioning and sync is an optional feature. It totally depends
on the deployment strategy that we want to adopt and given that whether we
choose to do metadata sync or not.

For these reasons adding the metadata sync log as a first class citizen to
the Log4JLogConfigInitializer does not sound like a good idea.

Let me know your thoughts?

Regards
Vanya

On Wed, Jun 15, 2016 at 12:41 PM, Lars Helge Øverland 
wrote:

> Hi there,
>
> okay. It would be great if we do not introduce another way of doing
> logging. The problem is that resolving the DHIS2_HOME directory is a bit
> complex - the system looks for the system property dhis2.home, the env
> variable DHIS2_HOME, then falls back to opt/dhis2. log4j 1 does not support
> this type of custom logic directly. Perhaps log4j 2 does it, not exactly
> sure, but the upgrade path is a bit tricky.
>
>
>
> Could you instead add a new logger in Log4JLogConfigInitializer for
> metadata sync? I.e.:
>
> /logs/dhis-metadata-sync.log
>
> If you need to set a custom location for your log4j properties for testing
> purposes you can already set a custom log4j.properties location, see docs
> here:
>
> http://dhis2.github.io/dhis2-docs/master/en/implementer/html/ch08s08.html
>
>
> regards,
>
> Lars
>
>
>
>
> On Wed, Jun 15, 2016 at 8:13 AM, Aamer Mohammed 
> wrote:
>
>> Hi Lars,
>>
>> We are using log4j.properties file instead of 'Log4JLogConfigInitializer'
>> for metadata sync logging purpose. The FILE parameter of FileAppender in
>> log4j.properties needs the value of DHIS2_HOME environment variable to save
>> the metadata sync log in the same folder location as that of the other
>> logs. We are creating a system property specified in VM options when
>> starting the DHIS server to get the value of environment variable and
>> log4j.properties file can use that property.
>>
>> We would be mentioning this in the documentation as well. Would like to
>> hear your thoughts regarding this.
>>
>> Thanks
>> Aamer.
>>
>>
>
>
> --
> Lars Helge Øverland
> Lead developer, DHIS 2
> University of Oslo
> Skype: larshelgeoverland
> l...@dhis2.org
> http://www.dhis2.org 
>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] Export Metadata - Error with Content-Type header

[Vanya Seth]

Adding DTO layer makes sense :). It will simplify stuff.

But unless you are looking at versioned DTO's itself, I am not sure how
long a way this might help you with versioning support.

Regards
Vanya

On Wed, Jun 15, 2016 at 9:04 AM, Morten Olav Hansen 
wrote:

> Hi Vanya
>
> It's not so much that we have to / want to remove older versions, it just
> that we can't guarantee more than a few APi versions. Remember that we also
> are not using DTOs yet, so within a few versions, there are bound to be
> incompatibilities in the payloads. Discussions about DTOs are still going
> on.
>
> --
> Morten Olav Hansen
> Senior Engineer, DHIS 2
> University of Oslo
> http://www.dhis2.org
>
> On Tue, Jun 14, 2016 at 7:48 PM, Vanya Seth 
> wrote:
>
>> Hi Morten
>>
>> Supporting API versioning is great but why do we want to get rid of the
>> previous versions as you explained in your email.
>> Well the whole point of supporting versioning is to let people continue
>> to use the older versions without the fear of breaking anything.
>> I can understand that we might not support it  (like bug fixing etc). But
>> completely getting rid of it ??
>>
>> Regards
>> Vanya
>>
>> On Tue, Jun 14, 2016 at 2:58 PM, Paulo Grácio 
>> wrote:
>>
>>> Ok, works fine with that version. Not sure if you guys are using Docker
>>> but if you are some images can be found here
>>> https://hub.docker.com/r/pgracio/dhis2-web/tags/
>>>
>>> Thanks,
>>> Paulo
>>>
>>> On Tue, Jun 14, 2016 at 10:55 AM Morten Olav Hansen 
>>> wrote:
>>>
>>>> Yes, that should be fine
>>>>
>>>> --
>>>> Morten Olav Hansen
>>>> Senior Engineer, DHIS 2
>>>> University of Oslo
>>>> http://www.dhis2.org
>>>>
>>>> On Tue, Jun 14, 2016 at 3:36 PM, Paulo Grácio 
>>>> wrote:
>>>>
>>>>> Ok, thanks for the clarification.
>>>>>
>>>>> Can I use this war to build a docker image to run system tests?
>>>>> https://www.dhis2.org/download/releases/trunk/dhis.war
>>>>>
>>>>> BR,
>>>>> Paulo
>>>>>
>>>>>
>>>>> On Tue, Jun 14, 2016 at 10:33 AM Morten Olav Hansen 
>>>>> wrote:
>>>>>
>>>>>> Ah, ok.. so in 2.23, only /api/23/metadata endpoint is versioned..
>>>>>> nothing else, everything will be part of 2.24
>>>>>>
>>>>>> --
>>>>>> Morten Olav Hansen
>>>>>> Senior Engineer, DHIS 2
>>>>>> University of Oslo
>>>>>> http://www.dhis2.org
>>>>>>
>>>>>> On Tue, Jun 14, 2016 at 3:29 PM, Paulo Grácio 
>>>>>> wrote:
>>>>>>
>>>>>>> Version:
>>>>>>> 2.23
>>>>>>> Build revision:
>>>>>>> 22991
>>>>>>> Build date:
>>>>>>> 2016-06-10 17:48
>>>>>>>
>>>>>>> On Tue, Jun 14, 2016 at 10:20 AM Morten Olav Hansen <
>>>>>>> mor...@dhis2.org> wrote:
>>>>>>>
>>>>>>>> - In DHIS 2.24 will you keep the API version 23?
>>>>>>>>>
>>>>>>>>
>>>>>>>> Yes, the plan is to keep 3 versions available, for 2.24 /api/23 and
>>>>>>>> /api/24 is available, for 2.25 we will add /api/25, and for 2.26 we 
>>>>>>>> will
>>>>>>>> add /api/26 and remove /api/23
>>>>>>>>
>>>>>>>>
>>>>>>>>> - Are all endpoints versioned? I'm trying to use
>>>>>>>>> http://localhost:8085/api/23/dataElements and it returns 404.
>>>>>>>>> http://localhost:8085/api/dataElements works fine.
>>>>>>>>>
>>>>>>>>
>>>>>>>> Yes, what version are you on?
>>>>>>>>
>>>>>>>> https://play.dhis2.org/dev/api/dataElements.json
>>>>>>>> https://play.dhis2.org/dev/api/23/dataElements.json
>>>>>>>> https://play.dhis2.org/dev/api/24/dataElements.json
>>>>>>>>
>>>>>>>> All works on latest trunk
>>>>>>>>
>>>>>>>> --
>>>>>>>> Morten

Re: [Dhis2-devs] Sync Anonymous Event Data along with coordinates code fix

[Vanya Seth]

Hi Morten

That would be great. Please let us know when you commit the changes. We ll
take a merge from the trunk.

Regards
Vanya

On Wed, Jun 15, 2016 at 9:01 AM, Morten Olav Hansen 
wrote:

> Hi
>
> We usually turn off most of that Jackson auto discovery magic, I see we
> haven't done that properly in Jackson*, I will add
> that now (so it follows JacksonUtils, RenderService etc)
>
> --
> Morten Olav Hansen
> Senior Engineer, DHIS 2
> University of Oslo
> http://www.dhis2.org
>
> On Tue, Jun 14, 2016 at 8:41 PM, Anilkumar Kodi  > wrote:
>
>> Hi Morten,
>>
>> We are doing Anonymous Event data push. As part of that we are also
>> sending coordinates.
>>
>> Coordinate object has 4 public properties which are listed below
>>
>> @JsonProperty( required = true )
>> @JacksonXmlProperty( isAttribute = true )
>> public Double getLatitude()
>>
>> @JsonProperty( required = true )
>> @JacksonXmlProperty( isAttribute = true )
>> public Double getLongitude()
>>
>> public boolean isValid()
>>
>> public String getCoordinateString()
>>
>>
>> We don't have @JsonIgnore/@JsonProperty on the Other 2 properties.
>>
>> Because of this we are getting Error while Deserializing.
>>
>> Moreover, the JSON Mapper for the class   has 
>> configuration FAIL_ON_UNKNOWN_PROPERTIES  set to *true*
>>
>> We have fixed this by adding @JsonIgnore on those properties.
>>
>> We Would like to know if you see any downstream issues with this minor 
>> change.
>>
>>
>>
>> Thanks,
>>
>> Anil Kumar & Srikanth
>>
>>
>>
>>
>>
>>
>
> ___
> 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
>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] MetadataVersion to be shown in the "About" section

[Vanya Seth]

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.

Regards
Vanya

On Mon, Jun 13, 2016 at 3:52 PM, Lars Helge Øverland  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 
> 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 
>> 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 
>>> 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
>>> l...@dhis2.org
>>> 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
> l...@dhis2.org
> http://www.dhis2.org <https://www.dhis2.org/>
>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] Export Metadata - Error with Content-Type header

[Vanya Seth]

Hi Morten

Supporting API versioning is great but why do we want to get rid of the
previous versions as you explained in your email.
Well the whole point of supporting versioning is to let people continue to
use the older versions without the fear of breaking anything.
I can understand that we might not support it  (like bug fixing etc). But
completely getting rid of it ??

Regards
Vanya

On Tue, Jun 14, 2016 at 2:58 PM, Paulo Grácio  wrote:

> Ok, works fine with that version. Not sure if you guys are using Docker
> but if you are some images can be found here
> https://hub.docker.com/r/pgracio/dhis2-web/tags/
>
> Thanks,
> Paulo
>
> On Tue, Jun 14, 2016 at 10:55 AM Morten Olav Hansen 
> wrote:
>
>> Yes, that should be fine
>>
>> --
>> Morten Olav Hansen
>> Senior Engineer, DHIS 2
>> University of Oslo
>> http://www.dhis2.org
>>
>> On Tue, Jun 14, 2016 at 3:36 PM, Paulo Grácio 
>> wrote:
>>
>>> Ok, thanks for the clarification.
>>>
>>> Can I use this war to build a docker image to run system tests?
>>> https://www.dhis2.org/download/releases/trunk/dhis.war
>>>
>>> BR,
>>> Paulo
>>>
>>>
>>> On Tue, Jun 14, 2016 at 10:33 AM Morten Olav Hansen 
>>> wrote:
>>>
 Ah, ok.. so in 2.23, only /api/23/metadata endpoint is versioned..
 nothing else, everything will be part of 2.24

 --
 Morten Olav Hansen
 Senior Engineer, DHIS 2
 University of Oslo
 http://www.dhis2.org

 On Tue, Jun 14, 2016 at 3:29 PM, Paulo Grácio 
 wrote:

> Version:
> 2.23
> Build revision:
> 22991
> Build date:
> 2016-06-10 17:48
>
> On Tue, Jun 14, 2016 at 10:20 AM Morten Olav Hansen 
> wrote:
>
>> - In DHIS 2.24 will you keep the API version 23?
>>>
>>
>> Yes, the plan is to keep 3 versions available, for 2.24 /api/23 and
>> /api/24 is available, for 2.25 we will add /api/25, and for 2.26 we will
>> add /api/26 and remove /api/23
>>
>>
>>> - Are all endpoints versioned? I'm trying to use
>>> http://localhost:8085/api/23/dataElements and it returns 404.
>>> http://localhost:8085/api/dataElements works fine.
>>>
>>
>> Yes, what version are you on?
>>
>> https://play.dhis2.org/dev/api/dataElements.json
>> https://play.dhis2.org/dev/api/23/dataElements.json
>> https://play.dhis2.org/dev/api/24/dataElements.json
>>
>> All works on latest trunk
>>
>> --
>> Morten
>>
>>
>>> Thanks,
>>> Paulo
>>>
>>> On Tue, Jun 14, 2016 at 4:35 AM Morten Olav Hansen 
>>> wrote:
>>>
 Hi Jason

 Yes, the idea is that your app should target a specific API
 version. We are discussing letting /api/ always be the latest, -but- 
 one of
 the reasons for adding versioning at all, was that we wanted to make 
 more
 breaking changes... so if you app only targets /api/ and not 
 /api/{version}
 there is a bigger risk that your app will break going forward.

 --
 Morten Olav Hansen
 Senior Engineer, DHIS 2
 University of Oslo
 http://www.dhis2.org

 On Tue, Jun 14, 2016 at 12:18 AM, Jason Pickering <
 jason.p.picker...@gmail.com> wrote:

> Hi Morten,
> I am a bit confused by this. Will we have to provide the explicit
> api version of the current version? So if we are on 2.24,will all API 
> calls
> to the default API require the current version of the server?
>
> Regards,
> Jason
>
> On Mon, Jun 13, 2016, 18:58 Paulo Grácio 
> wrote:
>
>> Ok, will create the tests based on /api/23/metadata.
>>
>> Thanks,
>> Paulo
>>
>> On Mon, Jun 13, 2016 at 11:17 AM Morten Olav Hansen <
>> mor...@dhis2.org> wrote:
>>
>>> No, that won't work right now, that endpoint is anyways getting
>>> deprecated (replaced by /api/23/metadata and /api/24/metadata)
>>>
>>> --
>>> Morten Olav Hansen
>>> Senior Engineer, DHIS 2
>>> University of Oslo
>>> http://www.dhis2.org
>>>
>>> On Mon, Jun 13, 2016 at 4:11 PM, Paulo Grácio <
>>> paulogra...@gmail.com> wrote:
>>>
 Hi Morten,

 yes removing Content type header makes it work but shouldn't it
 work with that header also? It works fine for other GET API calls.

 /Paulo


 On Mon, Jun 13, 2016 at 10:11 AM Morten Olav Hansen <
 mor...@dhis2.org> wrote:

> Hi Paulo
>
> Is there any reason you are doing this request? I assume you
> want XML back? you dont need to set input content-type as you are 
> not
> sending anything, and some of our internal

Re: [Dhis2-devs] MetadataVersion to be shown in the "About" section

[Vanya Seth]

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  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 
> 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
> l...@dhis2.org
> http://www.dhis2.org <https://www.dhis2.org/>
>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

[Dhis2-devs] MetadataVersion to be shown in the "About" section

[Vanya Seth]

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!!
___
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

Re: [Dhis2-devs] Issue with import using the /api/24/metadata (trunk)

[Vanya Seth]

Hi Morten

Thanks for the response. But would it be possible to share some other DB
that DHIS uses for testing?

Regards
Vanya

On Thu, Jun 9, 2016 at 4:38 PM, Morten Olav Hansen  wrote:

> Hi Vanya
>
> Yes, the SL demo database has a bunch of issues.. I wouldn't use that as
> an import/export example.. ;) This database is getting quite old, and has
> been for us for a long time.. so it has issues with invalid lng/lat, too
> short publicAccess fields, etc etc... it needs quite some work to be 100%
> import compatible (a lot of stuff is now being validated on import, which
> does not have
> constraints in the database)
>
> --
> Morten Olav Hansen
> Senior Engineer, DHIS 2
> University of Oslo
> http://www.dhis2.org
>
> On Thu, Jun 9, 2016 at 6:03 PM, Vanya Seth 
> wrote:
>
>> Hi Devs
>>
>> We have been trying to do an export from the demo instance and import it
>> using the API itself.
>> On a clean DB it fails to import all the items.
>>
>> Attached is the log file for the same.
>>
>>
>> --
>> With Regards
>> ThoughtWorks Technologies
>> Hyderabad
>>
>> --Stay Hungry Stay Foolish!!
>>
>> ___
>> 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
>>
>>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] Issue with import using the /api/24/metadata (trunk)

[Vanya Seth]

Hi All

sorry just an update. It was from the *dev* instance. But nonetheless it
should have worked.

Regards
Vanya

On Thu, Jun 9, 2016 at 4:33 PM, Vanya Seth  wrote:

> Hi Devs
>
> We have been trying to do an export from the demo instance and import it
> using the API itself.
> On a clean DB it fails to import all the items.
>
> Attached is the log file for the same.
>
>
> --
> With Regards
> ThoughtWorks Technologies
> Hyderabad
>
> --Stay Hungry Stay Foolish!!
>



-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

[Dhis2-devs] Issue with import using the /api/24/metadata (trunk)

[Vanya Seth]

Hi Devs

We have been trying to do an export from the demo instance and import it
using the API itself.
On a clean DB it fails to import all the items.

Attached is the log file for the same.


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
{
  "status": "ERROR",
  "stats": {
"total": 64,
"created": 0,
"updated": 0,
"deleted": 0,
"ignored": 64
  },
  "typeReports": [
{
  "klass": "org.hisp.dhis.program.Program",
  "stats": {
"total": 0,
"created": 0,
"updated": 0,
"deleted": 0,
"ignored": 0
  }
},
{
  "klass": "org.hisp.dhis.report.Report",
  "stats": {
"total": 0,
"created": 0,
"updated": 0,
"deleted": 0,
"ignored": 0
  }
},
{
  "klass": "org.hisp.dhis.dashboard.DashboardItem",
  "stats": {
"total": 0,
"created": 0,
"updated": 0,
"deleted": 0,
"ignored": 0
  }
},
{
  "klass": "org.hisp.dhis.constant.Constant",
  "stats": {
"total": 0,
"created": 0,
"updated": 0,
"deleted": 0,
"ignored": 0
  }
},
{
  "klass": "org.hisp.dhis.validation.ValidationRuleGroup",
  "stats": {
"total": 0,
"created": 0,
"updated": 0,
"deleted": 0,
"ignored": 0
  }
},
{
  "klass": "org.hisp.dhis.option.Option",
  "stats": {
"total": 0,
"created": 0,
"updated": 0,
"deleted": 0,
"ignored": 0
  }
},
{
  "klass": "org.hisp.dhis.dataelement.CategoryOptionGroup",
  "stats": {
"total": 0,
"created": 0,
"updated": 0,
"deleted": 0,
"ignored": 0
  }
},
{
  "klass": "org.hisp.dhis.program.ProgramTrackedEntityAttribute",
  "stats": {
"total": 0,
"created": 0,
"updated": 0,
"deleted": 0,
"ignored": 0
  }
},
{
  "klass": "org.hisp.dhis.sqlview.SqlView",
  "stats": {
"total": 0,
"created": 0,
"updated": 0,
"deleted": 0,
"ignored": 0
  }
},
{
  "klass": "org.hisp.dhis.dataelement.DataElementGroupSet",
  "stats": {
"total": 0,
"created": 0,
"updated": 0,
"deleted": 0,
"ignored": 0
  }
},
{
  "klass": "org.hisp.dhis.dataapproval.DataApprovalLevel",
  "stats": {
"total": 0,
"created": 0,
"updated": 0,
"deleted": 0,
"ignored": 0
  }
},
{
  "klass": "org.hisp.dhis.user.UserAuthorityGroup",
  "stats": {
"total": 1,
"created": 0,
"updated": 0,
"deleted": 0,
"ignored": 1
  },
  "objectReports": [
{
  "klass": "org.hisp.dhis.user.UserAuthorityGroup",
  "index": 9,
  "errorReports": [
{
  "message": "Property `name` with value `Superuser` on object 
Superuser [Ufph3mGRmMo] (UserAuthorityGroup) already exists on object 
yrB6vc5Ip3r.",
  "mainKlass": "org.hisp.dhis.user.UserAuthorityGroup",
  "errorCode": "E5003"
}
  ]
}
  ]
},
{
  "klass": "org.hisp.dhis.dataelement.DataElement",
  "stats": {
"total": 0,
"created": 0,
"updated": 0,
"deleted": 0,
"ignored": 0
  }
},
{
  "klass": "org.hisp.dhis.dashboard.Dashboard",
  "stats": {
"total": 0,
"created": 0,
"updated": 0,
"deleted": 0,
"ignored": 0
  }
},
{
  "klass": "org.hisp.dhis.attribute.Attribute",
  "stats": {
"total": 0,
"created": 0,
"updated": 0,
"deleted": 0,
"ignored": 0
  }
},
{
  "klass": "org.hisp.dhis.relationship.RelationshipType",
  "stats": {
"total": 0,
"created": 0,
"updated": 0,
"deleted": 0,
"ignored": 0
  }
},
{
  "klass": "org.hisp.dhis.program.ProgramDataElement",
  "stats": {
"total": 0,
"created": 0,
"updated": 0,
"deleted": 0,
"ignored": 0
  }
},
{
  "klass": "org.hisp.dhis.organisationunit.OrganisationUnitGroupSet",
  "stats": {
"total": 0,
"created": 0,
"updated": 0,
"deleted": 0,
"ignored": 0
  }
},
{
  "klass": "org.hisp.dhis.trackedentity.TrackedEntity",
  "stats": {
"total": 1,
"created": 0,
"updated": 0,
"deleted": 0,
"ignored": 1
  },
  "objectReports": [
{
  "klass": "org.hisp.dhis.trackedentity.TrackedEntity",
  "index": 6,
  "errorReports": [
{
  "message": "Property `name` with value `Person` on object Person 
[nEenWmSyUEp] (TrackedE

Re: [Dhis2-devs] DHIS2 Documentation for Metadata Sync and Versioning

[Vanya Seth]

Thanks for the information Lars.

Regards
Vanya

On Tue, Jun 7, 2016 at 7:26 AM, Lars Helge Øverland  wrote:

> Hi Vanya,
>
> thanks for taking the time to document this.
>
> Just some suggestions for your question on where to put what:
>
>
>> As we understand that there are 3 manuals
>>
>> - Developer guide
>> - User guide
>> - Implementor guide
>>
>> When we do the documentation are we targeting all these guides?
>>
>> Some key aspects that we believe are documentation worthy are:
>>
>> - The new API 's (versioning and sync).
>>
>
> Developer guide (API docs)
>
>
>> - The new task (Metadata sync task)
>> - Metadata Versioning and Metadata Sync as a concept.
>> - Best practices around the Metadata versioning setup.
>>
> - Optimization of the initial setup of new field instances given the
>> central-field deployment strategy
>>
>
> I suggest a new chapter in the user manual called "Metadata
> synchronization" for these.
>
>
> http://dhis2.github.io/dhis2-docs/master/en/user/html/dhis2_user_manual_en.html
>
>
>> - The changes to the existing "Settings" app [which is pretty much part
>> of setting up the Synchronization settings and the ability to create new
>> versions by enabling versioning ]
>>
>
> Add to settings chapter in user guide:
>
> http://dhis2.github.io/dhis2-docs/master/en/user/html/ch23.html
>
>
>> - The changes to the "Data Administration" app where we can now also
>> schedule the metadata sync at the time of choice.
>>
>> Add to data administration chapter in user guide:
>
> http://dhis2.github.io/dhis2-docs/master/en/user/html/ch22.html
>
>
>
>
>> It would be good if you could help us get started.
>>
>>
> regards,
>
> Lars
>
>
>> --
>> With Regards
>> Vanya
>> ThoughtWorks Technologies
>> Hyderabad
>>
>> --Stay Hungry Stay Foolish!!
>>
>
>
>
> --
> Lars Helge Øverland
> Lead developer, DHIS 2
> University of Oslo
> Skype: larshelgeoverland
> l...@dhis2.org
> http://www.dhis2.org 
>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] DHIS2 Documentation for Metadata Sync and Versioning

[Vanya Seth]

Thanks for the information Jason.

Regards
Vanya

On Mon, Jun 6, 2016 at 6:26 PM, Jason Pickering  wrote:

> Hi Vanya,
>
> Please have a look here
>
> http://dhis2.github.io/dhis2-docs/2.22/en/implementer/html/apa.html
>
> which describes in a fair amount of detail how to get started with the
> documentation.
>
> You can just submit a pull request through the GitHub repo.
>
> Let us know if you need further information.
>
> Regards,
> Jason
>
>
> On Mon, Jun 6, 2016 at 2:44 PM, Vanya Seth 
> wrote:
>
>> Hi Devs
>>
>> We are now beginning to write documentation for the Metadata Sync and
>> Versioning core features.
>>
>> What are the guidelines for doing this documentation? What tools/wiki are
>> being used for documentation at DHIS. It would be good if you could point
>> us to it.
>>
>> As we understand that there are 3 manuals
>>
>> - Developer guide
>> - User guide
>> - Implementor guide
>>
>> When we do the documentation are we targeting all these guides?
>>
>> Some key aspects that we believe are documentation worthy are:
>>
>> - The new API 's (versioning and sync).
>> - The new task (Metadata sync task)
>> - Metadata Versioning and Metadata Sync as a concept.
>> - Best practices around the Metadata versioning setup.
>> - Optimization of the initial setup of new field instances given the
>> central-field deployment strategy
>> - The changes to the existing "Settings" app [which is pretty much part
>> of setting up the Synchronization settings and the ability to create new
>> versions by enabling versioning ]
>> - The changes to the "Data Administration" app where we can now also
>> schedule the metadata sync at the time of choice.
>>
>> It would be good if you could help us get started.
>>
>> --
>> With Regards
>> Vanya
>> ThoughtWorks Technologies
>> Hyderabad
>>
>> --Stay Hungry Stay Foolish!!
>>
>
>
>
> --
> Jason P. Pickering
> email: jason.p.picker...@gmail.com
> tel:+46764147049
>



-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

[Dhis2-devs] DHIS2 Documentation for Metadata Sync and Versioning

[Vanya Seth]

Hi Devs

We are now beginning to write documentation for the Metadata Sync and
Versioning core features.

What are the guidelines for doing this documentation? What tools/wiki are
being used for documentation at DHIS. It would be good if you could point
us to it.

As we understand that there are 3 manuals

- Developer guide
- User guide
- Implementor guide

When we do the documentation are we targeting all these guides?

Some key aspects that we believe are documentation worthy are:

- The new API 's (versioning and sync).
- The new task (Metadata sync task)
- Metadata Versioning and Metadata Sync as a concept.
- Best practices around the Metadata versioning setup.
- Optimization of the initial setup of new field instances given the
central-field deployment strategy
- The changes to the existing "Settings" app [which is pretty much part of
setting up the Synchronization settings and the ability to create new
versions by enabling versioning ]
- The changes to the "Data Administration" app where we can now also
schedule the metadata sync at the time of choice.

It would be good if you could help us get started.

-- 
With Regards
Vanya
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] Generating a word document in dhis

[Vanya Seth]

Hi Morten

Thanks for the response. We are looking at apache *POI* and *docx4j*. We
are also looking at some node based solutions like *officegen*. There is
one more interesting software that we have evaluated called *pandoc*. This
is a very powerful tool and is capable of converting between different
formats (ODF, openXML document, Microsoft XML, JSON,Markdown..etc).

The general requirements we are looking at are (in case we go through the
server side approach). The API contract is still not clear to us. Will have
to spend some time on it.

But roughly it entails:
- Exposing an API that will take in the content and give out a word
document.
- The input DTO we will have to design which will have the details about
the styling, tables, images, paragraphs (the current requirement)

Does it look like a generic requirement? Would like to hear from about it
from Lars and others as well.

Regards
Vanya



On Mon, Jun 6, 2016 at 1:10 PM, Morten Olav Hansen  wrote:

> Hi
>
> From the server side, what libraries are you looking into? POI? we already
> have POI in the classpath, so at least it wouldn't add any dependencies.
>
> If this is useful generic, I will let Lars answer... maybe you can write a
> bit more about your exact requirements, would you basically be supporting
> `iReport` like reports, just with `.docx` as output instead of `.pdf` ? (so
> that would include, charts, text, etc)
>
> --
> Morten Olav Hansen
> Senior Engineer, DHIS 2
> University of Oslo
> http://www.dhis2.org
>
> On Mon, Jun 6, 2016 at 12:54 PM, Vanya Seth 
> wrote:
>
>> Hi Devs
>>
>> It would be helpful to get your inputs on this aspect.
>>
>> Regards
>> Vanya
>>
>> On Tue, May 31, 2016 at 11:00 AM, Sultanahamar Mohammad <
>> sult...@thoughtworks.com> wrote:
>>
>>> Hi Team,
>>>
>>> We have a use case where we have to generate word document off some
>>> charts, pivot tables and some commentary around them. For this we have
>>> explored some server side libraries. If we have a generic implementation
>>> around this, can we place it in dhis code and expose api. We have looked at
>>> couple of java based and node based libs.
>>> What are your thoughts around this?
>>>
>>> Regards,
>>> Sultan Ahamar.
>>>
>>
>>
>>
>> --
>> With Regards
>> ThoughtWorks Technologies
>> Hyderabad
>>
>> --Stay Hungry Stay Foolish!!
>>
>> ___
>> 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
>>
>>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] Generating a word document in dhis

[Vanya Seth]

Hi Devs

It would be helpful to get your inputs on this aspect.

Regards
Vanya

On Tue, May 31, 2016 at 11:00 AM, Sultanahamar Mohammad <
sult...@thoughtworks.com> wrote:

> Hi Team,
>
> We have a use case where we have to generate word document off some
> charts, pivot tables and some commentary around them. For this we have
> explored some server side libraries. If we have a generic implementation
> around this, can we place it in dhis code and expose api. We have looked at
> couple of java based and node based libs.
> What are your thoughts around this?
>
> Regards,
> Sultan Ahamar.
>



-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] issue with /api/eventReports for fetching data

[Vanya Seth]

Hi Lars,

Thanks for the response.

We evaluated both the approaches.
- Extending the /api/eventReport/ API to support /data  [just like
/reportTables does]
- Leveraging the analytics API to get the data and use some js lib to
render the table

We wanted your opinion on going ahead with the first approach. Do you
foresee any complexities and repercussions that we might have overlooked.

Thanks for the help in advance.

Regards
Vanya


On Mon, May 23, 2016 at 4:47 PM, Lars Helge Øverland  wrote:

> Hi there,
>
> okay. Can I ask - are you looking to get the event report data from the
> server in a tabular format (with columns, rows, etc), or do you plan to
> fetch the "plain data source" (as in one column per data dimension) from
> the api and then render the layout of the report in your client side app?
>
>
> best regards,
>
> Lars
>
>
>
> On Mon, May 23, 2016 at 10:45 AM, Vanya Seth 
> wrote:
>
>> Hi Lars
>>
>> Can you please let us know your thoughts about this?
>>
>> Regards
>> Vanya
>>
>> On Fri, May 13, 2016 at 12:57 PM, Vanya Seth 
>> wrote:
>>
>>> Hi Lars
>>>
>>> Hope you are doing well.
>>>
>>> We need to take a decision on it very soon. This is part of our current
>>> iteration. Would it be possible to let us know your thoughts about this?
>>>
>>> Regards
>>> Vanya
>>>
>>> On Wed, May 11, 2016 at 7:07 PM, Archana Chillala <
>>> archa...@thoughtworks.com> wrote:
>>>
>>>> Hi Lars,
>>>>
>>>> We have a use-case for fetching event reports for a custom app that
>>>> we're building. We are planning to extend the API to fetch data for event
>>>> reports. The potential approach we would follow is similar to the way that
>>>> pivot tables api are built i.e. /api/eventReports//data  should fetch
>>>> us appropriate data. The metadata configuration can be fetched using the
>>>> eventReport UID and data can be fetched by using EventAnalyticsService.
>>>>
>>>> Could you please let us know the complexities or the repercussions you
>>>> foresee that go along with extending the API. Any thoughts on this would be
>>>> valuable.
>>>>
>>>> *Cheers,*
>>>>
>>>> Archana Chillala
>>>> Application Developer
>>>> Email archa...@thoughtworks.com
>>>> Telephone +91 9100960533 <+91+9100960533>
>>>> [image: ThoughtWorks]
>>>> <http://www.thoughtworks.com/?utm_campaign=archana-chillala-signature&utm_medium=email&utm_source=thoughtworks-email-signature-generator>
>>>>
>>>> On Tue, May 10, 2016 at 3:00 AM, Lars Helge Øverland 
>>>> wrote:
>>>>
>>>>> Hi Srikanth,
>>>>>
>>>>> this specific feature is one we want to implement, but I cannot
>>>>> promise a delivery date - sorry. This area is quite complex and the event
>>>>> reports is still gaining new features, so this is a moving target and hard
>>>>> to know exactly when we will get time to implement the server version.
>>>>>
>>>>> regards,
>>>>>
>>>>> Lars
>>>>>
>>>>>
>>>>> On Fri, May 6, 2016 at 8:17 AM, Srikanth Katta <
>>>>> srika...@thoughtworks.com> wrote:
>>>>>
>>>>>> Hi Lars,
>>>>>>
>>>>>> Could you please let us know if there is any plan of extending the *event
>>>>>> reports api* for fetching data for 2.24 release. Please let us know
>>>>>> your roadmap to support this functionality.
>>>>>>
>>>>>> Thanks,
>>>>>> Srikanth
>>>>>>
>>>>>> On Mon, May 2, 2016 at 6:19 PM, Srikanth Katta <
>>>>>> srika...@thoughtworks.com> wrote:
>>>>>>
>>>>>>> Thank you, Lars
>>>>>>>
>>>>>>> On Mon, May 2, 2016 at 6:10 PM, Lars Helge Øverland 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi Srikanth,
>>>>>>>>
>>>>>>>> unfortunately we do not support this at the moment.
>>>>>>>>
>>>>>>>> You will have to use the aggregate event analytics API for now and
>>>>>>>> construct the table yourself.
>>>>>>>>
>>>>>>>> /

Re: [Dhis2-devs] [Issue] Program description does not get saved

[Vanya Seth]

Thanks Lars.

Regards
Vanya

On Mon, May 23, 2016 at 7:31 PM, Lars Helge Øverland  wrote:

> Hi Vanya,
>
> this has been fixed now in 2.22 -> trunk.
>
> regards,
>
> Lars
>
>
>
> On Fri, May 20, 2016 at 1:12 PM, Vanya Seth 
> wrote:
>
>> Hi Dhis-devs
>>
>> The program description is not getting saved for the 2.23 DHIS released
>> version. This was reported on the trunk but still exists in 2.23.
>> Can you please have a look at this?
>>
>> Regards
>> Vanya
>>
>> On Tue, Mar 29, 2016 at 11:13 AM, Archana Chillala <
>> archa...@thoughtworks.com> wrote:
>>
>>> Hi,
>>>
>>> I am using DHIS version 2.23. Through the programs/attributes module, I
>>> have created a program, added a description to it and saved it. But, when I
>>> later click on 'Edit' program, the description is missing. The program
>>> description gets cleared out even you add one and save it/update it.
>>> However, no errors/exceptions are generated in the logs.
>>>
>>> Is this a known issue? Any thoughts on this?
>>>
>>>
>>> *Thanks*
>>>
>>> Archana Chillala
>>> Application Developer
>>> Email archa...@thoughtworks.com
>>> Telephone +91 9100960533 <+91+9100960533>
>>> [image: ThoughtWorks]
>>> <http://www.thoughtworks.com/?utm_campaign=archana-chillala-signature&utm_medium=email&utm_source=thoughtworks-email-signature-generator>
>>>
>>
>>
>>
>> --
>> With Regards
>> ThoughtWorks Technologies
>> Hyderabad
>>
>> --Stay Hungry Stay Foolish!!
>>
>> ___
>> 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
>>
>>
>
>
> --
> Lars Helge Øverland
> Lead developer, DHIS 2
> University of Oslo
> Skype: larshelgeoverland
> l...@dhis2.org
> http://www.dhis2.org <https://www.dhis2.org/>
>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] [Dhis2-users] Some clarifications for Program indicators

[Vanya Seth]

Sure. No problem.

Regards
Vanya

On Mon, May 23, 2016 at 4:16 PM, Lars Helge Øverland  wrote:

>
>
> On Mon, May 23, 2016 at 12:31 PM, Vanya Seth 
> wrote:
>
>> We would also look into some possibilities ourselves and get back if
>> there's something worth discussing.
>>
>>
> Thanks, that sounds great.
>
> One option could be to ignore time partitioning completely. Another could
> be to have an option for number of years to include for analysis. Let me
> know if you come up with any bright new ideas ;)
>
> best regards,
>
> Lars
>
>
>
>> Regards
>> Vanya
>>
>> On Mon, May 23, 2016 at 3:58 PM, Vanya Seth 
>> wrote:
>>
>>> Thanks a lot for the information Lars.
>>>
>>> Really appreciate it.
>>>
>>> Regards
>>> Vanya
>>>
>>> On Mon, May 23, 2016 at 3:19 PM, Lars Helge Øverland 
>>> wrote:
>>>
>>>> Hi Vanya,
>>>>
>>>> thanks for raising this issue - it's a good question. Having program
>>>> indicators based on a data element / attributes dates instead of event date
>>>> has come up earlier and something we will have to support.
>>>>
>>>> Short story: Currently this is not possible.
>>>>
>>>> Long story: The current event analytics solution has a compromise
>>>> between query performance and flexibility around dates. If you have a look
>>>> at the event analytics tables (e.g. "analytics_event_2015_ebayegv0exc") you
>>>> will see two things:
>>>>
>>>> - The tables are partitioned by year (one analytics table with events
>>>> per year per program) based on event date. This reduces query time since
>>>> the indexes and tables become smaller instead of growing longer infinitely
>>>> as times goes.
>>>>
>>>> - The tables have columns for all period types based on event date.
>>>> This makes it possible to aggregate all periods in a query through
>>>> group-bys on those columns, instead of having to do one query per period,
>>>> and hence improves performance a lot.
>>>>
>>>> All this is great for performance but limits the analysis to be based
>>>> on event date. To partition data one needs a partition key and event date
>>>> is pretty much the only suitable candidate (in addition to program).
>>>>
>>>> So to support aggregation / analytics based on any date from data
>>>> elements/attributes of the events, one must sacrifice some of this and
>>>> basically have one analytics table per program, and have one query per
>>>> aggregation period. This will soon be a very popular requirement so we will
>>>> have to support it - still pondering how to solve this in a way which
>>>> offers required performance and flexibility.
>>>>
>>>>
>>>> best regards,
>>>>
>>>> Lars
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Tue, May 17, 2016 at 1:13 PM, Vanya Seth 
>>>> wrote:
>>>>
>>>>> Hi dhis-devs
>>>>>
>>>>> We are looking at doing some analysis for the Anonymous events. For
>>>>> which we are trying to set up some program indicators.
>>>>>
>>>>> Currently the issue that we face is that the events that DHIS2
>>>>> considers for calculations within a specific reporting period (week, 
>>>>> month)
>>>>> in event reports/visualizer, are the ones whose event date is within that
>>>>> reporting period.
>>>>>
>>>>> *Example of the problem*
>>>>>
>>>>> *Inpatient mortality rate*
>>>>>
>>>>> Relevant data elements: date of discharge, exit mode [death,
>>>>> discharged ...]
>>>>>
>>>>> *Requirement:*
>>>>>
>>>>> - Get all events where the discharge date was within the reporting
>>>>> period (all exits during period)
>>>>>
>>>>> - Get all events where the discharge date was within the reporting
>>>>> period and the exit mode was "death" (deaths during reporting period)
>>>>>
>>>>> - Divide deaths/all exits to get the mortality rate (indicator)
>>>>>
>>>>>

Re: [Dhis2-devs] [Dhis2-users] Some clarifications for Program indicators

[Vanya Seth]

Thanks a lot for the information Lars.

Really appreciate it.

Regards
Vanya

On Mon, May 23, 2016 at 3:19 PM, Lars Helge Øverland  wrote:

> Hi Vanya,
>
> thanks for raising this issue - it's a good question. Having program
> indicators based on a data element / attributes dates instead of event date
> has come up earlier and something we will have to support.
>
> Short story: Currently this is not possible.
>
> Long story: The current event analytics solution has a compromise between
> query performance and flexibility around dates. If you have a look at the
> event analytics tables (e.g. "analytics_event_2015_ebayegv0exc") you will
> see two things:
>
> - The tables are partitioned by year (one analytics table with events per
> year per program) based on event date. This reduces query time since the
> indexes and tables become smaller instead of growing longer infinitely as
> times goes.
>
> - The tables have columns for all period types based on event date. This
> makes it possible to aggregate all periods in a query through group-bys on
> those columns, instead of having to do one query per period, and hence
> improves performance a lot.
>
> All this is great for performance but limits the analysis to be based on
> event date. To partition data one needs a partition key and event date is
> pretty much the only suitable candidate (in addition to program).
>
> So to support aggregation / analytics based on any date from data
> elements/attributes of the events, one must sacrifice some of this and
> basically have one analytics table per program, and have one query per
> aggregation period. This will soon be a very popular requirement so we will
> have to support it - still pondering how to solve this in a way which
> offers required performance and flexibility.
>
>
> best regards,
>
> Lars
>
>
>
>
>
>
>
>
>
>
>
> On Tue, May 17, 2016 at 1:13 PM, Vanya Seth 
> wrote:
>
>> Hi dhis-devs
>>
>> We are looking at doing some analysis for the Anonymous events. For which
>> we are trying to set up some program indicators.
>>
>> Currently the issue that we face is that the events that DHIS2 considers
>> for calculations within a specific reporting period (week, month) in event
>> reports/visualizer, are the ones whose event date is within that reporting
>> period.
>>
>> *Example of the problem*
>>
>> *Inpatient mortality rate*
>>
>> Relevant data elements: date of discharge, exit mode [death, discharged
>> ...]
>>
>> *Requirement:*
>>
>> - Get all events where the discharge date was within the reporting period
>> (all exits during period)
>>
>> - Get all events where the discharge date was within the reporting period
>> and the exit mode was "death" (deaths during reporting period)
>>
>> - Divide deaths/all exits to get the mortality rate (indicator)
>>
>> As an example, if a patient gets admitted in April 2016 and hence the
>> event date is in the April 2016 reporting period. Now say the patient gets
>> discharged in May 2016. But this exit will be calculated in the April 2016
>> reporting period due to considering the event date for analysis.
>> There is no direct way in DHIS where in we can match the reporting period
>> to a date based data elements for filtering out data or also include them
>> in indicators.
>>
>> Any thoughts about how other users have solved these kind of issues would
>> be much appreciated.
>>
>>
>> --
>> With Regards
>> Vanya
>> ThoughtWorks Technologies
>> Hyderabad
>>
>> --Stay Hungry Stay Foolish!!
>>
>> ___
>> Mailing list: https://launchpad.net/~dhis2-users
>> Post to : dhis2-us...@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~dhis2-users
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> Lars Helge Øverland
> Lead developer, DHIS 2
> University of Oslo
> Skype: larshelgeoverland
> l...@dhis2.org
> http://www.dhis2.org <https://www.dhis2.org/>
>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] [Dhis2-users] Some clarifications for Program indicators

[Vanya Seth]

We would also look into some possibilities ourselves and get back if
there's something worth discussing.

Regards
Vanya

On Mon, May 23, 2016 at 3:58 PM, Vanya Seth  wrote:

> Thanks a lot for the information Lars.
>
> Really appreciate it.
>
> Regards
> Vanya
>
> On Mon, May 23, 2016 at 3:19 PM, Lars Helge Øverland 
> wrote:
>
>> Hi Vanya,
>>
>> thanks for raising this issue - it's a good question. Having program
>> indicators based on a data element / attributes dates instead of event date
>> has come up earlier and something we will have to support.
>>
>> Short story: Currently this is not possible.
>>
>> Long story: The current event analytics solution has a compromise between
>> query performance and flexibility around dates. If you have a look at the
>> event analytics tables (e.g. "analytics_event_2015_ebayegv0exc") you will
>> see two things:
>>
>> - The tables are partitioned by year (one analytics table with events per
>> year per program) based on event date. This reduces query time since the
>> indexes and tables become smaller instead of growing longer infinitely as
>> times goes.
>>
>> - The tables have columns for all period types based on event date. This
>> makes it possible to aggregate all periods in a query through group-bys on
>> those columns, instead of having to do one query per period, and hence
>> improves performance a lot.
>>
>> All this is great for performance but limits the analysis to be based on
>> event date. To partition data one needs a partition key and event date is
>> pretty much the only suitable candidate (in addition to program).
>>
>> So to support aggregation / analytics based on any date from data
>> elements/attributes of the events, one must sacrifice some of this and
>> basically have one analytics table per program, and have one query per
>> aggregation period. This will soon be a very popular requirement so we will
>> have to support it - still pondering how to solve this in a way which
>> offers required performance and flexibility.
>>
>>
>> best regards,
>>
>> Lars
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On Tue, May 17, 2016 at 1:13 PM, Vanya Seth 
>> wrote:
>>
>>> Hi dhis-devs
>>>
>>> We are looking at doing some analysis for the Anonymous events. For
>>> which we are trying to set up some program indicators.
>>>
>>> Currently the issue that we face is that the events that DHIS2 considers
>>> for calculations within a specific reporting period (week, month) in event
>>> reports/visualizer, are the ones whose event date is within that reporting
>>> period.
>>>
>>> *Example of the problem*
>>>
>>> *Inpatient mortality rate*
>>>
>>> Relevant data elements: date of discharge, exit mode [death, discharged
>>> ...]
>>>
>>> *Requirement:*
>>>
>>> - Get all events where the discharge date was within the reporting
>>> period (all exits during period)
>>>
>>> - Get all events where the discharge date was within the reporting
>>> period and the exit mode was "death" (deaths during reporting period)
>>>
>>> - Divide deaths/all exits to get the mortality rate (indicator)
>>>
>>> As an example, if a patient gets admitted in April 2016 and hence the
>>> event date is in the April 2016 reporting period. Now say the patient gets
>>> discharged in May 2016. But this exit will be calculated in the April 2016
>>> reporting period due to considering the event date for analysis.
>>> There is no direct way in DHIS where in we can match the reporting
>>> period to a date based data elements for filtering out data or also include
>>> them in indicators.
>>>
>>> Any thoughts about how other users have solved these kind of issues
>>> would be much appreciated.
>>>
>>>
>>> --
>>> With Regards
>>> Vanya
>>> ThoughtWorks Technologies
>>> Hyderabad
>>>
>>> --Stay Hungry Stay Foolish!!
>>>
>>> ___
>>> Mailing list: https://launchpad.net/~dhis2-users
>>> Post to : dhis2-us...@lists.launchpad.net
>>> Unsubscribe : https://launchpad.net/~dhis2-users
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>>
>> --
>> Lars Helge Øverland
>> Lead developer, DHIS 2
>> University of Oslo
>> Skype: larshelgeoverland
>> l...@dhis2.org
>> http://www.dhis2.org <https://www.dhis2.org/>
>>
>>
>
>
> --
> With Regards
> ThoughtWorks Technologies
> Hyderabad
>
> --Stay Hungry Stay Foolish!!
>



-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] Some clarifications for Program indicators

[Vanya Seth]

Hi devs and users

Would anyone with relevant experience in this, help us understand this
better?

Regards
Vanya

On Tue, May 17, 2016 at 4:43 PM, Vanya Seth  wrote:

> Hi dhis-devs
>
> We are looking at doing some analysis for the Anonymous events. For which
> we are trying to set up some program indicators.
>
> Currently the issue that we face is that the events that DHIS2 considers
> for calculations within a specific reporting period (week, month) in event
> reports/visualizer, are the ones whose event date is within that reporting
> period.
>
> *Example of the problem*
>
> *Inpatient mortality rate*
>
> Relevant data elements: date of discharge, exit mode [death, discharged
> ...]
>
> *Requirement:*
>
> - Get all events where the discharge date was within the reporting period
> (all exits during period)
>
> - Get all events where the discharge date was within the reporting period
> and the exit mode was "death" (deaths during reporting period)
>
> - Divide deaths/all exits to get the mortality rate (indicator)
>
> As an example, if a patient gets admitted in April 2016 and hence the
> event date is in the April 2016 reporting period. Now say the patient gets
> discharged in May 2016. But this exit will be calculated in the April 2016
> reporting period due to considering the event date for analysis.
> There is no direct way in DHIS where in we can match the reporting period
> to a date based data elements for filtering out data or also include them
> in indicators.
>
> Any thoughts about how other users have solved these kind of issues would
> be much appreciated.
>
>
> --
> With Regards
> Vanya
> ThoughtWorks Technologies
> Hyderabad
>
> --Stay Hungry Stay Foolish!!
>



-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] issue with /api/eventReports for fetching data

[Vanya Seth]

Hi Lars

Can you please let us know your thoughts about this?

Regards
Vanya

On Fri, May 13, 2016 at 12:57 PM, Vanya Seth 
wrote:

> Hi Lars
>
> Hope you are doing well.
>
> We need to take a decision on it very soon. This is part of our current
> iteration. Would it be possible to let us know your thoughts about this?
>
> Regards
> Vanya
>
> On Wed, May 11, 2016 at 7:07 PM, Archana Chillala <
> archa...@thoughtworks.com> wrote:
>
>> Hi Lars,
>>
>> We have a use-case for fetching event reports for a custom app that we're
>> building. We are planning to extend the API to fetch data for event
>> reports. The potential approach we would follow is similar to the way that
>> pivot tables api are built i.e. /api/eventReports//data  should fetch
>> us appropriate data. The metadata configuration can be fetched using the
>> eventReport UID and data can be fetched by using EventAnalyticsService.
>>
>> Could you please let us know the complexities or the repercussions you
>> foresee that go along with extending the API. Any thoughts on this would be
>> valuable.
>>
>> *Cheers,*
>>
>> Archana Chillala
>> Application Developer
>> Email archa...@thoughtworks.com
>> Telephone +91 9100960533 <+91+9100960533>
>> [image: ThoughtWorks]
>> <http://www.thoughtworks.com/?utm_campaign=archana-chillala-signature&utm_medium=email&utm_source=thoughtworks-email-signature-generator>
>>
>> On Tue, May 10, 2016 at 3:00 AM, Lars Helge Øverland 
>> wrote:
>>
>>> Hi Srikanth,
>>>
>>> this specific feature is one we want to implement, but I cannot promise
>>> a delivery date - sorry. This area is quite complex and the event reports
>>> is still gaining new features, so this is a moving target and hard to know
>>> exactly when we will get time to implement the server version.
>>>
>>> regards,
>>>
>>> Lars
>>>
>>>
>>> On Fri, May 6, 2016 at 8:17 AM, Srikanth Katta <
>>> srika...@thoughtworks.com> wrote:
>>>
>>>> Hi Lars,
>>>>
>>>> Could you please let us know if there is any plan of extending the *event
>>>> reports api* for fetching data for 2.24 release. Please let us know
>>>> your roadmap to support this functionality.
>>>>
>>>> Thanks,
>>>> Srikanth
>>>>
>>>> On Mon, May 2, 2016 at 6:19 PM, Srikanth Katta <
>>>> srika...@thoughtworks.com> wrote:
>>>>
>>>>> Thank you, Lars
>>>>>
>>>>> On Mon, May 2, 2016 at 6:10 PM, Lars Helge Øverland 
>>>>> wrote:
>>>>>
>>>>>> Hi Srikanth,
>>>>>>
>>>>>> unfortunately we do not support this at the moment.
>>>>>>
>>>>>> You will have to use the aggregate event analytics API for now and
>>>>>> construct the table yourself.
>>>>>>
>>>>>> /api/analytics/events/aggregate
>>>>>>
>>>>>> regards,
>>>>>>
>>>>>> Lars
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, May 2, 2016 at 1:28 PM, Srikanth Katta <
>>>>>> srika...@thoughtworks.com> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> We are using latest version of DHIS 2.21
>>>>>>> We have configured reports on Event Reports module and trying to
>>>>>>> fetch data through the API - *.../api/eventReports//data,*  but
>>>>>>> we get no response. We have looked up the documentation on developer 
>>>>>>> manual
>>>>>>>  for web api in *Viewing analytical resource representations*, but
>>>>>>> looks like no resource is provided for the same.
>>>>>>>
>>>>>>> Any help on this would be appreciated.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Srikanth
>>>>>>>
>>>>>>> ___
>>>>>>> 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
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Lars Helge Øverland
>>>>>> Lead developer, DHIS 2
>>>>>> University of Oslo
>>>>>> Skype: larshelgeoverland
>>>>>> http://www.dhis2.org <https://www.dhis2.org/>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> Lars Helge Øverland
>>> Lead developer, DHIS 2
>>> University of Oslo
>>> Skype: larshelgeoverland
>>> l...@dhis2.org
>>> http://www.dhis2.org <https://www.dhis2.org/>
>>>
>>>
>>
>
>
> --
> With Regards
> ThoughtWorks Technologies
> Hyderabad
>
> --Stay Hungry Stay Foolish!!
>



-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] [DHIS] Updating Program Version

[Vanya Seth]

Hi Abyot

This bug still exists in the latest 2.23 version. Can you please have a
look at this?

Regards
Vanya

On Mon, Mar 28, 2016 at 5:53 PM, Archana Chillala  wrote:

> Thanks, Abyot.
>
> Archana Chillala
> Application Developer
> Email archa...@thoughtworks.com
> Telephone +91 9100960533 <+91+9100960533>
> [image: ThoughtWorks]
> 
>
> On Mon, Mar 28, 2016 at 4:48 PM, Abyot Asalefew Gizaw 
> wrote:
>
>> Hi,
>>
>> When to increase a version is really tricky - there are lots of scenarios
>> / changes that trigger or do not trigger version increment.
>>
>> For now, we will fix for a program version not to increment when there is
>> no change at all.
>>
>> --
>> Abyot A. Gizaw.
>> Senior Engineer, DHIS2
>> University of Oslo
>> http://www.dhis2.org
>>
>> On Mon, Mar 28, 2016 at 12:48 PM, Archana Chillala <
>> archa...@thoughtworks.com> wrote:
>>
>>> Hi,
>>>
>>> Could you please provide any update on this? Program version gets
>>> incremented by when update button is clicked, even if there are no actual
>>> changes made to the program. Currently using DHIS version 2.23.
>>>
>>> Thank you.
>>>
>>> Archana Chillala
>>> Application Developer
>>> Email archa...@thoughtworks.com
>>> Telephone +91 9100960533 <+91+9100960533>
>>> [image: ThoughtWorks]
>>> 
>>>
>>> On Wed, Mar 16, 2016 at 3:55 PM, Abyot Asalefew Gizaw 
>>> wrote:
>>>
 Hi,

 I don't know how this is implemented. Yes, it doesn't make sense to
 bump the version while there is no change in the program.

 Otherwise, we need the program version. Even't capture updates its
 cache of programs based on version.



 ---
 Thank you,
 Abyot.

 On Wed, Mar 16, 2016 at 10:41 AM, Morten Olav Hansen 
 wrote:

> Hi
>
> When it comes to the web-api, we do not update the program version for
> every update. I'm not sure exactly why its being done like that in the
> program module.. but I see this comment:
> program.increaseVersion(); //TODO make more fine-grained
>
> So probably they wanted to do something more with it.. Maybe Abyot can
> shed some light on it? is this version flag in use today? I can see it
> being used for doing offline metadata, but then again.. its not very 
> useful
> if the version gets updated regardless of any actual changes..
>
> On Wed, Mar 16, 2016 at 3:53 PM, Archana Chillala <
> archa...@thoughtworks.com> wrote:
>
>> Hi Morten,
>>
>> I am using DHIS version 2.23. In the Program/attributes module, when
>> we create a program, one of the properties of the program - *Version
>> -* is automatically assigned a value 1. When we update the program,
>> the Version value gets incremented by 1 each time. But, even if we do not
>> make any changes to the program and just click update button, the program
>> version still gets incremented by 1.
>>
>> Is this the expected functionality? Could you please explain.
>>
>>
>>
>> *Thanks*
>>
>> Archana Chillala
>> Application Developer
>> Email archa...@thoughtworks.com
>> Telephone +91 9100960533 <+91+9100960533>
>> [image: ThoughtWorks]
>> 
>>
>
>
>
> --
> Morten
>


>>>
>>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] [Issue] Program description does not get saved

[Vanya Seth]

Hi Dhis-devs

The program description is not getting saved for the 2.23 DHIS released
version. This was reported on the trunk but still exists in 2.23.
Can you please have a look at this?

Regards
Vanya

On Tue, Mar 29, 2016 at 11:13 AM, Archana Chillala <
archa...@thoughtworks.com> wrote:

> Hi,
>
> I am using DHIS version 2.23. Through the programs/attributes module, I
> have created a program, added a description to it and saved it. But, when I
> later click on 'Edit' program, the description is missing. The program
> description gets cleared out even you add one and save it/update it.
> However, no errors/exceptions are generated in the logs.
>
> Is this a known issue? Any thoughts on this?
>
>
> *Thanks*
>
> Archana Chillala
> Application Developer
> Email archa...@thoughtworks.com
> Telephone +91 9100960533 <+91+9100960533>
> [image: ThoughtWorks]
> 
>



-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] FIX Ready: Header location for Data Entry tables

[Vanya Seth]

Hi Mark

Thanks a lot. Really appreciate it.

Regards
Vanya

On Wed, May 18, 2016 at 3:48 PM, Mark Polak  wrote:

> Hey all,
>
> Merged your changes into trunk for review by Lars.
>
> http://bazaar.launchpad.net/~dhis2-devs-core/dhis2/trunk/revision/23087
>
> Regards,
>
> Mark
>
> On Wed, May 11, 2016 at 3:25 PM, Sultanahamar Mohammad <
> sult...@thoughtworks.com> wrote:
>
>> Hi Mark,
>>
>> Could you please check the patch and let us know.
>>
>> Regards,
>> Sultan Ahamar.
>>
>> On Thu, May 5, 2016 at 12:59 PM, Sultanahamar Mohammad <
>> sult...@thoughtworks.com> wrote:
>>
>>> Hi Mark,
>>>
>>> I just fixed the issue. Here is the patch that we need to apply on top
>>> of previous patch. Its a change in form.js.
>>>
>>> Regards,
>>> Sultan Ahamar
>>>
>>> On Wed, May 4, 2016 at 10:56 AM, Sultanahamar Mohammad <
>>> sult...@thoughtworks.com> wrote:
>>>
>>>> Hey Mark,
>>>>
>>>> I was able to reproduce that error. Will look into it and let you know.
>>>>
>>>> Regards,
>>>> Sultan Ahamar.
>>>>
>>>> On Tue, May 3, 2016 at 2:54 PM, Sultanahamar Mohammad <
>>>> sult...@thoughtworks.com> wrote:
>>>>
>>>>> Hi Mark,
>>>>>
>>>>> I tried reproducing this scenario. So, I downloaded db dump from
>>>>> dhis2.org. I was not able to reproduce the same. I think there should
>>>>> be something missing in the patch. Will let u know.
>>>>>
>>>>> Regards,
>>>>> Sultan Ahamar.
>>>>>
>>>>> On Tue, May 3, 2016 at 11:29 AM, Sultanahamar Mohammad <
>>>>> sult...@thoughtworks.com> wrote:
>>>>>
>>>>>> Hi Mark,
>>>>>>
>>>>>> I will have a look and get back on this soon.
>>>>>>
>>>>>>   Good day.
>>>>>>
>>>>>> Regards,
>>>>>> Sultan Ahaamr.
>>>>>>
>>>>>> On Mon, May 2, 2016 at 5:48 PM, Mark Polak  wrote:
>>>>>>
>>>>>>> Hey Kaustav,
>>>>>>>
>>>>>>> I'm sorry for taking so long to get back on this. I've applied your
>>>>>>> patch and it looks good. I think we're close to be able to merge it in.
>>>>>>>
>>>>>>> One minor thing i noticed is that when multiple sections are
>>>>>>> rendered and the user searches in  section, the headers of the next 
>>>>>>> section
>>>>>>> are not adjusted correctly. See the screenshot, do you think it's 
>>>>>>> possible
>>>>>>> for you to look into hooking into these searchfields and readjusting the
>>>>>>> headers after the filtering?
>>>>>>>
>>>>>>> [image: Inline image 1]
>>>>>>>
>>>>>>> On Thu, Apr 14, 2016 at 8:06 AM, Vanya Seth >>>>>> > wrote:
>>>>>>>
>>>>>>>> Hi Mark
>>>>>>>>
>>>>>>>> Thanks for the acknowledgement. We really appreciate it.
>>>>>>>>
>>>>>>>> And we understand there is a lot of pressure for the upcoming
>>>>>>>> release. I think we should be good if you have a look at it early next 
>>>>>>>> week.
>>>>>>>>
>>>>>>>> Regards
>>>>>>>> Vanya
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Apr 13, 2016 at 2:40 PM, Mark Polak  wrote:
>>>>>>>>
>>>>>>>>> Hey Kaustav and Vanya,
>>>>>>>>>
>>>>>>>>> Unfortunately i have not yet. We have been very busy with getting
>>>>>>>>> 2.23 out. I hope to be able to look at it soon.
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>>
>>>>>>>>> Mark
>>>>>>>>>
>>>>>>>>> On Mon, Apr 11, 2016 at 11:12 AM, Vanya Seth <
>>>>>>>>> van...@thoughtworks.com> wrote:
>>>>>>>>>
>&g

Re: [Dhis2-devs] play.dhis2.org/demo: admin password not 'district' ?

[Vanya Seth]

Hi Greg

Please try with admin / District1

P.S. I am not the one who changed, just guessed as its the next logical
progression :)

Regards
Vanya

On Wed, May 18, 2016 at 12:49 PM, Greg Rowles  wrote:

> Hi Devs
>
> Any advice? I'm unable to login with admin and district... (have tried
> Chrome, Firefox, Safari and Opera so it's probably not my browser...)
>
> Greg
>
> --
> *Health Information Systems Program - South Africa*
> *- - - - - - - **- - - - - - - **- - - - - - - **- - - - - - - **- - - -
> - *
> Mobile  :073 246 2992
> Landline:   021 851 2216
> Skype:  gregory_rowles
>
> ___
> 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
>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

[Dhis2-devs] Some clarifications for Program indicators

[Vanya Seth]

Hi dhis-devs

We are looking at doing some analysis for the Anonymous events. For which
we are trying to set up some program indicators.

Currently the issue that we face is that the events that DHIS2 considers
for calculations within a specific reporting period (week, month) in event
reports/visualizer, are the ones whose event date is within that reporting
period.

*Example of the problem*

*Inpatient mortality rate*

Relevant data elements: date of discharge, exit mode [death, discharged ...]

*Requirement:*

- Get all events where the discharge date was within the reporting period
(all exits during period)

- Get all events where the discharge date was within the reporting period
and the exit mode was "death" (deaths during reporting period)

- Divide deaths/all exits to get the mortality rate (indicator)

As an example, if a patient gets admitted in April 2016 and hence the event
date is in the April 2016 reporting period. Now say the patient gets
discharged in May 2016. But this exit will be calculated in the April 2016
reporting period due to considering the event date for analysis.
There is no direct way in DHIS where in we can match the reporting period
to a date based data elements for filtering out data or also include them
in indicators.

Any thoughts about how other users have solved these kind of issues would
be much appreciated.


-- 
With Regards
Vanya
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

[Dhis2-devs] New Patch: Header for Data Entry tables

[Vanya Seth]

Hi Mark

Hope you are doing well.

The Data entry web app header patch now has the fixed code. Can you please
have a look at it so that we can get it merged with 2.21 and higher
versions ?

Regards
Vanya



On Wed, May 11, 2016 at 6:55 PM, Sultanahamar Mohammad <
sult...@thoughtworks.com> wrote:

> Hi Mark,
>
> Could you please check the patch and let us know.
>
> Regards,
> Sultan Ahamar.
>
> On Thu, May 5, 2016 at 12:59 PM, Sultanahamar Mohammad <
> sult...@thoughtworks.com> wrote:
>
>> Hi Mark,
>>
>> I just fixed the issue. Here is the patch that we need to apply on top of
>> previous patch. Its a change in form.js.
>>
>> Regards,
>> Sultan Ahamar
>>
>> On Wed, May 4, 2016 at 10:56 AM, Sultanahamar Mohammad <
>> sult...@thoughtworks.com> wrote:
>>
>>> Hey Mark,
>>>
>>> I was able to reproduce that error. Will look into it and let you know.
>>>
>>> Regards,
>>> Sultan Ahamar.
>>>
>>> On Tue, May 3, 2016 at 2:54 PM, Sultanahamar Mohammad <
>>> sult...@thoughtworks.com> wrote:
>>>
>>>> Hi Mark,
>>>>
>>>> I tried reproducing this scenario. So, I downloaded db dump from
>>>> dhis2.org. I was not able to reproduce the same. I think there should
>>>> be something missing in the patch. Will let u know.
>>>>
>>>> Regards,
>>>> Sultan Ahamar.
>>>>
>>>> On Tue, May 3, 2016 at 11:29 AM, Sultanahamar Mohammad <
>>>> sult...@thoughtworks.com> wrote:
>>>>
>>>>> Hi Mark,
>>>>>
>>>>> I will have a look and get back on this soon.
>>>>>
>>>>>   Good day.
>>>>>
>>>>> Regards,
>>>>> Sultan Ahaamr.
>>>>>
>>>>> On Mon, May 2, 2016 at 5:48 PM, Mark Polak  wrote:
>>>>>
>>>>>> Hey Kaustav,
>>>>>>
>>>>>> I'm sorry for taking so long to get back on this. I've applied your
>>>>>> patch and it looks good. I think we're close to be able to merge it in.
>>>>>>
>>>>>> One minor thing i noticed is that when multiple sections are rendered
>>>>>> and the user searches in  section, the headers of the next section are 
>>>>>> not
>>>>>> adjusted correctly. See the screenshot, do you think it's possible for 
>>>>>> you
>>>>>> to look into hooking into these searchfields and readjusting the headers
>>>>>> after the filtering?
>>>>>>
>>>>>> [image: Inline image 1]
>>>>>>
>>>>>> On Thu, Apr 14, 2016 at 8:06 AM, Vanya Seth 
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Mark
>>>>>>>
>>>>>>> Thanks for the acknowledgement. We really appreciate it.
>>>>>>>
>>>>>>> And we understand there is a lot of pressure for the upcoming
>>>>>>> release. I think we should be good if you have a look at it early next 
>>>>>>> week.
>>>>>>>
>>>>>>> Regards
>>>>>>> Vanya
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Apr 13, 2016 at 2:40 PM, Mark Polak  wrote:
>>>>>>>
>>>>>>>> Hey Kaustav and Vanya,
>>>>>>>>
>>>>>>>> Unfortunately i have not yet. We have been very busy with getting
>>>>>>>> 2.23 out. I hope to be able to look at it soon.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> Mark
>>>>>>>>
>>>>>>>> On Mon, Apr 11, 2016 at 11:12 AM, Vanya Seth <
>>>>>>>> van...@thoughtworks.com> wrote:
>>>>>>>>
>>>>>>>>> Hi Mark
>>>>>>>>>
>>>>>>>>> Hope you are doing well.
>>>>>>>>>
>>>>>>>>> Have you had a chance to look at Kaustav's patch?
>>>>>>>>>
>>>>>>>>> Regards
>>>>>>>>> Vanya
>>>>>>>>>
>>>>>>>>> On Thu, Apr 7, 2016 at 12:35 PM, Kau

Re: [Dhis2-devs] [Dhis2-users] Status of ImportSummaries in /api/events

[Vanya Seth]

Hi Morten

So, I am hoping, if its a conflict you will send the ImportSummary status
as Error or Warning.

And would you consider adding a first class status field on the
ImportSummaries object as well. I think it makes sense, as it allows the
consumer of the API to take an overall decision about the Event import.
Let me know if thats doable.

Regards
Vanya

On Thu, May 12, 2016 at 10:34 PM, Morten Olav Hansen 
wrote:

>
> On Thu, May 12, 2016 at 10:03 PM, Markus Bekken 
> wrote:
>
>> Will the https status of the whole call follow the importsummaries status?
>>
>
> No, that's too much of a change. Basically I want ImportSummary/ies to be
> frozen now, minor adjustments can be made, but improvements should be made
> in our new reporting classes.
>
> --
> Morten Olav Hansen
> Senior Engineer, DHIS 2
> University of Oslo
> http://www.dhis2.org
>



-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] issue with /api/eventReports for fetching data

[Vanya Seth]

Hi Lars

Hope you are doing well.

We need to take a decision on it very soon. This is part of our current
iteration. Would it be possible to let us know your thoughts about this?

Regards
Vanya

On Wed, May 11, 2016 at 7:07 PM, Archana Chillala  wrote:

> Hi Lars,
>
> We have a use-case for fetching event reports for a custom app that we're
> building. We are planning to extend the API to fetch data for event
> reports. The potential approach we would follow is similar to the way that
> pivot tables api are built i.e. /api/eventReports//data  should fetch
> us appropriate data. The metadata configuration can be fetched using the
> eventReport UID and data can be fetched by using EventAnalyticsService.
>
> Could you please let us know the complexities or the repercussions you
> foresee that go along with extending the API. Any thoughts on this would be
> valuable.
>
> *Cheers,*
>
> Archana Chillala
> Application Developer
> Email archa...@thoughtworks.com
> Telephone +91 9100960533 <+91+9100960533>
> [image: ThoughtWorks]
> 
>
> On Tue, May 10, 2016 at 3:00 AM, Lars Helge Øverland 
> wrote:
>
>> Hi Srikanth,
>>
>> this specific feature is one we want to implement, but I cannot promise a
>> delivery date - sorry. This area is quite complex and the event reports is
>> still gaining new features, so this is a moving target and hard to know
>> exactly when we will get time to implement the server version.
>>
>> regards,
>>
>> Lars
>>
>>
>> On Fri, May 6, 2016 at 8:17 AM, Srikanth Katta > > wrote:
>>
>>> Hi Lars,
>>>
>>> Could you please let us know if there is any plan of extending the *event
>>> reports api* for fetching data for 2.24 release. Please let us know
>>> your roadmap to support this functionality.
>>>
>>> Thanks,
>>> Srikanth
>>>
>>> On Mon, May 2, 2016 at 6:19 PM, Srikanth Katta <
>>> srika...@thoughtworks.com> wrote:
>>>
 Thank you, Lars

 On Mon, May 2, 2016 at 6:10 PM, Lars Helge Øverland 
 wrote:

> Hi Srikanth,
>
> unfortunately we do not support this at the moment.
>
> You will have to use the aggregate event analytics API for now and
> construct the table yourself.
>
> /api/analytics/events/aggregate
>
> regards,
>
> Lars
>
>
>
>
> On Mon, May 2, 2016 at 1:28 PM, Srikanth Katta <
> srika...@thoughtworks.com> wrote:
>
>> Hi,
>>
>> We are using latest version of DHIS 2.21
>> We have configured reports on Event Reports module and trying to
>> fetch data through the API - *.../api/eventReports//data,*  but
>> we get no response. We have looked up the documentation on developer 
>> manual
>>  for web api in *Viewing analytical resource representations*, but
>> looks like no resource is provided for the same.
>>
>> Any help on this would be appreciated.
>>
>> Thanks,
>> Srikanth
>>
>> ___
>> 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
>>
>>
>
>
> --
> Lars Helge Øverland
> Lead developer, DHIS 2
> University of Oslo
> Skype: larshelgeoverland
> http://www.dhis2.org 
>
>

>>>
>>
>>
>> --
>> Lars Helge Øverland
>> Lead developer, DHIS 2
>> University of Oslo
>> Skype: larshelgeoverland
>> l...@dhis2.org
>> http://www.dhis2.org 
>>
>>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] [Dhis2-users] Status of ImportSummaries in /api/events

[Vanya Seth]

Ok sounds good.

Regards
Vanya

On Thu, May 12, 2016 at 3:44 PM, Morten Olav Hansen 
wrote:

> Hi Vanya
>
> Yes, I agree it's not correct. I just want to wait for feedback from Abyot
> or Markus before I change anything, so it won't break EC/TC.
>
> --
> Morten Olav Hansen
> Senior Engineer, DHIS 2
> University of Oslo
> http://www.dhis2.org
>
> On Thu, May 12, 2016 at 4:51 PM, henri claude moungui <
> henrimoun...@yahoo.fr> wrote:
>
>> Hi all.
>> wasn't the Dry Run option at "yes" ?
>> If this is the case, maybe after resolving the conflict of the  category
>> option identifier: U8vu31ybiD5 , Aamer will have to retry by setting the
>> Dry Run at "No"
>>
>> Hope this helps...if I'm not out of the lines..
>>
>> Henri
>>
>>
>>
>>
>> Le Jeudi 12 mai 2016 10h33, Vanya Seth  a écrit
>> :
>>
>>
>> Hi Morten
>>
>> As mentioned earlier. We are working on the events data sync. And this
>> specific issue is in the /events POST API.
>>
>> The idea is to retry the event data sync if there is any conflict (where
>> essentially some data has not sycned ). Treating a CONFLICT as a SUCCESS
>> does not sound like a good idea.
>>
>> Apart from that would the /api/events POST be able to update the same
>> event again if retried. Am coming probably from the
>> "attributecategoryoptioncomboid" field.
>>
>> Regards
>> Vanya
>>
>> On Thu, May 12, 2016 at 12:26 PM, Morten Olav Hansen 
>> wrote:
>>
>> No, I mean for the new DXF2 importer, I'm sorry (I assume you are also
>> working on the metadata sync importer). The event importer has not had any
>> changes done.
>>
>> --
>> Morten Olav Hansen
>> Senior Engineer, DHIS 2
>> University of Oslo
>> http://www.dhis2.org
>>
>> On Thu, May 12, 2016 at 1:44 PM, Aamer Mohammed 
>> wrote:
>>
>> Thanks Morten for the insight. But we are also on a branch forked off on
>> 2.23 and it is not giving any WARNING kind of status in our case. Any
>> thoughts please?
>>
>>
>> On Thu, May 12, 2016 at 11:46 AM, Morten Olav Hansen 
>> wrote:
>>
>> Hi
>>
>> I agree this is confusing, but I think this is also the case in our old
>> importer. I'm not sure if we want to change it at this point (as we don't
>> want to break any third party clients out there).
>>
>> That said, as you might know, we changed the approach a bit in our new
>> importer, and it is much better at these kind of issues (in your case it
>> would give status=WARNING which means please have a closer look at the
>> report, or ERROR if all failed).
>>
>> We are hoping to have proper web-api versioning coming in 2.24, which
>> means we can potentially clean up these kinds of issues (but that part is
>> not started yet, so let's see).
>>
>> @Abyot: are you using this returned status for anything in your EC/TC
>> apps?
>>
>> --
>> Morten Olav Hansen
>> Senior Engineer, DHIS 2
>> University of Oslo
>> http://www.dhis2.org
>>
>> On Thu, May 12, 2016 at 12:52 PM, Aamer Mohammed > > wrote:
>>
>> Hi
>>
>> We are using /api/events to post event related data and it is being
>> uploaded successfully. The api returns a response of type ImportSummaries
>> which has the status of ImportSummary along with the count of data which is
>> imported/updated.
>> In case of any conflicts being reported in ImportSummary, we observe that
>> the status still shows as SUCCESS.
>>
>> -
>> ImportSummaries {
>> importSummaries = [ImportSummary {
>> status = SUCCESS,
>> description = 'null',
>> importCount = [imports = 2, updates = 0, ignores = 0],
>> conflicts = [ImportConflict {
>> object = 'Illegal category option identifier: U8vu31ybiD5', value =
>>   'U8vu31ybiD5' }],
>> dataSetComplete = 'null',
>> reference = 'jLBehWyIspM',
>> href = '
>> http://msfocamdsynchq.twhosted.com/api/events/jLBehWyIspM'
>> }]
>> }
>> --
>> Is this not an error because the complete import of the event data has
>> not happened. Please suggest.
>>
>> Thanks
>> Aamer.
>>
>>
>>
>>
>>
>>
>>
>> --
>> With Regards
>> ThoughtWorks Technologies
>> Hyderabad
>>
>> --Stay Hungry Stay Foolish!!
>>
>> ___
>> Mailing list: https://launchpad.net/~dhis2-users
>> Post to: dhis2-us...@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~dhis2-users
>> More help  : https://help.launchpad.net/ListHelp
>>
>>
>>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] Status of ImportSummaries in /api/events

[Vanya Seth]

Hi Morten

As mentioned earlier. We are working on the events data sync. And this
specific issue is in the /events POST API.

The idea is to retry the event data sync if there is any conflict (where
essentially some data has not sycned ). Treating a CONFLICT as a SUCCESS
does not sound like a good idea.

Apart from that would the /api/events POST be able to update the same event
again if retried. Am coming probably from the
"attributecategoryoptioncomboid" field.

Regards
Vanya

On Thu, May 12, 2016 at 12:26 PM, Morten Olav Hansen 
wrote:

> No, I mean for the new DXF2 importer, I'm sorry (I assume you are also
> working on the metadata sync importer). The event importer has not had any
> changes done.
>
> --
> Morten Olav Hansen
> Senior Engineer, DHIS 2
> University of Oslo
> http://www.dhis2.org
>
> On Thu, May 12, 2016 at 1:44 PM, Aamer Mohammed 
> wrote:
>
>> Thanks Morten for the insight. But we are also on a branch forked off on
>> 2.23 and it is not giving any WARNING kind of status in our case. Any
>> thoughts please?
>>
>>
>> On Thu, May 12, 2016 at 11:46 AM, Morten Olav Hansen 
>> wrote:
>>
>>> Hi
>>>
>>> I agree this is confusing, but I think this is also the case in our old
>>> importer. I'm not sure if we want to change it at this point (as we don't
>>> want to break any third party clients out there).
>>>
>>> That said, as you might know, we changed the approach a bit in our new
>>> importer, and it is much better at these kind of issues (in your case it
>>> would give status=WARNING which means please have a closer look at the
>>> report, or ERROR if all failed).
>>>
>>> We are hoping to have proper web-api versioning coming in 2.24, which
>>> means we can potentially clean up these kinds of issues (but that part is
>>> not started yet, so let's see).
>>>
>>> @Abyot: are you using this returned status for anything in your EC/TC
>>> apps?
>>>
>>> --
>>> Morten Olav Hansen
>>> Senior Engineer, DHIS 2
>>> University of Oslo
>>> http://www.dhis2.org
>>>
>>> On Thu, May 12, 2016 at 12:52 PM, Aamer Mohammed <
>>> aam...@thoughtworks.com> wrote:
>>>
 Hi

 We are using /api/events to post event related data and it is being
 uploaded successfully. The api returns a response of type ImportSummaries
 which has the status of ImportSummary along with the count of data which is
 imported/updated.
 In case of any conflicts being reported in ImportSummary, we observe
 that the status still shows as SUCCESS.

 -
 ImportSummaries {
 importSummaries = [ImportSummary {
 status = SUCCESS,
 description = 'null',
 importCount = [imports = 2, updates = 0, ignores = 0],
 conflicts = [ImportConflict {
 object = 'Illegal category option identifier: U8vu31ybiD5', value =
 'U8vu31ybiD5' }],
 dataSetComplete = 'null',
 reference = 'jLBehWyIspM',
 href = '
 http://msfocamdsynchq.twhosted.com/api/events/jLBehWyIspM'
 }]
 }
 --
 Is this not an error because the complete import of the event data has
 not happened. Please suggest.

 Thanks
 Aamer.

>>>
>>>
>>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] FIX Ready: Header location for Data Entry tables

[Vanya Seth]

Hi Mark

Thanks for the acknowledgement. We really appreciate it.

And we understand there is a lot of pressure for the upcoming release. I
think we should be good if you have a look at it early next week.

Regards
Vanya



On Wed, Apr 13, 2016 at 2:40 PM, Mark Polak  wrote:

> Hey Kaustav and Vanya,
>
> Unfortunately i have not yet. We have been very busy with getting 2.23
> out. I hope to be able to look at it soon.
>
> Regards,
>
> Mark
>
> On Mon, Apr 11, 2016 at 11:12 AM, Vanya Seth 
> wrote:
>
>> Hi Mark
>>
>> Hope you are doing well.
>>
>> Have you had a chance to look at Kaustav's patch?
>>
>> Regards
>> Vanya
>>
>> On Thu, Apr 7, 2016 at 12:35 PM, Kaustav Chakraborty <
>> kaust...@thoughtworks.com> wrote:
>>
>>> Hello Mark,
>>>
>>> Hope you are doing well.
>>>
>>> In line to our previous discussion we have the desired functionality
>>> ready which was to build a fixed header functionality on DHIS2 data entry
>>> application. This functionality will help the user to understand exactly
>>> for which column they are entering the data.
>>>
>>> To build this functionality we have used an external jQuery library
>>> floatThead <http://mkoryak.github.io/floatThead/>.
>>>
>>> I have attached the patch file along with this mail. Please verify it
>>> and provide inputs, if any.
>>>
>>> We would like to get this merged in 2.21 and higher.
>>>
>>> Thanks in advance.
>>>
>>>
>>>
>>> Regards,
>>>
>>> *Kaustav Chakraborty*
>>> STEP Intern
>>> Email kaust...@thoughtworks.com
>>> Telephone +91 91009 60526 <+91+91009+60526>
>>> [image: ThoughtWorks]
>>> <http://www.thoughtworks.com/?utm_campaign=kaustav-chakraborty-signature&utm_medium=email&utm_source=thoughtworks-email-signature-generator>
>>>
>>> On Fri, Mar 18, 2016 at 3:36 PM, Mark Polak  wrote:
>>>
>>>> Yes that sounds fine to me :)
>>>>
>>>> Good luck!
>>>>
>>>> On Fri, Mar 18, 2016 at 10:18 AM, Kaustav Chakraborty <
>>>> kaust...@thoughtworks.com> wrote:
>>>>
>>>>> Hi Mark,
>>>>>
>>>>> Thank you for that. We also looked for a couple of libraries and found
>>>>> the same with floatThread.
>>>>>
>>>>> I guess we are good to go with this approach.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Regards,
>>>>>
>>>>> *Kaustav Chakraborty*
>>>>> STEP Intern
>>>>> Email kaust...@thoughtworks.com
>>>>> Telephone +91 91009 60526 <+91+91009+60526>
>>>>> [image: ThoughtWorks]
>>>>> <http://www.thoughtworks.com/?utm_campaign=kaustav-chakraborty-signature&utm_medium=email&utm_source=thoughtworks-email-signature-generator>
>>>>>
>>>>> On Fri, Mar 18, 2016 at 2:29 PM, Mark Polak  wrote:
>>>>>
>>>>>> Hey All,
>>>>>>
>>>>>> We should have jQuery available on the page. So it is probably the
>>>>>> most straight forward way to use the floatThread thing.
>>>>>>
>>>>>> The library seems pretty mature. I like that better than the
>>>>>> scrollable table body, as that adds an extra scrollbar.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Mark
>>>>>>
>>>>>> On Fri, Mar 18, 2016 at 9:04 AM, Vanya Seth 
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Mark
>>>>>>>
>>>>>>> Thanks a lot for the response.
>>>>>>>
>>>>>>> The changes are for the section forms only.
>>>>>>>
>>>>>>> Thanks for a good to go. :)
>>>>>>> But if you could also comment on the technical approach presented in
>>>>>>> the first email, it would be very useful.
>>>>>>>
>>>>>>> Regards
>>>>>>> Vanya
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Mar 18, 2016 at 1:16 PM, Mark Polak  wrote:
>>>>>>>
>>>>>>>> Hey Kaustav and Vanya,
>>>>>>>>
>>>>>>>>

Re: [Dhis2-devs] FIX Ready: Header location for Data Entry tables

[Vanya Seth]

Hi Mark

Hope you are doing well.

Have you had a chance to look at Kaustav's patch?

Regards
Vanya

On Thu, Apr 7, 2016 at 12:35 PM, Kaustav Chakraborty <
kaust...@thoughtworks.com> wrote:

> Hello Mark,
>
> Hope you are doing well.
>
> In line to our previous discussion we have the desired functionality ready
> which was to build a fixed header functionality on DHIS2 data entry
> application. This functionality will help the user to understand exactly
> for which column they are entering the data.
>
> To build this functionality we have used an external jQuery library
> floatThead <http://mkoryak.github.io/floatThead/>.
>
> I have attached the patch file along with this mail. Please verify it and
> provide inputs, if any.
>
> We would like to get this merged in 2.21 and higher.
>
> Thanks in advance.
>
>
>
> Regards,
>
> *Kaustav Chakraborty*
> STEP Intern
> Email kaust...@thoughtworks.com
> Telephone +91 91009 60526 <+91+91009+60526>
> [image: ThoughtWorks]
> <http://www.thoughtworks.com/?utm_campaign=kaustav-chakraborty-signature&utm_medium=email&utm_source=thoughtworks-email-signature-generator>
>
> On Fri, Mar 18, 2016 at 3:36 PM, Mark Polak  wrote:
>
>> Yes that sounds fine to me :)
>>
>> Good luck!
>>
>> On Fri, Mar 18, 2016 at 10:18 AM, Kaustav Chakraborty <
>> kaust...@thoughtworks.com> wrote:
>>
>>> Hi Mark,
>>>
>>> Thank you for that. We also looked for a couple of libraries and found
>>> the same with floatThread.
>>>
>>> I guess we are good to go with this approach.
>>>
>>>
>>>
>>>
>>>
>>> Regards,
>>>
>>> *Kaustav Chakraborty*
>>> STEP Intern
>>> Email kaust...@thoughtworks.com
>>> Telephone +91 91009 60526 <+91+91009+60526>
>>> [image: ThoughtWorks]
>>> <http://www.thoughtworks.com/?utm_campaign=kaustav-chakraborty-signature&utm_medium=email&utm_source=thoughtworks-email-signature-generator>
>>>
>>> On Fri, Mar 18, 2016 at 2:29 PM, Mark Polak  wrote:
>>>
>>>> Hey All,
>>>>
>>>> We should have jQuery available on the page. So it is probably the most
>>>> straight forward way to use the floatThread thing.
>>>>
>>>> The library seems pretty mature. I like that better than the scrollable
>>>> table body, as that adds an extra scrollbar.
>>>>
>>>> Regards,
>>>>
>>>> Mark
>>>>
>>>> On Fri, Mar 18, 2016 at 9:04 AM, Vanya Seth 
>>>> wrote:
>>>>
>>>>> Hi Mark
>>>>>
>>>>> Thanks a lot for the response.
>>>>>
>>>>> The changes are for the section forms only.
>>>>>
>>>>> Thanks for a good to go. :)
>>>>> But if you could also comment on the technical approach presented in
>>>>> the first email, it would be very useful.
>>>>>
>>>>> Regards
>>>>> Vanya
>>>>>
>>>>>
>>>>> On Fri, Mar 18, 2016 at 1:16 PM, Mark Polak  wrote:
>>>>>
>>>>>> Hey Kaustav and Vanya,
>>>>>>
>>>>>> Your projected changes are related to section forms (not custom
>>>>>> forms) is that correct?
>>>>>>
>>>>>> For custom forms the users are able to "hack" the html
>>>>>> representation. Therefore they could accidentally break this feature, 
>>>>>> which
>>>>>> makes it seem not reliable.
>>>>>>
>>>>>> So it is for section forms then (the default generated forms) then we
>>>>>> think this would be a welcome feature to go into trunk.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Mark
>>>>>>
>>>>>> On Thu, Mar 17, 2016 at 4:03 PM, Mark Polak  wrote:
>>>>>>
>>>>>>> Hey Vanya,
>>>>>>>
>>>>>>> Thank you for your patience. I'm waiting for a reply from Lars on
>>>>>>> this. Will ask him to confirm again ;)
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Mark
>>>>>>>
>>>>>>> On Thu, Mar 17, 2016 at 3:34 PM, Vanya Seth >>>>>> > wrote:
>>>>>>>

Re: [Dhis2-devs] [DHIS] Program gets unassigned to a user role during metadata export-import

[Vanya Seth]

Hi Morten

In case if its not already handled. Same might be the case for DataSets.
UserRoles have dataset association as well.

Regards
Vanya

On Wed, Mar 23, 2016 at 9:39 AM, Morten Olav Hansen 
wrote:

> Hi again
>
> I'm guessing this is related the circular nature of our metadata, we are
> importing users/userRoles, then program, etc etc.. but userRoles actually
> need to know about programs to attach them.
>
> I will add a postImport hook for this in the new importer. I will have a
> look at it first thing after easter holiday (back on Tuesday).
>
> --
> Morten Olav Hansen
> Senior Engineer, DHIS 2
> University of Oslo
> http://www.dhis2.org
>
> On Wed, Mar 23, 2016 at 10:49 AM, Morten Olav Hansen 
> wrote:
>
>> Hi Archana
>>
>> Could you provide me with a bit more information. When you say your are
>> exporting then importing, are you exporting everything? including users,
>> user roles etc etc?
>>
>> Also, please let us know DHIS version and revision, using legacy importer
>> or new importer (from 2.23)
>>
>> --
>> Morten Olav Hansen
>> Senior Engineer, DHIS 2
>> University of Oslo
>> http://www.dhis2.org
>>
>> On Wed, Mar 23, 2016 at 12:35 AM, Archana Chillala <
>> archa...@thoughtworks.com> wrote:
>>
>>> Thank you, Morten.
>>>
>>
>>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] Header location for Data Entry tables

[Vanya Seth]

Hi Mark and Nicolay

Hope you both are doing well.

Have you had a chance to look into Kaustav's email?

We have started a new iteration and wanted to pick up this work asap.  Any
help would be greatly appreciated.

Thanks in advance
Vanya



On Tue, Mar 15, 2016 at 6:36 PM, Kaustav Chakraborty <
kaust...@thoughtworks.com> wrote:

> Hi Mark
>
> Hope you are doing well.
>
> We want to make some enhancements to the Data entry app.  Which is to make
> the data entry table header ( category combo header ) stay constant even if
> we scroll down the page, so that the user knows which column they are
> entering the data in.
>
>
> These are a few questions,
>
>
> *1. Would this be alright to add this to DHIS?*
>
> *2. If you have any recommendations regarding the implementation of this
> feature? Like using some library or anything of that sort?*
>
>
> At our end we have explored a few things:
>
> *Assume, the table is structured as below,*
>
> table
>
> thead
>
> tr
>
> th
>
> tbody
>
> tr
>
> td
>
>
> *1. Using a Library:*
>
> There is a javascript library called floatThead
>  that can be leveraged for this.
> It also works with multiple tables present in a single page. So while
> scrolling the table header remain fixed for each tables.
>
>
> *2. Not using any library,*
>
> We can have some fixed height given to a table body and put the y-axis
> scroll for the table. User has to come to the table element and scroll to
> get their data element to be seen.
>
>
> I have attached the screenshots for better understanding.
>
> We are waiting for your response.
>
>
>
> Thanks & Regards,
>
> *Kaustav Chakraborty*
> STEP Intern
> Email kaust...@thoughtworks.com
> Telephone +91 91009 60526 <+91+91009+60526>
> [image: ThoughtWorks]
> 
>



-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] Header location for Data Entry tables

[Vanya Seth]

Hi Mark

Thanks a lot for the response.

The changes are for the section forms only.

Thanks for a good to go. :)
But if you could also comment on the technical approach presented in the
first email, it would be very useful.

Regards
Vanya


On Fri, Mar 18, 2016 at 1:16 PM, Mark Polak  wrote:

> Hey Kaustav and Vanya,
>
> Your projected changes are related to section forms (not custom forms) is
> that correct?
>
> For custom forms the users are able to "hack" the html representation.
> Therefore they could accidentally break this feature, which makes it seem
> not reliable.
>
> So it is for section forms then (the default generated forms) then we
> think this would be a welcome feature to go into trunk.
>
> Regards,
>
> Mark
>
> On Thu, Mar 17, 2016 at 4:03 PM, Mark Polak  wrote:
>
>> Hey Vanya,
>>
>> Thank you for your patience. I'm waiting for a reply from Lars on this.
>> Will ask him to confirm again ;)
>>
>> Regards,
>>
>> Mark
>>
>> On Thu, Mar 17, 2016 at 3:34 PM, Vanya Seth 
>> wrote:
>>
>>> Hi Mark and Nicolay
>>>
>>> Hope you both are doing well.
>>>
>>> Have you had a chance to look into Kaustav's email?
>>>
>>> We have started a new iteration and wanted to pick up this work asap.
>>> Any help would be greatly appreciated.
>>>
>>> Thanks in advance
>>> Vanya
>>>
>>>
>>>
>>> On Tue, Mar 15, 2016 at 6:36 PM, Kaustav Chakraborty <
>>> kaust...@thoughtworks.com> wrote:
>>>
>>>> Hi Mark
>>>>
>>>> Hope you are doing well.
>>>>
>>>> We want to make some enhancements to the Data entry app.  Which is to
>>>> make the data entry table header ( category combo header ) stay constant
>>>> even if we scroll down the page, so that the user knows which column they
>>>> are entering the data in.
>>>>
>>>>
>>>> These are a few questions,
>>>>
>>>>
>>>> *1. Would this be alright to add this to DHIS?*
>>>>
>>>> *2. If you have any recommendations regarding the implementation of
>>>> this feature? Like using some library or anything of that sort?*
>>>>
>>>>
>>>> At our end we have explored a few things:
>>>>
>>>> *Assume, the table is structured as below,*
>>>>
>>>> table
>>>>
>>>> thead
>>>>
>>>> tr
>>>>
>>>> th
>>>>
>>>> tbody
>>>>
>>>> tr
>>>>
>>>> td
>>>>
>>>>
>>>> *1. Using a Library:*
>>>>
>>>> There is a javascript library called floatThead
>>>> <https://github.com/mkoryak/floatThead> that can be leveraged for
>>>> this. It also works with multiple tables present in a single page. So while
>>>> scrolling the table header remain fixed for each tables.
>>>>
>>>>
>>>> *2. Not using any library,*
>>>>
>>>> We can have some fixed height given to a table body and put the
>>>> y-axis scroll for the table. User has to come to the table element and
>>>> scroll to get their data element to be seen.
>>>>
>>>>
>>>> I have attached the screenshots for better understanding.
>>>>
>>>> We are waiting for your response.
>>>>
>>>>
>>>>
>>>> Thanks & Regards,
>>>>
>>>> *Kaustav Chakraborty*
>>>> STEP Intern
>>>> Email kaust...@thoughtworks.com
>>>> Telephone +91 91009 60526 <+91+91009+60526>
>>>> [image: ThoughtWorks]
>>>> <http://www.thoughtworks.com/?utm_campaign=kaustav-chakraborty-signature&utm_medium=email&utm_source=thoughtworks-email-signature-generator>
>>>>
>>>
>>>
>>>
>>> --
>>> With Regards
>>> ThoughtWorks Technologies
>>> Hyderabad
>>>
>>> --Stay Hungry Stay Foolish!!
>>>
>>
>>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] Moving dhis.conf as a classpath resource

[Vanya Seth]

Thanks Lars.

Regards
Vanya

On Tue, Mar 8, 2016 at 3:08 PM, Lars Helge Øverland  wrote:

> Hi Vanya,
>
> thanks for the suggestion. We do not plan to do this at this point, as
> arbitrary config properties can become unwieldy.
>
> I propose that you instead extend the settings app with new properties
> under Synchronization and base it on system settings (this will be more
> dynamic):
>
> https://play.dhis2.org/demo/dhis-web-settings/#
>
> If you really need compile time (application context startup time)
> configuration properties, then you could create a spring factory bean in
> combination with the DhisConfigurationProvider, something like this:
>
> class DhisConfigurationPropertyFactoryBean
>   implements FactoryBean
>
> which uses the DhisConfigurationProvider to look up a given property. Have
> a look at ConnectionPropertyFactoryBean.java for reference.
>
> regards,
>
> Lars
>
>
>
> On Tue, Mar 8, 2016 at 10:28 AM, Vanya Seth 
> wrote:
>
>> Hi Lars
>>
>> Had a question regarding dhis.conf being external to the system( as in,
>> in the DHIS2 home).
>> Would there be a chance where we plan to move this properties file as a
>> classpath resource.
>> There are multiple advantages to it.  Please see this snippet for more
>> details:
>>
>> > ="org.springframework.retry.policy.SimpleRetryPolicy">
>>   
>> 
>>
>> >   
>> class="*org.springframework.beans.factory.config.PropertyPlaceholderConfigurer*">
>>   
>> 
>>
>> We can leverage Spring's *PropertyPlaceholderConfigurer *to substitute
>> the property placeholders dynamically.
>> We can also inject the property values using the @Value annotation.
>>
>> Any thoughts?
>>
>> --
>> With Regards
>> Vanya
>> ThoughtWorks Technologies
>> Hyderabad
>>
>> --Stay Hungry Stay Foolish!!
>>
>
>
>
> --
> Lars Helge Øverland
> Lead developer, DHIS 2
> University of Oslo
> Skype: larshelgeoverland
> http://www.dhis2.org <https://www.dhis2.org/>
>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

[Dhis2-devs] Moving dhis.conf as a classpath resource

[Vanya Seth]

Hi Lars

Had a question regarding dhis.conf being external to the system( as in, in
the DHIS2 home).
Would there be a chance where we plan to move this properties file as a
classpath resource.
There are multiple advantages to it.  Please see this snippet for more
details:


  



  


We can leverage Spring's *PropertyPlaceholderConfigurer *to substitute the
property placeholders dynamically.
We can also inject the property values using the @Value annotation.

Any thoughts?

-- 
With Regards
Vanya
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] Where is the UI option to configure the "keySystemNotificationsEmail"

[Vanya Seth]

No problem :)

I think this should solve our problem.

Thanks a lot.

Regards
Vanya

On Thu, Feb 25, 2016 at 6:42 PM, Lars Helge Øverland  wrote:

> Ah apologies, I was confused here. In 2.22 you can set this from Settings
> > Server > System notifications email address.
>
>
>
> Lars
>
>
> On Thu, Feb 25, 2016 at 8:07 AM, Vanya Seth 
> wrote:
>
>> The setting you are referring to is this one:  "
>> keyMessageEmailNotification" which tells whether or not to send  the
>> email notifications.
>>
>> @Override
>> public boolean sendSystemEmail( Email email )
>> {
>> String recipient = (String) systemSettingManager.getSystemSetting( 
>> SettingKey.SYSTEM_NOTIFICATIONS_EMAIL );
>>
>>
>> and SystemSettingKey file has this entry:
>>
>> SYSTEM_NOTIFICATIONS_EMAIL( "keySystemNotificationsEmail" ),
>>
>> We do have the email address set on the Profile->profile.
>>
>> Regards
>>
>> Vanya
>>
>>
>> On Thu, Feb 25, 2016 at 6:30 PM, Lars Helge Øverland 
>> wrote:
>>
>>> Okay. I think the issue here is this - the "keySystemNoticationsEmail"
>>> user refers to whether or not you should send email notifications to that
>>> user. The email to send to you will have to set on the user object (User >
>>> email) in profile > profile.
>>>
>>> We have an open issue for including a description of all user/system
>>> settings in the docs.
>>>
>>>
>>> On Thu, Feb 25, 2016 at 7:55 AM, Vanya Seth 
>>> wrote:
>>>
>>>> Hi Lars
>>>>
>>>> Thanks for the response.
>>>>
>>>> But we did set the email address on the user's profile, but while we
>>>> use the method sendSystemEmail from the EmailService, we get the recipient
>>>> as "null". And for the recipient its trying to use the "
>>>> keySystemNotificationsEmail" key from the systemsetting.
>>>>
>>>> Regards
>>>> Vanya
>>>>
>>>> On Thu, Feb 25, 2016 at 6:18 PM, Lars Helge Øverland 
>>>> wrote:
>>>>
>>>>> Hi Vanya,
>>>>>
>>>>> this is currently a user setting (not system). So you can set it from
>>>>> profile > settings.
>>>>>
>>>>> That said, in version 2.23 we are introducing fallback to system
>>>>> settings for all user settings, so that you can easily enable email
>>>>> notifications for all users by default (and continue to have users 
>>>>> override
>>>>> it). This will apply to all user settings.
>>>>>
>>>>> https://blueprints.launchpad.net/dhis2/+spec/user-setting-fallback
>>>>>
>>>>>
>>>>> regards,
>>>>>
>>>>> Lars
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Feb 25, 2016 at 7:45 AM, Vanya Seth 
>>>>> wrote:
>>>>>
>>>>>> Hi Dhis devs
>>>>>>
>>>>>> Have been struggling to find this one.
>>>>>>
>>>>>> Wanted to know where is the UI option to set the system setting for "
>>>>>> keySystemNotificationsEmail". I know it exists through Web API, but
>>>>>> do we have the option to be set from some UI screen as well?
>>>>>>
>>>>>> --
>>>>>> With Regards
>>>>>> Vanya
>>>>>> ThoughtWorks Technologies
>>>>>> Hyderabad
>>>>>>
>>>>>> --Stay Hungry Stay Foolish!!
>>>>>>
>>>>>> ___
>>>>>> 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
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Lars Helge Øverland
>>>>> Lead developer, DHIS 2
>>>>> University of Oslo
>>>>> Skype: larshelgeoverland
>>>>> 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
>>> 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
> http://www.dhis2.org <https://www.dhis2.org/>
>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] Where is the UI option to configure the "keySystemNotificationsEmail"

[Vanya Seth]

The setting you are referring to is this one:  "keyMessageEmailNotification"
which tells whether or not to send  the email notifications.

@Override
public boolean sendSystemEmail( Email email )
{
String recipient = (String) systemSettingManager.getSystemSetting(
SettingKey.SYSTEM_NOTIFICATIONS_EMAIL );


and SystemSettingKey file has this entry:

SYSTEM_NOTIFICATIONS_EMAIL( "keySystemNotificationsEmail" ),

We do have the email address set on the Profile->profile.

Regards

Vanya


On Thu, Feb 25, 2016 at 6:30 PM, Lars Helge Øverland  wrote:

> Okay. I think the issue here is this - the "keySystemNoticationsEmail"
> user refers to whether or not you should send email notifications to that
> user. The email to send to you will have to set on the user object (User >
> email) in profile > profile.
>
> We have an open issue for including a description of all user/system
> settings in the docs.
>
>
> On Thu, Feb 25, 2016 at 7:55 AM, Vanya Seth 
> wrote:
>
>> Hi Lars
>>
>> Thanks for the response.
>>
>> But we did set the email address on the user's profile, but while we use
>> the method sendSystemEmail from the EmailService, we get the recipient as
>> "null". And for the recipient its trying to use the "keySystemNotificati
>> onsEmail" key from the systemsetting.
>>
>> Regards
>> Vanya
>>
>> On Thu, Feb 25, 2016 at 6:18 PM, Lars Helge Øverland 
>> wrote:
>>
>>> Hi Vanya,
>>>
>>> this is currently a user setting (not system). So you can set it from
>>> profile > settings.
>>>
>>> That said, in version 2.23 we are introducing fallback to system
>>> settings for all user settings, so that you can easily enable email
>>> notifications for all users by default (and continue to have users override
>>> it). This will apply to all user settings.
>>>
>>> https://blueprints.launchpad.net/dhis2/+spec/user-setting-fallback
>>>
>>>
>>> regards,
>>>
>>> Lars
>>>
>>>
>>>
>>> On Thu, Feb 25, 2016 at 7:45 AM, Vanya Seth 
>>> wrote:
>>>
>>>> Hi Dhis devs
>>>>
>>>> Have been struggling to find this one.
>>>>
>>>> Wanted to know where is the UI option to set the system setting for "
>>>> keySystemNotificationsEmail". I know it exists through Web API, but do
>>>> we have the option to be set from some UI screen as well?
>>>>
>>>> --
>>>> With Regards
>>>> Vanya
>>>> ThoughtWorks Technologies
>>>> Hyderabad
>>>>
>>>> --Stay Hungry Stay Foolish!!
>>>>
>>>> ___
>>>> 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
>>>>
>>>>
>>>
>>>
>>> --
>>> Lars Helge Øverland
>>> Lead developer, DHIS 2
>>> University of Oslo
>>> Skype: larshelgeoverland
>>> 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
> http://www.dhis2.org <https://www.dhis2.org/>
>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] Where is the UI option to configure the "keySystemNotificationsEmail"

[Vanya Seth]

Hi Lars

Thanks for the response.

But we did set the email address on the user's profile, but while we use
the method sendSystemEmail from the EmailService, we get the recipient as
"null". And for the recipient its trying to use the "keySystemNotificati
onsEmail" key from the systemsetting.

Regards
Vanya

On Thu, Feb 25, 2016 at 6:18 PM, Lars Helge Øverland  wrote:

> Hi Vanya,
>
> this is currently a user setting (not system). So you can set it from
> profile > settings.
>
> That said, in version 2.23 we are introducing fallback to system settings
> for all user settings, so that you can easily enable email notifications
> for all users by default (and continue to have users override it). This
> will apply to all user settings.
>
> https://blueprints.launchpad.net/dhis2/+spec/user-setting-fallback
>
>
> regards,
>
> Lars
>
>
>
> On Thu, Feb 25, 2016 at 7:45 AM, Vanya Seth 
> wrote:
>
>> Hi Dhis devs
>>
>> Have been struggling to find this one.
>>
>> Wanted to know where is the UI option to set the system setting for "
>> keySystemNotificationsEmail". I know it exists through Web API, but do
>> we have the option to be set from some UI screen as well?
>>
>> --
>> With Regards
>> Vanya
>> ThoughtWorks Technologies
>> Hyderabad
>>
>> --Stay Hungry Stay Foolish!!
>>
>> ___
>> 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
>>
>>
>
>
> --
> Lars Helge Øverland
> Lead developer, DHIS 2
> University of Oslo
> Skype: larshelgeoverland
> http://www.dhis2.org <https://www.dhis2.org/>
>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

[Dhis2-devs] Where is the UI option to configure the "keySystemNotificationsEmail"

[Vanya Seth]

Hi Dhis devs

Have been struggling to find this one.

Wanted to know where is the UI option to set the system setting for "
keySystemNotificationsEmail". I know it exists through Web API, but do we
have the option to be set from some UI screen as well?

-- 
With Regards
Vanya
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] DHIS Version 2.21 /api/events/{uid} fix

[Vanya Seth]

Thanks a lot.

Regards
Vanya

On Wed, Feb 3, 2016 at 4:50 PM, Morten Olav Hansen 
wrote:

> Thanks,
>
> I applied a similar patch to 2.21, 2.22, and trunk now.
>
> --
> Morten
>
> On Wed, Feb 3, 2016 at 5:43 PM, Anilkumar Kodi 
> wrote:
>
>> Hi Morten,
>>
>> We are working with the Android Event Capture app (legacy 2.21).
>> The *GET /api/events* and */api/events/{uid}* have been used for
>> fetching the events data.
>>
>> When we Invoke the GET events call we are getting all the fields like
>> "created" and "lastUpdated" but when we invoke GET call for the particular
>> event with api/events/{uid} we don't get "Created" and "lastUpdated"
>>  fields.
>> On looking up the code we realized that the Event object was not being
>> populated with these information. We have created a patch for the same.
>> Kindly commit it to the dhis code base.
>>
>>
>> We are using DHIS version *2.21* and revision *20983.*
>>
>> Regards
>> Anil Kumar Kodi,
>> ThoughtWorks
>> Phone: +917660010617
>>
>>
>
>


-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

[Dhis2-devs] Complete/Incomplete flow

[Vanya Seth]

Hello devs,

We were looking at certain optimizations for the look and feel of the DHIS
web app in terms of usability. We were particularly looking at the
"Complete/Incomplete” and the “Validate” buttons.


We are not sure of the intended relevance of using the word “Complete", if
what we are doing is a simple save. Initially we guess that Complete and
Incomplete are supposed to indicate the status of the data, i.e. Complete
indicates the data is saved, ready to be synced, and locked from further
changes; whereas Incomplete indicates the data is ready to be
updated/changed.


However, looking at the code and the changes in the DB it seems that on
“Complete”, and even when not pressing complete, the values typed into the
form are added to the "datavalue" table. In the case of the user clicking
“Complete" we also add an entry in the "completedatasetregistration" table.



We were thinking of customizing this behavior (leveraging the custom js
post) by having a single "Save" button. This button will be overloaded with
the "update” behavior inherent in the Incomplete button, with a prompt
asking for a confirmation in case a value is changed. (e.g. “Are you sure
you want to change these values?”)

The Save button would also be overloaded with the Validation functionality,
where clicking Save would generate running the Validate command.

Does this sound right? Or there is something that we are missing here?

On a related note, in the DHIS Android Event Capture app, there are again
"Complete" and "Validate" buttons. On saving the event the status changes
to "Incomplete". This seems like confusing user experience.  Any thoughts?


-- 
With Regards
Vanya
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

Re: [Dhis2-devs] Android Apps Issues

[Vanya Seth]

Hi Simen

I have sent out the Fuze meeting invite. The Agenda is included in there.

Regards
Vanya

On Wed, Jan 20, 2016 at 6:23 PM, Simen Skogly Russnes <
simen.s.russ...@gmail.com> wrote:

> Hi,
>
> we are based in Oslo. Tomorrow at 11.30 am GMT+1 is fine.
>
> The topics for the call from our side would mainly be figuring out how
> collaboration efforts could be implemented. Do you have an agenda that we
> can prepare a little for?
>
> Simen
>
> On Wed, Jan 20, 2016 at 1:35 PM, Vanya Seth 
> wrote:
>
>> Hi Araz and Simen
>>
>> Thanks for the response. Can we have a call tomorrow (Thursday)?
>> Theo (Product Owner) from client side would like to join the call. He's
>> based out of Berlin.  So, 11.30 am GMT + 1 is ok for a call?? Am not sure
>> where you guys are currently placed.
>> If this time is not convenient please let me know a time that suits you.
>>
>> Regards
>> Vanya
>>
>> On Tue, Jan 19, 2016 at 8:50 PM, Simen Skogly Russnes <
>> simen.s.russ...@gmail.com> wrote:
>>
>>> Hi Vanya,
>>>
>>> glad to see you are interested in the apps and the SDK. Arranging a call
>>> would be great. Would you perhaps be available already this week?
>>>
>>> Regards,
>>> Simen
>>>
>>> On Tue, Jan 19, 2016 at 12:35 PM, Vanya Seth 
>>> wrote:
>>>
>>>> Hi Araz
>>>>
>>>> Thanks for the response. Really appreciate it.
>>>> Its good to know that the fixes will be out with the next DHIS release.
>>>>
>>>> But I am looking more from the aspect of collaboration wherein we can
>>>> share the load of fixing these issues.  Can you let me know what is the
>>>> best way to take this forward? We are happy to jump on a call if required.
>>>> But given our Pilot (Evaluation ) timelines we would be keen to close
>>>> them in the next 2 weeks.
>>>>
>>>> FYI...As suggested by you we are right now working off the legacy
>>>> branch. (Sultan Ahamer from our team mailed regarding the failing build
>>>> earlier)
>>>>
>>>> *Details about the issue:*
>>>>
>>>>  *I]* Period labels are overlapping (see this example:
>>>> In the DHIS Web App:
>>>>   2015-5-15 to 2015-5-21
>>>>   2015-5-7 to 2015-5-14
>>>>
>>>> (In the web app for a weekly dataset if you look at the date range, the
>>>> next week starts from the next day, where the previous week ends.)
>>>>
>>>> In the Android App:
>>>>  2015-5-14 to 2015-5-21
>>>>  2015-5-7 to 2015-5-14
>>>> (But in the Android app, the next week period label starts from the
>>>> same day where the previous week ends. For a field user this might be
>>>> confusing in terms of where to enter the data for the day which appears in
>>>> both the weeks.) See the screenshot below. The overlap has been highlighted
>>>> in red.
>>>> [image: Inline image 1]
>>>>
>>>> Regards
>>>> Vanya
>>>>
>>>> On Tue, Jan 19, 2016 at 1:40 PM, Araz Abishov <
>>>> araz.abishov.g...@gmail.com> wrote:
>>>>
>>>>> Hello Vanya,
>>>>>
>>>>> It is really good to know that you are planning to start using android
>>>>> applications. I have answered some questions below:
>>>>>
>>>>> *[I] *We opened an issue in GitHub as well. But unfortunately no one
>>>>>> has responded yet.
>>>>>> https://github.com/dhis2/dhis2-android-datacapture/issues/12
>>>>>
>>>>> This issue will be fixed in upcoming release. I have created a
>>>>> milestone (April 1 - release of DHIS2 2.23) and assigned bug to it.
>>>>>
>>>>> *[I]* A dropdown field allows text entry (manually from the
>>>>>> keyboard). Rather this field should not allow any data entry.
>>>>>
>>>>> This is more a design issue, now we picked up another approach, which
>>>>> eliminates this problem.
>>>>>
>>>>> *I]* Period labels are overlapping (see this example:
>>>>>
>>>>> Could you please explain the problem in more details?
>>>>>
>>>>> *[E]* If data is not synced (sync failed), if it’s easy to suggest an
>>>>>> action to the user (something like “Please try again later or res

Re: [Dhis2-devs] Android Apps Issues

[Vanya Seth]

Hi Araz and Simen

Thanks for the response. Can we have a call tomorrow (Thursday)?
Theo (Product Owner) from client side would like to join the call. He's
based out of Berlin.  So, 11.30 am GMT + 1 is ok for a call?? Am not sure
where you guys are currently placed.
If this time is not convenient please let me know a time that suits you.

Regards
Vanya

On Tue, Jan 19, 2016 at 8:50 PM, Simen Skogly Russnes <
simen.s.russ...@gmail.com> wrote:

> Hi Vanya,
>
> glad to see you are interested in the apps and the SDK. Arranging a call
> would be great. Would you perhaps be available already this week?
>
> Regards,
> Simen
>
> On Tue, Jan 19, 2016 at 12:35 PM, Vanya Seth 
> wrote:
>
>> Hi Araz
>>
>> Thanks for the response. Really appreciate it.
>> Its good to know that the fixes will be out with the next DHIS release.
>>
>> But I am looking more from the aspect of collaboration wherein we can
>> share the load of fixing these issues.  Can you let me know what is the
>> best way to take this forward? We are happy to jump on a call if required.
>> But given our Pilot (Evaluation ) timelines we would be keen to close
>> them in the next 2 weeks.
>>
>> FYI...As suggested by you we are right now working off the legacy branch.
>> (Sultan Ahamer from our team mailed regarding the failing build earlier)
>>
>> *Details about the issue:*
>>
>>  *I]* Period labels are overlapping (see this example:
>> In the DHIS Web App:
>>   2015-5-15 to 2015-5-21
>>   2015-5-7 to 2015-5-14
>>
>> (In the web app for a weekly dataset if you look at the date range, the
>> next week starts from the next day, where the previous week ends.)
>>
>> In the Android App:
>>  2015-5-14 to 2015-5-21
>>  2015-5-7 to 2015-5-14
>> (But in the Android app, the next week period label starts from the same
>> day where the previous week ends. For a field user this might be confusing
>> in terms of where to enter the data for the day which appears in both the
>> weeks.) See the screenshot below. The overlap has been highlighted in red.
>> [image: Inline image 1]
>>
>> Regards
>> Vanya
>>
>> On Tue, Jan 19, 2016 at 1:40 PM, Araz Abishov <
>> araz.abishov.g...@gmail.com> wrote:
>>
>>> Hello Vanya,
>>>
>>> It is really good to know that you are planning to start using android
>>> applications. I have answered some questions below:
>>>
>>> *[I] *We opened an issue in GitHub as well. But unfortunately no one
>>>> has responded yet.
>>>> https://github.com/dhis2/dhis2-android-datacapture/issues/12
>>>
>>> This issue will be fixed in upcoming release. I have created a milestone
>>> (April 1 - release of DHIS2 2.23) and assigned bug to it.
>>>
>>> *[I]* A dropdown field allows text entry (manually from the keyboard).
>>>> Rather this field should not allow any data entry.
>>>
>>> This is more a design issue, now we picked up another approach, which
>>> eliminates this problem.
>>>
>>> *I]* Period labels are overlapping (see this example:
>>>
>>> Could you please explain the problem in more details?
>>>
>>> *[E]* If data is not synced (sync failed), if it’s easy to suggest an
>>>> action to the user (something like “Please try again later or restart 
>>>> app”).
>>>
>>> Create new issue on GitHub:
>>> https://github.com/dhis2/dhis2-android-datacapture/issues/15
>>>
>>> *[E]* A logout confirmation message ("Are you sure you want to log
>>>> out") is missing(although its present in the Event Capture app)
>>>
>>> Create new issue on GitHub:
>>> https://github.com/dhis2/dhis2-android-datacapture/issues/16
>>>
>>> *Q] *Is there a limit on the number of columns that can be accommodated
>>>> in the mobile app?
>>>
>>> At the moment this number (4) is hardcoded into app. But we are working
>>> on more flexible solution which will allow to choose amount of columns to
>>> be show to user.
>>>
>>> *[Q] *Is there any upper limit on the time for which the device can be
>>>> offline?
>>>
>>> No, there is no time limit for being in offline mode.
>>>
>>>  *[Q]*Is there any upper limit on the number of events that can show up
>>>> in the grid (for view purposes)?
>>>
>>> Initially event capture downloads 200 events from the server and then
>>> also shows all event

Re: [Dhis2-devs] Android Apps Issues

[Vanya Seth]

Hi Araz

Thanks for the response. Really appreciate it.
Its good to know that the fixes will be out with the next DHIS release.

But I am looking more from the aspect of collaboration wherein we can share
the load of fixing these issues.  Can you let me know what is the best way
to take this forward? We are happy to jump on a call if required.
But given our Pilot (Evaluation ) timelines we would be keen to close them
in the next 2 weeks.

FYI...As suggested by you we are right now working off the legacy branch.
(Sultan Ahamer from our team mailed regarding the failing build earlier)

*Details about the issue:*

 *I]* Period labels are overlapping (see this example:
In the DHIS Web App:
  2015-5-15 to 2015-5-21
  2015-5-7 to 2015-5-14

(In the web app for a weekly dataset if you look at the date range, the
next week starts from the next day, where the previous week ends.)

In the Android App:
 2015-5-14 to 2015-5-21
 2015-5-7 to 2015-5-14
(But in the Android app, the next week period label starts from the same
day where the previous week ends. For a field user this might be confusing
in terms of where to enter the data for the day which appears in both the
weeks.) See the screenshot below. The overlap has been highlighted in red.
[image: Inline image 1]

Regards
Vanya

On Tue, Jan 19, 2016 at 1:40 PM, Araz Abishov 
wrote:

> Hello Vanya,
>
> It is really good to know that you are planning to start using android
> applications. I have answered some questions below:
>
> *[I] *We opened an issue in GitHub as well. But unfortunately no one has
>> responded yet.
>> https://github.com/dhis2/dhis2-android-datacapture/issues/12
>
> This issue will be fixed in upcoming release. I have created a milestone
> (April 1 - release of DHIS2 2.23) and assigned bug to it.
>
> *[I]* A dropdown field allows text entry (manually from the keyboard).
>> Rather this field should not allow any data entry.
>
> This is more a design issue, now we picked up another approach, which
> eliminates this problem.
>
> *I]* Period labels are overlapping (see this example:
>
> Could you please explain the problem in more details?
>
> *[E]* If data is not synced (sync failed), if it’s easy to suggest an
>> action to the user (something like “Please try again later or restart app”).
>
> Create new issue on GitHub:
> https://github.com/dhis2/dhis2-android-datacapture/issues/15
>
> *[E]* A logout confirmation message ("Are you sure you want to log out")
>> is missing(although its present in the Event Capture app)
>
> Create new issue on GitHub:
> https://github.com/dhis2/dhis2-android-datacapture/issues/16
>
> *Q] *Is there a limit on the number of columns that can be accommodated
>> in the mobile app?
>
> At the moment this number (4) is hardcoded into app. But we are working on
> more flexible solution which will allow to choose amount of columns to be
> show to user.
>
> *[Q] *Is there any upper limit on the time for which the device can be
>> offline?
>
> No, there is no time limit for being in offline mode.
>
>  *[Q]*Is there any upper limit on the number of events that can show up
>> in the grid (for view purposes)?
>
> Initially event capture downloads 200 events from the server and then also
> shows all events which were created locally on device. The problem is that
> if you will have too many events, application will become slower.
>
> *[I]* If an event fails to sync, on clicking on the sync icon, the full
>> stack trace(exception) shows up. It's not a user friendly message.
>
> But it is the only way at the moment we can get feedback from the users
> with sync errors. In new version, we are planning to change it to something
> more user friendly.
>
> *[I]*The spinner doesn't stop even if the device is offline. (Swiping
>> initiates a sync, but in offline conditions, it should raise a message)
>
> *[I] *While offline, when we attempt login the message that comes up is
>> not user friendly.And same holds true for the message which comes when the
>> app times out while trying to log in.
>
> https://github.com/dhis2/dhis2-android-eventcapture/issues/64
>
> *[I] *There are no sync related notifications/messages (When we click on
>> the sync icon in offline as well as online mode)
>
> https://github.com/dhis2/dhis2-android-dashboard/issues/15
>
> If you have any questions, do not hesitate to ask.
>
> Best regards,
> Araz
>
>
> On Mon, Jan 18, 2016 at 10:09 AM, Vanya Seth 
> wrote:
>
>> Hi Dhis-Devs
>>
>> We are looking at evaluating three Android Apps (Data capture, Event
>> Capture and Dashboards) in couple of months (around March end/Early April)
>>  for MSF (OCA).
>

[Dhis2-devs] Android Apps Issues

[Vanya Seth]

Hi Dhis-Devs

We are looking at evaluating three Android Apps (Data capture, Event
Capture and Dashboards) in couple of months (around March end/Early April)
 for MSF (OCA).
We have been playing around with the apps and there are quite a few issues
and enhancements that we might be interested in
.
It would be good if we could get some clarity on the roadmap and if at all
they are on the priority to be fixed/implemented (We are happy to fix
ourselves as well, but its good to know the agenda of the dev team).

Here is a list of some issues/questions and enhancements that might make
sense.
*[Q] : Question*
*[I] :   Issue*
*[E] : Enhancement*

*Data Capture App:*
*1. [I] *We opened an issue in GitHub as well. But unfortunately no one has
responded yet. https://github.com/dhis2/dhis2-android-datacapture/issues/12
2. *[I]* A dropdown field allows text entry (manually from the keyboard).
Rather this field should not allow any data entry.
3. *[I]* Period labels are overlapping (see this example:
In the DHIS Web App:
  2015-5-15 to 2015-5-21
  2015-5-7 to 2015-5-14

In the Android App:
 2015-5-14 to 2015-5-21
 2015-5-7 to 2015-5-14

4. *[E]* If data is not synced (sync failed), if it’s easy to suggest an
action to the user (something like “Please try again later or restart app”).
5. *[E]* A logout confirmation message ("Are you sure you want to log out")
is missing(although its present in the Event Capture app)


*Event Capture App*
*1. [Q] *Is there a limit on the number of columns that can be accommodated
in the mobile app?
2. *[Q] *Is there any upper limit on the time for which the device can be
offline?
3. *[Q]*Is there any upper limit on the number of events that can show up
in the grid (for view purposes)?
4. *[I]* If an event fails to sync, on clicking on the sync icon, the full
stack trace(exception) shows up. It's not a user friendly message.
5. *[I]*The spinner doesn't stop even if the device is offline. (Swiping
initiates a sync, but in offline conditions, it should raise a message)
6. *[I] *While offline, when we attempt login the message that comes up is
not user friendly.And same holds true for the message which comes when the
app times out while trying to log in.


*Dashboard App*
*1.[I] *There are no sync related notifications/messages (When we click on
the sync icon in offline as well as online mode)

Regards
Vanya







-- 
With Regards
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

[Dhis2-devs] Sample Usage of the /api/fileteredMetaData API

[Vanya Seth]

Hello Devs

Can you please provide a sample request for invoking the above API. I am
not able to find any documentation around it.
If you can point me to relevant documentation even that would be very
helpful.

I wanted to check out the "exportDependencies" aspect  for a given entity.

Thanks in advance.

-- 
With Regards
Vanya Seth
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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

[Dhis2-devs] Information about Metadata Sync

[Vanya Seth]

Hi dhis-devs

I am from ThoughtWorks India and we are working for MSF (OCA). There is a
requirement to synchronize data/metadata across multiple dhis instances.
The deployment strategy that we have is: A central instance called as
Headquarters(HQ) and multiple field level instances for data collection.
The central instance is
responsible for creation of the metadata and do data analysis(data
collected from fields get synced to the HQ instance). So, this essentially
is a classical case of a distributed setting.

Data Sync functionality is built into the system. But for metadata sync
there is no direct or consolidated functionality implemented. We explored
the Metadata Export and Import functionality as a probable solution.

But then I stumbled upon this mail thread
https://lists.launchpad.net/dhis2-users/msg05889.html and there is a
mention of some synchronization tool under development with support coming
in from HISP India developers.
I had a look at the branches and this is what I think is their development
branch: https://code.launchpad.net/~dhis2-devs-core/dhis2/synchmanager_2.20

So, I wanted to understand a couple of things here:

1. Actual requirements/ blue print of the feature under development.
2. If we could get a high level solution approach that has been followed.
3. The roadmap in terms of feature release and also what all has been
implemented so far.

Also, would it be possible to have it all discussed over a call?

Thanks in advance for all the help.


--
With Regards
Vanya
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!
___
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