PKG_CRS_JOIN Table
DWLMS Schema
Explanation
Tracks
current information on the courses that were assigned to packages on or after
March 22, 2005.
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.
There is one PKG_CRS_JOIN record per
combination of package (PKG_ID) and course version (CO_REC_ID). In this
table, a package may include one or more courses (and/or one or more versions
of a
given course);
a course (or course version) may belong to one or more packages.
Common Uses
- Listing the courses or course versions that are included in the
specified packages.
- Listing the packages that include that the
specified courses or course versions.
| Primary Key |
Indexed Data Elements |
Related Tables |
PKG_ID
CO_REC_ID
|
CO_REC_ID
PKG_ID
|
COURSE_ITERATION
COURSE_MASTER
COURSE_OBJECT
KNODE_CRS_JOIN
LMS_COURSE_MASTER
LMS_STAFF_QUAL
LMS_TRAINEE_BU_COURSE_ASSIGN
PKG
PROFILER_ASSIGNMENTS
UPHS_USER_ENTITY
USER_COURSES |
Cautions
- The PKG_CRS_JOIN table stores only the current information for a package/course
version combination. Historical information is not available. For example,
if the record for package P and course version C originally
specified a PERIODICITY of 12, but the record was updated to set PERIODICITY
to 0, there is no way to
tell
from
the
PKG_CRS_JOIN
table
that
package P and course version C ever had a PERIODICITY of 12.
- The PKG table has information on the packages mentioned
in the PKG_CRS_JOIN table, where PKG_CRS_JOIN.PKG_ID = PKG.PKG_ID. (Business
Objects users will see that these tables are joined for them in the Learning
Management and Profiler Universe.)
- A package
usually (but not always) includes at least one course. There are some
records
in PKG
for
packages
with no
courses.
- A package can be used to assign a set of courses
to a business unit only if the package 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.) An active package
has PKG.STATUS=1; an inactive package has PKG.STATUS=0
(zero).
- 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). The COURSE_OBJECT
table has information on the course versions mentioned in the PKG_CRS_JOIN
table, where PKG_CRS_JOIN.CO_REC_ID = COURSE_OBJECT.CO_REC_ID. (Business
Objects users will see that these tables are joined for them in the Learning
Management
and
Profiler Universe.)
- A package can be used to assign a course version to a business unit
only if the course version is active. An active course
version has COURSE_OBJECT.STATUS=1; an inactive course version
has COURSE_OBJECT.STATUS=0 (zero).
- A package may be used to assign a course to a business unit
only if the course is active. A course version ought not to be active if
the course is inactive, but there may be inactive courses that have active
course versions. You
may use the COURSE_MASTER table or the LMS_COURSE_MASTER table to get
information on the courses mentioned in the PKG_CRS_JOIN table--for example,
where PKG_CRS_JOIN.CO_MAS_ID = COURSE_MASTER.CO_MAS_ID. An active
course
has COURSE_MASTER.STATUS=1 (LMS_COURSE_MASTER.COURSE_STATUS='A');
an inactive course has COURSE_MASTER.STATUS=0 (zero) (LMS_COURSE_MASTER.COURSE_STATUS='I').
- 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 package may include one or more courses (and/or one or more versions
of a given course); a course (or course version) may belong to one or
more packages.
- The PKG table includes some data elements that currently are not used.
Those data elements are:
- MANDATORY
- SEQUENCE_NUMBER
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 trainees 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.
Questions about this page? Email us at da-staff@isc.upenn.edu
|
