think about how you would handle changes to the data scripts rely on

[kapil1garg]

For example, sometimes SIG meetings or office hours are moved. might it be useful to have an easy way to update the data representation?

[kapil1garg]

as a general note, always assume the data is not correct, so any scripts that execute on the data should really be suggestions

[kapil1garg]

one way to support this is to change the underlying data fetch model. right now, the representations of the data are "static" in a sense where, for example, we know when a SIG will be (e.g., Wednesdays from 12:00 - 13:00) but the next instance of the venue is computed at query time.

Another model could be having the API compute the upcoming venues ahead of time and storing those. Then, a user could go in an edit when those occur if, for example, a SIG meeting or Office Horus had to be moved for any reason. This way the data stays up-to-date and enables scripts to trigger at the appropriate time.