Penn Computing

University of Pennsylvania
Penn Computing << go backback
PKG_CRS_JOIN Table   Tables and Data Elements   Learning Management Home   Data Warehouse Home

PKG_CRS_JOIN - Data Element Index

Select a data element to view its definition and its indexed, format, and null values.

 

Data element Definition
CO_MAS_ID

Indexed - no
Format - number (10)
May be null? yes

A number used within the Knowledge Link system as the unique identifier for the course that is included in the package (PKG_ID). 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. See also CO_REC_ID.

A course may be assigned to a business unit only if the status of the course is active. (A business unit--also known as a BU, role, Knowledge Node, or K Node--is a set of one or more Knowledge Link users.) Information on the course and its status is available in the COURSE_MASTER and LMS_COURSE_MASTER tables.

A course version ought not to be active if the course is inactive, but there may be inactive courses that have active course versions. A course may be assigned to a business unit only if it has an active course version. See CO_REC_ID.

Example: 13222

Values:
Refer to the LMS_COURSE_MASTER table or the COURSE_MASTER table for values.
CO_REC_ID

Indexed - yes
Format - number (10)
May be null? no

A number used within the Knowledge Link system as the unique identifier for the version of the course that is included in the package (PKG_ID). See also CO_MAS_ID.

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. The course versions may have overlapping active periods. Note that, once the latest version is created, Knowledge Link users ought to be able to register as trainees for the latest version only (though trainees who registered for the earlier version remain registered for that version). Information on the course version is available in the COURSE_OBJECT table.

Once a course is included in a package, when the course owner creates a new version of the course, a new PKG_CRS_JOIN record is automatically created, to include the new course version in the package. When a new course version is created, the course owner ought to make the former course version inactive, so that, when the package is assigned to a business unit, the former course version is not assigned to the business unit. However, there are some packages that include more than one active version of a given course.

A course version may be assigned to a business unit only if the status of the course version is active. (A business unit--also known as a BU, role, Knowledge Node, or K Node--is a set of one or more Knowledge Link users.) Information on the course version and its status is available in the COURSE_OBJECT table.

A course version ought not to be active if the course is inactive, but there may be inactive courses that have active course versions. See CO_MAS_ID.

Example: 13719

Values:
Refer to the COURSE_OBJECT table for values.
DATE_CREATED

Indexed - no
Format - date
May be null? yes

The date when the PKG_CRS_JOIN record was created in Knowledge Link.

Example: 10/24/2006

Values:
List of values not available
DATE_MODIFIED

Indexed - no
Format - date
May be null? yes

The date when the PKG_CRS_JOIN record was last updated in Knowledge Link.

Example: 11/13/2007

Values:
List of values not available
MANDATORY

Indexed - no
Format - number (10)
May be null? yes

This data element currently is not used.

PERIODICITY

Indexed - no
Format - number (2)
May be null? yes

The default value for the periodicity to be specified for the courses in this package when the package is used to assign those courses to a business unit. This default value may be changed when the assignment is made. (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 business unit--also known as a BU, role, Knowledge Node, or K Node--is a set of one or more Knowledge Link users.) See also PERIODICITY in the COURSE_OBJECT, KNODE_CRS_JOIN, LMS_TRAINEE_BU_COURSE_ASSIGN, and LMS_TRAINEE_COURSE_ASSIGN tables.

The value of PERIODICITY is an integer (with no decimal places), and indicates the number of months in the period from the time when a trainee completes a course to the time when the trainee is due to complete it again. PERIODICITY is a factor when the course is named in a mandatory course assignment; it is irrelevant for optional course assignments.

When PERIODICITY is null or 0, and the course is assigned as a mandatory course, the trainees are required to complete it only once.

Example: 12

Values:
List of values not available.
PKG_ID

Indexed - yes
Format - number (10)
May be null? no

A numeric value used to uniquely identify the PKG record within the Knowledge Link system.

A package is a set of courses that may be taken in any order, and that can be assigned to a business unit using one assignment specification. (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 business unit--also known as a BU, role, Knowledge Node, or K Node--is a set of one or more Knowledge Link users.) For example, say that trainees are usually required to take both course A and course B. Package P includes courses A and B. If business unit X is required to take both courses, it is more convenient to specify that P is assigned to X than to specify each course separately.

A package usually (but not always) includes at least one course. A given course may belong to more than one package.

Example: 10324

Values:
Refer to the PKG table for values.
SEQUENCE_NUMBER

Indexed - no
Format - number (3)
May be null? yes

This data element currently is not used.

 

PKG_CRS_JOIN Table   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