Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

ModelFeatureKSOSIDComments
canonical courses CourseService.Courseosid.course.Course 
 campusCourseService.Course.CampusLocationsosid.course.Course.CourseCampusRecord 
 codeCourseService.Course.Codeosid.course.Course.Number 
 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 coursesCourseService.Course.CrossListingsosid.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.CourseFeeRecordKS has not been redesigned with respect to KSA.
 instructors

CourseService.Course.PrimaryInstructor

CourseService.Course.Instructors

osid.acknowledgement.Credit

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 coursesCourseService.Course.Jointsosid.relationship.Relationship 
 learning objectivesCourseService.Course.CourseSpecificLososid.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 coursesCourseService.Course.isPilotCourseosid.course.Course.PilotCourseRecord 
 prerequisitesrulesosid.course.Course.PrerequisitesOSIDs should rename these rules to requisites.
 special topicsCourseService.Course.IsSpecialTopicsCourseosid.course.Course.SpecialTopicsCourseRecord 
 subject areasCourseService.Course.SubjectAreaosid.ontology.SubjectOSID subject tagging not used as an identifier.
 terms offeredCourseService.Course.TermsOfferedosid.course.Course.TermsOfferedCourseRecordMuddled feature.
 time

CourseService.Course.Duration

CourseService.Course.OutOfClassHours

 OSIDs manage at the activity level but doesn't roll up to the course level.
 versioningCourseService.Course.Versionosid.journaling.JournalEntry 
canonical formats CourseService.Format KS uses Formats to vary the Activities. OSIDs can surface these as different Courses.
canonical activities CourseService.Activityosid.course.ActivityUnit 
 content ownerCourseService.Activity.UnitsContentOwnerosid.course.Activity.ContentActivityRecord 
 estimated enrollmentCourseService.Activity.DefaultEnrollmentEstimateosid.course.Activity.EnrollmentActivityRecord 
 learning objectivesCourseService.Activity.Attributesosid.course.ActivityUnit.LearningObjectives 
 time estimates

CourseService.Activity.ContactHours

CourseService.Activity.Attributes

osid.course.ActivityUnit.TotalTargetContactTime

osid.course.ActivityUnit.TotalTargetIndividualEffort

osid.course.ActivityUnit.WeeklyContactTime

osid.course.ActivityUnit.WeeklyIndividualEffort

KS adds more detail at offering.
canonical program ProgramService.XYZProgramosid.course.program.Program 
 accrediting agenciesProgramService.MajorDiscipline.AccreditingAgenciesosid.course.program.Program.AccreditationProgramRecord(question) Accreditation should be modeled.
 classificationProgramService.XProgram.UniversityClassificationosid.ontology.Subject 
 codeProgramService.XProgram.Codeosid.course.program.Program.Number 
 codes (other)

ProgramService.XProgram.Cip2000Code

ProgramService.XProgram.Cip2010Code

ProgramService.XProgram.HegisCode

osid.ontology.Subject 
 core programProgramService.CoreProgramosid.relationship.Relationshipprogram hierarchy
 credentialsProgramService.CredentialProgram.ResultOptionsosid.course.program.Program.Credentials 
 effective dating

ProgramService.XProgram.EffectiveDate

ProgramService.XProgram.StartTerm

ProgramService.XProgram.EndTerm

ProgramService.XProgram.EndProgramEntryTerm

osid.course.program.rules.ProgramEnabler 
 honorsProgramService.HonorsProgramosid.relationship.Relationshipprogram hierarchy
 intensityProgramService.XProgram.Intensityosid.ontology.Subject 
 instructors

ProgramService.MajorDiscipline.PublishedInstructors

osid.acknowledgement.Credit(question)
 learning objectivesProgramService.XProgram.LearningObjectivesosid.course.program.Program.LearningObjectives 
 levelProgramService.CredentialProgram.Levelosid.course.Program.LevelProgramRecord 
 locationProgramService.XProgram.CampusLocationsosid.course.program.Program.CampusProgramRecord 
 majorsProgramService.MajorDisciplineosid.relationship.Relationshipprogram hierarchy
 minorsProgramService.MinorDisciplineosid.relationship.Relationshipprogram hierarchy
 orgs

ProgramService.XProgram.DivisionsContentOwner

ProgramService.XProgram.DivisionsStudentOversight

ProgramService.XProgram.DivisionsDeployment

ProgramService.XProgram.DivisionsFinancialControl

ProgramService.XProgram.UnitsContentOwner

ProgramService.XProgram.UnitsFinancialResources

ProgramService.XProgram.UnitsFinancialControl

ProgramService.XProgram.UnitsDeployment

ProgramService.XProgram.UnitsStudentOversight

ProgramService.CredentialProgram.Institution

osid.course.program.Program.Sponsors

osid.course.program.Program.XYZOrgProgramRecord

osid.authorization

 

these are overkill in KS
 publication targetsProgramService.CProgram.CatalogPublicationTargetsosid.course.program.Program.PublicationProgramRecord 
 requirementsProgramService.XProgram.ProgramRequirementsosid.course.program.Program.CompletionRequirements 
 review periodProgramService.MinorDiscipline.NextReviewPeriodosid.course.program.Program.ReviewProgramRecordReviews should be properly modeled.
 titles

ProgramService.XProgram.ShortTitle

ProgramService.XProgram.LongTitle

ProgramService.XProgram.TranscriptTitle

ProgramService.CProgram.DiplomaTitle

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.
 urlProgramService.CProgram.Urlosid.course.program.Program.URLProgramRecord 
 variationsProgramService.ProgramVariationosid.relationship.Relationshipprogram hierarchy
 versioningProgramService.XProgram.Versionosid.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 

...