dhis2-devs-core team mailing list archive

[Rodolfo Melia <rmelia@xxxxxxxxxxxx>]

Hi Lars - I just tested in 22027: It works !

Thanks !


*Rodolfo*


On 9 May 2016 at 09:25, Lars Helge Øverland <lars@xxxxxxxxx> wrote:

> Sounds good.
>
> On Mon, May 9, 2016 at 10:14 AM, Rodolfo Melia <rmelia@xxxxxxxxxxxx>
> wrote:
>
>> Thanks Lars !
>>
>> We will be testing 2.22 rev 22026 in our staging server later today, and
>> will report any issues.
>>
>> R
>>
>> *Rodolfo Meliá*
>> *Principal  |  *rmelia@xxxxxxxxxxxx
>> Skype: rod.melia  |  +44 777 576 4090  |  +1 708 872 7636
>> www.knowming.com
>>
>> On 8 May 2016 at 20:55, Lars Helge Øverland <lars@xxxxxxxxx> wrote:
>>
>>>
>>> Hi Rodolfo,
>>>
>>> you are right. Fixed now in 2.21 -> trunk.
>>>
>>> This was a regression bug which was introduced when we changed
>>> programstageinstance to become a timestamp field.
>>>
>>> I think the reason why this has not surfaced until now is that the DHIS
>>> 2 core apps record timestamps only with date precision, so these events
>>> likely come from imports from third-party systems. Sorry about that. Thanks
>>> for reporting.
>>>
>>> regards,
>>>
>>> Lars
>>>
>>>
>>>
>>>
>>>
>>> On Fri, May 6, 2016 at 5:50 PM, Rodolfo Melia <rmelia@xxxxxxxxxxxx>
>>> wrote:
>>>
>>>>
>>>> Tested on DHIS 2.22/ r 22016
>>>>
>>>> DHIS output: the inconsistency
>>>>
>>>>    1.
>>>>
>>>>    Results when displaying Events: 449 events
>>>>
>>>>
>>>>    2.
>>>>
>>>>    Results when displaying Aggregated Values: 170 events
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Demonstrating the bug
>>>>
>>>> Download the data in a spreadsheet, and mark records for which time is
>>>> set to 00:00:00.0 vs another time
>>>>
>>>>
>>>> PIVOT the data, counting only the ones for which 00:00:00.0 = true
>>>>
>>>>
>>>> Conclusion
>>>>
>>>> DHIS Event Analytics ONLY seems to take into consideration events for
>>>> which the time is set to 00:00:00.0. This is resulting in a significant
>>>> undercounting of events that are pushed thorugh the API, for which the time
>>>> is different to 00:00:00.0
>>>>
>>>> Suggested fix
>>>>
>>>> The possibility of an event having time should be preserved, but we
>>>> need the analytics to count all events on a given period, regardless of the
>>>> time of the event.
>>>>
>>>> Example (PSI
>>>> <https://www.psi-mis.org/dhis-web-event-reports/index.html?id=wfEBcyZ5s79>
>>>> )
>>>>
>>>>    -
>>>>
>>>>    Program: KH MAL - Surveillance App | Stage: Phone Push
>>>>    -
>>>>
>>>>    OU: Cambodia,
>>>>
>>>>    Period: April & May 2016
>>>>
>>>>
>>>> --
>>>> Mailing list: https://launchpad.net/~dhis2-devs-core
>>>> Post to     : dhis2-devs-core@xxxxxxxxxxxxxxxxxxx
>>>> Unsubscribe : https://launchpad.net/~dhis2-devs-core
>>>> More help   : https://help.launchpad.net/ListHelp
>>>>
>>>>
>>>
>>>
>>> --
>>> Lars Helge Øverland
>>> Lead developer, DHIS 2
>>> University of Oslo
>>> Skype: larshelgeoverland
>>> lars@xxxxxxxxx
>>> http://www.dhis2.org <https://www.dhis2.org/>
>>>
>>>
>>
>
>
> --
> Lars Helge Øverland
> Lead developer, DHIS 2
> University of Oslo
> Skype: larshelgeoverland
> lars@xxxxxxxxx
> http://www.dhis2.org <https://www.dhis2.org/>
>
>