October 2009 Archives

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
  

Notes from Day Ignite Conference, 2009

Chris Hanson
University of Phoenix

Community of over 1 million faculty, staff, students
400,000 students

Aptimus does marketing for U of Phoenix

Phoenix.edu

2009 Phoenix on CQ5 platform

Phoenix Objective

• authoritative destination for U Phoenix
  
• site transparent, informational, accessible
• engaging
• highly-engaged community site
• thought leadership
• scalable

Challenges

• org
• tech - myriad repositories and legacy systems
  
• process

Choosing CQ5

• integrate, not replace other systems
• core functionality for non tech users

CQ5.1 Released in April - rewrite of existing site with a new design

• 15 templates
• 50 components
• 10,000 pages
• scalable, redesigned and social

CQ5.2 June, 2009

• transition from custom DAM to out of box DAM
• Plans for social collaboration

Phoenix .edu programs and courses

• released in Sept.
• built a web service for ocyrus so everything can be managed through cq

Meritus (canadian Phoenix)

• leveraged effort from Phoenix.edu
• released in Sept

Next Steps

• implementing workflows
• next generation phoenix.edu

eCampus

• student and faculty portal

Branding and Marketing Guidelines

• DAM 
• storing all assets in DAM - marketing, advertising
  

Keynote Competing on the new web - agility matters. Kevin Cochrane - CEO Customer conversations and feedback to drive further development Help IT be agile to accelerate the needs of the business. Davis Neuscheler - CTO What's coming in CQ5.3? Focus on 4 key areas - the cq5 stakeholders: site owners suthors systems developers

Top 10 features:

1. revamped docs.day.com 
• written in day cms
• all documentation is indexed in google
• every page has collaboration features
2. Subtle improvements

• revised welcome screen
• increased usability - small things that make system more efficient
  

3.  DAM stepped up

• better use case delivered with geometrixx (sample site)
  
• thumbnails in user interface
• using cooliris -DAM integration

4. Calendar integration

• to outlook or ical

5. In-context editing (in-line editing)

• double click on text and can edit inline - so you don't have the pop up word-like text box
• the text area displays as it will on the actual web page
• You can even edit images that are text

6. clickstream cloud

• assembles tags of the pages your user visits.
• clickstream cloud has a lot of info integrated into it
• segment the groups that can have targeted campaigns
• you can visualize the current user's profile
• just by moving mouse, personalized info can change - lots of options for personalization
• segment editor - with logical ors and ands statements - to target users
  

7. Traditional marketing =Highest Paid Person's Opinion - with cq5.3 you can let your prospect decide

• 3 different banners - multivariate testing component
• you can rotate the banners and you can tell which works best via click throughs

8.  Performance - "the performance dialog"

• bridging the gap between developers and end users
• startup time
• performance timing component into the system
• url to performance graph

9. Developing with CQ5

• crxde replaces cqde
• ability to check out code from svn repository directly into your crxde development
• build and deploy osgi bundle
  
• commit changes back to code versioning system - with a click

10. Develop now

• crxde lite - all developer tasks are built in here.

11. Legacy or HTML Design

• you want to translate that into CQ
• site importer

12. Share your package

• package share -allows you to upload and share packages between Day, partners, third party apps, customers

13. Hardware

• Cloud computing - hardware in the cloud
• CRX CQ5 used cloud for trial, test and dev env
• all of our production servers are hosted in the cloud
• cloud manager - to test, for QA
• hardware is provisioned and configured in less than 5 minutes without any tech know how
• unlimited managed diskspace that are available
• storm traffic aware - you can just scale up and scale down quickly
• pay by hour of useage - no up-front or fixed costs.

The Cloud
Open Source
Web Development

JCR 2.0 released on September 25, 2009

JCR 2.1 release planned for early 2010

Q & A

What is the upgrade path/plan for CQ5.3?
The plan is for this to be a package that we can download. Much easier upgrade process. Hopefully more like a hotfix.

Will custom components migrate properly to CQ 5.3?
Hopefully yes.

On Wednesday, October 7, I attended the OCLC Members Meeting in Washington DC. The meeting was an annual gathering of OCLC members in the Washington DC area, and Amy Deuink and I joined colleagues from George Washington, George Mason, American University and other Washington area institutions for an update on some of the recent changes in OCLC and a preview of some of their upcoming web scale services.

Pamela Bailey, Executive Director for OCLC US Service Center welcomed the group and gave an update on the changes in OCLC. She emphasized the improved support and training and highlighted the new Consultative Services Group. She previewed the the new training portal.

Irene Hoffman spoke briefly on the changes in the governance of OCLC - more regional councils, feeding into a global council and on to the board of trustees.

The day's keynote speaker was Michael Edson, Director Web and New Media Strategy  at the Smithsonian Institution. His talk was excellent and extremely relevant on the Smithsonian's strategic plan and how that relates to their presence on the web.

• focusing on work that really matters
• the importance of catalyzing innovation and discovery outside the institution
• the changing learning model and how to make that work for the benefit of all.
  

He walked us through the steps his group took for their planning of the soon-to-be Smithsonian Commons - a quick and transparent process, documented on their wiki.  

Chris Martire, WorldCat Services, followed with two speakers: Kari Schmidt, Electronic Resources Librarian and Head of the Electronic Resources Management Unit at American University Library, and Oleg Kreymer, Systems Librarian for Thomas J. Watson Library of The Metropolitan Museum of Art. Oleg demonstrated their use of WorldCat QuickStart (http://libmma.worldcat.org/) and its configuration settings. Kari presented AU's work with WCL (http://americanuniversity.worldcat.org/), which they ran in test over the summer and are currently rolling out for student use in the fall semester. The primary difference between WCL and the quick start seems to be the ability to customize the look of the WCL interface, as well as it's consortial support.

Some of the issues Kari pointed out from AU's implementation: 
-    must have oclc number in catalog
-    interface options - branding, when to show library services, location codes, etc
-    released trial on web site asking for user feedback
-    main goal was to get buy in from staff - had oclc rep come in to do presentation
-    "find more logo" - developed by in-house graphic designer
-    challenges in consortial set up

After lunch and a discussion/roundtable activity, Matt Goldner, Product & Technology Advocate at OCLC, talked about Web scale and progress on OCLC's new Web-scale management services. Matt talked about the roll out schedule and alpha and beta testing plans. OCLC's plan for their web scale services is very ambitious. It will be interesting to see how things develop.
 
It was enlightening to see what is happening at OCLC, as I'm really only familiar with the WCL services. The most valuable take away from the meeting however, came from discussions with developers and system librarians from other institutions. It's always helpful to hear about where they are in the discovery layer process and the vision they have for their institutions.