University of Oklahoma Calendaring System in CQ5

Melanee Hamilton and Erin Yarbrough
University of Oklahoma

OU Implementation of Day Calendaring System OU was interested in an events calendar for the entire university. They implemented the calendaring system with the initial cq 4 migration, but got a lot of push back from their authors. It was just too difficult for the authors to use.

They spent some time looking for a 3rd party solution.  None of these solutions offered all they needed, so they came back to Day and worked with their developers to come up with The Perfect Calendar.
Their requirements included:

• the ability to share
• use of a consistent workflow
• the ability to push events to calendars and then the other calendars can display these events
• realtime updates
• event approval  - and rejecting - process (for sharing)
• import outside calendar - (sports are on another calendar)
• customizable layout - consistent branding
• submit events to other calendars
• generates ical feed
• easy event authoring - cq4 version was a little difficult for authors to use.

They were the beta customers for this development. Day was able to offer recommendations on requirements. They all wanted to make sure that what they created was based on clendaring standards.

Calendar Features:

• events were the content pieces - within calendar framework
• hope to use reverse replication at some point so that outside cms users can add and edit calendar
• double click on date to edit event on that date
• all events are ical based
• integrate calendars through workflows
• other calendars can subscribe to events - if we know another calendar that shows events you want - you subscribe to that calend
• expand and hide details
• future plans for calendar:
• search for events using tagging
• creating different views - semester?

How will OU roll out their new calendar?

• first to sites using cq
  
• second to people outside cq cms

Next Steps/Plans for the future:

• integrate with search page
• integrate with cq map - click on details of the event and see exactly where the event will be

How did OU achieve campus buy-in?

• maintain events without having a static web page
• use is the same across departments
• nice look to the calendar - branding
• one point to author public facing content - easy
• users are not going to use multiple systems
• homepage shows next 5 events on calendars
• self service access and permissions model