Metadata API and lastUpdated

Hi,
Can someone either confirm or deny that you can use a ISO 8601 UTC timestamp for the lastUpdated parameter in the metadata API. From the documentation:
http://dhis2.github.io/dhis2-docs/2.21/en/developer/html/dhis2_developer_manual_full.html#d4934e315
it appears that you cannot.

If not, can support for this possibly be added.

I tried with a UTC timestamp and it didn’t seem to work, but I may have messed up the request.

Thanks!

Cheers,
-carl

Hi Carl,

it seems to be working fine.

eg: to query for events updated after 8th Feb 10.20 am UTC

http://localhost/api/events.json?lastUpdated=2016-02-08T10:20:15Z , Z for UTC

···

On Sun, Feb 14, 2016 at 5:20 AM, Carl Leitner litlfred@ibiblio.org wrote:

Hi,
Can someone either confirm or deny that you can use a ISO 8601 UTC timestamp for the lastUpdated parameter in the metadata API. From the documentation:
http://dhis2.github.io/dhis2-docs/2.21/en/developer/html/dhis2_developer_manual_full.html#d4934e315
it appears that you cannot.

If not, can support for this possibly be added.

I tried with a UTC timestamp and it didn’t seem to work, but I may have messed up the request.

Thanks!

Cheers,
-carl


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Regards,
Pamod Amarakoon

Confidentiality Notice: the information contained in this email and any attachments may be legally privileged and confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution, or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachments for any purpose, nor disclose all or any part of the contents to any other person.

Thanks. It seems, at least with api/metadata it is getting everything for that day - that it is ignoring the time. For example on the dhis2 demo server there is an org unit that was updated today at 10:59:17.

false false /eOnrD5vLyri 2016-02-14 NONE

I would expect to see the org unit when I do this
curl -k -u admin:district -H ‘Accept: application/xml’ 'https://apps.dhis2.org/demo/api/metadata?assumeTrue=false&organisationUnits=true&lastUpdated=2016-02-14T10:59:00+0000Z’ | xmllint -format -
but not this
curl -k -u admin:district -H ‘Accept: application/xml’ 'https://apps.dhis2.org/demo/api/metadata?assumeTrue=false&organisationUnits=true&lastUpdated=2016-02-14T11:00:00+0000Z’ | xmllint -format -
However, I am seeing it for both. Any ideas what’s wrong with the query? I also tried the variants with out the +0000, with the same result.

Thanks for helping out!

Cheers,

-carl

···

On Feb 14, 2016, at 7:32 AM, Pamod Amarakoon pamodm@gmail.com wrote:

Hi Carl,

it seems to be working fine.

eg: to query for events updated after 8th Feb 10.20 am UTC

http://localhost/api/events.json?lastUpdated=2016-02-08T10:20:15Z , Z for UTC

On Sun, Feb 14, 2016 at 5:20 AM, Carl Leitner litlfred@ibiblio.org wrote:
Hi,
Can someone either confirm or deny that you can use a ISO 8601 UTC timestamp for the lastUpdated parameter in the metadata API. From the documentation:
http://dhis2.github.io/dhis2-docs/2.21/en/developer/html/dhis2_developer_manual_full.html#d4934e315
it appears that you cannot.

If not, can support for this possibly be added.

I tried with a UTC timestamp and it didn’t seem to work, but I may have messed up the request.

Thanks!

Cheers,
-carl


Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp


Regards,
Pamod Amarakoon

Confidentiality Notice: the information contained in this email and any attachments may be legally privileged and confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution, or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachments for any purpose, nor disclose all or any part of the contents to any other person.

I see the code for parsing lastUpdated on the event controller is not
the same as on the metadata filtered export. Carl, you are right that
currently the format is restricted to the patterns shown in the
manual. It would be trivial to add support for ISO8601 timestamp.
Can you make a blueprint so that it is not forgotten?

···

On 14 February 2016 at 14:14, Carl Leitner <litlfred@ibiblio.org> wrote:

Thanks. It seems, at least with api/metadata it is getting everything for
that day - that it is ignoring the time. For example on the dhis2 demo
server there is an org unit that was updated today at 10:59:17.

<organisationUnit name="Lagos" created="2016-02-14T10:59:17.864+0000"
lastUpdated="2016-02-14T10:59:17.931+0000" shortName="Lagos_1"
uuid="f3bdb327-2f38-465e-92a4-91b7c83c1225" id="eOnrD5vLyri" level="1">
      <externalAccess>false</externalAccess>
      <user name="John Traore" created="2013-04-18T17:15:08.407+0000"
lastUpdated="2016-02-14T12:28:51.104+0000" id="xE7jOejl9FI">
        <externalAccess>false</externalAccess>
      </user>
      <description/>
      <path>/eOnrD5vLyri</path>
      <openingDate>2016-02-14</openingDate>
      <featureType>NONE</featureType>
    </organisationUnit>

I would expect to see the org unit when I do this
curl -k -u admin:district -H 'Accept: application/xml'
'https://apps.dhis2.org/demo/api/metadata?assumeTrue=false&organisationUnits=true&lastUpdated=2016-02-14T10:59:00+0000Z'
> xmllint -format -
but not this
curl -k -u admin:district -H 'Accept: application/xml'
'https://apps.dhis2.org/demo/api/metadata?assumeTrue=false&organisationUnits=true&lastUpdated=2016-02-14T11:00:00+0000Z'
> xmllint -format -
However, I am seeing it for both. Any ideas what’s wrong with the query? I
also tried the variants with out the +0000, with the same result.

Thanks for helping out!

Cheers,
-carl

On Feb 14, 2016, at 7:32 AM, Pamod Amarakoon <pamodm@gmail.com> wrote:

Hi Carl,

it seems to be working fine.

eg: to query for events updated after 8th Feb 10.20 am UTC

http://localhost/api/events.json?lastUpdated=2016-02-08T10:20:15Z
, Z for UTC

On Sun, Feb 14, 2016 at 5:20 AM, Carl Leitner <litlfred@ibiblio.org> wrote:
Hi,
Can someone either confirm or deny that you can use a ISO 8601 UTC timestamp
for the lastUpdated parameter in the metadata API. From the documentation:

http://dhis2.github.io/dhis2-docs/2.21/en/developer/html/dhis2_developer_manual_full.html#d4934e315
it appears that you cannot.

If not, can support for this possibly be added.

I tried with a UTC timestamp and it didn’t seem to work, but I may have
messed up the request.

Thanks!

Cheers,
-carl

_______________________________________________
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp

--
Regards,
Pamod Amarakoon

Confidentiality Notice: the information contained in this email and any
attachments may be legally privileged and confidential. If you are not an
intended recipient, you are hereby notified that any dissemination,
distribution, or copying of this e-mail is strictly prohibited. If you have
received this e-mail in error, please notify the sender and permanently
delete the e-mail and any attachments immediately. You should not retain,
copy or use this e-mail or any attachments for any purpose, nor disclose all
or any part of the contents to any other person.

_______________________________________________
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp

Done:
https://blueprints.launchpad.net/dhis2/+spec/metadata-api-lastupdated-utc

Cheers,

-carl

···

On Feb 14, 2016, at 9:48 AM, Bob Jolliffe bobjolliffe@gmail.com wrote:

I see the code for parsing lastUpdated on the event controller is not
the same as on the metadata filtered export. Carl, you are right that
currently the format is restricted to the patterns shown in the
manual. It would be trivial to add support for ISO8601 timestamp.
Can you make a blueprint so that it is not forgotten?

On 14 February 2016 at 14:14, Carl Leitner litlfred@ibiblio.org wrote:

Thanks. It seems, at least with api/metadata it is getting everything for
that day - that it is ignoring the time. For example on the dhis2 demo
server there is an org unit that was updated today at 10:59:17.


false

false


/eOnrD5vLyri
2016-02-14
NONE

I would expect to see the org unit when I do this
curl -k -u admin:district -H ‘Accept: application/xml’
'https://apps.dhis2.org/demo/api/metadata?assumeTrue=false&organisationUnits=true&lastUpdated=2016-02-14T10:59:00+0000Z’

xmllint -format -
but not this
curl -k -u admin:district -H ‘Accept: application/xml’
'https://apps.dhis2.org/demo/api/metadata?assumeTrue=false&organisationUnits=true&lastUpdated=2016-02-14T11:00:00+0000Z’
xmllint -format -
However, I am seeing it for both. Any ideas what’s wrong with the query? I
also tried the variants with out the +0000, with the same result.

Thanks for helping out!

Cheers,
-carl

On Feb 14, 2016, at 7:32 AM, Pamod Amarakoon pamodm@gmail.com wrote:

Hi Carl,

it seems to be working fine.

eg: to query for events updated after 8th Feb 10.20 am UTC

http://localhost/api/events.json?lastUpdated=2016-02-08T10:20:15Z
, Z for UTC

On Sun, Feb 14, 2016 at 5:20 AM, Carl Leitner litlfred@ibiblio.org wrote:
Hi,
Can someone either confirm or deny that you can use a ISO 8601 UTC timestamp
for the lastUpdated parameter in the metadata API. From the documentation:

http://dhis2.github.io/dhis2-docs/2.21/en/developer/html/dhis2_developer_manual_full.html#d4934e315
it appears that you cannot.

If not, can support for this possibly be added.

I tried with a UTC timestamp and it didn’t seem to work, but I may have
messed up the request.

Thanks!

Cheers,
-carl


Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp


Regards,
Pamod Amarakoon

Confidentiality Notice: the information contained in this email and any
attachments may be legally privileged and confidential. If you are not an
intended recipient, you are hereby notified that any dissemination,
distribution, or copying of this e-mail is strictly prohibited. If you have
received this e-mail in error, please notify the sender and permanently
delete the e-mail and any attachments immediately. You should not retain,
copy or use this e-mail or any attachments for any purpose, nor disclose all
or any part of the contents to any other person.


Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp