Happenings

Completed Event Scraper. Added Styling for main application index page, as well as venue/event show pages. Modified Event/EventDates/Venues controllers, so edit/new/delete actions can only be executed by superadmin user. Modified venue model, to fix issues with validation of phone-number. Added more template logic to erb templates for all modules. Added Config for test environment, so devise doesn't fail. Edited time-formatting in en.yml. Set global time zone to Chicago/Central in application config. Refactored data scraper, to become more reuseable. Added Rake task to scrape event information and apply it to models. Added initial spec files for scrapers.

Much more complete. Still need to add calendar view to front page, and fix styling of venues view(s).
I created this relationship model to have m2m relationships between the venue and it's events. I realize now that the name of this model is faulty since what it actually does is tie an event to many event_dates. Originally I had this model with a belongs_to :venue as opposed to the :event, I changed the relationship, and forgot to rename the model. My reasoning for removing venue, is that since an event already belongs to a venue, if I needed to grab the venue for an event, and show all of the dates, i could reference event.venue instead of venue.event and event dates in which case the relationship here didn't make any sense (venue -> event_date). I couldn't figure out how to write this model so that the reference here would be through event_date.event(id) -> venue; the chain of event_date.event.venue seemed like a huge performance hit on queries.