1 / 30

Content Management Systems Survey

Content Management Systems Survey. CSG Survey Fall 2005 Tom Dopirak. What I Learned. If you try and start a CSG assignment within 2 weeks of the previous CSG you hear laughing Carl knows everybody Counting is hard Surveys look great until you analyze them

nitesh
Download Presentation

Content Management Systems Survey

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. Content Management Systems Survey CSG SurveyFall 2005Tom Dopirak

  2. What I Learned • If you try and start a CSG assignment within 2 weeks of the previous CSG you hear laughing • Carl knows everybody • Counting is hard • Surveys look great until you analyze them • There is no point in starting to analyze survey results until 48 hrs before the presentation • The more questions you ask , the more confusing the results are to correlate

  3. Mascot Available

  4. What is a Content Management System? In computing, a content management system (CMS) is a system used to organize and facilitate collaborative creation of documents and other content. A CMS is frequently a web application used for managing websites and web content, though in many cases, content management systems require special client software for editing and constructing articles. The market for content management systems remains fragmented, with many open-source and proprietary solutions available. -- WIKIPEDIA

  5. Who has content management? • Minnesota - FileNet • Delaware - Homegrown • Duke – HannonHill • Texas -Stellent • Princeton - Roxen • Cornell - Paperthin • Penn State - Zope, RedDot • Virginia - Brigolage, Layla • Georgetown - Homegrown

  6. “Sort of” Content Management • CMU (Blackboard) • Georgetown (Blackboard/Xythos) • Brown (Macromedia Contribute)

  7. Not Centrally Run or Influenced • Wisconsin • Yale • Michigan -- Many in departments • Virginia Tech • Washington -- Looking at Plone for internal use

  8. Active CMS Evaluations • Carnegie Mellon - Full evaluation • Delaware - Looking at open source • Washington - Zope internally • Brown - Considering Hannon Hill

  9. How It all works .

  10. Bolinos Bricolage Cocoon Drupal Lenya ** Magnolia Mambo Midgard Open CMS Oscom PHP-Fusion Postnuke Textpattern Typo3 Zope / Plone Joomia Hypercontent Major Open Source Options

  11. Day Software Documentum Ektron Emojo Eprise FileNet FatWire Hannon-Hill Ingenix Interwoven Media Surface Paper Thin Percussion Red Dot Serena SiteCore SiteRefresh Stellent Tridion UserLand Vignette Commercial Options

  12. Which clients motivated your consideration/adoption of a CMS? • Marketing -5 • Athletics - 0 • Alumni - 1 • Advancement - 3 • Academic Departments - 6 • Enrollment - 2 • Others - 8

  13. Which clients adopted your CMS? • Marketing -7 • Athletics - 0 • Alumni - 2 • Advancement - 5 • Academic Departments - 8 • Enrollment - 3 • Others - 7 • Administration,library, medical center

  14. Principal Business Drivers • Separation of content from presentation and/or logic - 7 • Uniform design - 7 • Reduce publishing costs- 5 • Enforce branding and identity - 6 • Scheduled publishing - 4 • Distribute responsibility and workload - 9 • Enforce web standards (accessibility, technical – non-design) - 6

  15. Does your CMS provide content to multiple different websites? • Yes - 6 • No - 4

  16. What are your publishing targets? • Web browsers - 11 • Mobile devices - 8 • Print - 7 • RSS - 1 • EMAIL - 1

  17. Another Day in IT

  18. Editing Tools to support publish process • Dreamweaver - 4 • Any HTML/XML editor - 3 • Supplied with CMS - 5

  19. Do you use a staging server to preview content? • Yes - 4 • No - 4 • Not sure - 1

  20. Are you using Campus authz/authn? • Both - 8 • Authentication - 2 • Not sure - 1 • Mixed - 2

  21. Media Types beyond text • Image - 4 • Video - 2 • Audio - 2 • Any format - 4 • Forms - 1

  22. What QA features does your CMS provide? • Link Checking - 5 • Accessibility checking - 4 • HTML/XML validation - 5 • Template enforcement - 9

  23. What is a content management system? It’s like a fat substitute. Everybody wants one but nobody really likes the taste and side effects when they finally get it and go back to doing things the old way. --TGD

  24. How Did Technology Affect the CMS Choice? • Integration with student system • Integration with Campus Authz/Authn • Establish vendor relationship • Time to deployment • Adherence to Open Standards • Ability to affect product development

  25. How Did Technology Affect the CMS Choice? • Preferred Open Source • It was a major factor • Wanted Unix + Apache • XML database + push to multiple web servers • Content in XML with XSLT rendering • Likely to adopt J2EE/ Open Source

  26. CMS Licensing

  27. Why I am the way I am?

  28. Do you use a staging server to preview content? • Yes No • Does you publish processing use Campus Authn/Authz • Yes No

More Related