Selection Process

In March 2004, The University of Texas at Austin purchased a Web content management solution from Stellent. This site is designed to provide background on the selection process and information about the planning and deployment of the product at The University of Texas.

High Level Goals

Some of the things we hope to accomplish with a Web Content Management solution are:

• Cost effective design and implementation of campus Web presence
• Greater distribution of content creation
• High quality, consistent experience in UT Web
• Measurable impact on:
  1. Internal Web publishing/development operations
  2. External messaging

Product Evaluation and Selection

Beginning in Summer, 2003 The University began actively searching for a Web content management solution for campus. A list of functional specifications was developed and feedback was solicited from the Web development community on campus.

A Request for Information was sent to major Web Content Management vendors that included the list of functional specifications. From these responses, four vendors (Stellent, Interwoven, Rhythymx Percussion, Merant Collage) were selected for more detailed examination. Each of these four vendors in turn made a more detailed presentation of their solution. Two vendors (Merant and Stellent) were then selected for 2 week "proof of concepts" (POCs). After these POCs, Stellent was selected as the vendor that came closest to meeting our needs.

What Was Purchased?

Stellent has a diverse product line. The University of Texas initially purchased the following products:

• (1) production Stellent Content Server, (1) backup server, and (4) development servers. The Stellent Content Server is the software that actually manages the content by providing metadata, workflow, versioning and other document management features.
• Licenses for document conversion to HTML, XML, and PDF formats for content that gets checked into the Content Server. These products are called Dynamic Converter, XML Converter, and PDF Converter respectively.
• (55) licenses to Stellent Content Publisher or Site Studio. These are Windows only tools that are used by Web developers to create and manage Web sites. ITS is committed to assisting Mac Web developers work with the Stellent Product line as well. Don't assume that if you use a Mac, you can't play; there will be limitations however.
• One license to convert AutoCAD documents to Web viewable formats
• Licenses for 5000 student contributors and 500 faculty/staff contributors

Deployment of Stellent

Product Training

Twelve staff members who were involved in the product selection received training on Stellent Content Server and Stellent Content Publisher for a total of five days from April 6 to April 14. The intent of this training was to get a core group of people educated on the product line so they can begin to use the product and train others.

We will plan on conducting training for Web developers during the summer. Exact dates and times will be determined.

Quick Wins

ITS is committed to demonstrating some "quick wins" with Stellent to show campus what is possible with the tool. Randy Ebeling will also be participating in a conference the first week of May in which he hopes to talk about some of the early wins with Stellent.

Metadata and Document Type Model

The use of Web content management software relies heavily on a strong metadata model. A team of staff from around campus will be charged with developing a model for metadata used in the system.

Security Model and Active Directory Integration

Campus also has complex security requirements. Stellent Content Server will integrate with the campus Active Directory for EID based authentication. However, group, role,and authorization information will be stored in Stellent's user database, not Active Directory. Another team will be charged with developing a robust security model for managing groups, roles, and authorizations in the Stellent Content Server.

Production Installation Configuration

We are acquiring the necessary hardware needed for a production installation of Stellent. The Stellent Content Server will run on Solaris but will also consist of a conversion component running on a Windows server.

Communication and Education to Campus

We are in the early stages of this process (we have had the software for about 3 weeks). The initial plan is to focus communication and training on Web developers who in turn will train content contributors in their own departments on the use of the applications and sites they create.

Also visit this site for updates on the Stellent deployment for campus. As the project takes shape we will use this site to update campus Web developers.

Product Advisory Board

To support the implementation and future use of Stellent on campus, a campus Product Advisory Board has been formed consisting of staff members from the Colleges, Administrative units, Public Affairs, Information Technology, and the General Libraries. This group will be responsible for both planning and evangelizing and also shaping future uses on campus.

If you have questions about Stellent contact TeamWeb.