Learning Environment Architecture Development Project
Technical Staff Needs Assessment Summary
TSP survey is conducted annually by IT, and was administered on-line in
the summer of 1999. See
http://tsp.ucdavis.edu/evaluation/99eval.html for details.
Survey Statistics
| Population for survey: |
300 individuals (Technology Support Coordinators) |
| Sample size for survey: |
300 individuals |
| Respondents (Response Rate) |
150 (50%) |
Support of Faculty
Over half (57%) reported that they provide some technical support to
faculty. The 77 respondents who answered this question indicated that
their faculty support efforts included showing faculty how to (question
asked respondents to check all that apply):
| Auto Lists |
File Transfer |
Backup | Anti-Virus |
Internet |
System Commands |
E-Mail |
Presentations |
| 44% |
73% |
78% |
77% |
92% |
69% |
81% |
64% |
Summary of comments (56 people commented):
Though the number of responses is up this year, fewer people seem to be
doing comprehensive support ("Anything that a faculty member can dream up
is fair game.") Those that are responsible for only specific areas tend
to fall under either the traditional technician services of
hardware/software troubleshooting and upgrade, or in the increasingly
popular web arena. Several commented that their departments are
considering hiring additional staff to support web development.
With regard to whether there have been changes in the way they are
expected to support faculty in their department this year, an increase in
interest in using the web and Powerpoint were the two most frequently
cited sources of additional support time. A representative comment:
"More like a continuous pressure as faculty are more involved in computer
technology. Primarily because the average age of the faculty is going
down a bit. Presentations using computers are up. Web based development
is up. Looking for ways to use computers to enhance laboratories and/or
lectures is up."
Note that over half of the respondents also provide support for from 1 to
30 staff members and students; 26% reported that they provide support for
50 or more staff. This may be the cause of some of the frustration
represented in this comment: "For each of the past four years that I have
been in this job, the percentage of my time devoted to faculty support
has nearly doubled. It seems now that faculty expectations for a
reasonable level of support are exceeding what I consider to be
reasonable. It would be great if the TSP could help to establish some
campus-wide support standards. One idea that I have toyed with is trying
to establish a network of students who can help faculty with home
computerswith pay, and independent of the university."
The diversity in support needs was also mentioned: "Some faculty want
total control, some want someone else to provide all the know-how and
effort and some want something in between. Recently there is also a bit
of a 'technology for technology's sake' mentality in some presentation
and other technologies. Many times the faculty are not really clear on
what they want either."
Computing Platforms in use
Almost three-fourths of those responding indicated that their department
uses at least one Macintosh computer. Forty-one percent reported that
they support at least 1 Unix machine.
Supporting web sites and web page creation
Of the 58 people responding, about half reported at least some
involvement with faculty web pages, which is somewhat lower than last
year. The number of responses naming someone else in the department or
an outside department is up in compensation, however. Many mentioned
student assistants as web developers, with caveats about consistency and
successful completion. However, about the same percentage said faculty
members have no one at all to help.
Respondents suggested the following ways in which the Technology Support
Program could help Technology Support Coordinators who assist faculty
with their web pages:
- "More and better introductory and intermediate classes
and support for Cold Fusion, Active Server Pages and
other database interfacing and management in support
of dynamic web sites. This coming year I foresee static
site maintenance eating us alive!"
- On-line resources (html primer, templates and solutions
to common problems, design programs, strategies for file
transfer)
- Classes for technical support staff on these topics
- Classes for faculty in using html editors
- The Arbor
- Help with security. ("Someone in the sciences,
a professor, is ding the password security . . . a lot to
ask.")
- "It would be great for the campus to purchase licenses
for some of the course management software, like
WebCT, Web Course-in-a-box, etc.
- "Probably nothing, unless you created a central
portal solution for students in a class."
- A TSP forum or special interest group for how
to support/satisfy the varying levels (demands) for
support of faculty efforts.
INITIAL EFFORTS & ADDITIONAL ANALYSIS NECESSARY
The following issues need to be addressed and resolved through the
Technology Support Program and consultation with the Technical Leads for
schools and colleges.
- What are the types of services the TSP or campus might
provide to help technical people support their faculty?
Note: A series of TSP Roundtables has been initiated to
explore this question. In addition, a new program, Providing
Support for Teaching Technologies (PSST) has been initiated
by the Teaching Resource Center to assist Technology Support
Coordinators in academic units, and/or those who are
involved in faculty support.
- How can all of the campus services (inside and out of IT)
coordinate web services? (A series of meetings was sponsored
by the AC4 chair to explore what services are offered, what
the gaps are, and how these can be filled. Recommendations
need to be derived from these discussions.)
- To what extent would development and installation of the
following technologies simplify the support task:
- Course management software
- Distributed file systems
- Database/Middleware/Web server combinations
- Others?
- To what extent should the campus purchase of site licenses
for these products? How many departments want to run
their servers for course web sites, and how many are not
prepared to do so?
- What are the implications on support of potential new
services (e.g., personal digital certificates)?
Note: The LEAD report has recommended pilot projects
to evaluate these questions. A pilot, sponsored by the
Teaching Resource Center has been initiated to evaluate
course management software (see
http://trc.ucdavis.edu/courseware).
Other recommended pilots are pending AC4 review and
approval of the LEAD report.
- Due to the rapidly evolving nature of faculty needs for
technical support and developments in instructional
technology, the next TSP survey should be jointly designed
by the TSP staff, the Teaching Resources Center educational
technology coordinator, and the LEAD team project
coordinator.