What we’ve covered so far

Computer history Internet history HTML and web content Information retrieval Search engines And now it’s time for...

Library Information Systems

Integrated Library System (ILS)—AKA Library Automation Systems or Integrated Online Library Systems (IOLS)– OPACS (online public access catalogs)

Online databases Digital Libraries E-book & E-journals

Library Information Systems

Ralph H. Parker in 1968 identifies LIS:

“as not only ‘automating’ existing processes within libraries (such as circulation, cataloging, and so forth) but also including access to materials not held by the library but available in electronic form”

(from Dr. K’s article)

Library Information Systems

Why Automate On Functions & Functionality Origins of LIS Management Considerations Trends & Issues within LIS

Why Libraries Use Technology

Modernization (‘60s & ‘70s) Patron Services (’80s & ’90s) Transformation (’90s up to today & tomorrow)

– Integration – Interoperability

Modernization

To increase efficiency of internal operations (internal workflow & sharing cataloging data)

To cope with increasing demands for services To reduce staff or prevent staff increases To allow more activities to be performed by

clerical and paraprofessional staff

Patron Services

To provide new forms of old services (electronic access using OPACs)

To improve access to existing services (remote login, etc)

Meeting end user expectations

Transformation

To provide new (increasingly digital) information services– Document Delivery– Digital Libraries – databases, e-books, e-journals,

web resources– New technologies (Wireless, RFID)

Functions & Functionality Of LIS

First came technical services – shared cataloging & item processing—some early ordering/acquisitions functionality—early electronic catalogs with only limited functionality

Next circulation control– check in/out, to overdues, requests/reserves—kept evolving

Then OPACs – Now adding in online DBs, Document Delivery, web, &

digital libraries

Costs Associated with LIS

Cost to prepare and make purchase decision Final contract cost that could include: Hardware,

software, telecommunications Maintenance that could include: Hardware, software,

training, conversion Costs to prepare site for implementation (both

hardware & software) Ongoing costs that could include: maintenance

contract, needed expansion, upgrades, licensing fees, training, staffing, cost to replace

Origins of LIS

1936 R.H. Parker—Punched cards for circulation 1960s Use of computers to automate technical services

(proprietary solutions with emphasis on SYSTEMS) 1965 OCLC explores standards for bibliographic records 1969 MARC record established (Bibliographic Information

Exchange) 1967-70 Bibliographic utilities (OCLC, RLN, WLN) 1971 First turnkey system CLSI (circ. control) –emphasis on

FUNCTIONALITY & PROPRIETARY SYSTEMS

Origins of LIS (2)

1974 Library automation marketplace reaches $50 million; online databases become available

1975 Data Research begins in St. Louis – UM Libraries get OCLC services

1981 CLSI markets first OPAC (online public access catalog)

1983 UM Libraries bring up LUMIN—online card catalog

Origins of LIS (3)

1981-1990 LIS vendors focus on snappy OPACs and less glamorous technical services functionalities

1986 CD-ROM boom in catalogs –beginning of LANS being applied in libraries

1988 Z39.50 (interoperability standard) established – beginning of OPEN SYSTEMS

1990s LIS peaks at $500 million– Rapid introduction of PCs—Market segmentation by library type—beginning of Internet—Early development of Digital Libraries – focus on USERS

Origins of LIS (4)

mid-1990s Growth in role of Web/Internet LIS vendor mergers and failures

– CLSI merges into GEAC– DRA buys INLEX and will then be bought by SIRSI– Ameritech buys Dynic & Notis– New companies Endeavor & ExLibris– Libraries begin to purchase their ‘second’ system

Origins of LIS (5)

Late 1990s & early 2000s rise of electronic resources, serials/acquisitions, digital libraries, wireless—products become more graphical and integrated – growth of offsite users

LIS Trends

Impact of the Web on end users Explosion of resources of all types –desire to integrate

all of them (moving from LPS to LIS) Growth of standards (MARC, DC, XML) Growth of portals (vendors offering one interface to

search local and global resources—movement towards providing these products to their current customers AND as standalone products)

Vendors seeking to id new needs and meet them– SIRSI/CIPA and use of ERM and FRBR

Today we want our ILS to

Deliver comprehensive automation efficiently Handle work that happens within a library’s

walls Deliver services to users outside the library via

the Web Use standards to interact with other systems Vendors to stay in front of curve (also our

responsibility)

The marketplace

2002 – Capture the migrating customer 2003 – Competition heats up 2004 – Migration down, innovation up 2005 – Gradual evolution 2006 – Reshuffling the deck

A Successful LIS Selection Process

Focus on the process and people not the technology

Build management support (also staff & community)—keep everyone informed

Understand the library’s real needs Continually train and develop your staff and

patrons on proper use of system

On Selection & Management

Keep in mind your library BUT look at other libraries—think about both today & tomorrow in your library, but realize a decision to purchase an LIS is not necessarily a long term relationship (but it might be)

Do what you can to foster a positive attitude about change within your organization (changing to this LIS will be good for the library, our users and staff because…)

RFP (Request for proposal)

Overview statement of problems & needs for procurement

Section of definite technical requirements & information Requirements for managing & implementing the project Requests for vendor qualifications and references Guidelines for legal and licensing requirements Appendices with library’s relevant information such as

network diagrams, technical requirements, and project plan outlines

Value of thorough, consistent, documented evaluation

Will You Always Need an RFP?—Other Ideas

Dual RFPs – one to meet purchasing requirements plus second document with more ‘practical’ questions

Or RFI, RFQ, etc. Vendor demos Web examples – many libraries now assuming basic

functionality and using selection process to id best vendor (or group of vendors) to meet their unique and/or new needs

Today’s vendors

See listings at LibraryTechnology.org (check out automation

history timeline)

Libdex.com (search by vendor)

One Vendor–DRA (Data Research Assoc.)

1975 – Data Research Associates formed for $30,000 Late ’70s-’80s – turnkey systems sold Mid-80s – OPAC added/ Migrations begin 1993/94 – DRA acquires INLEX & multiLIS (UNIX &

language support) 1997 – DRA Web2 1999 – Taos (client server app)—gone by 2002 2001 – Sirsi acquires DRA (Mike gets $50 million) &

2005 acquires Dynix 2006 – Sirsi/Dynix acquired by equity investment group