Re: [Dhis2-devs] [Dhis2-users] Enter data for a future date in Event and Tracker Capture

[Markus Bekken]

Hi again Georgi.

We have this Jira issue that would probably help you show the data you want in 
the reporting module if you remodeled your data, but it is planned for a later 
release - so perhaps no good to you now: DHIS2-127 


Lifting the restriction on registering future event dates is a possibility. The 
restriction only applies in the UI at the moment, the back-end supports future 
event dates. If you create an improvement issue for this in Jira we can discuss 
it there. If we allow it for all programs, the user should probably get a 
visual cue that the event date is in the future to minimize accidental wrong 
dates.

For your second question I honestly dont see why the periods should be within 
the same year as the enrollment. Please register this part as a bug in Jira.

Markus

> 26. apr. 2017 kl. 09.50 skrev Georgi Chakarov :
> 
> Hi Markus,
>  
> I thought about it but then it will be really hard in reporting module to the 
> display the data for the desired period.
>  
> Are you able to comment on the below?:
>  
> When selecting monthly, six-monthly, yearly period for repeatable program 
> stages you can't create a stage for a year different than the year of 
> enrollment.
>  
> Example
>  
> Program stage is six-monthly
>  
> 
>  
>  
> Enrollment date is in 2015
>  
> 
>  
> Current date is 2017
>  
> 
>  
> DHIS2 does not allow to create a six-monthly stages for 2016. Note how the 
> arrow used to go to next period (2016) is inactive. The only possible options 
> are the two six-monthly periods in 2015. 2014 is not active either.
>  
> 
>  
>  
>  
> From: Markus Bekken [mailto:mar...@dhis2.org] 
> Sent: Wednesday, April 26, 2017 10:47 AM
> To: Georgi Chakarov 
> Cc: Shurajit Dutta ; 
> dhis2-us...@lists.launchpad.net; dhis2-devs@lists.launchpad.net
> Subject: Re: [Dhis2-users] Enter data for a future date in Event and Tracker 
> Capture
>  
> Hi Georgi and Nick
>  
> The tracker does not allow allow event dates in the future. This restriction 
> is probably there because most(all so far?) tracker use cases register actual 
> events that already has happened. Knowing nothing about your usecase: Can you 
> model it slightly differently, capturing the future date a data element 
> instead of the event date?
>  
> Markus
>  
>  
>  
>  
>  
>  
> 26. apr. 2017 kl. 09.29 skrev Georgi Chakarov  >:
>  
> Hi Nick,
>  
> Thanks for your response!
>  
> See my comments below.
>  
> Regards,
>  
> Georgi
>  
> From: Shurajit Dutta [mailto:shurajitdu...@gmail.com 
> ] 
> Sent: Wednesday, April 26, 2017 6:02 AM
> To: Georgi Chakarov  >
> Cc: dhis2-us...@lists.launchpad.net ; 
> dhis2-devs@lists.launchpad.net 
> Subject: Re: [Dhis2-users] Enter data for a future date in Event and Tracker 
> Capture
>  
> Hi Georgi,
>  
> 1. You can select "Date in future" for attributes/data elements within a 
> program to enter future dates
>  
> 
>  
> I need program stage date/Event reporting date to be future dates. You know 
> how in Data Entry app you can allow for entering data in the future, so from 
> the period drop-down you can select to enter data for 2018 for example, 
> regardless that it is 2017 now. I need the same for Events and Tracker 
> capture stages.
>  
>  
> 2. Does the use of program indicators not solve this issue? You could select 
> those months as the period of interest during analysis.
>  
> The problem here is that the program indicators do not calculate properly. 
> Let me give you an example. My period is May, 1 2016 – April, 30 2017 (this 
> is Fiscal year 2017). I have been entering data for one Tracker program from 
> May,1 to April, 30 daily. I have built a program indicator of interest. When 
> I go to reporting I want to see ONE number, which is the sum/average/other 
> calculation of all months from May 2016 to April 2017. So, I select all these 
> months and put them in the reporting filter (I do not want them in 
> dimension). The reporting module fails to calculate the data properly for 
> these months, because they are in two different years.
> This problem is related to other malfunction in tracker:
>  
> When selecting monthly, six-monthly, yearly period for repeatable program 
> stages you can't create a stage for a year different than the year of 
> enrollment.
>  
> Example
>  
> Program stage is six-monthly
>  
> 
>  
>  
> Enrollment date is in 2015
>  
> 
>  
> Current date is 2017
>  
> 
>  
> DHIS2 does not allow to create a six-monthly stages for 2016. Note how the 
> arrow used to go to next period (2016) is inactive. The only possible options 
> are the two six-monthly periods in 2015. 2014 is not active 

Re: [Dhis2-devs] EC - possible program rule bug - triggering "hidefield" when clearing dates

[Olav Poppe]

Hi,
to add to this, it looks like it is only happening when the value that should 
be cleared is 0, so overwriting 0 with null.

Olav


> 24. apr. 2017 kl. 14.18 skrev Olav Poppe :
> 
> Hi devs,
> I’m have some problems with a program rule in EC: 
> The rule is if a date data element is empty, a numeric data element field 
> should be cleared and hidden. However, the rule is not triggered when the 
> date field has been filled and is later cleared. I have the exact same rule 
> set up in TC, and it works correctly. This is happening in 2.25 and 2.26. Any 
> advice?
> 
> For testing purposes, I added a second «show warning on completion» action to 
> the same rule, and this is triggered correctly when completing the event. In 
> other words, the formula for checking if the date is empty is correct, but 
> the hide action is not triggered.
> 
> Regards
> Olav
> 
> 
> 
> 
> 
> 
> ___
> 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


___
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] Auto-Generated Client UICs in Tracker v2.25

[Markus Bekken]

Also, you can vote for this issue, and add your specific requirements in the 
comments: 
https://jira.dhis2.org/browse/DHIS2-434


> 25. apr. 2017 kl. 17.49 skrev Em Le Hong :
> 
> You can use script on custom form. Until now, there's no way for default form 
> to generate based on tracked entity attributes.
> 
> On Tue, Apr 25, 2017 at 5:48 PM, Brian O'Donnell  > wrote:
> Hi all,
> 
> I'm curious if anyone has experience in auto-generating Unique Identifier 
> Codes (UICs) in tracker capture module (v2.25 or below), or if there is a 
> best practices document out there.
> 
> We are capturing sensitive information about clients through android tracker. 
> The service provider would like to capture name and phone number data, but 
> restrict viewing of these data to higher-level users. Data entry roles should 
> only be able to search based on a system-generated UIC. You should be able to 
> construct and re-construct UICs based on client data, as in the diagram from 
> PSI below.
> 
> 
> So we do not need a randomly generated ID for the tracked entity, but a 
> script which constructs a custom string attribute based on other tracked 
> entity attributes, similar to this app, but built directly into DHIS2 form: 
> https://play.google.com/store/apps/details?id=org.eyeseetea.uicapp=en 
> 
> 
> I am not the only one who has requested this 
> (https://lists.launchpad.net/dhis2-devs/msg47211.html 
> ) but I cannot find a 
> manual or correspondence online. Happy to provide more details on use case on 
> request.
> 
> Brian
> -- 
>    Brian O'Donnell, MPAff
> Informatics Project Manager
> bodonn...@akros.com  
> 
> ___
> 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 
> 
> 
> 
> 
> 
> -- 
> Em Le Hong
> DHIS2 Implementation| HISP Vietnam 
> em.hispviet...@gmail.com  | Skype: 
> em.hispviet...@gmail.com 
> 
> 
> 
> 
> 
> ___
> 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

___
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] Enter data for a future date in Event and Tracker Capture

[Markus Bekken]

Hi Georgi and Nick

The tracker does not allow allow event dates in the future. This restriction is 
probably there because most(all so far?) tracker use cases register actual 
events that already has happened. Knowing nothing about your usecase: Can you 
model it slightly differently, capturing the future date a data element instead 
of the event date?

Markus






> 26. apr. 2017 kl. 09.29 skrev Georgi Chakarov :
> 
> Hi Nick,
>  
> Thanks for your response!
>  
> See my comments below.
>  
> Regards,
>  
> Georgi
>  
> From: Shurajit Dutta [mailto:shurajitdu...@gmail.com 
> ] 
> Sent: Wednesday, April 26, 2017 6:02 AM
> To: Georgi Chakarov  >
> Cc: dhis2-us...@lists.launchpad.net ; 
> dhis2-devs@lists.launchpad.net 
> Subject: Re: [Dhis2-users] Enter data for a future date in Event and Tracker 
> Capture
>  
> Hi Georgi,
>  
> 1. You can select "Date in future" for attributes/data elements within a 
> program to enter future dates
>  
> 
>  
> I need program stage date/Event reporting date to be future dates. You know 
> how in Data Entry app you can allow for entering data in the future, so from 
> the period drop-down you can select to enter data for 2018 for example, 
> regardless that it is 2017 now. I need the same for Events and Tracker 
> capture stages.
>  
>  
> 2. Does the use of program indicators not solve this issue? You could select 
> those months as the period of interest during analysis.
>  
> The problem here is that the program indicators do not calculate properly. 
> Let me give you an example. My period is May, 1 2016 – April, 30 2017 (this 
> is Fiscal year 2017). I have been entering data for one Tracker program from 
> May,1 to April, 30 daily. I have built a program indicator of interest. When 
> I go to reporting I want to see ONE number, which is the sum/average/other 
> calculation of all months from May 2016 to April 2017. So, I select all these 
> months and put them in the reporting filter (I do not want them in 
> dimension). The reporting module fails to calculate the data properly for 
> these months, because they are in two different years.
> This problem is related to other malfunction in tracker:
>  
> When selecting monthly, six-monthly, yearly period for repeatable program 
> stages you can't create a stage for a year different than the year of 
> enrollment.
>  
> Example
>  
> Program stage is six-monthly
>  
> 
>  
>  
> Enrollment date is in 2015
>  
> 
>  
> Current date is 2017
>  
> 
>  
> DHIS2 does not allow to create a six-monthly stages for 2016. Note how the 
> arrow used to go to next period (2016) is inactive. The only possible options 
> are the two six-monthly periods in 2015. 2014 is not active either.
>  
> 
>  
>  
>  
> Nick
>  
> On Tue, Apr 25, 2017 at 9:53 PM, Georgi Chakarov  > wrote:
> Hello DHIS2 users and devs!
>  
> I have two questions:
> 1)  Is there a way to enter data for a future date in Event and Tracker 
> capture? The latest date that could be selected in these two apps at data 
> entry is the current date.
> 
>  
> 
> 2)  Has someone worked with project periods that are outside of the 
> available periods in DHIS2? I have a client that uses Fiscal Year May, 1 – 
> April, 30 and this is causing a real trouble at data entry as well as 
> reporting.
> 
> For example, the period from May, 1 2015 – April, 30 2016 is defined as 
> Fiscal Year 2016. Data is entered daily in Event and Tracker Capture. How do 
> we enter data so that we fall under this specific reporting period and how do 
> we report an aggregate number for the entire 2016 Fiscal Year?
> 
> [Not to mention that TRACKER DOES NOT correctly aggregate reports when 
> selecting two different years and setting them as report filter in the 
> reports layout, which is an option to display one aggregate number for 2 
> years.]
> 
>  
> 
>  
> Your input is highly appreciated and awaited!
>  
> Thanks,
>  
> Georgi
>  
>   
> Georgi Chakarov, CIA | geo...@logicaloutcomes.net 
>  | +1-647-478-5634 x 104 
>  | LogicalOutcomes c/o Centre for Social Innovation, 
> 720 Bathurst Street, Toronto Canada M5S 2R4 | You may unsubscribe from 
> receiving commercial electronic messages from LogicalOutcomes by emailing 
> i...@logicaloutcomes.net 
>  
> 
> ___
> 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 
> 

Re: [Dhis2-devs] Bug in event reports page display all elements on initial load

[Em Le Hong]

Hi Hari,

I have the same issue with you and I already created a ticket on Jira site.
Hope they will implement it soon.
https://jira.dhis2.org/browse/DHIS2-1441

I also tried with sharing settings, but it doesn't work as expectation.

On Wed, Apr 26, 2017 at 12:39 PM, Hari Krishna 
wrote:

> Hello there,
>
> We found a small bug in event reports page for DHIS version 2.25 and 2.26.
> On initial load of event reports page, when we select a program, both data
> elements and program indicators are listed under aggregated values tab. But
> we expecting to see only data elements under aggregated values tab. Is this
> the expected behavior? If so, we have sent a pull requests to fix this on
> 2.25  and 2.26
> .
>
> --
> Hari Krishna
> Developer
> Email harik...@thoughtworks.com
> Telephone +917660029495
> [image: ThoughtWorks]
> 
>
> ___
> 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
>
>


-- 
*Em Le Hong*
DHIS2 Implementation| *HISP Vietnam *
em.hispviet...@gmail.com | *Skype:* em.hispviet...@gmail.com
___
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] IMPLEMENTATION OF STAND ALONE TRACKER CAPTURE/PROGRAMS

[Stanley Kalyati]

Thanks everyone for such insight and i hope the development team is working
on this,though issues of duplication especially with my program where we
use Unique Identifiers for our Tracked Entities.

I guess improving internet connectivity is a better devil at the moment.

My regards

Stanley

On Wed, Apr 26, 2017 at 6:14 AM, Prosper BT  wrote:

> Thanks Team for sharing,
>
> We equally challenged here in Uganda with one implementation and given the
> complexity and amount of data to be entered there is no way we can you use
> android tablet or phone app. May be trying chromebook.
>
> BTW anyone who has tried chromebook?
>
> Calle on supporting offline web tracker capture, still comes to the issues
> of duplication of data while offline and access to the old records for
> updates.
>
> Regards
>
> Prosper Behumbiize, MPH
> DHIS2 Implementation| HISP Uganda
> pros...@hispuganda.org  | pros...@dhis2.org | Skype:
> prospertb
>
> On Wed, Apr 26, 2017 at 3:36 AM, Calle Hedberg 
> wrote:
>
>> Stanley,
>>
>> I understand your frustration, and others are having similar challenges.
>> Although Em Le Hong is factually correct when stating that Tracker Capture
>> App do work in offline mode, the current APK has significant stability and
>> functionality issues and it's not easy to e.g. get new functionality
>> developed on the browser side supported.
>>
>> A new Android SDK is being worked on that hopefully will address some of
>> these issues, but it is right now not clear when it will be ready
>> (according to the Roadmap for 2.27 it should be ready to piloting now, but
>> it is not).
>>
>> I also recently asked Abyot what the main issues/challenges are for
>> supporting offline Tracker capture, but I've received no response to that
>> yet (he might be on paternity leave - not sure).
>>
>> You are suggesting the use of localised installations with "uploading of
>> meta-data" (I presume you mean uploading of Tracker Enrollment & staging
>> data, not "meta-data"). I'm not aware of anybody who has tried that for a
>> national/wide-area Tracker Program, but I suspect it will be an uphill
>> battle - in particular if your enrollments are supposed to be unique across
>> the whole system (you don't provide any details about which country/area
>> this is, how complicated your tracker programs are, the tentative time-span
>> for each program, etc).
>>
>> My first option would be a major effort to improve connectivity, using a
>> mix of booster antennas, wide-area wireless, and/or VSAT or similar. If you
>> go the distributed installation route, I would NOT use "manual" email but
>> rather develop a customised solution for automated, asynchronous
>> communication between the local installation and the central server. It's
>> would require a lot of development work, though, and every new DHIS2
>> version release might further maintenance of such a custom solution.
>>
>> So in my view, rather use those resources to improve connectivity
>>
>> My 2c worth
>>
>> Regards from Freetown, Sierra Leone
>> Calle
>>
>> On 25 April 2017 at 18:19, Em Le Hong  wrote:
>>
>>> Hi Stanley,
>>>
>>> You can use DHIS2 Android apps, from google Play Store, type dhis2, you
>>> will see a list of application (tracker capture, event capture, data
>>> capture...). When you install DHIS2 android app on your Android devices,
>>> you just need internet for first time login to download metadata into your
>>> devices. Then you can use it offline to register tracked entity instance,
>>> do data, create event... When your device can connect to internet, it will
>>> synchronize and send all offline data to the server.
>>>
>>> You can read more on https://docs.dhis2.org/mast
>>> er/en/android/html/dhis2_android_user_man.html
>>>
>>> Hope this can help.
>>>
>>> On Thu, Apr 20, 2017 at 1:56 PM, Stanley Kalyati 
>>> wrote:
>>>
 I have a program in tracker and we have issues with internet
 connectivity in many areas.We resorted to using android phones but this has
 not improved situation as the phone too need to be online to access the
 Android Tracker Capture.

 I am now thinking of going offline and then have the data officers
 download the metadata and send via email and then i can upload in the main
 system.

 I have used this system before but with aggregate data and not Tracker
 Capture.

 My fear is that if i install a copy of the system on stand alone
 machines,chances of duplicates in the enrollment and events is likely to
 happen as different Data officers across the country will be sending in
 metadata for upload.

 My questions are:

 1-Is there anyone here who has implemented such a program on stand
 alone machines? If yes kindly share your experience

 2-Does this type of implementation bringforth duplicates within the
 program? or when uploading