Penn Computing

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

COURSE_OBJECT - Data Element Index

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

 

Data element Definition
ASSIGNMENT

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

A one digit number indicating whether E-mail Notifications are sent to trainees when a course assignment is created that indicates that this course version is currently required for them. (The course version is currently required for the trainee if: (1) it is named in an active mandatory course assignment made to a business unit that currently includes the trainee, and (2) the trainee is not grandfathered for the course.) When a course version is created, if the value for ASSIGNMENT is not otherwise specified, it is set by default to the assignment e-mail parameter for the course (COURSE_MASTER.ASSIGNMENT for the CO_MAS_ID).

See also NOTIFICATION, STATUS_SD, STATUS_PD, SD_BOUNDARY, SD_RECURR, and PD_RECURR.

The E-mail Notifications parameters in the COURSE_OBJECT table are not the ones that control whether Knowledge Link sends E-mail Notifications about a currently required course to a particular trainee. When a course version is created, its E-mail Notifications parameters are stored in the COURSE_OBJECT table, with their values defaulting to the values for the course. (See the COURSE_MASTER and LMS_COURSE_MASTER tables. The COURSE_MASTER and COURSE_OBJECT tables store the codes for the parameters; the LMS_COURSE_MASTER table stores the decoded values.) When a mandatory course is assigned to a business unit, the E-mail Notifications parameters for the mandatory course assignment are stored in the LMS_GOVERNING table, with their values defaulting to the values for the course version. Whether Knowledge Link sends E-mail Notifications about a course to a particular trainee depends not only on the parameters for the mandatory course assignment, but also on the trainee's GRANDFATHERED status for the course, the date when the trainee is next due to complete the course (DUE_DATE), and the status of that date relative to today's date (STATUS_DUEDATE_DESCRIPTION). The LMS_TRAINEE_BU_COURSE_ASSIGN table stores these three data elements for the trainees and their mandatory course assignments. The LMS_TRAINEE_COURSE_COMPLIANCE table stores these three data elements for trainees and their currently required courses (that is, mandatory courses for which the trainees are not grandfathered).

Values:
1 (assignment E-mail Notifications 
   are turned on for this course version)
0 (assignment E-mail Notifications 
   are not turned on for this course version)
AUTHOR

Indexed - no
Format - varchar2 (40)
May be null? yes

Text that names the creator or author of the course version’s content. The value of AUTHOR may be null.

Examples: 'bill kasenchar', 'GINA BARRETT', 'Samantha Davis-Del Lior', 'Mary Jo Shepherd - Janet Smith' The value is stored without the surrounding quotes.

Values:
List of values not available
BLENDED

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

This data element currently is not used.

CERT_STYLE

Indexed - no
Format - varchar2 (32)
May be null? yes

A character string that specifies the certificate style associated with a course version.
If it is not null, the value of CERT_STYLE corresponds to a certificate directory of the same name that is available in the Knowledge Link system. That directory contains the scripts and elements that create the certificate page that is displayed in the trainee’s “training record” in the Knowledge Link Navigator. The same CERT_STYLE value can be used for multiple courses.

Examples: 'CertStyle3', 'CertStyle65' The value is stored without the surrounding quotes.

Values:
List of values not available.

CO_BASE_URL

Indexed - no
Format - varchar2 (300)
May be null? yes

If the course version is an on-line training module (also known as a Web-based course), CO_BASE_URL stores the URL for the Web page that launches the training module. (A URL is a Uniform or Universal Resource Locator, the Internet address for a file or Web page.) CO_BASE_URL is null if the course version is not an on-line training module.

CO_BASE_URL is automatically populated from the course manifest if the course is loaded into Knowledge Link via a SCORM package. (This course load process both creates the COURSE_OBJECT record and loads the course content.) CO_BASE_URL can be entered by the administrator for other Web-based course content that may be hosted on a system other than Knowledge Link (at the University, the University of Pennsylvania Health System, or a third-party vendor’s site).

Example: 'http://knowledgelink.upenn.edu/content/univ_isc_fast_1-1_bkg_v1/imsmanifest.xml' The value is stored without the surrounding quotes.

Values:
List of values not available

CO_ID

Indexed - yes
Format - varchar2 (200)
May be null? no

A string that uniquely identifies the course version to Knowledge Link users. The COURSE_OBJECT table has one record per course version. See also CO_REC_ID, CO_TITLE, and DESCRIPTION.

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 CO_MAS_ID. Information on courses is available in the COURSE_MASTER and LMS_COURSE_MASTER tables.)

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 CO_ID is usually the Course Master ID, followed by an underscore, a lower case 'v', and the version number (CRS_VERSION). See COURSE_MASTER_ID in the LMS_COURSE_MASTER table.

The CO_ID may include letters and/or numerals and/or other characters. The letters in CO_ID may be in upper case, lower case, or mixed case. Most CO_ID values consist of four segments, in the following format:

  1. the enterprise that developed the course, followed by an underscore. Examples: UNIV (the University); UPHS (the University of Pennsylvania Health System); SOM (the School of Medicine)
  2. the intended audience for the course at the entity, school or center level, followed by an underscore. Examples: MED (Medicine); CPP (Clinical Practices); ALL (all entities)
  3. the intended audience for the course at the level of the division within the enterprise, followed by an underscore. Examples: EHRS (Environmental Health and Radiation Safety); NURS (Nursing); ALL (all schools or divisions)
  4. the course identifier code (determined by the course developer), followed by an underscore
  5. the version number. Examples: v2, v10

Example: 'UNIV_ALL_EHRS_BPYIP_v1' The value is stored without the surrounding quotes.

Values:
Refer to the COURSE_OBJECT table for values.
CO_MAS_ID

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

A number that uniquely identifies the course within the Knowledge Link system. 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. (Information on courses is available in the COURSE_MASTER and LMS_COURSE_MASTER tables.)

Example: 11883 (UNIV_ALL_EHRS_BPYIP)

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 course version. The COURSE_OBJECT table has one record per course version. See also CO_ID, CO_TITLE, and DESCRIPTION.

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 CO_MAS_ID. Information on courses is available in the COURSE_MASTER and LMS_COURSE_MASTER tables.)

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.

Example: 12055 (Bloodborne Pathogens for Childcare Center Employees - EHRS [UNIV_ALL_EHRS_BPYIP_v1])

Values:
Refer to the COURSE_OBJECT table for values.
CO_TITLE

Indexed - no
Format - varchar2 (256)
May be null? no

The title of the course version. It is common for more than one course version to have the same value for CO_TITLE. See also CO_REC_ID, CO_ID, and DESCRIPTION.

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 CO_MAS_ID. Information on courses is available in the COURSE_MASTER and LMS_COURSE_MASTER tables.)

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 CO_TITLE may be stored in upper case, lower case, or mixed case. Most course version titles consist of three parts, in the following format:

  1. text briefly identifying the course content
  2. a dash ('-') with spaces on either side, to serve as a separator
  3. the enterprise that developed the course. Examples: UNIV (the University); UPHS (the University of Pennsylvania Health System); SOM (the School of Medicine)

Note: It is common for more than one course version to have the same value for CO_TITLE.

Example: 'Bloodborne Pathogens for Childcare Center Employees - EHRS' The value is stored without the surrounding quotes.

Values:
List of values not available
COURSE_TYPE

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

A numeric code that indicates the type of educational experience provided by the course version.

Note: The description for COURSE_TYPE is not available in the LMS_DEFINITION table.

A course version’s COURSE_TYPE is set by the administrator on the Course Details page in the Knowledge Link manager interface. The current list of valid COURSE_TYPE values is shown below. Additional valid values can be created by an administrator through the Manager interface.

Values:
0 (no course type has been specified for the course version)
90026 (Competency)
90046 (In-Service)
CREDITS

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

The number of credits awarded to the trainee for completion of the course. CREDITS is used only for UPHS courses. The value of CREDITS may be null.

CREDITS is populated when the course version is created by an administrator using the Gradebook batch utility provided by Generation21 (the Knowledge Link vendor).

Examples: 0, 9, 20

Values:
List of values not available
CRS_VERSION

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

A sequence number uniquely identifying the version within the course to which it applies. See also CO_ 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. (Information on courses is available in the COURSE_MASTER and LMS_COURSE_MASTER tables.)

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.

In the COURSE_OBJECT table, a course (CO_MAS_ID) has at least one course version (CO_REC_ID), and may have more than one. For a given course, the version with the highest CRS_VERSION number is usually the latest version--the one whose iterations are scheduled in the future, or were scheduled most recently in the past. However, when a course has at least one COURSE_OBJECT record, and another record is created so that Knowledge Link can store data on trainees who completed an earlier version of the course in the past, the historical version of the course has the highest CRS_VERSION number, until another COURSE_OBJECT record is created for another version of the course.

Examples: 0, 2, 10

Values:
List of values not available

DATE_CREATED

Indexed - no
Format - date
May be null? yes

The date when the COURSE_OBJECT record was created in Knowledge Link. If it is not null, the value of DATE_CREATED may or may not include the time. See also DATE_MODIFIED.

Business Objects hint: by default, just the date will appear in your report, but you can change the format of the cell to show just the time, if you so desire. To select records for a particular date (say, 7/21/2008), set your query conditions to DATE_CREATED is greater than or equal to 7/21/2008 and DATE_CREATED is less than 7/22/2008. (The system will supply the time--12:00:00 AM--for both dates.)

Examples: 1/24/2008; 1/31/2008 2:13:01 PM

Values:
List of values not available
DATE_MODIFIED

Indexed - no
Format - date
May be null? yes

The date when the COURSE_OBJECT record was last updated in Knowledge Link. If it is not null, the value of DATE_MODIFIED may or may not include the time. See also DATE_CREATED.

Business Objects hint: by default, just the date will appear in your report, but you can change the format of the cell to show just the time, if you so desire. To select records for a particular date (say, 7/21/2008), set your query conditions to DATE_MODIFIED is greater than or equal to 7/21/2008 and DATE_MODIFIED is less than 7/22/2008. (The system will supply the time--12:00:00 AM--for both dates.)

Examples: 2/14/2008; 2/25/2008 12:30:04 PM

Values:
List of values not available
DESCRIPTION

Indexed - no
Format - varchar2 (4000)
May be null? yes

Text describing the course version. For some course versions, the DESCRIPTION is the same as the CO_TITLE. See also CO_ REC_ID, CO_ ID, and CO_TITLE.

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 CO_MAS_ID. Information on courses is available in the COURSE_MASTER and LMS_COURSE_MASTER tables.)

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 DESCRIPTION may be stored in upper case, lower case, or mixed case. Some course versions have no description--their value for DESCRIPTION is null. Some course versions have a DESCRIPTION that includes no words (for example, '111').

Note: It is common for more than one course version to have the same value for DESCRIPTION.

Example: 'Discussion of the OSHA Bloodborne Pathogens Standard and how it applies in a daycare setting. Covers infection control in the daycare, including work practice controls such as washing hands and disinfecting areas where children play.' The value is stored without the surrounding quotes.

Values:
List of values not available
DIST_MODE

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

A numeric code that denotes the distribution mode for the course version. This indicates how the course content is delivered to the trainees. The value may be set by the administrator (in the case of instructor led training), or by the system (in the case of Web-based training) when the course version is created.

The description for DIST_MODE is LMS_DEFINITION.NAME where COURSE_OBJECT.DIST_MODE = LMS_DEFINITION.DEF_ID.

Values:
0 (no distribution mode has been specified for the course version)
12 (Web Based)
13 (Instructor Led)
449 (Assessment)
3434 (Curriculum)
DURATION

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

The number of hours scheduled for the course. (The actual time spent completing the course may vary.) For example, Penn Medicine uses DURATION to specify contact hours for course versions used for nurse education.

DURATION is populated by entering a numerical value in the CE field on the Course Details page in the Knowledge Link manager interface. If populated, this value is displayed in the trainee’s “training record” in the Knowledge Link Navigator. If no CE value is specified for the course version, DURATION is null.

Examples: 0, 1, 3.5, 6.75, 20.7

Values:
-99,999.99 to 99,999.99
ECOMMERCE

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

This data element currently is not used.

ENROLL_URL

Indexed - no
Format - varchar2 (300)
May be null? yes

A text string containing the URL (if any) for a Web page that is hosted on a system other than Knowledge Link (at the University, the University of Pennsylvania Health System, or a third-party vendor’s site), and that provides information about the course and how to register to take it. (A URL is a Uniform or Universal Resource Locator, the Internet address for a file or Web page.) The value for ENROLL_URL may be null.

Example: 'http://www.med.upenn.edu/ohr' The value is stored without the surrounding quotes.

Values:
List of values not available
FINISH_BY

Indexed - no
Format - date
May be null? yes

This data element currently is not used. It is a property of Knowledge Link Assembler courses that are not available on Penn’s Knowledge Link system at this time.

G21_LOOK_AND_FEEL

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

This data element currently is not used.

GRANDFATHERING_VALUE

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

A numeric code that indicates whether the course version does or does not allow for grandfathering based on the trainee's transfer type. When a course version is created, if the GRANDFATHERING_VALUE is not otherwise specified, it is set by default to the grandfathering value for the course (COURSE_MASTER.GRANDFATHERING_VALUE for the CO_MAS_ID). If GRANDFATHERING_VALUE is null, the result is the same as if it were 0.

Sometimes, when a mandatory course is assigned to a business unit, not all of the trainees included in the business unit are currently required to take the course; some are "grandfathered". One of the things that may qualify trainees to be grandfathered is their transfer type, which indicates how they became included in the business unit--as a new employee, or via some kind of job transfer.

The GRANDFATHERING_VALUE in the COURSE_OBJECT table is not the one that indicates whether a trainee is grandfathered for a particular mandatory course assignment. The trainee's grandfathered status for the mandatory course assignment is available in LMS_TRAINEE_BU_COURSE_ASSIGN.GRANDFATHERED. (For more information on grandfathering, see the Cautions for the COURSE_OBJECT table.)

When the trainee is assigned to a business unit, the trainee's TRANSFER_TYPE is stored in the KNODE_USER_JOIN table. (Note: currently, this information is stored for trainees who are University of Pennsylvania Health System (UPHS) employees, but not for other trainees.) As of this writing, the only transfer types are new employees, intra-department transfers, inter-department transfers, and inter-entity transfers, so the values 0 and 15 have practically the same meaning for GRANDFATHERING_VALUE.

Values:
null (no GRANDFATHERING_VALUE has been specified;
no transfer types are grandfathered)
0 (no transfer types are grandfathered)
1 (new employees are not grandfathered;
others are grandfathered)
2 (intra-department transfers are not grandfathered;
others are grandfathered)
3 (new employees and intra-department transfers are not
grandfathered; others are grandfathered)
4 (inter-department transfers are not grandfathered;
others are grandfathered)
5 (new employees and inter-department transfers are not
grandfathered; others are grandfathered)
6 (intra-department and inter-department transfers are not
grandfathered; others are grandfathered)
7 (new employees, intra-department transfers, and
inter-department transfers are not grandfathered;
others are grandfathered)
8 (inter-entity transfers are not grandfathered;
others are grandfathered)
9 (new employees and inter-entity transfers are not
grandfathered; others are grandfathered)
10 (intra-department and inter-entity transfers are not
grandfathered; others are grandfathered)
11 (new employees, intra-department transfers, and
inter-entity transfers are not grandfathered;
others are grandfathered)
12 (inter-department and inter-entity transfers are not
grandfathered; others are grandfathered)
13 (new employees, inter-department transfers, and
inter-entity transfers are not grandfathered;
others are grandfathered)
14 (intra-department, inter-department, and inter-entity
transfers are not grandfathered; others are
grandfathered)
15 (new employees, intra-department transfers,
inter-department transfers, and inter-entity
transfers are not grandfathered; others are
grandfathered)
ITG_ID

Indexed - no
Format - varchar2 (80)
May be null? yes

This data element currently is not used.

KNODE_ID

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

The number used within the Knowledge Link system as the unique identifier for the business unit that owns the course version (CO_REC_ID). The owner's name and identification code are stored in the KNODE table (in NAME and IDENTIFIER, respectively), where COURSE_OBJECT .KNODE_ID = KNODE.KNODE_ID.

A business unit (also known as a BU, role, Knowledge Node, or K Node) is a set of one or more Knowledge Link users. The business units to which Knowledge Link users are assigned are known as KPs, or Knowledge Positions. (See the KNODE_USER_JOIN table.) Some KPs denote privileged groups, used to classify certain Knowledge Link users according to what they are authorized to do within the Knowledge Link system.

Business units are organized into a hierarchy. In the business unit hierarchy, the parent of a KP can be a Knowledge Community (KC) or a Knowledge Microcommunity (KMC). KCs and KMCs are the types of business units that are course version owners. The KCs that own course versions correspond to University orgs. or to University of Pennsylvania Health System (UPHS) entities (process levels) or departments (cost centers or accounting units). A KMC identifies a group of trainees from unrelated UPHS departments.

The owner of the course version is one of the criteria used to determine what course versions (if any) are included on the list of course versions that a given user can assign. Two of the other criteria are the course version's access level (XACCESS) and the user’s privileges (determined by the privileged KP(s) to which the user is assigned). Course versions can be assigned by Knowledge Link users with administrator, junior administrator, or instructor privileges.

  • If the user has administrator privileges, the user can assign any course version to any business unit, regardless of the course version’s owner and XACCESS.
  • If the user is assigned to a KP for a group whose privileges include the ability to assign course versions, and that KP’s parent is a KMC, the course version’s XACCESS is irrelevant. The list of course versions that the user can assign will include a given course version only if that KMC is the course version’s owner.
  • Otherwise, a given course version is included on the list of those that the user can assign if the user is assigned to a KP denoting a group whose privileges include the ability to assign course versions, the parent of that KP is a KC (not a KMC), and one of the following is true:
    • XACCESS is 167 (Local), and the KC is the same as the course version’s owner.
    • XACCESS is 166 (Inheritable), and the KC is the same as the course version’s owner, or falls above the course version’s owner in the business unit hierarchy.
    • XACCESS is 167 (Global). The course version’s owner is irrelevant if the course version's access level is Global.

Example: 44922 (Environmental Health and Radiation Safety Parent [UP.EHRS])

Values:
List of values not available
LANGUAGE

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

A numeric code that indicates the language in which the course version is offered. The value may be null or 0 if the language has not been specified.

The description for LANGUAGE is LMS_DEFINITION.NAME where COURSE_OBJECT.LANGUAGE = LMS_DEFINITION.DEF_ID.

Example: 29 (US English)

Values:
List of values not available
LAST_EXTRACT_DATE

Indexed - no
Format - date
May be null? yes

The date and time when this record was extracted from Knowledge Link and loaded into the Data Warehouse.

Note: The COURSE_OBJECT table is unlike most other tables in the Data Warehouse in that not all of its records have the same date stored in LAST_EXTRACT_DATE.

  • The Data Warehouse’s COURSE_OBJECT table (the “target”) is a copy of Knowledge Link’s COURSE_OBJECT table (the “source”). When most Data Warehouse tables are refreshed, all of the records in the target are deleted, and then the source records are loaded into the target. However, when the COURSE_OBJECT target is refreshed, it’s compared to the source. Target records that are not in the source are deleted from the target. Source records that are not in the target are added to the target, and have their LAST_EXTRACT_DATE set to the date and time when they were added to the target. If a course version’s source record has data that doesn’t match what is in its target record, the target record is updated, and its LAST_EXTRACT_DATE is changed to the date and time when the target record was updated. If a course version’s source record has data that matches what is in its target record, the target record is left untouched, and its LAST_EXTRACT_DATE remains unchanged.
  • To see when the COURSE_OBJECT table was last refreshed in the Data Warehouse, see the record with the highest value for LAST_EXTRACT_DATE.

Business Objects hints:

  • By default, just the date will appear in your report, but you can change the format of the cell to show just the time, if you so desire.
  • To select records that were added or updated on a particular date (say, 7/21/2008), set your query conditions to LAST_EXTRACT_DATE is greater than or equal to 7/21/2008 and LAST_EXTRACT_DATE is less than 7/22/2008. (The system will supply the time--12:00:00 AM--for both dates.)

Example: 8/29/2009 3:09:00 AM

Values:
List of values not available
LAUNCH_TYPE

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

A numeric code that indicates how a Web-based course is launched from Knowledge Link. The value is set automatically by the Knowledge Link system depending on the characteristics of the course or curriculum, and is used internally to control the delivery of content to the end user through the Navigator interface.

The description for LAUNCH_TYPE is LMS_DEFINITION.NAME where COURSE_OBJECT.LAUNCH_TYPE = LMS_DEFINITION.DEF_ID.

Examples: 372 (GEN21); 388 (SCORM 1.2); 3435 (Simple Curriculum)

Values:
List of values not available
MAX_PASSES

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

This data element currently is not used.

MGR_APPROVAL

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

This data element currently is not used.

NOTIFICATION

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

A one digit number indicating whether the E-mail Notifications feature is turned on for this course version. Knowledge Link's E-mail Notifications feature is designed to keep trainees informed regarding their outstanding currently required courses. (A course is currently required for a trainee if: (1) it is actively assigned as a mandatory course to a business unit that includes the trainee, and (2) the trainee is not grandfathered for the course.) If NOTIFICATION is 1, notifications can be triggered upon the mandatory assignment of the course, and/or when it becomes soon due or past due.

See also ASSIGNMENT, STATUS_SD, STATUS_PD, SD_BOUNDARY, SD_RECURR, and PD_RECURR.

When a course version is created, its default E-mail Notifications parameters are stored in the COURSE_OBJECT table, with their values defaulting to the values for the course. (See the COURSE_MASTER and LMS_COURSE_MASTER tables. The COURSE_MASTER and COURSE_OBJECT tables store the codes for the parameters; the LMS_COURSE_MASTER table stores the decoded values.) When a mandatory course is assigned to a business unit, the E-mail Notifications parameters for the mandatory course assignment are stored in the LMS_GOVERNING table, with their values defaulting to the values for the course version.

Whether Knowledge Link sends E-mail Notifications about a course to a particular trainee depends not only on the parameters for the mandatory course assignment, but also on the trainee's GRANDFATHERED status for the course, the date when the trainee is next due to complete the course (DUE_DATE), and the status of that date relative to today's date (STATUS_DUEDATE_DESCRIPTION). The LMS_TRAINEE_BU_COURSE_ASSIGN table stores these three data elements for the trainees and their mandatory course assignments. The LMS_TRAINEE_COURSE_COMPLIANCE table stores these three data elements for trainees and their currently required courses (that is, mandatory courses for which the trainees are not grandfathered).

Values:
1 (E-mail Notifications are turned on for this course version)
0 (E-mail Notifications are not turned on for this course version)
OBJECTIVES

Indexed - no
Format - varchar2 (4000)
May be null? yes

Text describing the aims of the course version. See also CO_ REC_ID, CO_ ID, and CO_TITLE.

OBJECTIVES may be stored in upper case, lower case, or mixed case, and may include punctuation marks or other special characters. Some course versions have no objectives--their value for OBJECTIVES is null.

Note: It is common for more than one course version to have the same value for OBJECTIVES.

Example: 'Falls, Aspiration, Pneumonia, Delirium' The value is stored without the surrounding quotes.

Values:
List of values not available
PASSING_SCORE

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

A number that represents the score the trainee must achieve to pass the course assessment. A passing score may be required in order to receive course credit.

The default value for COURSE_OBJECT.PASSING_SCORE is 80. However, the administrator may enter a different value in the “Passing Score” field on the Course Details page in the Knowledge Link manager interface.

The default value for the passing score for a course iteration is the value of the passing score for its parent course version, but an iteration’s passing score can be set to a different value. For example, for Web-based courses loaded by the TOC-SCORM API, the passing score is set for the embedded “testable SCO” at the course iteration level to the value sent in the SCORM manifest file. This iteration passing score may differ from the COURSE_OBJECT.PASSING_SCORE.

Examples: 0, 80, 100

Values:
List of values not available
PD_RECURR

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

A numeric code that indicates how often E-mail Notifications are sent to trainees when this course version is currently required for them and they are Past Due to complete it. (The course version is currently required for the trainee if: (1) it is named in an active mandatory course assignment made to a business unit that currently includes the trainee, and (2) the trainee is not grandfathered for the course.) When a course version is created, if the value for PD_RECURR is not otherwise specified, it is set by default to the soon due e-mail recurrence parameter for the course (COURSE_MASTER.PD_ RECURR for the CO_MAS_ID).

See also NOTIFICATION, ASSIGNMENT, STATUS_SD, STATUS_PD, SD_BOUNDARY, and SD_RECURR.

The E-mail Notifications parameters in the COURSE_OBJECT table are not the ones that control whether Knowledge Link sends E-mail Notifications about a currently required course to a particular trainee. When a course version is created, its E-mail Notifications parameters are stored in the COURSE_OBJECT table, with their values defaulting to the values for the course. (See the COURSE_MASTER and LMS_COURSE_MASTER tables. The COURSE_MASTER and COURSE_OBJECT tables store the codes for the parameters; the LMS_COURSE_MASTER table stores the decoded values.) When a mandatory course is assigned to a business unit, the E-mail Notifications parameters for the mandatory course assignment are stored in the LMS_GOVERNING table, with their values defaulting to the values for the course version. Whether Knowledge Link sends E-mail Notifications about a course to a particular trainee depends not only on the parameters for the mandatory course assignment, but also on the trainee's GRANDFATHERED status for the course, the date when the trainee is next due to complete the course (DUE_DATE), and the status of that date relative to today's date (STATUS_DUEDATE_DESCRIPTION). The LMS_TRAINEE_BU_COURSE_ASSIGN table stores these three data elements for the trainees and their mandatory course assignments. The LMS_TRAINEE_COURSE_COMPLIANCE table stores these three data elements for trainees and their currently required courses (that is, mandatory courses for which the trainees are not grandfathered).

Values:
2010 (Weekly)
2011 (Daily)
2012 (Once)
PERIODICITY

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

The default value for the number of months in the period from the time when a trainee completes the course version to the time when the trainee is due to complete it again. PERIODICITY is a factor when the course version 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.

The value for PERIODICITY is an integer (with no decimal places), and may be entered in the “Frequency (in Months)” field on the Course Details page in the Knowledge Link manager interface.

When a mandatory course is assigned to a business unit, if the assignment’s periodicity is not otherwise specified, is set by default to the PERIODICITY for the course version (CO_REC_ID) named in the assignment (the KNODE_CRS_JOIN record). A mandatory course assignment’s periodicity may also be changed after the assignment has been created.

Examples: 0, 12

Values:
List of values not available
PRICE

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

This data element currently is not used.

RIGHTS_MANAGEMENT

Indexed - no
Format - varchar2 (80)
May be null? yes

Text that names the individual or entity that owns the course content or intellectual property. The value of RIGHTS_MANAGEMENT may be null.

Examples: 'UPHS_NURSHUP', 'ULAR/ORA', 'ULAR?ORA', ‘Vice Provost for Research-Office of Regulatory Affairs' The value is stored without the surrounding quotes.

Values:
List of values not available
SD_BOUNDARY

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

For trainees that are currently required to take this course version, SD_BOUNDARY is the number of days before their Due Date when they become Soon Due to complete this course. (The course version is currently required for the trainee if: (1) it is named in an active mandatory course assignment made to a business unit that currently includes the trainee, and (2) the trainee is not grandfathered for the course.) When a course version is created, if the value for SD_BOUNDARY is not otherwise specified, it is set by default to the soon due e-mail boundary for the course (COURSE_MASTER.SD_BOUNDARY for the CO_MAS_ID).

SD_BOUNDARY is one of a set of parameters used by Knowledge Link's E-mail Notifications feature. See also NOTIFICATION, ASSIGNMENT, STATUS_SD, STATUS_PD, SD_RECURR, and PD_RECURR.

The E-mail Notifications parameters in the COURSE_OBJECT table are not the ones that control whether Knowledge Link sends E-mail Notifications about a currently required course to a particular trainee. When a course version is created, its E-mail Notifications parameters are stored in the COURSE_OBJECT table, with their values defaulting to the values for the course. (See the COURSE_MASTER and LMS_COURSE_MASTER tables. The COURSE_MASTER and COURSE_OBJECT tables store the codes for the parameters; the LMS_COURSE_MASTER table stores the decoded values.) When a mandatory course is assigned to a business unit, the E-mail Notifications parameters for the mandatory course assignment are stored in the LMS_GOVERNING table, with their values defaulting to the values for the course version. Whether Knowledge Link sends E-mail Notifications about a course to a particular trainee depends not only on the parameters for the mandatory course assignment, but also on the trainee's GRANDFATHERED status for the course, the date when the trainee is next due to complete the course (DUE_DATE), and the status of that date relative to today's date (STATUS_DUEDATE_DESCRIPTION). The LMS_TRAINEE_BU_COURSE_ASSIGN table stores these three data elements for the trainees and their mandatory course assignments. The LMS_TRAINEE_COURSE_COMPLIANCE table stores these three data elements for trainees and their currently required courses (that is, mandatory courses for which the trainees are not grandfathered).

Values:
List of values not available
SD_RECURR

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

A numeric code that indicates how often E-mail Notifications are sent to trainees when this course version is currently required for them and they are Soon Due to complete it. (The course version is currently required for the trainee if: (1) it is named in an active mandatory course assignment made to a business unit that currently includes the trainee, and (2) the trainee is not grandfathered for the course.) When a course version is created, if the value for SD_RECURR is not otherwise specified, it is set by default to the soon due e-mail recurrence parameter for the course (COURSE_MASTER.SD_ RECURR for the CO_MAS_ID).

See also NOTIFICATION, ASSIGNMENT, STATUS_SD, STATUS_PD, SD_BOUNDARY, and PD_RECURR.

The E-mail Notifications parameters in the COURSE_OBJECT table are not the ones that control whether Knowledge Link sends E-mail Notifications about a currently required course to a particular trainee. When a course version is created, its E-mail Notifications parameters are stored in the COURSE_OBJECT table, with their values defaulting to the values for the course. (See the COURSE_MASTER and LMS_COURSE_MASTER tables. The COURSE_MASTER and COURSE_OBJECT tables store the codes for the parameters; the LMS_COURSE_MASTER table stores the decoded values.) When a mandatory course is assigned to a business unit, the E-mail Notifications parameters for the mandatory course assignment are stored in the LMS_GOVERNING table, with their values defaulting to the values for the course version. Whether Knowledge Link sends E-mail Notifications about a course to a particular trainee depends not only on the parameters for the mandatory course assignment, but also on the trainee's GRANDFATHERED status for the course, the date when the trainee is next due to complete the course (DUE_DATE), and the status of that date relative to today's date (STATUS_DUEDATE_DESCRIPTION). The LMS_TRAINEE_BU_COURSE_ASSIGN table stores these three data elements for the trainees and their mandatory course assignments. The LMS_TRAINEE_COURSE_COMPLIANCE table stores these three data elements for trainees and their currently required courses (that is, mandatory courses for which the trainees are not grandfathered).

Values:
2010 (Weekly)
2011 (Daily)
2012 (Once)
STATUS

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

A one digit number indicating the status of the course version. A course version must be active when a record is created to:

  • set up an iteration of the course version. (See the COURSE_ITERATION table.) An iteration is an offering of a particular version of the course.
  • name the course as part of a package. (See the PKG_CRS_JOIN table.) 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.
  • assign the course to a business unit. (See the KNODE_CRS_JOIN table.) A business unit (also known as a BU, role, Knowledge Node, or K Node) is a set of one or more Knowledge Link users.
  • have a Knowledge Link user register as a trainee for an iteration of the course version. (See the LMS_REGISTRATION and REGISTRATION tables.)

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 CO_MAS_ID. Information on courses is available in the COURSE_MASTER and LMS_COURSE_MASTER tables.)

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.

Values:
1 (the course version is active)
0 (the course version is inactive)
STATUS_PD

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

A one digit number indicating whether E-mail Notifications are sent to trainees when this course version is currently required for them and they are Past Due to complete it. (The course version is currently required for the trainee if: (1) it is named in an active mandatory course assignment made to a business unit that currently includes the trainee, and (2) the trainee is not grandfathered for the course.) When a course version is created, if the value for STATUS_PD is not otherwise specified, it is set by default to the past due e-mail parameter for the course (COURSE_MASTER.STATUS_PD for the CO_MAS_ID).

See also NOTIFICATION, ASSIGNMENT, STATUS_SD, SD_BOUNDARY, SD_RECURR, and PD_RECURR.

The E-mail Notifications parameters in the COURSE_OBJECT table are not the ones that control whether Knowledge Link sends E-mail Notifications about a mandatory course to a particular trainee. When a course version is created, its E-mail Notifications parameters are stored in the COURSE_OBJECT table, with their values defaulting to the values for the course. (See the COURSE_MASTER and LMS_COURSE_MASTER tables. The COURSE_MASTER and COURSE_OBJECT tables store the codes for the parameters; the LMS_COURSE_MASTER table stores the decoded values.) When a mandatory course is assigned to a business unit, the E-mail Notifications parameters for the mandatory course assignment are stored in the LMS_GOVERNING table, with their values defaulting to the values for the course version. Whether Knowledge Link sends E-mail Notifications about a course to a particular trainee depends not only on the parameters for the mandatory course assignment, but also on the trainee's GRANDFATHERED status for the course, the date when the trainee is next due to complete the course (DUE_DATE), and the status of that date relative to today's date (STATUS_DUEDATE_DESCRIPTION). The LMS_TRAINEE_BU_COURSE_ASSIGN table stores these three data elements for the trainees and their mandatory course assignments. The LMS_TRAINEE_COURSE_COMPLIANCE table stores these three data elements for trainees and their currently required courses (that is, mandatory courses for which the trainees are not grandfathered).

Values:
1 ("Past Due" E-mail Notifications are turned on for this course version)
0 ("Past Due" E-mail Notifications are not turned on for this course
version)
STATUS_SD

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

A one digit number indicating whether E-mail Notifications are sent to trainees when this course version is currently required for them and they are Soon Due to complete it. (The course version is currently required for the trainee if: (1) it is named in an active mandatory course assignment made to a business unit that currently includes the trainee, and (2) the trainee is not grandfathered for the course.) When a course version is created, if the value for STATUS_SD is not otherwise specified, it is set by default to the soon due e-mail parameter for the course (COURSE_MASTER.STATUS_SD for the CO_MAS_ID).

See also NOTIFICATION, ASSIGNMENT, STATUS_PD, SD_BOUNDARY, SD_RECURR, and PD_RECURR.

The E-mail Notifications parameters in the COURSE_OBJECT table are not the ones that control whether Knowledge Link sends E-mail Notifications about a currently required course to a particular trainee. When a course version is created, its E-mail Notifications parameters are stored in the COURSE_OBJECT table, with their values defaulting to the values for the course. (See the COURSE_MASTER and LMS_COURSE_MASTER tables. The COURSE_MASTER and COURSE_OBJECT tables store the codes for the parameters; the LMS_COURSE_MASTER table stores the decoded values.) When a mandatory course is assigned to a business unit, the E-mail Notifications parameters for the mandatory course assignment are stored in the LMS_GOVERNING table, with their values defaulting to the values for the course version. Whether Knowledge Link sends E-mail Notifications about a course to a particular trainee depends not only on the parameters for the mandatory course assignment, but also on the trainee's GRANDFATHERED status for the course, the date when the trainee is next due to complete the course (DUE_DATE), and the status of that date relative to today's date (STATUS_DUEDATE_DESCRIPTION). The LMS_TRAINEE_BU_COURSE_ASSIGN table stores these three data elements for the trainees and their mandatory course assignments. The LMS_TRAINEE_COURSE_COMPLIANCE table stores these three data elements for trainees and their currently required courses (that is, mandatory courses for which the trainees are not grandfathered).

Values:
1 ("Soon Due" E-mail Notifications are turned on for this course)
0 ("Soon Due" E-mail Notifications are not turned on for this course)
SUPPLIER_ID

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

A number used to uniquely identify the group that is responsible for maintaining the course version in Knowledge Link. The value of SUPPLIER_ID may be null. Note: in the Knowledge Link system, the SUPPLIER table stores the name and contact information for the supplier, but that information is not available in the Data Warehouse.

The supplier is responsible for the development of the course version’s content, the delivery of that content, and the upkeep of the administrative records on the course version. Suppliers are defined in the Knowledge Link manager by System Administrators or Junior Administrators that are authorized to create and update course versions.

The supplier is usually (but not always) a group at the University or at UPHS.

In most cases, the SUPPLIER_ID is the same for all versions of a given course, but it can change from one version to another if a different group becomes responsible for maintaining the course version in Knowledge Link.

Example: 10041 (Nursing Education – HUP)

Values:
List of values not available
TARGET_AUDIENCE

Indexed - no
Format - varchar2 (800)
May be null? yes

Text describing the kind of trainees for which the course version is intended. The value of TARGET_AUDIENCE may be null.

TARGET_AUDIENCE information is entered on the Course Details page in the Knowledge Link manager interface by System Administrators or Junior Administrators that are authorized to create and update course versions.

Examples: 'Manager/Supervisors/Coordinators', 'SOM GRANT-FUNDED STAFF' The value is stored without the surrounding quotes.

Values:
List of values not available
THRESHOLD_SCORE

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

This data element currently is not used. It is a property of Knowledge Link Assembler courses that are not available on Penn’s Knowledge Link system at this time.

XACCESS

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

A numeric code that indicates the course version's access level, which is one of the criteria used to determine whether a given Knowledge Link user can assign the course version to a business unit.

A business unit (also known as a BU, role, Knowledge Node, or K Node) is a set of one or more Knowledge Link users. The business units to which Knowledge Link users are assigned are known as KPs, or Knowledge Positions. (See the KNODE_USER_JOIN table.) Some KPs denote privileged groups, used to classify certain Knowledge Link users according to what they are authorized to do within the Knowledge Link system.

Business units are organized into a hierarchy. In the business unit hierarchy, the parent of a KP can be a Knowledge Community (KC) or a Knowledge Microcommunity (KMC). KCs and KMCs are the types of business units that are course version owners. The KCs that own course versions correspond to University orgs. or to University of Pennsylvania Health System (UPHS) entities (process levels) or departments (cost centers or accounting units). A KMC identifies a group of trainees from unrelated UPHS departments.

The course version’s XACCESS, the course version’s owner (KNODE_ID), and the user’s privileges are among the criteria that determine whether the course version is included in the list of course versions that the user can assign. Course versions can be assigned by Knowledge Link users with administrator, junior administrator, or instructor privileges. Note:

  • If the user has administrator privileges, the user can assign any course version to any business unit, regardless of the course version’s owner and XACCESS.
  • If the user is assigned to a KP for a group whose privileges include the ability to assign course versions, and that KP’s parent is a KMC, the course version’s XACCESS is irrelevant. The list of course versions that the user can assign will include a given course version only if that KMC is the course version’s owner.

There are three kinds of XACCESS:

  • Global—the course version is included on the list of those that the user can assign if: (1) the user is assigned to a KP denoting a group whose privileges include the ability to assign course versions, and (2) the parent of that KP is a KC (not a KMC). The course version’s owner is irrelevant if XACCESS is 165 (Global).
  • Inheritable—the course version is included on the list of those that the user can assign if: (1) the user is assigned to a KP denoting a group whose privileges include the ability to assign course versions, (2) the parent of that KP is a KC (not a KMC), and (3) that KC is the same as the course version’s owner, or falls above the course version’s owner in the business unit hierarchy. 166 (Inheritable) is the default value for XACCESS.
  • Local—the course version is included on the list of those that the user can assign if: (1) the user is assigned to a KP denoting a group whose privileges include the ability to assign course versions, (2) the parent of that KP is a KC (not a KMC), and (3) that KC is the same as the course version’s owner.

The description for XACCESS is LMS_DEFINITION.NAME where COURSE_OBJECT.XACCESS = LMS_DEFINITION.DEF_ID.

Values:
165 (Global)
166 (Inheritable)
167 (Local)

 

COURSE_OBJECT 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