Xref: utzoo alt.comp.acad-freedom.talk:63 comp.admin.policy:277 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!lll-winken!ames!dftsrv!mimsy!mojo!russotto From: russotto@eng.umd.edu (Matthew T. Russotto) Newsgroups: alt.comp.acad-freedom.talk,comp.admin.policy Subject: Re: Ohio State University CIS Policies Message-ID: <1991Jun5.143833.21547@eng.umd.edu> Date: 5 Jun 91 14:38:33 GMT References: <1991Jun4.160947.7193@eng.umd.edu> Sender: news@eng.umd.edu (C-News) Organization: College of Engineering, Maryversity of Uniland, College Park Lines: 26 In article sbrack@bluemoon.uucp (Steven S. Brack) writes: >> > When I was locked out of my class account early this quarter, > I made 15 phone calls to 10 different people, not counting > being transferred all over campus. > > Apparently the policy of our system administration is to keep > students from solving problems on the local admin level. My > account priveleges were restored after I met with the chair > of the department that owned, but did not manage, the system in > question. My telephony took me all the way from my professor > to the local system manager to the director of Academic Computing > Services, then to the Dean of the Engineering College. I finally > called our University Ombudsperson, who helped me determine who > I should have been talking to, as none of the people I talked to > directed me to the right place. Absolutely. This is apparentely quite common-- every problem I've had with this University, in various departments, has resulted in this sort of runaround. Seems to be standard operating procedure-- which is why a formal, known, due process is needed. The university has a process that staff and faculty can use against students-- why shouldn't students have a process to use against staff and faculty? -- Matthew T. Russotto russotto@eng.umd.edu russotto@wam.umd.edu .sig under construction, like the rest of this campus.