General overview of tasks with which ANS can help:

Detail of Instructional Tasks

Student and faculty accounts

• Each student has his/her own account

• Do we start with all classes or just certain ones?

• Do we include non-credit classes?

• UImport scripting

• Transfer data from "mainframe" to Netframe

• Testing selected accounts

• Who is responsible for doing anything

• What type of contingency accounts to have

• Faculty requested traditional "class accounts"

• Baladin prefers temporary personal accounts

• Faculty management accounts

• how created

• who creates

• what rights

• Access

• To accounts from off campus

• From Macintosh computers

• From CAD, GDT, IT, and other labs

• To Orchard from on campus

• Help and account maintenance

• How are students and faculty notified when accounts are ready?

• Who provides ongoing support?

 How to run software

• All software will be accessed only through Netware Application Launcher (NAL)

• Configuration of software will be tested and signed off by faculty or staff in the academic department for which the software is installed

• Software installed on a "clean" stand-alone workstation

• NAL installs the configuration on the network server

• Problems arise and must be dealt with on an ad-hoc basis

• Initial problems are resolved by the installer

• Testing is carried out by the user department requesting the installation

• Installer adjusts the installation until user signs off

• What to do when procedures are not followed?

• When is a WCC staff member "trained" to install software?

• How is ongoing support provided?

• How are new applications added?

• Can we use alternative (non-NAL) network access methods?

• Who is in charge of making policy decisions?

 Access to data

• Instructional data is "owned" by Department and maintenance delegated to faculty and staff

• Data is accessible only to students in a given class, determined by group membership, unless access is widened by the data owner

• Department chair is responsible determining who has maintenance duties. Data may be maintained by department staff or with help from IS staff, at the option of the department

• File structure is set up on the Netframe so that each Dept has its own area

Network Svcs

• Department chairs are each given an account with full access and supervisory rights over their directory area

• Chairs and/or staff designated by chairs are given training on how to administer instructional data space, e.g. set up directories, assign access rights, load data, and maintain security 

• Dept chairs are also given forms to request services from IS

• What exactly is the directory structure to use?

• Who will create a directory for each department?

• Who in IS is responsible for helping Depts maintain their data space?

 Training

• Technical experts (e.g. ANS) need to train WCC technical staff

• WCC technical staff need to train non-technical staff

• Documentation is prepared giving overview and specific objectives, step-by-step instructions, and error-recovery details

• Experts demonstrate a procedure

• Trainees do the same procedure under supervision

• Trainees repeat the procedure independently with help immediately available

• When level of confidence is sufficient, experts and tech staff "sign off"

• Installing & debugging using NAL

• Preparing uimport control file from SIS

• Using uimport to create accounts

• How to administer instructional data space on Novell (e.g. set up directories, assign access rights, load data, and maintain security)

• Logging in as a student, downloading instructional data, and using apps

• Using temporary (class) accounts

• When will training be provided?

• Which individuals within each organization will provide it?