If districts choose to use Studies Weekly to roster their accounts, they can create and manage user accounts for teachers and students district-wide through a variety of automated processes. Studies Weekly is also able to collect roster data through third-party applications, such as ClassLink or Clever.
Each user included in the data that is sent through the roster connection will be given a Studies Weekly Online account and will be assigned either a district admin, teacher, co-teacher, or student role. The users will also be assigned to the classroom(s) specified in the roster data.
ClassLink is one of our third-party applications that has very little maintenance and setup. Once the connection is established, Studies Weekly Online accounts will be created based on the data shared from ClassLink. Studies Weekly can import your school's roster directly from ClassLink to synchronize your schools' user accounts each night. Your district will be able to choose what data is shared with Studies Weekly through ClassLink. The users and classrooms that were shared will be created in Studies Weekly Online. They will be able to log in to their ClassLink account and find the Studies Weekly application to launch their Studies Weekly Online account.
To set up this integration with ClassLink, locate the Studies Weekly application in ClassLink and begin sharing data with Studies Weekly. Email firstname.lastname@example.org to inform them you’d like to utilize ClassLink and that you have started sharing data with Studies Weekly. They will then inform you of the next steps.
Clever is another third-party application that integrates with Studies Weekly. A connection with Clever requires your district to request to connect with Studies Weekly by locating the Studies Weekly application in Clever’s application library and requesting to connect. Once the connection is approved by someone on Studies Weekly’s team, your district can begin sharing data with us. You’ll want to ensure your district has purchased Studies Weekly publications so your users can gain access through their Clever portal.
After your connection is approved and the launch date is established, Studies Weekly will create user accounts. Users will be able to log in to their Clever account and find the Studies Weekly application to launch their Studies Weekly Online account.
If you add schools to the roster data at any point during your integration with Studies Weekly, the change will need to be approved by someone on Studies Weekly’s rostering team.
To qualify for third-party integration, the size of your Studies Weekly order must average at least $2,000 per school, each school year.
Once your users are rostered, publications will be auto-assigned based on data provided in the roster. For example, if you provide the class’s grade level in the data, publications will be assigned to that classroom automatically for that grade level. If grade data is not provided, no publications will be auto-assigned and teachers will need to manually add publications to their classrooms. Teachers can add or remove publications by following these instructions.
Studies Weekly can receive your district's roster data and information through an API connection that is compatible with OneRoster. If your student information system (SIS) is OneRoster compatible, Studies Weekly will provide a way for your district to send us your credentials to connect with us directly.
ClassLink is OneRoster certified, which means we integrate well with ClassLink through API. ClassLink provides a launchpad for your users to access Studies Weekly while only having to login to one place to access your Studies Weekly publication(s).
OneRoster API Integration
Studies Weekly can receive your district's roster data and information through an API connection, which means you’ll be sending data from your SIS directly to Studies Weekly. We currently have support for an API connection that follows OneRoster specifications. To set up an API connection, send an email to email@example.com to let them know what Student Information System (SIS) you have and that you’d like to connect through OneRoster API. Studies Weekly will provide a way for your district to send us your credentials to complete the API connection.
If your SIS is not able to filter down the data you send us, the OneRoster CSV option below may be a better solution for you.
CSV File Upload Integration
Studies Weekly is compatible with two CSV file formats to give your district the ability to choose what will best meet your needs. Studies Weekly is able to accept OneRoster formatted files or Studies Weekly formatted files. You can choose the frequency in which files are uploaded. Regardless of when files are uploaded, files are processed each night to provide you the latest information as soon as the next morning.
OneRoster Formatted Files
Studies Weekly is able to accept OneRoster CSV files through Secure File Transfer Protocol (SFTP). You can choose what data you send us by exporting the required files from your SIS with the required fields selected. Studies Weekly will provide you with SFTP credentials so you can access our server to upload files as needed. Once files are uploaded and the nightly sync occurs, your users will have accounts created.
See the list of Mandatory CSVs and important notes here on the ClassLink website.
Studies Weekly Formatted Files
If your district is not able to export OneRoster formatted files or if you’d prefer to personally manage the user data, Studies Weekly has its own format in which you can provide CSV files.
You will be assigned a district admin account where you can upload your files for validating and file processing. Files will first be validated, which just means they’ll be scanned for any breaks in your data. The files will then be processed later that night during the nightly sync. If you reach out to firstname.lastname@example.org during the setup, we can manually push the sync to ensure everything is working so you don’t have to wait to know if the data is processing accurately.
After the initial setup and once you have a successful sync, Studies Weekly can provide you with SFTP credentials to access our server and upload files as often as you’d like.
This file is used to provide us with each school in your district that will be using Studies Weekly. Each school using Studies Weekly must be listed in this file in order for accounts to be created and for your users to see the publications your district has purchased.
This file is used to create user accounts for anyone you’d like to have the teacher role on their account. We will use the teacher's email address as their username and they will be able to use the reset password link to set up their account for the first time. If you’d prefer, we have the ability to send each new user an email with their login information.
This file is used to create user accounts for anyone that needs the student role on their account. How you set their username and password will be dependent on which method you would like your students to login with.
For Google SSO, this file will contain four columns: student name, student email, student ID and username. The Google hosted email address must be assigned in the username column.
For custom usernames and passwords, this file will contain five columns: student name, student email, student ID, username, password*.
*Each password must be at least 5 characters and include a number. If no password is provided, please include the header in the file, and we will auto generate one for you.
This file is used to create all of the classrooms at any and all schools within your district. This is also where you will assign the main teacher to their classroom. Additional teachers can be assigned to a class in the teacher_class.csv file. In order for your teachers to have a classroom online, a classroom needs to be declared in this file.
This file is used to assign students to classrooms. If you find that one of your teachers is missing a student, you can check this file to ensure they are assigned to their teacher accordingly.
This file is used to assign a co-teacher or a second teacher to a classroom. The teachers added to this file will have the same abilities as the main teacher. The only ability the main teacher will have that the secondary teacher will not is deleting a classroom. The main teacher will be assigned in the classes.csv file.
After all the files have been created, it is recommended that you maintain a ‘final file’ of each on your desktop. As changes happen throughout the year, you will add to or remove from the files.
Whatever data is in your files will be reflected online. If you remove any users from the files and upload a different file, users will be removed and added accordingly.
Once your users are rostered, teachers will need to manually add publications to their classrooms. Teachers can add additional publications to their classroom if needed.
All column headers and filenames MUST be identical to those listed in the OneRoster specifications. All columns listed in the specifications are also required. If a column indicates it is not required, the column itself is required, but the data for each row can be blank.
All CSV files MUST be UTF-8 encoded or the process will not be successful.
For information about the SFTP server, to request SFTP credentials, to request district admin credentials, or if anything is not working as expected, please contact our rostering support team at email@example.com.