Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

MW2010: Bill Bostick, Building a Cultural Calendar

A presentation from Museums and the Web 2010.

This mini workshop will focus on the calendar sub-project of the Balboa Park Online Collaborative’s multi-institutional, Drupal Web site deployment. Like most cultural institution Web sites, the sites from BPOC member institutions have a significant emphasis on events – exhibitions, lectures, classes, tours, performances, etc. Commercial calendar products are often not flexible enough to meet the specific needs of the cultural heritage field, forcing many museums to make do with inadequate calendaring systems at great expense. Additionally, the complexities of scheduling events on-line for museums and cultural institutions (e.g. a tour that takes place every other Monday, except for holidays, when it happens on Tuesday) often leads to either inefficient or, on the other end of the spectrum, overly complex calendaring software that non-technical staff are loathe to embrace and technical staff are loathe to support. Finally, in a multi-institutional environment like Balboa Park, there is significant need for a centralized, automated calendar system that will streamline workflows for marketing and publicity staff by simplifying the data entry process and allowing the institutions to both coordinate events with their neighbors and distribute accurate event information to other media outlets and social networks en masse.

  • Be the first to comment

  • Be the first to like this

MW2010: Bill Bostick, Building a Cultural Calendar

  1. 1. Building a Cultural Calendar<br />Balboa Park Online Collaborative<br />San Diego, CA<br />
  2. 2. Balboa Park Online Collaborative<br />About 20 Member Cultural Institutions<br />Size and Resources vary greatly<br />Many have no dedicated technology staff<br />They all have online calendars<br /><br />
  3. 3.
  4. 4. Goals of project<br />Atomic representation of Events<br />Support for complex recurring events<br />Support for instance-specific data<br />Two-way Aggregation of calendar data between sites<br />Eliminate duplication of effort<br />Simple and efficient backend<br />Compatibility with Drupal components<br />
  5. 5. Non-Goals of Project<br />Presentation<br />
  6. 6.
  7. 7. Existing Calendar Solutions<br />Existing Drupal Date Support<br />Alternative CMS Date Support<br />Google Calendar<br />iCal-based solutions (phpCalendar, etc.)<br />
  8. 8. What’s So Hard About Recurring Events?<br />No support for multiple RRULEs<br />No support for combining RRULEs and RDATEs<br />Insufficient Granularity<br />No support for Instance-Specific Data<br />Cumbersome and Complex Backend<br />Recurring Event vs. a Series of Events<br />
  9. 9.
  10. 10.
  11. 11.
  12. 12.
  13. 13.
  14. 14.
  15. 15. Aggregation<br />Two-way aggregation of events<br />Propagate changes from multiple points<br />Provide Custom Feeds as required<br />
  16. 16.
  17. 17.
  18. 18. Drupal Components<br />Extended Date CCK Field<br />Javascript CCK Date Field Widget<br />Instance Node Type and Reference<br />Atom-based Event Aggregator<br />Aggregation Client<br />
  19. 19. Something to Share?<br /><br />
  20. 20. Questions?<br />