• CO_MAS_ID
• CO_MAS_ID_AS_IS
• CO_REC_ID
• CO_REC_ID_AS_IS
• COURSE_COMPLETED
• COURSE_ITERATION_TITLE
• COURSE_MASTER_ID
• COURSE_OWNER_BU_ID
• COURSE_OWNER_BU_NAME
• COURSE_OWNER_BU_NUMBER
• CURRENT_COURSE_REG_FLAG
• CURRENT_CRS_ITERATION_REG_FLAG
• CURRENT_PERIODICITY
• CURRENTLY_REQUIRED
• DATE_COURSE_COMPLETED
• DATE_REGISTRATION_CREATED
• DATE_REGISTRATION_DROPPED
• DATE_REGISTRATION_MODIFIED
• FIRST_NAME

• ITERATION_ID
• LAST_COURSE_COMPLETION_FLAG
• LAST_CRS_COMPL_OR_REG_FLAG
• LAST_EXTRACT_DATE
• LAST_NAME
• MIDDLE_INITIAL
• NEXT_COURSE_DATE
• PENN_ID
• REG_REC_ID
• REGISTRATION_BU_ID
• REGISTRATION_BU_NAME
• REGISTRATION_BU_NUMBER
• REGISTRATION_STATUS_CODE
• REGISTRATION_STATUS_DESC
• REGISTRATION_STATUS_REASON
• TIME_COURSE_COMPLETED
• USER_REC_ID
• WAIT_LIST_PRIORITY

The number used within the Knowledge Link system as the unique identifier for the course that includes the course iteration (ITERATION_ID) for which the trainee (USER_REC_ID) has registered per this registration request (REG_REC_ID). See also COURSE_MASTER_ID and CO_REC_ID.

To retrieve the attributes of the course, query the LMS_COURSE_MASTER table where LMS_REGISTRATION.CO_MAS_ID = LMS_COURSE_MASTER.CO_MAS_ID.

A course is a formal educational unit that deals with a particular subject. A course provides training to members of the Penn Community in support of their academic activities and job responsibilities at the University and/or at the University of Pennsylvania Health System. A course may have more than one version. For example, if the course covers Software Package X, version 1 of the course might cover Software Package X release 2.0, and version 2 of the course might cover Software Package X release 3.5. A course iteration is an offering of a particular version of the course. A course version may have more than one course iteration. For example, version 2 of the instructor-led course on Software Package X will have two course iterations if it is offered in two different places on the same date and at the same time. Web-based courses commonly have one iteration per version.

Examples: 12437 (UNIV_ALL_ALL_PROFILER ); 10252 (UPHS_HUP_NURS_ORT131)

Values:
Refer to the LMS_COURSE_MASTER
or COURSE_MASTER table for values.
Note:  some of the courses in those tables
have no associated LMS_REGISTRATION records.

According to the Knowledge Link REGISTRATION table's record for this registration request (REG_REC_ID), this is the identifier of the course for which the trainee (USER_REC_ID) has registered in Knowledge Link. Trainees register for course iterations (not courses); CO_MAS_ID_AS_IS might not accurately reflect the course to which the course iteration (ITERATION_ID) belongs. See also CO_MAS_ID and CO_REC_ID_AS_IS.

CO_MAS_ID_AS_IS stores the number used within the Knowledge Link system as the unique identifier for a course. To retrieve the attributes of the course, query the LMS_COURSE_MASTER table where LMS_REGISTRATION.CO_MAS_ID_AS_IS = LMS_COURSE_MASTER.CO_MAS_ID.

A course is a formal educational unit that deals with a particular subject. A course provides training to members of the Penn Community in support of their academic activities and job responsibilities at the University and/or at the University of Pennsylvania Health System. A course may have more than one version. For example, if the course covers Software Package X, version 1 of the course might cover Software Package X release 2.0, and version 2 of the course might cover Software Package X release 3.5. A course iteration is an offering of a particular version of the course. A course version may have more than one course iteration. For example, version 2 of the instructor-led course on Software Package X will have two course iterations if it is offered in two different places on the same date and at the same time. Web-based courses commonly have one iteration per version.

Examples: 12437 (UNIV_ALL_ALL_PROFILER ); 10221 (UPHS_HUP_NURS_ORT101)

Values:
Refer to the LMS_COURSE_MASTER
or COURSE_MASTER table for values.
Note:  some of the courses in those tables
have no associated LMS_REGISTRATION records.

The number used within the Knowledge Link system as the unique identifier for the course version offered in the course iteration (ITERATION_ID) for which the trainee (USER_REC_ID) has registered per this registration request (REG_REC_ID). See also CO_MAS_ID and COURSE_MASTER_ID.

To retrieve the attributes of the course version, query the COURSE_OBJECT table where LMS_REGISTRATION.CO_REC_ID = COURSE_OBJECT.CO_REC_ID.

A course is a formal educational unit that deals with a particular subject. A course provides training to members of the Penn Community in support of their academic activities and job responsibilities at the University and/or at the University of Pennsylvania Health System. A course may have more than one version. For example, if the course covers Software Package X, version 1 of the course might cover Software Package X release 2.0, and version 2 of the course might cover Software Package X release 3.5. A course iteration is an offering of a particular version of the course. A course version may have more than one course iteration. For example, version 2 of the instructor-led course on Software Package X will have two course iterations if it is offered in two different places on the same date and at the same time. Web-based courses commonly have one iteration per version.

Examples: 12675 (UNIV_ALL_ALL_PROFILER_v1; PennProfiler-Required Training Assessment-VPR); 10272 (UPHS_HUP_NURS_ORT131_v1; Nurse Residency Program - HUP); 10000 (UPHS_ALL_WORK_HIPAA105_v1; HIPAA Privacy Overview for the Workforce [Learning Module Only] - UPHS)

Values:
Refer to the COURSE_OBJECT table for values.
Note:  some of the course versions in that table
have no associated LMS_REGISTRATION records.

According to the Knowledge Link REGISTRATION table's record for this registration request (REG_REC_ID), this is the identifier of the course version for which the trainee has registered in Knowledge Link. Trainees register for course iterations (not course versions); CO_REC_ID_AS_IS might not accurately reflect the course version that is offered in the course iteration (ITERATION_ID). See also CO_REC_ID and CO_MAS_ID_AS_IS.

CO_REC_ID_AS_IS stores the number used within the Knowledge Link system as the unique identifier for a course version. To retrieve the attributes of the course version, query the COURSE_OBJECT table where LMS_REGISTRATION.CO_REC_ID_AS_IS = COURSE_OBJECT.CO_REC_ID.

A course is a formal educational unit that deals with a particular subject. A course provides training to members of the Penn Community in support of their academic activities and job responsibilities at the University and/or at the University of Pennsylvania Health System. A course may have more than one version. For example, if the course covers Software Package X, version 1 of the course might cover Software Package X release 2.0, and version 2 of the course might cover Software Package X release 3.5. A course iteration is an offering of a particular version of the course. A course version may have more than one course iteration. For example, version 2 of the instructor-led course on Software Package X will have two course iterations if it is offered in two different places on the same date and at the same time. Web-based courses commonly have one iteration per version.

Examples: 12675 (UNIV_ALL_ALL_PROFILER_v1; PennProfiler-Required Training Assessment-VPR); 10241 (UPHS_HUP_NURS_ORT101_v1; Nursing Orientation - HUP)

Values:
Refer to the COURSE_OBJECT table for values.
Note:  some of the course versions in that table
have no associated LMS_REGISTRATION records.

A Yes/No flag indicating whether the trainee (USER_REC_ID) has completed the course iteration (ITERATION_ID) for which the trainee has registered per this registration request (REG_REC_ID). See also DATE_COURSE_COMPLETED, LAST_COURSE_COMPLETION_FLAG, and CURRENTLY_REQUIRED.

Note: A trainee may legitimately be on record as having completed the course iteration even if the registration status is not Enrolled.

If the course offered in this course iteration is currently required for this trainee, and the trainee has completed the course iteration, and is not overdue to re-take the course, the trainee is compliant with regard to the course. For compliance information regarding the trainee and course, see the LMS_CURRENT_TRAINEE_CRS_STATUS table.

Values:
Y (the trainee has completed the course iteration)
N (the trainee has not completed the course iteration)

The name of the course iteration (ITERATION_ID) for which the trainee (USER_REC_ID) has registered per this registration request (REG_REC_ID). The course iteration's title might or might not be the same as the course version's title. It is common for more than one course iteration to have the same value for COURSE_ITERATION_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. A course iteration is an offering of a particular version of the course. A course version may have more than one course iteration. For example, version 2 of the instructor-led course on Software Package X will have two course iterations if it is offered in two different places on the same date and at the same time. Web-based courses commonly have one iteration per version.

Examples: 'PennProfiler-Required Training Assessment-VPR'; 'Nursing Orientation - HUP'; 'HIPAA ED - WORKFORCE (EMP)' The value is stored without the surrounding quotes.

Values:
Refer to the COURSE_ITERATION table for values.
Note:  some of the course iterations in that table
have no associated LMS_REGISTRATION records.

A string that uniquely identifies the course that includes the course iteration (ITERATION_ID) for which the trainee (USER_REC_ID) has registered per this registration request (REG_REC_ID). See also CO_MAS_ID and CO_REC_ID.

To retrieve the attributes of the course, query the LMS_COURSE_MASTER table where LMS_REGISTRATION.COURSE_MASTER_ID = LMS_COURSE_MASTER.COURSE_MASTER_ID.

A course is a formal educational unit that deals with a particular subject. A course provides training to members of the Penn Community in support of their academic activities and job responsibilities at the University and/or at the University of Pennsylvania Health System. A course may have more than one version. For example, if the course covers Software Package X, version 1 of the course might cover Software Package X release 2.0, and version 2 of the course might cover Software Package X release 3.5. A course iteration is an offering of a particular version of the course. A course version may have more than one course iteration. For example, version 2 of the instructor-led course on Software Package X will have two course iterations if it is offered in two different places on the same date and at the same time. Web-based courses commonly have one iteration per version.

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)

Examples: UNIV_ALL_ALL_PROFILER ; UPHS_HUP_NURS_ORT131

Values:
Refer to the LMS_COURSE_MASTER table for values.
Note:  some of the courses in that table
have no associated LMS_REGISTRATION records.

A string that uniquely identifies the business unit that owns the course version (CO_REC_ID). See also COURSE_OWNER_BU_NAME and COURSE_OWNER_BU_NUMBER.

Knowledge Communities (KC) and Knowledge Microcommunities (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. (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.)

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. For more information, see the data element documentation for COURSE_OBJECT.KNODE_ID.

The COURSE_OWNER_BU_ID is the KNODE.IDENTIFIER where LMS_REGISTRATION.COURSE_OWNER_BU_NUMBER = KNODE.KNODE_ID. For information on how the COURSE_OWNER_BU_ID value is formatted, see the data element documentation for KNODE.IDENTIFIER.

Examples: 'UP.EHRS'; 'HS.PATREG' The value is stored without the surrounding quotes.

Values:
Refer to the KNODE table for values.
Note:  some of the business units in that table
have no associated LMS_REGISTRATION records.

A phrase or string that describes the business unit that owns the course version (CO_REC_ID). It is possible for more than one business unit to have the same name. See also COURSE_OWNER_BU_ID and COURSE_OWNER_BU_NUMBER.

Knowledge Communities (KC) and Knowledge Microcommunities (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. (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.)

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. For more information, see the data element documentation for COURSE_OBJECT.KNODE_ID.

The COURSE_OWNER_BU_NAME is the KNODE.NAME where LMS_REGISTRATION.COURSE_OWNER_BU_NUMBER = KNODE.KNODE_ID. For information on how the COURSE_OWNER_BU_NAME value is formatted, see the data element documentation for KNODE.NAME.

Examples: 'Environmental Health and Radiation Safety Parent'; 'Patient Registration' The value is stored without the surrounding quotes.

Values:
Refer to the KNODE table for values.
Note:  some of the business units in that table
have no associated LMS_REGISTRATION records.

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 COURSE_OWNER_BU_NUMBER value corresponds to a KNODE.KNODE_ID. See also COURSE_OWNER_BU_ID and COURSE_OWNER_BU_NAME.

Knowledge Communities (KC) and Knowledge Microcommunities (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. (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.)

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. For more information, see the data element documentation for COURSE_OBJECT.KNODE_ID.

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

Values:
Refer to the KNODE table for values.
Note:  some of the business units in that table
have no associated LMS_REGISTRATION records.

A Yes/No flag indicating whether this LMS_REGISTRATION record is the one that reflects the trainee’s latest Enrolled or Wait-Listed registration for the course. A trainee (identified by the PENN_ID or USER_REC_ID) may have more than one record for a given course (identified by the COURSE_MASTER_ID or CO_MAS_ID), but one record at most will have CURRENT_COURSE_REG_FLAG = 'Y'. If the trainee does not have an Enrolled or Wait-Listed registration for the course, all of the records for the trainee and course have CURRENT_COURSE_REG_FLAG = 'N'.

See also CURRENT_CRS_ITERATION_REG_FLAG, LAST_COURSE_COMPLETION_FLAG, LAST_CRS_COMPL_OR_REG_FLAG, REGISTRATION_STATUS_CODE, REGISTRATION_STATUS_DESC, REGISTRATION_STATUS_REASON, and WAIT_LIST_PRIORITY.

A trainee registers for a course iteration (ITERATION_ID), which is an offering of a particular version (CO_REC_ID) of a course (CO_MAS_ID). If the trainee has registered for more than one iteration of the course, there are multiple records for the trainee and course with CURRENT_CRS_ITERATION_REG_FLAG = ‘Y’. When determining which of those records is the one that reflects the trainee’s latest Enrolled or Wait-Listed registration for the course, the first factor considered is the distribution mode for the course version for which the trainee has registered. (The distribution mode is the COURSE_OBJECT.DIST_MODE where LMS_REGISTRATION.CO_REC_ID = COURSE_OBJECT.CO_REC_ID.) Another factor is the course iteration’s start date and time—the START_DATE and START_TIME in COURSE_ITERATION table where LMS_REGISTRATION.ITERATION_ID = COURSE_ITERATION.ITERATION_ID.

If the course version is instructor-led (DIST_MODE = 13), this is the order of preference for choosing the record that has CURRENT_COURSE_REG_FLAG set to ‘Y’:

1. Start with the group of records for the trainee and course where CURRENT_CRS_ITERATION_REG_FLAG is ‘Y’ and with REGISTRATION_STATUS_DESC is ‘Enrolled’ or ‘Wait-Listed’.
2. Ignore the records (if any) for iterations whose start date falls before today. Among the remaining records, find the one(s) with the highest values for the iteration start date and time where REGISTRATION_STATUS_DESC is ‘Enrolled’. If only one is found, choose it; if more than one is found, choose the record that also has the highest value for REG_REC_ID.
3. Ignore the records (if any) for iterations whose start date falls before today. Among the remaining records, find the one(s) whose iteration start date falls closest to today's date and whose REGISTRATION_STATUS_DESC is ‘Wait-Listed’. If only one is found, choose it; if more than one is found, find the record(s) that also have the lowest value for the iteration start time. If only one is found, choose it; if more than one is found, choose the record that also has the highest value for REG_REC_ID.
4. Find the record(s) with the highest values for the iteration start date and time where REGISTRATION_STATUS_DESC is ‘Enrolled’. If only one is found, choose it; if more than one is found, choose the record that also has the highest value for REG_REC_ID.
5. Find the record(s) with the highest values for the iteration start date and time where REGISTRATION_STATUS_DESC is ‘Wait-Listed’. If only one is found, choose it; if more than one is found, choose the record that also has the highest value for REG_REC_ID.
6. If the group does not include a record that was chosen in one of the four steps described above, all of the records in the group have CURRENT_COURSE_REG_FLAG set to 'N'.

If the course version is not instructor-led, this is the order of preference for choosing the record that has CURRENT_COURSE_REG_FLAG set to ‘Y’:

1. Start with the group of records for the trainee and course where CURRENT_CRS_ITERATION_REG_FLAG is ‘Y’ and with REGISTRATION_STATUS_DESC is ‘Enrolled’. (Courses that are not instructor-led do not have ‘Wait-Listed’ records.)
2. Find the record(s) with the highest values for the iteration start date and time. If only one is found, choose it. If more than one is found,
3. choose the record that also has COURSE_COMPLETED=0. If there is no such record,
4. choose the record that also has the highest value for the sort date. (If DATE_COMPLETED is not null, the sort date's value is set to the value of DATE_COMPLETED. Otherwise, the sort date's value is set to the value of DATE_CREATED.)
5. If the group of records for the trainee and course does not include a record that was chosen in one of the three steps described above, all of the records in the group have CURRENT_COURSE_REG_FLAG set to 'N'.

Values:
Y (this record reflects the trainee's latest Enrolled or 
   Wait-Listed registration for the course)
N (this record stores information that either has been superseded 
   by a later record pertaining to the trainee and the course,
   or pertains to a Dropped registration)

A Yes/No flag indicating whether this LMS_REGISTRATION record is the one that reflects the trainee’s current registration status with regard to the course iteration. A trainee (identified by the PENN_ID or USER_REC_ID) may have more than one record for a given course iteration (identified by the ITERATION_ID). To report on the trainee’s current registration status regarding a course iteration, select records where CURRENT_CRS_ITERATION_REG_FLAG = ‘Y’. See also CURRENT_COURSE_REG_FLAG, LAST_COURSE_COMPLETION_FLAG, LAST_CRS_COMPL_OR_REG_FLAG, REGISTRATION_STATUS_CODE, REGISTRATION_STATUS_DESC, REGISTRATION_STATUS_REASON, and WAIT_LIST_PRIORITY.

In the set of LMS_REGISTRATION records for a given trainee and course iteration, the one with the highest value of REG_REC_ID is the one whose CURRENT_CRS_ITERATION_REG_FLAG = ‘Y’. The other records in that set have CURRENT_CRS_ITERATION_REG_FLAG = ‘N’.

Values:
Y (this record reflects the trainee's current registration 
   status with regard to the course iteration)
N (this record stores information that has been superseded 
   by a later record pertaining to the trainee and the course 
   iteration)

The current value of the number of months in the period from the time when the trainee (USER_REC_ID) completes the course (CO_MAS_ID) to the time when the trainee is due to complete it again. PERIODICITY is a factor when the course is currently required for the trainee (CURRENTLY_REQUIRED = ‘Y’); it is irrelevant for optional courses. In some cases, PERIODICITY is null.

When PERIODICITY is null or 0, and the course is currently required for the trainee, the trainee is required to complete it only once.

Examples: 0, 12

Values:
List of values not available

A Yes/No flag indicating whether or not the course (CO_MAS_ID) is currently required for the trainee (USER_REC_ID). See also COURSE_COMPLETED and DATE_COURSE_COMPLETED.

If the course is actively assigned as a mandatory course to a business unit that currently includes the trainee, and the trainee is not grandfathered for the course, CURRENTLY_REQUIRED is 'Y'. For further information about grandfathering, see the data element documentation for LMS_TRAINEE_BU_COURSE_ASSIGN.GRANDFATHERED.

If the trainee is currently required to take the course offered in the course iteration (ITERATION_ID), and has completed the course iteration, and is not overdue to re-take the course, the trainee is compliant with regard to the course. For compliance information regarding the trainee and course, see the LMS_CURRENT_TRAINEE_CRS_STATUS table.

The primary source of information on which courses are currently required for trainees is the KNODE_CRS_JOIN table, which stores information on mandatory and optional courses currently assigned to business units that may represent individual trainees or groups of trainees. The USER_COURSES and LMS_TRAINEE_BU_COURSE_ASSIGN tables store information on mandatory courses currently assigned to individual trainees. If a trainee belongs to multiple business units that have the same mandatory course assigned to them, these tables store more than one record for the trainee and course. The LMS_TRAINEE_COURSE_ASSIGN table stores one record per trainee and currently required course. Historical information on required course assignments is not available. If a trainee was once required to take a particular course, but is not currently required to take it, there is no way to tell that the course was ever required for the trainee.

Values:
Y (the course is currently a required course for the trainee)
N (the course is currently an optional course for the trainee)

The date when the trainee (USER_REC_ID) completed the course iteration (ITERATION_ID) for which the trainee has registered per this registration request (REG_REC_ID). See also COURSE_COMPLETED, LAST_COURSE_COMPLETION_FLAG, and CURRENTLY_REQUIRED.

Note:

• A trainee may legitimately be on record as having completed the course iteration even if the registration status is not Enrolled.
• Some records have a non-null value for DATE_COURSE_COMPLETED, even though COURSE_COMPLETED = 'N'. If COURSE_COMPLETED = 'N', DATE_COURSE_COMPLETED should be ignored.

If the course offered in this course iteration is currently required for this trainee, and the trainee has completed the course iteration, and is not overdue to re-take the course, the trainee is compliant with regard to the course. For compliance information regarding the trainee and course, see the LMS_CURRENT_TRAINEE_CRS_STATUS table.

Example: 4/11/2007

Values:
List of values not available

The date when the record for this registration request (REG_REC_ID) was created. The value might or might not include the time. See also DATE_REGISTRATION_MODIFIED and DATE_REGISTRATION_DROPPED.

Note: the value for DATE_REGISTRATION_CREATED might not be reliable. For example, some records have a value for DATE_REGISTRATION_CREATED that is later than the value for DATE_REGISTRATION_MODIFIED.

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 created on a particular date (say, 7/21/2008), include a query filter stipulating that DATE_REGISTRATION_CREATED is greater than or equal to 7/21/2008 and DATE_REGISTRATION_CREATED is less than 7/22/2008. (The system will supply the time--12:00:00 AM--for both dates.)

Examples: 5/29/2009; 4/24/2006 3:17:06 PM

Values:
List of values not available

The date when the record for this registration request (REG_REC_ID) had its registration status changed to Dropped. The value might or might not include the time. DATE_REGISTRATION_DROPPED is null if the status was never changed to Dropped. See also REGISTRATION_STATUS_CODE, REGISTRATION_STATUS_DESC, REGISTRATION_STATUS_REASON, DATE_REGISTRATION_CREATED and DATE_REGISTRATION_MODIFIED.

Note:

• DATE_REGISTRATION_DROPPED may have a non-null value even if the registration status is not Dropped. When a trainee (USER_REC_ID) decides to cancel his or her registration for a course iteration (ITERTATION_ID), he or she drops the course in Knowledge Link. The record for the current registration request for the trainee and course iteration (CURRENT_CRS_ITERATION_REG_FLAG = ‘Y’) has its registration status changed to Dropped. However, an instructor may later override the registration status (often to change it to Enrolled).
• The value for DATE_REGISTRATION_DROPPED might not be reliable.
  • Some records have a null value for DATE_REGISTRATION_DROPPED even though their registration status is Dropped.
  • Some records have a value for DATE_REGISTRATION_CREATED that is later than the value for DATE_REGISTRATION_DROPPED.

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 created on a particular date (say, 7/21/2008), include a query filter stipulating that DATE_REGISTRATION_DROPPED is greater than or equal to 7/21/2008 and DATE_REGISTRATION_DROPPED is less than 7/22/2008. (The system will supply the time--12:00:00 AM--for both dates.)

Examples: 8/28/2009; 4/26/2006 10:45:52 AM

Values:
List of values not available

The date when the record for this registration request (REG_REC_ID) was last modified. The value might or might not include the time. See also DATE_REGISTRATION_CREATED and DATE_REGISTRATION_DROPPED.

Note: the value for DATE_REGISTRATION_MODIFIED might not be reliable. For example, some records have a value for DATE_REGISTRATION_CREATED that is later than the value for DATE_REGISTRATION_MODIFIED, and some have a value for DATE_REGISTRATION_DROPPED that is later than the value for DATE_REGISTRATION_MODIFIED.

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 created on a particular date (say, 7/21/2008), include a query filter stipulating that DATE_REGISTRATION_MODIFIED is greater than or equal to 7/21/2008 and DATE_REGISTRATION_MODIFIED is less than 7/22/2008. (The system will supply the time--12:00:00 AM--for both dates.)

Examples: 4/19/2010; 4/26/2006 10:45:52 AM

Values:
List of values not available

The given name of the trainee (USER_REC_ID), stored in upper case to facilitate record selection conditions and sorting. See also MIDDLE_INITIAL and LAST_NAME.

The FIRST_NAME is taken from LMS_PERSON.FIRST_NAME where LMS_REGISTRATION.USER_REC_ID = LMS_PERSON.USER_REC_ID. Further information about the trainee is available in the LMS_PERSON table.

Example: ABIGAIL

Values:
List of values not available.

The number used within the Knowledge Link system as the unique identifier for the course iteration (ITERATION_ID) for which the trainee (USER_REC_ID) has registered per this registration request (REG_REC_ID). See also CO_REC_ID, CO_MAS_ID, and COURSE_MASTER_ID.

To retrieve the attributes of the course iteration, query the COURSE_ITERATION table where LMS_REGISTRATION.ITERATION_ID = COURSE_ITERATION.ITERATION_ID.

A course is a formal educational unit that deals with a particular subject. A course provides training to members of the Penn Community in support of their academic activities and job responsibilities at the University and/or at the University of Pennsylvania Health System. A course may have more than one version. For example, if the course covers Software Package X, version 1 of the course might cover Software Package X release 2.0, and version 2 of the course might cover Software Package X release 3.5. A course iteration is an offering of a particular version of the course. A course version may have more than one course iteration. For example, version 2 of the instructor-led course on Software Package X will have two course iterations if it is offered in two different places on the same date and at the same time. Web-based courses commonly have one iteration per version.

Examples: 100856 (PennProfiler-Required Training Assessment-VPR); 13514 (RESIDENCY PHASE II (8&9/04)); 12323 (HIPAA ONLINE EDU - MANAGER EQUIV)

Values:
Refer to the COURSE_ITERATION table for values.
Note:  some of the course iterations in that table
have no associated LMS_REGISTRATION records.

A Yes/No flag indicating whether this LMS_REGISTRATION record is the one with information on the trainee’s latest completion of the course. A trainee (identified by the PENN_ID or USER_REC_ID) may have records for multiple completions of the same course. A trainee registers for a course iteration (ITERATION_ID), which is an offering of a particular version (CO_REC_ID) of a course (CO_MAS_ID). For example, if the trainee has been required to complete the course yearly for the past three years, the trainee might have three completion records for three different iterations and/or versions of the course. To report on the trainee’s latest completion of the course, select records where LAST_COURSE_COMPLETION_FLAG = ‘Y’. See also CURRENT_CRS_ITERATION_REG_FLAG, CURRENT_COURSE_REG_FLAG, and LAST_CRS_COMPL_OR_REG_FLAG.

In the set of LMS_REGISTRATION records for a given trainee and course, one record at most may have LAST_COURSE_COMPLETION_FLAG = ‘Y’. Note: if none of a trainee’s LMS_REGISTRATION records for a course have COURSE_COMPLETED = ‘Y’, all of those records will have LAST_COURSE_COMPLETION_FLAG = ‘N’.

When determining which record is the one with information on a particular trainee’s latest completion of a particular course, two of the factors considered are the course iteration’s start date and time—the START_DATE and START_TIME in COURSE_ITERATION table where LMS_REGISTRATION.ITERATION_ID = COURSE_ITERATION .ITERATION_ID.

Given a group of records for a given trainee and course where COURSE_COMPLETED = ‘Y’, this is the order of preference for choosing which record has LAST_COURSE_COMPLETION_FLAG set to ‘Y’:

1. Find the record(s) with the highest values for the iteration start date and time.
   If only one is found, choose it. If more than one is found,
2. find the record(s) that also have the highest value for the sort date. (If DATE_COMPLETED is not null, the sort date's value is set to the value of DATE_COMPLETED. Otherwise, the sort date's value is set to the value of DATE_CREATED.) If only one is found, choose it. If more than one is found,
3. choose the record that also has the highest value for REG_REC_ID.

Values:
Y (this record is the one with information on the 
   trainee’s latest completion of the course)
N (this record stores information that has been 
   superseded by a later record pertaining to the trainee's
   completion of the course)

A Yes/No flag that indicates which registration record is reflected in the LMS_CURRENT_TRAINEE_CRS_STATUS record for the trainee and course. If a trainee has completed a course and is not overdue to re-take it, the LMS_CURRENT_TRAINEE_CRS_STATUS record for that trainee and course stores information from the LMS_REGISTRATION record with information on the trainee’s latest completion of the course. Otherwise, the LMS_CURRENT_TRAINEE_CRS_STATUS record for that trainee and course stores information from the LMS_REGISTRATION record that reflects the trainee’s latest Enrolled or Wait-Listed registration for the course.

In the set of LMS_REGISTRATION records for a given trainee and course, one record at most will have LAST_CRS_COMPL_OR_REG_FLAG = 'Y'. The other records in that set have LAST_CRS_COMPL_OR_REG_FLAG = 'N'. If the trainee does not have an Enrolled or Wait-Listed registration for the course, and has never completed an iteration of the course, there is no record for the trainee and course that has LAST_CRS_COMPL_OR_REG_FLAG = 'Y'.

When determining which record is the one whose information is reflected in the LMS_CURRENT_TRAINEE_CRS_STATUS record for a trainee and a course, the first factor considered is whether the course is currently required for the trainee (CURRENTLY_REQUIRED = ‘Y’), or whether it is optional (CURRENTLY_REQUIRED = ‘N’). If it is currently required, the next factor considered is whether the trainee is compliant with regard to the course. (If the trainee is currently required to take the course offered in the course iteration, and has completed the course iteration, and is not overdue to re-take the course, the trainee is compliant with regard to the course.) The Yes/No flag indicating whether the trainee is compliant with regard to the course is LMS_TRAINEE_COURSE_ASSIGN.COMPLIANT where LMS_REGISTRATION.USER_REC_ID = LMS_TRAINEE_COURSE_ASSIGN.USER_REC_ID and LMS_REGISTRATION.CO_MAS_ID = LMS_TRAINEE_COURSE_ASSIGN. CO_MAS_ID.

This is the order of preference for choosing which of a group of LMS_REGISTRATION records for a given trainee and course has LAST_CRS_COMPL_OR_REG_FLAG set to 'Y':

1. If the course is currently required for the trainee, and the trainee is compliant, choose the record with LAST_COURSE_COMPLETION_FLAG = ‘Y’.
2. If the course is currently required for the trainee, and the trainee is not compliant, choose the record with CURRENT_COURSE_REG_FLAG = ‘Y’.
3. If there is a record with LAST_COURSE_COMPLETION_FLAG = ‘Y’, choose it.
4. Choose the record with CURRENT_COURSE_REG_FLAG = ‘Y’.
5. If the group of records for the trainee and course does not include a record that was chosen in one of the four steps described above, all of the records in the group have LAST_CRS_COMPL_OR_REG_FLAG set to 'N'.

See also CURRENT_CRS_ITERATION_REG_FLAG, CURRENT_COURSE_REG_FLAG, and LAST_COURSE_COMPLETION_FLAG.

Values:
Y (this record is the one whose information is 
   reflected in the LMS_CURRENT_TRAINEE_CRS_STATUS
   record for the trainee and course)
N (this record is not the one whose information is 
   reflected in the LMS_CURRENT_TRAINEE_CRS_STATUS
   record for the trainee and course)

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

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.

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

Values:
List of values not available

The surname of the trainee (USER_REC_ID), stored in upper case to facilitate record selection conditions and sorting. See also FIRST_NAME and MIDDLE_INITIAL.

The LAST_NAME is taken from LMS_PERSON.LAST_NAME where LMS_REGISTRATION.USER_REC_ID = LMS_PERSON.USER_REC_ID. Further information about the trainee is available in the LMS_PERSON table.

Example: ADAMS

Values:
List of values not available

The first letter of the middle name of the trainee (USER_REC_ID), stored in upper case. The value is null for some trainees. See also FIRST_NAME and LAST_NAME.

Note: although the value of MIDDLE_INITIAL ought to be an upper case letter (if it is not null), it can be a character of any type--for example, '-'.

The MIDDLE_INITIAL is taken from LMS_PERSON.MIDDLE_INITIAL where LMS_REGISTRATION.USER_REC_ID = LMS_PERSON.USER_REC_ID. Further information about the trainee is available in the LMS_PERSON table.

Example: S

Values:
List of values not available

This data element currently is not used, even when its value is not null. See LMS_TRAINEE_COURSE_ASSIGN.DUE_DATE or
LMS_CURRENT_TRAINEE_CRS_STATUS.DUE_BY_DATE.

An 8-digit identification number assigned to the trainee by the Penn Community system. No two persons have the same Penn ID. See also USER_REC_ID, FIRST_NAME, MIDDLE_INITIAL, and LAST_NAME.

Most tables in the Data Warehouse use PENN_ID as the unique identifier for a person. This facilitates joining tables with data that pertains to people, regardless of whether those tables are in the same data collection.

Example: 12345678

Values:
Refer to the LMS_PERSON table for values.
Note:  some of the trainees in that table
have no associated LMS_REGISTRATION records.

A number used within the Knowledge Link system as the unique identifier for the registration request record. There is one LMS_REGISTRATION record per REG_REC_ID. When a registration request record is created, it is assigned a REG_REC_ID whose value is 1 plus the value of the highest REG_REC_ID in the REGISTRATION table.

A trainee may have multiple LMS_REGISTRATION records for the same course iteration. For example, say that Jane Smith (USER_REC_ID 12345) registers for an iteration of Workplace Hazard Assessment - EHRS to be held on the first of next month at 8:30 a.m. in the Left Bank Building's EHRS Conference Room. (ITERATION_ID 98765). An LMS_REGISTRATION record is created for this registration request with REG_REC_ID 3333333. Its registration status is initially Wait-Listed. When a seat in the course iteration becomes available, the status changes to Enrolled. Then Jane is asked to attend a meeting that will be held at the same time as the course iteration. She drops the course (changing the status to Dropped). However, the meeting is cancelled, so Jane registers again for ITERATION_ID 98765. Another LMS_REGISTRATION record is created for this new registration request for USER_REC_ID 12345 and ITERATION_ID 98765, with REG_REC_ID 3333345.

Example: 10143

Values:
List of values not available

A string that uniquely identifies the business unit that, at the time of the registration request, included the trainee (USER_REC_ID) and had the course version (CO_REC_ID) assigned to it. See also REGISTRATION_BU_NAME and REGISTRATION_BU_NUMBER.

A trainee registers for a course iteration (ITERATION_ID), which is an offering of a particular version (CO_REC_ID) of a course (CO_MAS_ID). A trainee cannot register for an iteration of a course version if that course version does not have an active assignment to a business unit that includes the trainee.

A business unit (also known as a BU, role, Knowledge Node, or K Node) is a set of one or more Knowledge Link users. Business unit X includes a trainee if that trainee is actively assigned to X (see the KNODE_USER_JOIN table) or to a business unit that that falls below X in the business unit hierarchy. (For more information on the business unit hierarchy, see the documentation on PARENT_ID and TYPE in the KNODE table.)

The REGISTRATION_BU_ID is the KNODE.IDENTIFIER where LMS_REGISTRATION.REGISTRATION_BU_NUMBER = KNODE.KNODE_ID. For information on how the REGISTRATION_BU_ID value is formatted, see the data element documentation for KNODE.IDENTIFIER.

Examples: 'UP.10001205'; 'UP.0101'; 'HS.BCCD' The value is stored without the surrounding quotes.

Values:
Refer to the KNODE table for values.
Note:  some of the business units in that table
have no associated LMS_REGISTRATION records.

A phrase or string that describes the business unit that, at the time of the registration request, included the trainee (USER_REC_ID) and had the course version (CO_REC_ID) assigned to it. It is possible for more than one business unit to have the same name. See also REGISTRATION_BU_ID and REGISTRATION_BU_NUMBER.

A trainee registers for a course iteration (ITERATION_ID), which is an offering of a particular version (CO_REC_ID) of a course (CO_MAS_ID). A trainee cannot register for an iteration of a course version if that course version does not have an active assignment to a business unit that includes the trainee.

A business unit (also known as a BU, role, Knowledge Node, or K Node) is a set of one or more Knowledge Link users. Business unit X includes a trainee if that trainee is actively assigned to X (see the KNODE_USER_JOIN table) or to a business unit that that falls below X in the business unit hierarchy. (For more information on the business unit hierarchy, see the documentation on PARENT_ID and TYPE in the KNODE table.)

The REGISTRATION_BU_NAME is the KNODE.NAME where LMS_REGISTRATION.REGISTRATION_BU_NUMBER = KNODE.KNODE_ID. For information on how the REGISTRATION_BU_NAME value is formatted, see the data element documentation for KNODE.NAME.

Examples: 'UP.jsheehan.External Affairs.ASSOC DEAN ADMIN'; 'Anthropology'; 'Billing Compliance (BCCD)' The value is stored without the surrounding quotes.

Values:
Refer to the KNODE table for values.
Note:  some of the business units in that table
have no associated LMS_REGISTRATION records.

A number used to uniquely identify the business unit that, at the time of the registration request, included the trainee (USER_REC_ID) and had the course version (CO_REC_ID) assigned to it. The REGISTRATION_BU_NUMBER value corresponds to a KNODE.KNODE_ID. See also REGISTRATION_BU_ID and REGISTRATION_BU_NAME.

A trainee registers for a course iteration (ITERATION_ID), which is an offering of a particular version (CO_REC_ID) of a course (CO_MAS_ID). A trainee cannot register for an iteration of a course version if that course version does not have an active assignment to a business unit that includes the trainee.

A business unit (also known as a BU, role, Knowledge Node, or K Node) is a set of one or more Knowledge Link users. Business unit X includes a trainee if that trainee is actively assigned to X (see the KNODE_USER_JOIN table) or to a business unit that that falls below X in the business unit hierarchy. (For more information on the business unit hierarchy, see the documentation on PARENT_ID and TYPE in the KNODE table.)

Examples: 10022, 44239, 61352

Values:
Refer to the KNODE table for values.
Note:  some of the courses in that table
have no associated LMS_REGISTRATION records.

A number that uniquely identifies the status of the registration of the trainee (USER_REC_ID) for the course iteration (ITERATION_ID) per this registration request (REG_REC_ID). See also REGISTRATION_STATUS_DESC, REGISTRATION_STATUS_REASON, WAIT_LIST_PRIORITY, CURRENT_CRS_ITERATION_REG_FLAG, and CURRENT_COURSE_REG_FLAG.

A trainee may have multiple LMS_REGISTRATION records for the same course iteration. For example, say that Jane Smith (USER_REC_ID 12345) registers for an iteration of Workplace Hazard Assessment - EHRS to be held on the first of next month at 8:30 a.m. in the Left Bank Building's EHRS Conference Room. (ITERATION_ID 98765). An LMS_REGISTRATION record is created for this registration request with REG_REC_ID 3333333. Its registration status is initially Wait-Listed. When a seat in the course iteration becomes available, the status changes to Enrolled. Then Jane is asked to attend a meeting that will be held at the same time as the course iteration. She drops the course (changing the status to Dropped). However, the meeting is cancelled, so Jane registers again for ITERATION_ID 98765. Another LMS_REGISTRATION record is created for this new registration request for USER_REC_ID 12345 and ITERATION_ID 98765, with REG_REC_ID 3333345.

Values:
39 (Enrolled)
40 (Wait-Listed; applicable to instructor-led
    courses only)
41 (Dropped)

The description of the status of the registration of the trainee (USER_REC_ID) for the course iteration (ITERATION_ID) per this registration request (REG_REC_ID). See also REGISTRATION_STATUS_CODE, REGISTRATION_STATUS_REASON, WAIT_LIST_PRIORITY, CURRENT_CRS_ITERATION_REG_FLAG, and CURRENT_COURSE_REG_FLAG.

A trainee may have multiple LMS_REGISTRATION records for the same course iteration. For example, say that Jane Smith (USER_REC_ID 12345) registers for an iteration of Workplace Hazard Assessment - EHRS to be held on the first of next month at 8:30 a.m. in the Left Bank Building's EHRS Conference Room. (ITERATION_ID 98765). An LMS_REGISTRATION record is created for this registration request with REG_REC_ID 3333333. Its registration status is initially Wait-Listed. When a seat in the course iteration becomes available, the status changes to Enrolled. Then Jane is asked to attend a meeting that will be held at the same time as the course iteration. She drops the course (changing the status to Dropped). However, the meeting is cancelled, so Jane registers again for ITERATION_ID 98765. Another LMS_REGISTRATION record is created for this new registration request for USER_REC_ID 12345 and ITERATION_ID 98765, with REG_REC_ID 3333345.

Values:
Dropped
Enrolled
Wait-Listed (applicable to instructor-led courses only)

Comments about the registration request (REG_REC_ID). See also REGISTRATION_STATUS_CODE, REGISTRATION_STATUS_DESC, WAIT_LIST_PRIORITY, CURRENT_CRS_ITERATION_REG_FLAG, and CURRENT_COURSE_REG_FLAG.

This information is not available for many records. When the value for REGISTRATION_STATUS_REASON is not null, it is stored in mixed case, and may include letters and/or numerals and/or other characters. The comments may describe any characteristic of the registration request (such as how the record for the request was created); they do not necessarily have to do with the registration status.

Note: the value for REGISTRATION_STATUS_REASON might not describe the registration request in its current state. For example, some records have a value for REGISTRATION_STATUS_REASON that begins with 'Completed' but have COURSE_COMPLETED = 'N'.

Examples: 'Dropped for new version'; 'CPR400 Curriculum Enrollment'; 'BCCD Cleanup: Drop Enrollments' The value is stored without the surrounding quotes.

Values:
List of values not available

A string indicating how much time the trainee (USER_REC_ID) has spent on taking the course iteration (ITERATION_ID) per this registration request (REG_REC_ID).

For instructor-led courses, TIME_COURSE_COMPLETED indicates how much time it took the trainee to complete the course iteration. For Web-based courses, it indicates how much time the trainee has spent on taking the course iteration so far, regardless of whether or not the trainee has completed the course iteration. (The code identifying the distribution mode is the COURSE_OBJECT.DIST_MODE where LMS_REGISTRATION.CO_REC_ID = COURSE_OBJECT.CO_REC_ID.)

TIME_COURSE_COMPLETED is null for many records. When it is not null, the value may represent the amount of time in hours (when the value includes a decimal point) or the time in hours, minutes, and seconds (when the value is in the format HH:MM:SS).

Note:

• TIME_COURSE_COMPLETED values may be formatted inconsistently. For example, some records for a particular ITERATION_ID have '0.25' for TIME_COURSE_COMPLETED, while other records for that same course iteration have '.25'.
• In some cases, TIME_COURSE_COMPLETED is null, even though COURSE_COMPLETED is 'Y'.

Examples: '1'; '.25'; '0.75'; '2.0'; '00:00:32'; '00:12:08'; '01:30:00' The value is stored without the surrounding quotes.

Values:
List of values not available

The number used within the Knowledge Link system as the unique identifier for the trainee that has registered for the course iteration (ITERATION_ID) per this registration request (REG_REC_ID). See also PENN_ID, FIRST_NAME, MIDDLE_INITIAL, and LAST_NAME.

Some tables in the Data Warehouse's Learning Management data collection store data about Knowledge Link users but do not store the users' Penn IDs. USER_REC_ID enables the LMS_REGISTRATION table to be joined to those tables.

Further information about the trainee is available in the LMS_PERSON table where LMS_REGISTRATION.USER_REC_ID = LMS_PERSON.USER_REC_ID.

Example: 10159

Values:
Refer to the LMS_PERSON table or the 
  GEN21_USER table for values.
Note:  some of the trainees in those tables
have no associated LMS_REGISTRATION records.

When the status of the registration of the trainee (USER_REC_ID) for the course iteration (ITERATION_ID) per this registration request (REG_REC_ID) is Wait-Listed, the number stored in WAIT_LIST_PRIORITY indicates what priority the trainee has for becoming enrolled in the course iteration if another trainee drops the course iteration. If WAIT_LIST_PRIORITY = 0, the trainee will become enrolled the next time someone drops the course iteration. See also REGISTRATION_STATUS_DESC.

Note:

• Wait lists are kept only for instructor-led courses. (The code identifying the distribution mode is the COURSE_OBJECT.DIST_MODE where LMS_REGISTRATION.CO_REC_ID = COURSE_OBJECT.CO_REC_ID.)
• In some records, WAIT_LIST_PRIORITY is null even though the registration status is Wait-Listed.
• In some records, WAIT_LIST_PRIORITY is not null even though the registration status is not Wait-Listed.

Examples: 0, 9

Values:
List of values not available