Deptcomp Task Force Information
Campuswide task force groups were recently formed to tackle
some of the technical issues we all face.
MAY 26, 2006—Group tasks include researching and recommending help desk software for the
local and university level, considering the possibilities for expanding
site license purchases, coordinating technical training and professional
development opportunities, and developing standard policies and
procedures for IT resources to be recommended to decision-makers.
For those who are interested in learning more about these groups
and their work, we've listed the task forces and their co-chairs
below. Task force wikis and websites are also listed, where available.
1. IT
Security
Tim Miller, Administrator,
Johnson Hall
John
Kemp, Senior Security Engineer,
Information Services
http://security.uoregon.edu/sectaskforce/
This group will work together to develop standards for the campus
and will assist with tightening security across the IT community.
2. Helpdesk
Software
Dennis
Bishop, Director of Information Technology, Knight Law School
Dan
Albrich, Manager, Microcomputer Services, Information Service
https://helpdesk-task.uoregon.edu/
This group will review and recommend a software package that could
be used for tracking "problem tickets at the local, or university
level." Such an application will be useful in supporting faculty,
students, or staff, as it would allow better communication within
the UO IT community, passing tickets when needed to others, and
the creation of a knowledge base of common problems and
their solutions.
3. University
IT Website
Dave
Ragsdale, Web Specialist, Information Services
School
IT Directors to review design as a group activity
This team will consider the design of a UO "IT Homepage" on
the web. Such a page would present a valuable front door to prospective,
new, or current students as well as existing faculty and staff.
While it wouldn’t replace the need for college or administrative
office sites, it might be a good starting point for those seeking
answers to common IT-related questions.
4. Site
Licenses and Volume Purchases
Chris
Jones, Director of Architecture and Allied Arts Computing Services
Mary
Bradley, Microcomputer Lab Coordinator, Information Services
http://aaa.uoregon.edu/computing/sitelicense/
Every year the UO spends a substantial part of university funds
on IT hardware and software. While some of these purchases are
for specialized equipment or applications, much of it is spent
on items where substantial savings could be realized if we worked
together. This group will consider the possibilities for reducing
costs by considering site licenses or volume purchases.
5. Calendar
Software
Tony
Saxman, Director, Business Tech Ctr, Lundquist College of Business
Noreen
Hogan, Principal Technologist, Information Services
http://limestone.uoregon.edu:8000/calendar/wiki
It is difficult to schedule meetings with a group when everyone
is using different electronic calendaring software. While our end
users will be exploring options for calendaring from an application
perspective, this group will help explore the issues involved in
implementing applications from a technical perspective. Their work
will be critical to development of a common calendaring standard
for the university.
6. Training
and Professional Development
Linda King, Associate VP, Human Resources
Beth Sprague, Assistant to the CIO, Information Services
IT Professional Development Task Force Report
With the number of UO personnel providing IT support numbering
well over 200, there is a great need to coordinate training and
professional development opportunities. Members of this group will
help survey the UO IT community and recommend ways we can meet
the training and professional development needs of the group. This
might involve on-site courses, vendor briefings, special speakers,
reference materials, or conference attendance.
7. Peer
Consulting & Review
Don
Harris, Vice Provost, Information Services & CIO
Occasionally, offices desire an outside opinion on a particular
IT issue they are considering. The idea behind the peer consulting
concept is that we could form teams within UO to address common
areas, (e.g., security server administration, multimedia, desktop
issues) and then make these teams available to help others as desired.
Members of this task force will help coordinate this service at
the university.
8. Web
Services & Applications
Mary Harrsch, Network/Information Systems Mgr, College of Education
http://civil-tongue.net:8000/webapps/
The web is a critical resource for many departments at the university.
There continues to be a need to help coordinate the many personnel
who are involved in developing or supporting web resources throughout
the institution. The intent of this group will be to expand that
communication and coordination through user groups, training, and
exploring new options and opportunities.
9. Support
Services
Andre Chinn, Coordinator of Instructional Technology, Journalism
Micah Sardell, Systems Manager, Admin Services & Computing Facilities
http://jcomm.uoregon.edu/stf/doku.php/taskforce
A wide variety of possible support services have been identified
by groups such as the research center directors and IT college
directors. Examples of possible services include managed
servers, videoconferencing, research clusters, backup servers,
collaborative software, security measures, and many more. Members
of this task force will work to determine what areas offer the
most promise for the UO and what would be involved in implementing
selected services.
10. Policies and Procedures
Andrew
Bonamici, Associate University Librarian
Jon
Miyake, Acceptable Use Policy Officer, Information Services
http://www.uoregon.edu/~bonamici/itpolicy.html
We are very much behind as a campus in having adequate policies
and procedures for IT resources. This task force will review
standard policy and procedures areas as identified by EDUCAUSE
and other organizations. They will then define a subset of policy
or procedure areas where the UO would benefit by defining or customizing
its own set of standards. Recommendations will then be made to
appropriate IT governance groups for approval.
|
