For the Activity Search API, the various date/time fields are all in different formats, with some not including time zone information. Can this be standardized in the next version of the API? For instance (referencing example provided here:
<eventDate>2010-08-15T07:00:00-07:00</eventDate> <~~ includes T
<startDate>2010-08-15</startDate>
<startTime>7:00:00</startTime> <~~ doesn't include time zone
<endDate>2010-08-15</endDate>
<endTime>7:00:00</endTime> <~~ doesn't include time zone
<lastModifiedDate>2010-04-20 17:15:41.23</lastModifiedDate> <~~ doesn't include T, uses space instead
<UpdateDateTime>7/13/2010 7:13:55 PM</UpdateDateTime> <~~ uses slashes instead of dashes and isn't in the same order as the other datetimes
Also, what is the difference between lastModifiedDateTime and UpdateDateTime?
And lastly, my main issue is that it is difficult to get the start datetime and the end datetime easily and have time zone information included as well. Right now, I must parse together endDate and endTime and then determine time zone based on (I'm guessing) the eventDate field. Can this also be streamlined for the next version of the API?
Message edited by Matt 12 years ago
jarredd
–
12 years ago
Hi Matt,
Thanks for bringing this up. I'll check with the API development team to see if we can standardize this in the next version of the API. Please allow some time to investigate and I'll reply to this thread with an update.
Thanks,
Jarred
jarredd
–
12 years ago
Hi Matt,
I have added this to the development queue for review. As we are approaching the launch of the version 2 Activity API, we will need to dig into the requirements for this update. I agree that this should be implemented and will push to get this completed as soon as possible. I will announce via Twitter and within the blog when we make these updates.
For the Activity Search API, the various date/time fields are all in different formats, with some not including time zone information. Can this be standardized in the next version of the API? For instance (referencing example provided here:
<eventDate>2010-08-15T07:00:00-07:00</eventDate>
<~~ includes T<startDate>2010-08-15</startDate>
<startTime>7:00:00</startTime>
<~~ doesn't include time zone<endDate>2010-08-15</endDate>
<endTime>7:00:00</endTime>
<~~ doesn't include time zone<lastModifiedDate>2010-04-20 17:15:41.23</lastModifiedDate>
<~~ doesn't include T, uses space instead<lastModifiedDateTime>2010-08-02 15:15:08.767</lastModifiedDateTime>
<UpdateDateTime>7/13/2010 7:13:55 PM</UpdateDateTime>
<~~ uses slashes instead of dashes and isn't in the same order as the other datetimesAlso, what is the difference between
lastModifiedDateTime
andUpdateDateTime
?And lastly, my main issue is that it is difficult to get the start datetime and the end datetime easily and have time zone information included as well. Right now, I must parse together endDate and endTime and then determine time zone based on (I'm guessing) the eventDate field. Can this also be streamlined for the next version of the API?
Message edited by Matt 12 years ago
jarredd – 12 years ago
Hi Matt,
Thanks for bringing this up. I'll check with the API development team to see if we can standardize this in the next version of the API. Please allow some time to investigate and I'll reply to this thread with an update.
Thanks, Jarred
jarredd – 12 years ago
Hi Matt,
I have added this to the development queue for review. As we are approaching the launch of the version 2 Activity API, we will need to dig into the requirements for this update. I agree that this should be implemented and will push to get this completed as soon as possible. I will announce via Twitter and within the blog when we make these updates.
Best, Jarred