...
| Section | ||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Introduction
...
- New schemas have been introduced:
- The OLE Instance schema is loosely based on the MARC Format for Holdings Data (MFHD). OLE Instance documents are used to identify and describe library resources locally owned/licensed by libraries and as such contain unique information that can not be captured in Bibliographic documents that may be used/shared by multiple libraries.
- ONIX-PL, a standard used to describe and transmit licensing information for electronic resources, will be utilized as the central schema for storing data within Kuali OLE's OLE’s licensing module.
- KFS has been upgraded.
- With the onset of Rice 2.0, KRAD and KRMS features have been incorporated into part of OLE.
- KRAD provides the user interface OLE needs for inquiries and lookups, transactional and maintenance documents.
- KRMS provides OLE the opportunity to build its own flexible and easily managed business rule system.
- Code refactoring corrects the mistakes made during the 0.3 Milestone Release and keeps the OLE system better maintained.
The Service Registry contains information about all services that have been registered from OLE to the services bus (KSB), designed to allow developers to quickly develop and deploy services for remote and local consumption. - KFS PURAP upgrade has been postponed.
Please also see the OLE 0.6 Milestone User Documentation to test run the demo, read through the Drivers Manual, and learn more about the O.6 release.
...
A full KFS 5.0 code merge and upgrade is expected during the OLE project schedule for OLE 0.8 (fall 2012spring 2013). OLE did prepare and edit some existing code and services to prepare for eventual upgrades, but partial upgrades during OLE 0.6 were postponed until KFS completes testing and debugging of KFS 5.0.
...
- Perform lookups/inquiries within a lightbox/iframe that pops up over the document
- Open documents or route log from action list or document search in a lightbox
- Add support for some transactional document layouts without using JSPs.
KRAD makes data dictionary change such as adding lookup constraints and custom constraints. Overall, KRAD will enhance OLE UI capabilities.
For more about KRAD, see Rice KRAD analysis
KRMS
The other important component in Rice 2.0 is Kuali Rule Management System (KRMS). KRMS is a rule engine for defining decision logic, commonly referred to as business rules. KRMS facilitates the creation and maintenance of rules outside of an application for rapid update and flexible implementation that can be shared across applications. KRMS provides OLE the opportunity to build its own flexible and easily managed business rule system.
For more about KRMS, see the KRMS and PeopleFlow Functional Overview
How OLE is affected
Based on the above Rice 2.0 features, obviously, moving OLE to Rice 2.0 framework is what we should go for. However, Kuali OLE's current version is bundled with KFS, which utilizes Rice 1.x. Since Rice 2.0 was formally released on Feb 24th, 2012, it was impossible for KFS (Kuali Financial System) to upgrade to Rice 2.0 before OLE 0.6 release. It is not realistic to abandon KFS and one-year's worth of implementation based on that and to rebuild our own financial system for OLE. So for the OLE 0.6 release we set up two servers, one for OLE with KFS/Rice1.x to keep our financial functions and one for OLE on Rice2.0 to try the new features and see what kind of benefits it can bring for OLE. Since Rice 1.x can not talk with Rice 2.0 through the KSB (Kuali Service Bus), therefore, the communication between two servers geso through SOAP services like this simple drawing for the architecture.
...