• CO_MAS_ID
• COURSE_ASSIGNMENT
• COURSE_MASTER_ID
• COURSE_NOTIFICATION
• COURSE_PD_RECURR
• COURSE_SD_BOUNDARY
• COURSE_SD_RECURR
• COURSE_STATUS
• COURSE_STATUS_PD

• COURSE_STATUS_SD
• GRANDFATHERING_VALUE
• LAST_EXTRACT_DATE
• LATEST_CO_REC_ID
• LATEST_COURSE_DESCRIPTION
• LATEST_COURSE_OWNER_BU_ID
• LATEST_COURSE_OWNER_BU_NAME
• LATEST_COURSE_OWNER_BU_NUMBER
• LATEST_COURSE_TITLE

A number that uniquely identifies the course within the Knowledge Link system. See also COURSE_MASTER_ID, LATEST_CO_REC_ID, and LATEST_COURSE_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.

Example: 11883

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

A Yes/No flag that indicates whether E-mail Notifications are sent to trainees when a course assignment is created that indicates that this course is currently required for them. (The course is currently required for the trainees if: (1) it is actively assigned as a mandatory course to a business unit that currently includes the trainees, and (2) the trainees are not grandfathered for the course.) When a course is created, if the value for COURSE_ASSIGNMENT is not otherwise specified, it is set by default to 'N'.

See also COURSE_NOTIFICATION, COURSE_STATUS_SD, COURSE_STATUS_PD, COURSE_SD_BOUNDARY, COURSE_SD_RECURR, and COURSE_PD_RECURR.

The E-mail Notifications parameters in the LMS_COURSE_MASTER 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. 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:
Y (assignment E-mail Notifications are turned on for this course)
N (the default value; 
   assignment E-mail Notifications are not turned on for this course)

A string that uniquely identifies the course to Knowledge Link users. See also CO_MAS_ID, LATEST_CO_REC_ID, and LATEST_COURSE_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.

The COURSE_MASTER_ID may include letters and/or numerals and/or other characters. The letters in COURSE_MASTER_ID may be in upper case, lower case, or mixed case. Most COURSE_MASTER_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)

Example: UNIV_ALL_EHRS_BPYIP

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

A Yes/No flag that indicates whether E-mail Notifications are turned on for this course. Knowledge Link's E-mail Notifications feature is designed to keep trainees informed regarding their outstanding currently required courses. (The course is currently required for a trainee if: (1) it is actively assigned as a mandatory course to a business unit that currently includes the trainee, and (2) the trainee is not grandfathered for the course.) When a course is created, if the value for COURSE_NOTIFICATION is not otherwise specified, it is set by default to 'Y'.

See also COURSE_ASSIGNMENT, COURSE_STATUS_SD, COURSE_STATUS_PD, COURSE_SD_BOUNDARY, COURSE_SD_RECURR, and COURSE_PD_RECURR.

The E-mail Notifications parameters in the LMS_COURSE_MASTER 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. 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:
Y (the default value; E-mail Notifications are turned on for this course)
N (E-mail Notifications are not turned on for this course)

A string that indicates how often E-mail Notifications are sent to trainees when this course is currently required for them and they are Past Due to complete it. (The course is currently required for the trainees if: (1) it is actively assigned as a mandatory course to a business unit that currently includes the trainees, and (2) the trainees are not grandfathered for the course.) When a course is created, if the value for COURSE_PD_RECURR is not otherwise specified, it is set by default to 'Once'.

See also COURSE_NOTIFICATION, COURSE_ASSIGNMENT, COURSE_STATUS_SD, COURSE_STATUS_PD, COURSE_SD_BOUNDARY, and COURSE_SD_RECURR.

The E-mail Notifications parameters in the LMS_COURSE_MASTER 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. 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:

Once (the default value)
Daily
Weekly

For trainees that are currently required to take this course, COURSE_SD_BOUNDARY is the number of days before their Due Date when they become Soon Due to complete this course. (The course is currently required for the trainees if: (1) it is actively assigned as a mandatory course to a business unit that currently includes the trainees, and (2) the trainees are not grandfathered for the course.) When a course is created, if the value for COURSE_SD_BOUNDARY is not otherwise specified, it is set by default to 30.

COURSE_SD_BOUNDARY is one of a set of parameters used by Knowledge Link's E-mail Notifications feature. See also COURSE_NOTIFICATION, COURSE_ASSIGNMENT, COURSE_STATUS_SD, COURSE_STATUS_PD, COURSE_SD_RECURR, and COURSE_PD_RECURR.

The E-mail Notifications parameters in the LMS_COURSE_MASTER 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. 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.

A string that indicates how often E-mail Notifications are sent to trainees when this course is currently required for them and they are Soon Due to complete it. (The course is currently required for the trainees if: (1) it is actively assigned as a mandatory course to a business unit that currently includes the trainees, and (2) the trainees are not grandfathered for the course.) When a course is created, if the value for COURSE_SD_RECURR is not otherwise specified, it is set by default to 'Once'.

See also COURSE_NOTIFICATION, COURSE_ASSIGNMENT, COURSE_STATUS_SD, COURSE_STATUS_PD, COURSE_SD_BOUNDARY, and COURSE_PD_RECURR.

The E-mail Notifications parameters in the LMS_COURSE_MASTER 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. 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:

Once (the default value)
Daily
Weekly

A letter indicating whether the course is active or inactive. A course must be active when a record is created to:

• establish a version of the course. (See the COURSE_OBJECT table.)
• set up an iteration of the course. (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 the course. (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.

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. Information on course versions is available in the COURSE_OBJECT table.

Values:
A (the course is active)
I (the course is inactive)

A Yes/No flag that indicates whether E-mail Notifications are sent to trainees when this course is currently required for them and they are Past Due to complete it. (The course is currently required for the trainees if: (1) it is actively assigned as a mandatory course to a business unit that currently includes the trainees, and (2) the trainees are not grandfathered for the course.) When a course is created, if the value for COURSE_STATUS_PD is not otherwise specified, it is set by default to 'Y'.

See also COURSE_NOTIFICATION, COURSE_ASSIGNMENT, COURSE_STATUS_SD, COURSE_SD_BOUNDARY, COURSE_SD_RECURR, and COURSE_PD_RECURR.

The E-mail Notifications parameters in the LMS_COURSE_MASTER 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. 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:
Y (the default value; 
  "Past Due" E-mail Notifications are turned on for this course)
N ("Past Due" E-mail Notifications are not turned on for this course)

A Yes/No flag that indicates whether E-mail Notifications are sent to trainees when this course is currently required for them and they are Soon Due to complete it. (The course is currently required for the trainees if: (1) it is actively assigned as a mandatory course to a business unit that currently includes the trainees, and (2) the trainees are not grandfathered for the course.) When a course is created, if the value for COURSE_STATUS_SD is not otherwise specified, it is set by default to 'Y'.

See also COURSE_NOTIFICATION, COURSE_ASSIGNMENT, COURSE_STATUS_PD, COURSE_SD_BOUNDARY, COURSE_SD_RECURR, and COURSE_PD_RECURR.

The E-mail Notifications parameters in the LMS_COURSE_MASTER 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. 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:
Y (the default value; 
  "Soon Due" E-mail Notifications are turned on for this course)
N ("Soon Due" E-mail Notifications are not turned on for this course)

A Yes/No flag that indicates whether the course does or does not allow for grandfathering based on the trainee's transfer type. When a course is created, if the GRANDFATHERING_VALUE is not otherwise specified, its default value is 'N' (no transfer types are grandfathered).

Sometimes, when a mandatory course is assigned to a business unit, not all of the trainees included in the business unit are 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 LMS_COURSE_MASTER 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 LMS_COURSE_MASTER table.)

Values:

Y (at least one transfer type is grandfathered)
N (the default value; no transfer types are grandfathered)
    

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

Example: 3/31/2008

Values:
List of values not available.

A number used within the Knowledge Link system as the unique identifier for the version of this course that has the highest version number. (Note: this is usually, but not always, the course version whose iterations are scheduled in the future, or were scheduled most recently in the past. If no version has been created for this course, the value of LATEST_CO_REC_ID is null.) See also CO_MAS_ID, COURSE_MASTER_ID, and LATEST_COURSE_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.

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.

Information on the latest course version is available in the COURSE_OBJECT table where LMS_COURSE_MASTER.LATEST_CO_REC_ID = COURSE_OBJECT.CO_REC_ID.

Example: 12055

Values:
List of values not available

Text describing the version of this course that has the highest version number. (Note: this is usually, but not always, the course version whose iterations are scheduled in the future, or were scheduled most recently in the past.) Because a description of the course itself is not stored in Knowledge Link, LATEST_COURSE_DESCRIPTION may be considered to be the current description of the course. If no version has been created for this course, the value of LATEST_COURSE_DESCRIPTION is null. See also CO_MAS_ID, COURSE_MASTER_ID, LATEST_CO_REC_ID, and LATEST_COURSE_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.

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.

Information on the latest course version is available in the COURSE_OBJECT table where LMS_COURSE_MASTER.LATEST_CO_REC_ID = COURSE_OBJECT.CO_REC_ID.

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

A string employed by Knowledge Link users to uniquely identify the business unit that owns the version of this course that has the highest version number. (See LATEST_CO_REC_ID. Note: this is usually, but not always, the course version whose iterations are scheduled in the future, or were scheduled most recently in the past.) The course version owner determines which business units can create a KNODE_CRS_JOIN record to assign the course version to a business unit. The course per se has no owner specified in Knowledge Link, but LATEST_COURSE_OWNER_BU_ID may be considered to be the identifier of the current owner of the course. If no version has been created for this course, the value of LATEST_COURSE_OWNER_BU_ID is null. See also LATEST_COURSE_OWNER_BU_NUMBER and LATEST_COURSE_OWNER_BU_NAME.

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. Information on the latest course version is available in the COURSE_OBJECT table where LMS_COURSE_MASTER.LATEST_CO_REC_ID = COURSE_OBJECT.CO_REC_ID.

A course version can be assigned to a business unit by a Knowledge Link user who: (1) has System Administrator, Junior Administrator, or Instructor privileges, (2) is authorized for the business unit that is the owner of the course version (or is authorized for a business unit that is below the course version owner business unit in the hierarchy), and (3) is authorized for the business unit named in the assignment (or is authorized for a business unit that is above the assignment business unit in the hierarchy). A course version can be assigned to the business unit that is the owner of the course version, or to a business unit that is below the course version owner business unit in the hierarchy, but not to any other business units. For more information on course version assignments, 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. Knowledge Communities and Knowledge Microcommunities are the types of business units that are course owners. A Knowledge Community corresponds to a University org. or to a University of Pennsylvania Health System (UPHS) entity (process level) or department (cost center or accounting unit). A Knowledge Microcommunity is a business unit that was created to allow courses to be assigned to Knowledge Link users from unrelated UPHS departments. (For further information on business units, see the documentation for the KNODE table. The business unit hierarchy is described in the documentation for PARENT_ID in the KNODE table.)

Most LATEST_COURSE_OWNER_BU_ID values are determined in the manner described below. Generally speaking, the further down the business unit is in the hierarchy, the more qualifiers its LATEST_COURSE_OWNER_BU_ID has.

University

• org.: UP.org. code
  • example: UP.9937
  • For information on orgs., see the General Ledger data collection's documentation on the ORG_CODES table.

UPHS

• entity and department: HS.entity.department.jobclass.EEO code
  • examples: HS.CRDTL; HS.CRDTL.NeontChiefA.A.10
• Knowledge Microcommunity: HS.microcommunity abbreviation
  • example: HS.PATREG

Values:
List of values not available

A phrase or string that labels the business unit that owns the version of this course that has the highest version number. (See LATEST_CO_REC_ID. Note: this is usually, but not always, the course version whose iterations are scheduled in the future, or were scheduled most recently in the past.) The course version owner determines which business units can create a KNODE_CRS_JOIN record to assign the course version to a business unit. The course per se has no owner specified in Knowledge Link, but LATEST_COURSE_OWNER_BU_NAME may be considered to be the name of the current owner of the course. If no version has been created for this course, the value of LATEST_COURSE_OWNER_BU_NAME is null. See also LATEST_COURSE_OWNER_BU_ID and LATEST_COURSE_OWNER_BU_NUMBER.

The LATEST_COURSE_OWNER_BU_NAME may include letters and/or numerals and/or other characters. The letters in LATEST_COURSE_OWNER_BU_NAME may be in upper case, lower case, or mixed case. It is possible for more than one business unit to have the same name. See also LATEST_COURSE_OWNER_BU_ID and LATEST_COURSE_OWNER_BU_NUMBER.

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. Information on the latest course version is available in the COURSE_OBJECT table where LMS_COURSE_MASTER.LATEST_CO_REC_ID = COURSE_OBJECT.CO_REC_ID.

A course version can be assigned to a business unit by a Knowledge Link user who: (1) has System Administrator, Junior Administrator, or Instructor privileges, (2) is authorized for the business unit that is the owner of the course version (or is authorized for a business unit that is below the course version owner business unit in the hierarchy), and (3) is authorized for the business unit named in the assignment (or is authorized for a business unit that is above the assignment business unit in the hierarchy). A course version can be assigned to the business unit that is the owner of the course version, or to a business unit that is below the course version owner business unit in the hierarchy, but not to any other business units. For more information on course version assignments, 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. Knowledge Communities and Knowledge Microcommunities are the types of business units that are course owners. A Knowledge Community corresponds to a University org. or to a University of Pennsylvania Health System (UPHS) entity (process level) or department (cost center or accounting unit). A Knowledge Microcommunity is a business unit that was created to allow courses to be assigned to Knowledge Link users from unrelated UPHS departments. (For further information on business units, see the documentation for the KNODE table. The business unit hierarchy is described in the documentation for PARENT_ID in the KNODE table.)

Most LATEST_COURSE_OWNER_BU_NAME values are determined in the manner described below.

University

• org.: the name of the org. (see ORG_CODES.DESCRIPTION), truncated at 50 characters
  • example: Journal of Biochemistry and Molecular Biology Educ
  • For information on orgs., see the General Ledger data collection's documentation on the ORG_CODES table.

UPHS

• entity: HS.entity
  • example: HS.CRDTL
• department: the department name
  • example: Administrator: Neonatology* (CRDTL)
• Knowledge Microcommunity: the microcommunity name
  • example: Patient Registration

Values:
List of values not available

The number used within the Knowledge Link system as the unique identifier for the business unit that owns the version of this course that has the highest version number. (See LATEST_CO_REC_ID. Note: this is usually, but not always, the course version whose iterations are scheduled in the future, or were scheduled most recently in the past.) The course version owner determines which business units can create a KNODE_CRS_JOIN record to assign the course version to a business unit. The course per se has no owner specified in Knowledge Link, but LATEST_COURSE_OWNER_BU_NUMBER may be considered to be the ID number of the current owner of the course. If no version has been created for this course, the value of LATEST_COURSE_OWNER_BU_NUMBER is null. See also LATEST_COURSE_OWNER_BU_ID and LATEST_COURSE_OWNER_BU_NAME.

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. Information on the latest course version is available in the COURSE_OBJECT table where LMS_COURSE_MASTER.LATEST_CO_REC_ID = COURSE_OBJECT.CO_REC_ID.

A course version can be assigned to a business unit by a Knowledge Link user who: (1) has System Administrator, Junior Administrator, or Instructor privileges, (2) is authorized for the business unit that is the owner of the course version (or is authorized for a business unit that is below the course version owner business unit in the hierarchy), and (3) is authorized for the business unit named in the assignment (or is authorized for a business unit that is above the assignment business unit in the hierarchy). A course version can be assigned to the business unit that is the owner of the course version, or to a business unit that is below the course version owner business unit in the hierarchy, but not to any other business units. For more information on course version assignments, 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. Knowledge Communities and Knowledge Microcommunities are the types of business units that are course owners. A Knowledge Community corresponds to a University org. or to a University of Pennsylvania Health System (UPHS) entity (process level) or department (cost center or accounting unit). A Knowledge Microcommunity is a business unit that was created to allow courses to be assigned to Knowledge Link users from unrelated UPHS departments. (For further information on business units, see the documentation for the KNODE table. The business unit hierarchy is described in the documentation for PARENT_ID in the KNODE table.)

Example: 44922

Values:
List of values not available

The title of the version of this course that has the highest version number. (See LATEST_CO_REC_ID. Note: this is usually, but not always, the course version whose iterations are scheduled in the future, or were scheduled most recently in the past.) The course per se has no title specified in Knowledge Link, but LATEST_COURSE_TITLE may be considered to be the current title of the course. If no version has been created for this course, the value of LATEST_COURSE_TITLE is null. See also CO_MAS_ID, COURSE_MASTER_ID, and LATEST_CO_REC_ID.

Note: it is common for more than one course to have the same LATEST_COURSE_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.

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. Information on the latest course version is available in the COURSE_OBJECT table where LMS_COURSE_MASTER.LATEST_CO_REC_ID = COURSE_OBJECT.CO_REC_ID.

Most course version titles consist of three parts that identify both the content and provider of the course version, and follow 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)

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

Values:
List of values not available