1 / 57

Waterloo CMS Project

Waterloo CMS Project. Strengthening Collaboration of University Web Specialists. Overview of Presentation. Technical Projects Collaboration - Lessons Learned Current Waterloo CMS Project - Overview OTWS Technical Overview Questions & Answers. Collaboration – Lessons Learned.

amable
Download Presentation

Waterloo CMS Project

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. Waterloo CMS Project Strengthening Collaboration of University Web Specialists

  2. Overview of Presentation • Technical Projects Collaboration - Lessons Learned • Current Waterloo CMS Project - Overview • OTWS Technical Overview • Questions & Answers WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  3. Collaboration – Lessons Learned Collaboration on Technical Projects Lessons Learned from UW Web CMS Projects WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  4. Historical Perspective Web Advisory Committee has sponsored 4 investigations into web content management: • Content Management • Content Management Systems • Web Content Management Systems • Waterloo CMS Project WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  5. Shared Need • There must be a shared need WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  6. Defined Goal • There must be clearly defined goal WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  7. Time Commitment • There must be a time commitment from individuals WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  8. Be Flexible • Be flexible with time commitments from individuals you really want on the project WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  9. Commitment from Above • Get commitment from above WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  10. Secure Funds • Try to secure the funds that you need to accomplish your goals WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  11. Project Plan • A clear project plan that all stakeholders are aware of and agree with WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  12. Representation • Representation from major units on campus WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  13. Politics • Leave your politics at the door WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  14. Consensus • Joint decision making - consensus not voting WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  15. Disagreement • Agree to disagree behind closed doors WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  16. Leadership • One project head WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  17. Transparency • Transparency WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  18. Positivity • Commitment to positivity WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  19. Mutual Respect • It helps if you like each other WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  20. Collaboration Tools • Use the tools WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  21. Meetings • Follow good meeting practices: • Standard meeting times • Agenda • Minutes (or at least notes) • One hour is optimal • End on time WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  22. Success • Nothing succeeds like success WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  23. Waterloo CMS Project Waterloo CMS Project Overview of the Current Project WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  24. Project Start The beginning Project Charter • Finalized Sep 4 2009 • Available on IST website http://ist.uwaterloo.ca/projects/wcmsproject/waterloo-cms-project-charter-20090904.pdf WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  25. Project Objective Implement OTWS as the centrally supported website creation and maintenance tool at the University. • OTWS was previously RedDot WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  26. Central Support OTWS will replace the current centrally supported website creation and maintenance tools, Adobe Dreamweaver and Contribute. • Dreamweaver may be used for template design work for templates to bring into OTWS What about DW and Contribute? WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  27. Software Costs Budgeting for software costs to use the CMS is not required • Website maintenance is done via a browser (e.g. IE, Firefox) • No additional application needs to be installed on workstations • IE for administrative interface Do we need to budget for additional software? WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  28. Project Schedule • Pilot website using the CMS is scheduled for launch in Sep 2010 • CMS adoption across the University will begin after Sep 2010 When can we use the CMS in our area? WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  29. Project Planning PLANNING IS KEY to successful CMS implementation and rollout! • Training and support plans in place for users of the CMS • Internal expertise to administer and support the CMS • New web-design requirements to implement in the CMS • Scalable system architecture definition & implementation • Flexible application architecture definition & implementation Why will it take so long until we can use the CMS? WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  30. Deliverables & Work • Internal expertise in the CMS (via training and pilot) • System architecture requirements definition & set-up • Application architecture requirements definition & set-up • Pilot website plan, design, development, testing & launch • New web-design implementation in the CMS • Accessibility-compliance configuration and testing • Training and support plan (documentation and courses) • University rollout plan (+ content migration strategy) < What are we suppose to do on this project? WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  31. Pilot Website What website will be the pilot website? The pilot website will be a new Waterloo Web Resources website • Resource for CMS adopters/users across the University • Will house and point to University web resources • Way to develop internal expertise in the CMS • Manageable size website to do as iterative prototypes • Large enough to test the capabilities and requirements of the CMS WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  32. Project Team Glenn Anderson (IST), Lara Babalola (Science), Linda Beaulieu (Engineering), Mary Lynn Benninger (Registrar’s Office), Daniel Delattre (Engineering), Michelle Douglas-Mills (AHS), Donald Duff-McCracken (Environment), Guillermo Fuentes (Arts), Eva Grabinski (IST), Manfred Grisebach (IST), Sarah Forgrave (CPA), Chris Gray (Library), Lauren Harrison (Housing & Residences), Adam Hewgill (Housing & Residences), Bob Hicks (IST), Karen Jack (Secretariat), Pat Lafranier (IST), Tammy Marcinko (Human Resources), Isaac Morland (CSCF), Liam Morland (Distance & Continuing Ed), Rose Padacz (OPD), Susan Shifflet (OPD), Sean Speers (Arts), Terry Stewart (AHS), Jason Testart (IST),  Martin Timmerman (IST), Lisa Tomalty (IST), Evan Truong (Environment), Heather Wey (IST), Jonathan Woodcock (Engineering) What areas are represented on the project? WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  33. Project Roles WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  34. Team Structure & Commitment How much time are team members putting into the project? Core Project Team Members: • Responsible for conducting the core work on the project • 0.5 to 4.0 days per week (dependent on project phase, role and demands) University Consultants: • Responsible for providing consulting in special areas of relevance to the project (accessibility-legislation consulting; online-security-requirements consulting; University-policies consulting; communications consulting) • 0.5 days per month anticipated * No secondments WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  35. Organizational Chart How is such a large team organized to do work? WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  36. Project Communications How can I learn about the project? • web.uwaterloo.ca • Daily Bulletin • WatITis (technical) • Web Advisory Committee (WAC) minutes • UWweb mailing list • Contact project team member • Suggestions? Other: Status updates- UCIST, WAC, CTSC, ASCR, FACCUS WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  37. New Web Design Yes, the plan is to rollout the CMS with the new web design/templates from the Web Redesign Project Will the new web-design templates be available in the CMS? WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  38. OTWS Overview Open Text Web Solutions System Overview WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  39. Rationale WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  40. Users WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  41. Remote Users Firewall WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  42. Management Server WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  43. System Requirements • Windows Server 2003 and up • Microsoft SQL Server or Oracle • Minimum 4 Gb RAM • Minimum 20Gb Disk space • Our plans: • Windows Server 2008 R2 • Microsoft SQL Server 2005 • Virtual machines at first • Clustering Management server ? WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  44. Ancillary Servers WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  45. Security • LDAP Authentication • Granular Privileges • Versioning • Work Flows • Audit Trails • Login Histories • Fully SSL compatible • Captcha (Built-in Q1, 2010) WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  46. Support • 8-5 M-F standard support • Coordinated by IST likely • Training at cost • Public Forum • Mailing List • Knowledge Base • Online Help • Third Party Partners WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  47. Ease of Use • Web 2.0 based GUI • Wysiwyg editor • Inline editing • Drag-n-Drop Content • Undo • Spell Checker • Friendly URLs • Image resizing • Mass uploading WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  48. Performance • Clustering • Load Balancing • Page Caching • Static Content Export WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  49. Management • Online administration • Workflow engine • Trash • Multiple sites and subsite • Content Scheduling and Staging • Themes/Skins • Web Statistics • Multi-language support WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

  50. Interoperability • FTP and SFTP support • WebDAV Support • WAI Compliant (section 509) • XHTML Compliant • Content Syndication (RSS) • UTF-8 support WatITis | Strengthening Collaboration | December 8, 2009 | Waterloo CMS Project

More Related