-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Meeting Tracking #363
Comments
Liaison needs to be notified periodically of status of boardmembers vis-s-vis remote meeting participation. Need to clearly flag that a member has done too many remote meetings and has to attend in person or cannot vote. |
Google Calendar API has recommended way of keeping event information in sync. |
Create individual meeting records by reading times from Google Calendar events. If there is no event for, the use the regularly scheduled time for each committee. Updates #363
Now that we have a table of meetings, the meeting information is stored in Meetings, not in the MeetingFiles table. Updates #363
Update the database meetings with information from Google Calendars using a CRON. The plan is hourly so far. Updates #363
We can probably set up push notifications from Google for calendar events. https://developers.google.com/calendar/api/guides/push |
This lets Committees sync calendar events, rather than needing to request a full calendar's worth of events. This also sets the stage for registering a watch on a calendar so we can receive push notifications when something on a calendar changes. Updates #363
We still need to pin down what should be done with OnBoard meetings when someone deletes a Google Calendar event. |
This lets Committees sync calendar events, rather than needing to request a full calendar's worth of events. This also sets the stage for registering a watch on a calendar so we can receive push notifications when something on a calendar changes. Updates #363
This lets Committees sync calendar events, rather than needing to request a full calendar's worth of events. This also sets the stage for registering a watch on a calendar so we can receive push notifications when something on a calendar changes. Updates #363
So far, OnBoard has never tracked meetings themselves; instead, we've relied on the Google Calendar to be the official meeting. This has limited us and caused some unexpected problems.
For instance, the meeting files sometimes happen to have the same date as the event in the Google Calendar, but not always. The Google Calendar Event can be changed, but no one goes back in and updates the dates on the meeting files, so they're no longer correlated.
We also want to start keeping track of meeting attendance, but do not have a place in the OnBoard database to associate with the meeting.
OnBoard likely needs meetings to be represented in the database. We'll need to figure out how we want to keep the database information in sync with what's in Google Calendar.
The text was updated successfully, but these errors were encountered: