Course Management Service Documentation

The Course Management Service provides support for defining a structure of courses, offerings, and sections based on requirements given in course-management-reqs-6.doc. This structure will be tied into the Sakai [ENC:SuperStructure], which means that tools and resources can be attached directly to sections. The Service provides a means to identify instructors and other people with specific roles in the educational process. It defines a roster of students and their status in sections. The complete design is available in course-management-design-6.doc

Definitions

A Canonical Course is a general course that exists across terms. It is an abstract course.

A Course Offering can occur in a specific term and have a grade type, status type, etc. A course offering is a canonical course associated with a specific term. It may be concrete where the canonical is abstract. The roster associated with a course offering allows sections to be aggregated.

A Course Section is an instance of a course offering that has a schedule, location, roster, etc. Sections may also have Sub-Sections.

A Course Set is a set of canonical courses that can be used to describe majors, departments and other high level collections of canonical courses.

A [ENC:Session] is a unit of time in which a course offering exists. It can include a schedule of events, such as holidays.

An [ENC:Enrollment Record] describes the participation of a person in a course, their role, and their status in the course.

A [ENC:Student] is a participant in a course. Students will have an enrollment status.

A [ENC:Leader] is the designated teacher of a course. A course or section may have more than one leader. The term "leader" is used in a very generic sense and is not intended to convey a particular title or qualification.

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Apr 25, 2005

    casey dunn says:

    Where does the responsibility for tracking content associated with a canonical c...

    Where does the responsibility for tracking content associated with a canonical course lay?

  2. Apr 25, 2005

    casey dunn says:

    OK, further reading (I had started with this page and the design doc) - the Requ...

    OK, further reading (I had started with this page and the design doc) - the Requirements doc's Query and Access section mentions these as assets, and indicates that the assets are associated with the course offering or section.

    canonical assets would promote / support asset reuse.

  3. Apr 26, 2005

    casey dunn says:

    If canonical courses are going to be the route for resolving cross-listing group...

    If canonical courses are going to be the route for resolving cross-listing group membership (as well as asset lists) the service api will have to return time based (term, session, quarter) collections/lists/foo.

    I'm speaking from the POV of "reduce your sets as quickly as possible," if that's unclear.

  4. Apr 26, 2005

    Mark J. Norton says:

    The precise relationship between course management and content assests associate...

    The precise relationship between course management and content assests associated with a course (of any flavor) is still in flux. As the Sakai SuperStructure concept starts to be included in future tool development, we may find that there are simpler ways to manage course content.

    It would help if you could express your needs either as use cases or requirements. Send them directly me, please.

  5. Feb 22, 2006

    Jim Farmer says:

    The concept of a "session" as a concept was abandoned by community colleges in t...

    The concept of a "session" as a concept was abandoned by community colleges in the mid-1970s when "open entry, open exit" courses were offered, in continuing education when courses were added with a series of "events," and later when "executive" MBA programs were added. Some have no concept of "session" or "term" and in others it becomes a statistical measure.

    In developing the Illinois BHE and community colleges information systems, each offering was linked to a series of dates-yes a "term" was an option. "Open Entry, and open exit" courses were counted at wherever the mid-point of the expected completion date occurred even though a student had two yearsmore with approval-to "complete" a course. And to make it more complex, students could be given partial credit for learning objectives that had been accomplished. One could, for example, get 1.33 units of History 203 having completed one-third of a four unit course.

    Following these procedure-subsequentlly adopted by several state systems-I would omit session except, perhaps, as part of an identifier of a course offering. And now most colleges have section numbers that are unique for a college year. (Note again, the college year is a "variable" for open entry, open exit).

  6. Feb 22, 2006

    Jim Farmer says:

    The strikeouts in the previous post were made by Confluence which seems to have ...

    The strikeouts in the previous post were made by Confluence which seems to have different opinions that I do about the text.