You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Request by @viengthong2015 from the Center for Health Statistics and Information, Laos
As a Registry Administrator, I want to be able to synchronize only the Geo-Objects that have changed since the last synchronization. Currently, GeoPrism Registry synchronizes all Geo-Objects of a given type as specified in the DHIS2 synchronization configuration. This will make it easier to identify which organization units have been updated by GeoPrism Registry based on the update date.
Problems this relates to
External system synchronization
Proposed solution
Whenever running a synchronization with an external system, GeoPrism Registry checks which changes were synchronized in a previous run, and compares all the Geo-Objects and their attributes about to be synchronized. It then generates a 'changeset' to be synchronized.
Considered alternatives
Option to synchronize specific Geo-Objects by specifying their codes.
Additional context
None
The text was updated successfully, but these errors were encountered:
This could potentially be implemented by having GeoPrism Registry first checking if the attributes of the corresponding organization unit are the same as the Geo-Object, and if there is any difference, only then updating the organization unit.
User stories
Request by @viengthong2015 from the Center for Health Statistics and Information, Laos
As a Registry Administrator, I want to be able to synchronize only the Geo-Objects that have changed since the last synchronization. Currently, GeoPrism Registry synchronizes all Geo-Objects of a given type as specified in the DHIS2 synchronization configuration. This will make it easier to identify which organization units have been updated by GeoPrism Registry based on the update date.
Problems this relates to
External system synchronization
Proposed solution
Whenever running a synchronization with an external system, GeoPrism Registry checks which changes were synchronized in a previous run, and compares all the Geo-Objects and their attributes about to be synchronized. It then generates a 'changeset' to be synchronized.
Considered alternatives
Option to synchronize specific Geo-Objects by specifying their codes.
Additional context
None
The text was updated successfully, but these errors were encountered: