1. Duke Enterprise CMS CGS Meeting 5/7/2004 Cheryl Crupi Senior Manager, Duke OIT Office of Web Services

2. CMS Project Background Project Goals System for managing web content Syndication of content across websites Requirements Discovery 1 year process Diverse stakeholders - ONC, Fuqua, Pratt, DCRI, Auxiliary Svcs, Arts & Sciences, OIT Key Partnership Office of News & Communications (ONC) providing strategic leadership for content OIT providing the technology solution

3. CMS Project Background (cont.) Vendor Selection From field of about 10, seriously considered Interwoven and Zope Zope was selected Project Scope CMS for Dukes federated structure Z4EDU product - Zope Corporation hopes to offer the product broadly to the higher education industry

4. 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 – search for content by topic or source / automatically subscribe or manually moderate items Workflow – manage content lifecycle – author, edit, publish, deliver, archive Versioning – check-in / check-out, revision history Remote Access – seamless access via the web Dynamic delivery – content from a variety of sources / schedule publish and expiration / delivery in multiple formats (future) Authentication - Shibboleth

5. Syndication Model Local Channels (push) Syndication within a family of websites – content not generally available (synd. w/in a division) No limit to channels / no institutional moderation Global Channels (push) Syndication to hub – content available to all No limit to channels / no institutional moderation Enterprise Channels (pull) Syndication to hub – content available to all Official channels with administrative oversight and certification of information (HR channel)

6. Deployment Model Central Campus Build Independent Verticals Library Pratt School of Engineering (potential) Health System (potential) Independent CMS Systems Law School

7. Central Campus Build OIT role Manage system Facilitate requirements gathering and prioritization of enhancements to benefit the general user community (benevolent dictator role) Support users Build sites School / department role Contribute code for broadly applicable enhancements Cost Model Access to system – free Hosting – free Site design and development – for fee

8. Independent Verticals OIT role Provide access to code base Provide infrastructure for collaboration among participants in the open source community Potentially develop custom enhancements School / department role Administer own infrastructure Enhance as needed Cost model Code –base is free Technical support – free / for fee Custom enhancement – program themselves or for fee

9. Independent CMS Systems OIT role Provide information on standards and best practices Support RSS syndication to and from the enterprise syndication hub Support potential migration to enterprise system at some point School / department role Administer own system Support RSS syndication to and from hub Cost model Info sharing – free Syndication support – free Support migration to enterprise CMS – free / for fee

10. Branding Recent Recommendation of the University Web Policy Group encourages consistent use of visual identity elements and providing ready access online to visual identity resources ONC is driving a web branding initiative to develop basic standards for logo use and typography Web Services can support the branding initiative by serving as a clearing house for visual identity resources and information (i.e., what color is Duke blue) Likely have biggest impact by offering CMS templates (quick deployment and no design costs) and having logos and other design elements in the CMS repository

11. Timeline CMS Development – complete 4/30 Acceptance Test Projects – May Duke News Fuqua School of Business Pilots – June HR Library (independent vertical) General Availability – June / July