KUALI OLE
REFLECTIONS ON OUR FIRST YEAR OF
COLLABORATIVE SOFTWARE
DEVELOPMENT
Robert H. McDonald, Indiana University
Molly Tamarkin, Duke University
Mike Winkler, University of Pennsylvania
OUTLINE
• What is Kuali Open Library Environment?
• Year one deliverables
• Lessons from our first year
• Year two roadmap and deliverables
• A look at our architecture
• First code release, project strategies, joining us
KUALI OLE IS PART OF
THE KUALI FOUNDATION
• Open source software by higher
education, for higher education
• Community source development
approach
• Examples are Kuali Financial System
(KFS), Kuali Coeus, Kuali Mobility,
Kuali Ready
• See kuali.org
HOW THE FOUNDATION
WORKS
Software:
Community approach:
•
No licensing fees
•
•
Non-proprietary
code
Golden rule: those who
bring the gold make the
rules
•
Partners tender
resources to a project
and direct development
•
Each project has its
own governance
•
Collaboration among
like-minded institutions
•
•
Sustainability
through partner
contributions
Commercial
partners provide
market for services
and support
KUALI OLE FOUNDING
PARTNERS
OLE GOALS & PRINCIPLES
• 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
YEAR 1 DELIVERABLES
JULY 2010—JUNE 2011
Develop and Execute Software Development
Contract
• HTC Global Services-Detroit, MI started with 4 staff – now
16+ - will move toward 22 in next quarter
Hire and Engage Kuali OLE Core Team
• 7 member team based at Indiana University; just hired 2 more
Business Analysts
Create Governance Structure
• Formed Project Board, Functional Council, Technical Council
YEAR 1 DELIVERABLES
JULY 2010—JUNE 2011
• Formed teams led by FC members
• Deliver, Select & Acquire, Describe & Manage,
Workflows, Data Model, Communications, and
User Stories
• Created agile framework and timeline
• Developed User Story Process
• Demo’ed prototype Kuali OLE 0.2 at Spring 2011
CNI meeting
QUESTIONS
KUALI FOUNDATION
KUALI OLE GOALS
YEAR ONE DELIVERABLES
LESSONS FROM YEAR ONE
• There is no “set it and forget it”
•
•
•
•
Governance structure
Team management
Meeting management
Project communications
• Product does not trump process
• Without adjusting process and governance, you
will not improve product capacity
LESSONS FROM YEAR ONE
• Extensive reliance on “volunteer” input requires
that we make careful use of volunteer time
• Meetings need clear rationales for existence
• Outcomes need to be clear
• Failures to meet objectives should lead to
process adjustment
• Listen to staff concerns
• Agendas need to be community-driven
• Decide; act; assess; adjust; repeat
GOVERNANCE CHANGES
• Created process to rotate leadership of
functional council
• Created vice-chair role
• Created role of board liaison
• Disbanded technical council and shifted
membership to specific spec areas
PROCESS CHANGES
• From FC-led themed teams
•
Deliver, Select & Acquire, Describe & Manage, Workflows,
Data Model, Communications, and User Stories
• To FC-led Tiger Teams
•
•
•
•
Teams comprised of core team rep, FC rep, and TC rep.
Designed to address spec writing bottleneck
Active Tiger teams are: Scope & Roadmap; Select & Acquire;
Describe; Deliver; Manage Entity Relationship; Systems
Integration
Still have Communications and User Stories teams
• Created more face-to-face workshops designed for
focused spec writing efforts
ROADMAP BASICS
INCLUDES
•Where we’re going
•How we’ll get there
•Functional priorities
• “straight line process”
•Infrastructure to build
•Minimal deliverables
•Areas to research
MAPS TO JIRA TASKS
ROADMAPS: PAST & PRESENT
YEAR ONE 7/10-6/11
YEAR TWO 7/11-6/12
•Winnowing user stories to
2000
•Kuali Rice™ for workflow
•Architectural development
•Adapting KFS for Select &
Acquire
•Adopt Apache Jackrabbit ™
for metadata
•Support multiple
descriptive metadata
formats
•Complete Select & Acquire,
Deliver, Describe, and begin
creating implementation
tools
•Code release in November
and April
FUTURE ROADMAP
• Full release mid-year two in December 2012
• Last half of year two will be tweaking,
documentation, and implementation plans
• Year three will focus on:
•
•
•
•
Implementation
Documentation
Migration
Commercial partnerships
QUESTIONS
LESSONS LEARNED
GOVERNANCE & PROCESS CHANGES
ROADMAPS
INTERPRETING OUR GOALS
ARCHITECTURALLY
Kuali OLE is a service-oriented toolbox
for enterprise library management
• Financial management & budgeting that can interoperate
with the ERP
• Workflow & rules engine to manage business process
• ETL tools & data integration pathways to ease integration
of data into OLE
• Standard interfaces to OLE data & functions to enable easy
and robust integration
• Service bus and service registry to document & manage the
OLE API
KUALI OLE ARCHITECTURE
• Transactional System based upon Kuali
Financials
• Core system driven by Java-based Kuali Rice
• Database agnostic (developed on Oracle)
• Bibliographic data accessed using SOLR/Lucene
indexing
• Jackrabbit
• Development environment on Amazon EC Cloud
TIERED DATA STORAGE
Descriptive Data
(MARCXML, EAD, VRA, ERMI, etc)
Key
Data Store
Document
Index
Document
Repository
Semantic Relationships
Relational Data
(Collections, tagging, FRBR)
(Fund, status, administrative)
Semantic
Repository
Relational
Repository
Semantic
Broker
SQL Broker
Kuali OLE
Kuali Rice
Metrics
3rd Parties
Document
Broker
Messaging & Queues (Kuali Enterprise Service Bus)
Kuali Identity
Mgmt (KIM)
Kuali Enterprise
Workflow (KEW)
Kuali Enterprise
Notification (KEN)
3rd Party
Interfaces
Kuali Financial
System (KFS)
Services
Repository
RELEASE 0.3
• Cloud instance and downloadable code
• Provides flexible document store
• Provides faced searching for internal
management (public interface-neutral)
• Supports basic material selection and
acquisition
• http://kuali.org/test-drives
KUALI OLE IN SUM
Innovative Technologies
• Document store
• Flexible workflows
More than building software: deep project collaboration
• Members have direct representation and influence
• We are open and transparent
Transforming research libraries
• Ownership of workflow lets us focus our staff
• Permits strategic integration with new partners – i.e. discovery
WAIT, THERE’S MORE
Workflow over module-based system
• Layered functionality ready for localization
Breaks down our metadata silos
• Combines them under integrated, flexible management
Strength through community
• Open for review
• Shared risk and mitigating risk through partnership
• Diversity of views, experience, needs
ENGAGING WITH US
JOINING THE
PARTNERSHIP
•Let’s talk (Robert at
rhmcdona@indiana.edu)
•Not too late to join year
three development
•Interested in consortial and
cloud approaches
FOLLOW US
•@kualiole on twitter
•Blog:
http://kualiole.tumblr.com
•Project site:
http://kuali.org/OLE
QUESTIONS
ARCHITECTURE
RELEASES & TECHNOLOGIES
PARTNERSHIPS