The Sync Method supports the pulling of student and/or class information from the Clever integration tool, the PowerSchool Student Information System (SIS), or the RIC One API, and automatically loading the information into Hapara daily. The configuration specified in the "Sync Configuration" page determines how the Sync Load Method works. It also impacts the format of the data that you will need to load.
If Sync is turned on, then the Sync Configuration tab is not editable. You must turn Sync off before you can edit the page.
The Academic Year Suffix is used by the Data Loader to simplify data management, and maintain a yearly class structure.
For Northern Hemisphere customers from "-1617" to "-1718".
This section specifies whether you load data from the Clever integration tool, the PowerSchool SIS, or the RIC One API. These are the only three sources currently supported by this method.
This Id is generated by Clever for your district/school and should have been provided to you.
These details are generated by PowerSchool for your district/school and should have been provided to you.
The section also contains a "Test" button allowing the access to PowerSchool to be tested.
This section specifies whether you load Student data, Class data or both. You must select at least one of the options.
During initial testing you may decide to only synchronize Classes. But in day to day operation, almost all customers synchronize Students daily (because Student data changes often).
NB: For RIC One integration, this section is hidden. The first option below is applied - the class email is used for the class name.
The Class Names generated here must be unique across the school. If your CourseNames are not unique, choosing an option with the suffix SISId will ensure the Class Names calculated here are unique.
If some of the fields, in the option you choose above, are not provided by Clever/PowerSchool then the Class will not be uploaded. For example, if you choose the option "CourseName-Period-SISId" and Clever/PowerSchool provides a blank "Period" value, then the associated class will not be imported.
Teachers can assign a "nickname" to each of their classes in Hapara via the Manage Classes page.
Student folders are Google Drive folders that can be created for each student in a class. The folders are shared to the student and the teacher, so the work here is not visible to other students unless explicitly shared.
The Hapara Dashboard product supports students having zero to many Subject Folders per Student per Class. This setting states how folders will be used with Classes loaded via the Sync Method.
Options 1 to 4 are commonly used in secondary schools where a Class represents a combination of a subject (e.g. English) and a student cohort (e.g. Grade8B).
Option 5 is commonly used in primary schools where a Class represents a student cohort (e.g. Grade2c) and the teacher teaches multiple subjects to that class. You specify the folder names that will be used for all classes (e.g. English,Math,Art,Other) in this section.
Option 6 is not recommended for customers who are using the Hapara Dashboard product.
Option 6 is recommended for customers who are only using Workspace and Highlights.
Also refer to the Naming Subject Folders - Recommendations article.
You can also specify a suffix that will be added to the end of all student subject folder names - both in each Teacher's Google Drive and each Student's Google Drive. Suffixes help make the folder names unique across all students. This suffix doesn't help students (as they only see their own folders). This suffix helps teachers who see student subject folders in Google Drive (as the folder names they see will all be different).
Option 2 is the most commonly used.
If you select Option 4 the portion of the student email address before the "@" symbol will be used as the suffix.
Warning: Once the suffix is added to the folder names, the suffix cannot be removed or changed. So it is important to get this setting right.
Note: If you have purchased an "unprovisioned" Hapara product (such as Reseller Highlights) then this section will be hidden.
The Hapara Dashboard product supports teachers viewing student's posts and comments on Google sites. This setting states how Student Sites will be used with Classes loaded via the Sync Method.
The Hapara Dashboard product supports teachers viewing student's Google blogs. This setting state how Student Blogs will be used with Classes loaded via the Sync Method.
Also refer to the Setting Up The Blogger Tab article.
Note: Hapara does not create (or provision) Blogs. Instead the Hapara Dashboard shows existing Blogs that match the option chosen above.
Hapara can create a Google Class Calendar for each class. This setting states how Calendars will be used with Classes loaded via the Sync Method.
Option 2 is the most commonly used. This means the Calendar is given the same name as the Class.
Option 2 will create a Google Calendar for the Class (if the Calendar does not already exist).
Admins and teachers who can view the class.
Option 1 is the most commonly used.
Also refer to the Setting up the Gmail Viewer article.
Note: If the Gmail Viewer has been disabled, then this section will be hidden. The Gmail Viewer is enabled / disabled via the Hapara Admin Console > Modules > Gmail Viewer page.
You can specify people who will be emailed after a (successful or unsuccessful) automated daily Sync has occurred. Multiple people can be specified e.g. "person1@myschool.org,person2@myschool.org".
We recommend that this field be filled in. Irrespective of whether this field filled in, the results of every Sync can be viewed on the Status page.
Each person listed here will receive two emails per automated daily Sync - that is two emails per day. The first email shows the results of the extraction of data from your SIS. The second email shows the results of the completed load.