ICS Task Force - Joint meeting with the Pharos Management Team
Dec 1, 2000

Notes from Gail Cosmo

Demo of basic ILL transactions using the RSS module of Pharos
 

Questions and Comments from the Management Team:

1. Where does the request go if there are no RSS holdings in the Union List? -Can go directly to OCLC Review (messaging) file
2. It is recommended to set public library browsers to have ‘no right mouse click’ capability.
3. Need capability of masking SSN numbers
4. Need to mask patron details on pick sheet to lending library
5. Need to have default profiles on each campus server
6. There should be local priority for a book, even after it is on the pick list and checked out
7. Need ability to scan by barcode. (epixtech is working on this)
8. Ability to send directly to Infotrieve
9. COLD policies are already in place
10. Recommend standardized language and operations
11. Start with simple transactions then expand
12. Possibly begin with a Northern California and a Southern California region for testing

• The ICS Task Force recommends proceeding with the pilot testing—see statement.
• The ICS task force would like to have a product designed specifically for the CSU.
• Link+ is a working example of user-friendly features in a resource-sharing program.
• The Pharos objective is to route users searches through the online CSU union catalog.
• By involving additional pilot test sites will create a more accurate measure of workflow, a larger group of experts, and a better way to test the bugs, especially between the different OPACs.
• Set up will be complicated with the number of Pharos servers, ISO, RPAs, WebPACs, AutoFind, Z39.50, etc. for each campus for the interoperability.
• Some libraries (CFI) may choose to route Pharos requests through the CLIO ILL management system.
• Some libraries may adapt the Pharos request form as their online ILL request form.

a)     Have a master list/spread sheet/documentation for: set up configurations; required defaults; tracking all elements; recommendations for
        customizing defaults and testing. Would be nice to have a file copy to download on each server.

b)    Profile standardized defaults for each campus.

c)    Provide upgrades and configuration of the new RSS software on all pilot sites. (By epixtech?)

d)    Provide a list of Systems people contacts for Marvin from each campus.

e)    Include the different OPAC sites in the testing: CFS/Geac, CHU/Endeavor, CARL, etc.

f)    Desirable to have statistical package; a requirement prior to statewide implementation.

g)    Have major bugs completely worked out.

h)    Have Marvin or ‘team’ make visit to all pilot campus sites.

i)    Need preliminary training.

j)    Have a user group FAQ and fact finding element, perhaps through a listserv

k)    Have the CSU hire staffing to oversee, install, train, and test the product.

• Would like to brainstorm with key people of RSS and talk about options.
• Will not be simple to set up program, but helpful to have similar defaults across campuses.
• CSU needs documentation from epixtech

ICS Task Force Recommendation to the PHAROS management Team