| Legend |
|---|
| straight forward feature mapping |
| feature mapping through orchestration or other OBA |
| poor design of feature |
| missing feature |
Curriculum
| Modeling Support | Feature | KS | OSID | Comments |
|---|---|---|---|---|
| canonical courses | CourseService.Course | osid.course.Course | ||
| campus | CourseService.Course.CampusLocations | osid.course.Course.CourseCampusRecord | ||
| code management | CourseService.Course.suffix CourseService.Course.level CourseService.Course.SubjectArea | osid.course.Course.CourseCodeRecord | OSIDs can assign more than one "level" to a Course as defined by its GradeSystem. | |
| cross listed courses | CourseService.Course.CrossListings | osid.course.Course.CourseCrossListingRecord | ||
| effective dating | CourseService.Course.EffectiveDate CourseService.Course.ExpirationDate CourseService.Course.StartTerm CourseService.Course.EndTerm | osid.course.Course.IsActive osid.course.rules.CourseEnabler | This data in KS informs the offerability is the course but may not be enforced. | |
| fees | CourseService.Course.Fees CourseService.Course.Revenue CourseService.Course.Expenditure | osid.course.Course.CourseFeeRecord | KS has not been redesigned with respect to KSA. | |
| instructors | CourseService.Course.PrimaryInstructor CourseService.Course.Instructors | osid.contact.Contact | In KS, the canonical instructors are not necessarily the ones who are teaching in a particular term, but instructors who are associated with the course. | |
| joint courses | CourseService.Course.Joints | osid.relationship.Relationship | ||
| learning objectives | CourseService.Course.CourseSpecificLos | osid.Course.LearningObjectives | ||
| names | CourseService.Course.CourseTitle CourseService.Course.TranscriptTitle | osid.course.Course.DisplayName osid.course.Course.Title | OSID display names are brought into "context" (e.g. a transcript application gets the transcript title through the display name while the LMS may see the course code through the display name). Management of these different names can be done via OsidRecord. | |
| options | CourseService.Course.CreditOptions CourseService.Course.GradingOptions | osid.course.Course.CreditAmounts osid.course.Course.GradingOptions | ||
| organizations | CourseService.Course.UnitsDeployment CourseService.Course.UnitsContentOwner | osid.course.Course.Sponsors osid.course.rules.CourseProcessorEnabler | Content owner is a better name than sponsors. Deployment smells like an authorization rule. | |
| pilot courses | CourseService.Course.isPilotCourse | osid.course.Course.PilotCourseRecord | ||
| prerequisites | rules | osid.course.Course.Prerequisites | OSIDs should rename these rules to requisites. | |
| special topics | CourseService.Course.IsSpecialTopicsCourse | osid.course.Course.SpecialTopicsCourseRecord | ||
| subject areas | CourseService.Course.SubjectArea | osid.ontology.Subject | OSID subject tagging not used as an identifier. | |
| terms offered | CourseService.Course.TermsOffered | osid.course.Course.TermsOfferedCourseRecord | Muddled feature. | |
| time | CourseService.Course.Duration CourseService.Course.OutOfClassHours | OSIDs manage at the activity level but doesn't roll up to the course level. | ||
| versioning | CourseService.Course.Version | osid.journaling.JournalEntry | ||
| canonical formats | CourseService.Format | KS uses Formats to vary the Activities. OSIDs can surface these as different Courses. | ||
| canonical activities | CourseService.Activity | osid.course.ActivityUnit | ||
| content owner | CourseService.Activity.UnitsContentOwner | osid.course.Activity.ContentActivityRecord | ||
| estimated enrollment | CourseService.Activity.DefaultEnrollmentEstimate | osid.course.Activity.EnrollmentActivityRecord | ||
| learning objectives | dynamic attributes | osid.course.ActivityUnit.LearningObjectives | ||
| time estimates | CourseService.Activity.ContactHours | osid.course.ActivityUnit.TotalTargetContactTime osid.course.ActivityUnit.TotalTargetIndividualEffort osid.course.ActivityUnit.WeeklyContactTime osid.course.ActivityUnit.WeeklyIndividualEffort | ||
| canonical program | ||||
| classification | ProgramService.XProgram.UniversityClassification | osid.ontology.Subject | ||
| code | ProgramService.XProgram.Code | osid.course.program.Program.Number | ||
| codes (other) | ProgramService.XProgram.Cip2000Code ProgramService.XProgram.Cip2010Code ProgramService.XProgram.HegisCode | osid.ontology.Subject | ||
| core program | ||||
| credential program | ||||
| effective dating | ||||
| intensity | ProgramService.XProgram.Intensity | osid.ontology.Subject | ||
| majors | ||||
| minors | ||||
| honors | ||||
| titles | ProgramService.XProgram.ShortTitle ProgramService.XProgram.LongTitle ProgramService.XProgram.TranscriptTitle | osid.course.program.Program.DisplayName osid.course.program.Program.Ttitle osid.course.program.Program.TranscriptProgramRecord | OSID display names are brought into "context" (e.g. a transcript application gets the transcript title through the display name while the LMS may see the course code through the display name). Management of these different names can be done via OsidRecord. | |
| variations | ||||
| versioning | ProgramService.XProgram.Version | osid.journaling.JournalEntry | ||
| syllabus | osid.course.syllabus.Syllabus | |||
| content | osid.course.syllabus.Docet.Assessements osid.course.syllabus.Docet.Assets | |||
| learning objectives | osid.course.syllabus.Docet.LearningObjectives | |||
| modules | osid.course.syllabus.Module | |||
| time management | osid.course.syllabus.Docet.Duration |
Offering
Registration
Academic Record
Academic Plan
General Services
| Modeling Support | Feature | KS | OSID | Comments |
|---|---|---|---|---|
| acknowledgement | ||||
authentication | ||||
| authorization | ||||
| cataloging | ||||
| commenting | ||||
| communication | ||||
| contact | ||||
| logging | ||||
| messaging | ||||
| ontology | ||||
| person | ||||
| process | ||||
| relationship | ||||
| room | ||||
| search | ||||
| sequencing | ||||
| state | ||||
| repository | ||||
| type | ||||
| versioining |