Penn Computing

University of Pennsylvania
Penn Computing << go backback
LMS_PERSON Table - Data Element Index    Tables and Data Elements   Learning Management Home   Data Warehouse Home

LMS_PERSON Table

DWLMS Schema

Explanation
Contains the most current available information about users of the Knowledge Link and/or Penn Profiler systems. There is one record per user, which includes the person's name, Penn Community status, unique identifiers (Penn ID, etc.), e-mail address, and primary administrative group in Knowledge Link. LMS_PERSON also provides information about the user’s primary University job appointment and/or University of Pennsylvania Health System job. For Penn Profiler users, it tracks the e-mail address of the person’s supervisor, along with information on when the user was last given the assignment to complete the Profiler survey, when the user last edited the survey, and when the user last completed it.

The Data Warehouse's Learning Management data collection also includes a copy of Knowledge Link's GEN21_USER table and its companion, the CUSTOM_DATA table. The LMS_PERSON table includes data from both of these tables, plus other data to support ad hoc reporting.

Common Uses

  • Retrieving the names and e-mail addresses of people that have records in other tables. ("I'm generating a list of people who are qualified to teach course X, and I need their names and e-mail addresses.")
  • Checking the e-mail address of a person's supervisor. ("I've gotten e-mail from Penn Profiler asking me to use BEN Reports to check my staff's compliance with training requirements. John Doe is on my staff, but he's not listed in my Current Required Course Status, by Supervisor report. What is on file as his SUPERVISOR_EMAIL address?")
  • Monitoring people's Penn Profiler status. ("Who last completed the Profiler survey over a year ago?")
  • Generating reports that select records based on the person's Penn Community status, job information, or primary administrative group. ("When did the active administrative assistants in the Graduate School of Education last complete the Profiler survey?")
Primary Key Indexed Data Elements Related Tables
PENN_ID
ASSIGNMENT_FEED_ELIGIBLE
FIRST_NAME
NAME
PENN_ID
TRAINEE_ORG_BU_ID
TRAINEE_ORG_BU_NAME
TRAINEE_ORG_BU_NUMBER
CUSTOM_DATA
GEN21_USER
KNODE
KNODE_CRS_JOIN
KNODE_USER_JOIN
LMS_BUSINESS_UNIT_GROUP
LMS_COMPLIANCE
LMS_COURSE_ITER_INSTRUCTOR LMS_CURRENT_CRS_ITER_REG_INSTR LMS_CURRENT_TRAINEE_CRS_STATUS LMS_REGISTRATION LMS_STAFF_QUAL LMS_TRAINEE_BU_COURSE_ASSIGN LMS_TRAINEE_COURSE_ASSIGN LMS_TRAINEE_COURSE_COMPLIANCE PROFILER_ASSIGNMENTS PROFILER_USER_ANSWER PROFILER_USER_QUESTIONNAIRE REGISTRATION UPHS_COST_CENTER UPHS_RAW_DATA UPHS_USER_ENTITY USER_COURSES


Cautions

  • The LMS_PERSON table stores only current information on Knowledge Link and Profiler users. For example, suppose that a record was created in 2005 for a man named John Doe, whose Penn ID is 12345678. In 2008, this man changed his name to Harry Smith. There is no way to tell from the LMS_PERSON table that Harry Smith, the man whose PennID is 12345678, was once named John Doe.
  • The LMS_PERSON table has one record per user of the Knowledge Link and/or Penn Profiler systems. The PENN_ID is used in LMS_PERSON as the unique identifier of the user. This facilitates joining the LMS_PERSON table with other Data Warehouse tables, both in the Learning Management data collection and in other data collections.
    • Most users are persons: University of Pennsylvania Health System (UPHS) employees, University employees, University students, or 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). For these users, PENN_ID is an 8-digit identification number assigned to the person by the Penn Community system. No two persons have the same Penn ID.
    • Some LMS_PERSON records store information for Knowledge Link administrator user IDs. For those records, PENN_ID is not really a Penn ID, but a code that begins with a letter and is unique in the LMS_PERSON table.
  • There are several data elements that may store a unique identifier for the person.
    • The recommended one is PENN_ID. It always has a non-null value.
    • Other unique identifiers for a person are PENNKEY (which always has a non-null value) and USER_REC_ID, HIBERNATE_ID, and UPHS_EMPLOYEE_NUMBER (any of which may be null).
    • 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_PERSON table to be joined to those tables.
  • Most people with records in LMS_PERSON use both Knowledge Link and Penn Profiler. However, some are users of one system but not the other. EXTRACT_SOURCE indicates whether the person uses both systems ('B'), Knowledge Link only ('L'), or Profiler only ('P').
    • If EXTRACT_SOURCE is 'P', the data elements for information from Knowledge Link will be null. These data elements are:
      • DEPT_START_DATE
      • EMAIL_ADDRESS
      • FIRST_NAME
      • FIRST_NAME_AS_IS
      • LAST_NAME
      • LAST_NAME_AS_IS
      • LMS_DATE_CREATED
      • LMS_DATE_MODIFIED
      • MIDDLE_INITIAL
      • MIDDLE_NAME_AS_IS
      • PRIMARY_BUSINESS_UNIT_ID
      • PRIMARY_BUSINESS_UNIT_NAME
      • PRIMARY_BUSINESS_UNIT_NUMBER
      • REMARKS
      • TRAINEE_ORG_BU_ID
      • TRAINEE_ORG_BU_NAME
      • TRAINEE_ORG_BU_NUMBER
      • UPHS_COMPANY_NUMBER
      • UPHS_DEPARTMENT_CODE
      • UPHS_DEPARTMENT_NAME
      • UPHS_DEPARTMENT_NAME_AS_IS
      • UPHS_EMPLOYEE_NUMBER
      • UPHS_ENTITY_CODE
      • UPHS_JOB_CODE
      • UPHS_JOB_TITLE
      • USER_REC_ID
    • If EXTRACT_SOURCE is 'L', the data elements for information from the Penn Profiler system will be null. These data elements are:
      • ASSIGNMENT_FEED_ELIGIBLE (the value will be '.' rather than null)
      • DATE_LAST_ASSIGNED_TO_PROFILER
      • FULL_NAME_AS_IS
      • HIBERNATE_ID
      • LAST_CERTIFICATION_DATE
      • LAST_NOTIFICATION
      • NOTIFICATION_EMAIL
      • NOTIFICATION_REQUIRED (the value will be '.' rather than null)
      • PROFILER_DATE_LAST_EDITED
      • SUPERVISOR_EMAIL
      • UNIV_PRIMARY_APPT_JOB_CLASS
      • UNIV_PRIMARY_APPT_ORG
  • There are several data elements that may store the person's name.
    • The recommended one is NAME, which stores the person's name in upper case, in the format LASTNAME, FIRSTNAME M. The last name and first name may be separated by a comma and a space, or just by a comma, and the NAME value might or might not end with a period.
    • Other data elements for the person's name are FIRST_NAME, MIDDLE_INITIAL, LAST_NAME, FIRST_NAME_AS_IS, MIDDLE_NAME_AS_IS, LAST_NAME_AS_IS, and FULL_NAME_AS_IS.
  • PENN_COMMUNITY_MEMBER_STATUS has a somewhat misleading name. It indicates whether the person is an active ('A') or inactive ('I') user of the Knowledge Link and/or Penn Profiler systems. An active user is an active member of the Penn Community that has at least one active affiliation that is relevant to Knowledge Link. For further information, see the data element documentation for PENN_COMMUNITY_MEMBER_STATUS.
  • When reporting on a person's primary administrative group in Knowledge Link, decide whether you want to use the person's primary business unit or Trainee Org./BU.
    • The person's primary business unit is the person's primary Knowledge Position (KP), the business unit to which the person is primarily assigned in Knowledge Link.
      • For more information about the person's primary business unit, see the data element documentation for PRIMARY_BUSINESS_UNIT_ID.
      • PRIMARY_BUSINESS_UNIT_ID and PRIMARY_BUSINESS_UNIT_NUMBER each are unique identifiers of the person's primary business unit. PRIMARY_BUSINESS_UNIT_NAME is also available, but it is not necessarily unique.
    • The person's Trainee Org./BU the business unit for the primary administrative group to which the person belongs. If the person’s primary business unit corresponds to a departmental trainee group of UPHS employees, the person’s Trainee Org./BU is the same as his or her primary business unit. However, in many cases, the person’s primary business unit is a business unit that includes only that person. In those cases, the person’s Trainee Org./BU is business unit that is the parent of the person’s primary business unit—one step above that business unit in the business unit hierarchy.
      • For more information about the person's Trainee Org./BU, see the data element documentation for TRAINEE_ORG_BU_ID.
      • TRAINEE_ORG_BU_ID and TRAINEE_ORG_BU_NUMBER each are unique identifiers of the person's Trainee Org./BU. TRAINEE_ORG_BU_NAME is also available, but it is not necessarily unique.
  • E-mail addresses may be found in EMAIL_ADDRESS, NOTIFICATION_EMAIL, and SUPERVISOR_EMAIL.
    • The values in these data elements are not necessarily valid e-mail addresses.
    • Because most people with records in LMS_PERSON are Knowledge Link users, EMAIL_ADDRESS is the data element recommended for use in queries that involve a person's e-mail address. However, if EMAIL_ADDRESS is null, NOTIFICATION_EMAIL (from Penn Profiler) might store the person's e-mail address.
    • LMS_PERSON records for some people (such as housekeeping staff) might have a value for SUPERVISOR_EMAIL even though they have no value for EMAIL_ADDRESS and/or NOTIFICATION_EMAIL.
  • LMS_PERSON stores information about the user’s primary University job appointment or University of Pennsylvania Health System (UPHS) job. If the person is both a University employee and a UPHS employee, information about both jobs is stored.
    • Data elements pertaining to the user’s primary University job appointment:
      • UNIV_PRIMARY_APPT_JOB_CLASS
      • UNIV_PRIMARY_APPT_ORG
    • Data elements pertaining to the user’s UPHS job:
      • UPHS_COMPANY_NUMBER
      • UPHS_DEPARTMENT_CODE
      • UPHS_DEPARTMENT_NAME
      • UPHS_DEPARTMENT_NAME_AS_IS
      • UPHS_EMPLOYEE_NUMBER
      • UPHS_ENTITY_CODE
      • UPHS_JOB_CODE
      • UPHS_JOB_TITLE
  • DEPT_START_DATE stores the date the person was hired to work in his or her current job department, or the date the person transferred into his or her current job department.
    • One of the tests for determining whether a particular person is grandfathered for a given mandatory course assignment is to compare the person's DEPT_START_DATE with the effective date of the course assignment. For more information on grandfathering, see the Caution regarding the GRANDFATHERING_VALUE in the documentation for the COURSE_OBJECT table.
    • Currently, DEPT_START_DATE is used only for employees of the University of Pennsylvania Health System (UPHS), and indicates the most recent date when the person began working in his or her current UPHS department. However, DEPT_START_DATE is null for some UPHS employees. It is also null for people that are not UPHS employees. Someone who is both a UPHS employee and a University employee might or might not have a non-null DEPT_START_DATE.
  • NOTIFICATION_EMAIL, NOTIFICATION_REQUIRED, and LAST_NOTIFICATION have nothing to do with Knowledge Link's E-mail Notifications function. The Penn Profiler system uses this information when it notifies users that they need to take (or re-take) the survey, and when it informs them about the courses that Profiler assigned to them as mandatory courses.
  • Although LMS_PERSON can be joined to KNODE_CRS_JOIN where the PRIMARY_BUSINESS_UNIT_NUMBER or TRAINEE_ORG_BU_NUMBER matches the KNODE_ID, joining these tables is not recommended. Trainees fall under more business units than just their primary or trainee org. business unit; using those business units to look up course assignments in KNODE_CRS_JOIN could yield incomplete results.

Source

Knowledge Link and Penn Profiler.

Knowledge Link is the learning management system used by the University and by the University of Pennsylvania Health System (UPHS) since March, 2005. It enables authorized administrators to schedule training courses, assign resources to courses, assign groups of trainees to courses, and to create online courses. It enables trainees to find out what courses have been assigned to them, to register for those courses (whether those courses are on-line or instructor-led), to take on-line courses, and to provide feedback via course evaluations. Knowledge Link was first used to track information on training required by regulation, but it now tracks information on a variety of training courses.

The Penn Profiler (Profiler) is a system that adds value to Knowledge Link by providing a way to fully and proactively identify a person’s current training requirements and to record them in Knowledge Link. Used by the University since April, 2008, Profiler enables authorized users to contribute content for inclusion in a survey that will be taken by prospective trainees. The survey content includes questions on a person’s academic activities and job responsibilities, and information on the training courses that are required for those doing certain kinds of work. Based on a person’s responses to the survey, Profiler determines the training courses that the person is currently required to take, and feeds the course assignments to Knowledge Link.

LMS_PERSON Table - Data Element Index    Tables and Data Elements   Learning Management Home   Data Warehouse Home

Questions about this page? Email us at da-staff@isc.upenn.edu

Information Systems and Computing
University of Pennsylvania
Information Systems and Computing, University of Pennsylvania