Opensis Integration: Difference between revisions
From MoodleDocs
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
#Transition to adodb | #Transition to adodb | ||
##Transition to moodle/lib/dmllib.php calls | ##Transition to moodle/lib/dmllib.php calls | ||
# | #Evaluate OpenSIS language strings (get terminology matching with Moodle) | ||
# | #Evaluate OpenSIS table structures | ||
#Evaluate OpenSIS permissions scheme and migrate toward Moodle user, role, capability, context schema | |||
#Assessment OpenSIS security | #Assessment OpenSIS security | ||
##ensure md5 passwords | ##ensure md5 passwords | ||
Revision as of 15:33, 12 May 2009
This document hopes to outline the goals of integrating OpenSIS with Moodle.
Major Milestones
- MySQL integration
- Transition to adodb
- Transition to moodle/lib/dmllib.php calls
- Evaluate OpenSIS language strings (get terminology matching with Moodle)
- Evaluate OpenSIS table structures
- Evaluate OpenSIS permissions scheme and migrate toward Moodle user, role, capability, context schema
- Assessment OpenSIS security
- ensure md5 passwords
Desired functionality from integration
- Users - Single signon for teachers, students, administrators between both systems. The disadvantage to this is that an account will need to be created in OpenSIS for all Moodle users. Alternatively, OpenSIS could use Moodle for authentication which allows for authentication via LDAP and others.
- Courses - Courses created in OpenSIS should automatically create a course in Moodle. By default, this should use the following Course category hierarchy (Marking period, subject (department), course).
- Enrollments - Teachers and students assigned to a course/period should be automatically enrolled in the Moodle course.
- Grades -
