Campus Web Steering Committee (CWSC)

1. Campus Web Steering Committee (CWSC) November 17, 2010

2. Agenda Discussion item: • Possible Refresh of Campus Website look and feel Brett Pollak (30 minutes) Information items: • Review Draft Mobile Strategy & Evaluation Process • Review current emergency procedures & new emergency banner • Web Accessibility Brett Pollak (20 minutes) Standing Item: • Sites moved into CMS and current queue. Brett Pollak (10 minutes)

3. Brett Pollak Campus Website refresh?

4. My Goal with this subject • To determine if this group feels it’s worth putting work into “refreshing” the campus website in early 2011.

5. Questions you might have… • How did we get to where we are today? • Why should we change anything? • What is a website design refresh vs. redesign?

6. December, 2007 Launched current design of campus website Collaboration between campus-wide group. Design originally developed by a vendor, PINT. Design pulled in house and iterated through to deployment Home page, together with audience-based pages; along with “pilot websites” launched in the Vignette CMS.

7. March – June, 2008 March, 2008: Campus Web Manager hired Small tweaks, to the Explore/Learn/Apply area, addition of “Academics” section. Initiative to promote the CMS and get more organizations using the system Growing frustration with the CMS by the current users Recruiting new folks to use the system proved difficult

8. June – Sept., 2008 Evaluate a new CMS Functional requirements Researched what other universities were using Compared vendor products against open source products Proof of concept in top 3 CMS’s. Created a scorecard and had users rated each system. Cascade Server was clear cut winner

9. Oct., 2008 – Current Procured and implemented Cascade Server Migrated all sites from Vignette into Cascade Server and deployed in March, 2009 Campus-wide branding templates for sites that want to use the CMS Since March, we’ve migrated 32 more websites into the CMS Over 600 active users update their web content in the CMS

10. Why change the campus site? • Heavy adoption of the CMS, and thus brand consistency across those sites • Web designs have evolved since 2007 • Technology has changed since 2007 • HTML5 & CSS3 • Campus site is our first impression; our face to the world. It should be first class. • Home page averages 28,000 page views per day. • Keep up with other UC’s and Universities

11. Last home page refresh

12. How it could work • Contain the refresh to the campus website • Home page: keep the elements, refresh the look • Explore, Learn, Apply content • Campus Search • People Directory • Iterative, rapid prototyping approach • Begin the project towards the tail end of the TritonLink Redesign project. • What do you think?

13. 2 Year CWO Roadmap Key: Complete In Process Proposed Ongoing 2010 2011 UXT Project Design Requests Migrate Websites to the CMS Blink Operations UXT UI Framework Support Portal Services Transition UCPA Maintenance/Support TritonLink & Current Students Redesign Financial Apps UI TL Phase 1 Giving Website Redesign Mobile framework Apply mobile framework to Student & Other Apps Online Giving UI Online Giving Redesign Phase 1 & 2 Lightweight Event Form Framework Maplink Upgrades (Security)Timekeeping Roles Screens CMS utilities Phase 1 CMS utilities Phase 2 Search Enhancements Calendar Enhancements Enhance CMS Templates Campus Website Refresh CMS Sites Model CMS upgrade Move RMP into Blink

14. Brett Pollak Review Draft Mobile Strategy

15. History • ACT contracted with vendor,TerriblyClever, to launch iPhone app • Relatively low cost & quick time to market benefits • Proven success by vendor with other universities • Support for iPhone, Blackberry and mobile Web browser • ACT builds data feeds to vendor, leveraging their application. • iPhone app launched June '09 • v1.1 with additional features in September '09  • Blackberry app and m.ucsd.edu launched in January '10 • Launched v1.2 with link to Library mobile. Now working on mobile tours.

16. What’s the issue? Vendor bought out by Blackboard so mobile team’s efforts have been redirected Any change or enhancement has to go through the vendor. This includes simply adding a link Want to have platform others on campus can use “Locked in” to technical platform Annual maintenance fee $$ Usage reporting is limited

17. What are the options? • Find another vendor • Not many reputable vendors for this kind of thing • Issues of going through vendor for changes still exist • Develop a framework ourselves • Starting from scratch • Would need to enhance it ourselves to keep it up to date in a fast paced arena • Leverage an existing mobile framework • Non-University open source community for mobile is limited (SproutCore, Sencha) • MIT framework is the most mature • UCLA framework is newer and approaches things differently

18. What we’re doing Mobile Framework Evaluation

19. What are we doing? Reviewed goals with group All tended to agree what our requirements were Evaluated some best of breed candidates Each evaluated one framework Based on evaluation, looking closer at a couple Proof of concept using: XML and RSS datafeed

20. Next steps • Continue to evaluate frameworks • Proof of concept: test UCLA framework using our data (80% built out) • Determine if we can leverage framework code in iPhone & Blackberry apps. • Replace vendor with framework • Document & communicate • Create governance • Create a roadmap for mobilizing student and other applications

21. Mobile Demo

22. Brett Pollak Emergency

23. Emergency Types • Severity 1 (low) • Indirectly affects on-campus activities. • UCSD Community: (Students, faculty, staff, parents, etc.) would possibly access ucsd.edu for further information about precautions to take based on the incident. • Example: H1N1 Flu, Severe storms in the area • Severity 2 (medium) • Some damage or affect to the campus is immediately evident • UCSD Community would very likely access ucsd.edu for further information about possible evacuation procedures, campus closure, or direction. • Non UCSD audiences may also access ucsd.edu for more info • Example: Large magnitude earthquake with the epicenter in the southern California area, a fire approaching campus, etc. • Some damage or affect to the campus (classes closed) may be immediately evident or likely to be evident in the near future • Severity 3 (high) • High impact, on-campus incident • Has been or will be declared an emergency by EOC • Event that could potentially capture media attention of a state-wide, national, or international audience. • Example: On-campus shooter, large on-campus fire DRAFT

24. Emergency Status: to this point

26. Emergency Simulation • October, 19th: Continuity & Emergency Services • Simulated large magnitude earthquake on Rose Canyon fault • Mock incidents were called into EOC and response simulations were enacted • Communication via “staging” version of campus site • Disaster recovery tested in conjunction with the simulation

27. Emergency Banner Demo

28. Accessibility • CSU schools were mandated to comply with Section 508 Guidelines by CA Legislature • UC’s are “encouraged” to adopt accessibility practices by the Regents. • Electronic Accessibility Leadership Team • http://www.ucop.edu/irc/itaccessibility/resources/ • Christine Bagwell and Barry Niman are Chairs (I sit in time to time) • What the CWO does… • We ensure our CMS templates comply with Section 508 Guidelines • Campus Web Developers: speaker on building Accessible Websites • In process of procuring software licenses that can be shared by Campus Web Developers

29. Brett Pollak Show & tell: sites moved into CMS & enhancements

30. Redesigns, New Sites & Webapps Now live… • CREATE (May) • SD-CAB (June) • San Diego Writing Project (June) • Current Students Home Page (June) • Online Giving Redesign (July) • Program for Religion (August) • Chancellor’s 5K (August) • Disability Resources (August) • Philosophy (September) • Libraries (September) • Celebrate50 (September) • Physical Sciences (September) • Office of Graduate Studies (Oct.) • Career Services Center (Nov.) Next up… Social Sciences Giving Math Department Chemistry Department Literature Department Conflict of Interest Ethnic Studies Department Literature Department Psychology Department Parents & Families