Untangling the Web: Cooperative Development and Maintenance

Michael Adams, Julius Bianchi, and Carole Thompson

to start of paper

Life Backstage

Two years ago there was no web site at CLU. The systems manager selected a familiar software--the NCSA http server--for the University's web server. The decision to install NCSA http server pre-dated the Internet Task Force and was made without any consensus. Our needs have changed dramatically since then, and we have now decided to move to the Netscape Commerce Server, to incorporate encryption as our users submit or receive sensitive data over the web. This decision was made differently, having been the suggestion of the Director of Publications to consider another server. He is more involved with a variety of units who are developing the mechanisms we use to deliver information to and receive from users. After review by members of the ITF, the system manager proceeded to contact Netcom and make the arrangements for use of the software, and is now planning the migration.

Server installation and setup involve a variety of elements. When setting up a web server, a site must have a TCP/IP and network connection. Aliases must be added to the DNS (domain name service) for the host server allowing the web server host machine to be referred to as "www" or any other name. In CLU's case, we also registered a domain alias with Internic, so that we are not only www.callutheran.edu, but www.clunet.edu.

Increasingly, security for a server is becoming an issue as data submission through the use of forms becomes common, and as we expand our use of the web for data retrieval of a sensitive nature, as in the case of delivering student data or library "has" or fine lists. Some directories are restricted to our internal domain, in other instances, data retrieval should be restricted to password access. Some of the access restrictions are included in the server software setup and configuration and others become a part of the CGI or perl scripts that must be written for custom applications. The extent to which a site uses scripted routines may prompt a decision about hiring or training someone to program scripts. In time, availability of commercial scripts and other programs will increase allowing users to buy off-the-shelf programs rather than having to develop custom programs in-house.

Maintenance of the server is largely left to the administrator, although experience is teaching our group that some issues need review by the Task Force, especially when users "push the envelope". Naturally, a site must implement routines so that the software is started up whenever the machine recycles, but checker routines will verify that the server's processes exist in the machine's process table, and alert an administrator if it falls out for any reason.

Performance is becoming a particularly vulnerable issue as our campus increases its use of and dependence on our web server. Better performance as well as the addition of new features is a reason to keep up with upgrades and patches for the server software and is a key issue in development and expansion. Obtaining statistics from the server logs involves obtaining and installing the statistics software, coordinating its use by groups or units on campus, and automating report generation. Logfiles must also be regularly moved off the system, and restarted to keep disk space optimized, and to speed the collection of usage data for statistics. Backups of data are included with the overnight routines, but individuals who painstakingly create and update pages should be encouraged to keep copies of their work. Individual backups are easily made if web authors are editing on local PCs and uploading to the appropriate directory on the central server. Upgrades to existing software are generally low-impact. As the technology changes, migration to a second generation server may occur. Moving to another software is far more complex, particularly when serving several thousand pages every day. Someone always seems to need access to the system.

The development of the subdirectory structure containing documents, graphics, and script and program files needs careful thought so that it will evolve well as the site grows in complexity and volume. CLU has created two principal types of directories, departmental and topical, which reside in a specific file partition dedicated to the campus wide information system. General campus page files are owned by their creators, with group ownership which permits fixes or modifications under urgent circumstances by any member of the team group. Departmental pages are owned by a designated departmental maintainer but again obtain oversight by the core development team by having ownership set to the core team group ID. Symbolic links are added to the designated maintainer's login directory, to facilitate changing directories and eliminating the need to use and remember the rather long and tedious absolute pathname(s). Many users have developed personal pages in the public_html, but none of these are linked to the campus pages.

Another issue is one of decentralization and the extent to which it is encouraged if users have sufficient sophistication. To this point, we have a minimal level of decentralization, although it is an area which begs attention. We have three "official" web servers at CLU: two are run by ISS, one by the Computer Science Department. Unofficially, we have only a handful of known staff and students who have installed server software on PCs. Decentralizing makes hardware issues and software issues more critical, in terms of the workstation equipment hosting the departmental pages. Who maintains them? Who decides what server software? Who is responsible for the backups? Do the advantages outweigh the disadvantages? Do individual machines receive domain name configuration, students as well as departmental machines? These issues will be most appropriately decided by the Internet Task Force.

Net Results

On a similar set of questions about University-provided electronic information resources, over 50% of the students reported that these resources frequently or always: (1) supported the content of the course; (2) were easy to find and use; (3) allowed them to explore new avenues of information; (4) and provided tangible results (Crowe et al. 1996).

Ten departments link to the University's home page and a variety of other electronic resources have been published. These include on-line syllabi:

• {http://www.clunet.edu/~schwarz/afrolit.html}
• {http://robles.callutheran.edu/~crowe/edcs.html}
• http://robles.callutheran.edu/~karayan/503.html
• http://robles.callutheran.edu/~karayan/512.html

connected to the course in the on-line catalogues, electronic text books (http://robles.callutheran.edu/~crowe/tofc.html also connected to the catalogues) and most recently the Hedda Gabler page ({http://robles.callutheran.edu/~arndt/Hedda/heddam.html}) complimenting the Drama Department's spring production of that play. (Theater goers could browse, read, and learn before and after the performance and during intermission. The cast also used the page to learn about the play. Any student, faculty, staff, alumni, or cyber-citizen can also review the Hedda Gabler material.)

Since the installation of CLU's home page, we have seen phenomenal changes in the frequency of home page hits. Data from the past three quarters show steady increases in hits to our home page. The Quarter 3 shows dramatic growth since the beginning of t he academic year as noted in Table I.

While the University has only offered CLUnet accounts to currently enrolled students, faculty and staff, the web site has been a means of staying connected or getting re-connected with alumni and friends of the University. Several issues of the CLU Magazine ({http://www.clunet.edu/News_Publications/CLUmagazine/CLUmags.html}) have also been electronically published via our web server. We are also promoting the University's Public Radio station ({http://www.kclu.org/}). Guests from external domains have increased over the past nine months as seen in Figure I.

Home Page Evolution

We have a "Visitor's Center" ({http://ww2.clunet.edu/admission/}) under construction which will contain the Campus Tour, Frequently Asked Questions about CLU and CLUnet, Viewbook, and Cultural Events and Lectures. The "Visitor's Center" will be a promotional site for CLU.

We are also exploring the distribution of some inventory pages and "downloadable CLUnet bookmarks," as potentially useful additions to CLUnet in aiding lost users find there way around our tangled web. Specifically we need to refine where we place new information and how to help visitors find it. For example, soon we will have a student employment opportunity page with sub categories for off-campus, on-camp us, internships, etc. Additional future offerings include: an Alumni Page and Class Schedules (Undergraduate Programs), and we will be updating the Undergraduate Catalog.

The number of pages is growing with many interesting and useful additions that are often getting "lost," only to be found on the "What's New" page. While the site needs to be dynamic, the overall design must be consistent over time to ensure that users can find the information that they have viewed in the past. When an item is placed on the "What's New" page, the development team needs to identify where the item will reside and let the user know where that item will reside after it is not so "new." The task force has not identified the appropriate length of time that things remain on the "What's New" page.

The library software (Data Research Associates) will soon provide library users with account information using a "PIN" which will support on-line holds, individual borrower record, and book renewals. The administrative information system (Datatel) will support student queries for degree completion history and academic performance. We also expect to process change of address and course add/drops over the web server and perhaps offer classes over the net. CLUnet's ultimate success will come with more interactive services for students, faculty and staff. A web developer's job is never done.

References

Attachment A

Internet Task Force Membership

Administration
Michael Adams, Director of Publications
Julius Bianchi, Director of User Services, ISS
Lynda Fulford, Director of Public Information
Mark Lager, Coordinator of Information Resources, ISS
Lucy Rodriguez, Registrar
Allen Scott, Director of Institutional Research
Carole Thompson, Systems Manager, ISS

Attachment B

California Lutheran University Computer Use Policy

Attachment C

Departmental Home Page Policy

• abide by the rules of the CLU Computer Use Policy
• follow the University guidelines for design and interface conventions
• maintain the page (keep it up-to-date)

Departmental pages must use the following interface conventions:

• link to the official catalog information that is maintained by the Publications Office when providing policy, core requirements, course listings, faculty profiles or any other catalog information;
• link to schedule information published by the registrar or publish only after receiving approval from the registrar;
• use the official template and graphics.

Before being electronically connected to the CLU Home Page, Departmental Pages must be reviewed by the Internet Task Force and where appropriate, University Relations Office.

Once linked to the CLU Home Page**, Departmental Pages will be reviewed periodically by the Internet Task Force and University Relations Office to check that the Departmental Page is still in compliance with University policy.

*The University Relations Office/Publications Office is charged with the responsibility of ensuring that all published material, in any form, printed or electronic, accurately presents the University with a high level of professionalism and reflects the Mission of the University with a high level of professionalism and reflects the Mission of the University. The reality is that neither University Relations nor Publications Offices have the human resources to review every document, however those offices s till maintain the authority to edit, rewrite and redesign material that is determined not to conform with University editorial publication standards.

**PROCEDURE: Once approved, Departmental Pages will be placed in a directory on robles where University Publications Staff and the System Administrator(s) have authority to share the Departmental Pages. Departmental staff will submit updated files to University Publications or ISS for posting.

Faculty/Staff Home Pages

• abide by the rules of the CLU Computer Use Policy
• maintain the page (keep it up-to-date)

Faculty/Staff may place home pages in their robles account.

Student Home Pages