.. index:: tbl1_People =========== tbl1_People =========== .. default-role:: doc :Description: This table is one of the centerpieces of Solutions and has many related tables. It holds all of the data for people associated with the department. :Relation: one-to-many with `tbl1_AppointmentHistory` table with tbl1_People.PersonID = tbl1_AppointmentHistory.appt_PersonID one-to-one with `tbl1_Appointments` table with tbl1_People.PersonID = tbl1_Appointments.appt_PersonID one-to-many with `tbl1_Instructors_ClassesTaught` where tbl1_People.PersonID = tbl1_Instructors_ClassesTaught.*_PersonID (several field relationships possible) one-to-many with `tbl1_People_docs` where tbl1_People.PersonID = tbl1_People_docs.PersonID one-to-many with `tbl1_Person_History` where tbl1_People.PersonID = tbl1_Person_History.PersonID one-to-many with `tbl1_Schedule_Data` where tbl1_People.PersonID = tbl1_Schedule_Data.*PersonN_id (6 fields available) one-to-many with `tbl1_schedule_inbound_from_css` where tbl1_People.PersonID = tbl1_schedule_inbound_from_css.person1_id one-to-many with `Tbl1_SIRS_data` where tbl1_People.PersonID = Tbl1_SIRS_data.PersonID :Source: manually entered department data Columns ======= **PersonID** ``int(11) NOT NULL`` :Description: main identifier for a person, used throughout Solutions :Footnote: We have some "special purpose" people records in this table, all with negative PersonID values. These "people" can be selected in the instructor field for a course to indicate the specific situation: "STAFF, TBD" for 'to be determined' (id = -5) "STAFF" for a generic unspecified staff assignement (id = -4) "NON-PRINT" for non-print sections (id = -3) "CANCELED" for canceled sections (id = -2) "OPEN" for open sections (id = -1) It might be better to obsolete these usages and instead have checkbox fields to indicate these section statuses; however this has been in the Solutions design from the beginning and it will be tricky to change in current solutions-access incarnation :Options: ``display="true", null="true", search="false", type=""`` **EmployeeID** ``varchar(40) DEFAULT NULL`` :Description: 8-digit number, sometimes called Payroll ID :Options: ``display="true", null="true", search="false", type=""`` **LastName** ``varchar(255) DEFAULT NULL`` :Description: Last name :Options: ``display="true", null="true", search="false", type=""`` **FirstName** ``varchar(255) DEFAULT NULL`` :Description: First name :Options: ``display="true", null="true", search="false", type=""`` **FullName** ``varchar(255) DEFAULT NULL`` :Description: Full name in last, first format :Options: ``display="true", null="true", search="false", type=""`` **Email** ``varchar(255) DEFAULT NULL`` :Description: Rutgers Email address :Options: ``display="true", null="true", search="false", type=""`` **office** ``varchar(255) DEFAULT NULL`` :Description: Office #, should correspond to office in the `tbl1_Offices` table :Options: ``display="true", null="true", search="false", type=""`` **extension** ``varchar(255) DEFAULT NULL`` :Description: 5-digit phone extension (connected to office) :Options: ``display="true", null="true", search="false", type=""`` **address** ``varchar(255) DEFAULT NULL`` :Description: address :Options: ``display="true", null="true", search="false", type=""`` **phone** ``varchar(255) DEFAULT NULL`` :Description: Contact phone # (not Rutgers phone) :Options: ``display="true", null="true", search="false", type=""`` **spouse** ``varchar(50) DEFAULT NULL`` :Description: Spouse first name :Options: ``display="true", null="true", search="false", type=""`` **Notes** ``mediumtext DEFAULT NULL`` :Description: Notes :Options: ``display="true", null="true", search="false", type=""`` **CommuteMinutes** ``int(11) DEFAULT NULL`` :Description: How long a commute does person have to get to office? :Options: ``display="true", null="true", search="false", type=""`` **USCitizen** ``bit(1) DEFAULT NULL`` :Description: True if person is a US Citizen :Options: ``display="true", null="true", search="false", type=""`` **VisaType** ``varchar(50) DEFAULT NULL`` :Description: Visa type, if appropriate :Options: ``display="true", null="true", search="false", type=""`` **VisaExpiration** ``datetime DEFAULT NULL`` :Description: zVisa expiration date :Options: ``display="true", null="true", search="false", type=""`` **NetID** ``varchar(10) DEFAULT NULL`` :Description: person's netid :Footnote: We have occassions where a peson needs to be added to Solutions before they have a netid. In these cases, the value "TBD" (to be determined) can be entered in this field :Options: ``display="true", null="true", search="false", type=""`` **DateAdded** ``datetime DEFAULT NULL`` :Description: Date person was added to Solutions :Options: ``display="true", null="true", search="false", type=""`` **MostRecentRole** ``varchar(255) DEFAULT NULL`` :Footnote: this is automatically set when person is added :Options: ``display="true", null="true", search="false", type=""`` **phone_cell** ``varchar(255) DEFAULT NULL`` :Description: cell phone :Options: ``display="true", null="true", search="false", type=""`` **email_personal** ``varchar(255) DEFAULT NULL`` :Description: Email address that is not a Rutgers internal email :Options: ``display="true", null="true", search="false", type=""`` **title** ``varchar(255) DEFAULT NULL`` :Description: Person's job title, should correspond to a title from `tbl1_Titles` category :Options: ``display="true", null="true", search="false", type=""`` **employment_start_date** ``datetime DEFAULT NULL`` :Description: Employment Start Date :Options: ``display="true", null="true", search="false", type=""`` **employment_end_date** ``datetime DEFAULT NULL`` :Description: Employment End Date (if applicable) :Options: ``display="true", null="true", search="false", type=""`` **inactive** ``bit(1) DEFAULT NULL`` :Description: TRUE if person should be considered 'inactive' :Footnote: This is an area of Solutions that should be analyzed and possibly changed. There is confusion as to when a person should be considered "Inactive". For example, if a person retires but we still hear from them on occasion, as opposed to someone who is deceased. Also, in some reports inactive people are excluded; however, there are ambiguous situations, for example a person on sabbatical. Even though they are away, we would want them to get a teaching survey if they will be back to teach that semester. This suggests a more complete design above and beyond simply a true/false value in this field. :Options: ``display="true", null="true", search="false", type=""`` **last_updated** ``datetime DEFAULT NULL`` :Description: when was person record last updated :Footnote: automtaically set by Solutions :Options: ``display="true", null="true", search="false", type=""`` **title2** ``varchar(255) DEFAULT NULL`` :Description: Secondary title, if applicable :Options: ``display="true", null="true", search="false", type=""`` **LastNameKey** ``varchar(25) DEFAULT NULL`` :Description: Algorithmically derived soundex key on last name, which enables matches on phonetic lookups :Footnote: this is automatically derived by Solutions when record is saved :Options: ``display="true", null="true", search="false", type=""`` **FirstNameKey** ``varchar(25) DEFAULT NULL`` :Description: Algorithmically derived soundex key on first name, which enables matches on phonetic lookups :Footnote: this is automatically derived by Solutions when record is saved :Options: ``display="true", null="true", search="false", type=""`` **ruid** ``varchar(255) DEFAULT NULL`` :Options: ``display="true", null="true", search="false", type=""`` **image_file** ``varchar(255) DEFAULT NULL`` :Description: file name of image of person :Footnote: this file is assumed to be in a subfolder IMAGES under the share path (MATHDATA) :Options: ``display="true", null="true", search="false", type=""`` **ShowOnWeb** ``bit(1) DEFAULT NULL`` :Description: Obsolete? :Footnote: This corresponds to a "show on web" checkbox on people window, but I am pretty sure it is not being used for anything anymore :Options: ``display="true", null="true", search="false", type=""`` **Phd_year** ``int(11) DEFAULT NULL`` :Description: Year person received Phd :Options: ``display="true", null="true", search="false", type=""`` **DOB** ``datetime DEFAULT NULL`` :Description: Date of Birth :Options: ``display="true", null="true", search="false", type=""`` **gender** ``varchar(20) DEFAULT NULL`` :Description: M, F or blank :Options: ``display="true", null="true", search="false", type=""`` **name_title** ``varchar(20) DEFAULT NULL`` :Description: Dr., Mr., Mrs, etc :Options: ``display="true", null="true", search="false", type=""`` **URL** ``varchar(255) DEFAULT NULL`` :Description: Person's personal URL, if they have one :Options: ``display="true", null="true", search="false", type=""`` **NotesH** ``mediumtext DEFAULT NULL`` :Description: Obsolete? was for hidden notes originally :Options: ``display="true", null="true", search="false", type=""`` **KeyNum** ``varchar(40) DEFAULT NULL`` :Description: Key Number (corresponds to office #) :Options: ``display="true", null="true", search="false", type=""`` **StatusCode** ``smallint(6) DEFAULT NULL`` :Description: numeric code corresponding to person's status. See `tbl1_Statuses` table :Footnote: This is related to the footnote with the inactive column. Solutions handling of active/inactive people and incorporation of related status codes and events is an evolving area. :Options: ``display="true", null="true", search="false", type=""`` **research_interest** ``mediumtext DEFAULT NULL`` :Description: Person's research interest :Options: ``display="true", null="true", search="false", type=""`` **location** ``varchar(60) DEFAULT NULL`` :Description: Where does person work? (if not local to Math Dept) :Options: ``display="true", null="true", search="false", type=""`` **title_category_web** ``varchar(25) DEFAULT NULL`` :Description: This is main category driver for a person, used throughout Solutions. Category is one of the ones listed in the `tbl1_Categories` table :Options: ``display="true", null="true", search="false", type=""`` **JobCode** ``varchar(10) DEFAULT NULL`` :Description: 5-digit job code :Options: ``display="true", null="true", search="false", type=""`` **PhD_from** ``varchar(100) DEFAULT NULL`` :Description: Where did person get their Phd from? :Options: ``display="true", null="true", search="false", type=""`` **gs_type** ``varchar(15) DEFAULT NULL`` :Description: Type of graduate student, TA or GA :Footnote: This was beginning foundations of an unfinished feature to incorporate graduate lines into Solutions, and also to determine which graduate students need to teach. It got complicated because grad students' statuses and types change frequently (contact: Katie Guarino) :Options: ``display="true", null="true", search="false", type=""`` **gs_start_semester** ``varchar(15) DEFAULT NULL`` :Description: Grad Student Start Semester (not used?) :Options: ``display="true", null="true", search="false", type=""`` **gs_start_year** ``smallint(6) DEFAULT NULL`` :Description: Grad Student start year :Options: ``display="true", null="true", search="false", type=""`` **title_category_web2** ``varchar(25) DEFAULT NULL`` :Options: ``display="true", null="true", search="false", type=""`` **PerCreditRate** ``double DEFAULT NULL`` :Description: For PTLs, pay rate per credit. :Footnote: This might be obsolete. It was tied to the PTL Payroll function which is not actively used by anyone :Options: ``display="true", null="true", search="false", type=""`` **TenureTrack** ``bit(1) DEFAULT NULL`` :Description: True if person is tenure track :Options: ``display="true", null="true", search="false", type=""`` **grad_faculty_type** ``varchar(25) DEFAULT NULL`` *For Graduate Faculty, what type? Either: No, Full, Adjunct or Associate* :Description: TR :Options: ``display="true", null="true", search="false", type=""`` **specialty** ``varchar(30) DEFAULT NULL`` :Description: Graduate Faculty's specialty :Options: ``display="true", null="true", search="false", type=""`` **office_hours** ``mediumtext DEFAULT NULL`` :Description: Office Hours :Footnote: Office hours are viewable but not directly updatable in Solutions interface. Current procedures is that instructors enter their office hours directly into Joomla. A Solutions export/import from Joomla (which I am not sure is still being used by office staff) updates the values in Solutions. :Options: ``display="true", null="true", search="false", type=""`` **last_change** ``timestamp NOT NULL DEFAULT current_timestamp() ON UPDATE current_timestamp()`` :Options: ``display="true", null="true", search="false", type=""``