ACM Home Page
Please provide us with feedback. Feedback
Campus computing newsletter editors & the network: a new role for the 1990s
Source User Services Conference archive
Proceedings of the 18th annual ACM SIGUCCS conference on User services table of contents
Cincinnati, Ohio, United States
Pages: 16 - 24  
Year of Publication: 1990
ISBN:0-89791-406-6
Author
Sponsor
SIGUCCS: ACM Special Interest Group on University and College Computing Services
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): n/a,   Downloads (12 Months): n/a,   Citation Count: 0
Additional Information:

abstract   index terms  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/99186.99187
What is a DOI?

ABSTRACT

Campus computing newsletter editors have traditionally been responsible for disseminating relevant technical and general information to a specific user community; most often members of the computing department. As information technology and computer networks become more readily available to a wider range of individuals — and classrooms — editors must now also address a more diverse user community. How do campus computing publications specialists keep up with these and other changes while continuing to create publications that meet the needs of their readers? One important resource is the network. National networks provide editors and writers with an opportunity to tap into the resources available on other campuses to expand their own knowledge base and broaden the information available to their readers. Services such as the CCNEWS Newsletter — an electronic forum for campus computing newsletter editors, and other network services, such as discussion groups focusing on page layout and design software, and the English language, are attracting hundreds of editors and writers. Local area networks — another resource that has become invaluable to editors — are also replacing traditional methods of coordinating newsletters. The use of e-mail and conferencing is enabling writers and editors to more easily collaborate on articles, and has become an efficient method of planning and distributing relevant information. But the network is only one element that has influenced new policies and procedures for campus computing editors. Desktop publishing, laser output, and the myriad page layout and design and graphics programs have created a demand for more aesthetically pleasing publications. Likewise, electronic spelling checkers, grammar checkers, and stylesheets mean newsletters with better-quality writing. New potentials and concerns need to be addressed regarding the role of the campus computing newsletter editors. Panelists — including the editor of CCNEWS, and newsletter editors from the University of California-Davis and Brown University — will attempt to explore and define this new role in an increasingly information-intense environment, while focusing on the following policy and procedural issues: Are campus computing publications adequately meeting the needs of their increasingly diverse community — from writing departments to engineering labs? How can the network be used to gain information that will encourage more reader interest, without sacrificing the quality of material relevant to a specific campus community? Evidence suggests that editing a campus computing newsletter is just one of many responsibilities delegated to a staff member within the campus computing department (or some central service on campus). In addition, editors traditionally rely on their colleagues on campus to contribute material and provide input. Given these time constraints and limited resources, how can the network — both local and national — help to reduce the frustrations of the editor's job and help better coordinate their tasks? As campus computing publications become more aesthetically sophisticated — due to the increased availability of page layout and design software, computer graphics, and laser output — are the qualifications of the editor changing to reflect design and editorial ability, as well as technical expertise? What kinds of new information, guidelines, and criteria should senior staff responsible for overseeing campus computing publications possess to better manage these publications?