Submit a Ticket My Tickets
Login  Sign up

Setting up the Course Template

Table of Contents
Pre-Built Course Template Fields
Primary and Graded Component
Course Aliases
Dependencies Management
Template Fields (In Depth)
Notes on Custom Fields
Required Learning Outcomes

LOCATION: Scheduling > Settings > Course Template
The course template defines the basic set of information that constitutes a course. It is often determined by making sure that the fields map with an institution's student information system, in addition to any fields that may be handled outside of the SIS. It uses the same drag and drop form builder that is described in Setting up Curriculum Forms

An example course template could include:

  • Subject Code

  • Course Number

  • Course Title

  • Department(s)

  • College/School

  • Start Term

  • End Term

  • Description

  • Topics

  • Files

  • Learning Outcomes

  • Syllabi

  • Credits (Fixed, Variable, etc.)

  • Requisites. 


Pre-Built Course Template Fields

Delivered prebuilt fields can't be adjusted to have the "single" or "multiple" value changed. In these cases, we advise that the client create custom fields or arrange for an enhancement. 

Primary and Graded Component

  • Primary Component and Graded Component are fields built for PeopleSoft customers. These are stored at the course level, rather than within the pre-built Components card. The options shown on the drop-downs for these fields are automatically fetched from the available components on a given course (i.e. the Component Name fields for that course, as defined in the pre-built Components card). It is worth noting that if a component doesn’t have a name, it will not show up on the drop-down list. The drop-down is updated in real time (i.e. if a user edits the course and adds a Component Name, this new name will immediately show up as an option in the Primary/Graded Component drop-downs).
  • If `Optional Component = Yes`, then the component is not displayed as an option in the `Primary Component` and `Graded Component` fields. This change prevents Course POST errors and prevents end users from accidentally selecting `optional components` as `primary components` and `graded components`. This behavior enhancement is aligned with how the fields operate in Peoplesoft. 
  • In the below example, we have setup two components. One has `Optional Component = Yes` and the other has `Optional Component = No`.

Only the Lecture component is available for selection as the primary component or the graded component. 

Course Aliases

We want to add a new input for the course template called "Aliases". This input can only be allowed once in the Course Template and in the Form.

Aliases are when Courses can have two different Course Codes (as a reminder, what is called the Course Code is usually just an institution's way of saying Subject Code + Course Number, so MATH101 is a course code).

Some courses might have multiple course codes. An example of which is BIOCHEM101. 

This course is a Biology Chem course, offered in the Biology department. However, chemistry majors call this course CHEM101, so it can stay consistent with the fact that Chemistry majors must take CHEM courses. In other words, these students take the same class, but for reporting purposes, they have different names. 

Courses can have multiple aliases (so it will be an array of objects). 

Dependencies Management

For schools that don't utilize our requisite builder, we have implemented the ability to hide the "dependencies" card. This can be set by navigating to the template, clicking the eye icon in the "dependencies" card, then modifying visibility settings.

Template Fields (In Depth)

For the CIP / Hegis code fields: 

  • Options for these fields are loaded in from the integration. 
  • The value is stored as the actual code of the data: "CIP Code" or "Hegis Code" - i.e. 05.0206.
  • In the Course/Program page, we will display the "code + description" for users to make it more readable. This only occurs in the Course/Program page, and any reports of curriculum data will only show the code. 

Notes on Custom Fields

Custom fields can be added to the template by dragging and dropping "custom fields" from the question bank. All custom questions added to the course and program template are assumed to be "Coursedog-only" content, and by default are not integrated unless a specific exception is made in the integration wiring.

Required Learning Outcomes

Users are able to define a required number of learning outcomes in a proposal. This can be accessed by defining “required # of elements” in question settings. The “use error alert” feature has also been added, which presents validation errors as a large flag at the top of the card.

In the below example, because the user has only created one learning outcome, the error is shown alerting the user they need to two learning outcomes. 

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.