Kuali OLE Overview

1
Kuali OLE Overview
John Little ILS Support Section
Head John.Little_at_Duke.edu
Slides by Robert McDonald rhmcdona_at_indiana.edu
2
Agenda

• Open Library Environment Overview
• Paths for NextGen ILS
• Overview of Proposed Kuali OLE Build Plan
• Timeline
• Partners
• Mellon Funding
• Governance
• Questions

3
Open Library Environment (OLE)

• What is the OLE Project?
• Community source alternative to current ILS
• International participation from 15 libraries and
  consortia
• Planning phase September 08 July 09

4
Why OLE Now?

• Current ILS products are inadequate
• Growing need for library systems to interact with
  other enterprise systems
• Vendor consolidation constrains choices
• Libraries need to control their own destinies

5
OLE Principles

• Flexibility
• Community Ownership
• Service Oriented Architecture
• Enterprise-Level Integration
• Efficiency
• Sustainability

6
OLE Regional Design Workshops

• Regional Design Workshops
• Did you or your staff attend a workshop?
• 350 people from 95 institutions!
• Who attended?

7
OLE Final Report and Prospectus

• OLE Final Report
• http//oleproject.org/final-ole-project-report/
• Prospectus for Interested Build Partners

8
Legacy ILS
Legacy ILS Functionality
Public User Interface
Circulation
Acquisitions
Vendor Based ePurchasing
Functional modules
Cataloging
Serials
Vendor Based Metadata Enhancement
Data Stores
Staff Interfaces
9
Legacy ILS
Legacy ILS FunctionalityeContentModuleAdvan
ced DiscoveryInterface
Learning Mgmt./Campus Portal Feeds
Proxy/VPN for eContent Access
OpenURL Linking
Federated Search/ Advanced Discovery
Electronic Resource Mgmt. System
Unified Workflow Interface for Staff
10
NextGen ILS
NextGen Search System/Faceted Search
exports and reformats MARC from ILS
Web 2.0 Engine
Raw MARC data
Indices
Parse text files
Flat text files
HTTP
HTTP
User Interface
11
Paths for NextGen ILS at IU

• OCLC Path
• Ex Libris Path
• Kuali OLE Path (Community Source Software)
• Other Open Source or Community Source Path

12
OCLC Path (Web-based Management)

• Raise 100K-150K per year ongoing
• No new staff
• Possible three years till migration
• Need to be a working partner
• Total - 250K per year ongoing

13
Ex Libris Path (URM)

• Raise 200K-250K per year
• No new staff
• Two years till migration
• Princeton, Purdue University, Boston College and
  Katholieke Universiteit are Partners
• Total 350K per year ongoing

14
Kuali OLE Path (IU)

• 319K over two years (Founding Partner Cash
  Investment)
• 50K-100K in training 100K
• No new staff
• Total Approx 500K over three years
• Possible reinvestment of current ILS licensing
  140K per year
• Investment in OLE is recovered in 4 years after
  migration
• Mellon Investment makes this path possible

15
Kuali OLE Build Plan

• Mellon Foundation Matching Funding
• Two Year Timeline
• Year 1 Deliverables (Will Focus on one of these)
• A fully functioning core of services and
  framework the OLE Core Components
• Management of Electronic Resources Services
• Leased eContent
• Owned eContent
• Peer Resource Sharing Services
• Sharing content peer to peer
• Sharing workflow consortial
• Acquisitions Services
• Will be the same as MER
• Will add EDI/Direct MER

16
Kuali OLE Build Plan

• Two Year Timeline
• Year 2 Deliverables
• Integrations
• EDI/Local ERP
• Discovery Interface (broker for multi-discovery
  use)
• Data Migration Services
• Registries and Utilities
• Orchestrations
• define workflows to match relevant, local
  resource set
• determine optimum dataflows including effort
  distribution and sharing
• Functional Scope
• meet the business needs of a research or academic
  library
• allow current ILS to be turned off

17
Build Plan Recommendations

• Governance Kuali Foundation
• Service Oriented Architecture Framework/Java
• Use Existing Middleware Kuali Rice
• Use Existing Discovery Interfaces
• VueFind
• Blacklight
• WorldCat Local
• Offshore Coding Kuali Coeus and Sophie

18
Open Discovery for Many Discovery Systems
Blacklight Example at UVa
19
Kuali OLE Build Partnership

• Indiana University (Lead School Kuali OLE)
• Florida Consortium (FC) (University of Florida
  Lead)
• Lehigh University
• Triangle Research Libraries Network
• Duke University
• North Carolina State University
• University of Chicago
• University of Maryland
• University of Michigan
• University of Pennsylvania

20
Florida Consortium

• University of Florida (Lead School Florida
  Consortium)
• Florida State University
• Florida Center for Library Automation
• New College
• University of Central Florida
• University of South Florida
• Florida International University
• Rollins College
• University of Miami

21
Kuali OLE Collaborations

• Kuali Foundation representation on foundation
  and rice boards and technical groups.
• Fluid Project Fluid will be a joint partner in
  the interface design for the end-user of Kuali
  OLE.
• CollectionSpace CollectionSpace will share
  knowledge about each others project as well as
  representatives to technical and functional
  councils.
• NISO ERMI Working Group Kuali OLE will have a
  representative to this group.
• Astea Solutions Consultants on software coding
  development.

22
(No Transcript)
23
Kuali OLE Governance
Kuali Foundation
Kuali Rice
Kuali OLE Board
Functional Council
Technical Council
ProjectManager
24
Academic Enterprise
25
ERP
Library
PCH
HR
FIN
ER
Acq
P2P
KNS/KSB
KNS/KSB
Library as Academic Enterprise Partner
26
Questions and Discussion

• Kuali Open Library Environment (OLE)