1 / 32

Campus Web Steering Committee (CWSC)

Campus Web Steering Committee (CWSC). September 30, 2010. Agenda. New CWO Structure Brett Pollak & Emily Deere (10 minutes) TritonLink & Current Students Roadmap: Beth Surrell & Brett Pollak (10 minutes) Review Draft Mobile Strategy Brett Pollak (20 minutes)

ivanbritt
Télécharger la présentation

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) September 30, 2010

  2. Agenda New CWO Structure Brett Pollak & Emily Deere (10 minutes) TritonLink & Current Students Roadmap: Beth Surrell & Brett Pollak (10 minutes) Review Draft Mobile Strategy Brett Pollak (20 minutes) Show & Tell: New & Redesigned Websites & Applications Brett Pollak (20 minutes) Review emergency procedures (if there is time) Brett Pollak

  3. Emily Deere & Brett Pollak New CWO Structure

  4. Campus Web Office Mission The purpose of the Campus Web Office is to provide tools and services that integrate UC San Diego Web content so campus information is more accessible to end users. Vision The CWO accomplishes this through… • Offering a centralized content management system • Templates that reflect campus branding for websites and web applications • Services & training to help UCSD departments and organizations get the most out of these tools. • Mobile development

  5. User Experience Technologies (UXT) * Student Employees

  6. CWO Project Initiation

  7. Current Projects • Online event form registration framework • Mobile framework • CMS upgrade to version 6.7.2 • Enhance Campus-wide CMS Templates • RMP websites into Blink • UI Design for new SSO • Identify & train Blink content owners in CMS • Over 60 people trained since June • Blink now relatively self sustaining • Migrate websites to CMS • TritonLink redesign Phase 2 • Giving website redesign • Online Giving redesign

  8. 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 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

  9. Beth Surrell & Brett Pollak TritonLink & Current students redesign

  10. Current Students & TritonLink Content: • Migrate Current Students content to new campus-wide templates • Remove TL branding from content. Branding would only be on Current Students homepage. • Anticipate this may reduce concern of campus units that feel their content competes with TL branding Applications: • Update TritonLink tools to use latest version of the application decorator • The application portal (currently MyTritonLink tab)  requiring login will be enhanced

  11. Brett Pollak Review Draft Mobile Strategy

  12. Current State Currently use a vendor for apps and m.ucsd.edu

  13. Statistics Since September, ‘09 • Over 16,000 downloads of the iPod and Blackberry apps • Apps have been run over 200,000 times • No stats available for browser version

  14. 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 “Locked in” to technical platform Annual maintenance fee $$ Usage reporting is limited

  15. 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 (OpenMobile, RhoMobile) • MIT framework is the most mature • UCLA framework is newer and approaches things differently

  16. Trends in mobile… • Moving away from downloadable apps to browser based frameworks • Why?... • Can’t keep pace with all the new platforms • iPhone, Android, Blackberry, iPad, etc. • Each vendor has different requirements and proprietary technology for constructing the app • Every enhancement needs to be approved by the vendor and “pushed” as an update to consumers • Long process

  17. Trends in mobile… • Moving to frameworks for the mobile browser • Why?... • Device agnostic • Mobile browsers becoming more sophisticated and can handle more dynamic interaction • Touch sensing, Geolocation • HTML 5 & CSS 3 • Enhancements rolled out in real time • Less costly to maintain

  18. Different types of frameworks • Most frameworks are a package deal: • Server side and client side bundled together • This means all the stuff has to live on the same server. • Examples: Most open source and MIT framework • Client side framework • Platform independent. • Mobile Web Browser specific: optimized per device • Can be used for Web content (CMS) or Web applications • Example: UCLA Framework

  19. UCLA Framework • Keep it in the “UC Family”.  • UCLA is very open to having all the UC’s contribute to the core code and branches, • They have a governance structure in place • Monthly meetings to discuss strategy and new offerings • They are doing this the “right way”: great documentation, devoted to a long term strategy, looking ahead • Other UC campuses contributing to framework: • UC Riverside • UC Berkeley

  20. UCLA Framework • HTML is the primary driver so it can be used across different technologies • Markup: • Simplistic • Semantic • Degrades gracefully • Standards compliant (WC3) • Fully documented

  21. UCLA Framework

  22. UCLA Framework

  23. 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 a roadmap for mobilizing student and other applications

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

  25. 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) Next up… Social Sciences Office of Graduate Studies Giving Math Department Chemistry Department Career Services Center Literature Department Conflict of Interest Ethnic Studies Department Literature Department Psychology Department Parents & Families Research Portal

  26. Brett Pollak Emergency

  27. Emergency Status

  28. Emergency Status

More Related