"Data output and analysis organisation units" selection NOT respected an Analytics

Dear Team,

Am trying to look for this bug and whether it was fixed but seem its not because I have tested on the demo and the problem still exists.

  1. When we create users especially the district or lower level users, we restrict analysis to their Orgunits

I created a user ‘prosper’ on the demo and only assigned to Bo districts then put him a user group for dashboard sharing.

image

​When you use the user assigned Orgunits, it will shows the the entire country hierarchy in the the dashboard.

image

Regards

···

Prosper Behumbiize, MPH
Global HISP| University Of Oslo/HISP Uganda
+256 752 751 776 | +256 776 139 139

prosper@hispuganda.org | prosper@dhis2.org | Skype: prospertb

Dear Team,

This issues is still existing even in 2.23

Regards

image

image

···

On Wed, Apr 20, 2016 at 3:27 PM, Prosper BT ptb3000@gmail.com wrote:

Dear Team,

Am trying to look for this bug and whether it was fixed but seem its not because I have tested on the demo and the problem still exists.

  1. When we create users especially the district or lower level users, we restrict analysis to their Orgunits

I created a user ‘prosper’ on the demo and only assigned to Bo districts then put him a user group for dashboard sharing.

​When you use the user assigned Orgunits, it will shows the the entire country hierarchy in the the dashboard.

Regards

Prosper Behumbiize, MPH
Global HISP| University Of Oslo/HISP Uganda
+256 752 751 776 | +256 776 139 139

prosper@hispuganda.org | prosper@dhis2.org | Skype: prospertb

Prosper Behumbiize, MPH
Global HISP| University Of Oslo/HISP Uganda
+256 752 751 776 | +256 776 139 139

prosper@hispuganda.org | prosper@dhis2.org | Skype: prospertb

Hi Prosper,

in fact it is the “data capture / maintenance” org units which are used as basis for the “user org unit”.

The rationale behind this is that a typical user works at a district (and has the district as data capture org unit), and should be able to see the entire country or province for analysis. So here it makes sense to have the “user org unit” referring to the district in order to provide meaningful and relevant charts / pivots.

In your case, which “data capture” org unit did you select? I am guessing Sierra Leone. Try setting it to “Bo”, clear cache and try again.

So a potential weakness here is that one is allowed to specify a data output org unit which is below the data capture org unit. This situation will in fact lead to a conflict / validation error when you create analytics favorites with user org units.

image

image

···

On Wed, Apr 27, 2016 at 6:49 AM, Prosper BT ptb3000@gmail.com wrote:

Dear Team,

This issues is still existing even in 2.23

Regards

On Wed, Apr 20, 2016 at 3:27 PM, Prosper BT ptb3000@gmail.com wrote:

Dear Team,

Am trying to look for this bug and whether it was fixed but seem its not because I have tested on the demo and the problem still exists.

  1. When we create users especially the district or lower level users, we restrict analysis to their Orgunits

I created a user ‘prosper’ on the demo and only assigned to Bo districts then put him a user group for dashboard sharing.

​When you use the user assigned Orgunits, it will shows the the entire country hierarchy in the the dashboard.

Regards

Prosper Behumbiize, MPH
Global HISP| University Of Oslo/HISP Uganda
+256 752 751 776 | +256 776 139 139

prosper@hispuganda.org | prosper@dhis2.org | Skype: prospertb


Prosper Behumbiize, MPH
Global HISP| University Of Oslo/HISP Uganda
+256 752 751 776 | +256 776 139 139

prosper@hispuganda.org | prosper@dhis2.org | Skype: prospertb

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

http://www.dhis2.org

Hi Prosper,

the “user org unit” / cache issue should be resolved in 2.23 now.

Could you please try again on your side?

regards,

Lars

image

image

···

On Tue, May 3, 2016 at 2:49 PM, Lars Helge Øverland lars@dhis2.org wrote:

Hi Prosper,

in fact it is the “data capture / maintenance” org units which are used as basis for the “user org unit”.

The rationale behind this is that a typical user works at a district (and has the district as data capture org unit), and should be able to see the entire country or province for analysis. So here it makes sense to have the “user org unit” referring to the district in order to provide meaningful and relevant charts / pivots.

In your case, which “data capture” org unit did you select? I am guessing Sierra Leone. Try setting it to “Bo”, clear cache and try again.

So a potential weakness here is that one is allowed to specify a data output org unit which is below the data capture org unit. This situation will in fact lead to a conflict / validation error when you create analytics favorites with user org units.

We also discovered another related weakness today related to how we treat user org units in analytics - we do not send the user id together with the USER_ORG_UNIT keyword in the URLs, which means that a proxy cache will potentially return data which does not correspond to various user’s USER_ORG_UNIT. We will fix this asap.

regards,

Lars

On Wed, Apr 27, 2016 at 6:49 AM, Prosper BT ptb3000@gmail.com wrote:

Dear Team,

This issues is still existing even in 2.23

Regards


Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

http://www.dhis2.org

On Wed, Apr 20, 2016 at 3:27 PM, Prosper BT ptb3000@gmail.com wrote:

Dear Team,

Am trying to look for this bug and whether it was fixed but seem its not because I have tested on the demo and the problem still exists.

  1. When we create users especially the district or lower level users, we restrict analysis to their Orgunits

I created a user ‘prosper’ on the demo and only assigned to Bo districts then put him a user group for dashboard sharing.

​When you use the user assigned Orgunits, it will shows the the entire country hierarchy in the the dashboard.

Regards

Prosper Behumbiize, MPH
Global HISP| University Of Oslo/HISP Uganda
+256 752 751 776 | +256 776 139 139

prosper@hispuganda.org | prosper@dhis2.org | Skype: prospertb


Prosper Behumbiize, MPH
Global HISP| University Of Oslo/HISP Uganda
+256 752 751 776 | +256 776 139 139

prosper@hispuganda.org | prosper@dhis2.org | Skype: prospertb

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

Hi Lars

Thanks tested with pivot tables and it works, looking to the fix in all the Analytics App and back porting to 2.22

Regards

image

image

···

On Mon, May 9, 2016 at 11:47 PM, Lars Helge Øverland lars@dhis2.org wrote:

Hi Prosper,

the “user org unit” / cache issue should be resolved in 2.23 now.

Could you please try again on your side?

regards,

Lars

On Tue, May 3, 2016 at 2:49 PM, Lars Helge Øverland lars@dhis2.org wrote:

Hi Prosper,

in fact it is the “data capture / maintenance” org units which are used as basis for the “user org unit”.

The rationale behind this is that a typical user works at a district (and has the district as data capture org unit), and should be able to see the entire country or province for analysis. So here it makes sense to have the “user org unit” referring to the district in order to provide meaningful and relevant charts / pivots.

In your case, which “data capture” org unit did you select? I am guessing Sierra Leone. Try setting it to “Bo”, clear cache and try again.

So a potential weakness here is that one is allowed to specify a data output org unit which is below the data capture org unit. This situation will in fact lead to a conflict / validation error when you create analytics favorites with user org units.

We also discovered another related weakness today related to how we treat user org units in analytics - we do not send the user id together with the USER_ORG_UNIT keyword in the URLs, which means that a proxy cache will potentially return data which does not correspond to various user’s USER_ORG_UNIT. We will fix this asap.

regards,

Lars

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

On Wed, Apr 27, 2016 at 6:49 AM, Prosper BT ptb3000@gmail.com wrote:

Dear Team,

This issues is still existing even in 2.23

Regards


Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

http://www.dhis2.org

On Wed, Apr 20, 2016 at 3:27 PM, Prosper BT ptb3000@gmail.com wrote:

Dear Team,

Am trying to look for this bug and whether it was fixed but seem its not because I have tested on the demo and the problem still exists.

  1. When we create users especially the district or lower level users, we restrict analysis to their Orgunits

I created a user ‘prosper’ on the demo and only assigned to Bo districts then put him a user group for dashboard sharing.

​When you use the user assigned Orgunits, it will shows the the entire country hierarchy in the the dashboard.

Regards

Prosper Behumbiize, MPH
Global HISP| University Of Oslo/HISP Uganda
+256 752 751 776 | +256 776 139 139

prosper@hispuganda.org | prosper@dhis2.org | Skype: prospertb


Prosper Behumbiize, MPH
Global HISP| University Of Oslo/HISP Uganda
+256 752 751 776 | +256 776 139 139

prosper@hispuganda.org | prosper@dhis2.org | Skype: prospertb

Prosper Behumbiize, MPH
Global DHIS2 Implementation| HISP Uganda/University Of Oslo
+256 752 751 776 | +256 776 139 139

prosper@hispuganda.org | prosper@dhis2.org | Skype: prospertb

Thanks. Fixed across all apps now down to 2.21.

regards,

Lars

image

image

···

On Tue, May 10, 2016 at 9:57 AM, Prosper BT ptb3000@gmail.com wrote:

Hi Lars

Thanks tested with pivot tables and it works, looking to the fix in all the Analytics App and back porting to 2.22

Regards

On Mon, May 9, 2016 at 11:47 PM, Lars Helge Øverland lars@dhis2.org wrote:

Hi Prosper,

the “user org unit” / cache issue should be resolved in 2.23 now.

Could you please try again on your side?

regards,

Lars

Prosper Behumbiize, MPH
Global DHIS2 Implementation| HISP Uganda/University Of Oslo
+256 752 751 776 | +256 776 139 139

prosper@hispuganda.org | prosper@dhis2.org | Skype: prospertb

On Tue, May 3, 2016 at 2:49 PM, Lars Helge Øverland lars@dhis2.org wrote:

Hi Prosper,

in fact it is the “data capture / maintenance” org units which are used as basis for the “user org unit”.

The rationale behind this is that a typical user works at a district (and has the district as data capture org unit), and should be able to see the entire country or province for analysis. So here it makes sense to have the “user org unit” referring to the district in order to provide meaningful and relevant charts / pivots.

In your case, which “data capture” org unit did you select? I am guessing Sierra Leone. Try setting it to “Bo”, clear cache and try again.

So a potential weakness here is that one is allowed to specify a data output org unit which is below the data capture org unit. This situation will in fact lead to a conflict / validation error when you create analytics favorites with user org units.

We also discovered another related weakness today related to how we treat user org units in analytics - we do not send the user id together with the USER_ORG_UNIT keyword in the URLs, which means that a proxy cache will potentially return data which does not correspond to various user’s USER_ORG_UNIT. We will fix this asap.

regards,

Lars

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

On Wed, Apr 27, 2016 at 6:49 AM, Prosper BT ptb3000@gmail.com wrote:

Dear Team,

This issues is still existing even in 2.23

Regards


Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

http://www.dhis2.org

On Wed, Apr 20, 2016 at 3:27 PM, Prosper BT ptb3000@gmail.com wrote:

Dear Team,

Am trying to look for this bug and whether it was fixed but seem its not because I have tested on the demo and the problem still exists.

  1. When we create users especially the district or lower level users, we restrict analysis to their Orgunits

I created a user ‘prosper’ on the demo and only assigned to Bo districts then put him a user group for dashboard sharing.

​When you use the user assigned Orgunits, it will shows the the entire country hierarchy in the the dashboard.

Regards

Prosper Behumbiize, MPH
Global HISP| University Of Oslo/HISP Uganda
+256 752 751 776 | +256 776 139 139

prosper@hispuganda.org | prosper@dhis2.org | Skype: prospertb


Prosper Behumbiize, MPH
Global HISP| University Of Oslo/HISP Uganda
+256 752 751 776 | +256 776 139 139

prosper@hispuganda.org | prosper@dhis2.org | Skype: prospertb

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org