1 / 41

Campus Web Steering Committee (CWSC)

Campus Web Steering Committee (CWSC). March 16, 2009 Brett Pollak. Agenda. Action Item: Brett Pollak (10 minutes) Emergency Status Page Promotion: Update emergency link on home page footer based on revised emergency procedure process

rogan-bray
Download Presentation

Campus Web Steering Committee (CWSC)

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. Campus Web Steering Committee (CWSC) March 16, 2009 Brett Pollak

  2. Agenda Action Item: Brett Pollak (10 minutes) Emergency Status Page Promotion: • Update emergency link on home page footer based on revised emergency procedure process • Potential inclusion of link to Emergency Status on other campus sites Informational Item: Brett Pollak & Emily Deere (10 minutes) Exploratory idea to be CMS provider for UC Berkeley: • Request • Approach • Pros and Cons Project updates: Brett Pollak (30 minutes) • Moving to Sites Model in CMS • Mobile optimize Libraries Hours (proof of concept) • Sites moved into CMS • Analytics

  3. Emergency Status Page Promotion: Brett pollak

  4. Emergency Status Promotion ucsd.edu/emergency

  5. Emergency Status Promotion

  6. Emergency Status Promotion

  7. Emergency Status Promotion

  8. Emergency Status Promotion Proposal • Change UCSD home page footer to link to ucsd.edu/emergency. • Remove icon and change link wording to “Emergency Status” • Blink: same change & archive old Emergency page • Add Emergency Status link to footer for • UCSD Umbrella Sites? • Prospective Students, Current Students, Parents & Families, Faculty & Staff, Alumni, Friends & Visitors -- or -- • All sites in the CMS?

  9. Emergency Status Promotion Proposal

  10. Emergency Status Promotion Proposal

  11. Emergency Status Promotion Proposal

  12. Options • Home page only • Home page plus UCSD Audience sites • All sites in the CMS

  13. Exploratory idea to be CMS provider for UC Berkeley: Brett pollak &Emily Deere

  14. CMS & Berkeley • What? • Exploratory idea to leverage our instance of Cascade Server for Berkeley’s Web CMS needs • Who? • IST (Info Systems & Technology) • J.R. Schulden (App Services Director) • Bill Allison (App Services) • Why? • Berkeley wants to centralize web operations for similar reasons to UCSD

  15. What’s in it for them? • Leverages existing environments (and components such as the Google Search Appliance) at UCSD • Reduces their costs associated with purchase and install of hardware for web, app, and database layers; firewall, networking and other data center costs; database licensing • Reduces (or leverages shared) staffing needs for implementation and operations (Data Center, System Administration, DBA, Application Administration) • Leverages UCSD/UCOP agreement and robust infrastructure for business continuity/disaster recovery model • Potentially reduces vendor licensing costs, one-time and/or ongoing (pending assessment of UCSD contract)

  16. What’s in it for us? • $$ • Enables multi-campus leverage in current and future contract negotiations • Increases inter-campus pool of technical subject matter experts providing application and site administration support • Increases campus participation in shared service models, with potential for partnerships with other campuses (UCI, UC Davis, UC Santa Cruz, UCOP) • Enables development of inter-campus pool of technical competency for future expansion of Web Services (mobile web, mashups, widgets, middleware components, etc.)

  17. How would it work

  18. Risks/Considerations • Vendor licensing may not accommodate multi-campus licensing, thus not reducing licensing costs • Likelihood = High • Impact = None (as planned; pending contract negotiations may actually reduce licensing costs) • Can UCSD Infrastructure support Berkeley’s needs? • Likelihood = Med (based on preliminary discussion with UCSD representatives) • Impact = High • Security model may require shared privileges between campus’ administrators, and/or limited privileges to Berkeley application and/or site administrators • Likelihood = Med • Impact = Low-Med (reduce through technical discussion/design re: user/group settings, SSL certifications per campus domain(s), etc.) • Account provisioning & authentication • Likelihood = High • Impact = Med-High (reduce through use of common mechanism such as Shibboleth, or pending technical feasibility for campus unique mechanisms) • Impacts to existing projects

  19. Next steps • Conference call this afternoon to better understand Berkeley’s CMS requirements • Feasibility/Scope document

  20. Project updates: Moving to Sites Model in CMS Mobile optimize Libraries Hours (proof of concept) Sites moved into CMS Analytics Brett pollak

  21. Cascade Server Sites Model • With upgrade from v5 to v6 Cascade Server employs a new model for managing websites Advantages: • Less time to create new sites within the system • More streamlined approach to developing and maintaining content templates • More efficient way of distributing new templates & enhancements across existing CMS websites.

  22. Makeup of a CMS Website

  23. XSLT Layout (Skeleton)

  24. Campus-wide CSS (Skin)

  25. HTML (Clothes)

  26. CMS

  27. Sites Model Project Sites currently are copies with skeleton, skin, and clothes initially derived from a central source but independent branches. “Sites” will centralize the skeleton and skin so existing sites can inherit new features easier “Sites” will significantly reduce the effort for setting up new sites in the CMS. “Sites” will allow for administrator-level access on a site-by-site basis.

  28. Blink Campus-wide Sustainability

  29. Timeline

  30. Project updates: Moving to Sites Model in CMS Mobile optimize Libraries Hours (proof of concept) Sites moved into CMS Analytics Brett pollak

  31. Mobile Optimize Libraries Hours POC • Who? • Libraries ITD, ACT, & CWO to develop a proof of concept in the CMS for maintaining Libraries hours content and optimizing display for Smartphones. • Why? • Determines how well the CMS outputs a mobile optimized template

  32. Mobile Optimize Libraries Hours POC

  33. Mobile Optimize Libraries Hours POC

  34. Project updates: Moving to Sites Model in CMS Mobile optimize Libraries Hours (proof of concept) Sites moved into CMS Analytics Brett pollak

  35. Sites in the CMS

  36. Sites Using the CMS (or in process) • Campus-wide • ucsd.edu, including audience-based websites • Prospective Students • Current Students (TritonLink) • Parents & Families • Alumni • Friends & Visitors • Campus Web Office • Libraries • Sustainability 2.0 • Resources for People With Disabilities • iPhone Application Web site • Blink • Undergraduate Research Portal • UCSD Emeriti Association • UXT • Retirement Association • CREATE •  Colleges • Sixth College • Roosevelt College • International House • Warren College • Revelle College • Departments & Centers • Linguistics Department • Center for Molecular Biology • Political Science Department • Department of History • AIP • CILAS • Women's Center • Ethnic Studies Dept. • Literature Dept. • Philosophy Dept. • Math Dept. • Divisions • Biological Sciences • Physical Sciences  • Social Sciences (?) • Rady (?)

  37. Project updates: Moving to Sites Model in CMS Mobile optimize Libraries Hours (proof of concept) Sites moved into CMS Analytics Brett pollak

  38. UCSD Sites Start of Quarter Start of Quarter Start of Quarter

  39. January Metrics

  40. February Metrics

  41. Home Page Pageviews Jan 1 – March 15 Recent on-campus incidents didn’t increase traffic to home page

More Related