I've investigated and retract that this is a bug. I guess I
misunderstood at first, but reading your report again makes it clear
that you are actually supplying a GML file with coordinates for all
orgunits, including those which already have coordinates.
As you are, in fact, importing coordinates for all of these orgunits,
it's technically not wrong that the lastUpdated is also set to reflect
this. We don't really discern between old vs. new value of metadata when
updating on import.
If you wish to avoid this you can give the importer a GML file which
only contains the orgunits you actually wish to update.
Setting this one to won't fix.
** Changed in: dhis2
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to DHIS.
https://bugs.launchpad.net/bugs/1597724
Title:
Import of GML file update lastupdated date of all objects with co-
ordinates
Status in DHIS:
Invalid
Bug description:
Importing of a GML file updates the "lastupdated" date of all
organisationunit with GIS co-ordinates to the date of the import.
Not sure if this is by design but it creates a problem for facility
registries in that it appears that all organisationunits with co-
ordinates had some field updated every time a GML file is imported
when in fact only some of the objects had updates.
Ideally the import should only update new/real updates and for those
update the GIS co-ordinates instead of overwriting all co-ordinates
and seeing them as updates.
To manage notifications about this bug go to:
https://bugs.launchpad.net/dhis2/+bug/1597724/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp
