Content Management Systems

From Clinicaltools.com

Jump to: navigation, search

Contents

Table of Features

Features Drupal JBoss Portals Moodle Plone
Bulletin board X X X X
Calendar X : we embedded google calendar, but there is a drupal events module X: google calendar widget X X
Chat X : modules available, have not been tested X : google talk widget X X : available, not implemented
Comment on this page X X : toggle-able
Customizable forms: contact us X X: requires programming X
Customizable forms: enter your contact information (prescribers) X X: requires programming X : totally customizable objects
Customizable header/footer X X X X
Database (e.g., for items like our websites database) X : CMS is database-driven - all content types are stored this way X X - can use ZODB or SQL
E-mail this page X X
Hypertext Transfer Protocol Secure (https) X - may be problems with some modules X
Multiple permission levels X : can define unlimited different user roles X X X - also built in workflow systems
Printer-friendly link X X
RSS X : reader and publisher X X X : readers easy; publish any collection
Site search X : standard search and modules for custom searches X : implements Apache Lucene X
Categories/Labels/Filters/Tags X: ability to create taxonomies and tag content. Useful for searching, displaying subsets of content, filtering content, etc. X: for the blog feature X : as complicated as we want - includes vocabulary as well as smart folder/collection
Test/Survey functionality (with data collection) Quiz module currently being evaluated? X X: formgen is basic system for this, more complicated possible
User registration / account creation X X X X : also openid support
Hot-deployable modules/add-ons (does not require service restart) X X requires restart to make Plone product available, install/uninstall possible without restart
Column-layout modification (i.e., adding/removing columns) X : is theme dependent X X : theme dependent
CSS access (ability to edit cascading style sheets) X : but not through CMS interface X : not through CMS interface X : through Zope
File upload (including images) via browser X X X X : kupu does a great job of this
Groups (ability to separate members by specific groups -- e.g., different medical schools) X : with Organic groups module, or possibly with user roles X X : role like system
Navigation updates (navigation automatically updates when new pages are created) X : for book type content X X x : depending on content type and add/on navigation
CMS Versioning (ability to roll back content to prior versions) X
TOTAL 23 18 Still testing 21

Framework

Need

In its move away from JPartner, Clinical Tools (CTI) needs a robust CMS that provides various features (see table above).

Vision

CTI uses a CMS that is stable, flexible, and scalable, allowing the company to run all of its content through one platform.

Mission

CTI is testing various CMS platforms to see which one best meets our need.

Constraints

  1. Time: We have to get this done in less than two weeks.
  2. We may not find one CMS that serves as a panacea. Most likely, we will utilize two or three; the CMS used in any given situation will be determined by the circumstances of that situation.

Strengths

The CMS platforms we are investigating are open source (i.e., free). We don't have to pay or sign up for a contract during this testing phase.

Target Audience

  • CTI Staff: those who would use the CMS in the course of their work
  • CTI Clients: physicians, medical students, caregivers, etc.

Participants and Roles

  • CTI staff members will be testing the platforms posted in the table above and noting which ones contain what features.

Goal

We have enough data to determine which CMS platform(s) is appropriate for CTI.

Objectives

  • Test each CMS in the above table.
  • Record which CMS contains what features.
  • Meet and discuss the assets and liabilities of each CMS.
  • Decide which one(s) to implement with each project.

Timeline

Deadline: August 8, 2008

Evaluation

Success will be determined by whether all of the above objectives are met (simple binary question).

Findings and Questions

TBD

New Ideas

TBD

Miscellaneous Notes

CTI needs two core functionalities from its CMS: quiz delivery and data collection. In Drupal, this is achieved via Webforms at its simplest and CCK at its most complicated. Neither are perfect. This issue alone warrants an investigation of moodle (see review).

Course Experience Delivery: In Drupal, this is mainly a presentation issue and thus, probably depends on views. There are also logic issues (can I just _____ to the post test -- has enough time elapsed?).

Plone Comment (from James): "buildout config allows quick version/ghost deployment."

CMS Reviews

Retrieved from "http://wiki.clinicaltools.com/Content_Management_Systems"