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
yab...@gmail.com>
Sent: Thursday, 05 April 2018 12:14 PM
To: Edward Robinson <erobin...@projectbalance.com>
Cc: Martin Van Aken <mar...@joyouscoding.com>; dhis2-users
<dhis2-users@lists.launchpad.net>
Subject: Re: [Dhis2-users] Import/Export data between similar but distinct
8:56 PM
> *To:* dhis2-users <dhis2-users@lists.launchpad.net>
> *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
> system
Behalf Of Martin Van Aken
Sent: Tuesday, 09 January 2018 8:56 PM
To: dhis2-users <dhis2-users@lists.launchpad.net>
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 sys
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
