In the Administrative Information Services department at Columbia University, we decided to build a set of content management tools to use with our clients.

Goals

CuCMS 1.0 was built upon a basic set of content management criteria

• Store, edit and publish files of any type
• Maintain history of file changes
• Recognize relationships between files
• Enforce access controls to projects and files
• Use uPortal as the platform for management functions

The design process also yielded a set of fundamental technological requirements

• XML based content storage for adaptability, reuse, speed of development
• XSL Transformations to allow multiple output forms of XML content
• XML Includes to minimize data redundancy
• Extensible, customizeable framework for file editors
• Publish files to remote servers via FTP