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

Vanya_Seth · 26 August 2016 04:50

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!!

Lars · 24 September 2016 12:28

Hi Vanya,

yes this sounds like a good idea to me. Of course, if the metadata is in fact compatible it is unnecessary to abort, but since we do not have a solid way to define which DHIS 2 versions are metadata compatible I think this could be a good idea. Please go ahead.

best regards,

Lars

···

On Tue, Sep 6, 2016 at 1:39 PM, Suresh Jaydev Kurumeti skurumet@thoughtworks.com wrote:

Where do we stand on this with priority for Implementation 1?

–

On Tue, Aug 30, 2016 at 3:58 PM, Suresh Jaydev Kurumeti skurumet@thoughtworks.com wrote:

Hi Lars, Morten, Let us know your inputs / Priority of this new feature. This would enable us plan our Implementation 1 work.

–
**
Suresh Jaydev Kurumeti
Email
skurumet@thoughtworks.com
Telephone
+91 99018 99344
**

On Fri, Aug 26, 2016 at 10:20 AM, Vanya Seth vanyas@thoughtworks.com wrote:

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!!

–

**
Suresh Jaydev Kurumeti
Email
skurumet@thoughtworks.com
Telephone
+91 99018 99344
**

–

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

Vanya_Seth · 26 September 2016 05:28

Thanks for the information.

Could you also tell about the release timeline for 2.25? If we plan to do this for 2.25 then whats the time frame that we are looking at?

Regards

Vanya

···

On Sat, Sep 24, 2016 at 5:58 PM, Lars Helge Øverland lars@dhis2.org wrote:

Hi Vanya,

yes this sounds like a good idea to me. Of course, if the metadata is in fact compatible it is unnecessary to abort, but since we do not have a solid way to define which DHIS 2 versions are metadata compatible I think this could be a good idea. Please go ahead.

best regards,

Lars

–

On Tue, Sep 6, 2016 at 1:39 PM, Suresh Jaydev Kurumeti skurumet@thoughtworks.com wrote:

Where do we stand on this with priority for Implementation 1?

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

–

On Tue, Aug 30, 2016 at 3:58 PM, Suresh Jaydev Kurumeti skurumet@thoughtworks.com wrote:

Hi Lars, Morten, Let us know your inputs / Priority of this new feature. This would enable us plan our Implementation 1 work.

–
**
Suresh Jaydev Kurumeti
Email
skurumet@thoughtworks.com
Telephone
+91 99018 99344
**

On Fri, Aug 26, 2016 at 10:20 AM, Vanya Seth vanyas@thoughtworks.com wrote:

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!!

–

**
Suresh Jaydev Kurumeti
Email
skurumet@thoughtworks.com
Telephone
+91 99018 99344
**

–

With Regards
ThoughtWorks Technologies

Hyderabad

–Stay Hungry Stay Foolish!!

Lars · 26 September 2016 07:41

Hi Vanya, we are having a code freeze tomorrow so that might be a bit late. Would be great if we can target this for 2.26.

best regards,

Lars

···

On Mon, Sep 26, 2016 at 7:28 AM, Vanya Seth vanyas@thoughtworks.com wrote:

Thanks for the information.

Could you also tell about the release timeline for 2.25? If we plan to do this for 2.25 then whats the time frame that we are looking at?

Regards

Vanya

–

On Sat, Sep 24, 2016 at 5:58 PM, Lars Helge Øverland lars@dhis2.org wrote:

Hi Vanya,

yes this sounds like a good idea to me. Of course, if the metadata is in fact compatible it is unnecessary to abort, but since we do not have a solid way to define which DHIS 2 versions are metadata compatible I think this could be a good idea. Please go ahead.

best regards,

Lars

–
With Regards
ThoughtWorks Technologies

Hyderabad

–Stay Hungry Stay Foolish!!

On Tue, Sep 6, 2016 at 1:39 PM, Suresh Jaydev Kurumeti skurumet@thoughtworks.com wrote:

Where do we stand on this with priority for Implementation 1?

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

–

On Tue, Aug 30, 2016 at 3:58 PM, Suresh Jaydev Kurumeti skurumet@thoughtworks.com wrote:

Hi Lars, Morten, Let us know your inputs / Priority of this new feature. This would enable us plan our Implementation 1 work.

–
**
Suresh Jaydev Kurumeti
Email
skurumet@thoughtworks.com
Telephone
+91 99018 99344
**

On Fri, Aug 26, 2016 at 10:20 AM, Vanya Seth vanyas@thoughtworks.com wrote:

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!!

–

**
Suresh Jaydev Kurumeti
Email
skurumet@thoughtworks.com
Telephone
+91 99018 99344
**

–

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

Vanya_Seth · 26 September 2016 07:47

Hi Lars

Sure. This feature we can target for 2.26. But the other PR’s that we will send today you would consider them for 2.25 ?

Regards

Vanya

···

On Mon, Sep 26, 2016 at 1:11 PM, Lars Helge Øverland lars@dhis2.org wrote:

Hi Vanya, we are having a code freeze tomorrow so that might be a bit late. Would be great if we can target this for 2.26.

best regards,

Lars

–

On Mon, Sep 26, 2016 at 7:28 AM, Vanya Seth vanyas@thoughtworks.com wrote:

Thanks for the information.

Could you also tell about the release timeline for 2.25? If we plan to do this for 2.25 then whats the time frame that we are looking at?

Regards

Vanya

–
Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

On Sat, Sep 24, 2016 at 5:58 PM, Lars Helge Øverland lars@dhis2.org wrote:

Hi Vanya,

yes this sounds like a good idea to me. Of course, if the metadata is in fact compatible it is unnecessary to abort, but since we do not have a solid way to define which DHIS 2 versions are metadata compatible I think this could be a good idea. Please go ahead.

best regards,

Lars

–
With Regards
ThoughtWorks Technologies

Hyderabad

–Stay Hungry Stay Foolish!!

On Tue, Sep 6, 2016 at 1:39 PM, Suresh Jaydev Kurumeti skurumet@thoughtworks.com wrote:

Where do we stand on this with priority for Implementation 1?

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

–

On Tue, Aug 30, 2016 at 3:58 PM, Suresh Jaydev Kurumeti skurumet@thoughtworks.com wrote:

Hi Lars, Morten, Let us know your inputs / Priority of this new feature. This would enable us plan our Implementation 1 work.

–
**
Suresh Jaydev Kurumeti
Email
skurumet@thoughtworks.com
Telephone
+91 99018 99344
**

On Fri, Aug 26, 2016 at 10:20 AM, Vanya Seth vanyas@thoughtworks.com wrote:

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!!

–

**
Suresh Jaydev Kurumeti
Email
skurumet@thoughtworks.com
Telephone
+91 99018 99344
**

–

With Regards
ThoughtWorks Technologies

Hyderabad

–Stay Hungry Stay Foolish!!

Lars · 26 September 2016 07:50

Thanks. Yes we will definitely check it out.

Lars

···

On Mon, Sep 26, 2016 at 9:47 AM, Vanya Seth vanyas@thoughtworks.com wrote:

Hi Lars

Sure. This feature we can target for 2.26. But the other PR’s that we will send today you would consider them for 2.25 ?

Regards

Vanya

–

On Mon, Sep 26, 2016 at 1:11 PM, Lars Helge Øverland lars@dhis2.org wrote:

Hi Vanya, we are having a code freeze tomorrow so that might be a bit late. Would be great if we can target this for 2.26.

best regards,

Lars

–
With Regards
ThoughtWorks Technologies

Hyderabad

–Stay Hungry Stay Foolish!!

On Mon, Sep 26, 2016 at 7:28 AM, Vanya Seth vanyas@thoughtworks.com wrote:

Thanks for the information.

Could you also tell about the release timeline for 2.25? If we plan to do this for 2.25 then whats the time frame that we are looking at?

Regards

Vanya

–
Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

On Sat, Sep 24, 2016 at 5:58 PM, Lars Helge Øverland lars@dhis2.org wrote:

Hi Vanya,

yes this sounds like a good idea to me. Of course, if the metadata is in fact compatible it is unnecessary to abort, but since we do not have a solid way to define which DHIS 2 versions are metadata compatible I think this could be a good idea. Please go ahead.

best regards,

Lars

–
With Regards
ThoughtWorks Technologies

Hyderabad

–Stay Hungry Stay Foolish!!

On Tue, Sep 6, 2016 at 1:39 PM, Suresh Jaydev Kurumeti skurumet@thoughtworks.com wrote:

Where do we stand on this with priority for Implementation 1?

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

–

On Tue, Aug 30, 2016 at 3:58 PM, Suresh Jaydev Kurumeti skurumet@thoughtworks.com wrote:

Hi Lars, Morten, Let us know your inputs / Priority of this new feature. This would enable us plan our Implementation 1 work.

–
**
Suresh Jaydev Kurumeti
Email
skurumet@thoughtworks.com
Telephone
+91 99018 99344
**

On Fri, Aug 26, 2016 at 10:20 AM, Vanya Seth vanyas@thoughtworks.com wrote:

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!!

–

**
Suresh Jaydev Kurumeti
Email
skurumet@thoughtworks.com
Telephone
+91 99018 99344
**

–

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

Vanya_Seth · 26 September 2016 07:51

Perfect. Thanks.

Regards

Vanya

···

On Mon, Sep 26, 2016 at 1:20 PM, Lars Helge Øverland lars@dhis2.org wrote:

Thanks. Yes we will definitely check it out.

Lars

–

On Mon, Sep 26, 2016 at 9:47 AM, Vanya Seth vanyas@thoughtworks.com wrote:

Hi Lars

Sure. This feature we can target for 2.26. But the other PR’s that we will send today you would consider them for 2.25 ?

Regards

Vanya

–
Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

On Mon, Sep 26, 2016 at 1:11 PM, Lars Helge Øverland lars@dhis2.org wrote:

Hi Vanya, we are having a code freeze tomorrow so that might be a bit late. Would be great if we can target this for 2.26.

best regards,

Lars

–
With Regards
ThoughtWorks Technologies

Hyderabad

–Stay Hungry Stay Foolish!!

On Mon, Sep 26, 2016 at 7:28 AM, Vanya Seth vanyas@thoughtworks.com wrote:

Thanks for the information.

Could you also tell about the release timeline for 2.25? If we plan to do this for 2.25 then whats the time frame that we are looking at?

Regards

Vanya

–
Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

On Sat, Sep 24, 2016 at 5:58 PM, Lars Helge Øverland lars@dhis2.org wrote:

Hi Vanya,

yes this sounds like a good idea to me. Of course, if the metadata is in fact compatible it is unnecessary to abort, but since we do not have a solid way to define which DHIS 2 versions are metadata compatible I think this could be a good idea. Please go ahead.

best regards,

Lars

–
With Regards
ThoughtWorks Technologies

Hyderabad

–Stay Hungry Stay Foolish!!

On Tue, Sep 6, 2016 at 1:39 PM, Suresh Jaydev Kurumeti skurumet@thoughtworks.com wrote:

Where do we stand on this with priority for Implementation 1?

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

lars@dhis2.org

http://www.dhis2.org

–

On Tue, Aug 30, 2016 at 3:58 PM, Suresh Jaydev Kurumeti skurumet@thoughtworks.com wrote:

Hi Lars, Morten, Let us know your inputs / Priority of this new feature. This would enable us plan our Implementation 1 work.

–
**
Suresh Jaydev Kurumeti
Email
skurumet@thoughtworks.com
Telephone
+91 99018 99344
**

On Fri, Aug 26, 2016 at 10:20 AM, Vanya Seth vanyas@thoughtworks.com wrote:

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!!

–

**
Suresh Jaydev Kurumeti
Email
skurumet@thoughtworks.com
Telephone
+91 99018 99344
**

–

With Regards
ThoughtWorks Technologies

Hyderabad

–Stay Hungry Stay Foolish!!