South Dakota Library Network: Request for Proposal, February 2012
South Dakota Library Network
Request for Proposals
for an
Integrated Consortial Network Library Management System
February 2012
1
South Dakota Library Network: Request for Proposal, February 2012
Contents
1.
2.
3.
4.
5.
6.
Introduction .......................................................................................................................................... 5
1.1.
Purpose ......................................................................................................................................... 5
1.2.
Definitions ..................................................................................................................................... 5
RFP Schedule & Proposal Instructions .................................................................................................. 5
2.1.
Schedule ........................................................................................................................................ 5
2.2.
Letter of Intent to Propose ........................................................................................................... 5
2.3.
Proposal Transmittal ..................................................................................................................... 6
2.4.
Content and format of vendor response ...................................................................................... 6
2.5.
RFP Process Conditions ................................................................................................................. 7
Selection Process .................................................................................................................................. 7
3.1.
RFP Evaluation............................................................................................................................... 7
3.2.
Vendor Presentations ................................................................................................................... 8
3.3.
Preferred Vendor or Vendors ....................................................................................................... 8
3.4.
Award of Contract. ........................................................................................................................ 8
Background Information ....................................................................................................................... 8
4.1.
Organization Overview ................................................................................................................. 8
4.2.
Current Systems and Operational Environments ......................................................................... 9
4.3.
Goals of the Project..................................................................................................................... 10
Vendor Information ............................................................................................................................ 10
5.1.
Background. ................................................................................................................................ 10
5.2.
Experience ................................................................................................................................... 11
5.3.
Products and Customers ............................................................................................................. 11
5.4.
Vendor Contacts.......................................................................................................................... 13
5.5.
Training ....................................................................................................................................... 13
5.6.
Documentation ........................................................................................................................... 13
Technical Specifications ...................................................................................................................... 14
6.1.
Network ...................................................................................................................................... 14
6.2.
Software ...................................................................................................................................... 14
6.3.
Database ..................................................................................................................................... 15
6.4.
Storage ........................................................................................................................................ 15
6.5.
Back-up and Archiving................................................................................................................. 15
2
South Dakota Library Network: Request for Proposal, February 2012
6.6.
Hosting Environment. ................................................................................................................. 16
6.7.
Servers......................................................................................................................................... 16
6.8.
Upgrade and Maintenance Process ............................................................................................ 17
6.9.
Client/Staff Interface................................................................................................................... 18
6.10.
Security ................................................................................................................................... 18
6.11.
Authentication and Authorization .......................................................................................... 19
6.12.
Presentation ............................................................................................................................ 19
6.13.
Report Writing ........................................................................................................................ 20
6.14.
Performance............................................................................................................................ 21
6.15.
Acceptance tests ..................................................................................................................... 21
7.
Subsystem Specifications .................................................................................................................... 22
7.1.
Online Public Access Catalog ...................................................................................................... 22
7.2.
Cataloging and Authority Control ............................................................................................... 25
7.3.
Acquisitions and Serials Control.................................................................................................. 28
7.4.
Circulation ................................................................................................................................... 30
7.5.
Media Booking ............................................................................................................................ 34
7.6.
Course Reserves .......................................................................................................................... 34
7.7.
Interlibrary Loan (ILL). ................................................................................................................. 34
7.8.
Inventory ..................................................................................................................................... 36
8.
System Migration and Implementation .............................................................................................. 36
8.1.
Installation and Migration........................................................................................................... 36
8.2.
Customization ............................................................................................................................. 39
8.3.
Licensing ...................................................................................................................................... 39
9.
Post-implementation. ......................................................................................................................... 39
9.1.
Support and Maintenance .......................................................................................................... 39
9.2.
Training ....................................................................................................................................... 40
9.3.
Upgrades ..................................................................................................................................... 40
9.4.
Problem Resolution..................................................................................................................... 40
10.
Financial Quote ............................................................................................................................... 41
11.
Terms and Conditions ..................................................................................................................... 41
Appendix A: SDLN Current System and Operational Environment ............................................................ 46
Appendix B: Siouxland Libraries Current System and Operational Environment ....................................... 47
3
South Dakota Library Network: Request for Proposal, February 2012
Appendix C: Rapid City Public Library Current System Information and Operational Environment ......... 48
Appendix E: SDLN Mission and Vision......................................................................................................... 53
Appendix F: SDLN Member Libraries ......................................................................................................... 54
4
South Dakota Library Network: Request for Proposal, February 2012
1. Introduction
1.1. Purpose
The purpose of this Request for Proposal (RFP) and the subsequent vendor
demonstrations is to identify and select a vendor or vendors with whom the South
Dakota Board of Regents on behalf of the South Dakota Library Network (SDLN) will
negotiate a contract to supply, install and subsequently support an integrated library
management system. This system must be capable of supporting an online public
access catalog, cataloging, circulation, acquisitions, serials, reporting and interlibrary
loan. The system must support the functional needs of the different types and sizes of
member libraries, academic, public, school (K-12), and special libraries.
1.2. Definitions
Full member library (SDLN): A full member library has access to all functional modules of
the ExLibris Aleph ILS, electronic database resources, and all other services provided by
SDLN. Each member library has a voting representative on the SDLN Advisory Council.
Remote member library (SDLN): A remote member library has access to the interlibrary
loan module of ExLibris Aleph ILS in addition to the electronic database resources and all
other services provided by SDLN.
2. RFP Schedule & Proposal Instructions
2.1. Schedule
The RFP process will move forward as follows:
Letter of intent to propose is due Mar. 8, 2012
Proposal is due Mar. 23, 2012
Review of proposals is complete Apr. 30, 2012
The following dates will be set pending a favorable outcome of proposal process:
Presentations by selected vendors
Completion of vendor negotiations
Contract signed
Migration schedule
2.2. Letter of Intent to Propose
A letter of intent to propose must be received by the SDLN Library Network Executive
5
South Dakota Library Network: Request for Proposal, February 2012
Committee by 5:00 PM CST, Mar. 8, 2012. Letters must be sent to the following
address:
Warren Wilson, SDLN Operations Director
wwilson@sdln.net
Additionally, a print copy of the letter may be sent to:
Warren Wilson, SDLN Operations Director
South Dakota Library Network
1200 University Street, Unit 9672
Spearfish, SD 57799
2.3. Proposal Transmittal
Proposals must be received by the SDLN Executive Committee’s designated
representative no later than 5:00 PM CST, Mar. 23, 2012. Late proposals will not be
accepted, and will be returned unopened to the vendor. Proposals must be sent to:
Warren Wilson, SDLN Operations Director
wwilson@sdln.net
Additionally, a print copy of the proposal must be sent to:
Warren Wilson, SDLN Operations Director
South Dakota Library Network
1200 University Street, Unit 9672
Spearfish, SD 57799
Once submitted, proposals may be withdrawn from consideration by the vendor at any
point prior to the specified proposal due date.
2.4. Content and format of vendor response
Vendors MUST supply the following information:
2.4.1. Affirmative action certification of compliance
2.4.2. Certificate of insurance
2.4.3. South Dakota tax ID number
2.4.4. Affidavit of non-collusion
2.4.5. Whom to contact with questions
6
South Dakota Library Network: Request for Proposal, February 2012
2.5. RFP Process Conditions
2.5.1. The SD Board of Regents on behalf of SDLN reserves the right to make awards for
services to more than one vendor.
2.5.2. Intellectual property, ownership, and copyright. Information provided
confidentially by vendors to SDLN shall remain confidential. If labeled as
confidential in the vendor’s submitted proposal, such information shall not be
disclosed by employees of member institutions of SDLN, or by employees of the
State of South Dakota to any third party, without prior written authorization of the
vendor.
3. Selection Process
3.1. RFP Evaluation
3.1.1. Proposals will be evaluated by members of the SDLN Executive Committee, the
SDLN RFP Task Force, and other staff of SDLN libraries. The proposals will be
evaluated based on the following criteria:

Ability of the vendor to meet essential requirements

Vendor information and services

Technical specifications and performance

Subsystem specifications

Implementation

Training and support

Costs

Suitability

Favorable references from current customers
Vendors MUST describe in the response to each specific requirement how the
proposed system meets these requirements. Each respondent must specify clearly
which parameters are system-wide and which are governed locally, and which
data must be shared on a system-wide basis.
Proposals will be evaluated based on how well they meet the system and
performance specifications stated in the RFP. Submission of a proposal by a vendor
shall be judged as acceptance of the evaluation technique and as vendor recognition
7
South Dakota Library Network: Request for Proposal, February 2012
that some subjective judgments may be made by SDLN.
Any vendor may be asked to further clarify or explain, in writing, any areas of their
proposal.
3.2. Vendor Presentations
Vendors meeting all criteria as evaluated by the SDLN Executive Committee and RFP
Task Force will be invited to present their system. Vendors will be given a list of specific
processes to demonstrate, and will be expected to answer any questions about their
system and proposal. Presentations will be evaluated by the SDLN Executive
Committee and representatives from member libraries. Each system will be evaluated
based on how well the system is able to perform the listed processes during the
demonstration.
3.3. Preferred Vendor or Vendors
In addition to information gathered through formal review and information obtained
during the vendor presentations, recommendations from multi-type consortia using the
system will also be obtained as part of the evaluation process. The preferred vendor or
vendors will be selected based on the RFP responses, the system as demonstrated, and
peer library references.
3.4. Award of Contract
A response to the RFP is an offer to contract with the South Dakota Board of Regents
on behalf of SDLN. A contract is not formed until the official contract document is
signed by the SD Board of Regents.
3.4.1. Multiple awards. The SD Board of Regents on behalf of SDLN reserves the right
to make awards for services to more than one vendor.
3.4.2. Rejection of proposals. The SD Board of Regents on behalf of SDLN may cancel
this RFP or reject any and all proposals at any time prior to an award. The SD
Board of Regents on behalf of SDLN will not provide information on why a
particular proposal was not selected.
4. Background Information
4.1. Organization Overview
The South Dakota Library Network is investigating new integrated library systems on
behalf of all member libraries. The majority of SDLN libraries currently operate on the
ExLibris/Aleph system, however South Dakota’s two largest cities are currently served
by SDLN member libraries operating on Sirsi-Dynix/Horizon and Innovative/Millennium.
Briefly:
4.1.1. SDLN is made up of 54 Full member libraries and 135 Remote member libraries.
Full members pay for and have access to all functional modules of the Aleph ILS.
8
South Dakota Library Network: Request for Proposal, February 2012
Remote members have access to the Interlibrary Loan module only (not all are
currently using it).
4.1.2. Siouxland Libraries consists of a main library, nine branches and a book mobile
operating on SirsiDynix’s Horizon. The libraries serve the citizens in the city of
Sioux Falls and Minnehaha County, excluding the city of Dell Rapids. Siouxland
Libraries is a public library system formed by the governments of Minnehaha
County and the City of Sioux Falls. Two of the branches are combination
public/school libraries: Brandon and Hartford. An additional branch will be
opening in Sioux Falls in 2013.
Population served: 186,940, based on 2010 census data. (Population estimate in 5
years Is 201,000.)
Siouxland Libraries is an SDLN Full member library. Their bibliographic records are
loaded in ExLibris Aleph, and they utilize the ExLibris Aleph system for resource
sharing with other SDLN member libraries.
4.1.3. Rapid City Public Library consists of a downtown library and one branch library
operating on Innovative’s Millennium. The libraries serve citizens in Rapid City and
Pennington County. A second branch serving Rapid City’s east side is planned to
open in 2012, with a third branch serving the west side to follow in the next few
years.
Rapid City Public Library has 55,000 patrons and serves a population of 90,000+.
Rapid City Public Library is an SDLN Remote member. The library’s bibliographic
and patron records are not loaded into ExLibris Aleph, and they do not participate
in resource sharing via the Aleph system.
4.1.4. Other SDLN Remote member libraries currently rely on various stand-alone
systems, including Follett’s Destiny and Book Systems’ Concourse systems.
4.2. Current Systems and Operational Environments
4.2.1. SDLN currently uses the ExLibris Aleph (v.20.01/rep change 3556) ILS in
combination with Serials Solutions’ AquaBrowser discovery tool. Further
information regarding SDLN’s current system and operational environment can be
found in APPENDIX A.
4.2.2. Siouxland Libraries uses the SirsiDynix Horizon 7.51 (Sybase 15 on Red Hat Linux)
system. Third-party systems are used for reporting – Webreporter – and
telephone messaging via Talking Tech. ILLIAD is currently being implemented.
Further information regarding Siouxland Libraries current system and operational
environment can be found in APPENDIX B.
9
South Dakota Library Network: Request for Proposal, February 2012
4.2.3. Rapid City Public Libraries uses the Innovative Millennium system (v2009b,
upgrading to v2011 in March 2012). Third-party products currently in use include
the Envisionware PC Reservation system, Envisionware LPT: One Print Client, and
Novelist Select. Further information regarding Rapid City Public Libraries can be
found in APPENDIX C.
Note: Transaction records and activity levels for SDLN, Siouxland Libraries and Rapid City
Public Library are located in APPENDIX D.
4.3. Goals of the Project
Provide a new shared integrated library system for the South Dakota Library Network. The
new ILS may incorporate a discovery layer.
In general, the proposed system is expected to operate efficiently in an environment in
which any participating library or group of libraries can:

Establish its own operating policies and procedures

Control the use of the integrated library system through independent password
and authorization functionality, and

Control access to certain files through independent password and authorization
functionality.
The catalog database must allow any library the option of simultaneously searching the
holdings of all SDLN libraries. It is essential that the system function to allow each library
or group of libraries to establish its own operating policies and control access to files
involving internal library functions, and that information concerning the holdings and
circulation status of individual library holdings be easily accessible and immediately
visible from any workstation accessing the system, regardless of its location.
5. Vendor Information
5.1. Background
Provide a brief company description, including the name(s) of its owners and or
principal officers, date of origin and/or incorporation, state and/or country of
incorporation, and whether it is a subsidiary or stand-alone entity.
5.1.1. Is the company publicly held, privately traded?
5.1.2. How many FTEs work for the company?
5.1.3. Identify the number and location of sales and support personnel accessible to
the purchaser.
10
South Dakota Library Network: Request for Proposal, February 2012
5.1.4. If the company is currently for sale or involved in any transactions to expand or
be acquired by another company, explain.
5.1.5. If the company has been involved in a reorganization, acquisition or merger in
last three (3) years, explain.
5.1.6. If the company has been involved in public litigation with a client or third-party
vendor the last three (3) years related to the system that is being proposed in
response to the RFP, explain.
5.2. Provide a link to or copy of the most recent annual company report.
5.3. Experience
5.3.1. Describe the company’s experience in providing automation services to large,
multi-type library consortia.
5.3.1.1. Describe the company’s experience in providing automation services and
support to the various types of smaller libraries that make up multi-type
library consortia.
5.3.2. Describe the company’s position in the ILS marketplace.
5.3.3. How many years has the company worked within the library automation
industry?
5.3.4. Describe the company’s commitment to system development in the last three
(3) years, and projected plans for the next three (3) years.
5.3.4.1. Describe how participating libraries’ input is used in development of the
system.
5.3.4.2. Describe how new functional requirements identified by participating
libraries are accommodated.
5.3.4.3. Describe how participating libraries’ input is used in developing “fixes”
for identified issues.
5.3.5. How long has the system being proposed in response to this RFP been in
production and actively supported?
5.3.6. How does the company actively participate in the development and use of
industry standards?
5.4. Products and Customers
5.4.1. Name the system that is being proposed in response to the RFP, and describe it
11
South Dakota Library Network: Request for Proposal, February 2012
briefly.
5.4.1.1. The system proposed should be a complete system, defined as the
applications, software, software installation, database loaders, training,
documentation, maintenance, and ongoing software enhancements
necessary to provide easy-to-use, online, real-time, integrated and automated
support for the following functions. For each of the functions below, indicate
whether it is operational (Op), planned (P), in development (D), in testing (T)
or unavailable (NO) for a consortial system:
5.4.1.1.1.
Online public access catalog (OPAC), including union catalog
Op, P, D, T or NO?
If P, D, or T, enter Release Date:
5.4.1.1.2.
Cataloging and authority control
Op, P, D, T or NO?
If P, D, or T, enter Release Date:
5.4.1.1.3.
Circulation
Op, P, D, T or NO?
If P, D, or T, enter Release Date:
5.4.1.1.4.
Media Booking
Op, P, D, T or NO?
If P, D, or T, enter Release Date:
5.4.1.1.5.
Course Reserve
Op, P, D, T or NO?
If P, D, or T, enter Release Date:
5.4.1.1.6.
Acquisitions
Op, P, D, T or NO?
If P, D, or T, enter Release Date:
5.4.1.1.7.
Serials management
Op, P, D, T or NO?
If P, D, or T, enter Release Date:
5.4.1.1.8.
Interlibrary loan
Op, P, D, T or NO?
If P, D, or T, enter Release Date:
5.4.1.1.9.
Reports
Op, P, D, T or NO?
If P, D, or T, enter Release Date:
5.4.1.1.10.
Inventory
Op, P, D, T or NO?
If P, D, or T, enter Release Date:
5.4.1.1.11.
Does the system include an integrated discovery layer?
Op, P, D, T or NO?
If P, D, or T, enter Release Date:
5.4.1.1.12.
If no, indicate whether a discovery layer is available but at
additional cost, and
12
South Dakota Library Network: Request for Proposal, February 2012
5.4.1.1.13.
Which, if any, third-party discovery layers have been successfully
integrated with the system?
5.4.2. State the dates and general content of at least three planned general releases or
major upgrades to the system.
5.4.3. How many customers are currently running production versions (NOT
experimental, test or beta versions) of the system?
5.4.4. List consortia and/or groups of libraries of similar size and characteristics to
SDLN that are currently using the system. Identify a contact person for each,
including name, address, telephone number and email.
5.5. Vendor Contacts
5.5.1. Describe any user groups or community resources (wikis, listservs, etc.) available
for the administration and/or staff users of the system.
5.6. Training
5.6.1. Describe the training offered for new users of the system surrounding a typical
implementation, including any associated costs.
5.6.2. Describe different types of on-going training opportunities offered (computerbased training, on-site training, training manuals, etc.) including any associated
costs for each.
5.6.3. How many training hours are typically required before staff master the initial use
of the system?
5.6.4. What type of training is offered/available when a new release or version is
distributed? What cost, if any, is associated?
5.7. Documentation
5.7.1. Is documentation intended specifically for consortial administration of the
system available? Is there an additional cost?
5.7.2. State the media type and number of copies of documentation that will be
provided at the time of purchase. If documentation is made available as an online
knowledge base, state the method of access and number of authorized users.
5.7.3. Is documentation for system administrators and staff end-users updated with
each system change? Indicate the timeframe in which new documentation is
typically made available following a system change.
13
South Dakota Library Network: Request for Proposal, February 2012
5.7.4. Is all system documentation/access to system documentation included with the
system or is there additional documentation available that is packaged and sold
separately? Describe additional documentation options, if any.
6. Technical Specifications
The vendor must describe in detail how the system functions in respect to each capability
below, including whether third party products are necessary and if there is additional cost
involved.
6.1. Network
6.1.1. Describe the configuration of the proposed system – hosted, non-hosted or
cloud-based. If more than one option exists, or if a combination of hosting types is
proposed, the response must clearly state the differences and ramifications of
each choice, including cost variables.
6.1.2. Describe or provide a visual representation of the system architecture.
6.2. Software
6.2.1. What OS version and build does the system’s software run on?
6.2.2. What is the underlying database (including version and build)?
6.2.3. Describe any other system software (database software and/or third party
products) required for operation of the proposed system within each member
library.
6.2.4. What programming language is the ILS written in?
6.2.5. Describe the manner in which character sets are supported.
6.2.6. Does the system provide a Z39.50 client? Can the system demonstrate
compliance with ANSI/NISO Z39.50 -2003 by interoperating over a TCP/IP line with
another vendor’s client software that is Z39.50-2003 compliant?
6.2.7. Describe the level of access SDLN administrative staff will have to the system’s
underlying database tables, scripts and/or code.
6.2.7.1.
Is the access direct via SQL, via an API, or other? Explain.
6.2.8. How are changes or customizations to the underlying code carried forward when
a version change or update happens?
6.2.9. How does the system provide for the creation and implementation of customergenerated APIs and web services to connect with external systems, allow data
14
South Dakota Library Network: Request for Proposal, February 2012
collection and manipulation, etc.?
6.2.10. SDLN member libraries are located in two different time zones, Mountain and
Central. Explain how the system would handle time-sensitive functions so that
activity occurring in each time-zone is tracked and reported correctly.
6.3. Database
6.3.1. Is the system able to access input from multiple workstations, applying the
appropriate record locking to ensure data integrity?
6.3.1.1.
Can more than one user open/edit a record simultaneously? Explain.
6.3.2. If a change is made to the database, does the system automatically update all
affected records in real time? Explain.
6.3.3. Does the system use an open, relational database that is ANSI SQL compliant? If
not, please describe the type of relational database used.
6.3.4. Does the system comply with/provide ODBC (open database connectivity)?
6.3.5. Is it possible to export any record or portion of record to ASCII format?
6.3.5.1. In what other formats can records/portions of records be exported
(comma delimited, XML, etc.)?
6.3.6. Describe how the system indexes and/or re-indexes records when changes are
made.
6.3.6.1.
Does the indexing process require system down-time?
6.4. Storage
6.4.1. What is the overall storage capacity?
6.4.2. How much storage is allocated per customer?
6.4.3. Describe any limits on storage, including limitations on overall storage, records
and graphics.
6.5. Back-up and Archiving
6.5.1. Describe the system’s back-up systems.
6.5.2. Where, and on what type of media are back-ups stored?
15
South Dakota Library Network: Request for Proposal, February 2012
6.5.3. What is a typical back-up schedule, and what is the retention policy for back-up
data?
6.5.4. Describe the system’s disaster recovery plan.
6.5.4.1. If a bare-metal restore is required, what is an estimated time for
recovery?
6.5.4.2. Describe the process of restoring data, including records, as well as a
whole system restore.
6.5.5. Describe the routine data back-up process and any alternatives offered.
6.5.6. Are redundant back-up systems provided? If so, please describe.
6.6. Hosting Environment (specify hosted, non-hosted and/or cloud-based)
Describe the hosting environments provided and which is recommended for SDLN.
Address each of the following points.
6.6.1. If hosted, where are the system’s servers physically located? List and explain any
legal ramifications there are based on the system’s physical location.
6.6.2. Describe the system’s power supply including battery back-ups or UPS that are
recommended and/or employed, as well as how long they generate power in the
event of power failure.
6.6.3. Describe any fire suppression systems used and/or recommended.
6.6.4. Describe climate control systems used and/or necessary, including air
conditioning and humidity controls.
6.6.5. Describe the physical security of the environment including access restrictions,
locks, security guards, etc.
6.6.6. Describe the system-monitoring information available, and the kind of
notification system used in the event of service interruptions if the system is not
hosted locally.
6.7. Servers
6.7.1. Describe the hardware specifications and components necessary for the system
to be fully functional.
6.7.2. Are servers dedicated or virtual?
6.7.2.1. If virtual, how many other customers have access to them and what
security measures are in place to prevent unauthorized access?
16
South Dakota Library Network: Request for Proposal, February 2012
6.7.3. How many servers are dedicated to the production environment?
6.7.3.1.
How many test and/or staging environments would be available to SDLN?
6.7.4. Are all servers managed from and located in a central location?
6.7.5. Describe the hardware expansion process and its impact on services to member
libraries.
6.7.6. Describe any clustering, load-balancing, and/or failovers.
6.7.7. Describe how bandwidth allocations are assigned and what happens if
allocations are exceeded.
6.7.8. How is additional bandwidth obtained, and what costs are associated with
increased bandwidth?
6.7.9. If a hosted system is recommended:
6.7.9.1.
How many customers are handled per server?
6.7.9.2. Explain how customer data is stored across servers and locations,
including all physical server locations and whether data is stored on multiple
servers.
6.7.9.3.
How are security breaches handled?
6.7.9.3.1.
How are customers notified of security breaches, and how soon
after a breach is discovered?
6.7.9.4. How would data be retrieved and withdrawn in the event a member
library separated from SDLN?
6.7.9.5.
How would data be retrieved and returned in the event SDLN dissolved?
6.7.9.6. How would data be retrieved and returned in the event the hosted
system dissolves or SDLN wishes to dissolve the agreement?
6.8. Upgrade and Maintenance Process
6.8.1. Describe how routine maintenance and upgrades are performed, including
whether changes are made on one server or customer at a time.
6.8.2. Describe the anticipated frequency of software and hardware upgrades, and
who is expected to install the upgrades.
6.8.3. Describe whether customers experience downtime or system slowness during
17
South Dakota Library Network: Request for Proposal, February 2012
upgrades/maintenance. Specify the typical amount of downtime/system
slowdown experienced.
6.8.4. How much advance notification are customers given before upgrades and
maintenance are performed?
6.8.5. When are maintenance and upgrades typically preformed?
6.8.6. What is the typical up-time guaranteed?
6.9. Client/Staff Interface
6.9.1. Describe the typical client/staff workstation environment and requirements.
6.9.2. Does the system run simultaneously with other common clients on a single
workstation?
6.9.3. Does a staff client have to be installed on individual workstations? How
frequently do upgrades require individual workstation installs and/or downloads?
6.9.4. If a software as a service (SaaS) option is proposed and the software runs on a
browser/web-based client, is it cross-browser compliant, working on all major
browsers including Internet Explorer, Firefox, Safari and Chrome? List the
supported browsers, and the minimum recommended browser versions.
6.9.5. If the client does not run through a browser, list supported client platforms
(Windows XP, Windows 7, Mac OXS X Lion, iPad, mobile devices, etc.) Describe the
minimum and recommended configurations. Include CPU model and speed, RAM
usage, OS version and disk space requirements.
6.9.6. Describe any plug-ins, Active X or client modules (Java, etc.) which are required
to run the software.
6.10.
Security
6.10.1. Describe the system’s virus protection.
6.10.2. Describe the system’s firewall solution.
6.10.3. Describe the software security updates procedures.
6.10.4. Describe the privacy safeguards.
6.10.5. Is access to remote system monitoring provided? Describe, including whether
alerts are available once thresholds are met, and the kinds of notices (email, SMS,
phone, etc.) available for:
18
South Dakota Library Network: Request for Proposal, February 2012
6.10.5.1. Disk usage
6.10.5.2. Server load
6.10.5.3. Database usage
6.10.5.4. Any others provided
6.11.
Authentication and Authorization
6.11.1. Is an administrator at the local level (in each member library) able to set
functions and screen access rights by individual or group?
6.11.2. Describe how the system authenticates both a staff member and a public user.
6.11.3. Does security for remote users allow the following: anonymous login (guest
user/no password); user-specific authentication using login-ID/password.
6.11.4. Describe the process of user authentication.
6.11.5. Describe authorization/authentication process for specific record types and
field groups within records.
6.11.6. Describe the process by which the system authenticates authorized staff to
create, edit, and delete all types of records.
6.11.7. Describe the process of creating user-authentication profiles (basic definitions
that can be copied onto new user profiles). Are there templates, or can existing
profiles be cloned and applied to new users?
6.11.8. Is authorization/authentication role or attribute based?
6.12.
Presentation
The vendor must describe in detail how the system functions in respect to each
capability below, indicating if third-party products are necessary and if there is
additional cost involved.
6.12.1. Help
6.12.1.1. Describe the help options available for the system including:
6.12.1.1.1.
In person, hands-on module training
6.12.1.1.2.
Interactive online tutorials
6.12.1.1.3.
Knowledge-base
19
South Dakota Library Network: Request for Proposal, February 2012
6.12.1.1.4.
Customer listserv or online forum
6.12.1.1.5.
Emergency trouble-shooting (telephone, tweets, email, text, etc.)
6.12.1.1.6.
Support manuals (print, electronic)
6.12.1.1.7.
Periodic in-person training for updates or new releases
6.12.1.1.8.
Context-sensitive, integrated help on each screen and/or within
each module
6.12.1.2. Are updates to online help provided with changes and updates to the
system? Is there an extra charge?
6.12.1.3. Can libraries edit help screens locally?
6.12.2. User Interface
6.12.2.1. Does the system have a time-out feature that can be adjusted by
authorized staff at the global/consortia level?
6.12.2.1.1.
Can the public and staff interfaces be set to time out at different
durations?
6.13.
Report Writing
This section relates to end-user generation of reports on any data element used by the
system or created by functional activity, singly or in combination, for standard or
customized time periods.
6.13.1. Describe the reporting system used by the system – specifically indicate
whether it is written and/or maintained by a third party.
6.13.2. Are authorized staff at local libraries able to define and format specific reports
without having to explicitly write SQL commands? Describe how reports are
defined and formatted in the system.
6.13.3. Does the system support pre-programming and scheduling of standard and
custom reports? Describe how the system accommodates pre-programming and
scheduling of standard and custom reports.
6.13.4. Describe the output options available for reports.
6.13.5. Provide a list of standard reports.
6.13.5.1. Indicate which of these can be set locally to generate automatically on a
scheduled basis (e.g. circulation reports, overdues, etc.).
20
South Dakota Library Network: Request for Proposal, February 2012
6.13.6. Describe the process of creating a customized report, including how it is
constructed, and whether the configuration can be saved, altered, deleted and/or
shared with other libraries for viewing and copying.
6.13.7. Does the system provide lists, counts, and other statistical reports monitoring
OPAC search activities, either singly or in combination with each other, for
standard or customized time periods (including comparable data from previous
years)? Describe/list options available.
6.14.
Performance
6.14.1. What is the maximum number of simultaneous users and inquiry users (local
and/or remote) that the system can be configured for? What is the recommended
number of simultaneous users that should be configured for a consortia of SDLN’s
size?
6.14.2. Does the system have a time-out feature that can be adjusted by functional
area by the system administrator, and if so at what level (global/consortia, local
library level)? Describe the system’s time-out feature.
6.14.3. Is it possible to run reports simultaneously and/or at peak periods without
system performance degradation? Are there any reports which should NOT be run
at peak periods due to system degradation issues?
6.15.
Acceptance tests
6.15.1. The vendor must provide SDLN with a list of all physical and environmental
requirements of the system.
6.15.2. The vendor must provide SDLN with a list of the qualifications and numbers of
staff to operate and maintain the proposed system. For each staff person, a list of
duties should be provided.
6.15.3. The vendor must supply bandwidth recommendations for the central site (if
hosted by SDLN), and for local library sites.
6.15.4. The vendor must supply load-testing results of the system to show system
performance is within acceptable limits for a consortial environment.
6.15.5. The vendor must propose acceptance tests which will be used to demonstrate
that the system is working. Following any amendments of the proposed
acceptance tests as may be agreed upon by SDLN and the vendor, these
acceptance tests will be expected to demonstrate the functionality claimed in the
vendor’s total proposal.
6.15.6. SDLN reserves the right to develop tests to verify compliance with the
21
South Dakota Library Network: Request for Proposal, February 2012
requirements of the RFP and with the vendor’s response to the RFP during
implementation or at any time during the life of the contract.
7. Subsystem Specifications
The vendor must describe in detail how the system functions in respect to each capability
below, whether third-party products are necessary and if there is additional cost involved in
implementation.
7.1. Online Public Access Catalog
This section deals with the system’s searching and display of records to the public, as
well as the features and options available to patrons.
7.1.1. General Considerations
7.1.1.1.
Does the system support SSL, and if so, is it enabled by default?
7.1.1.1.1.
Is the SSL certificate locally generated, or is a certificate needed
from a certificate authority such as VeriSign or Thawte?
7.1.1.2. Does the system allow access to the OPAC through all major browsers,
including Internet Explorer 7+, Firefox, Chrome, Safari and Opera?
7.1.1.3. Does the system provide a secured interface between the OPAC and
patron files that will allow patrons to access personal circulation information
(e.g. items on loan, fines, holds, etc.)? Describe how.
7.1.1.4. List and describe any patron customization/personalization options (e.g.
ability to save searches, add tags, save favorites, a reading history, etc.)
indicating whether each option can be turned on/off at an individual/local
library level by authorized staff.
7.1.1.4.1.
Does the system, at the discretion of the local library, allow for
patrons to choose to maintain or purge their reading history, search
history, etc.?
7.1.1.4.2.
Describe any methods by which in a consortial setting the system
provides for patrons to offer feedback and suggestions directly to their
local library.
7.1.1.5. Describe any automated list or RSS feed options (for new books, popular
titles, etc.) that can be generated by staff for display in the OPAC. Indicate
whether these options, if available, are configurable at the local library level
or at the global/consortia-level.
7.1.1.6. Does the system provide a notification method for alerting patrons? Can
notifications be automated (fine/block/book arrival) or customized (e.g.
22
South Dakota Library Network: Request for Proposal, February 2012
forgotten item, etc.)? Describe.
7.1.1.7. Does the system support payment of fines or bills online? If so, is it
native support, or is third-party involvement such as Paypal required?
7.1.1.7.1.
If supported, is the option enabled globally for all libraries, or can
it be controlled at the local library level?
7.1.2. Ease of Use
7.1.2.1. Does the system provide the ability to locally – at the local library level –
customize the contents and display of the menu, search and results screens?
Describe the level of customization possible.
7.1.2.2. Describe which screen readers (e.g. Bobby, Jaws) have been used to test
the usability of the proposed system by persons covered by the Americans
with Disabilities Act – report the outcome of the tests.
7.1.2.3. Describe the system’s compatibility with standard adaptation products
used by individuals covered by the Americans with Disabilities Act.
7.1.3. User Help Capabilities
7.1.3.1. Does the system provide the ability to customize, add or suppress
commands, help screens, menus, and documentation at the global/consortia
level for default profiles, and at the workstation/local level for session
profiles? Describe the level to which customizations are possible.
7.1.4. Searching Capabilities
7.1.4.1. Regardless of the file structure used by the system, does the OPAC allow
holdings for all libraries to be searched and displayed simultaneously or singly
at the patron’s discretion?
7.1.4.2. Describe how the system determines a patron’s default location (login, IP
authentication, saved patron choice, etc.)?
7.1.4.3. Describe the search capabilities of the OPAC indicating whether the
system supports Boolean operators, proximity (adjacent, near) operators in a
keyword search.
7.1.4.4.
Does the system support “did you mean…” prompts?
7.1.4.5.
Is there a built-in spellcheck feature?
7.1.4.6.
Does the system provide hot links to redirect a search to other authors,
23
South Dakota Library Network: Request for Proposal, February 2012
titles, or subjects in a bibliographic record? Describe how and where this is
accomplished, including the level to which the feature is customizable at the
local library level or if settings must be configured at the global/consortia
level.
7.1.4.7. Does the system display cross-references for entries in an authority file
such as subject headings and uniform titles?
7.1.4.8. List all methods available to users to limit searching. Include how
customizable the limit settings are on a local and global/consortia level.
7.1.4.9. Does the system allow all MARC fields and sub-fields to be indexed for
searching (e.g. MARC tag 586 and other notes fields; specific material in
subfield “a” of MARC tag 300, etc.)? Describe the system’s capability,
including how locally configurable these settings are on a local and
global/consortia level.
7.1.4.10. Does the system allow users to view and edit previous searches and to resubmit them without having to re-key them?
7.1.4.11. What is the maximum number of items that a search will return? Indicate
if the default display limit number can be set locally, how the system displays
a search when the default display limit has been reached and/or exceeded,
and with what options the user is presented when an excessive number of
results is retrieved.
7.1.4.12. Describe and provide examples of the system’s ability to correctly
recognize, sort, retrieve and display call numbers, including Library of
Congress, Dewey Decimal, local call numbers, SuDoc, etc.
7.1.4.13. Does the system allow custom site groupings to be defined as default
search options (“search all libraries in my town…”)? Describe how and at
what level (global/consortia, local library administration, etc.) these options
could be configured.
7.1.5. Output capabilities
7.1.5.1. When an item’s status changes (it is checked out, returned, etc.) is the
item’s status immediately reflected in the OPAC?
7.1.5.2. At what point in a patron’s search is item status information (on shelf/on
loan/on hold, etc.) first visible to the patron?
7.1.5.2.1.
If an item is checked out, does the status information indicate the
date/time the item is due back?
24
South Dakota Library Network: Request for Proposal, February 2012
7.1.5.3. Does the system display status change labels (e.g. Re-shelving, On Hold,
etc.)? Describe, including how customizable the status change labels and
time-settings (for re-shelving periods, etc.) are at the library and
global/consortia level.
7.1.5.3.1.
Do all libraries need to agree on a set of item status labels, or is
customization at the local library level possible?
7.1.5.3.2.
At what level are the time settings for the status change labels
set? (Local library or global/consortia level)
7.1.5.4. When searching multiple locations, describe how and to what level
search results are de-duplicated.
7.1.5.5.
How are duplicate titles displayed in a list of search results?
7.1.5.6.
Does the search interface support FRBR-ization of search results?
7.1.5.7. Does the search interface offer the patron breadcrumbs or a link-trail to
navigate back through their search?
7.1.5.8. What output options are available (print, email, text, save, etc.) for the
patron to communicate item-level information?
7.1.5.9. List any third-party bibliographic export or citation management products
the system is compatible with (EndNote, Refworks, etc.).
7.1.5.10. Does the system support the display of images including cover/jacket art
in the search results list?
7.2. Cataloging and Authority Control
This section describes system capabilities that have to do with creation and
maintenance of bibliographic, holding and authority control records – the records that
comprise the catalog database.
7.2.1. Record creation
7.2.1.1. How would each library’s individual bibliographic data be maintained in
the proposed system?
7.2.1.2. Are local libraries able to transfer bibliographic or authority records in
batches or individually from national bibliographic utilities or vendors? List
the bibliographic utilities and vendors with which the system interfaces
(OCLC, MARCIVE, Baker & Taylor, Midwest Tapes, etc.).
7.2.1.3.
Is it possible to convert, index and load these records into the OPAC in a
25
South Dakota Library Network: Request for Proposal, February 2012
single transaction? Describe how the system enables this process.
7.2.1.4.
List the methods by which cataloging records can be imported.
7.2.1.5. Does the system allow the addition of graphics such as book covers to
bibliographic records, or provide some mechanism of linking to title-specific
graphics files? Describe what services and processes are available to provide
this feature as well as any associated costs.
7.2.1.6. What is the maximum number of fields allowed for a single record
(bibliographic, authority or holding)?
7.2.1.7. What is the maximum number of characters allowed for a single record
(bibliographic, authority or holding)?
7.2.1.8. What is the maximum number of item records that can be associated
with a holdings record?
7.2.1.9. Does the system have the capability to store bibliographic, authority and
holdings records that are created online by a staff member in a working file
that can be easily reviewed by another staff member prior to the records
being entered into the catalog?
7.2.1.10. When bibliographic or authority records are imported from databases
outside the system, does it automatically detect matching standard numbers
in the existing database? If so, describe the action taken by the system.
(Report, prompt, merge, overlay, etc.)
7.2.1.10.1.
Does the system allow local libraries to define which linked
records will be affected by merge/overlay (e.g. bibliographic records
only, or bibliographic and holdings records)?
7.2.1.10.2.
Does the system allow each individual library to determine fields
that should not be overlaid?
7.2.1.10.3.
Does the system preserve the links between the bibliographic
record and other records (circulation, ILL, serials, etc.) following the
overlay?
7.2.1.11. Does the system mark errors in imported records and provide a
mechanism for retrieval of those records for correction? Describe this
process.
7.2.1.12. Does the system allow the presence of more than one live URL link in a
catalog record?
26
South Dakota Library Network: Request for Proposal, February 2012
7.2.1.13. How does the system handle record numbering when records are
imported from multiple different vendors?
7.2.1.13.1.
Is the record source preserved in the record?
7.2.1.13.2.
Is the record source used in determining whether a record is
overlaid or preserved, and if so, how?
7.2.2. Describe the process by which ebook and e-audio records may be batch-loaded,
edited, accessed and maintained.
7.2.3. When a new record is added, an existing record is edited, or a record is deleted
what is the delay prior to the change displaying in the OPAC?
7.2.4. Describe the process by which the system will manage authority control
efficiently and effectively in SDLN’s consortial environment.
7.2.5. Is authority control synced with OCLC? Describe how syncing is handled.
7.2.6. Which character holding libraries are included/available?
7.2.7. How are new cataloging rules implemented?
7.2.8. Is it possible for authorized staff members at a local library to delete and
undelete item, holding or bibliographic records individually and/or in batches?
Describe the steps necessary to complete these processes.
7.2.8.1. How does the system notify of or otherwise prevent inadvertent deletion
of a bibliographic record which has records associated with it?
7.2.8.2. How does the system notify of or otherwise prevent inadvertent deletion
of a holding record should any item attached to the holding record be
checked out or have a circulation transaction (bill, hold, recall, etc.) associated
with it?
7.2.9. Does the system provide for/allow the creation of custom cataloging templates?
Describe.
7.2.10. Standards
Indicate which of the standards below are supported by the system, and to what
extent:
7.2.11. Descriptive cataloging
 AACR2 [Anglo-American Cataloging Rules, Revised, 2005 edition]
 MARC21 [Machine Readable Cataloging, v.21]
27
South Dakota Library Network: Request for Proposal, February 2012




OCLC Bibliographic Formats & Standards
DACS [Describing Archives : A Content Standard]
DCRM (B) [Descriptive Cataloging of Rare materials : Books]
DCMI [Dublin Core Metadata Initiative]
7.2.12. Holdings
 MARC21 [Machine Readable Cataloging, v.21]
 <additional serial prediction patterns for more complex patterns>
7.2.13. Subject/Authorities
 LCSH [Library of Congress Subject Headings]
 MeSH [Medical Subject Headings]
 LCSH for children [Library of Congress Subject Headings Children's Subject
Headings]
 Sears Subject Headings
 LCGFT [Library of Congress Genre/Form Terms]
 GSAFD [Guidelines on Subject Access to Individual Works of Fiction,
Drama, etc.]
 MIGFG [Moving Image Genre Form Guide]
 TGM [Getty's Thesaurus of Graphic Materials]
 TGN [Getty's Thesaurus of Geographic Names]
 AAT [Getty's Art and Architecture Thesaurus]
 VRA Core [Visual Resources Association Core]
 LCNAF [Library of Congress Name Authority File]
 LCSAF [Library of Congress Subject Authority File]
 MARC21 [Machine Readable Cataloging, v.21]
7.2.14. Classification Handling Standards
 LCC [Library of Congress Classification]
 DDC [Dewey Decimal Classification]
 NLM [National Library of Medicine Medical Classification]
 Sudocs and others based on it [Superindentent of Documents Classification
Schema]
 Free text call nos., such as successive numbering (i.e. CD 111, CD 112)
7.2.15. What plans have been made to accommodate upcoming changes in cataloging
systems and metadata formats? Specifically, how will the transition to FRBR (e.g.
RDA), FRAD, FRSD, and MARC’s replacement be handled?
7.3. Acquisitions and Serials Control
This section relates to system capabilities that have to do with ordering and receipt of
library materials and fund accounting activities that accompany those activities. The
vendor must describe in detail the manner in which its system functions with respect to
28
South Dakota Library Network: Request for Proposal, February 2012
each point below.
7.3.1. Describe how acquisitions and serials functionalities are integrated in the system
– is it possible to use either serials or acquisitions “modules” without using both?
7.3.2. Describe how the system protects secure data (for example, fund number or
name of requestor) in a consortial environment.
7.3.3. List and describe all standard reports available to be generated in the
acquisitions/fund accounting module.
7.3.4. Define the output formats available and submit examples.
7.3.5. Describe how acquisitions functions are integrated with other modules/system
functions. In particular, describe how acquisitions functions are integrated with
serials functions.
7.3.6. Describe how access to order history is maintained and accomplished.
7.3.7. Are acquisitions reports available by call number and format?
7.3.8. Is it possible to set, on a library by library basis at the library level, whether onorder items can be viewed in the OPAC?
7.3.9. Does the system permit authorized local library staff to suppress a bibliographic
record, order, or other record from display in the OPAC?
7.3.9.1. If available, is this option set at the global/consortia level, or on a libraryby-library basis at the local level?
7.3.10. Does the system permit authorized local library staff to suppress specific fields
within a bibliographic record from display in the OPAC?
7.3.10.1. If available, is this option set globally, or on a library-by-library basis?
7.3.11. List the third-party systems which are currently capable of communicating with
the system for acquisitions purposes (e.g. Banner, YBP, Mackin, Amazon, etc.).
7.3.11.1. Describe the process by which communication with each of the thirdparty systems is configured and according to what standard (EDI, EDIFACT,
etc).
7.3.11.2. Does set-up take place on the local library level, or on the
global/consortia level?
7.3.11.3. Indicate to what level the system complies with EDI/EDIFACT standards.
29
South Dakota Library Network: Request for Proposal, February 2012
7.3.12. Is patron-driven acquisitions available? If so, does the system provide for local
library-level administration of patron-driven acquisitions, and is the option set at a
global/consortium-wide level, or is it available on a library-by-library basis?
7.3.13. Does the system provide for automatic routing of received items?
7.3.14. Describe and provide examples of the system’s budget tracking capabilities.
7.3.15. Serials
7.3.15.1. Does the system provide a way to track license agreements?
7.3.15.1.1.
Describe any available options for electronic resources
management (ERM), and indicate additional costs associated, if any.
7.3.15.1.2.
Describe how tracking is handled for:
7.3.15.1.2.1.
Administrative passwords
7.3.15.1.2.2.
URLs
7.3.15.1.2.3.
Statistical portals
7.3.15.1.2.4.
License terms for ILL
7.3.15.1.2.5.
License terms for Course Reserves
7.3.15.2. Are prediction patterns available, and can custom prediction patterns be
configured for a) serials and b) standing orders
7.3.15.3. Does the system allow for the creation of routing lists, and automatic
routing of received serials issues?
7.4. Circulation
This section relates to capabilities that have to do with circulation of library materials to
library users, including the management of items placed on reserve and scheduled via
media booking. The vendor must describe in detail the manner in which its system
functions with respect to each of the points delineated below.
7.4.1. SDLN member libraries are located in two different time zones, Mountain and
Central. Explain how the system would handle time-stamping, calendars, duedates, back-dating and other time-sensitive functions so that each library’s
circulation transactions are recorded correctly with respect to time zone.
7.4.2. Describe the level to which the system allows authorized staff at local libraries
and sub-library or branch locations to control each of the functions below:
30
South Dakota Library Network: Request for Proposal, February 2012
7.4.2.1.
Calendars
7.4.2.2. Notices: headings, wording and formatting, including that on overdues,
recalls, holds, fines, etc.
7.4.2.3.
Reports
7.4.2.4.
Locations
7.4.2.5.
Patron types/classes
7.4.2.6.
Policies, including:
7.4.2.6.1.
Circulation periods
7.4.2.6.2.
Patron blocks
7.4.2.6.3.
Fines
7.4.2.7.
Passwords
7.4.2.8.
Staff authorizations
7.4.3. List the methods by which an individual library might opt to send notices (fines,
holds, recalls, overdues, etc.) to its patrons (email, text, print, etc.) from within the
system.
7.4.4. Does the system allow individual libraries to:
7.4.4.1.
Schedule the running of notices, billing and reports to run automatically?
7.4.4.2.
Elect to run them manually/on-demand if desired?
7.4.5. Is the system configured to integrate with third-party email products (Outlook,
etc.)? Indicate which products, and if additional cost is involved in configuring the
system?
7.4.5.1.
Is it possible to send an email directly from a patron’s record?
7.4.6. Is the system configured to integrate with third-party telephone messaging
products? Indicate which products, if any, and if additional cost is involved in
configuration.
7.4.7. Describe the level to which patron records are searchable and provide examples.
7.4.8. Indicate whether the system provides for each of the following functions to be
set by authorized staff at a local library/sub-library/branch level:
31
South Dakota Library Network: Request for Proposal, February 2012
7.4.8.1.
Back-dating
7.4.8.2. Bulk changing of due-dates based on specific parameters (due-date, item
type, etc.)
7.4.8.3.
Ability to place holds on on-order items
7.4.8.4.
Ability to place copy-level holds
7.4.9. Describe how the system would handle patron categories for a large number of
libraries and circulation units:
7.4.9.1. What is a maximum number of patron categories that the system can
handle?
7.4.9.2.
What is the maximum number of patron categories per individual library?
7.4.10. Describe how the system would handle item categories for a large number of
libraries and circulation units:
7.4.10.1. What is the maximum number of item categories that the system can
handle?
7.4.10.2. What is the maximum number of item categories per individual library?
7.4.11. Patron and item records
7.4.11.1. Describe how security for patron records is handled by the system.
7.4.11.2. Describe the process by which patron records can be batch-loaded,
indicating which third-party systems or protocols the systems supports.
7.4.11.3. Describe the available methods to create, display and edit patron
(name/address) records both within the system and off-line.
7.4.11.3.1.
Describe how the system handles management of patron records
in a consortial setting, including:
7.4.11.3.1.1.
Unique patron records
7.4.11.3.1.2.
Duplicate patron records
7.4.11.3.1.3.
How ownership of patron records is determined
7.4.11.3.1.4.
How patron records for the system are handled where
patron information can be shared between libraries
32
South Dakota Library Network: Request for Proposal, February 2012
7.4.11.3.1.5.
How patron records for the system are handled when
patron information must remain private and cannot be shared with
other libraries
7.4.11.3.2.
Indicate whether the system can accommodate the following
information fields, whether additional fields can be customized, and at
what level (global/consortia administration, local library administration,
etc.):
7.4.11.3.2.1.
System-generated ID number
7.4.11.3.2.2.
Barcode (14-digit, Codabar)
7.4.11.3.2.3.
Name
7.4.11.3.2.4.
Street address
7.4.11.3.2.5.
City, State, Zip code
7.4.11.3.2.6.
Email address
7.4.11.3.2.7.
Phone number
7.4.11.3.2.8.
Registration ID
7.4.11.3.2.9.
Drivers license number
7.4.11.3.2.10.
Permanent government-issued ID number
7.4.11.3.2.11.
Date of birth
7.4.11.3.2.12.
Patron class
7.4.11.3.2.13.
Expiration date
7.4.11.3.2.14.
Notes field(s)
7.4.11.3.3.
Indicate which patron record fields can be duplicated and to what
extent duplication is possible – does the system support multiple
address, phone number and email address, notes, etc. fields?
7.4.11.4. Describe the parameters available for purging patron records.
7.4.11.4.1.
Describe any safeguards that prevent the deletion of patron
records if outstanding obligations (bills, fines, charged items, etc.) exist.
7.4.11.5. Is it possible to create links between records, or set hierarchical
33
South Dakota Library Network: Request for Proposal, February 2012
relationships between records? (Parent/child, family, authorized proxy users,
etc.)
7.4.12. Describe how off-line circulation is handled should the system servers go offline, or a library’s internet access go down.
7.5. Media Booking
7.5.1.
Does the system offer a media-booking function? Describe.
7.5.1.1.
What reports are available for this function?
7.6. Course Reserves
7.6.1. Does the system offer a course reserves function? Describe.
7.6.1.1.
What reports are available for this function?
7.7. Interlibrary Loan (ILL)
This section relates to standards and protocols that allow communication between
libraries for the purposes of resource sharing.
7.7.1. List and describe the standard reports available for interlibrary loan.
7.7.2. List and describe the ILL statistics collected and fields available for creating
custom reports.
7.7.3. Describe how the system communicates with circulation functions for the
purposes of the following in relation to ILL items and requests:
7.7.3.1.
Fines/fees
7.7.3.2.
Blocks
7.7.3.3.
Holds
7.7.3.4.
Check-in/out
7.7.4. Describe how communication between libraries within the SDLN consortium
with regards to ILL items takes place.
7.7.5. Are local libraries able to set their own parameters for:
7.7.5.1.
Preferred borrowing partners
7.7.5.2.
Policies
34
South Dakota Library Network: Request for Proposal, February 2012
7.7.5.3.
Due dates
7.7.5.4.
Return delivery delays
7.7.5.5.
Renewal parameters
7.7.5.6.
ILL fees
7.7.5.7.
Maximum number of active requests per patron
7.7.6. Are local library staff able to search for active and closed ILL requests by the
following:
7.7.6.1.
Bibliographic field
7.7.6.2.
OCLC numbers
7.7.6.3.
NLM numbers
7.7.6.4.
RLIN numbers
7.7.6.5.
ISSN or ISBN numbers
7.7.6.6.
User/patron ID/barcode
7.7.6.7.
User/patron name
7.7.6.8.
Unique numbers (such as tracking numbers assigned by the system)
7.7.6.9.
Originating institution
7.7.6.10. Transaction status
7.7.6.11. Local call number
7.7.6.12. Title
7.7.6.13. Article title
7.7.6.14. Author
7.7.6.15. Format
7.7.7. Is an online archive of completed ILL requests maintained?
7.7.7.1. If yes, is it possible to specify for how long the requests are maintained in
the archive, and at what level are archiving parameters set (global/consortia
or local library level)
35
South Dakota Library Network: Request for Proposal, February 2012
7.7.8. Does the system track U.S. copyright for successfully completed requests?
Describe how access to the list of compiled titles is provided.
7.7.9. Is the system Z39.50 compliant?
7.7.10. Is the system ISO ILL 10161 and 101060 compliant? Describe operability.
7.7.11. Describe how communication/requests from/to libraries outside the consortium
can be handled within the system.
7.7.12. Does the system provide a mechanism for both mediated (staff-reviewed) and
unmediated (requests sent to potential lenders without intermediary review by
library staff) patron requests?
7.7.13. What delivery options are supported by the system (fax, Ariel, email, standard
mail, courier, etc.)? Is it possible to customize delivery options, and if so at what
level (global/consortia-wide, or local library level)?
7.7.14. Does the system provide the option of blank request forms for returnable and
non-returnable (copy/electronic) items?
7.7.15. Which third-party interlibrary loan/document delivery products is the system
compatible with (ILLIAD, CLIO, etc.)? List and describe at what level the third-party
products can be implemented (global/consortia-wide or local library level).
7.8. Inventory
7.8.1. Describe the system’s inventory capabilities.
7.8.2. Describe the process of setting up an inventory report, and attach or include
sample inventory reports.
7.8.3. Provide a list of compatible software and equipment necessary for inventory
(scanners, etc.).
8. System Migration and Implementation
8.1. Installation and Migration
The vendor should be able to migrate all necessary data from the existing system so
that the system is fully operational for each library on go-live date(s).
Describe the data migration planning process and testing processes recommended for
consortia prior to implementation.
8.1.1. Implementation plan
36
South Dakota Library Network: Request for Proposal, February 2012
8.1.1.1. Provide a detailed schedule for the system’s implementation, explaining
how coordination with SDLN management and staff at member libraries will
be undertaken. The schedule should include database clean-up, database
profiling, installation of hardware, loading of the system and application
software, installation of all ILS modules, database conversion and loading, and
the migration of each SDLN member library to the new ILS.
8.1.2. If applicable, it is expected that the vendor will be responsible for installation of
any necessary central site equipment, including servers (database, transaction,
web, etc.) cabling, connections to Internet (locally provided connection), etc., as
well as the system and application software.
8.1.3. Conversion
8.1.3.1. Outline a potential conversion plan from the existing database to the
vendor’s hardware and software, including data conversion, code translation,
and testing plans. Include an estimate of the length of “down time” required
for each library converting to the proposed ILS, and state at what point(s)
during the implementation the down time will occur.
8.1.3.2. The vendor must load all MARC records from the various databases that
contain MARC data.
8.1.3.3. The vendor will convert the following types of records from the current
SDLN, and provide proposals for converting equivalent data from Siouxland
Libraries and Rapid City Public Library systems, including statistical
information as it exists. The vendor must list all data that cannot be
converted and loaded into the new system. For each type of data not
convertible, provide written explanations with recommendations of what
should be done.
8.1.3.3.1.
Item circulation records, including copy information
8.1.3.3.2.
Patron records, including links
8.1.3.3.3.
Fine records (including outstanding items and amounts owed)
8.1.3.3.4.
Serials check-in records
8.1.3.3.5.
Serials holdings records
8.1.3.3.6.
Acquisitions order records
8.1.3.3.7.
Acquisitions purchase order records
8.1.3.3.8.
Acquisitions fund records
37
South Dakota Library Network: Request for Proposal, February 2012
8.1.3.3.9.
Department records
8.1.3.3.10.
Vendor records
8.1.3.3.11.
Interlibrary loan borrower records
8.1.3.3.12.
Copyright compliance records
8.1.3.3.13.
Booking records
8.1.3.4.
The following types of links should be maintained:
8.1.3.4.1.
Bib record to/from items, orders, ILL records, serials check-in
records, etc.
8.1.3.4.2.
Patron to charged items
8.1.3.4.3.
Patron to patron accounting
8.1.3.4.4.
Patron to charged items to patron accounting
8.1.3.4.5.
Purchase order/Invoice to order
8.1.3.5. In order to estimate the process and effort required to convert data
currently in the systems of participating libraries to the new system(s), the
vendor must respond to the following:
8.1.3.5.1.
Specify the information required from the participating libraries in
order to carry out the conversion tasks
8.1.3.5.2.
Supply copies of forms typically used to record information
needed for conversion
8.1.3.5.3.
Outline typical steps in the conversion process, focusing
particularly on procedures for library review of test files.
8.1.3.6. The vendor will supply a list of ExLibris/Aleph, SirsiDynix/Horizon and
Innovative/Millennium libraries whose data has been converted for use in the
system.
8.1.3.7. The vendor will supply a list of other libraries whose data have been
converted for use in the system.
8.1.3.8. The vendor must supply detailed costs for conversion of all data from
SDLN’s ExLibris/Aleph system, Siouxland Libraries’ SirsiDynix/Horizon system,
and Rapid City Public Library’s Innovative/Millennium system.
38
South Dakota Library Network: Request for Proposal, February 2012
8.1.3.8.1.
A base conversion cost should be provided for SDLN alone, with
cost estimates for additional conversion of Siouxland Libraries and Rapid
City Public Library provided as separate lines.
8.1.3.8.2.
What database clean-up, if any, is recommended as part of the
conversion process?
8.1.3.8.3.
Does the vendor provide database clean-up service? If so, is
database clean-up part of the base cost of the system? If additional
costs apply, please provide a schedule.
8.2. Customization
8.2.1. Describe the options for customization of the system in a consortial
environment, specifying at what level (vendor, SDLN, local library) each option is
available.
8.2.2. What effect do upgrades and version changes have on customizations made at
both the global/consortium level and at the local library level? (Do customizations
remain in place, or do all settings revert to out-of-the-box/default following each
upgrade?)
8.3. Licensing
8.3.1. If the vendor, whether directly or through a successor or an affiliate shall cease
to be in the information management software business, or if the vendor should be
declared bankrupt by a court of competent jurisdiction, SDLN shall have the right
to access, for its own and sole use only, for maintenance use only, one copy of the
source code to the software proposed hereunder.
8.3.2. List any third-party licenses which are required for the recommended
implementation and use of this system.
9.
Post-implementation
This section relates to post-implementation support and maintenance of the system
supplied by and/or available from the vendor for application software, system software
environment, hardware environment, and user functionality.
9.1. Support and Maintenance
9.1.1. What are normal support business hours for the system, and in what time
zone? What are hours for support outside of business hours, and are there
associated costs involved?
9.1.2. Describe the method of support given normal resolution times by each contact
method supported, noting any associated costs.
39
South Dakota Library Network: Request for Proposal, February 2012
9.1.2.1.
Phone call (800 number)
9.1.2.2.
Email
9.1.2.3.
Other
9.2. Training
9.2.1. Describe a typical post-implementation training program. Identify the number
of training personnel, length of the training, and topics to be covered, as well as
any associated costs.
9.2.1.1. Provide a list of additional training options available and the costs
associated with each.
9.3. Upgrades
9.3.1. Describe the frequency and procedures for system upgrades, indicating if
upgrades and fixes are dynamic or if downtime is required.
9.3.1.1.
Will upgrades be performed by the vendor or by SDLN staff?
9.3.1.2.
What costs will apply to upgrades?
9.3.1.3. If downtime is required for installing upgrades, what is the average length
of time the system is unavailable?
9.3.1.4. Describe the frequency of and cost (if any) of onsite visits by the vendor
for preventative maintenance or site reviews.
9.4. Problem Resolution
9.4.1. Describe options and/or levels of support available for 24x7, 365 problem
resolution, including who can report problems, and how problems are escalated.
9.4.2. Does the vendor provide a single point of contact for problem reporting and
resolution?
9.4.3. What is the average initial response time for expert technical consultation and
software support?
9.4.4.
What is the average time to resolution for critical problems reported?
9.4.5.
What is the average time to resolution for non-critical problems reported?
9.4.6.
What are the costs associated with different levels of problem resolution?
40
South Dakota Library Network: Request for Proposal, February 2012
9.4.7.
Describe the preferred process for problem resolution.
10. Financial Quote
The vendor must supply costs for each item proposed. Hardware, software, and
maintenance costs must be itemized, as SDLN reserves the right to purchase a combination
or software only. In addition, the vendor must supply detailed descriptions and costs for
each conversion service proposed for each of the three systems.
10.1.
The vendor must provide cost estimates, detailed breakdowns and explanatory
comments as appropriate for the following points, indicating a base cost for SDLN only,
with estimated costs for participation by Siouxland Libraries and Rapid City Public
Library provided as separate lines:
10.1.1. Set-up fees (one-time)
10.1.2. Annual fees
10.1.3. System software
10.1.4. Third-party software
10.1.5. System hardware
10.1.6. Database conversion and preparation
10.1.7. Installation services
10.1.8. Training:
10.1.8.1. System operations
10.1.8.2. Profiling
10.1.8.3. For each application
10.1.9. User Documentation
10.1.10.
Hardware maintenance
10.1.11.
Software maintenance
10.1.12.
Telephone support
10.1.13.
Additional modules/Other costs
11. Terms and Conditions
41
South Dakota Library Network: Request for Proposal, February 2012
11.1.
Any contract or agreement resulting from this RFP will include the standard
terms and conditions as listed below, along with any additional terms and conditions as
negotiated by the parties.
11.2.
The State of South Dakota requires that all contractors, vendors, and suppliers
doing business with any State agency, department, or institution, provide a statement
of non-discrimination. By signing and submitting their proposal, the vendor certifies
they do not discriminate in their employment practices with regard to race, color,
creed, religion, age, sex, ancestry, national origin or disability.
11.3.
The Contractor will perform those services described in the Work Plan, which will
be attached to the contract as Exhibit A and incorporated by reference. The
Contractor’s response to this RFP shall be considered part of the Work Plan.
11.4.
The services to be provided under the contract shall commence and terminate
on mutually agreed upon dates. Terms for early termination shall be included in the
agreement as negotiated by the parties.
11.5.
The terms of the agreement shall state whether or not the Contractor will use
State equipment, supplies or facilities. If the Contractor will use State equipment,
supplies or facilities, the scope and conditions of such use will be clearly indicated in
the agreement.
11.6.
Unless otherwise negotiated and agreed upon by the parties, The State will make
payment in compliance with the Prompt Payment Act, SDCL 5-26 for services provided
under the contract.
11.7.
The agreement shall indicate whether or not SDLN shall have the option to
renew the agreement. If a renewal option is specified, SDLN shall have the option to
renew the agreement (unless otherwise modified by a special contract term, condition,
or specification), under the same terms and conditions, for one (1) year intervals.
Notice of intent to renew shall be given by SDLN to the Contractor as mutually agreed
upon prior to the end of the current contract term. If the notice of intent to renew is
given, the Agreement shall renew unless terminated by either party pursuant to the
Termination Provision of the Agreement.
11.8.
The Contractor agrees to indemnify and hold the State of South Dakota, its
officers, agents and employees, harmless from and against any and all actions, suits,
damages, liability or other proceedings that may arise as the result of performing
services hereunder. This section does not require the Contractor to be responsible for
or defend against claims or damages arising solely from errors or omissions of the
State, its officers, agents and employees.
11.9.
The Contractor, at all times during the term of the Agreement, shall obtain and
maintain in force insurance coverage of the types and with the limits as follows:
42
South Dakota Library Network: Request for Proposal, February 2012
11.9.1. Commercial General Liability Insurance:
The Contractor shall maintain occurrence based commercial general liability
insurance or equivalent form with a limit of not less than $1,000,000 for each
occurrence and $2,000,000 aggregate.
11.9.2. Worker’s Compensation Insurance:
The Contractor shall procure and maintain workers’ compensation and employers’
liability insurance as required by South Dakota law.
11.10.
Before beginning work under the Agreement, the Contractor shall furnish SDLN
with properly executed Certificates of Insurance which shall clearly evidence all
insurance required in this Agreement and which provide that such insurance may not
be canceled, except on 30 days’ prior written notice to SDLN. The Contractor shall
furnish copies of insurance policies if requested by SDLN.
11.11.
While performing services under agreement with SDLN, the Contractor is an
independent contractor and not an officer, agent, or employee of the State of South
Dakota.
11.12.
Contractor agrees to report to SDLN any event encountered in the course of
performance of this Agreement which results in injury, or death, to the person or
property of third parties, or which may otherwise subject Contractor or SDLN to
liability. Contractor shall report any such event to SDLN immediately upon discovery.
Contractor’s obligation under this section shall only be to report the occurrence of any
event to SDLN and to make any other report provided for by their duties or applicable
law. Contractor’s obligation to report shall not require disclosure of any information
subject to privilege or confidentiality under law (e.g., attorney-client communications).
Reporting to SDLN under this section shall not excuse or satisfy any obligation of
Contractor to report any event to law enforcement or other entities under the
requirement of any applicable law.
11.13.
The Agreement may be terminated by either party by providing written notice as
mutually agreed and specified in the Agreement. In the event the Contractor breaches
any of the terms or conditions of the Agreement, the Agreement may be terminated by
SDLN at any time with or without notice. If termination for such a default is effected by
SDLN, any payments due to Contractor at the time of termination may be adjusted to
cover any additional costs to SDLN because of Contractor’s default. Upon termination
SDLN may take over the work and may award another party an agreement to complete
the work under the Agreement. If after SDLN termination for a default by Contractor it
is determined that Contractor was not at fault, then the Contractor shall be paid for
eligible services rendered and expenses incurred up to the date of termination.
11.14.
The Agreement depends upon the continued availability of appropriated funds
and expenditure authority from the Legislature for the intended purpose. If for any
43
South Dakota Library Network: Request for Proposal, February 2012
reason the Legislature fails to appropriate funds or grant expenditure authority, or
funds become unavailable by operation of law or federal funds reductions, the
Agreement will be terminated by SDLN. Termination for any of these reasons is not a
default by SDLN nor does it give rise to a claim against SDLN.
11.15.
The Agreement may not be assigned without the express prior written consent
of SDLN. This Agreement may not be amended except in writing, which writing shall be
expressly identified as a part thereof, and be signed by an authorized representative of
each of the parties thereto.
11.16.
The Agreement shall be governed by and construed in accordance with the laws
of the State of South Dakota. Any lawsuit pertaining to or affecting the Agreement shall
be venued in Circuit Court, Sixth Judicial Circuit, Hughes County, South Dakota.
11.17.
The Contractor will comply with all federal, state and local laws, regulations,
ordinances, guidelines, permits and requirements applicable to providing services
pursuant to the Agreement, and will be solely responsible for obtaining current
information on such requirements.
11.18.
In the event that any court of competent jurisdiction shall hold any provision of
the Agreement unenforceable or invalid; such holding shall not invalidate or render
unenforceable any other provision thereof.
11.19.
All other prior discussions, communications and representations concerning the
subject matter of the Agreement are superseded by the terms of the Agreement, and
except as specifically provided therein, the Agreement constitutes the entire
agreement with respect to the subject matter thereof.
11.20.
Any notice or other communication required under the Agreement shall be in
writing and sent to the appropriate address and individuals indicated in the Agreement,
or such authorized designees as either party may from time to time designate in
writing. Notices or communications to or between the parties shall be deemed to have
been delivered when mailed by first class mail, provided that notice of default or
termination shall be sent by registered or certified mail, or, if personally delivered,
when received by such party.
11.21.
The Contractor may not use subcontractors to perform the services described in
the Agreement without the express prior written consent of SDLN. The Contractor will
include provisions in its subcontracts requiring its subcontractors to comply with the
applicable provisions of the Agreement, to indemnify the State, and to provide
insurance coverage for the benefit of the State in a manner consistent with the
Agreement. The Contractor will cause its subcontractors, agents, and employees to
comply, with applicable federal, state and local laws, regulations, ordinances,
guidelines, permits and requirements and will adopt such review and inspection
procedures as are necessary to assure such compliance.
44
South Dakota Library Network: Request for Proposal, February 2012
45
South Dakota Library Network: Request for Proposal, February 2012
Appendix A: SDLN Current System and Operational Environment
SDLN currently uses the ExLibris Aleph (v.20.01/rep change 3556) ILS in combination with
Serials Solutions’ AquaBrowser discovery tool. GoogleBooks is used to provide cover images
and supplemental content detail.
Aleph operates on the Red Hat Enterprise Linux 5.4 64-bit system. SDLN has two HP ProLiant
DL585 G5 servers for the Aleph production and test environments, and two HP ProLiant DL585
G6 servers for the Oracle production and test environments.
Physical security: servers are contained in SDLN’s locked data center inside locked server racks.
Electronic security: protected by redundant Cisco ASA 5510 security appliances. Regular OS and
Firmware updates are applied to update system.
Aleph’s x-server integrated with Serials Solutions’ AquaBrowser is used to provide
authentication for licensed databases. An in-house authentication server verifies valid accounts
against global patron records.
Number of SDLN member libraries currently using each Aleph system functional module:
Configured Libraries 189
OPAC
Circulation
Interlibrary Loan (ILL)
Serials
Acquisitions
Inventory
Cataloging/Authority Control
Available to all libraries
54
130
17
17
Available to full member libraries - not tracked
130
FTE support staff for system management and administration: 6 FTE
46
South Dakota Library Network: Request for Proposal, February 2012
Appendix B: Siouxland Libraries Current System and Operational Environment
Siouxland Libraries uses the SirsiDynix Horizon 7.51 (Sybase 15 on Red Hat Linux) system, and
third-party telephone messaging system provided by Talking Tech through SirsiDynix. Alpha-G
has been used to provide customized reports and notices, and the SD Debt Collect module is
used with Unique Collection Agency.
Servers:
Horizon: Sybase 15 on Red Hat Linux
OPAC/HIP: Dell Windows
Webreporter (reporting server): Dell Windows
Telephone messaging: Dell Windows
SIP server (glorified PC): Windows
Servers are located in the library’s computer room.
Physical security: City of Sioux Falls IT staff provides overall network and security support.
Siouxland Libraries uses the following functional modules:
OPAC
Circulation
Serials
Acquisitions
ILL (currently implementing ILLIAD)
Inventory
Authority Control (with Marcive support)
Telephone messaging
Webreporter
System management: 1.5 FTE staff
47
South Dakota Library Network: Request for Proposal, February 2012
Appendix C: Rapid City Public Library
Current System Information and Operational Environment
Rapid City Public Library uses Innovative’s Millennium (2009b, upgrading to v2011 by March
2012). Third party products currently in use include the Envisionware PC Reservation system,
Envisionware LPT: One Print Client, and Novelist Select.
Servers: RCPL has several on-site servers for web applications, PC reservations, and other
services.
Physical security and internal server back-ups: provided by City of Rapid City’s IT staff.
Rapid City Public Library uses the following functional modules:
OPAC
Circulation
Serials
Acquisitions
Serials
Interlibrary loan
Inventory (implementing 2012)
System management: 1 FTE primary support, with assistance from five other staff in support
roles.
48
South Dakota Library Network: Request for Proposal, February 2012
Appendix D: Transaction Records & Activity Levels
Transaction Records: 2011
Bibliographic
SDLN
Siouxland Libraries
Rapid City Public Libraries
4,359,778
166,000
153,285
5,432,831
374,625 (all)
173,600
Records
Bar-coded items
(circulation
345,070 (Siouxland
records)
only)
Patron records
263,758
134,140
55,801
Serials – current
11,720
972 (all)
200
subscription
931 (Siouxland only)
records
Acquisitions:
121,775
current order
Purchase Orders: 550
Not tracked
Fund Records: 84
records
Vendor Records
Not tracked
950 (since 2004)
21
Authority Records
Not tracked
480,665 total
Not tracked
171,136 MARC
authority
49
South Dakota Library Network: Request for Proposal, February 2012
Transaction activity levels for 2011:
SDLN
Siouxland Libraries
Rapid City Public
Libraries
OPAC
Not tracked
2,973,393
Not tracked
Circulation
1,715,823
1,963,918
1,251,000
Not tracked
Not tracked
transactions
Serials check-
170,585
ins
(Est: 3-4000)
Cataloging
New: 3,651
transactions
Updates: 272,769
Not Tracked
23,377
Siouxland Libraries
Rapid City Public
Total: 27,6420
Bibliographic Records Added
SDLN
Library
2007
22,742
No records
Unavailable due to 2010
migration
2008
(115,167)
No records
Unavailable due to 2010
migration
2009
49,631
13,000
Unavailable due to 2010
migration
2010
(36,627)
12,500
8,395
2011
88,860
15,000
14,521
50
South Dakota Library Network: Request for Proposal, February 2012
Patron Records Added
SDLN
Siouxland Libraries
Rapid City Public Library
2007
34,056
10,329
5,671
2008
4,771
10,067
6,131
2009
17,416
9,508
6,189
2010
(27,048)
9,098
5,764
2011
(53,372)
10,129
6,131
Items checked out/in
SDLN
Siouxland Libraries
Rapid City Public
LIbraries
2007
Checked
Checked
Checked
out
in
out
1,724,626
1,743,669
1,614,216
Checked in
1,610,179
Checked
Checked
out
in
747,000
Not
tracked
2008
1,724,216
1,735,499
1,711,237
1,692,380
858,000
Not
tracked
2009
1,820,134
1,808,204
1,835,501
1,814,249
1,018,000
Not
tracked
2010
1,803,352
1,802,356
1,906,372
1,874,139
1,182,000
Not
tracked
2011
1,715,823
1,714,854
1,963,918
1,900,937
1,251,000
Not
tracked
51
South Dakota Library Network: Request for Proposal, February 2012
Siouxland Libraries – Yearly Catalog and Website Use
2011 Total
Library Catalog
Patron Logins
This Year
Last Year
2011
2010
375,125
2 Years
Ago
2009
3 Years
Ago
2008
4 Years
Ago
2007
5 Years
Ago
2006
369,013
1.66%
323,145
254,338
187,694
133,774
2,347
-14.32%
2,082
1,622
1,739
1,506
Patron Updates
Holds placed by
patron
284,675
291,384
-2.30%
256,149
194,849
131,566
97,061
Renewals
186,860
172,630
8.24%
148,931
101,697
62,996
41,329
Searches
2,124,722
3,023,561
-29.73%
3,785,871
2,476,151
1,359,120
1,290,493
3,858,935
-22.95%
4,516,178
3,028,657
1,743,115
1,564,163
805,384
743,830
8.28%
661,769
255,550
190,399
145,871
90,532
88,850
1.89%
75,234
24,061
25,027
19,122
895,916
832,680
7.59%
737,003
279,611
215,426
164,993
TOTAL CATALOG USE
2,011
Percent
Change
2,973,393
Website visits
www.siouxlandlib.org
www.slkids.org
TOTAL VISITS
52
South Dakota Library Network: Request for Proposal, February 2012
Appendix E: SDLN Mission and Vision
Mission
Vision
SDLN
Today
SDLN: Connecting South Dakota's libraries
SDLN is the framework through which member libraries connect with each other to
optimize shared resources and services for their communities.
SDLN offers its member libraries automated systems enabling them to deliver
creative library services in a cost effective manner. Currently SDLN:
 Offers members a common computer system (ILS)
 Facilitates resource sharing (ILL) among libraries
 Provides database access and support
 Coordinates a single point of technical support
 Features friendly, helpful, knowledgeable staff
 Develops training opportunities (From SDLN & other members)
 Allows economy of scale/low cost group purchasing
 Promotes member-driven governance
 Fosters multi-type cooperation including uniform services statewide –
encouraging lifelong literacy
 Provides special services – email, web hosting, authentication, patron loads
 Enables local customization, policies, control, websites
 Communicates directly with member libraries
53
South Dakota Library Network: Request for Proposal, February 2012
Appendix F: SDLN Member Libraries
SDLN Full Member Libraries – 30 December 2011
Academic Libraries
Beulah Williams Library (NSU)
NSU Reading Clinic (NRC)
Instructional Technology Center (ITC)
Devereaux Library (SMT)
Black Hills State University E.Y Berry Library - Learning Center (BHS)
South Dakota State University H.M Briggs Library (SDB)
I.D Weeks Library & Lommen Health Sciences Library (USD)
University of South Dakota McKusick Law Library (SDL)
Karl E. Mundt Library (DSU)
Lake Area Technical Institute (LTI)
Dakota Wesleyan UniversityMcGovern Library (SDW)
University of Sioux Falls Mears Library (SDF)
Augustana College Mikkelsen Library & Sioux Falls Seminary (SDA)
Center for Western Studies (CWS)
Mount Marty College Library (MMC)
Oglala Lakota College Resource Center (SDO)
Presentation College Library (PRN)
Sinte Gleska University Library (SGC)
Southeast Technical Institute Library (STI)
National American University Thomas Jefferson Library (SDT)
Western Dakota Technical Institute (WDT)
Public Libraries
Alexander Mitchell Public Library (AML)
Brookings Public Library (SBR)
Deadwood Public Library (DWD)
Grace Balloch Memorial Library (SPF)
Huron Public Library (HPL)
Keystone Town Library (KST)
Phoebe Apperson Hearst Library Lead (LEA)
Madison Public Library (MPL)
Mitchell Public Library (MIT)
Plankinton City Library (PLK)
Rawlins Municipal Library Pierre (RPL)
Siouxland Libraries (SDD)
South Dakota State Library (SDS)
54
South Dakota Library Network: Request for Proposal, February 2012
Sturgis Public Library (STG)
Vermillion Public Library (LVE)
Wall Public Library (WAL)
Watertown Regional Library (WAT)
Whitewood Public Library (WWD)
Yankton Community Library (YCL)
School Libraries
Chamberlain High School Dist 07-1 (CHS)
Chamberlain Elementary School (CES)
Cheyenne Eagle Butte High School (CEB)
Grant-Deuel School District 25-3 (GDS)
Huron High School (HHS)
Little Wound School Library (LWS)
Mount Vernon School Library (MVS)
Spearfish High School (SHS)
Todd County High School / District (TCH)
Todd South Elementary (TCS)
Todd County Middle School (TCM)
Todd County Curriculum Center (TCC)
Watertown High School (WTN)
Wolsey School Library (WOL)
Yankton High School (YHS)
Special Libraries
Avera McKennan Hospital (AVE)
Avera Sacred Heart Hospital Medical Library (SHH)
Don Lee Kulow Memorial Library (GIE)
Wegner Health Science Libraries (WEG)
South Dakota State Archives (SDH)
55
South Dakota Library Network: Request for Proposal, February 2012
SDLN Remote Member Libraries – 20 December 2011
A.H Brown Public Library
Edmunds Central Library
Aberdeen Central High School Library
Elk Point / Jefferson School Library
Agar-Blunt-Onida School District Library
Elk Point Community Library
Alcester School Community Library
Elkton School Library
Andes Central High School Library
Elkton Community Library
Armour School Library
Emma Burnham Public Library
Avon School Library
Enemy Swim Day School
Baltic High School Library
Eureka High School Library
Belle Fourche Public Library
Faith Public/School Library
Beresford Public Library
Faulk County Library
Beresford School District Library
Faulkton School Library
Bison School Library
Federal Prison Camp Library
Box Elder/ Douglas School
Flandreau High School Library
Britton - Hecla School Library
Flandreau Indian School Library
Britton Public Library
Freeman Public Library
Brookings High School Library
Garreston School Library
Burke High School Library
Georgia Morse Middle School
Canton Middle / High School Library
Gettysburg High School Library
Canton Public Library
Grant County Public Library
Castlewood School Library
Gregory Public Library
Centerville Community Library
Groton High School Library
Centerville School Library
Hakkon Community Library
Chester High School Library
Haakon School Dist 27-1 Library
Clark Jr/Sr High School Library
Hamlin High School
Colman-Egan School Library
Hanson School Library
Corsica School Library
Harrisburg High School Library
Cozard Memorial Library
Hazel L Meyer Memorial Library
Crow Creek Tribal Schools
Highmore School Library K-12
Custer County Library
Hill City Schools
Custer High School Library
Hill City Community Library
Dakota Valley Schools
Hot Springs Schools
Dell Rapids Carnegie Public Library
Hoven High School Library
Dell Rapids Public School Library
Howard High School Library
Deubrook School Library
Huron High School Library
Dr Paul Bunker Medical Library
Hyde County Library
Dupree School Library
Ipswich High School Library
Jackson County Library
Sioux Falls School District
Jones County High School Library
Sisseton Memorial Library
Kimball High School Library
Sisseton Wahpeton College Library
Lead High School Library
St Francis Indian School Library
Lemmon High School Library
Stanley County High School Library
Lennox High School
Sunshine Bible Academy Library
56
South Dakota Library Network: Request for Proposal, February 2012
Leola School Library
Lower Brule Community College Library
Lyman School District Libraries
Madison Central Schools
Marion High School Library
McCook Central School
McIntosh High School Library
McLaughlin Dist 15-2 Elem Library
McLaughlin Public Library
Milbank High School Library
Miller High School Library
Mitchell School District Library
Mitchell Technical Institute Library
Mobridge High School Library
Montrose School Library
Newell High School Library
North Sioux City Community Library
Northwestern School Library Coord
O'Gorman High School Library
Parker High School Library
Pine Ridge High School Library
Platte High School Library
Potter County Free Public Library
Rapid City Public Library
Redfield Carnegie Library
Redfield Jr / Sr High School Library
Riggs High School Library
Roncalli High School Library
Rosholt High School Library
Scotland High School / Community Library
SD Human Services Center
Selby Area / School Library
Timber Lake High School Library
Tiospa Zina Tribal School Library
Tiospaye Topa School Library
Tripp County Library
Tri-Valley Media Center
Tulare School District Library
VA Black Hills Health Care System
Vermillion High School Library
Viborg Public Library
Wagner Public Library
Wagner School Library
Wall High School Library
Waubay Public Library
Webster Public Library
Wessington Springs School District
White River High School Library
Willow Lake School Library
Winner High School Library
Woonsocket High School Library
57