Res 1994-016 - Laserfiche WebLink

Home Browse Search

:>5"8:; (g) All transactions ~rformcd during the test, whether at a monitored or unmonítored workstation, shall be according to the-prescribed transaction logs. No spontaneous transactions will be attempted during the test period by any-ôperator. (h) THE CITY and DYNIX will jointly create and approve all transaction logs prior to the application of the exarmnatlOn. (i) The tinal results will be calculated by THE CITY staff. DYNIX representatives will be allowed to verify the test tindmgs. (j) The full load ~rformance mix transaction logs (terminal functions and transaction ty~s) will be as follows: I. Two (2) terminals ~rforming circulation transactions. 1.1 CHARGE function. These terminals will be scheduled to charge out an average of five (5) Library items ~r minute. Each patron will be borrowing either two (2) or three (3) items. 1.2 RENEWAL function. Transaction logs will be designed to initiate and include one renewal transaction for each 5th patron charging out materials. 1.3 PATRON CARD RENEWAL function. Transaction logs will be designed to initiate a patron card renewal procedure for every 25th patron which charges out materials. IA FINE POSTING transactions. Transaction logs will be designed to initiate a tine posting every 15th- charge transaction. 1.5 HOLD transaction. Transactions will be designed to initiate a hold request every 40th charge transaction. 1.6 CHARGE BLOCK function. Transaction logs will be designed to initiate a block of the charge function . . every 50th charge transactIOn. 2. Two (2) terminals ~rforming circulation discharge transactions. 2.1 DISCHARGE function. The terminals will be scheduled to discharge an average of 15 library materials ~r rmnute. 2.2 OVERDUE posting. Transaction logs will be designed so that every 25th discharge will require the posting of an overdue fine to the patron record. 2.3 FINE PAYMENT function. Transaction logs will be designed where every 30th discharge will post a tine payment to the appropriate records. , J. One terminal ~rforming patron inquiry and registration transactions. 3.1 PATRON REG ISTRA nON function. Transaction logs will be designed where the terminal will ~rfonn 15 patron registrations per hour. 3.2 PATRON INQUIRY function. Transaction logs will be designed where the terminal will ~rform IS patron record inquiries ~r hour which will display patron infonnation, library materials charged out, and tines paid/~nding. 4. Four (4) terminals ~rforming t~hnical services and database maintenance transactions. 4.! BIBLIOGRAPHIC DATABASE INQUIRY function. Transaction logs will be designed where the terminals are ~rforming an average of one (I) bibliographic record inquiry per minute. CITY OF SAN MARCOS - PAGE R-43 January 17, 1994