Library Software

The Vendor is required to provide pc-based library automation system with the expectation that the new system will be able to:
• Federated or integrated searching, using a familiar internet type visual interface which allows single inquiry of subscription databases, internet, and library catalog.
• As well as provide 24/7 access to the online public access catalog.
• Will use system wide inventory data to locate and share resources and route interlibrary loan requests through the automation system.
• It will be necessary for each library’s collection, circulation and patron information to be stored in a single database that is accessible from each library.
• Will utilize a centralized system to provide access to marc records so when a new title comes in, the bibliographic information gets entered correctly and only once.
• Will combine data to create useful reports for grant purposes as well as state and federal reporting requirements.
• Has the technological life span of at least ten (10) years, be able to operate in a MS server network environment, be able to operate on multiple pc architectures, and be readily expandable to meet increased needs as events dictate.
• The bps library system is open to systems accessed and maintained remotely by vendors.
• User friendly to the average trained library staff member and easily explainable to the average library patron.
• Some form of local back-up circulation system in case of network breakdown.
• System security through hierarchical levels of access and provide a stable “firewall” to prevent unwanted system intrusion.
• Integrate with security systems available on the market.
- Courseware management system requirements
1. Circulation subsystem should provide:
• Rapid response with minimum errors in potentially crowded bandwidth situations
• Search all bibliographic records using the standard parameters of author, title subject, call number and barcode number
• Accurately retrieve and modify patron records
• Accurate maintenance on material and patron status and rapid resolution of problems
2. Public access catalog should provide:
• A search hierarchy to allow searches first at the host location and then expandable to the entire system
• A user-friendly search access by author, title, key words, subject, call number and series with the ability to easily use search techniques
• Create search reports and print bibliographic information (author, subject, call number) with holdings and book status clearly displayed on demand.
3. Cataloging subsystem should provide:
• A ready interface with standard bibliographic utilities such as marc 21, OCLC, aacr2 and be upgradeable to RDA (resource description and access)
• The means to produce barcode labels for each processed copy either individually or as a batch process.
• The means to accurately maintain subject, author, and title authority files, and to provide algorithms to produce additional authority files as determined.
4. Acquisition subsystem should provide:
• Seamless interface with the main bibliographic record database
• Ability to produce selection lists.