Hi Martin,
when you say import/export I assume data value exchange here - correct?
The approach I recommend is using the "identifier schemes". This allows you
to keep multiple sets of identifiers (id schemes) for data elements and org
units. You can set it up simply by adding unique metadata attr
, 05 April 2018 12:14 PM
To: Edward Robinson
Cc: Martin Van Aken ; dhis2-users
Subject: Re: [Dhis2-users] Import/Export data between similar but distinct
systems
Hi Martin,
Yes, basically the Idea would be to extract metadata/data from one instance
(source), do some transformations and load
e we’re not 100% sure when it will be
> complete, but it should be in the next few weeks.
>
> Ed
>
>
>
> *From:* Dhis2-users lists.launchpad.net> *On Behalf Of *Martin Van Aken
> *Sent:* Tuesday, 09 January 2018 8:56 PM
> *To:* dhis2-users
> *Subject:* [Dhis2-users
-users
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 concerne
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,
5 matches
Mail list logo
