1. Presenters: Andy Sarno
Beth Camden
Michael Winkler

2. • Overview of Kuali OLE
• Review of our First Year
• Our Innovative Technology
• Our Second Year…and Beyond

3. • Kuali OLE is a enterprise approach to Library
Management
• Partners & Mellon
• 2 year project starting in July 2010
• We are at year one

4. • Community-source library management system
• Next-gen technology environment
• Re-examine library business operations
• Break away from print-based workflows
• Reflect the changing nature of library materials
and new approaches to scholarly work
• Integrate with enterprise-level systems

7. • Hire and Engage Kuali OLE Core Team
• Engage Software Development Contract – HTC Global Services
• Set Kuali OLE Agile Framework and Timelines – Develop User Story
Process
• Form Specification Writing Teams based on major functions
• Develop Year 1 Prototype Kuali OLE 0.2 – Demo at CNI Spring 2011
Member Meeting
• http://www.kuali.org/ole/demo/spring11/cni
• Set Agenda for Year 2 Software Release
• Leading to our first public release here at Kuali Days – Version 0.3

8. Features Research
Describe
Select & Acquire • Apache Jackrabbit™ • Partner finance systems
• Kuali® Financial System v4 document repository for • Partner identity
management systems
Version 0.3 Release
Core metadata
• Extensive library business • Support multiple descriptive • Document store
November 2011
process analysis metadata formats relationship linking
• Kuali® Rice 1.1 for workflow • Define document types – • Data dependencies for
• Supply chain automation bibliographic, localization, Deliver policies
• Vendor firm order ingest enhancement • Metadata editor
• Manual invoice entry • 5 million bibliographic, 5 architecture
• Enhanced Pre-order million item documents • Relationship between
Selection loaded bibliographic, holding, and
• Purchase discrete item item-level records
• Requisition Searching • Serials receipts and
• Purchase Order • Faceted search for predictive check-in
• Encumber funds descriptive metadata
• Receive item • Transactional metadata
search with linked descriptive
metadata
Implementation of Core Technologies

9. • Service Layer Architecture – to provide
isolation of concerns & to improve flexibility
• Kuali Technologies – to provide ready-built
technologies for development, messaging,
coordination, & financials
• Standard interfaces (when it makes sense) – to
provide open & predictable pathways in & out
• Multiple data stores – to provide purpose-built
data repositories that best model interactions &
provide some future-proofing

10. Amazon EC Cloud
Vendors Utilities Users
Interfaces
External
IdM
Data
EDIFact ONIX-PL Standard NCIP ILS-DI
Interchange
s
Workflows
Business
Logic &
Service Bus: AuthN/AuthZ, Queues, Alerts, & Messaging Service
Registry
Architectur
Storage
Descriptive Relationship
Transaction
e
Data - Data -
al Data - KFS DocStore RDBMS

11. • Roadmap for Version 1.0
• Partner Implementation Strategies
• Developing GOKb Sister Project
• Sustaining & Growing our Partnership

12. Features Research
Select & Acquire Describe Impact on Rice 2.0
• Ingest order records • Metadata management • Installation & Training
• Fund accounting • Localization & • Build Data exchange
• Payment with ERP enhancement between Rice 1.x and
metadata
Version 0.6 Release
Rice 2.0
Deliver architecture OR
• Patron infrastructure • Linked data
March 2012
Map/Re-factor KFS 4
• Design Patron integration Core Code to Rice 2.0
classification • Document Store
linking • Convert code based on
Manage Entity Relationship • Ingest & overlay Rice 1.x to Rice 2.0
• Document linking tools documents from external • License management
sources services
• Editor infrastructure • Rules Engine
Pre-requisites for local
Financial integration
Integration with ILL,
Reserves, Course
Library Starts Here: Select, Acquire, Management System
Describe
12
1/27/2012 Draft Version 0.4.1

13. Features
Research
Deliver
• Design Deliver policies Select & Acquire • Partner ERP
• Policy Management • Complex PO to invoice integration
services (Checkin, relationships requirements
Checkout, Hold, • License Management
Version 0.8 Release
Reserve) workflows • Partner Identity Mgmt
• Patron Management • Document Type for Deals integration
August 2012
services requirements
• Patron information Complete Describe
services with enterprise • Metadata Editor web • External development
IdM application and use of API
• Initial integration with ILL, • Batch Editing
Resource Sharing • Editor interaction • Integration with GOKb
systems • Record extraction
Implementation Tools
• Data integration with
discovery systems
• Initial data migration tool
set (extract, transfer,
Bringing it to the People: Deliver and
load)
License Management
1/27/2012 Draft Version 0.4.1 13

14. Features
Select & Acquire Research
• Bi-directional messaging Implementation Tools
with ERP, supply chain • Reporting Tools • Partner implementation
• Documented API & strategies
Deliver service registry • Software distribution
Version 1.0 Release
• Patron self services • Distribution packaging management
• External development
December 2012
• Circulation standards • Framework for training
(SIP2, NCIP, etc) development and use of API
• Finish ILL integration • Documentation • Electronic serials
• Completed migration management with
Manage Entity Relationship toolkit GOKb
• Initial integration of • Description Data • OpenURL integration
GOKb • Circulation history • KFS 5 Core upgrade
• Initial electronic resource • Acquisition history • GOKb linked data in
workflows • Complete system ready Orders (Select &
for implementation Acquire)
(minimum of 6 months • GOKb linked data for
expectedt) electronic resources
• Exposure of Service (Describe, Deliver)
Registry • OpenURL services
Ready for Implementation
1/27/2012 Draft Version 0.4.1 14

15. • Follow us on Twitter: @kualiole
• Read our Blog: http://kualiole.tumblr.com/
• Join our mailing list:
• Visit our website: http://ole.kuali.org/