Topic Field Terminology
and Definitions |
Topic Title Short |
This is a required field. It is limited to 30
characters, including spaces. |
Topic Title Long |
This is a required field. It is limited to 50
characters, including spaces. |
Instructor Name |
10 character limit, Twin Cities only. Use this
field to enter the name of the topic's instructor. |
Short Description |
10 character limit. Crookston, Duluth, and Morris
only. Use to enter a brief description of the topic. |
Max - Min Credits for Course |
The maximum and minimum credit values for the
course. These values cannot be changed on this page, but can be changed
for the course associated with this topic or in the Electronic Course
Scheduling (ECS) system. |
Course Grading Basis |
The grading basis for the course. This value
cannot be changed on this page, but can be changed by updating the
course. To choose a different grading basis for the topic, use the "Topic
Grading Basis" field. |
Topic Grading Basis |
Select a value for this field only if you want
the value to be different from the course's grading basis. |
Course Prerequisites for Catalog |
The values that appear here are read-only and
were entered at the course level. To update these fields, create
a course proposal. To create prerequisites for the topic only, use
the "Topic Prerequistes for Catalog" field below. |
Topic Prerequisites for Class Schedule |
Any topic prerequisites that are different from
the course prerequisites and that should appear in
the class schedule should be entered here. Prerequisites can include
consent, class standing, or completion of specific courses. Any prerequisites
that are advisory to the student can be entered here, as well as
any information about additional topic requirements. If you want
to enforce any of these prerequisites, you must enter values in the "Topic
Consent Requirement" and/or "Topic Enforced Prerequisites" field(s). |
Course Consent Requirement |
The values that appear here are read-only and
were entered at the course level. To update the value in this field,
create a course proposal. To create a consent requirement for the
topic only, use the "Topic Consent Requirement" field
below. |
Topic Consent Requirement |
Any topic consent requirements that are different
from the Course Consent Requirements should be entered here. The
default value is "no required consent." If you wish to
enforce consent at any other level, select the radio button of the
level at which you will actually control entry to the course (i.e.,
through magic numbers). |
Course Enforced Prerequisites |
The values that appear here are read-only and
were entered at the course level. To update the value in this field,
create a course proposal. To create an Enforced Prerequisite for
the topic only, use the "Topic Enforced Prerequisite" field
below. |
Override Course Enforced Prerequisites |
Check this field if you want the Topic Enforced
Prerequisites to replace the Course Enforced Prerequisites. Do not
check this field if you want the Topic Enforced Prerequisites to
be an addition to the Course Enforced Prerequisites. |
Topic Enforced Prerequisites |
Any topic enforced prerequisites that are different
from the Course Enforced Prerequisite should be entered here. The
default value is "no required consent." You may enforce
restricted access to a topic based on prerequisite courses, student
standing, or both (e.g., "ARCH 3411, junior Arch major").
If any prerequisite is entered into this field, PeopleSoft will ALWAYS
restrict access to the class for those students who do not meet the
requirements of the prerequisite, regardless of other student status
information. You may choose from predefined sets (i.e., other prerequisites
that have been entered for the same designator) or if a prerequisite
group does not exist in the list below to fit this topic, you may
create a new prerequisite group. New groups are reviewed by OTR prior
to implementation. |
Editor Comments |
Optional field to be used by topic entry staff
to communicate about the topic internally. Submitters/approvers of
courses can use this field as a way of passing on information to
whomever might be looking at the proposal as it goes through approval. |
Proposal Changes |
Optional field to be used by the department/college
to indicate changes being made to the topic for other staff or departments.
This field is especially useful in noting for reviewers anything
that has changed in an updated topic. |
Student Learning Outcomes |
This is a required field. Choose 1-7 learning outcomes that will be
addressed by the topic. See SLO information at:
http://www.slo.umn.edu |
How This Outcome Will be Addressed |
This field must be completed for each outcome chosen. See the SLO website at
http://www.slo.umn.edu/resources/ecas_examples.html for more information and examples. |
How This Outcome Will be Assessed |
This field must be completed for each outcome chosen. See the SLO website at
http://www.slo.umn.edu/resources/ecas_examples.html for more information and examples. |