Page Comparison

...

Block 1 - Base SSP Configuration

external_person	Description
Purpose	Holds attributes for any user accessing or referenced by SSP. For example, supports search results, early alerting and student creation. Records in this table are periodically synchronized into the "person" table and several of its supporting tables. Both school_id and username must be unique identifiers for each record. I.e. any given school_id or username can occur at most once.
Considerations	All users who will sign into SSP or MyGPS should have a row in the table including; All students that may be added to SSP All coaches (counselors, faculty members, advisors, etc) that may be assigned as a coach for a student All faculty members who may have an Early Alert rosters Only students should have a coach_school_id and student_type_code Commonly implementers add students to external data that are "system active" so that they are available to SSP. The litmus test would be: "Could the student walk off the street and register for courses?" The username must match the username that a user will use to log into SSP
Sync'd Fields

external_term	Description
Purpose
Consideration

...