Versions Compared

Old Version 6

changes.mady.by.user Jason Elwood

Saved on

compared with

New Version 7

changes.mady.by.user Jason Elwood

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

external_personDescription
PurposeHolds 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?".  If so they should be available to SSP in the external data.
  • The username must match the username that a user will use to log into SSP
Sync'd Fields 
  • first_name
  • middle_name
  • last_name
  • birth_date
  • primary_email_address
  • username
  • home_phone
  • work_phone
  • cell_phone
  • address_line_1
  • address_line_2
  • city
  • state
  • zip_code
  • residency_county
  • photo_url
  • school_id
  • coach_school_id
  • office_location
  • office_hours
  • actual_start_term
  • actual_start_year
  • marital_status
  • ethnicity
  • gender
  • balance_owed
  • student_type_code
  • race_code
external_termDescription
PurposeHolds academic calendar information. Required in many locations throughout the application: Caseload Assignment, Main, Intake and MAP.
Considerations
  • term_code must be used consistently in other external database tables. 
Consideration 
  • There are no foreign keys, but the data must have integrity by used consistent values.
  • Commonly implementers don't have exact dates for future terms.  In order for MAP to render to future terms in which coaches/advisors can develop plans, future terms may need to be fabricated until the exact terms.  Future terms should be fabricated for up to 5 years after the current academic year.  The dates should be arbitrary and won’t affect SSP if they are changed when the new dates are officially defined.  The following  are sample dates that can be used for the fabricated terms.
    • Fall: 8/15-12/15
    • Spring: 1/5-5/10
    • Summer: 5/15-8/1
  • registration_start_date and registration_end_date are only used for MAP

 

SSP Configuration Guide

  1. Install Settings
  2. General Settings
  3. Begin collecting referrals for counseling reference guide
  4. Begin collecting Journal track-step-detail

...