Penn Computing

University of Pennsylvania
Penn Computing << go backback
COURSE_ITERATION Table - Data Element Index    Tables and Data Elements   Learning Management Home   Data Warehouse Home

COURSE_ITERATION Table

DWLMS Schema

Explanation
Tracks current information on course iterations. You can identify a course iteration by its ITERATION_ID. The COURSE_ITERATION table has one record per course iteration. A record indicates the course iteration's status and the course version whose content is provided by the course iteration; provides descriptive information on the course iteration; and includes information related to scheduling, registration, and trainee scoring.

A course is a formal educational unit that deals with a particular subject. A course provides training to members of the Penn Community in support of their academic activities and job responsibilities at the University and/or at the University of Pennsylvania Health System. A course may have more than one version. For example, if the course covers Software Package X, version 1 of the course might cover Software Package X release 2.0, and version 2 of the course might cover Software Package X release 3.5. A course iteration is an offering of a particular version of the course. A course version may have more than one course iteration. For example, version 2 of the instructor-led course on Software Package X will have two course iterations if it is offered in two different places on the same date and at the same time. Web-based courses commonly have one iteration per version.

Common Uses

  • Displaying the title (NAME) of the course iteration, rather than the numeric ID number that appears in a related table.
  • Providing the descriptions for selected course iterations.
  • Retrieving information on the course iterations for a given course version.
  • Selecting course iterations to be included in a report based on their status, or on whether they are the latest iterations of their courses.
  • Reporting on when a course iteration starts and ends, and on what days of the week the class is held.
  • Finding out the location where a course iteration is held, or the Web address for a Web-based course iteration.
  • Checking administrative information related to the registration process for a course iteration: whether it has a wait list; whether its wait list is active; the minimum, maximum, and current number of trainees enrolled in the course iteration; the last dates when a trainee can enroll in it or drop it; and the lead time for e-mailing reminders to trainees.
  • Listing the passing score for a course iteration's course assessment.
Primary Key Indexed Data Elements Related Tables
ITERATION_ID
CO_REC_ID
ITERATION_ID
KNODE_ID
COURSE_OBJECT

KNODE_CRS_JOIN

LMS_COURSE_ITER_INSTRUCTOR
LMS_COURSE_MASTER
LMS_CURRENT_CRS_ITER_REG_INSTR
LMS_CURRENT_TRAINEE_CRS_STATUS
LMS_DEFINITION
LMS_LOCATION
LMS_REGISTRATION
LMS_STAFF_ASSIGN
LMS_STAFF_QUAL
LMS_TRAINEE_BU_COURSE_ASSIGN
PKG_CRS_JOIN
REGISTRATION
UPHS_CI_PATHLORE
UPHS_COST_CENTER
UPHS_RAW_DATA
UPHS_USER_ENTITY
USER_COURSES


Cautions

  • The COURSE_ITERATION table stores only the current information for a course iteration. Historical information for a course iteration is not available. For example, if a course iteration originally had a PASSING_SCORE of 80, but had its PASSING_SCORE changed to 100, there is no way to tell from the COURSE_ITERATION table that the course iteration ever had a PASSING_SCORE of 80.
  • There are a few data elements that provide information about the course iteration's identity:
    • The ITERATION_ID is a number (such as 10103) used to uniquely identify the course iteration within the Knowledge Link system.
    • The NAME is the title of the course iteration. One example is 'Web Design Using Dreamweaver'. (The value is stored without the quotes.)
      • Note: It is common for more than one course iteration to have the same value for NAME.
      • The NAME may be stored in upper case, lower case, or mixed case. Some iterations have no title--their value for NAME is null.
      • The NAME of a course iteration might or might not be the same as the title of the course version that is offered in the course iteration.
    • The DESCRIPTION often stores a few sentences about the content of the course iteration and the target audience.
      • Note: It is common for more than one course iteration to have the same value for DESCRIPTION.
      • For some course iterations, the NAME is the same as the DESCRIPTION.
      • The DESCRIPTION may be stored in upper case, lower case, or mixed case. Some iterations have no description--their value for DESCRIPTION is null.
      • The DESCRIPTION of a course iteration might or might not be the same as the description of the course version that is offered in the course iteration.
    • Some course iterations have a non-null value for ITERATION_XREF, which is used within the Knowledge Link Gradebook facility as the unique identifier for the course iteration.
  • A course version (CO_REC_ID) may have more than one course iteration (ITERATION_ID). For Web-based training, IS_LATEST_ITER indicates whether the course iteration is the course version’s most recently created iteration. Knowledge Link uses IS_LATEST_ITER to determine how course iterations are displayed for Web-based courses. Note: IS_LATEST_ITERATION is irrelevant for iterations of instructor led training, even when its value is not null.
  • Instead of text, STATUS stores a number that indicates the course iteration's status.
    • To display the description of the status (rather than its numeric code), use the LMS_DEFINITION.NAME where COURSE_ITERATION.STATUS = LMS_DEFINITION.DEF_ID.
    • A trainee can register for the course iteration only if its status is active (STATUS=50).
  • The LOCATION_ID is a numeric code that identifies the place where the course iteration's class meetings (if any) will be held. (Web-based courses, for example, have no class meetings--their value for LOCATION_ID is null.) Information on the location is available in the LMS_LOCATION table where COURSE_ITERATION.LOCATION_ID = LMS_LOCATION.LOCATION_ID
  • MAX_STUDENT stores the maximum number of trainees that can enroll in the course iteration. If the course iteration involves class meetings held at a specified location, the default value for MAX_STUDENT reflects the location's seating capacity at the time the course iteration record was created. However, MAX_STUDENT can have any value, even one that is greater than the location's seating capacity.
  • ALLOW_WAIT_LIST and WL_ACTIVE are used to manage the wait list for an instructor led course iteration's wait list. These data elements are irrelevant for Web-based training, even when their values are not null.
    • ALLOW_WAIT_LIST is a number indicating whether the course iteration can (1) or cannot (0) have a wait list once the maximum number of enrolled trainees has been reached.
    • WL_ACTIVE is a number indicating whether the course iteration's maximum number of enrolled trainees has (1) or has not (0) been reached.
    • When ALLOW_WAIT_LIST and WL_ACTIVE are both set to 1, trainees attempting to register for the course iteration are asked whether they want to be added to the wait list. When an enrolled trainee drops out of the course iteration, the first trainee on the wait list becomes enrolled.
    • Note: a Knowledge Link Administrator or Junior Administrator can use the forced enrollment feature to register a trainee for a course iteration regardless of how ALLOW_WAIT_LIST and WL_ACTIVE are set.
  • Instead of text, DAYS_OF_WEEK stores a number that indicates what day(s) of the week are the class meeting dates for the course iteration.
    • DAYS_OF_WEEK cannot be decoded using the LMS_DEFINITION table.
    • Each day of the week has a unique value for DAYS_OF_WEEK: Sunday (64), Monday (32), Tuesday (16), Wednesday (8), 4 Thursday (4), Friday (2), and Saturday (1).
    • If a course iteration will have class meetings on more than one day of the week, DAYS_OF_WEEK is equal to the sum of the values for those days. DAYS_OF_WEEK may be null or 0 if the course iteration will meet every day from the START_DATE through the END_DATE, or if the course iteration is Web-based and may be taken on any day from the START_DATE through the END_DATE. For example, if a course iteration has a START_DATE of May 5, 2008 (a Monday), an END_DATE of May 9, 2008 (a Friday), and DAYS_OF_WEEK set to 42 (32 + 8 + 2), the class schedule detail for the course iteration will show that the meeting dates are May 5, 7, and 9, 2008 (Monday, Wednesday, and Friday).
  • A course version and its iterations all have the same distribution mode. For example, they are all instructor led, or are all Web-based.
    • For a course iteration's distribution mode, see COURSE_OBJECT.DIST_MODE where COURSE_ITERATION.CO_REC_ID = COURSE_OBJECT.CO_REC_ID.
    • The COURSE_ITERATION table includes several data elements that are pertinent to one distribution mode, but not to other distribution modes, even when those data elements are not null.
      • The following data elements are pertinent only to instructor led training:
        • ALLOW_WAIT_LIST
        • ENROLL_URL
        • LAST_DROP_DATE
        • LAST_ENROLL_DATE
        • REMINDER_DAYS
        • WL_ACTIVE
      • URL is pertinent only to Web-based training.
  • Knowledge Link can store data regarding the costs associated with a course iteration. Most training providers do not use Knowledge Link to track their training costs, but that data is available for some course iterations, in the following data elements:
    • EXP_COMMENT
    • INSTR_EXP
    • OTHER_EXP
    • RES_EXP
  • The COURSE_ITERATION table includes several data elements that currently are not used. Those data elements are:
    • CERT_ISSUED
    • DIST_MODE (Note: This is not used, even when its value is not null. DIST_MODE refers to the way the course content is delivered to the trainees (for example, in a Web-based or instructor led format). For information on the course iteration's distribution mode, see COURSE_OBJECT.DIST_MODE where COURSE_ITERATION.CO_REC_ID = COURSE_OBJECT.CO_REC_ID.)
    • ENROLLMENT_CAT
    • FAC_EXP
    • KNODE_ID (Note: This is not used, even when its value is not null. See COURSE_OBJECT.KNODE_ID where COURSE_ITERATION.CO_REC_ID = COURSE_OBJECT.CO_REC_ID.)
    • LANG_NAME
    • PERFORMANCE_TEST
    • SKILLSOFT_ID
    • TERM_DEF_ID
    • THRESHOLD_SCORE (Note: This is not used, even when its value is not null or 0.)
    • XACCESS (Note: This is not used, even when its value is not null. See COURSE_OBJECT.XACCESS where COURSE_ITERATION.CO_REC_ID = COURSE_OBJECT.CO_REC_ID.)
  • It might appear that the list of related tables shown above incorrectly excludes the KNODE, KNODE_USER_JOIN, and LMS_BUSINESS_UNIT_GROUP tables. Although COURSE_ITERATION can be joined to these tables based on KNODE_ID, such joins are not recommended, because COURSE_ITERATION.KNODE_ID is not used, even when it is not null.

Source

Knowledge Link, the learning management system used by the University and by the University of Pennsylvania Health System (UPHS) since March, 2005.

Knowledge Link enables authorized administrators to schedule training courses, assign resources to courses, assign groups of Knowledge Link users to courses, and to create online courses. It enables trainees to find out what courses have been assigned to them, to register for those courses (whether those courses are on-line or instructor-led), to take on-line courses, and to provide feedback via course evaluations. Knowledge Link was first used to track information on training required by regulation, but it now tracks information on a variety of training courses.

COURSE_ITERATION Table - Data Element Index    Tables and Data Elements   Learning Management Home   Data Warehouse Home

Questions about this page? Email us at da-staff@isc.upenn.edu

Information Systems and Computing
University of Pennsylvania
Information Systems and Computing, University of Pennsylvania