dhis2-devs team mailing list archive

[Lars Helge Øverland <larshelge@xxxxxxxxx>]

You cannot in any case use internal ids for mapping.

** Changed in: dhis2
       Status: New => Invalid

-- 
import/export based on name not ID
https://bugs.launchpad.net/bugs/578621
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to DHIS.

Status in DHIS 2 - District Health Information Software: Invalid

Bug description:
Currently with DHIS2.0.4, when running import/export function for DHIS2 db, and through import-analysis show that identifier for daels, dataset, categoryoptions, indicator, etc. is the NAME, not ID.
It seems messy, for example: a dataset/dael (which already exists in the center db) is renamed in the local db when exported/imported into the center (or upper levels db) it's recognized as a new one for importing.
So, if lacking user's notice/awareness, this "new" element would be added into the destination db but later on when opening the equivalent session of that element type (dael, sataset, ect.) conflicts occur.

Suggestion: unify the management/strategy for import/export identifier, what's it called "updates", "new"?