As part of its mission, the Web CMS implementation committee was tasked in March of 2008 with conducting a comprehensive evaluation of the selected system — Hannon Hill Cascade Server — in the context of our campus deployment. Today, the committee published its assessment of the product and its unanimous recommendation to proceed with deployment of the system at UC Davis.

(more…)

Last year, UC Davis conducted a survey of higher ed institutions across the nation. We collected comprehensive data about the adoption and use of Web content management systems, and published this information for the public. Our goal was to learn about the experiences - both positive and negative - of other universities in the adoption of Web CMS, and to share this information with those who may currently be considering the same.

Recently, the URL for the survey results has changed to http://cms.ucdavis.edu/cmssurvey. Please update your bookmarks accordingly.

An updated version of the Web CMS frequently asked questions has been posted to the initiative’s official Web site at http://cms.ucdavis.edu. Collaboratively developed by the CMS implementation committee using feedback and questions received from staff across campus, the FAQ provides answers to common questions about CMS and the UC Davis Web Content Management Initiative.

(more…)

While the implementation committee has been hard at work on the configuration and implementation of the software, templates and user roles in Cascade Server, the campus has clearly been abuzz with talk about when the system will be available, what features and functionality it will provide, and who will be able to use it. As part of a multifaceted effort to inform the campus about our process and progress, our implementation committee has activated two new subcommittees: training and communications.

(more…)

As one of its first tasks, the implementation committee was charged with the recruitment of partners whose sites will be among the first to be deployed using the campus Web CMS later this year. The first adopters of the Web CMS will play a substantial role in deciding the nature and shape of the system on campus. As such, being an implementation partner requires a significant commitment.

After meeting with many units and departments who have expressed interest, evaluating requirements and comparing objectives, the committee has finalized the list of partners.

(more…)

As of April 30, the Requirements and Evaluations Committee has officially wrapped up its work, and the implementation phase of the UC Davis Web CMS initiative has begun.

(more…)

The Web CMS implementation committee convened for the first time this week. Like the requirements and evaluation committee that preceded it, the implementation committee includes technologists and content managers representing a broad cross-section of the campus. However, implementation committee members have additionally agreed to be among the first adopters of the campus Web CMS.

(more…)

The UC Davis Web Content Management Initiative spent much of 2007 learning what different parts of campus need from a Web CMS, then evaluated 150 potential sources. The requirements and evaluation (R&E) committee–which includes technical and Web publishing representatives from academic and administrative units across the campus–diligently narrowed that list to 14 candidates, then nine, then three, and now one.

(more…)

As part of UC Davis’s active search for a campus Web content management solution, the project’s Requirements and Evaluation committee has conducted a review of select, pre-qualified Web CMS applications. To provide the necessary background and hands-on product experience required for a thorough assessment, and to develop and document recommendations that will be presented to the project team and steering committee, the committee recently invited specific vendors to provide informational product demonstrations.

(more…)

Today, the Requirements and Evaluation committee of the UC Davis Web CMS initiative publicly released the project’s Technical and Functional Requirements. This document details and prioritizes the specific Web CMS features and functions required by the campus, as formulated and agreed upon by the committee.

(more…)