Group meetings by time, instead of just date #310
Comments
|
This is a requirement for the city website: |
|
It turns out, in the database, we never kept track of the time of the meetings, only the date. This change is going to require a database schema change and data migration. We'll need to run through all the meetingFiles and get the full datetime information from the Google Calendar Event. |
This adds another level of organization to the meeting data feed. Meetings are now organized by date and event_id. Meetings that are not in Google Calendar will have an event_id of zero. This means if there are multiple meetings on the same day that are not in a calendar, they will still be lumped together. We do not have time information in the database for meetingFiles. However, for meetings that are in Google Calendar, we can display the start time of the event. Ultimately, we need to do a database schema change to change the meetingFiles.date column to be a datetime. Then we'll need to run through all the Google Calendar events and populate the datetime information. Until then, the only place we do not have the time information is on the MeetingFiles/Index controller. That is purely reading from the database. Updates #310
|
The commit gets us mostly there. It covers all cases except for the MeetingFiles/Index route. That page is reading entirely from the database, and we don't have time information there. Ultimately, we need to do a database schema change to make the column a datetime and then write a script to populate the datetime from all the Google Calendars. |
|
This will likely be taken care of if we tackle actually tracking meetings: #363 |
In the data feeds, we group meetings by date. In most cases this is sufficient, however there are a few cases when the same committee meets multiple times in one day. When there are multiple meetings in one day, the data feed does not offer enough information to distinguish the meetings.
The text was updated successfully, but these errors were encountered: