Hello,
We
are using DHIS2 2.13 as the backend system for Kolkata Medical Emergency System. The concept note of the project can be found here: http://www.missionarogya.org/p/kmes.html. The online portal is using the web-apis
The datavaluesets web-api calls are returning the lastupdated timestamp for the dataelement. But it returns it as a date instead of a timestamp as following: timestamp=“2013-10-16”
Because, in first instance, it does’t seems like a bug, rather it can be treat as new
enhancement in up comming release of DHIS 2.
Regards,
Brajesh Murari
···
A fool can become a genius when he understands he is a fool. But; A genius can become a fool when he understands he is a genius.
----------------------------------------------------------------------------------------------------------------------------------Dr. Abdul Kalam-----------
On Monday, 18 November 2013 5:58 PM, Rajib Sengupta rajibs123@yahoo.com wrote:
Hello,
We
are using DHIS2 2.13 as the backend system for Kolkata Medical Emergency System. The concept note of the project can be found here: http://www.missionarogya.org/p/kmes.html. The online portal is using the web-apis
The datavaluesets web-api calls are returning the lastupdated timestamp for the dataelement. But it returns it as a date instead of a timestamp as following: timestamp=“2013-10-16”
Hello,
We are using DHIS2 2.13 as the backend system for Kolkata Medical Emergency System. The concept note of the project can be found here: http://www.missionarogya.org/p/kmes.html. The online portal is using the web-apis
The datavaluesets web-api calls are returning the lastupdated timestamp for the dataelement. But it returns it as a date instead of a timestamp as following: timestamp=“2013-10-16”
So what do we want here, a full timestamp as in numbers, or a full ISO 8601 string? We have had it likes this for several releases now, and it has the potential to break external users.
I’m not too happy with the name “timestamp”, but I guess that’s minor…
···
–
Morten
On Tue, Nov 19, 2013 at 12:08 PM, Saptarshi Purkayastha sunbiz@gmail.com wrote:
Hello,
We are using DHIS2 2.13 as the backend system for Kolkata Medical Emergency System. The concept note of the project can be found here: http://www.missionarogya.org/p/kmes.html. The online portal is using the web-apis
The datavaluesets web-api calls are returning the lastupdated timestamp for the dataelement. But it returns it as a date instead of a timestamp as following: timestamp=“2013-10-16”
I feel it would be good as a full ISO 8601 string.
2013-11-19T14:01:54 with or without the timezone.
Surprisingly, in the call that I pasted in my last email, for 3 datavalue there is no timestamp attribute.
Also the link which Knut sent doesn't have timestamp attribute. It will be good if they are consistent and with timestamp.
I like the lastupdated name instead of timestamp. This also allows to follow-up if the values have been changed or not since the last time they were read.
Also to be consistent this field should be populated for all the dataValue- here is one example which doesn’t has the timestamp
Thanks for prompt action
Rajib
···
On Tuesday, November 19, 2013 5:13 PM, Saptarshi Purkayastha sunbiz@gmail.com wrote:
I feel it would be good as a full ISO 8601 string.
2013-11-19T14:01:54 with or without the timezone.
Surprisingly, in the call that I pasted in my last email, for 3 datavalue there is no timestamp attribute.
Also the link which Knut sent doesn’t have timestamp attribute. It will be good if they are consistent and with timestamp.
I like the lastupdated name instead of timestamp. This also allows to follow-up if the values have been changed or not since the last time they were read.
So what do we want here, a full timestamp as in numbers, or a full ISO 8601 string? We have had it likes this for several releases now, and it has the potential to break external users.
I’m not too happy with the name “timestamp”, but I guess that’s minor…
–
Morten
On Tue, Nov 19, 2013 at 12:08 PM, Saptarshi Purkayastha sunbiz@gmail.com wrote:
Hello,
We
are using DHIS2 2.13 as the backend system for Kolkata Medical Emergency System. The concept note of the project can be found here: http://www.missionarogya.org/p/kmes.html. The online portal is using the web-apis
The datavaluesets web-api calls are returning the lastupdated timestamp for the dataelement. But it returns it as a date instead of a timestamp as following: timestamp=“2013-10-16”
Please let me know if this issue is identified to be fixed in the core DHIS2 and if yes, whether I need to do anything else (like report a bug etc. in a issue tracking system), so that I can follow the progress of this issue (such as, if anyone is assigned to this, any tentative timeline). Based on the timeline, we need to decide if we need to move forward with our own fix or wait for the core DHIS2 fix .
Thanks,
Rajib
···
On Wednesday, November 20, 2013 1:03 AM, Rajib Sengupta rajibs123@yahoo.com wrote:
As Saptarshi mentioned it will be good to have the timestamp as full ISO 8601 string for the web api calls for “Reading Large bulks of data value”.
Also to be consistent this field should be populated for all the dataValue- here is one example which doesn’t has the timestamp
Thanks for prompt
action
Rajib
On Tuesday, November 19, 2013 5:13 PM, Saptarshi Purkayastha sunbiz@gmail.com wrote:
I feel it would be good as a full ISO 8601 string.
2013-11-19T14:01:54 with or without the timezone.
Surprisingly, in the call that I pasted in my last email, for 3 datavalue there is no timestamp attribute.
Also the link which Knut sent doesn’t have timestamp attribute. It will be good if they are consistent and with timestamp.
I like the lastupdated name instead of timestamp. This also allows to follow-up if the values have been changed or not since the last time they were read.
So what do we want here, a full timestamp as in numbers, or a full ISO 8601 string? We have had it likes this for several releases now, and it has the potential to break external users.
I’m not too happy with the name “timestamp”, but I guess that’s minor…
–
Morten
On Tue, Nov 19, 2013 at 12:08 PM, Saptarshi Purkayastha sunbiz@gmail.com wrote:
Hello,
We
are using DHIS2 2.13 as the backend system for Kolkata Medical Emergency System. The concept note of the project can be found here: http://www.missionarogya.org/p/kmes.html. The online portal is using the web-apis
The datavaluesets web-api calls are returning the lastupdated timestamp for the dataelement. But it returns it as a date instead of a timestamp as following: timestamp=“2013-10-16”
For the record I do also agree with you and Saptarshi that it should be a timestamp string. Following the late Jon Postel’s principle we could consider accepting either a timestamp or date (and cast accordingly) but always produce a timestamp. (Note we must be effectively downcasting anyway as the underlying sql field is a timestamp). That might mitigate some of the potential external breakages Morten is predicting. At least half of them and that maybe the biggest half.
Regarding it not always being populated that is probably a characteristic of the demo data. In normal use the datavalues should always be timestamped though it could and certainly does happen that people have brought them in to the database directly without it. Of course that is easily prevented with a schema constraint, but that really does have the potential to break some legacy databases so people might be reluctant to do it. You could of course enforce the constraint on your own database to prevent such problems (not a bad idea in my view).
Please let me know if this issue is identified to be fixed in the core DHIS2 and if yes, whether I need to do anything else (like report a bug etc. in a issue tracking system), so that I can follow the progress of this issue (such as, if anyone is assigned to this, any tentative timeline). Based on the timeline, we need to decide if we need to move forward with our own fix or wait for the core DHIS2 fix .
Thanks,
Rajib
On Wednesday, November 20, 2013 1:03 AM, Rajib Sengupta rajibs123@yahoo.com wrote:
As Saptarshi mentioned it will be good to have the timestamp as full ISO 8601 string for the web api calls for “Reading Large bulks of data value”.
Also to be consistent this field should be populated for all the dataValue- here is one example which doesn’t has the timestamp
Thanks for prompt action
Rajib
On Tuesday, November 19, 2013 5:13 PM, Saptarshi Purkayastha sunbiz@gmail.com wrote:
I feel it would be good as a full ISO 8601 string.
2013-11-19T14:01:54 with or without the timezone.
Surprisingly, in the call that I pasted in my last email, for 3 datavalue there is no timestamp attribute.
Also the link which Knut sent doesn’t have timestamp attribute. It will be good if they are consistent and with timestamp.
I like the lastupdated name instead of timestamp. This also allows to follow-up if the values have been changed or not since the last time they were read.
So what do we want here, a full timestamp as in numbers, or a full ISO 8601 string? We have had it likes this for several releases now, and it has the potential to break external users.
I’m not too happy with the name “timestamp”, but I guess that’s minor…
–
Morten
On Tue, Nov 19, 2013 at 12:08 PM, Saptarshi Purkayastha sunbiz@gmail.com wrote:
Hello,
We are using DHIS2 2.13 as the backend system for Kolkata Medical Emergency System. The concept note of the project can be found here: http://www.missionarogya.org/p/kmes.html. The online portal is using the web-apis
The datavaluesets web-api calls are returning the lastupdated timestamp for the dataelement. But it returns it as a date instead of a timestamp as following: timestamp=“2013-10-16”