iteration3.2

Overview:

• We already implemented our features in iteration3-1 so this week we focused on patching cucumber tests that were incomplete before.
• Also Hongjun worked on refactoring code to handle more cases when parsing the XML feed from events.berkeley.edu rss feed and was merged with the changes from iteration3-1 and we are in the process of merging the refactored code into iteration3-2. One unanticipated challenge that comes with parsing events.berkeley.edu is recurring events. We are considering to use the ice_cube gem to store meta data about recurring events for persistence storage although we still have to figure what additional meta data should be stored in our Event model such that it is possible to query all events recurring or not. One thought is to add the columns is_recurring (boolean) and schedule_yaml (text) and storing the start and end_times of the recurrences. If there is an infinite end time, then set the end time of the Event instance to nil.
  • http://stackoverflow.com/questions/5183630/calendar-recurring-repeating-events-best-storage-method
  • https://www.ruby-toolbox.com/categories/recurring_events
  • http://stackoverflow.com/questions/10148960/recurring-events-in-calendar-rails
  • https://github.com/seejohnrun/ice_cube

git log iteration3-1..iteration3-2
git log iteration3-2..origin/eventsBerkeley-polished
git log iteration3-2..origin/merge-eventsBerkeley-polished