Orbis 2  Systems Installation, Implementation and Operations Group  (SIIOG)

Meeting Notes: February 21, 2002


Present: Gail Barnett, Roy Lechich, Ernie Marinko, Fred Martz, Wes Most, Karen Reardon


Agenda: Discuss:

                Operation Standards

                Interim Backup Requirements



                Most of the discussion concerned a review of the proposed Hours of Availablity Operational Standard document.  We felt that the document should cover expectations for both Staff  and Web Voyage, rather than Staff and OPAC.  The OPAC is part of  Web Voyage; the other part is the patron empowerment functions, and we discussed some potentially thorny issues with scenarios involving these functions.  For example, if a patron has been in the middle of placing requests, how does he/she know that  they will be processed during a cutover from production to backup?

                Wes pointed out that since we are not using Unix clustering technology, some manual intervention will most likely be necessary to effect a cutover, and this should be taken into consideration.  Gail brought up the issues of batch loads – we don’t know yet exactly how long they will take.  We also discussed how long keyword index rebuilds might potentially affect downtime.

                This led into a preliminary discussion about announcement and communication requirements in the event of a system problem.  We briefly discussed the question of how it would be communicated to the circulation centers whether or not they should go into offline circulation mode.  If this is to be Systems-driven, then we would need to implement standards and the Workstation Support Group would need to be involved as part of their support charge.


                We discussed the various users who would need direct Oracle access, as opposed to just the Voyager clients.  Besides the Systems Office, the two current reasons for supplying Oracle access are:

-          to use reports.mdb, the Voyager supplied MS-Access database which contains links to the Voyager Oracle tables and a number of “canned” reports.

-          To use Gary Strawn’s Spine Label Printing program, which has been determined to be superior to Voyager’s spine-label printing capabilities.  This is a stand-alone application, written in Visual Basic, which does not depend on any Voyager client software whatsoever; instead it requires a direct connection to the Oracle database via an ODBC Data Source.


Karen asked about the timeline for the formation of the Reports Implementation team, whose charge it will be to evaluate, test, tune, tweak  and implement the “canned” reports supplied by Voyager.


We also decided to extend our meeting time from one hour to one and a half hours.


Action Items and Questions:

1)       Find out when the Report Team will be formed.

2)       Find out to what extent the Systems office will drive the switching of circulation into offline mode, or whether the Circulation groups will handle this, and if so, what they would need from us.