Introduction to class & roster sync jobs

 

Screen_Shot_2017-04-30_at_5.55.03_PM.png

Each Little SIS class & roster sync job includes the following basic configuration settings and preferences:

  • Job name and description
  • The Windows path / file name of the CSV source(s).
  • Mappings between the source data and fields, including the class alias field.
  • Inclusion and exclusion rules that limit which classes in the SIS data are to be synced to Classroom.
  • Preferences such as
    • Whether to overwrite teacher-entered values for fields like “Course name”
    • Whether to add / remove students
    • Notifications to teachers
    • Teacher-change handling
    • Thresholds for evaluating potential matches amongst teacher-created Classroom classes
  • Staging and sync automation preferences and schedule

Pro-tips:

  1. Setting up multiple Little SIS sync jobs is a good practice for creating a logical separation between different segments of your school or district and/or between year-long and semester-long classes, and can provide more direct control and visibility than if you simply had a single monolithic job for your whole domain.
  2. Sync jobs can be cloned within the jobs list, making it easy to preserve the majority of your configuration while changing only your class inclusion and exclusion rules. 

Sync jobs can exist in different states, and can be optionally automated to varying degrees:

  • Awaiting analysis: The job has just been created and has never run a sync analysis, or has recently had a set of staged changes run.  Clicking the "Run Sync Analysis" button will make the analysis available for "Review & Action."

  • Analyzing: The job is in the process of analyzing changes to be made in the next run.  

  • Analyzed, pending review: The job has evaluated all changes to be made in the next run. Sync jobs can be analyzed manually from the jobs list (after which the user must manually review and stage all changes), or scheduled to be analyzed automatically. Depending on your automation settings:
    • Job can be left as manual-run-only
    • or... they can be analyzed automatically on a schedule and held for review
    • or... they can be fully automated, and have changes stage and execute without approval

  • In review: You are in the process of reviewing the analysis and approving / staging actions for commit.

  • Committing staged actions: Once you have performed a review and staged all the actions you want to commit, your next step is to commit these actions to Classroom.  Note that you are not required to stage / commit all changes identified in the analysis.  E.g. you can partially review and push changes.