Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Synchronize with DHIS2 only the Geo-Objects that have changed since the last synchronization #901

Open
rfromthecastle opened this issue May 4, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@rfromthecastle
Copy link

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

@rfromthecastle rfromthecastle added the enhancement New feature or request label May 4, 2023
@rfromthecastle
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: No status
Development

No branches or pull requests

1 participant