dhis2-devs team mailing list archive

Thread
Date

Inputs for new feature: Stopping sync on DHIS version difference between Central and field instance

To: Lars Helge Øverland <lars@xxxxxxxxx>, Morten Olav Hansen <morten@xxxxxxxxx>, Theo Krommydakis <theo.krommydakis@xxxxxxxxxxxxxx>, Claes-Philip Staiger <claes-philip@xxxxxxxxxx>, DHIS 2 Developers list <dhis2-devs@xxxxxxxxxxxxxxxxxxx>, TWOCA <twoca@xxxxxxxxxxxxxxxx>
From: Vanya Seth <vanyas@xxxxxxxxxxxxxxxx>
Date: Fri, 26 Aug 2016 10:20:54 +0530

Hello  Lars and Morten

We are considering adding another feature to the metadata sync and
versioning.

The idea is to stop sync if the Remote server (Central instance) and the
field instance are on different DHIS2 versions. This is important as
metadata created on one version of DHIS2 might not be compatible with
another version of DHIS2. This also ensures that instances tied up in this
ecosystem remain on the same DHIS2 version.

We would like to make this change from the following standpoint:

- Synchronization API   /api/metadata/sync  : spitting out relevant http
status code and message.

- Metadata synchronization task: The task will send out an email
notification to the admin telling the reason of abort of sync.

Please let us know how you feel about this feature (read restriction :) ).

We will be happy to pick it up as you give us a good to go!

-- 
With Regards
Vanya
ThoughtWorks Technologies
Hyderabad

--Stay Hungry Stay Foolish!!