DukeWeb Enterprise CMS

Update for Web Community2/10/2004

Cheryl CrupiSenior Manager, Duke OIT Office of Web Services

CMS Needs

Needs > identified by CMS ITAC sub committee:

Create and maintain web sites.

Enable content sharing (syndication)

Support users with diverse technical skills and project resources.

Recommendation > enterprise CMS for the Duke community (DukeWeb)

DukeWeb Functionality

Content Authoring – friendly web interface for non-technical users to create and update content.

Flexible Presentation – presentation separate from content enables easy design changes.

Syndication – Inbound and outbound content sharing via RSS or XML.

Workflow – manage content lifecycle – author, edit, publish, expire, archive.

Versioning – check-in / check-out, revision history.

Remote Access – seamless access via the web.

Dynamic delivery – content from a variety of sources / delivery possible in multiple formats.

Security – Duke NetID authentication via WebAuth

CMS Solution

December ’04 Duke purchased an enterprise license of ContentXML as the underlying technology for DukeWeb.

ContentXML was selected based on a variety of criteria, including: Viability as an enterprise tool Functionality Flexibility Cost Speed to deployment

ContentXML is an XML based “push” CMS product.

Deployment Vision

Services andResources

CommunityEngagement

Central Infrastructure

SuccessfulDeployment

Community Engagement

To ensure communication and community involvement, these teams are being convened to guide and support rollout.

Sponsors Strategic direction, policy, prioritization.

Advisory Team Deployment oversight and feedback.

Technical Team - Core

Infrastructure management and support.

Technical Advisory Team

Business practices, data sharing standards, technical oversight

Functional Team - Core

Evolving community needs and future requirements.

Communication Team Communicate with user communities.

Services and Resources

Access to DukeWeb for any Duke related project (free)

Resources Generic templates (free) Image bank (free) Web statistics (AWStats Project) Hosting – TBD (assessing needs and demand)

Web Projects (fee-for-service) OWS or vendor referrals To get into the project queue contact OWS

Training and Knowledge Sharing Training – working on training plans Community collaboration tools (Confluence) Documentation OIT user support – working on model

CMS High Level Rollout Plan

Milestone Kick Off Targeted Dates

Notes

Production Environment Setup 1/4/05 2/7/05 Complete.

First Website Implementation - Office of News & Communications

12/20/05 4/4/05 On Schedule. User training – target week of 3/21/05

Student Affairs Planning 2/7/05 3/31/05

Student Affairs Implementation (Phased approach)

4/1/05 7/05

Generic Template Development

4/1/05 7/05

General Availability Target 7/05 Training schedule TBD.