Posted:  Aug 31, 2010

The Treasury Institute has published a white paper on Kuali Endowment Management, a module of the Kuali Financial System that is slated for release in November of this year. You can download the white paper at  http://www.treasuryinstitute.org/KEM%20Whitepaper.pdf, and learn more about Kuali Endowment Management at Kuali Days in November.

Posted:  Aug 29, 2010

Kuali Days 2010

Manchester Grand Hyatt- San Diego, California

November 8-10

http://www.kuali.org/kd/kd2010

Conference Program in Process
The Call for Proposals has ended and the Conference Committee is in the process of reviewing over 100 contributions! The Track Chairs are excited about the contributions and have provided the following snapshots of the content you might expect to hear at the conference.

Kuali Coeus – Paul Sandoval, Track Chair
Looking to the Future  - Kuali Coeus 2.0 contains Proposal/Budget with grants.gov system to system interface, Institute Proposal, Proposal Log and Award.  This year the track will include discussion of the current/future modules and also give you in insight as to how implementing schools are configuring each module to meets its own needs.

Kuali Financial Systems, Theresa Todd, Track Chair
Live and in use – the Kuali Financial System has propelled from ‘Theory to Practice’.   The KFS track this year has added new exciting topics to cover all levels of users.   For those getting their feet wet, we still provide the pre-conference workshop KFS Basics, as well as demonstrations of different modules of the KFS system.  Developers can attend the pre-conference workshop – KFS Hands-On Developer Introduction.  For the more advanced user more exciting advanced topics are offered such as Security, Financial Reporting, KFS Year-end and Training Campus.  Don’t miss the introduction of the new Kuali Endowment Module.  And everyone is invited to join in on the many Birds of a Feather (BOF) topics where ideas and issues can be discussed with your peers.  

Kuali Rice – Emily Deere, Track Chair
As the Track Coordinator of the Rice Track, I can say we’ve come a long way in a year with Rice! Our pre-conference workshops set the stage with details on Kuali Rice Installation & Configuration and integration with Kuali Identity Management (KIM). Both the new and familiar will benefit from our roadmap and business case sessions. In addition we’ve sessions focused on integration, KRAD, Lightweight UI clients and much more.

Implementation Track, John Hunter, Track Chair
The Implementation Track offers many opportunities for implementing schools to share information for a successful conversion to KFS.  Sessions offered are from theory (implementation strategies and business process analysis) to practice (lessons learned, yearend and financial statements).  Whether you are implementing Kuali Financials, Kuali Coeus or both, this track has it all!

Kuali Student, Matt Coombs, Track Chair
As the Track Coordinator of the Kuali Student Track, I am pleased to report steady and consistent progress as we have moved from theory to downloadable code! The conference presentations will give you all the  details you will need on Kuali Student releases, implementation and integration with other Kuali components like Kuali Identity Management (KIM) and Kuali Enterprise Workflow (KEW), as well as third party systems such as Red Lantern and Sigma. Whether you are just curious and kicking the tires or are a serious Kuali Student investigator, you will be able to interact with the project leadership, participate in discussions regarding status and roadmap, and listen to implementers share their recent experiences with the newest releases. Come join us!

Other Track - Zach Naiman, Track Chair
The Other Topics track is loaded with exciting sessions, including sessions on the newer Kuali projects (Kuali Ready, Kuali OLE and Kuali People Management for the Enterprise), implementing Kuali outside the US, Kuali for government, decision support, procurement process, KFS-KC integration, capturing software requirements, building a good user interface, evolving collaboration infrastructure and more!

Be sure to check the Kuali Days Website for more information about the conference program including pre-conference workshops and general session speakers. The full conference program is scheduled to be online in mid-September.

Conference Sponsorships Available
The Kuali Days Conference Committee invites companies who want to engage with a growing community of universities, colleges, businesses, and other organizations that have partnered to build and sustain open source administrative software for higher education by higher education to participate in the conference through sponsorship opportunities.

Kuali Days 2010 Registration
Don’t miss out on this conference! Register early and save!

Kuali Days 2010 Hotel Reservations
The beautiful Manchester Grand Hyatt located on the San Diego Bay and next to Sea Port Village awaits your reservation. The cut off date for making sure you get the conference special rate of $169 is October 15, 2010.

 

Posted:  Aug 20, 2010

The Kuali OLE project is hiring for two positions:

• Senior Architect
• Data Architect

Senior Architect

Job Description: Ensures successful design of the Kuali OLE services-oriented management system and the evolution of the architecture to meet the needs of the Kuali OLE partnership. The Kuali OLE system will be designed using best practices and existing software from the Kuali Rice middleware and Kuali Financial System software. Acts as a leader and a mentor to other Kuali OLE core technical staff as they begin their education/training in the Kuali Rice middleware, develops the framework for the Kuali OLE software, and works closely with the Kuali OLE Project Manager in outsourcing the primary coding of the Kuali OLE software with a contract vendor. Ensures that the applications follow the standards and functional design set by the Kuali OLE Functional Council and the Kuali OLE Board, that developments use the latest versions of Kuali infrastructure, that Kuali OLE takes advantage of relevant and emerging functionality, and that requirements for Kuali OLE are communicated to inform development of Kuali Rice and other Kuali software involved in the development of Kuali OLE. 

Qualifications: Bachelor's degree and five years of professional programming experience working with enterprise applications, including at least one year of technical team leadership experience required. An equivalent combination of education and experience may be considered. Proficiency in Java and experience with one or more relational database such as Oracle, MS SQL Server, etc.; strong SQL/relational database/data modeling skills; and extensive systems analysis and design experience with enterprise systems is required. Experience with Java application design/design patterns; good oral and written communication skills; strong work ethic; ability to solve problems quickly; ability to motivate others; and excellent skills in leadership, problem-solving, decision-making, and communications needed. Experience with other Kuali Foundation software projects a plus. 
https://jobs.iu.edu/joblisting/index.cfm?jlnum=1924&search=2

Data Architect

Job Description: Ensures the successful logical and physical design of the Kuali Open Library Environment (OLE) data architecture to meet the needs of the Kuali OLE user community. The Kuali OLE system will be designed using best practices and existing software from the Kuali Rice middleware and Kuali Financial System software. Acts as a consultant and guide to the Kuali OLE data model team as they gather and document data requirements. Converts those requirements into a well-documented, logical data model; conducts quality assurance for the data model in conjunction with the user community; and oversees the build/implementation of the physical data model. Works closely with the Kuali OLE Project Manager and the Kuali OLE Senior Technical Architect to ensure models are built according to schedule and that they meet the technical requirements and standards established by the Kuali OLE Functional Council and the Kuali OLE Board. Ensures that Kuali OLE takes advantage of relevant and emerging functionality, and that requirements for Kuali OLE are communicated to inform development of Kuali Rice and other Kuali software involved in the development of Kuali OLE. 

Qualifications: REQUIRED: Bachelor’s degree and three years of professional data architecture experience with both normalized and denormalized models. 

A combination of education and experience may be considered. Extensive experience with one or more relational database such as Oracle, MS SQL Server, etc. required. Strong SQL/relational database/data modeling skills and experience with metadata documentation tools and data design tools (ERwin/Designer) required. Good oral and written communication skills; strong work ethic; ability to solve problems quickly; ability to motivate others; and excellent skills in leadership, problem-solving, decision-making, and communication needed. Experience with other Kuali Foundation software projects a plus. 
https://jobs.iu.edu/joblisting/index.cfm?jlnum=2314&search=2

Posted:  Aug 18, 2010

Kuali will be updating our wiki to the most recent version of Confluence this Saturday night.

Although the new version of Confluence is not very different from our current version, we encourage everybody to have a look at the new version before we go live. You can log in to the new version using your Kuali Single-Sign-On credentials at http://wiki.kuali.org.

After this weekend, the URL of our Confluence will change from http://test.kuali.org/confluence to http://wiki.kuali.org

Note that you can see the Kuali Foundation's infrastructure calendar, which includes changes like these and our regular maintenance schedule, at the bottom of the KIS home page (http://kuali.org/kis)

If you have any questions or concerns, please contact the Kuali Foundation staff by writing to help@kuali.org.

Comparing open source vs. proprietary software is like comparing apples and oranges. It’s a comparison that just doesn’t make sense for anything other than the basic comparison of licensing rights.

There are great variations among open source options, and among proprietary options. Yet many conversations about open source software tend to use very broad generalizations and treat each of these (open or proprietary) as a distinct thing. I’m involved in a lot of conversations about adopting open source software and I’m always struck by the black & white view of proprietary vs. open.

At the highest level organizations and even governments are adopting an ideological disposition that favors “open” vs. “closed.” In the education community there is often an affinity toward openness because of the alignment with core values and the mission of the academy. This is a good and healthy way to set strategy.

When it comes to making a decision about a particular need though, many people and organizations are looking for a pragmatic approach to making decisions about their options. Even those who have an established strategy that considers open source need to make specific decisions about the options for a particular need. This is where the simple open source vs. proprietary discussion breaks down. The general distinctions between open source and proprietary provide almost no useful information to inform a choice between X open source product, and Y proprietary product. In fact, most often, the choice isn’t really between X and Y, it’s between W, X, Y, and Z, where the other options represent the new choices afforded by open licensing.

Colleges, universities, K-12 schools and districts, have more choice today than ever when it comes to enterprise software. Despite a great deal of consolidation in the proprietary software vendor space, the emergence of community-developed, open licensed software, and SaaS services have more than filled the competitive void. I work in the Kuali and Sakai communities that together produce some of the most mission-critical enterprise systems for schools: eLearning Platform, Financials, Research, Student, Business Continuity, and more.

Some of the most important questions an institution can ask when considering the various options aren’t those that appear in an RFP with a feature matrix. They are introspective questions about institutional culture and capabilities–where the institution is today, and where it would like to be. And also, of course, what are the goals for the new system?

I spend a lot of time talking to people considering open source “alternatives” to the proprietary eLearning and ERP systems. I’ve recently begun to use a tool in those conversations that helps facilitate the conversation. If I’m near a whiteboard I’ll use that, otherwise the iPad makes a good mobile whiteboard alternative. Here’s a snapshot from a recent conversation:

This simple visual has been a very effective way of elaborating the choices for these software needs and comparing them on two dimensions. The two I’ve focused on have been cost and control. I typically talk about 5 different sourcing options:

• Licensed proprietary software
• “Home grown” software developed at the institution
• “DIY” (do-it-yourself) open source software (OSS)
• Commercial OSS
• Software as a Service (SaaS) OSS

Among the various choices it’s fairly easy to paint a picture of the options relative to cost and control tradeoffs. These aren’t the only dimensions to consider, but they are two that should be central to the decision. I should also note that control can directly relate to risk, strategic fit, and institutional capabilities (both current and desired future). One of the other reasons I’ve often focused on cost / control is because one of the most often cited reasons for looking at open source eLearning or ERP options is greater control.

You might be looking at the diagram, thinking… “He’s nuts. That green dot should be lower (or higher) or further to the right.” Good thinking. There isn’t one right way to paint this picture. It’s a conversational tool that needs to be adapted to fit the specific situation you’re talking about. I believe that there’s some “rough general truth” to the relative positions I’ve indicated, but the real usefulness is in the conversation & thinking that this tool facilitates, not where I’ve placed the data points.

As a starting point I’ll use this to understand current institutional culture and capabilities. How are systems generally sourced today? In some cases economics or new institutional leadership are driving a cultural change. The diagram can be a useful tool to understand how the various options support that desired change. It’s also interesting to note that the culture around things like eLearning or Research might be very different than the culture around Financials.

One of the most interesting conversations is about the various open source options. Ok, this is probably most interesting because it’s where I’ve focused for the past 8 years or so. Most people assume that to consider open source they have to hire software engineers and generally have to support it differently than the proprietary system they are replacing (the “DIY OSS” option). By the way most research and media coverage makes the same assumption. The visual helps to clarify that option relative to other options. There are good reasons an institution might move from proprietary or home grown to DIY OSS. There may be a strong institutional culture driving it. Often though, institutions believe that to leverage something like the Sakai eLearning platform they have to move to DIY OSS. And if that’s not a match to the institutional culture, or they don’t have the resources and don’t want to build the necessary capacity, the analysis stops. Most institutions, in fact, adopt open source software in the very same way they adopt proprietary software. But the options aren’t widely understood.

If you are involved in sourcing a replacement system, or a new capability for your institution. You have lots of options. Consider them all. You may find that’s it’s a useful exercise to compare the characteristics of each that are important to your institution. This should be a very strategic discussion that starts by determining the characteristics that are important to your institution: cost, risk, capabilities, control of future capabilities, alignment of values, future potential, opportunities for staff development, opportunities to align with peer institutions, etc.  From there it’s a much simpler comparison exercise to understand how each option supports your goals.

Tagged: education, kuali, open source, sakai, software

Posted:  Aug 10, 2010

Kuali Student is currently seeking to fill the below positions. Please send cover letter and resume via e-mail to ks.jobs@kuali.org

• Testing Engineer
• Senior Developer/Lead
• User Experience (UX) Designer

Depending on the circumstances of the successful applicants, these positions could be established in a number of ways, including:

• an employment agreement between the applicant and a KS Partner institution
• as a personal consultancy directly to the Kuali Foundation
• other arrangements will be considered

Testing Engineer
The ideal candidate should have excellent communication skills, a passion for testing in an open source community, the ability to automate test cases using open source tools, scripting and/or coding languages, and a devotion to tracking down the cause of hard to find bugs.
The Kuali Student Testing Engineer has the following responsibilities:

• Designs, builds and implements test frameworks and reusable test components
• Works with the QA manager to develop test plans for non-functional testing
• Writes and executes reusable test cases at the white and grey box levels using open source tools, scripting and/or coding languages
• Automates repetitive and low level test cases
• Records and communicates test results
• Files defects using a defect tracking system (JIRA)
• Works with development to help pinpoint root causes
• Manages and maintains one or more libraries of automated tests

The incumbent should have the following skill set:

• 5 -7 years experience testing web service solutions
• Computer Science degree or equivalent experience
• Experience reviewing, writing and applying an object oriented programming language (JAVA) towards testing
• Experience applying a scripting language to automate test cases (Ruby, Javascript, Perl)
• Experience automating web browser testing (Selenium, Watir)
• Comfortable building and navigating source code with little help
• Experience with MySQL and/or Oracle
• Knowledge of web service architectures
• Knowledge of industry standards including SOAP, XML, WSDL

Senior Developer/Lead
The Kuali Student Development Lead has the following responsibilities:

• Works closely with Business Analysts and Subject Matter Experts to ensure a clear understanding of the business requirements
• Develops plans and supervises work of Developers
• Provides technical leadership and mentors developers to develop their skills
• Works with Developers to resolve technical issues and problems that occur within the team
• Ensure Developers write unit and component tests
• Ensure Developers commit code so that it may be part of continuous integration
• Performs quick-turnaround for code that breaks builds/tests done in continuous integration
• Ensures code analysis takes place
• Performs regular code reviews
• Ensures code documentation
• Works with Developers and Testers to resolve issues
• Designs, Codes, and Tests software
• Prepares program documentation
• May be required to present to the Higher Education Community at Kuali Days and other North American Higher Ed conferences

The incumbent should have the following skill set:

• Supervisory skills and prior experience managing a team
• Excellent analytical and problem solving skills
• Excellent communication and facilitation skills
• Able to express technical issues in language a SME or Business Analyst will understand
• Deep technical skills
• At least 5 years Java experience (Sun Java certification an asset)
• Familiarity with Spring IOC and AOP
• Familiarity with ORM concepts and JPA in particular (preferably the hibernate implementation)
• Advantageous if they have worked with Eclipse and SVN
• Knowledge of XML, XSD, WSDL, SOAP

User Experience (UX) Designer
Under direction from the User Experience Architect, the Kuali Student UX Designer has the following specialist responsibilities in addition to the Business Analyst responsibilities:

• Conduct user research
• Design and develop UX deliverables (personas, principles, guidelines, UX design patterns, wireframes, etc.)
• Contribute to interim artifacts such as user data analysis, function maps, etc.
• Apply internationalization standards and accessibility standards to all aspects of Kuali Student
• Apply UX design patterns uniformly across all development nodes and within partner projects
• Design, develop and conduct usability testing
• Contribute to documentation, especially in cases where there is no Kuali Student-supplied user interface
• Collaborate with and makes presentations to other teams and groups as necessary

Posted:  Aug 10, 2010

The Chief Process Experience Architect serves as the chief process architect to enhance the user experience and process efficiency of IT for IU campuses. The position will lead a team that uses empirical, anthropological, and other evidence-based approaches to understand the human elements of system use and potential for improving process effectiveness. Initially, work will be targeted towards student systems to ensure that development adequately addresses students' needs; future efforts will focus on additional information systems and will use research and analysis to enhance human/computer interaction through the design and development of subsequent systems. In order to accomplish these goals successfully, individual must be able to assess the objectives of a high-level, diverse audience and use various forms of communication at both an executive and technical level to advise accordingly. Must be able to effectively document and communicate insights to an experienced development team. Ultimately, this position will be responsible for the successful creation, modification, and implementation of the interface to Indiana University's most utilized information systems.

Qualifications: Bachelor’s degree and five years demonstrated leadership in human/computer interaction initiatives and projects with emphasis on process re-engineering required. Excellent interpersonal, written, and oral communication skills essential. Track record in successfully leading high-level process redesign on large-scale projects required. Demonstrated ability to successfully interact with and guide high-level executives from different organizations towards desired outcomes required. Master's in Information Systems or Human/Computer Interaction preferred. Experience within higher education highly desirable.

If interested, please apply online at https://jobs.iu.edu/. Refer to job number #2073.

Indiana University is an Affirmative Action/Equal Employment institution.

Posted:  Aug 04, 2010

Kuali Rice is currently seeking to fill 4-5 positions on the development team for the Kuali Rice enterprise class middleware suite which serves as the foundation of the Kuali family of products.

• Project Manager: Provides leadership for the planning, software development, implementation, maintenance, and documentation of all aspects of the Kuali Rice software project. Read full job description.
• Business Analyst: Creates and maintains the strategic partnership between the business needs of the Kuali community and technology delivery in an agile development environment. Read full job description.
• 1-2 Developers: Participates in analysis and design of features and improvements, develops code for the Kuali Rice project according to standards and best practices. Read full job description.
• Configuration Manager: Responsible for project infrastructure to support development, deployment, and release of Kuali Rice software including version control, bug tracking, documentation, databases, integration environments, test environments, and release processes. Read full job description.

Depending on the circumstances of the successful applicants, these positions could be established in a number of ways, including:
• an agreement to second the employee to the Kuali Foundation, if the candidate wishes to remain with his or her institution
• as a personal consultancy directly to the Kuali Foundation
• other arrangements will be considered

Please send cover letter and resume via e-mail to rice.jobs@kuali.org.

No.  The Kuali Financial System (KFS), however, does include Effort Certification in its Labor Ledger.  Effort Certification was introduced with KFS Release 3.0.  See http://www.kuali.org/kfs for additional details.

Kuali Coeus calculates salary - both sponsor requests and cost sharing - from percent effort listed in the proposal budget.  This information is not integrated with the KFS effort certification module.

 

Posted:  Jul 06, 2010

The Internet2 Middleware Initiative and the Kuali Foundation today announced the integration of two key elements of their identity management (IdM) offerings. Internet2's Grouper Groups Management Toolkit now interoperates with the Kuali Rice software.

The Kuali Rice software provides an enterprise class middleware suite of integrated products that allows for applications to be built in an agile fashion. Internet2's Grouper Groups Management Toolkit enables project managers, departments, institutions and end users to create and manage institutional and personal groups. It puts control of a group in the hands of its steward and enables the person to manage the membership and what resources it can access.

"Alignment of open source projects yields significant benefits for the higher education IT community," said Tom Barton, Senior Director for Integration at the University of Chicago and Chair of the Internet2 Grouper Working Group. "We believe this Grouper/Kuali integration is an important part of a broad effort to promote the synergies between various open-source IdM efforts."

Eric Westfall, Enterprise Software Architect at Indiana University and Kuali Rice Project Manager added, "The results of this collaborative effort will allow for institutions to leverage current or future investments in Grouper in conjunction with their Kuali implementation projects. Additionally, this is a reification of one of the core Kuali Identity Management design principles, which was to provide a platform within Kuali for integration with other IdM products."

An early adopter of the Grouper/Kuali integration will be the University of Pennsylvania, which has leveraged Grouper to manage course, affiliate, and ad-hoc groups on campus. University of Pennsylvania wanted to integrate the workflow features offered in Kuali Rice to this existing system to allow automated approval of access requests to protected resources.

"Penn is converting paper forms used for access to protected resources to electronic forms in order to improve service to the staff and to provide even tighter overall security," explains Jim Johnson, Director of Data Administration at University of Pennsylvania. "The Grouper/Kuali Rice integration enables faster provisioning of access to electronic services for authorized users, allowing them to more quickly utilize the resources. Using Grouper and Kuali Rice together in one system means we can even further reduce manual errors in assigning access privileges. It has the added benefit of reducing effort expended in security administration, which can be redirected to other activities. The system also creates an audit trail that can be used for reporting and troubleshooting."

In addition to taking advantage of the Kuali Rice workflow features, University of Pennsylvania intends to leverage the Grouper/Kuali integration to feed group, identity and possibly role information into Kuali Ole (Online Library Environment) which Penn is a founding member. Kuali Ole seeks to define a next-generation technology environment based on a thoroughly re-examined model of library business operations.

While the idea of a collaboration between the Grouper and Kuali projects began several years ago, a plan to develop the integration came as a result of discussions among the community at the June 2009 Advance CAMP workshop. The meeting was a unique forum for improving channels for collaboration and alignment between community source middleware projects.

With highly motivated team members from both projects leading the way, the collaboration progressed quickly culminating in a demonstration of the integration at the Spring 2010 Internet2 Member Meeting in April 2010. With the recent release of Grouper version 1.6 in June 2010, the Grouper Kuali integration became available to users.

The 2010 "Advance CAMP: Second Identity Services Summit," held in Raleigh, North Carolina, in June 2010, continued the efforts towards alignment of open-source IdM software and may lead to additional collaborative projects.

"Collaborations like this, to keep independent open-source efforts aligned, continue to need nurturing, and this is a major goal of our Advance CAMPs," said Ken Klingenstein, Senior Director of the Internet2 Middleware and Security Initiatives. "For example, a key collaborative project on the horizon for the Grouper development team is to examine closer integration with Jasig's uPortal framework, among other important projects."

For more information on the Grouper Groups Management Toolkit, visit http://www.internet2.edu/grouper/. For more information on Kuali Rice, see http://kuali.org/rice/.

##

About Internet2

Led by the research and education community since 1996, Internet2 promotes the missions of its members by providing both leading-edge network capabilities and unique partnership opportunities that together facilitate the development, deployment and use of revolutionary Internet technologies. Internet2 brings the U.S. research and academic community together with technology leaders from industry, government and the international community to undertake collaborative efforts that have a fundamental impact on tomorrow's Internet. For more information: www.internet2.edu

About the Kuali Foundation

The Kuali Foundation (www.kuali.org) is a growing community of universities, colleges, businesses, and other organizations that have partnered to build and sustain open-source administrative software for higher education, by higher education. Kuali software is designed to meet the needs of all sizes of institutions, from land-grant research universities to community colleges. Members of the Kuali Community share a common vision of open, modular, and distributed systems for their software requirements. Kuali software is released under the Educational Community License. The Kuali Projects are tied together by the Kuali Foundation, a non-profit organization that coordinates the efforts of partners, manages and protects the community's intellectual property, and handles common concerns among the Kuali Projects.

Development of the Grouper Group Management Toolkit was supported with funding from University of Chicago and the University of Bristol with additional support from Internet2 through their NSF Middleware Initiative (Cooperative Agreements No. OCI-0330626 and OCI-0721896) and the Joint Information Systems Committee (JISC).

 

Posted:  Jun 30, 2010

UPDATE: This position has been filled.

The Kuali Foundation is looking for an exceptionally talented technology professional who has the vision and execution skills to lead a rapidly growing open source community's technical direction. This unique opportunity is for the Kuali Rice Lead Architect position. Kuali Rice is an enterprise middleware suite that provides the foundation for Kuali's enterprise applications such as the Kuali Financial, Student, and Research Systems. Kuali Rice is also being adopted by educational institutions as a core part of a next generation enterprise architecture. This position offers the right candidate an opportunity to have an important impact improving the use of technology to further education globally. The successful candidate will have proven leadership abilities, experience with open source communities, exceptional communication and collaboration skills, and strong service oriented architecture and design expertise.

Click this link to read the full job description

Please send cover letter and resume via e-mail to: Eric Westfall, Kuali Rice Project Manager, ewestfal@indiana.edu

Posted:  Jun 25, 2010

Kuali OLE welcomes our newest team member, Brad Skiles. Brad will serve as the OLE Project Manager and he comes on board board July 1, 2010. Brad comes to us from Purdue University and has worked in IT for over 20 years. He has worked with a variety of administrative applications with experience as a director, project manager, and DBA.  He has an extensive background in management, data architecture, business intelligence, and data quality and has been active in professional groups such as the International Oracle Users Group Association, the Data Administration Managers Association, and EDUCAUSE.  Brad and his family will be relocating to Bloomington, IN over the summer and we are happy to have them in the Kuali family.

QUARTERLY NEWSLETTER

June 2010

INTRODUCTION

The Kuali Spring Workshop 2010 in Ft. Collins, Colorado was a great success with 251 attendees and lots of work accomplished. In addition to the many meetings for project Boards, Functional Councils, Developers, and SMEs, Kuali Coeus (KC) kicked off their IRB tester training and Kuali Rice held a combined ARC/TRC meeting on key roadmap priorities. Celebrations were also in swing for the milestone KC 2.0 release and Kuali HR/Payroll created detailed plans for an initial deliverable.

NEW INVESTORS AND MEMBERS

New Members
Since our last published newsletter, we have added eight new members to the Kuali community. California State University, Office of the Chancellor and Tufts University are new investing partners in Kuali Ready and Duke University, University of Florida, North Carolina State University, Lehigh University, University of Chicago, and University of Pennsylvania are investing partners in Kuali OLE. We welcome all of these new members of Kuali!

Indiana University (IU) Becomes Investing Partner in Kuali Student Project
Indiana University, a founder in the Kuali community five years ago, has expanded its involvement by joining the Kuali Student (KS) initiative as an investing partner. See more at http://kuali.org/node/340.

KUALI PROJECT UPDATES

Kuali Coeus
The Kuali Coeus (KC) project is pleased to announce the release of Kuali Coeus 2.0.  This release includes both new functionality – the Award module - and additional functionality for the Proposal Development module. This release kicks off a number of implementations by partner schools in 2010, including Colorado State University, Indiana University, Cornell University, Michigan State University (pending funding approval), Iowa State University, the University of Arizona, the University of California, Irvine, and the University of California, Berkeley. See more at http://kuali.org/node/339.

On the heels of the milestone release of KC 2.0 on May 14th, 2010, the KC team is now focused on efforts to reach functional equivalency with Coeus 4.5 by the end of calendar year 2011.  The Coeus and Kuali Coeus communities have come together to work collaboratively toward this objective by comparing the applications, identifying the gaps, and defining the required specifications.  Development is underway on many of the gap features for Award, Budget, and Proposal Development.  It has been a complete team effort!    

Near future plans call for the release of KC 3.0 which will provide the Institutional Review Board (IRB) functionality in October 2010, closely followed by the KC 3.1 release in January 2011 providing functionality equivalent with Coeus 4.5 for the Award, Budget, and Proposal Development modules.  As for the ultimate objective, the Kuali Coeus team expects to deliver KC 5.0, fully equivalent to Coeus 4.5 for all modules, by the end of calendar year 2011.   These are indeed eventful days for the KC project!

Kuali Student
The Kuali Student Program (KS) released an initial version of the Curriculum Management (CM) module (Release 1.0) on May 15, 2010. The Founder’s Release comprises all of the business functionality and SOA software infrastructure to make possible the online creation, modification, approval, and retirement of courses. All KS business functionality is enabled by the Kuali Rice infrastructure services including identity services (KIM), the enterprise workflow engine (KEW) and new Business Rules Management services.  These infrastructure services will combine to make this and future Kuali Student modules highly configurable to match local business requirements.

In the Fall of 2010, Kuali Student will issue its first public software release of the Curriculum Management module (Release 1.1) with all of the capabilities described above for both courses and programs.

A Message from the Kuali Student Board Chair
Since the inception of Kuali Student, Cath Fairlie has provided outstanding leadership to our project in her role as Program Director. Cath did most of the heavy lifting in the early days of planning and preparing to launch the project and was instrumental in securing the $2.5M grant from the Andrew Mellon Foundation in October 2007. The KS Board had always hoped that Cath would remain with KS until we completed our first software release, and we are delighted that she was able to do so. However, we are now at a transition point and Cath has expressed her wish to move on to other challenges.  

Please join me in welcoming Dan McDevitt, of Indiana University, as the new Program Director of Kuali Student! Dan comes to us with deep and long-standing experience in large application development and implementation projects at IU. Dan will be spending a great deal of time with Cath over the next 6 weeks to ensure a smooth transition. Our goal is to make the leadership handover on July 1st as effective as possible.

Kuali Rice
Kuali Rice released version 1.0.2 on May 14th. This version included a few new pieces of functionality, including the ability to implement custom statuses on workflow documents as well as providing a way to link documents together.  It also included improvements to the Rice configuration system as well as numerous bug fixes. See more at http://kuali.org/node/337.

In parallel with development of the recently released 1.0.2 version, the Kuali Rice team is continuing to forge ahead with development of version 1.1.  Recent discussions within the Application and Technology Roadmap Committees of Kuali Rice have resulted in some reorganization of the deliverables for this version of Rice. Difficulties integrating support for the Java Persistence API (JPA) with the Kuali Nervous System architecture caused the roadmap committees to drop this from the 1.1 scope. Moving forward, the main priority of Kuali Rice 1.1 continues to be middleware version compatibility.  Once implemented, this will allow for older Kuali Rice client applications to interact successfully with a newer version of the Kuali Rice Standalone Server, a crucial feature for Kuali application projects to be written using different versions of Kuali Rice.  Additionally, it should help prevent "forced-march" upgrades for institutions with Kuali Rice implementations that include integration with numerous client applications.

Kuali Ready
This quarter has been very exciting for Kuali Ready - their community-hosted, Above Campus Service continuity planning tool is taking off! They successfully launched the hosted software-as-a-service to their founding partners on April 1st and already have eight instances up and running, with another six orders in the queue. In addition, at the Spring Workshop the Ready Board voted to open up subscriptions to any Kuali Foundation member and to select early adopters, so if you are interested in signing up or would like more information about the tool, please visit our page at http://kuali.org/ready.

Kuali Open Library Environment
In mid-April, Kuali OLE received matching fund contributions from The Andrew W. Mellon Foundation and began revising their overall timeline based on this milestone. The overall release cycle for Kuali OLE will now run July 2010-July 2012 with a first round test release in July 2011 and a release of Kuali OLE 1.0 scheduled for July 2012. Additionally, Brad Wheeler (Indiana University) and Deborah Jakubs (Duke University) were named as co-chairs of the OLE board, Robert McDonald (Indiana University) was named Kuali OLE Executive Director and Mike Winkler (University of Pennsylvania) was named the Kuali OLE Functional Council Chair. SME teams are also forming.

Currently Kuali OLE is seeking a lead architect and they will continue to post job advertisements for core team vacancies as they become available on the Kuali Foundation site. The Kuali OLE team will be posting positions for a data architect, a configuration/quality assurance manager and a lead developer in the near future.

Kuali Financial System
The Kuali Financial System project is in full steam for the KFS 4.0 release expected in late October 2010, which includes the new Endowment Module for managing endowment funds and their corresponding investments. This management will include a means to account for the investments, investment transactions, obligations, and the underlying funds to which those assets and liabilities belong.  This release will also include interfaces between Kuali Coeus and the Kuali Financial System that will automatically create Account and Budget Adjustment documents for Coeus Awards.   

Additionally, several partner institutions are contributing code back to the project for either enhancements or bug fixes.   This is very exciting as the project continues to formalize the contribution process to maximize and manage the adoption and application of community contributed code.

COMMERCIAL AFFILIATE PROFILE

Syntel is a global provider of Information Technology and Knowledge Process Services founded in 1980 in Troy, Michigan and listed on the NASDAQ in 1997 (SYNT). Revenues in 2009 were $419 Million with 14,000+ global employees and a market capitalization of ~$1.5 Billion. Syntel has been a Kuali Commercial Affiliate since 2007 and they established a Higher Education Center of Excellence (COE) to support the relationship with Kuali and develop functional and technical expertise on KFS and Rice. The team developed reusable assets, methodologies, tools, enhancements and accelerators to help clients manage their Kuali ecosystem including:

• Automated Testing of KFS using Syntel iTAP (integrated Test Accelerator Platform)
• Data Migration Workbench (Open Source Jasper ETL)
• KFS Reporting (Open Source Jasper Reports)
• Active Directory Integration (KFS user management) and Customized User Interface

Syntel offers services to manage the lifecycle of Kuali projects covering implementation (system implementation, customization, development, testing and migration) and maintenance (application support, upgrades and enhancements). 
Visit http://www.syntelinc.com/Industries.aspx?id=54 for additional information or contact Syntel at Sameer_Arora@Syntelinc.com.

QUARTERLY NEWS UPDATE

Kuali Foundation Receives Leveraging Excellence Award for 2010 from NCCI
The National Consortium for Continuous Improvement has honored the Kuali Foundation with the Leveraging Excellence Award for 2010. The Kuali Foundation joins MIT’s Venture Mentoring Service as the 2010 winners. See more at http://kuali.org/node/325.

Kuali Days 2010 Planning Underway
Kymber Horn (The University of Arizona) and Aaron Godert (Cornell University) have accepted the Conference Chair and Vice Chair roles for the next Kuali Days Conference and the conference committee has been meeting regularly. Starting this year, the Conference Committee will run a Call for Proposals, opening up the process to allow anyone to submit a presentation for consideration (open is inevitable!). More information is available at http://kuali.org/kd.

New job postings for the Kuali community
Our community is growing! Since the last quarterly newsletter, Boston University posted four positions for their KC implementation team, UWV is looking for a KC developer, and OLE posted for a new project manager. See the Kuali Insider feed for more information on these opportunities.  Are you looking to hire people for your Kuali implementation? Send your job announcement to help@kuali.org and ask the Kuali Foundation to post it to the Kuali website.

Continual improvements to Kuali’s collaboration infrastructure
As of May 15th, the Kuali community can now use one username and password for KIS, Jira, and Confluence. See more at http://kuali.org/node/325. On June 12th, Jira was upgraded to version 4.1 adding many new improvements.

UPCOMING EVENTS

Kuali Days 2010
November 8-10, 2010
Manchester Grand Hyatt, San Diego, CA
http://kuali.org/kd

EUNIS 2010
June 22-25, 2010
Warsaw, Poland
http://www.eunis.pl/

Advance CAMP: The Second Identity Services Summit
June 23-25, 2010
Raleigh, North Carolina
https://spaces.internet2.edu/display/ACAMPIdSummit2010/Home  

NCCI 2010
July 21-24, 2010
San Francisco, CA
http://bit.ly/bea0PV

NACUBO 2010 Annual Meeting
July 24-27, 2010
San Francisco, CA
http://www.nacuboannualmeeting.org/  

CACUBO Annual Meeting 2010
October 3-5, 2010
Indianapolis, IN
http://www.cacubo.org/announcements/Annual%20Meeting/index.html  

EDUCAUSE 2010
October 12-15, 2010
Anaheim, CA
http://net.educause.edu/e10
 

 

Posted:  Jun 21, 2010

We invite proposals for conference sessions at Kuali Days 2010 in San Diego, California. With Kuali projects moving from theory to practice and more institutions adopting Kuali applications, Kuali Days is changing from an internal community event focused on teams of subject matter experts to an event that will engage a wider audience that includes adopters, potential adopters, and end-users. Your contributions and innovative ideas will help us develop a comprehensive, community-generated conference. We encourage the Kuali community to join us in creating the next generation of Kuali Days!

The Conference will be held at the beautiful Manchester Grand Hyatt located on the San Diego Bay next to the City’s popular Seaport Village and steps away from Gaslamp Quarter with shopping, dining, and entertainment venues.

There are five tracks featured this year: Kuali Financial System, Kuali Coeus, Kuali Student, Kuali Rice, Kuali Implementers, and Other Topics. Detailed information on tracks, session types, and what to include in a proposal is available at http://kuali.org/kd2010/cfp

Submit a proposal online before August 2, 2010 at https://www.concentra-cms.com/cfp/proposal/47. Questions on the proposal submission process should sent to KualiCFP@concentra-cms.com

We look forward to seeing you at Kuali Days 2010: From Theory to Practice!
Additional information: http://kuali.org/kd

When your institution implements the Kuali Financial System, your users will be successful more quickly if you provide customized user guides that reflect your unique KFS configuration and financial administration processes. Such guides are not replacements for user training. They serve, instead, as day-to-day references that help users work effectively with your KFS system and the associated procedures and processes.

read more

Posted:  Jun 08, 2010

Original Post: http://sakaiproject.org/news/sakai-3-project-manager-job-description

Sakai is looking for a new breed of Project Manager. The vibrant, broadly distributed, very diverse next generation Sakai project needs a PM who can coordinate an agile development team with a focus on inclusion, participatory design and broad community engagement. If you are excited by this opportunity to explore new territory as part of the Sakai team, please apply here to the position entitled Sakai 3 Project Manager.

The project manager will be a line report to the Executive Director of the Sakai Foundation, but will be accountable to the Sakai 3 Steering Committee for the success of the project.” Under the above governance, the Project Manager is responsible for providing senior leadership, strategic direction, and technical expertise. S/he will aggregate and manage a team of IT professionals from multiple universities to meet the goals of the Sakai 3 Project, coordinating the planning, design, and implementation activities to deliver a production-ready Sakai product. In consultation with the Director, the incumbent defines the deliverables, timelines, priorities, and milestones of the project, leads the activities of the software development team, and coordinates with both academic and industry partners.

The incumbent is also responsible for refining the budget as the detailed plans are formulated and negotiating variations to resource commitments (financial and people) to ensure the successful progression of the project, and reporting to funding organizations for multiple projects.

These tasks require a combination of expertise in managing software projects, an understanding of formal software process, knowledge of the technological aspects of agile and open source software development, and strong communication skills. This is a fixed term position, ideally full-time, estimated for a duration of 12 months.

Job duties

1. Leads and coordinates software design, development, and testing teams
2. Requirements analysis and communication
3. Liaison and contract negotiation with outside organizations who will be partners or customers to reach contractual agreement on scope, schedule, deliverables, intellectual property considerations, and financial compensation.
4. Develops required materials including technical specifications, project and resource plans, project updates, presentation materials.
5. Liaises with current and potential project partners, Sakai community members, and external partners
6. Risk assessment and reporting
7. Provides expert technical leadership to the development team
8. Coordinates and tracks project deliverables from multiple teams by defining, implementing, and updating a project reporting process
9. Assists in managing financial resources for projects
10. Develops short term and long-term project plans, priorities and objectives

To ensure successful completion of projects the incumbent is expected to apply expertise specific to coordination of software development. S/he will apply communication, analytical, and negotiation skills to ensure success in the acquisition of resources. The incumbent will be independently responsible for achieving results and determining the degree of collaboration and direction required on a case by case basis as per the above governance.

The Sakai 3 project team is distributed across several continents and works together virtually. The Project Manager may work from any location. Because of time zone differences, work hours may be irregular.

Travel is required.

Qualifications

1. A minimum of ten years experience in both management of software projects and functional management of software development teams.
2. A background combining post-graduate education, hands-on design or development experience, and project management at a senior level, including experience in managing the business aspects of software projects, and demonstrated leadership and coaching skills.
3. Prior experience managing staff.
4. Demonstrated ability to communicate effectively and credibly.
5. A graduate degree in an area that covers project management as a topic of academic study (e.g., computer science, cognitive science, information studies, business, engineering) or the equivalent in experience (more than 3 years managing a major multi-partner project).
6. Expertise in the areas of open source software, user experience design, agile software methodologies, and accessible technology.
7. Demonstrated experience successfully managing software projects in a virtual environment.
8. Desirable: knowledge of the Sakai system and Community.

If you are excited by this opportunity to explore new territory as part of the Sakai team, please send a concise CV and an application addressing each of the qualifications individually and indicate your full-time/part-time availability by midnight Saturday, 12th June 2010 to Dr Philip Uys (puys@csu.edu.au).

Staff from institutions using Sakai are welcome to apply and a secondment from such institutions as their contribution to the project will be considered.

Note: Interviews could be held as early as Thursday, 17th June.

 

Posted:  Jun 07, 2010

This June, the Kuali Foundation will make a number of improvements to our collaboration infrastructure:

• On Saturday, June 12 we will upgrade our Jira system. The newer version of Jira includes improved dashboards, gadgets and reporting, and promises a boost in speed. We strongly encourage Jira users to get familiar with the new Jira interface by going to our Jira test environment.
• Kuali's mailing lists are moving from Sakai to Google Groups, and we are taking this opportunity to change the address of many lists so that they meet our naming conventions. If you are ever not sure of the correct address to use, consult your team's page in KIS or look at this quick reference page: KIS -> Mailing Lists.
• In late June, we will upgrade our Confluence installation

Remember to write to help@kuali.org if you ever have problems accessing Kuali resources or using our collaboration infrastructure.

 

AbstractIn KIS of the Dragon, I documented using the liquibase rollback functionality for testing. Since then, I have found that liquibase has a small bug with rollbacks. Some of you may have encountered it. It uses regex substitution when rolling back (not sure what exactly). Part of defining the group in regex substitution is the '$', so that makes '$' kind of a reserved character that isn't very well documented in liquibase. It doesn't effect SQL at all, but it does mean using '$' in changeSet attributes is forbidden. Just to give an example of what will happen, when you rollback in this scenario, you get an exception:

Jun 5, 2010 8:07:24 AM liquibase.commandline.Main main
SEVERE: Illegal group reference
java.lang.IllegalArgumentException: Illegal group reference
at java.util.regex.Matcher.appendReplacement(Matcher.java:725)
at java.util.regex.Matcher.replaceFirst(Matcher.java:872)
at java.lang.String.replaceFirst(String.java:2158)
at liquibase.database.AbstractDatabase.removeRanStatus(AbstractDatabase.java:1328)
at liquibase.parser.visitor.RollbackVisitor.visit(RollbackVisitor.java:23)
at liquibase.parser.ChangeLogIterator.run(ChangeLogIterator.java:41)
at liquibase.Liquibase.rollback(Liquibase.java:273)
at liquibase.Liquibase.rollback(Liquibase.java:248)
at liquibase.commandline.Main.doMigration(Main.java:682)
at liquibase.commandline.Main.main(Main.java:97)

Below, we have the offending XML responsible for this.
<databaseChangeLog
xmlns="http://www.liquibase.org/xml/ns/dbchangelog/1.9"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog/1.9
http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-1.9.xsd"&gh;

<changeSet id="$Revision$" author="$Author$">
ProblemYou probably thought the above was the problem. No no no no no. That was just background on it. Such a thing is actually easily fixed. The real problem is testing in your IDE. The reason we have '$' is for the Subversion keywords. We want these in our changelogs so we can rollback in our other environments. Subversion doesn't actually add this information until after the svn:keywords property and the file are committed to the VCS. When it does, you get something that looks like this:
<databaseChangeLog
xmlns="http://www.liquibase.org/xml/ns/dbchangelog/1.9"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog/1.9
http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-1.9.xsd"&gh;

<changeSet id="$Revision: 1$" author="$Author: przybyls$">
There are still '$' in there.

What does this have to do with the IDE?At UA, we use a liquibase template, so all developers are consistent with their usage. It looks something like:

<?xml version="1.0" encoding="UTF-8"?>

<databaseChangeLog
xmlns="http://www.liquibase.org/xml/ns/dbchangelog/1.9"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog/1.9
http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-1.9.xsd">

<changeSet id="$Revision$" author="$Author$">
<sql splitStatements="false" endDelimiter=""><![CDATA[
DECLARE
BEGIN
END;
]]>
</sql>
<rollback>
<sql><![CDATA[
DECLARE
BEGIN
END;
]]>
</sql>
</rollback>
</changeSet>
</databaseChangeLog>
The first thing you should notice is the '$' in the id and author attributes. This actually makes the problem part of our IDE. Now developers have to remember to change this. That makes this template pretty much...useless.

Solution (it's not as cool as you think)At UA, we decided to take liquibase testing out of our IDE and instead move it into continuous integration with Ad-Hoc builds. In the end, developers still use the template. Only now, they don't need to install liquibase at all! It's one of those, "Why didn't I think of this before!?" moments.

Instructions for HudsonI hope you're using Hudson. If you're not, you have my sympathies. I am truly sorry that you will have to find your own way of doing this.

Step 1: Create an ad-hoc buildTo do this, you simply setup a build parameter in your project/build configuration. When you do this, Hudson will want to know about the parameter you are adding. I used a file. This way developers simply upload their file to Hudson. I called mine test.xml and you will see that come up in a second.

Step 2: Setup the Execution ScriptI just used shell with the following contents:

/home/tomcat/liquibase/liquibase --defaultsFile=/home/tomcat/renwoluk.properties tag before
sed -e 's/\$Revision\$/test/g' test.xml > /tmp/test.xml;mv /tmp/test.xml test.xml
sed -e 's/\$Author\$/test/g' test.xml > /tmp/test.xml;mv /tmp/test.xml test.xml
/home/tomcat/liquibase/liquibase --defaultsFile=/home/tomcat/renwoluk.properties --changeLogFile=test.xml updateSQL
/home/tomcat/liquibase/liquibase --defaultsFile=/home/tomcat/renwoluk.properties --changeLogFile=test.xml update
/home/tomcat/liquibase/liquibase --defaultsFile=/home/tomcat/renwoluk.properties --changeLogFile=test.xml rollbackSQL before
/home/tomcat/liquibase/liquibase --defaultsFile=/home/tomcat/renwoluk.properties --changeLogFile=test.xml rollback before

Notice the sed commands that do the replace on test.xml. It is then simply doing an update and rollback just like in KIS of the Dragon.

ConclusionThat's it. Now developers can all test their liquibase changelogs in a consistent manner without any modification to their IDE. Hudson is also really effective here because changelog testing is really really fast. It takes a few seconds and won't hang up Hudson. Hudson also can facilitate multiple executors. I will include in another post on liquibase automation how to integrate this into configuration management and automated build processes.

ApologiesI am very sorry for the content in KIS of the Dragon because it was somewhat incorrect. I'm glad to remedy it here.

I also apologize for having not put out a screencast in awhile. My goal was one a week. I've had some family crisis to deal with lately and I made the mistake of working on a few at the same time. In the coming week, expect a torrent of posts.

Posted:  May 14, 2010

The Kuali Coeus (KC) project is pleased to announce the release of Kuali Coeus 2.0.  This release includes both new functionality – the Award module - and additional functionality for the Proposal Development module.  This release, building on the functionality of KC 1.1.1, allows implementing schools to: 

• Create and maintain sponsored awards, including award budgets, reporting requirements, invoicing and payment schedules, and award terms and conditions
• Create and maintain complex award hierarchies to show relationships between parent and children awards
• Link submitted proposals to awards with Institutional Proposal and Proposal Log
• Create, route, and submit proposals for both Grants.gov and non-Grants.gov submissions
• Create proposal budgets at various levels of detail
• Create and maintain complex proposal hierarchies so that individually routed and created proposals can be linked together for aggregate submissions

The release of Kuali Coeus 2.0 will kick-off a number of implementations by our partner schools in 2010, including Colorado State University, Indiana University, Cornell University, Michigan State University (pending funding approval), Iowa State University, the University of Arizona, the University of California, Irvine, and the University of California, Berkeley.  

This release represents a significant milestone on our path to achieving functional equivalence with Coeus in 2011. The occasion will be marked by a joint meeting of the Kuali Coeus Functional Council and Coeus Steering Committee at Colorado State University later this month.  Coeus and Kuali personnel continue to work hard towards the goal of full equivalence with Coeus, and a convergence of our communities.  

This release would not be possible without the extremely hard work of the Kuali and Coeus participants on the Subject Matter Expert Teams, Development Team, and Quality Assurance teams.  We are profoundly grateful for the amazing effort of everyone involved in this project. 

Download KC 2.0 at: http://kuali.org/download-form

Our next release, scheduled for Fall 2010, includes the IRB/Human Participants module. You can view the KC Timeline at: http://www.kuali.org/kc/timeline

Posted:  May 14, 2010

The Kuali Rice team is happy to announce the availability of version 1.0.2 of Kuali Rice.

Highlights of this release include:

• KEW Application Document Status Enhancement
• Addition of document linking mechanism
• Fixes for the "remote" run mode for KIM and other Rice modules
• Rice Configuration System Enhancements

Download links, release notes (including upgrade instructions), and online documentation can all be found in our documentation portal located at:

http://rice.kuali.org/docs/1.0.2

Thanks everyone and enjoy!