Rice Status Update University of California July 20, 2009

1. Rice Status Update University of California July 20, 2009 Eric Westfall – Kuali Rice Project Manager

2. Rice 1.0 - Status • Target date for public release is July 31 • Team is currently in the final phase of QA, working on packaging, licensing, release notes and continued testing • During development of Rice 1.0, approximately 1,100 issues have been resolved. • Colorado State University and San Joaquin Delta College went live on July 1st with a pre-release version of KFS 3.0. This included a pre-release version of Rice 1.0. • Innovativ Consulting has been working on the documentation for the Rice 1.0 release. This includes a significant amount of new documentation as well as improvements to our existing documentation.

3. Rice 1.0 – Major Changes • Major refactoring of package structures to conform with project standards • Refactoring of all database identifiers (table names, column names, etc.) to conform with project standards • Reorganization of Rice modules including explicit separation of API and Implementation classes.

4. Rice 1.0 – Major Changes • Implementation of Kuali Identity Management Module • Replacement of existing identity services supplied by KEW • Integration of KIM authz into other modules of Rice (most notably KNS and KEW) • Created a Kuali CAS Server which integrates with KIM

5. Rice 1.0 – Major Changes • Rewrite of numerous KEW screens to leverage the KNS application framework, including (but not limited to): • Document Search • Action List • Route Log • Routing Rules

6. Rice 1.0 – Major Changes • Consolidation of duplicate framework code and services that existed in KEW and KNS • Lookup framework removed from KEW, replaced with KNS • Application Constants removed from KEW, replaced with KNS system parameters • Duplicate concept of “Document Type” removed from KNS, consolidated with KEW Document Types

7. Rice 1.0 – Major Changes • A new document for maintaining Document Types was implemented • Improved compliance with accessibility standards (in the KNS as a framework and in KEW implementation) • Upgrade from XFire to Apache CXF as backend implementation of KSB web service functionality

8. Rice 1.0 – Major Changes • Improvements to the way that services can be published to the KSB service registry • Foundation put in place for future replacement of OJB with JPA • Numerous other bug fixes and miscellaneous improvements • Major rewrites and improvements to the Rice documentation

9. Rice 1.1 –Features and Timing • Rice 1.1 is the next major release of the Rice software • This will be more then a set of simple enhancements and bug fixes, we are planning to undertake some significant projects as part of this release • KualiCoeus 2.0 and Kuali Student 1.0 are going to be using a 1.0.x version of Rice instead of waiting for Rice 1.1 to be completed

10. Rice 1.1 –Features • What follows is a list of proposed changes in Rice 1.1, the final decisions have not yet been made by the ARC • One commitment made by the Rice project for version 1.1 is to provide compatibility between versions moving forward • There is a working group formed in the TRC which is working to identify what work will be required to facilitate this

11. Rice 1.1 – Features • Conversion from OJB to JPA • there is a working group formed in the TRC that is working on the plan for this • Support for simple Document Type-based delegation • Remove/replace user functionality for doing mass changes to data that depend on a user • update permissions, groups, roles, rules, etc. when someone leaves the university or changes positions

12. Rice 1.1 – Features • Extract the batch framework from KFS into Rice • Various Document Search improvements • Create standards for naming of Rice configuration parameters and implement them • Create standards for Rice service names and implement them • Improved XML ingestion features and fixes to schemas for easier use in XML tools

13. Rice 1.1 – Features • Improvements to KNS Help System • Consolidate KEW help system with KNS help system • Consolidate KEW notes and attachments with KNS notes and attachments • possible other work here as well regarding using alternate storage for attachments (like a CMS) • Convert KEN GUI screens to use the KNS • Convert KSB GUI screens to use the KNS

14. Rice 1.1 –Features • Improvements to Action List to allow for display of custom columns • Improvements to email delivery preferences • Add support to KNS for versionable documents • Allow for greater customization of exception routing • Extract “Global” or “Mass” document framework from KFS

15. Rice 1.1 – Features • Improvements to Document Search implementation to ensure that it’s behavior is consistent with other KNS-based lookups • Includes general improvements to the design of the document search “back-end” • Implement more screens in KIM for maintaining data • Upgrade to Spring Framework version 2.5 • Other miscellaneous improvements

16. Rice 1.1 – Timing • Facilitating compatibility between Rice versions post 1.1 is the top priority for the Rice 1.1 release • That work alone is expected to take a significant amount of time, since we will be locked in to certain decisions once Rice 1.1 is released • Analysis and planning alone for this is likely to take a few months

17. Rice 1.1 – Timing • JPA work is also expected to require a large amount of time, includes authoring documentation and tools for existing applications to help with their conversion • All of this will be discussed with the ARC when we bring these items to them for planning and prioritization of the Rice 1.1 release

18. Rice 1.1 – Timing • Prior to discussion with the ARC, it’s hard to predict the amount of time the release will take • Original targets were fall of this year • However, Rice 1.0 release has taken longer then expected so 1.1 release may need to slip into next year • As mentioned before, this will depend on decisions made by the ARC • Some of these items could end up on the wish list after ARC prioritization

19. Rice – RequestedFuture Features • We refer to our requested list of future features as the “The Wish List” • What follows is a list of items that have been suggested by others and are on our list to consider for future implementation • When and to what extent this work happens will be determined by the roadmap committees

20. Rice – Wish List • Graphical Editor for KEW Process Definitions • Graphical View of a Document's Routing Process • BPEL/BPMN Support • In general, better support for industry standard workflow constructs • More Extensive set of Remote APIs • Improved Web 2.0 and AJAX Support

21. Rice – Wish List • Continue to evolve KSB toward more industry standards • At the extreme case, this might result in replacement of the KSB • Alternatively, this could include improving utilization of other open source products within KSB (such as Active MQ) • RSS Support • primarily in the context of the notification module

22. Rice – Wish List • Portlet support • JMX Support • Greater configurability of notification preferences • Add support for facilitating the creation of mobile applications • Improvements to the KNS to provide a less rigid and more flexible framework

23. Rice – Wish List • Implement support for automated “escalation” in the workflow engine • Evolve the eDocLite functionality to take more advantage of the KNS • and possibly be folded into the KNS as another option for rapid application development