1 / 24

CalEvents@Berkeley Anatomy of an Event Calendar

CalEvents@Berkeley Anatomy of an Event Calendar. Sarah Jones CalAgenda (campus online calendar) Service sarah@socrates.berkeley.edu UCCSC 2004 - 2 August 2004. Agenda. Origin SIMS 290 - Document Engineering class Event Calendar Modeling Team Event calendar model

genica
Download Presentation

CalEvents@Berkeley Anatomy of an Event Calendar

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CalEvents@BerkeleyAnatomy of an Event Calendar • Sarah Jones • CalAgenda (campus online calendar) Service • sarah@socrates.berkeley.edu • UCCSC 2004 - 2 August 2004

  2. Agenda • Origin • SIMS 290 - Document Engineering class • Event Calendar Modeling Team • Event calendar model • User Interface for Event entry form • Now what? • Q & A

  3. Origin of project • Desire to offer ability to subscribe to events to CalAgenda subscribers • Campus calendar (Oracle Calendar) system had only simple event calendars • Current, de facto event calendar using old technology, lacks features • http://www.berkeley.edu/calendar/ • Professor Bob Glushko’s SIMS Document Engineering class - Spring and Summer 2003 needed real campus examples to model

  4. SIMS 290 assignment • Spring 2003 School of Information Management & Systems assignment in SIMS 290-4 Document Engineering • 10 different teams analyzed and modeled 6 different calendars • UC Berkeley Events • College of Letters & Sciences • Haas School of Business • Men’s Basketball • Official Academic Calendar • PDA (Mail taxes on April 15) • Why these event calendars were chosen

  5. Approaches to modeling • Classical modeling • Abstract real world system or environment • Systems analysis • Systems design • Document engineering modeling • Data viewed as document, a collection of information

  6. The modeling process • Why bother to model? • Fresh look at business processes • Don’t just replicate current process • Broad survey of domains

  7. Creating a data matrix • Create an aggregate data matrix by examining elements of 6 event calendars • Determine core and context elements • Core elements- those that are common to all calendars, such as event title • If you change the element, does it change the event? • Context elements - those that are used in specific kinds of calendars, such as score, admission fee, refreshments

  8. Aggregating element data into a matrix • Enter event calendar element names down left column • Enter X for each element contained in a particular calendar Element Calendar 1 Calendar 2 Calendar 3 Element 1 X X X Element 2 X X Element 3 X X Element 4 X

  9. Team 9 model

  10. Team 7 model

  11. Campus events - a closer look • August 2003 - Do broader survey of campus event calendars • Event calendar survey team (7 members): • School of Info Mgmt graduate students • Lawrence Hall of Science technical Web folks • Campus calendar system (CalAgenda) technical folks • What has been done? Standards? • Oracle Calendar • iCalendar, SKiCal, Oasis Universal Business Language (UBL)

  12. Categories of campus calendars • Athletics - Men's Basketball, CalFit • Performances - Cal Performances, Music Department Noon Concerts • Museums - Berkeley Art Museum & Pacific Film Archive, Lawrence Hall of Science • Academic Departments - Math Department, International Area Studies • Administrative Departments - University Health Services, Capital Projects • Centers - Center for Document Engineering, California Biodiversity Center • Schools/Colleges - Letters & Science, Haas School of Business • Student Groups - SUPERB • Libraries - UC Berkeley Library, Bancroft Library • Calendar applications - PDA (handheld personal data assistant), CalAgenda • Aggregate calendar - UCB NewCenter Calendar

  13. A couple of calendars of interest • Men's Basketball (Intercollegiate) • Capital Projects

  14. Common event elements • Event name • Date event being held • Event start time • Event end time • Duration • Location • Repetition

  15. Less common event elements • Ticket required • Admission fee • Refreshments • Score

  16. Event Calendar Model • Again, why bother doing a model? • Assumptions • Special cases • Standards • Work with UBL technical committee members • Use UBL elements in model

  17. Can’t assume • Conferences (nested calendars) - how do you connect the events, especially if you have tracks • Repeating vs recurring events • Exhibits and building hours

  18. Can’t ignore special cases • Refreshments • Event is rescheduled • Permanent exhibit • Holidays

  19. Our event model evolution • Unified Modeling Language (UML) • Relationships • Similar to database modeling • Combined our Team A & Team B Models to produce final model

  20. Final event calendar model

  21. Administrative User Interface • SIMS graduate students used model as basis for developing UI for entering event calendar data • Use cases • Usability testing • Demo

  22. Now what? • Finish requirements • Bring model into agreement with iCalendar • What’s out there • WebEvent - not standards based

  23. Q & A • Questions?

  24. Credits • Modeling • Lawrence Hall of Science - Sara Leavitt, Kathleen Connors • SIMS graduate students - Allison Bloodworth, Carolyn Cracraft • CalAgenda - Jeff McCullough, Mimi Mugler, Sarah Jones • User Interface - Allison Bloodworth, Myra Liu, Nadine Fiebrich, Zhanna Shamis

More Related