Schedules meetings (BETA) - Time expressions?

Brian Pugh
Brian Pugh
Ninth Anniversary Kudos 1 Name Dropper Facilitator 1
in SKY Developer General Discussions

I tried the school api for schedule meetings-time expressions.

Here are a few of the time/date returns:

<!--td {border: 1px solid #ccc;}br {mso-data-placement:same-cell;}-->

value.start_timevalue.end_timevalue.meeting_date
1900-01-01T09:20:00-04:001900-01-01T10:00:00-04:002022-09-06T00:00:00+00:00
1900-01-01T11:00:00-04:001900-01-01T11:39:00-04:002022-09-06T00:00:00+00:00
1900-01-01T11:40:00-04:001900-01-01T12:20:00-04:002022-09-06T00:00:00+00:00
1900-01-01T13:15:00-04:001900-01-01T13:54:00-04:002022-09-06T00:00:00+00:00
1900-01-01T13:55:00-04:001900-01-01T14:35:00-04:002022-09-06T00:00:00+00:00

What type of time expressions are these and is there a google formula to convert them into readable “human” time?

Thank you very much,

Brian

Comments

  • Michael Panagos
    Michael Panagos
    Tenth Anniversary Kudos 2 Name Dropper Facilitator 1

    To answer your question, these are written in the https://en.wikipedia.org/wiki/ISO_8601 format.

    I'm having an issue with the times in this beta endpoint, however. The issue with the start time and end time being returned in these formats is that it doesn't calculate DST properly if the date is 2007 or later. This is because they use 1970:

    "start_time": "1970-01-01T13:00:00Z",
    "end_time": "1970-01-01T14:00:00Z",

    But in the US DST was extended in 2007 so these events now become an hour off if in that extended window. I am going to write support to see if there's something they can do for that.

    I'm hoping that the meeting date can be added to these fields instead of the 1970 date.

  • Brian Pugh
    Brian Pugh
    Ninth Anniversary Kudos 1 Name Dropper Facilitator 1

    @Brian Pugh

    I really appreciate this, Michael. A new world for me.

  • Stephen Boyle
    Stephen Boyle Blackbaud Employee
    Tenth Anniversary Kudos 5 First Reply Name Dropper

    @Michael Panagos
    Hi! As a bit of history, the original intent of these fields was to have separate date and time fields. However, they were all given datetime data type, so the times were missing date info and the date has no time info. That wasn't an issue for the date, but caused DST issues with the time fields.

    We've now updated the time fields to include the date info. A bit redundant but it should clear up the DST oddities as the date portion will now reflect the correct DST rules. This should hit Production in the 3/28 release.

Categories