FROM BIBFRAME TO THE CLOUD

The Future of the ILS

PresentersElayna Turner

■ Librarian/ILS Administrator for the Gloucester County Library System

■ ILS Experience– Horizon (SirsiDynix)– Symphony (SirsiDynix)

■ eturner@gcls.org

Tim Dewysockie■ Application Specialist for Rowan University Libraries

■ ILS Experience– Horizon (SirsiDynix)– Polaris (Innovative)– Voyager (ExLibris)

■ dewysockie@rowan.edu

Where We Are: The Integrated Library System (ILS)

Where We’re Going: ■ Shaped by current technology landscape

– Software as a Service (SaaS)

– API’s/Web Services

– Open source software

■ Shaped by libraries’ needs

– Differs by type of library

Software as a Service:

API’s:

Public Library Considerations

■ Focus on circulation of physical materials

■ Focus on user experience

■ Focus on electronic resources

Academic Library Considerations■ Focus on user experience

■ Focus on electronic resources

■ Problem: Traditional ILS was designed for print

■ Result: Products have been developed to fill this void

Where We’re Going: Trends in Library Technology■ The “Future” of the ILS:

– Library Services Platforms (LSPs)

– “Hybrid” Solutions

– Open Source Solutions

■ Related developments in library technology

– Discovery layers

– BIBFRAME/Linked Data Integration

Library Services Platforms■ Software as a Service (SaaS)

■ Built on API’s/web services

■ Designed to manage multiple types of resources from single application

■ Examples

– Alma (ExLibris),

– OCLC WorldShare

– Insignia Library System

OCLC WorldShare:

“Hybrid” Solutions■ Hybrid of ILS and LSP

■ Builds on existing ILS technology

– Still dependant on ILS

– Can be self-hosted or SaaS

■ Examples

– Sierra (Innovative),

– Symphony or Horizon &

BLUEcloud (SirsiDynix)

Example: SirsiDynix BLUEcloud LSP

Open Source Solutions■ Predates development of LSP’s

■ Alternative to proprietary solutions

■ Development community

■ Note: Open source solutions are neither free nor cheap

■ Examples– Koha, Evergreen

Example: Koha

Related Library Technology

Developments

Where We Are:The Online Public Access Catalog (OPAC)

Where We’re Going: Discovery Layers■ Index-based discovery layers

– Central index: crosswalk data into single shared schema, then index it

■ API’s

■ Possible uses

– Use in conjunction with traditional OPAC, replace existing OPAC

Discovery Layers■ Positive

– Integrates previously siloed resources into single search interface

■ Negative

– Results set too large, too imprecise

■ Proprietary

– Summon (ProQuest), EDS (EBSCO), Enterprise (SirsiDynix), Primo (ExLibris)

■ Open source

– VuFind, Blacklight

– Apache Solr index

Bento Box

■ Done using open source tools; no currently available proprietary solutions

■ Positive: User does not have to choose what type of material to search

■ Negative: User initially sees less results; must click a source to see more

BIBFRAME and Linked Data Integration

MARC

BIBFRAME and Linked Data Integration

BIBFRAME

Bibliographic Records in a Google Search

BIBFRAME & Linked Data Integration

■ Many ILS’s are working to allow linked data integration to make library materials

more discoverable

■ This means taking collections out of traditional catalogs and making them findable

on the web.

■ Extracting MARC data and outputting it to BIBFRAME

■ Examples: BLUEcloud Visibility (SirsiDynix), Innovative Linked Data, EBSCO Linked

Library Service

Questions For the Future■ What needs are not addressed by these trends in library technology?

– Academic libraries: integration with learning management systems (LMS’s)?

■ Will traditional ILS’s coexist with LSP’s, or will LSP’s become the new standard?

■ Do these new trends create problems that didn’t exist before? – Privacy and security concerns with cloud-based applications

■ Will the decoupling of the user interface (OPAC/discovery layer)from the ILS/LSP become the norm?

Thank YouQuestions/Comments:

Elayna Turner - eturner@gcls.org

Tim Dewysockie - dewysockie@rowan.edu