Re: [Dhis2-users] [Dhis2-devs] Program indicators export to another system

2018-02-05 Thread Knut Staring
Agree very much on having a GUI/app for mapping. For example, I am currently setting up an instance with simplified geometries for the whole world based on GADM - with the hierarchy down to admin level 1, 2, 3, 4 created based on the shapefiles and using the codes from GADM for admin1 and admin2

Re: [Dhis2-users] [Dhis2-devs] Program indicators export to another system

2018-02-05 Thread Aaron C White
Elmarie, The devs might correct me, but I don't think that the code import scheme would account for different data element ids since the import tool would be trying to match a code for the programIndicator itself and not the configured expression or filter. I ran into this problem last year and

Re: [Dhis2-users] [Dhis2-devs] Program indicators export to another system

2018-02-05 Thread Calle Hedberg
Knut I did that for IDSR/Malaria in order to "map" local IDSR program indicators to the WHO aggregated malaria data elements. It is, frankly, a painful and "expert" approach to the problem, and in my opinion very difficult to maintain. The presumably simplest solution is to expand the "Data

Re: [Dhis2-users] [Dhis2-devs] Program indicators export to another system

2018-02-01 Thread Knut Staring
Hi Elmarie, This is an important issue, and I expect others will have a better answer, but one approach could perhaps be to replace the UID for the Programme Indicators with the desired data element UID. I suppose that would have to be done either directly in the database or through the API, but