Campus Web Steering Committee (CWSC)

1. Campus Web Steering Committee (CWSC) January 25, 2009

2. Agenda Items • Alumni Association request to link directly to alumni.ucsd.ed from ucsd.edu home page • Paula Thomas (15 minutes) • UCSD Emergency Response Proposal • Brett Pollak (30 minutes) • Sites migrated to CMS & Notable Projects • Brett Pollak (15 minutes)

3. Alumni Association request to link directly to alumni.ucsd.ed from ucsd.edu home page Paula Thomas

4. Emergency Notification Proposal Brett Pollak

5. Goals • Decrease time between incident and our response • Categorize potential incidents so we have a better idea how to respond • Train cross-functional teams so multiple people can step in

6. 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, Last week’s storms • 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

7. Severity 1 (Low) • Response may contain info on “preventative measures”. • Example: H1N1 Swine Flu, last week’s storms, etc. Treatment: • ucsd.edu/emergency page updated with summary of emergency, results or actions related to campus, supporting info. • Headline link in the News section on the ucsd.edu home page, linking to ucsd.edu/emergency. • Link from Blink, TritonLink, and other audience based sites, as necessary. DRAFT

8. Severity 1 (Low) Process • CES, EPG or EOC recommends to Brett Pollak or Sydney Donahoe campus communication is necessary. • Default assumption is to place communication under ucsd.edu/emergency • If a devoted site is needed, it can be quickly created in the campus-wide CMS • Jeff Gattas & Janet Howard review and approve messaging. • Site is linked from the UCSD home page, Blink, TL and other audience based sites as necessary DRAFT

10. DRAFT

11. DRAFT

12. Severity 2 (Medium) • 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 • Students, faculty, staff, parents would likely access ucsd.edu for further information about evacuation procedures, or other precautions to take based on the incident. Treatment • Default assumption is to place communication under ucsd.edu/emergency • If a devoted site is needed, it can be quickly created in the campus-wide CMS • Jeff Gattas & Janet Howard provide or review and approve messaging. • Rotating graphic area on home page changed to contain only one graphic that directs users to emergency site for more info (also Blink, TL, and other audience sites) • Allows user to click the image to get more information about evacuation procedures, closures, emergency planning, etc. DRAFT

13. DRAFT

14. DRAFT

15. Severity 2 (Medium) Process • EPG or EOC determines course of action and content for web page details and instruction • ucsd.edu/emergency is updated based on messaging delivered from EPG or EOC • Site is linked to from the UCSD home page via graphic in rotating image area, and Blink and TL as necessary. DRAFT

16. Severity 3 (High) • Active on-campus shooter • Large scale on-campus fires, or other high impact incident • Could potentially capture the attention of a state-wide, national, or international audience. DRAFT

17. Severity 3 (High) Treatment • UCSD home page changes to include only info about the emergency • Ensures viewers do not miss info updates • Lightweight: optimized to handle increased Web traffic • ucsd.edu/emergency would point here DRAFT

18. DRAFT

19. Severity 3 (High) Treatment Additional Treatment Option: • Banner strip displays below UCSD header, which includes link back to emergency information DRAFT

20. DRAFT

21. Disaster Recovery Examples: • Power Failures in TPC datacenter • Fire or earthquake disables TPC datacenter Result: • CMS users can log into CMS hosted at UCOP (Berkley) • Limited number of accounts created (CMS not behind SSO) • Daily data feeds to UCOP from TPC • Utility created to switch DNS quickly so content under ucsd.edu is being delivered from UCOP Web server environment.

22. Next Steps • Incorporate feedback from this meeting; meeting with Jeff Gattas on Feb. 1 to get his feedback. • Training for emergency responders scheduled for Feb. 1. • Brett Pollak • Charlotte Klock • Elazar Harel • Erik Strahm • Sydney Donahoe • Allisa Becker • Phillip VanSaun • Janet Howard • Work with ACT to determine level of effort for Emergency Banner if CWSC agrees it should be a priority. • Schedule DR test over weekend • Ongoing reminders about process to emergency responders

23. The Campus CMS:Site Migration Status & Project List

24. Sites launched since Cascade Server deployment in March, 2009

25. In Process

26. Notable CWO Projects • CMS Upgrade: conversion to “Sites”model (first quarter) • Allows for streamlined creation of new sites • Ability to share content types across sites • Phase 2: UCSD Mobile Strategy (first/second quarter) • Onboard new sites in CMS (ongoing) • Academic units • External Relations • Assist with Current Students redesign (first/second quarter)