dhis2-users team mailing list archive

[Isaiah Nyabuto <isaiahnyabuto@xxxxxxxxx>]

Hi Martin,

Yes, basically the Idea would be to extract metadata/data from one instance
(source), do some transformations and load into the other instance
(destination). You can extract and load the metadata/data directly using
the dhis2 import/export App or work extensively using dhis2 APIs. There are
various ETL tools that can be used in the process,  I prefer using R.
The following guide can walk you through the whole process.
http://rstudio-pubs-static.s3.amazonaws.com/139589_a81125b491094fe3b5e79e3bcea0a56b.html


@Edward, I would like to see what you guys are working on J


Thank you





On Wed, Apr 4, 2018 at 4:28 PM, Edward Robinson <
erobinson@xxxxxxxxxxxxxxxxxx> wrote:

> We’re currently working on something for this – a desktop app that runs on
> Windows / Mac / Linux that allows you to specify some parameters to ‘map’
> from one side to the other and a shell app that runs on a Linux box and
> reads the config file created by the desktop app once a day to transfer
> data from the one to the other using the API.  We specifically need to
> transfer aggregate program indicator values from one side to data elements
> on the other.
>
> Things to think about:
>
>    - You need to map Organisational units on both sides
>    - You need to specify the from element + category option combo /
>    indicator and the to element + category option combo on the other side
>    - You need to specify the period type and optionally a start / end
>    date so that the system knows what periods to target.
>
> The system is still in development but will effectively enable incremental
> updates by recording periods already taken care of for each source /
> destination / ou.
>
> I’ll keep you posted, at this stage we’re not 100% sure when it will be
> complete, but it should be in the next few weeks.
>
> Ed
>
>
>
> *From:* Dhis2-users <dhis2-users-bounces+erobinson=projectbalance.com@
> lists.launchpad.net> *On Behalf Of *Martin Van Aken
> *Sent:* Tuesday, 09 January 2018 8:56 PM
> *To:* dhis2-users <dhis2-users@xxxxxxxxxxxxxxxxxxx>
> *Subject:* [Dhis2-users] Import/Export data between similar but distinct
> systems
>
>
>
> Hello DHIS2 community,
>
> We need to make frequent import/export between two different DHIS2
> systems. While they are similar and the format "fits", we know some
> differences, mainly:
>
>
>
> - The org units concerned exist on both sides but with different ids
>
> - Same for the data elements
>
> - In some situation, the export value may be an indicator, to be imported
> in a data element
>
>
>
> I can imagine making the export in CSV, then having a "matching sheet" in
> XLS with the link between OU in the source system and OU in the destination
> system.
>
>
>
> Is someone doing those kind of operations? What's your typical flow/way of
> working?
>
> I think I remember Lars presenting some feature helping with this on one
> of the last DHIS2 releases, but I'm not sure.
>
>
>
> Martin
>
> --
>
> *Martin Van Aken - Freelance Enthusiast Developer*
>
>
>
> Mobile : +32 486 899 652
>
>
>
> Follow me on Twitter : @martinvanaken <http://twitter.com/martinvanaken>
>
> Call me on Skype : vanakenm
>
> Hang out with me : martin@xxxxxxxxxxxxxxxx
>
> Contact me on LinkedIn : http://www.linkedin.com/in/martinvanaken
>
> Company website : www.joyouscoding.com
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-users
> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
--------------------------------------------------------------------------------
Isaiah Nyabuto
+254 729 572 616
Bsc. Health Records Management & Informatics, JKUAT.