• DATASOURCE
• DATE_CREATED
• DATE_MODIFIED
• EXPIRATION_DATE

• KNODE_ID
• STATUS
• TRANSFER_TYPE
• USER_REC_ID

Text indicating the system that assigned the Knowledge Link user (USER_REC_ID) to the business unit (KNODE_ID).

Values:
null (a Knowledge Link administrator 
      assigned the user to the 
      business unit)
UPENN_1 (the XML feed from the 
      University assigned the user 
      to the business unit)
Gen21_BU (the XML feed from the 
      University of Pennsylvania 
      Health System assigned the user 
      to the business unit)

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

Example: 10/24/2006

Values:
List of values not available

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

Example: 11/13/2007

Values:
List of values not available

If the KNODE_USER_JOIN record is inactive (STATUS=0), the EXPIRATION_DATE is the date when it became inactive.

EXPIRATION_DATE should be used in reports only if the KNODE_USER_JOIN record is inactive. An active record might or might not have a non-null value for EXPIRATION_DATE if the record was inactive in the past.

Example: 11/13/2007

Values:
List of values not available

A numeric value that identifies the business unit assigned to the Knowledge Link user (USER_REC_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. Most business units correspond to bureaucratic groups that reflect various administrative subdivisions used for University of Pennsylvania Health System (UPHS) employees, University employees, University students, and auxiliary members of the Penn Community (members whose training records and current training assignments are stored in Knowledge Link, but who are not UPHS employees or persons with a FAC, STAF, or STU affiliation). Some business units denote privileged groups, used to classify certain Knowledge Link users according to what they are authorized to do within the Knowledge Link system. Information on the business unit is available in the KNODE table.

A business unit may have zero, one, or more users assigned to it. Only business units that are Knowledge Positions can have users assigned to them. (For an explanation of what a Knowledge Position is, see the LMS_BUSINESS_UNIT_TYPE table.)

A Knowledge Link user may register for a course only if the course is assigned to a business unit that currently includes the user. While a KNODE_USER_JOIN record specifies the user and a business unit to which the user is assigned, the user is included in that business unit and in the business units that are above it in the business unit hierarchy. If a course is assigned to a business unit, a user is included in that business unit if he or she has a KNODE_USER_JOIN record that has STATUS = 1, and that has the KNODE_ID of the business unit itself or of a business unit that is below it in the hierarchy. (For more information on the business unit hierarchy, see PARENT_ID and TYPE in the KNODE table.)

Example: 10124

Values:
Refer to the KNODE table for values.

A KNODE_USER_JOIN record pairs a Knowledge Link user (USER_REC_ID) with a business unit (KNODE_ID) to which the user is assigned. STATUS is a numeral indicating whether the assignment 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. Most business units correspond to bureaucratic groups that reflect various administrative subdivisions used for University of Pennsylvania Health System (UPHS) employees, University employees, University students, and auxiliary members of the Penn Community (members whose training records and current training assignments are stored in Knowledge Link, but who are not UPHS employees or persons with a FAC, STAF, or STU affiliation). Some business units denote privileged groups, used to classify certain Knowledge Link users according to what they are authorized to do within the Knowledge Link system.

A Knowledge Link user may register for a course only if the course is assigned to a business unit that currently includes the user. While a KNODE_USER_JOIN record identifies a business unit to which the user is assigned, the user is included in that business unit and in the business units that are above it in the business unit hierarchy. If a course is assigned to a business unit, a user is included in that business unit if he or she has a KNODE_USER_JOIN record that has STATUS = 1, and that has the KNODE_ID of the business unit itself or of a business unit that is below it in the hierarchy. (For more information on the business unit hierarchy, see PARENT_ID and TYPE in the KNODE table.)

Values:
0 (inactive; the Knowledge Link user no longer 
   belongs to the business unit)
1 (active; the Knowledge Link user currently 
   belongs to the business unit)

A numeric value that indicates how the Knowledge Link user (USER_REC_ID) joined the business unit (KNODE_ID). Note: currently, this information is stored for trainees who are University of Pennsylvania Health System (UPHS) employees, but not for other trainees.

A business unit (also known as a BU, role, Knowledge Node, or K Node) is a set of one or more Knowledge Link users. (Information on the user is available in the LMS_PERSON table.) Most business units correspond to bureaucratic groups that reflect various administrative subdivisions used for University of Pennsylvania Health System (UPHS) employees, University employees, University students, and auxiliary members of the Penn Community (members whose training records and current training assignments are stored in Knowledge Link, but who are not UPHS employees or persons with a FAC, STAF, or STU affiliation). Some business units denote privileged groups, used to classify certain Knowledge Link users according to what they are authorized to do within the Knowledge Link system.

A user may be assigned to zero, one, or more business units. For example, a student that is also a University employee with a FAC or STAF affiliation in the Penn Community will have two KNODE_USER_JOIN records. A University of Pennsylvania Health System (UPHS) employee that is also part of a UPHS Knowledge Microcommunity will have two KNODE_USER_JOIN records. (For an explanation of what a Knowledge Microcommunity is, see the LMS_BUSINESS_UNIT_TYPE table.)

While a KNODE_USER_JOIN record specifies the user and a business unit to which the user is assigned, the user is included in that business unit and in the business units that are above it in the business unit hierarchy. If a course is assigned to a business unit, a user is included in that business unit if he or she has a KNODE_USER_JOIN record that both is active (has STATUS = 1) and specifies a KNODE_ID that either matches the course assignment’s business unit or falls under it in the hierarchy. (For more information on the business unit hierarchy, see PARENT_ID and TYPE in the KNODE table.)

In some cases, when a mandatory course is assigned to a business unit, not all of the trainees included in that 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. For example, say a mandatory course assignment is created that specifies course C, course version CV, and business unit B1. John Doe has an active assignment to business unit B2, which falls under B1 in the business unit hierarchy, so he is included in the mandatory course assignment. John is grandfathered for this mandatory course assignment if his TRANSFER_TYPE for B2 is grandfathered per the GRANDFATHERING_VALUE for CV. John is grandfathered for course C if he is grandfathered for all of the mandatory course assignments for C that include him. For more information on grandfathering, see the Cautions for the COURSE_OBJECT table on GRANDFATHERING_VALUE.

Values:
null (the transfer type is unknown)
1 (new employee)
2 (intra-department transfer)
4 (inter-department transfer)
8 (inter-entity transfer)

A numeric value that identifies the Knowledge Link user assigned to the business unit (KNODE_ID). Information on the user is available in the LMS_PERSON 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. Most business units correspond to bureaucratic groups that reflect various administrative subdivisions used for University of Pennsylvania Health System (UPHS) employees, University employees, University students, and auxiliary members of the Penn Community (members whose training records and current training assignments are stored in Knowledge Link, but who are not UPHS employees or persons with a FAC, STAF, or STU affiliation). Some business units denote privileged groups, used to classify certain Knowledge Link users according to what they are authorized to do within the Knowledge Link system.

A user may be assigned to zero, one, or more business units. For example, a student that is also a University employee with a FAC or STAF affiliation in the Penn Community will have two KNODE_USER_JOIN records. A University of Pennsylvania Health System (UPHS) employee that is also part of a UPHS Knowledge Microcommunity will have two KNODE_USER_JOIN records. (For an explanation of what a Knowledge Microcommunity is, see the LMS_BUSINESS_UNIT_TYPE table.)

A Knowledge Link user may register for a course only if the course is assigned to a business unit that currently includes the user. While a KNODE_USER_JOIN record specifies the user and a business unit to which the user is assigned, the user is included in that business unit and in the business units that are above it in the business unit hierarchy. If a course is assigned to a business unit, a user is included in that business unit if he or she has a KNODE_USER_JOIN record that has STATUS = 1, and that has the KNODE_ID of the business unit itself or of a business unit that is below it in the hierarchy. (For more information on the business unit hierarchy, see PARENT_ID and TYPE in the KNODE table.)

Example: 10159

Values:
Refer to the LMS_PERSON table or the 
  GEN21_USER table for values.