dhis2-devs team mailing list archive
-
dhis2-devs team
-
Mailing list archive
-
Message #50647
Re: modifying the UID of default
Hi,
South Africa is using a National Data Dictionary (DHIS2-based) to "control"
most meta-data, which means we have standardised uids and codes for
- orgunits
- data elements
- indicators
- validation rules
- categories/options/combos
etc.
Makes life a lot easier when you have many separate DHIS2 instances.
This is now increasingly also coming up as an international / global
challenge - since DHIS2 does not have any kind of import matching mechanism
where the incoming uid/code/name can be matched to internal uid/code/name
(if different), you end up with a lot of uid fiddling. The need to be able
to export program indicator data as aggregate values to other systems
exacerbate this challenge.
Regards
Calle
On 6 February 2018 at 11:06, Ramón José Jiménez Pomareta <dhis2@xxxxxxxxxxx>
wrote:
> Hello,
>
> We are thinking about harmonize all *defaults *of our 5 DHIS2 platforms
> (Particularly, to set to each *default *element the same ID throughout
> all the databases (4 different IDs in total, no only 1 of course), and to
> change the UIDs references in all the DB). Do you think that can be useful
> to avoid import/export issues we currently have? Or the new update on 28
> about this topic solves this kind of issues?
>
> I am thinking about the *defaults *of:
> categoryOptions
> categoryOptionsCombos
> categoryCombos
> categories
>
> Thank you so much !
>
> Ramón José JIMÉNEZ POMARETA
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help : https://help.launchpad.net/ListHelp
>
>
--
*******************************************
Calle Hedberg
46D Alma Road, 7700 Rosebank, SOUTH AFRICA
Tel/fax (home): +27-21-685-6472
Cell: +27-82-853-5352
Iridium SatPhone: +8816-315-19119
Email: calle.hedberg@xxxxxxxxx
Skype: calle_hedberg
*******************************************
Follow ups
References