Committee Charge  

UCSC has developed web sites with exemplary form and function. However, the web development 

tools deployed across the campus are heterogeneous. For UCSC to move to a portal environment, and 

produce a better, more consistent web presence, we will need to use common tools, have a support 

model for these tools, and have an oversight and governance model for tool usage. Implementing 

common tools across campus is a first step towards a portal. 

In FY2000 01, the ITC's Web Presence Committee survey showed that UCSC invested $2.3M for web 

services emanating from 600 web servers. Over 80% of the expenditure was for labor. In this era of 

budget reductions, we have an opportunity to focus on using web development tools to optimize web 

sites in preparation for developing a campus portal. Clearly, web expenditures are big business on 

campus, and warrant a centralized strategy and development support framework. While the total 

amount spent on web services may not be reduced below $2.3M, the quality of information provision 

can be increased. In 2001, the Web Presence Committee was the first step in web strategy 

development. The Web Services Committee has continued the work of that first committee, with a 

focus on defining a sustainable web development framework. This sustainable framework will enable 

long term web services integration, which is essential for the New Business Architecture, and for 

increased efficiencies in the academic arena.  

The Web Services Committee is charged to: 

1.  Define the current and recommended UCSC web development framework, including the roles 

and responsibilities of web developers, content managers, system administrators, information 

architects, and unit heads.  

2. Recommend 

a 

governance/oversight model to provide leadership and planning. 

3.  Identify "official" sites and sources of information at UCSC, and identify a process for 

identifying future sites.  

4. Identify 

appropriate 

content management strategies and recommended next steps.  

5. Identify 

web development tools currently used at UCSC, and a process for tool adoption.  

6.  Recommend next steps to move toward achieving the web presence vision contained in New 

Business Architecture, AIS Web module, and other academic or campus web initiatives, including 

portals. 

This report proposes a web development framework, identifies  readiness  issues in that framework, 

recommends actions to be taken, and resources required. There are four primary sets of customers 

who will be impacted if the report is implemented: 

1.  The UCSC academic community (faculty, students, instructional staff)  

2.  The UCSC administrative community (staff) 

3.  Visitors to the campus web sites (e.g. prospective students and faculty) 

4.  The UCSC computing support staff 

_________________________________________________________________________________

Web Services Committee 

Page 4 

May 28, 2002