Kuali OLE Release 0.6
description
Transcript of Kuali OLE Release 0.6
Agenda
• General Kuali OLE update • Release 0.6 overview• Demonstration of Kuali OLE 0.6• Where Kuali OLE is headed• Penn’s implementation and needs
moving forward (discussion)
• 2008-2009 Mellon Funded OLE Project Investigation
• 2009 Formed OLE Build Partnership of 9 higher education institutions
• 2010 OLE Build Phase Funded by Andrew W Mellon Foundation & the Kuali OLE Partnership for a 2 year software build phase
• Building a flexible, service-oriented, enterprise library management system for academic & research libraries
Brief History of Kuali OLE
• Build (July 2010-December 2010)– Hire and Engage Kuali OLE Core Team– Engage Software Development Contract with HTC Global Services– Set Kuali OLE Agile Framework and Timelines– Form Functional Specification Writing Teams
• Year 1 Prototype – Kuali OLE 0.2 (December 2010-April 2011)– Demo at CNI Spring 2011 Member Meeting– http://www.kuali.org/ole/demo/spring11/cni
• Software Releases– First Public Release – Version 0.3 – Kuali Days 2011 (October 2011)– Second Public Release – Version 0.6 (May 2012)
• Cloud Demo - http://demo.ole.kuali.org• Develop Year 2 Roadmap (November 2011-April 2012)• Develop GOKb Project with JISC for OLE ERM Components (June 2012-
Nov. 2013)
Kuali OLE Milestones
Kuali OLE Service Layers – Version 0.6
KRADRapid Application
Development Environment
Kuali Rice 2.0Enterprise Middleware – Identity Management, Workflow, Messaging, Triggers
Rapid Application Development, Service Registry, Rules Engine
Kuali Financial System Version
5.0Kuali OLE Core Financial
Functions
Apache Jackrabbit
Kuali OLE Document Store
Select & AcquirePay Invoices, Budget and
Fund Accounting
Descriptive Metadata
Instance Document,
ONIX-PL
Document Editor
FrameworkSchema-driven
Editors
New!
Soon!
Faceted DiscoverySolr Search & Faceting
Identity Management
Dynamic Patron Management
Patron Services
Patron Schema & Classification
Document Editing & Workflow
MARC, Instance, ONIX-PL, & Associate Documents
Key Technologies• Kuali Financial System (KFS)• Kuali Rice 2.0 provides middleware, including:
– Kuali Rapid Application Development (KRAD) – Kuali Rule Management System (KRMS)– Kuali Identity Management (KIM) will support patron
management• Document Store (DocStore):
– Apache Jackrabbit and Solr Lucene. – Format-agnostic (MARC, Dublin core, etc.) – Faceted interface for staff.
Kuali OLE 0.6 Demonstration Site:
http://demo.ole.kuali.org/ole-demo/portal.jsp
• Kuali OLE Version 0.8 - 4th Quarter 2012– KRAD Integration with:
• Bibliographic Editor• Instance Editor in KRAD• Licensing Editor KRAD• Integration with KFS 5.0• Data Loaders for Alpha Testing
• Kuali OLE Version 1.0 - 1st Quarter 2013– Production Ready Version (Beta)– Early Adopters will use this to get ready for production switch– Cloud Hosting Scenarios– Final integration with full RICE 2.0 and KFS 5.0
Kuali OLE Upcoming Releases
• Release OLE 0.6 (May 2012)– Model Library w/Test Drive Version on Amazon Cloud– OLE 0.6 Test-Drive (Amazon Cloud) -
http://demo.ole.kuali.org– OLE 0.6 Driver’s Manual -
https://wiki.kuali.org/display/OLE/OLE+0.6+Milestone+User+Documentation
• Release OLE 0.8 (October 2012)– Open Version of Software with Data Loaders
• Partners/Evaluators can load their own data• Release OLE 1.0 (Q1 2013)
– Early Adopter Implementation Package– Initial Mellon Build Grant ends with Release of OLE 1.0
Year 2 Deliverables
• Release OLE 1.5 (Q3 2013)– Start Proposed New Mellon Grant for Year 3– New Partnership Investment for Year 3
• Early Implementations (2013-2014)– Lehigh University– University of Chicago
• Mid-Implementations (2014-2015)– Indiana University– University of Pennsylvania– Duke University– North Carolina State University
• Later Implementations– University of Maryland (2016)
• Planning Implementations– Florida Consortium
Year 3 Deliverables
• Year 3 will include final development of 1.5 product, implementation patterns, & service integrations
• Adoption, expansion, & integration of GOKb• Implementation at partner sites• Developing multiple models of deployment including local, consortial,
& cloud-based• Bring on at least one Kuali Commercial Affiliate to support Kuali OLE• Business model transition from development organization to
sustaining organization for year 4 and beyond– Supporting our own infrastructure– Keeping core team together to support partners– Expanding partnership
Year 3 and Beyond
Penn’s OLE Implementation• Probable date for full implementation – Summer 2014
– Release 1.0 in Spring 2013– Approximately 1 year to fully implement
• As partners and developers of the product , we can take a proactive role in fitting OLE to our needs
• What are our “must haves” that we’ll need for a successful implementation?
• Scalability issues?• How can we leverage earlier implementations than
ours (Chicago, Lehigh)?– Lessons learned?– Tools/features developed?