I Did Not Know You Could Do That With An SIS: How To Make Kuali Student Work For You

transcript

open source administration software for education

next generation student system

Norman Wright, Business Analyst, University of Southern California Doug Chew, Systems Analyst, University of British Columbia Kamal Muthuswamy, Senior Application Systems Engineer, University of Washington

In The Next 60 Minutes …

• Introduction• Architecture• UI Configuration• Search Configuration• Data Configuration• Workflow Configuration• Challenge• Q/A

From the Charter…

• Kuali Student will be a modular, open source, standards-based next generation student system that will offer a flexible, scalable, cost-

effective system that can be configured to meet the business requirements of any higher education institution

That’s a tall order….

• We wanted a system that is infinitely configurable!

• So we came up with….

Welcome to Kuali Student R1.1

No Actually…

• The Charter Translated into reality….• We analyzed not just the founder and partner

schools but did a wide scan….• How do schools actually differ?

– Look and Feel– Validation– Text and labels– Additional Data– Lookups– Workflow

Draw a Distinction between Validation & UI

Validation• Cares about what

– Data– Rules– Integrity

• Must be rock solid• One Rule for all contexts

User Interface• Cares about how

– Look and feel– Ordering– Ease of Entry

• Can allow in invalid data – and then validation gives

error• Varies by context

The resulting KS Architecture

• Highly Configurable• SOA Based• GWT Driven UIF • Spring beans based configurations

KS Architecture

Configuring UI

• GWT Deferred Binding• Themes• Hiding Sections / Fields• Messages

KS Look and Feel

Institution Look and Feel

Hiding a Section / Field

• Extend CourseConfigurer• Override methods

• Deferred Binding to replace CourseConfigurer

Removing the Financials Section

Before After

Hide Pass Fail Field

Before After

Kuali Student Message Maintenance

• Validation messages• Constraints• Labels• Help text• Instruction text

Labels

Before

Help Text

Before

Configuring Lookups & Searches

Subject Area as Search Oracle

Subject Area as Drop Down

Before xml

• <property name="widget" value="SUGGEST_BOX" />

• <property name="resultDisplayKey“ value="enumeration.resultColumn.abbrevValue" />

• <property name="resultSortKey" value="enumeration.resultColumn.sortKey" />

After xml

• <property name="widget" value="DROP_DOWN" />

• <property name="resultReturnKey" value="enumeration.resultColumn.abbrevValue"/>

• <property name="resultDisplayKey" value="enumeration.resultColumn.value" />

• <property name="resultSortKey" value="enumeration.resultColumn.sortKey" />

Applies Cross-listing entry as well

Start Term Before

Start Term after

XML For configuring what is allowed

• <property name="key" value="atp.advancedAtpSearchParam.atpType" />• <property name="name" value="Atp types" />• <property name="desc" value="Atp types for courses" />• <property name="caseSensitive" value="false" />• <property name="writeAccess" value="NEVER" />• <property name="dataType" value="STRING" />• <property name="optional" value="true" />• <property name="defaultValueList">• <list>• <value>kuali.atp.type.Spring</value>• <value>kuali.atp.type.Fall</value>• <value>kuali.atp.type.Session1</value>• <value>kuali.atp.type.Session2</value>• <value>kuali.atp.type.Mini-mester1A</value>• <value>kuali.atp.type.Mini-mester1B</value>• </list>• </property>

XML For configuring what is allowed

• <property name="key" value="atp.advancedAtpSearchParam.atpType" />• <property name="name" value="Atp types" />• <property name="desc" value="Atp types for courses" />• <property name="caseSensitive" value="false" />• <property name="writeAccess" value="NEVER" />• <property name="dataType" value="STRING" />• <property name="optional" value="true" />• <property name="defaultValueList">• <list> • <value>kuali.atp.type.Spring</value>• <value>kuali.atp.type.Fall</value>• • </list>• </property>

Browse Catalog Before

Browse Course Catalog After

Data Configuration: Dictionaries

• Central to KS data configurations• Spring bean based XML files• Manages constraints around data• Allows adding new data fields without code

changes• Easy to extend and override• Consumed by both the services and UIF

Data Configuration: Overriding default constraints

• Basic constraints – minLength, maxLength, validChars, etc

• Conditional constraints– When State = ‘active’ require Title

• Lookup based constraints– Program Code should be in X lookup table

• Custom constraint– Any custom logic for validating fields

Basic Constraints: Before

Basic Constraints: After

Basic Constraints: XML

• <bean id="courseInfo.courseNumberSuffix-parent" abstract="true"parent="cluIdentifierInfo.suffixCode-parent">• <property name="name" value="courseNumberSuffix" />• <property name="minLength" value=“4" />• <property name="maxLength" value=“4" />• <property name="validChars" ref="digits" />• <property name="caseConstraint">• <bean parent="caseConstraint">• <property name="operator" value="EQUALS"/>• <property name="fieldPath" value="state"/>• <property name="whenConstraint">• <list>• <bean parent="whenConstraint">• <property name="values“> <list> <value>DRAFT</value> </list> </property>• <property name="constraint">

Custom Validation: Before

Custom Validation: After

Custom Validation: XML

• <bean id="courseInfo.revenues-parent" abstract="true" parent="baseComplexRepeating">

• <property name="name" value="revenues" />• <property name="dataObjectStructure"

ref="org.kuali.student.lum.course.dto.CourseRevenueInfo" />• </bean>

• <bean id="courseInfo.revenues" parent="courseInfo.revenues-parent" >

• <property name="customValidatorClass" value="org.kuali.student.lum.course.service.utils.RevenuePercentValidator"/>

• </bean>

Data Configuration:Adding new fields

• Dynamic attributes (DA) on most message structures

• No code change required at the service level• All constraints available for DA• Expose DA as regular field to KS UIF

Adding New Field: Before

Adding New Field: After

Adding New Field: XML

• <bean id="org.kuali.student.lum.course.dto.CourseInfo-parent” abstract="true" parent="objectStructureDefinition">

• <property name="attributes“> <list>• • <ref bean="courseInfo.finalExamStatus" />• <ref bean="courseInfo.finalExamRationale"/>• </list> </property>• </bean>

• <bean id="courseInfo.finalExamStatus" parent="baseString">• <property name="name" value="finalExamStatus" />• <property name="maxLength" value="15" />• <property name="validChars" ref="alpha"/>• • <property name="dynamic" value="true"/>• </bean>

More Configuration

• Configure ATP, Messages, Enumerations

• Configure Rules (RequirementComponents)

Infrastructure Configuration

• Tomcat 6.0.24• JAVA JDK: 1.6.0_18• RICE 1.03• dB:• Oracle XE 10.2.0 for development and test• Oracle 11G in test• OS: Fedora 8

Configuring Workflow

• KSOR - Kuali Student Organizations• KIM - Kuali Identity Management• KEW - Kuali Enterprise Workflow

KS Organization

• Publication Office• Senate• Division• College• Department

UBC Organization Approval Hierarchy

• Publication Office• Senate• Faculty• Department

Positions and People

• Define positions in organizations• Add people in Kuali Rice (KIM)• Configure KIM for field level authorization

Organization Memberships

• Memberships - add people to positions• Workflow tied to positions

KS Approval Workflow

UBC Approval Workflow

Complex Workflows - Branches

• Branches• Logic Split Nodes

Undergraduate Course

Proposal

Workflow

Graduate Course

Proposal

Workflow

Standard UBC Workflow

Pilot Course Workflow

Proposal

Workflow

Summary

• Highly not Infinitely Configurable• Leverage Configurability in Rice• Clean separation of different layers of

archictecture

• KS Configuration Guide

KS Configuration Challenge

Questions

I Did Not Know You Could Do That With An SIS: How To Make Kuali Student Work For You

Technology