date:20151014

Re: [Dhis2-users] [Dhis2-devs] Difference between attribute and disaggregate option for category combos

2015-10-14 Thread Lars Helge Øverland

On Wed, Oct 14, 2015 at 5:42 PM, Elmarie Claasen  wrote:

> Hi Lars,
>
>
>
> Thanks that is what I did.
>
> A general question – Isn’t this a way to easily add targets for certain
> data elements with known denominators eg population by setting up a dataset
> with e.g. Yearly or Quarterly period and then capture the target values as
> dataset attributes rather than create a new data element for the target
> which makes analysis more tricky since you need to link the 2 data elements
> to each other somehow?
>
>
>

Hi Elmarie,

yes that would be a feasible approach.

The downside is that if you now load this data element in pivot
tables/charts, by default you will get the real value + the target. So for
people who are not aware of this target dimension/category, they might see
values twice as high as that they would expect.

So it works given that this is handled through user training or other ways.

Lars




> Regards,
>
>
>
> *Elmarie Claasen*
>
> [image: Hisp logo]
>
> Project Manager
>
> Health Information Systems Program
>
> Tel:  041-367 1027
>
> Cell: 082 374 2209
>
> E-mail: elma...@hisp.org
>
> Skype:  elmarie.claasen52
>
>
>
>
>
> This message and any attachments are subject to a disclaimer published at 
> http://www.hisp.org/policies.html#comms_disclaimer
> .   Please read the disclaimer before opening any attachment or taking any
> other action in terms of this electronic transmission.
> If you cannot access the disclaimer, kindly send an email to 
> disclai...@hisp.org
> and a copy will be provided to you. By replying to this e-mail or opening
> any attachment you agree to be bound by the provisions of the disclaimer.
>
>
>
> *From:* Lars Helge Øverland [mailto:larshe...@gmail.com]
> *Sent:* 13 October 2015 02:00 PM
> *To:* Elmarie Claasen
> *Cc:* DHIS 2 Developers list; DHIS 2 Users list
> *Subject:* Re: [Dhis2-devs] Difference between attribute and disaggregate
> option for category combos
>
>
>
> Hi Elmarie,
>
>
>
> the data dimension type on category and category combo indicates whether
> you want to use these as disaggregation categories (linked to data
> elements) or attribute categories (linked to data sets). So attributes
> refers to data set categories.
>
>
>
> If you would like to create a data set category (e.g. one category option
> for "preliminary" and one for "validated"), then you need to set these to
> "attribute". So:
>
>
>
> Category combo: "Output type" - data dimension set to "attribute".
>
> Category: "Output type" -  data dimension set to "attribute".
>
> Category options: "Preliminary output" and "Validated output".
>
>
>
> You can now assign the "Output type" category combo to your data set, and
> the data entry screen will allow you to choose between preliminary and
> validated before entering data.
>
>
>
> regards,
>
>
> Lars
>
>
>
>
>
>
>
> On Tue, Oct 13, 2015 at 1:34 PM, Elmarie Claasen  wrote:
>
> Hi all,
>
>
>
> I need to set up a dhis2 instance in which we want to capture the data for
> specific month twice e.g. preliminary output and validated output. We don’t
> need those to be added together as usual in a data element category
> combination.
>
>
>
> I have been looking into dataset category combinations but that looks a
> lot similar in the manual to attributes. Would like clarity on the
> difference between using disaggregate or attribute when selecting data
> dimension on a catcombo.
>
>
>
> Any suggestions on alternatives would be welcome J
>
>
>
> Regards,
>
>
>
> *Elmarie Claasen*
>
> [image: Hisp logo]
>
> Project Manager
>
> Health Information Systems Program
>
> Tel:  041-367 1027
>
> Cell: 082 374 2209
>
> E-mail: elma...@hisp.org
>
> Skype:  elmarie.claasen52
>
>
>
>
>
> This message and any attachments are subject to a disclaimer published at 
> http://www.hisp.org/policies.html#comms_disclaimer
> .   Please read the disclaimer before opening any attachment or taking any
> other action in terms of this electronic transmission.
> If you cannot access the disclaimer, kindly send an email to 
> disclai...@hisp.org
> and a copy will be provided to you. By replying to this e-mail or opening
> any attachment you agree to be bound by the provisions of the disclaimer.
>
>
>
>
>
> *This message and any attachments are subject to a disclaimer published at
> http://www.hisp.org/policies.html#comms_disclaimer
> .  Please read the
> disclaimer before opening any attachment or taking any other action in
> terms of this electronic transmission.  If you cannot access the
> disclaimer, kindly send an email to disclai...@hisp.org
>  and a copy will be provided to you. By replying to
> this e-mail or opening any attachment you agree to be bound by the
> provisions of the disclaimer.*
>
>
> ___
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to : dhis2-d...@lists.launchpad.net
>

Re: [Dhis2-users] [Dhis2-devs] Difference between attribute and disaggregate option for category combos

2015-10-14 Thread Elmarie Claasen

Hi Lars,

 

Thanks that is what I did. 

A general question – Isn’t this a way to easily add targets for certain data 
elements with known denominators eg population by setting up a dataset with 
e.g. Yearly or Quarterly period and then capture the target values as dataset 
attributes rather than create a new data element for the target which makes 
analysis more tricky since you need to link the 2 data elements to each other 
somehow?

 

Regards,

 

Elmarie Claasen

Hisp logo

Project Manager

Health Information Systems Program

Tel:  041-367 1027

Cell: 082 374 2209

E-mail:   elma...@hisp.org

Skype:  elmarie.claasen52 

 

 

This message and any attachments are subject to a disclaimer published at  
 
http://www.hisp.org/policies.html#comms_disclaimer .   Please read the 
disclaimer before opening any attachment or taking any other action in terms of 
this electronic transmission. 
If you cannot access the disclaimer, kindly send an email to  
 disclai...@hisp.org and a copy will be provided to 
you. By replying to this e-mail or opening any attachment you agree to be bound 
by the provisions of the disclaimer. 

 

From: Lars Helge Øverland [mailto:larshe...@gmail.com] 
Sent: 13 October 2015 02:00 PM
To: Elmarie Claasen
Cc: DHIS 2 Developers list; DHIS 2 Users list
Subject: Re: [Dhis2-devs] Difference between attribute and disaggregate option 
for category combos

 

Hi Elmarie,

 

the data dimension type on category and category combo indicates whether you 
want to use these as disaggregation categories (linked to data elements) or 
attribute categories (linked to data sets). So attributes refers to data set 
categories.

 

If you would like to create a data set category (e.g. one category option for 
"preliminary" and one for "validated"), then you need to set these to 
"attribute". So:

 

Category combo: "Output type" - data dimension set to "attribute".

Category: "Output type" -  data dimension set to "attribute".

Category options: "Preliminary output" and "Validated output".

 

You can now assign the "Output type" category combo to your data set, and the 
data entry screen will allow you to choose between preliminary and validated 
before entering data.

 

regards,


Lars

 

 

 

On Tue, Oct 13, 2015 at 1:34 PM, Elmarie Claasen  wrote:

Hi all,

 

I need to set up a dhis2 instance in which we want to capture the data for 
specific month twice e.g. preliminary output and validated output. We don’t 
need those to be added together as usual in a data element category 
combination. 

 

I have been looking into dataset category combinations but that looks a lot 
similar in the manual to attributes. Would like clarity on the difference 
between using disaggregate or attribute when selecting data dimension on a 
catcombo. 

 

Any suggestions on alternatives would be welcome J

 

Regards,

 

Elmarie Claasen

Hisp logo

Project Manager

Health Information Systems Program

Tel:  041-367 1027

Cell: 082 374 2209

E-mail:   elma...@hisp.org

Skype:  elmarie.claasen52 

 

 

This message and any attachments are subject to a disclaimer published at  
 
http://www.hisp.org/policies.html#comms_disclaimer .   Please read the 
disclaimer before opening any attachment or taking any other action in terms of 
this electronic transmission. 
If you cannot access the disclaimer, kindly send an email to  
 disclai...@hisp.org and a copy will be provided to 
you. By replying to this e-mail or opening any attachment you agree to be bound 
by the provisions of the disclaimer. 

 

 

This message and any attachments are subject to a disclaimer published at 
http://www.hisp.org/policies.html#comms_disclaimer.  Please read the disclaimer 
before opening any attachment or taking any other action in terms of this 
electronic transmission.  If you cannot access the disclaimer, kindly send an 
email to disclai...@hisp.org and a copy will be provided to you. By replying to 
this e-mail or opening any attachment you agree to be bound by the provisions 
of the disclaimer.


___
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-d...@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  

 


-- 


*This message and any attachments are subject to a disclaimer published at 
http://www.hisp.org/policies.html#comms_disclaimer 
.  Please read the 
disclaimer before opening any attachment or taking any other action in 
terms of this electronic transmission.

[Dhis2-users] DHIS2 analytics table returns empty

2015-10-14 Thread Yemi Awe

Dear Team,
Upgrading to dhis2.20 is returning empty rows in the analytics_20xx.

The logs shows
* WARN  2015-10-10 11:40:15,779 Duplicate object: [Data element: 584 option
combo: 486 period: 795 org unit: 51 org unit group: 0 value: 55.0]
(AbstractBatchHandler.java [SimpleAsyncTaskExecutor-72])
* WARN  2015-10-10 11:40:15,779 Duplicate object: [Data element: 584 option
combo: 488 period: 795 org unit: 51 org unit group: 0 value: 12.0]
(AbstractBatchHandler.java [SimpleAsyncTaskExecutor-72])
* WARN  2015-10-10 11:40:15,779 Duplicate object: [Data element: 574 option
combo: 485 period: 795 org unit: 51 org unit group: 0 value: 24.0]
(AbstractBatchHandler.java [SimpleAsyncTaskExecutor-72])
* WARN  2015-10-10 11:40:15,779 Duplicate object: [Data element: 573 option
combo: 487 period: 795 org unit: 51 org unit group: 0 value: 77.0]
(AbstractBatchHandler.java [SimpleAsyncTaskExecutor-72])
* WARN  2015-10-10 11:40:15,779 Duplicate object: [Data element: 574 option
combo: 486 period: 795 org unit: 51 org unit group: 0 value: 28.0]
(AbstractBatchHandler.java [SimpleAsyncTaskExecutor-72])


I set all the dataelement to default then i have the WARN in the log

* WARN  2015-10-13 14:45:25,591 Ignoring category combo, not valid:
[IdentifiableObject: id='14', uid='JKlMSbFzlum', code='null',
name='default', created='Mon Mar 17 11:25:58 WAT 2014', lastUpdated='Tue
Oct 13 14:34:48 WAT 2015', class='class
org.hisp.dhis.dataelement.DataElementCategoryCombo"']
(DefaultResourceTableService.java [taskScheduler-2])

I installed a fresh 2.20 version and created a sample data and the
analytics_2015 successfully generated.

I found out that the fresh 2.20 version has _categorystructure with 4
columns and the old one has 2 columns.

As at this moment the old version is not generating the analytics_20xx even
though it is successful the tables are empty.

Any idea pls...


Tools
* Postgresql
* Tomcat 7.0
* jdk 1.8.0_1xxx
* Firefox, Chrome
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp

[Dhis2-users] XML Import of Org Unit Attribute

2015-10-14 Thread Laura E. Lincks

Version: 2.20
Build: 19958

I need to update existing Org Units with a new, non-existing Org Unit
attribute *values* using XML meta-data import.

I'm trying to create the simplest XML to do this, excluding tags which have
no bearing on the update. I just need to add an attribute value to each Org
Unit.

*I've noticed the following:*
I must include *openingDate*, *name* and *shortName* even though I am not
affecting any of those properties (these did not appear to be mandatory in
2.18)
If I do not include *created* a new *created* date is generated
If I do not include *(u)id* a new (u)*id* is generated (tag is "id", column
name is "uid")

I would think that generating new *uid *and *created* values could cause
problems with data integrity. Is this intentional? Are Org Unit records
being deleted and recreated when running an XML import as it appears to? I
would assume that if I don't include those tags it would retain whatever
values already exist for each record.

It seems that in order to ONLY add a non-existing attribute to each Org
Unit (and not alter the *uid* or *created*  values) I must include the
following tags in my XML file:

*For organisationUnit:*
id
created
name
shortName
openingDate

*For Org Unit Attribute:*
code
name
id
value
externalAccess (maybe??)

Can someone confirm or comment on my findings and questions?
Thanks.

*Laura E. Lincks*
Database Manager/Developer
ICAP - Columbia University
Mailman School of Public Health
60 Haven Ave, Floor B1
New York, NY 10032
Tel: 212 304 7132
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-users] [Dhis2-devs] XML Import of Org Unit Attribute

2015-10-14 Thread Morten Olav Hansen

Hi Laura

The simplest way to get to know what is required for a import is to go to
/api/schemas, in your case you should have a look at
/api/schemas/organisationUnit.

We do not support any kind of patching when it comes to multiple imports,
so you have to include the full object. If you are only updating one single
OU, we do support single/multiple value PATCHING, please see [1]

[1] https://www.dhis2.org/doc/snapshot/en/developer/html/ch01s09.html#d5e789

--
Morten

On Thu, Oct 15, 2015 at 9:45 AM, Laura E. Lincks <
laura.lin...@icap.columbia.edu> wrote:

> Version: 2.20
> Build: 19958
>
> I need to update existing Org Units with a new, non-existing Org Unit
> attribute *values* using XML meta-data import.
>
> I'm trying to create the simplest XML to do this, excluding tags which
> have no bearing on the update. I just need to add an attribute value to
> each Org Unit.
>
> *I've noticed the following:*
> I must include *openingDate*, *name* and *shortName* even though I am not
> affecting any of those properties (these did not appear to be mandatory in
> 2.18)
> If I do not include *created* a new *created* date is generated
> If I do not include *(u)id* a new (u)*id* is generated (tag is "id",
> column name is "uid")
>
> I would think that generating new *uid *and *created* values could cause
> problems with data integrity. Is this intentional? Are Org Unit records
> being deleted and recreated when running an XML import as it appears to? I
> would assume that if I don't include those tags it would retain whatever
> values already exist for each record.
>
> It seems that in order to ONLY add a non-existing attribute to each Org
> Unit (and not alter the *uid* or *created*  values) I must include the
> following tags in my XML file:
>
> *For organisationUnit:*
> id
> created
> name
> shortName
> openingDate
>
> *For Org Unit Attribute:*
> code
> name
> id
> value
> externalAccess (maybe??)
>
> Can someone confirm or comment on my findings and questions?
> Thanks.
>
> *Laura E. Lincks*
> Database Manager/Developer
> ICAP - Columbia University
> Mailman School of Public Health
> 60 Haven Ave, Floor B1
> New York, NY 10032
> Tel: 212 304 7132
>
> ___
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to : dhis2-d...@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help   : https://help.launchpad.net/ListHelp

Re: [Dhis2-users] [Dhis2-devs] Difference between attribute and disaggregate option for category combos

Re: [Dhis2-users] [Dhis2-devs] Difference between attribute and disaggregate option for category combos

[Dhis2-users] DHIS2 analytics table returns empty

[Dhis2-users] XML Import of Org Unit Attribute

Re: [Dhis2-users] [Dhis2-devs] XML Import of Org Unit Attribute

5 matches

Site Navigation

Mail list logo

Footer information