Note--the following list is from the OPAC Task Force Final Report and has been amended to contain the results of a preliminary meeting to draft "drop dead" requirements for the current infostation effort.   The assumptions for this
project are that we will begin by replacing the OPAC terminals at BML and MCL with Pentiums running Netscape.  There are 15 terminals at BML and 6 at MCL which will be replaced in time for fall quarter.
--Earl 4/9/97

Note--the following has been further amended to evaluate which "drop dead" and other objectives have not been meet as of October 1997.  I also added numbers to the requirement sections, and added a title to the section about not necessary and not permitted functions.
--Brian 10/30/97

FUNCTIONAL REQUIREMENTS

Functional requirements include those pertaining to USING the infostations; EXTRACTING information for one's use from a variety of sources; VIEWING and, in some cases, LISTENING to resources retrieved; SYSTEM management features, and ADMINISTRATIVE/ENVIRONMENTAL considerations.  Essential and desirable requirements for each of these categories follow.

I. USING infostations

GOAL: Equipment that can be used without staff intervention to access all UCSD's networked information sources

ESSENTIAL REQUIREMENTS:

DROP DEAD--Pentiums with Netscape and best plugins, helpers and other software that we can find.  Context specific help is VERY desirable--need programming done so public service staff can provide content over time.

DESIRABLE FEATURES:

EVALUATION:

There is on-line help that is available for various specific contexts -- and in that regard it is "context specific." However, the help system invocation is not "context sensitive" -- it always opens to the same place, and the patron has to navigate to the specific help section they need.  If "context specific" really means "context sensitive," then we should evaluate how high a priority this is in relation to other current objectives such as CD-ROM integration.

Staff intervention not required but suggested, since the Interface will not launch because of security measures taken to meet requirements in V. and VII (explained below).

II. EXTRACTING information

GOAL: Ability to capture information for downloading to disk, sending on email, or easy, quick, inexpensive, high-quality continuous printing
 
ESSENTIAL REQUIREMENTS: DROP DEAD--Email using mailto and mail document (disable mail and news readers); printing to directly connected local printers supplied by Copier Services; simplified printing from browser and telnet clients; downloading to disk VERY desirable. [May need some way to warn users of the number of pages they are about to print because of the potential cost.]

DESIRABLE FEATURES:

EVALUATION:

Some issues still exist with printing.  The printing from the browser and telnet has in no way been simplified.  No warning exists for patrons about the number of pages or the cost of the print job.  Remote printing to ACS accounts should be possible, but has not been implemented.  Remote printing to user's own workstation has not been investigated.

III. VIEWING resources retrieved

GOAL: Ability to view full-page color display that may include roman and non-roman scripts, musical or scientific notations

     ESSENTIAL REQUIREMENTS:

DROP DEAD--View text in browser or helper window; 17" monitors if at all possible (15" minimum); display multiple character sets and scientific notation; display large-size print as user option; provide multimedia capabilities with PC sound only (no speakers) and headphone jacks (see below).

     DESIRABLE FEATURES:

EVALUATION:

No special consideration has been made to allow the display of alternate character sets.  Some facility for this is built into Netscape and Adobe Acrobat.  This has not been a problem up to this point, but will become an issue when deployed in libraries where foreign language research is more common.

No special consideration has been made for disabled patrons.  Netscape has the ability to adjust font size.

IV. LISTENING to resources retrieved

GOAL: Ability to listen to resources without disturbing others

ESSENTIAL REQUIREMENT:

DROP DEAD--Basic sound with headphone jacks and PC speaker but not
external speakers.

     DESIRABLE FEATURES:

EVALUATION:

The headphone jack is on the back of the machine.  Patch cords need purchased so that patron reach the headphone jack.

V. SYSTEM management features

     GOAL: Easily maintained workstations with system integrity and security

     ESSENTIAL REQUIREMENTS:

DROP DEAD--Centralized server-based management; auto-booting and auto-reset; default to full-screen or large window for telnet helpers; lock-down and security for hardware, cables, peripherals and internal parts (memory, etc.); provide access for departmental tech support; tamper-proof software and automatic housecleaning; timely updates of features and functions as required by libraries.

EVALUATION:

Telnet does not default to full screen because full screen is a 17" monitor.

A remote distribution system still needs to integrated into the system (PC-RDIST).  This will meet the requirements of automatic housecleaning and timely updates of software.

The InfoStations automatically reboot once a day or once every other day depending on location.  They do not currently automatically log in or automatically launch the interface.
 

VI. ADMINISTRATION/ENVIRONMENT considerations

GOAL: To provide flexibility for all users and functions, depending on the needs of  individual locations

     ESSENTIAL REQUIREMENTS:

DROP DEAD--Tiered access (not for BML/MCL but probably for other libraries) including time out and limits to functions; display large characters at users option.

EVALUATION:

This requirement was excluded from the initial deployment phase.  BML is using terminal OPACs for express access.  Term of use tiers are as much a social issue as technical one.  'Ability to operate functions on more than one major platform' is unclear.  What does platform mean in this context?

VII. Not necessary and not permitted functions

In its deliberations, the Task Force also considered the following functions and decided they were not necessary for the infostations and, for those in the second list below, should not be permitted:
 
NOT NECESSARY:
  1. Ability to communicate from workstation via voice (e.g. voice email)
  2. Access to dial-up BBS or other information resources
  3. CD-ROM drives (Infostations should provide access to networked CD-ROMs, but capability for using CD-ROMs that are not networked should be provided at other library workstations rather than the infostations)
 INFOSTATIONS SHOULD NOT:
  1. allow a user to manipulate information, for example by using word processing or database software, except for purposes of copying and pasting results or sending retrievals to a remote printer
  2. allow a user to work on personal email, except for emailing results of a retrieval
  3. allow a user to exit the main system interface
  4. allow a user to remove or move applications
  5. allow a user to install or launch unauthorized applications
  6. allow someone to remove hardware
  7. allow a user to disturb others with audio or visual retrievals
  8. allow excessively long sessions (length to be determined)
DROP DEAD--All of the above within the limits of the technology; Infostations will not access the CD ROM network.
 
EVALUATION:

There is no word processor.  A patron can invoke Netscape Composer right now.

Users can telnet to any site, and work on email if they are a pine, elm, or unix mail user.  Many web sites offer access to email.  This is a policy issue as much as a technical one.

Users can exit from the interface, but it is easy to start back up.

The method that is being used now to prevent the launch of unauthorized applications requires that the desktop be hidden.  A side effect of this is that this also disables the ability of the interface to auto launch.

No technical method is in place to disallow excessively long sessions.