In compliance with the IMS Global OneRoster v1.0 data interchange format, the following seven files/data tables are required. Note that each data table is a .csv (Comma Separated Value) file.
- orgs.csv – The orgs data table describes the organizations to be included in the roster information. Typically, the organizations are schools or districts. Each row should be one organization (school or district). Note: Quaver does not collect this information but requires the header row for the table to comply with the OneRoster format.
- users.csv – The users data table describes the various users of the organization (teachers, students, administrators, IT staff). It includes the actual names of the users, as well as their email addresses, login names, and other information. Each row represents one user.
- academicSessions.csv – The academic sessions data table describes the quarters, semesters, or terms during which classes will be taught. Each row represents a term with a title and start and end dates.
- courses.csv – The courses data table establishes the course to which multiple classes may belong. Each row represents a course such as “General Music.” Note: Quaver does not collect this information but requires the header row for the table to comply with the OneRoster format.
- classes.csv – The classes data table lists the classes taught for each course, including the grade level and the title of the class. Each row represents a class, for example, “Music, 5th period.”
- enrollments.csv – The enrollments data table assigns users to their various classes. Each row designates one user belonging to one class.
- demographics.csv – The demographics data table describes the sex, ethnicity, birth date and other information of each user. Note: Quaver does not collect this information but requires the header row for the table to comply with the OneRoster format.
The format is a model onto which your organization’s data can be mapped. Do not worry if your data structure does not exactly conform to the model! The detailed specifications for each file clearly explain the information Quaver requires to create class rosters, which is a small fraction of what the format can accommodate. We will gladly help you with any questions you have about how to best map your data.
While Quaver would prefer to receive data tables that include only information related to music classes, we do not require districts to filter that data before being sent to us. Therefore, we do not create Quaver classes for a teacher in our system until both of the following are true:
The teacher has logged into Quaver via SSO using an account that can be matched to a teacher submitted in the OneRoster users.csv file.
The teacher has registered a valid Quaver content access code to their Quaver account. The code activates all relevant content for that teacher, and we interpret that as a signal to create the teacher’s class rosters. Teachers are usually sent their access codes via email outside of this rostering process. If teachers have questions about their access code, they should contact their supervisor or Quaver Key Account Representative. Note: Rostered student accounts do not need to enter a content access code to gain access to student content.