1992-93 CARL/CSI
MASTER SERVICE AGREEMENT
Prepared By: Rick Forsman Joan Chambers Gail Dow Gary Pitkin Rick Woods
With the Assistance of: Sharon Andersen
Brenda Bailey 1\lan N. Charnes
Gene Damon
October 7, 1992
Colorado Alliance of Research Libraries
.
r
1992-1993 CARL/CSI MASTER SERVICE AGREEMENT
This Master Service Agreement is entered into this day of , 1992 by the Colorado Alliance of Research
~~---Libraries ("CARL") in behalf of libraries that contract for services with CARL and CARL Systems, Inc. ("CSI"). CARL members are defined as Auraria ("Auraria"), University of Colorado at Boulder ("CUB"),
University of Colorado Health Science Center ("CU-HSC") collectively known as The Regents of the University of Colorado, a body corporate ("University of Colorado"), Colorado State University ("CSU"), Denver Public Library ("DPL"), University of Denver ("DU"), Colorado School of Mines ("Mines"), University of Northern Colorado ("UNC"),
University of Wyoming ("UW"), Boulder Public Library ("BPL"), State Board for Community Colleges and Occupational Education ("CCLink"), High Plains Regional Library System ("HPRLS"), Regis University
("Regis"), Pikes Peak Library District ("PPLD") and Colorado State Library ("State Library").
CSI agrees to provide all necessary professional and technical services to CARL to fully maintain the CARL System ("System")
software and to provide on-going system enhancements and upgrades as described in Riders C and H to this Agreement. In addition, CSI will operate the Denver platform located at 3801 E. Florida Ave., Denver, CO 80210 on behalf of CARL as described in Rider B.
The MSA is entered into based on the best information and
understandings available at the time the MSA Task Force met on August 31 and September 1, 1992. Upon identification of unforeseen
factors which might materially affect the MSA, CARL and CSI agree to renegotiate, in a reasonable manner, affected portions of the MSA. General System Requirements: This agreement is based on the following assumptions:
MSA
1. The "System" will adhere to all NISO standards and to all telecommunication protocols and standards (e.g. TCP/IP, X.64, X.25 and OS!) as required by CARL. New standards (e.g. ANSI ACS X.12, Z39.50, Z39.69-199X), as adopted by CARL, will be
implemented by CSI on a timetable established by negotiations between CARL and CSI. CSI will define the resources required to
implement any new standards desired by CARL.
2. Full MARC record is the basis for all Alliance files relating to bibliographic records: the system conforms to all current MARC formats. The "System" accepts OCLC, RLIN, WLN, BNA or any other incoming records that follow USMARC format. Changes to MARC formats, as adopted by CARL, will be implemented on a timetable established by negotiations between CARL and CSI. 3. The "System" contains security protection provided at logon.
4. CSI will provide system-generated printed and/or online reports (e.g. management reports, database use, terminal activity) as previously identified by CARL members or as later standardized by the appropriate CARL committees. (See Rider J) .
5. The "System" provides a range of output products (e.g. labels, purchase orders, extracts, tapes) upon request by CARL members. Any new output products are subject to negotiation between CARL and CSI.
6. CSI will continue to support the existing and currently scheduled additions of multiple branches or satellite locations.
7. On-going PAC support includes Boolean searching and search qualifiers.
8. The "System" provides online help messages and prompts.
9. The "System" performance shall not fall below current levels and:
Full system must be available for library staff and users 98% of the longest library hours of any CARL member.
Maximum 3 second response time for all transactions (e.g. checkout, discharging, checkin, acquisition transactions) except online reindexing of record which may take up to 15 seconds, provided the appropriate hardware is available. CARL member libraries must receive advance notice of major software changes.
10. Major new developments will be subject to formal acceptance by CARL. If a development does not meet specifications, written notice will be given by CARL to CSI. CSI will have 60 days to conform to the specifications upon receiving written notice. A mutually agreed-upon impartial expert may be utilized to decide
if specifications are met . Both parties will be bound by the decision of the outside expert.
MSA
All new and modified major software will be subjected to a test plan which includes Functional Testing, Integration Testing and Regression Testing. Problems shall be reported promptly to the CARL Technical Support Coordinator for evaluation.
CSI, in conjunction with CARL, will define and identify in detail the resources needed to implement a universal test file to support testing. The test file will contain examples to verify that the specifications have been met and that the functions are operational.
11. A new networkwide trouble reporting procedure and logging system will be put into place by CSI by Jan. 1, 1993. This system will allow staff to classify problems according to
severity using the priority system listed below; provide online status of the problem; provide a response to the reporting
library; track, among other things, the response time; and initiate an alarm system for non-response.
The priorities used in the new trouble reporting procedure and logging system are:
"A" Module or function is down, or unavailable, and there is no workaround procedure. E.g.Hardware, software or
network failure and work in the library has stopped. "B" Problem is a serious inconvenience to library staff
and/or patrons; temporary workaround is available. E.g. Software module or an essential datafile is unavailable, such as staff unable to maintain particular range of OCLC records.
"C" Problem is an inconvenience to library staff only; library patrons are not aware of the problem. E.g. Sporadic software failure within a function.
"F" Enhancement or feature request (see section g below) "R" Customized report request (see section g below)
The response requirements are:
a. All problem reports from CARL to CSI must be logged within 1 working day
b. Problems must be assigned to CSI staff and reviewed in the following time frame:
"A" Priority within 24 hours (any day of the week) "B" priority within 5 working days"'"
"C" priority within 30 working days
c. Reporting CARL institution must receive telephone or
written response from CSI according to the following time frame:
"A" priority within 1 working day "B" priority within 5 working days "C" priority within 30 working days "F" priority within 5 working days "R" priority within 5 working days
... working day refers to Monday through Friday, excluding holidays
d. 50% of reported problems must be resolved by CSI or otherwise handled by mutual agreement within 25 working days.
e. Another 25% must be resolved by CSI or otherwise handled by mutual agreement within 60 working days.
f. All problems must be resolved by CSI or otherwise handled by mutual agreement within 120 working days.
g. The trouble reporting procedure and logging system is not intended to handle enhancement or customized report
requests. These types of reports or requests should be sent directly to the appropriate CARL Committee or Task Force. Requests which CSI perceives to be enhancement requests will be give a priority of "F", responded to with an explanation as to why the request received this priority, and forwarded to the appropriate CARL group for consideration as allowed for under Rider F, section 14. Requests which CSI perceives to be customized report requests will be give a priority of "R", responded to with an explanations as to why the request received this priority, and forwarded to the appropriate CARL group for consideration as allowed for under Rider F, section 10. Requests for customized reports and global database changes which do not fall under Rider B, section 2, may be ordered and paid for independent of this document, as agreed upon by CSI and the requesting institution.
The existing TR logs will be reviewed by CSI in conjunction with the reporting CARL library to determine which problems are still current. Migration of old TRLOG entries to the new system will be completed by March 31, 1993.
12. CSI will designate at least one FTE CSI liaison to CARL. CSI will, insofar as possible, maintain continuity of staff
throughout a project.
13. CSI will notify CARL institutions of any scheduled down-time
48 hours in advance and provide a timeline for scheduled installations, new product releases and implementation of modules at member sites.
14. After consultation with CARL members, the CARL Executive Director will meet with CSI on at least a quarterly basis to monitor performance milestones on all major services and enhancements.
Rider A
Specifications For Each Basic Module
Public Access Catalog (PAC)
1. The "System" will comply with all System Documentation Public Access Catalog Release A100.
2. The "System" will provide access by gateway or other means to databases not mounted on the CARL platform. CSI will mount, support, and design generic menus for outside databases in accordance with CARL specifications. Special indexing and
custom screens will be made available on terms to be negotiated by CARL and CSI.
3. CSI will implement the recommendation for Title Re-indexing and regenerate the Title Index as defined in Attachment 4.
4. CSI will implement Name Authority Control as recommended by the CARL Authority Control Task Force.
5. CSI will fix joint author searching problems (e.g. Masters and Johnson as identified in Attachment 8) and expand search
capabilities to improve handling of monster names, allow more efficient joint author searching and provide for search
qualifiers such as date and language.
6. The System will support Boolean searching capabilities. Cataloging and Bibliographic Maintenance
1. The "System" will comply with all System Documentation Bibliographic Maintenance Release A111.
2. CSI will fix all identified loader problems in a timely manner
and in accordance with a timeline developed by CSI and CARL. 3. Implementation of Cataloger's Workstations will be performed by
CSI upon request by a CARL institution in accordance with a timeline developed by CSI and CARL.
4. CSI will resolve any title problems that remain after
completion of reindexing in PAC #3 above. Circulation and Reserves
1. Circulation Release C100 will be stabilized at the University of Colorado, Boulder.
2. CSI will fix and maintain, but not enhance, "OldCirc" and Old
Rider B
Operations of Denver Platform
CSI will operate the Denver platform located at 3801 E. Florida Ave., Denver, CO 80210 on behalf of CARL and the CARL sites located on that platform (Auraria, Colorado State University, University of
Colorado-Boulder, University of Colorado Health Science Center, Denver Public Library, University of Denver, Colorado School of Mines, University of Northern Colorado, University of _Wyoming,
CCLink, Regis University, High Plains Regional Library System and the Colorado State Library) . CSI will respond promptly to all requests connected with its role as system operator.
The following services will be performed by CSI:
1. All data will be backed up on a regular basis and stored off-site.
2. In cooperation with affected member library CSI will identify and restore any lost data resulting from CSI-created
operational problems and use its best efforts in all other cases.
3. CSI will install new ports and terminals as requested by CARL on a schedule mutually agreed upon.
4. CSI will manage disk space and other hardware resources. CSI will advise CARL of additional equipment required with
sufficient lead time to allow for budget considerations. CARL will advise CSI of its members' expansion plans similarly. 5. In consultation with CARL members, CSI will periodically on an
"as needed" basis reindex CARL's database which resides on the Denver platform, but not less frequently than once a year
unless mutually agreed upon.
6. CSI will provide a Technical Support Desk and Off-Hours support as outlined in Attachment 7.
1. CSI will notify CARL sites of any scheduled hardware
maintenance, software developments and releases, proposed software enhancements and other technical information
pertaining to the CARL mainframe or the "System" software as noted on a schedule mutually agreed upon by CARL and CSI.
8. CSI will distribute reports and other batch products in formats and on a schedule mutually agreed upon by CARL and CSI.
9. CSI will operate the computer and telecommunications network in a manner that is consistent with the needs of CARL.
10. CSI will load records (e.g. OCLC), approval tapes, invoices and patron files on a schedule mutually agreed upon by CARL
institutions and CSI.
11. CSI will maintain all CARL menus on an as needed basis.
12. CSI will define and identify in detail the resources needed to implement and maintain a Test Database as described in
Attachment 3.
13. CSI will provide CARL with a current copy of the code for the system and will provide to CARL new versions of the code as they are produced.
Rider C
Priorities for FY93 Fixes and Enhancements
Basic System fixes take precedence over Enhancements. Fix is
understood to mean that CSI corrects reported program bugs to comply with documentation. Enhancements are major system revisions which contain new features in addition to preceding fixes. However, to the extent possible, the following items are intended to be worked on concurrently. The categories of "Acquisitions", "Indexing/
deindexing", "Outstanding Obligations to CARL Members" and
"Circulation" are the top four objectives, in priority order, of the CARL 1992-93 Strategic Plan.
Items identified with an asterisk require no additional CARL involvement. The other items require CARL to develop plans and specifications as noted in Rider F in order for CSI to meet these objectives.
I. Acquisitions: 1. Basic System:
a. Fix known and reported bugs involving ISBN
b. Interface with institution- specific Local Fund Accounting c. Implement Acquisitions module at UW and CSU
2. Enhancements
• a. Version 7.19: Implementation and stabilization of Version 7.19 (currently in draft form) at sites using the
Serials/Acquisitions module.
• b. Change OCLC PRISM load to Acquisitions
c. Develop Vendor Interface with Faxon, EBSCO, BNA, Baker & Taylor, Yankee
d. When required, implement X.12 Standard (see Attachment 1: CSU Memo from Pat Smith and Carmel Bush to Gail Dow
regarding X12)
II. Indexing/Deindexing 1. Basic System:
a. Fix "Hanging Titles" of all sorts and remove all occurrences from the catalogs
• b. Implement Title Indexing (see Attachment 4: CARL
Bibliographic Issues Committee Recommendations for the Title Indexes, Aug. 15, 1991) and regenerate title indexes
III. Outstanding Obligations to CARL Members 1. Basic System:
*a. Make substantial progress in fulfilling outstanding obligations to CARL members (per Rider H)
*b. Clean up existing TR Log: Eliminate those problems already solved. In conjunction with reporting institution,
identify those problems that still need to be solved and those that are no longer valid.
c. Fix "Can't Locate Bib Record" problems.
d. Implement Name Authority Control as described in the Authority Control Task Force specifications
* e. Fix Loaders: A schedule will be issued for the timely fix of all currently reported loader problems.
f. Marcive Integration: (1) Load Marcive
(2) Extract and link to local holdings
(3) Integrate post 1986 GPO records g. Mag stripe reader connection for DU and UW
* h. Generation and timely distribution of all generic reports (as identified in Rider J) and other routine print
products produced on a scheduled basis as identified in the current documentation or mutually agreed upon by CSI and requesting institution.
2. Enhancements:
a. Management Reports to be defined by appropriate CARL committees
IV. Circulation 1. Basic:
* a. Stabilize (bring into line with documentation) Version C100
* b. Convert DPL, HPRLS, CSU, CCLink and DU Law (?) to Version C100
• c. Complete Reserves Module (see Attachment 6:July 31, 1992 Spec i f i cat i on s)
2. Enhancements
V. PAC
a. Global Security design to provide local site control of matrix driven pass wording, along the lines recommended in the July 16, 1992 Memo from Security Task Force to CARL Circulation Users Group (Attachment 2).
1. Enhancements
- a. Enhanced searching for PAC including Boolean and search qualifiers (e.g. dates). Enhanced searching should also be available for the UnCover database (see Attachment 8). b. On-line help screens in modules other than PAC. (See Attachment 9).
Rider D
Fee, Payment Schedule and Contract Milestones
Facilities Management Fee
The Facilities Management Fee is the amount that CARL pays to CSI for direct services and is intended specifically to reimburse CSI for staff costs associated with operating the Denver platform and for maintenance and enhancement of "The CARL System." The amount budgeted for 1992-93 is $536,000.
Payment Schedule
It is agreed that CARL will reimburse CSI for the three months of 1992-93 during which no MSA was in effect ($134,000). The
libraries that have chosen to withhold 27% of the assessment to pay on a monthly performance basis (CUB, Auraria, CU-HSC, CSU and UNC) will be billed for July, August and September. Subsequent payments will be made on a monthly basis as CSI successfully
implements the major projects identified in the "Contract
Milestones" which follows. The monthly payment upon satisfactory performance is $44,666. Failure to reach contract milestones will
reduce each month's amount by $30,000.
Contract Milestones
See Attachment 9 for details.
9/30/92: Cataloger's Workstation (install
&
train) -CUB Re-run missing record report - DUNew GENPO - UNC
10/1/92: Print label function - Auraria Patron Purge - DU
Improve Print Label function - UNC
10/15/92: PAC display note table- CU Law Major Microform load - DU Law Set up news file - HPRLS
Major Microform load (Early English Books) -CUB
10/30/92: Major Microform load- Auraria
Release of Acquisitions version 7.19
10/31/92: Conversion to C100 Circulation - Red Rocks Comm.College Conversion to C100 Circulation - Pikes Peak Comm.College Major Microform load (Music Pop) if data received by
10/16/92 - CUB
11/1/92: Revise PRISM download software to handle order creation
11/15/92: "C i rc" Fi seals successfu 11 y imp 1 emen ted - CUB
Successful Patron Tape Load (assuming receipt of tape by 11/1/92) -CUB
Shipment of records to authority control pre-processing vendor
11/16/92: Schedule for the fix of all currently requested loader problems complete
11/30/92: Complete Marcive data load to new reference file
12/1/92: Implementation schedule for Authority Control completed EBSCO Tape Load - Auraria
1/1/93: Design and computer requirements for Title index complete
Conversion to C100 Circulation - DPL Serlev3 Loader - DU
Magnetic Stripe Reader connection - DU Fix "Circ" - CUB
1/15/93: Test database for new titles index available
Extract and load of OCLC government documents records from existing documents reference file complete Local documents data extract available for test site
(Marcive)
1/30/93: Re-index - CUHSC
2/1/93: Dial-up user last activity date logging - DPL
3/1/93: Ability to extract Conser records - CCLink
3/15/93: First site title re-index started
3/30/93: Prototype authority test files operational
3/31/93: TRLOG implemented as specified in section 11 of this document
4/1/93: ANSI ASC X.12 with Faxon if Faxon ready
4/15/93: Title re-indexing schedule for all sites complete
4/30/93: Release Acquisitions Version 7.19 for test - CSU
5/30/93: University fund accounting interface - CSU
6/30/93: Implement Name Authorities
MSA-Rider D
Complete development of Reserves Module (Attachment 6) "NewCirc" operable - CSU
Implementation of Acquisitions Module - UW
Rider E
Training and Documentation
1. CSI will provide training sessions on any new module or upgrade. The training will be provided to a limited number of staff at each CARL institution who will act as trainers for other members of their institution.
a. Training for new versions and releases will be given at CSI headquarters.
b. When a new module or service is introduced or an upgrade is deemed sufficiently different from its predecessor by CSI, training will be provided on-site to CARL institutions. 2. CSI will provide complete written User Documentation for each
module and upgrade.
3. CSI will inform all CARL institutions of scheduled releases and training sessions with sufficient lead time to allow the
institutions to schedule training meeting times and space where appropriate.
a. Written User Documentation will be distributed 6-8 weeks prior to scheduled release of the upgrade or module.
b. Training by CSI will occur 3-4 weeks prior to release of the upgrade or module.
4. Additional training will be available to CARL at a price schedule to be provided by CSI.
Rider F
CARL Responsibilities
These are responsibilities for CARL as an Alliance. Additional site-specific responsibilities may be required.
1. CARL will plan for port/terminal additions on a quarterly basis, advise CSI of expansion plans and negotiate an installation
schedule with CSI.
2. Upon timely notification by CSI, CARL will upgrade hardware as needed to accommodate CARL projects and daily operations without degrading the system.
3. The appropriate CARL committee will define a universal test file to support testing. The test file will contain examples which will verify if specifications have been met and if the functions being tested are operational.
4. CARL will outline an installation plan for Authority Control
including pre-processing. CARL will fulfill the Authority Control responsibilities defined in the Sept. 25, 1992 Authority Control Task Force Report (Attachment 5).
5. CARL will plan for the implementation of Cataloger's Workstations and work with CSI to develop a schedule for that implementation. 6. CARL will plan a schedule for the conversion of remaining sites to
Circulation Release C100.
7. CARL will schedule Magnetic Card conversions at all appropriate sites.
8. CARL will schedule PRISM installations.
9. CARL institution staff members will identify problems and report them to CSI only after following the procedures outlined in the current Procedures for After Hours Support announcement
(Attachment 7).
10. An appropriate CARL committee or task force will identify the
necessary list of generic management reports and develop a process for requesting and approving any additional or customized reports. 11. CARL institutions will provide In-house training for their
respective staff. Additional training over that provided for in Rider E will be available from CSI at an additional cost.
12. CARL will employ a Technical Support Coordinator.
13. An appropriate CARL committee or task force will define global security needs as suggested in Attachment 2.
14. CARL will define a process for prioritizing suggested enhancements to be developed by CSI.
15. CARL sites will provide specifications for local Fund Accounting interfaces.
16. CARL will identify the vendors for which an interface needs to be developed.
17. The appropriate CARL committee or task force will define the Marcive integration specifications and implementation plan. 18. The appropriate CARL committee or task force will define the
desired on-line HELP screens.
19. The appropriate CARL committee or task force will define desired implementation plan for authority module.
Rider G Clarifications
1. CARL and CSI will review the terms of this agreement at least monthly to effect any changes mutually agreed upon.
2. Any sub-agreements, schedule changes or other mutually agreed-upon alterations will be documented in writing, added to this Agreement under this Rider G, and distributed to all CARL members.
Rider H
SITE SPECIFIC TASKS A. AURARIA
Patron Loader
Major Microform Load EBSCO Tape Load
Print label function New GENPO
B. COLORADO STATE UNIVERSITY OCLC loaders
Acquisitions implementation
University fund accounting interface Conversion to NewCirc
PRISM download implementation See Rider I (when ready)
C. DENVER PUBLIC LIBRARY Conversion to NewCirc
Special services for branch closings/re-openings
Dial-up user last activity date logging
D. UNIVERSITY OF COLORADO AT BOULDER Major Microform load
Cataloger's Workstation (install and train) Patron loader In test Oct. 30, 1992 Dec. 1, 1992 Oct. 1, 1992 Awaiting June 30, June 30, June 30, Awaiting specification 1993 1993 1993
OCLC loader specs
Jan. 1, 1993 On-going Feb. 1, 1993 Oct. 1, 1992 Sept . 30, 1992 In test
E. UNIVERSITY OF COLORADO HEALTH SCIENCES CENTER Re-index
Conversion of new hospitals Cataloger's Workstation
(install and train)
F. UNIVERSITY OF COLORADO LAW Patron loader
PAC display not table
PRISM (specification, test and implement)
Cataloger's Workstation (install and train)
MSA-Rider H Page 19
Jan . 30, 19 9 3
(pending grant approval) To be scheduled Awaiting specifications Oct. 15, 1992 To be scheduled To be scheduled October 11., 1992
G. UNIVERSITY OF DENVER Patron loader
Serlev3 loader
Re-run missing record report Mag strip reader connection Cataloger's Workstation
(install and train) Patron purge
H. UNIVERSITY OF DENVER LAW LIBRARY Patron loader
Conversion of NewCirc Major microform load
I. UNIVERSITY OF NORTHERN COLORADO New GENPO
Improve print label function J. UNIVERSITY OF WYOMING
Acquisitions implementation K. CCLINK
Ability to extract Conser records (subject to decision to retain
the Conser database)
Conversion to new circulation Arapahoe Front Range Red Rocks Pikes Peak Others L. HIGH PLAINS Conversion to NewCirc Estes Park Fort Morgan Sterling
Set up news file M. REGIS UNIVERSITY
Clean-up from Teikyo extract Conversion to NewCirc
MSA-Rider H Page 20
Awaiting test tape Jan. 1, 1993
Sept . 30, 1992 Jan. 1, 1993 To be scheduled Oct. 1, 1992
Awaiting test tape To be scheduled Oct. 15, 1992 Sept. 30, 1992 Oct. 1, 1992 June 30, 1993 Mar. 1, 1993 Completed In test Oct. 31, 1992 Oct. 31, 1992 To be scheduled To be scheduled In test In test Oct . 15 , 19 9 2 To be scheduled To be scheduled October 1, 1992
N. STATE DEPARTMENT OF EDUCTION
~ctivate claims for serials control To be scheduled Restore all remaining fixed fields
for state publications database Provide printout of all DDB (state
publications) records from database #83
0. BOULDER PUBLIC LIBRARY Conversion to NewCirc Software up-grade
Shared cataloging between databases P. PPLD
Local PAC screens
Circulation backup on mainframe Inventory program
To be scheduled To be scheduled
With software up-grade
In test
To be specified To be specified
MSA-Rider H Page 21 October 1., 1992
--Rider I
Rider J
Reports
Statistical reports are produced regularly as often as the library needs, and contain figures on charge outs, returns, traces, claims returns, renewals, conversions, temporary conversions written and holdings records deleted by branch since the last Cleanup. For institutions using the Reserve module, counts of reserve charge outs, renewals, and returns are given. The statistics can be bro-ken down by branch where the activity occurred and can be given tor month to date and year to date as well.
Cleanup also produces an institutional snapshot, giving a cumulative count of each type of Circula-tion transacCircula-tion in that institution's file after the cleanup run was completed.
Reports for staff use may include tracer or claims return search lists, hold shelf expired lists, and statistical reports.
Month end reports include: Borrower by borrower type Circulation by borrower type
Circulation by media code, broken into branches Circulation by location code, broken into branches Circulation by call number, broken into branches
Reports not associated with Cleanup can be customized for a library's needs. Some other reports available include:
Borrowers List: Runs against the User file, and includes name, user 10, status, borrower type, date of last action, date registered, date of expiration, and address (both primary and secondary if selected). Sorting "All" sorts alphabetically by name either for the whole file or within borrower type; sorting "Selected borrower type• sorts alphabetically by name within each borrower type. The institution also has the option to include the borrower notes field, and may select hard blocked, soft blocked, or all borrowers for the report.
All Problem Borrowers: Runs against the Transactions file, and selects patrons with a fine, over-due or lost item. Includes name, user 10, status, borrower type, address, call number, title, item number, dates, fine amount, and item status with the total number of items and the dollar amount
---.. ·--- ----··---
-
-
--
-
•....--owed. The report is sorted alphabetically by name, and can be limited to transactions older than a selected date. Can list all fines, overdues and lost items or only lost items, only overdues or only fines.
Problem Borrowers-Selected Borrower Type: Runs against the User file and selects patrons of the selected borrower types with fines, overdue or lost items. Includes name, user 10, status, borrower type, address, call number, title, item number, dates, fine amount, and item status with the total number of items and the dollar amount owed. Sorting "All" sorts alphabetically by name either for the whole file or within borrower type; sorting "Selected borrower type" sorts alphabeti-cally by name within each borrower type. The report can be limited to transactions older than a selected date. Can list all fines, overdues and lost items or only lost items, only overdues or only fines. Up to ten valid borrower types may be selected.
Borrower's Transactions-Selected Borrower Type: Runs against the User file and lists all transactions for patrons in the selected borrower types. Includes name, user ID, status, borrower type, address, call number, title, item number, dates, fine amount, and item status with the total number of items and the dollar amount owed. Sorting wAll" sorts alphabetically by name either for the whole file or within borrower type; sorting "Selected borrower type" sorts alphabetically by name within each borrower type. The report can be limited to transactions older than a selected date. Up to ten valid borrower types may be selected.
Tracers, Claims Returned, or Lost List: Runs against theTransactions file and selects tracers, claims returns, or lost items. Includes information on branch, location, call number, item number, dates of transaction, author, title, and borrower name and ID number. The report can be limited to transactions older than a selected date and can clear tracers.
Count of Titles by Branch: Runs against the Display file and counts only monographs with per-manent records. Includes information on branch and number of titles and is sorted alphabetically by branch.
Titles by Branch and/or Location: Runs against the Holdings file and includes information on branch, location, call number, author or item number and title. The report can be sorted by branch, within branch by location, within location by call number, or by title.
Temporary Records and ltemless Bibliographic Records by Call Number: Runs against the Display file and selects either temporary records or records that have no Holdings records attached. Includes call number, author and title, and indicates whether there are temporary records or records with no holdings attached. The program sorts by call number order and can be limited to a call number range.
Temporary Items by Branch: Runs against the Display file and selects temporary records. Includes call number, item number, branch, location, temporary status, date of status and notes, and sorts by call number order.
Listing of Titles-Selected Words: Runs against the Words file. Looks for items with a match on all words supplied. The report includes information on author, title, and call number, and is sorted alphabetically by title. Can check three valid words from the WORDS file, for one branch and up to two locations.
Hold Shelf List: Runs against the Transactions file and looks for transactions with outstanding holds. The report includes branch, location, call number, item number, dates of transaction, author, and title, and sorts by branch, within branch by location, and within location by call number. Can report for one branch or all and can order by branch or by call number over all branches. Parameters: Runs through the institution's parameter file and includes parameter type, meaning and code. The program sorts by parameter type, and can select one institution and parameter type at a time.
Conversion Lists: Provides a list of temporary conversions created at the institution since the last
run. Includes the di$.P.Jay_level_~a_1Ln_l,l_mt?.~t;>ranch and locatim\ __ the __ tu;>ldil]g_s level calL number.
branch and location, and the author and title. Can exclude temporary conversions done strictly for Reserve.
Reserve Lists: Lists items on reserve at the institution. Lists are organized by professor name or by course name and can be separated by branch. The elements of the Reserve holdings record to be printed may be specified according to media type.
Fiscal Tapes and Reports: Reports or tapes of outstanding fines, lost book charges. Can report credits or payments to be sent to the institution's outside collection agency.
MSA-Rider
J Page 24Rider K
FY94 MSA OBJECTIVES
1. Budget: Databases (Subscriptions and Implications, eg. hardware) 2. Assessment Strategy
3. Written Disaster Recovery Program
4. Authority Control-Subject, Uniform Titles, etc. 5. Series Title Re-indexing
6. Magnetic Card Reader-Wyoming 7. Withdraw "OldCirc" 8. Implement "NewCirc": DU Wyoming Mines PPLD (?) BPL (?) 9. Bindery 10. e-Mail ILL State Library Regis
11. Prioritize Phased Re-Write
12. Maintenance of Old Versions if libraries do not wish to implement new version.
13. Functionality for all MARC Formats in UnCover
14. Levels of security: authorized functions across modules at logon and configurable by institution
15. Search qualifiers, same searching capabilities possible in all databases
16. Electronic submission of problem reports to be viewed by other
CARL members
17. Linking owners to UnCover record.
18. In Rider B, elaborate on how print products should be handled,
including error procedures
19. Additions of Special Collection databases to PAC menu
