Product: Roster Server
Audience: ClassLink Administrator
Now your server is ready to go and you can provide access to your roster data with vendors that accept the OneRoster format.
- Adding Applications
- Setting Up Permissions
- Granting App Permissions
- Course Permission Options
- Bulk Select Values
- Application Actions
- CSV or REST?
To add an application in the Roster Server, go to Applications -> Add Applications to search for an application or browse the list to find applications.
By switching on the Show Development Apps toggle, it will show the applications that are flagged as development in the developer console (under the application name, you'll see a DEV label).
Then, click the blue Add button to include the application for rostering.
Setting Up Permissions
After choosing to add the application for the roster, there will be a choice presented between two permission types from General: Custom and Full. Custom is the most common permission setting with options to select Unenrolled Users and/or Demographics. By default, the Roster Server will only send users that are enrolled in a class (teachers and students). If you wish to send administrators or other users who are not enrolled in a class, turn on the Unenrolled Users toggle. You can also switch off Demographics for vendors that don’t require it. The Custom setting also allows for the selection of all or some schools and courses.
The Full setting will automatically select all orgs and courses, along with unenrolled users and demographics. The Roster Server will automatically filter the data based upon the selections made here. Permissions are not permanent and can be later edited.
To select certain orgs (buildings), on the left frame, click Orgs -> Pick Orgs to select from a list of building options or All Orgs to select all buildings.
Granting App Permissions
Click on the Applications tab to see a list of applications you have currently provisioned access to. All added apps will be presented here and will show any Recent REST and SFTP Access by the app. Org or Course Access gives a quick overview of how much access that app has for Orgs and Courses. The levels are Full and Basic.
Toggling on Show Extra Columns will give an expanded view of all the users the application's permissions encompass.
Course Permission Options
When selecting courses, there are special options that can be accessed by clicking the Actions button on the right side of the menu.
The actions available are Paste IDs (explained in the next section), Select Courses by Courses: Org ID and Select courses by Classes: School ID.
-Selecting courses by Courses: Org ID - selects all the courses that are assigned to the orgs that are currently selected
Select courses by Classes: School ID - selects the classes assigned to the orgs currently selected and adds courses based on those classes' School IDs. In other words, it will select all the courses assigned to the classes that your selected orgs have.
Bulk Select Values
Another option is the ability to mass-select courses/orgs using a comma-separated list of sourcedIds. Click Paste IDs -> paste the values -> Validate.
The error report card will show the number of invalid sourcedIds:
Once you are finished selecting Orgs and Courses, click Add App to complete your application setup.
When you select a course, you select every class contained in that course and all student/teacher enrollments associated with those classes. Each time you select a course, the system will check to see if the proper org dependency is selected. If you select a course that references an org which is not in your selected permissions, then the system will select that org as well. This is to conform to the OneRoster standard, which demands that all courses have valid dependencies.
Therefore, in order for Roster Server to remain compliant to the OneRoster standard, every course in a given data set MUST refer back to an existing org. In the past, Roster Server allowed users to select individual orgs and courses without regard for "completeness" of data. This would potentially produce CSV exports that were not standard OneRoster files. The Roster Server ensures that all CSV exports can be safely re-imported into Roster Server without any loss of data.
From the list of added applications, under the Actions column, there are options of Edit Permissions, Run Sanity Check, or More Actions.
- Edit Permissions - Edit Orgs and Courses permissions that were previously set.
- Run Sanity Check - Runs a Sanity Check to see if the data has the correct connections.
Under the More Actions menu, additional options include:
- Preview Permissions - Preview Orgs and Courses permissions that were previously set.
- Find - Search for a Class or User. See Find for more details.
- Explore in API - Redirects to the ClassLink Roster Server API
- API Key and Secret - Displays the API key and secret of the app.
- SFTP Settings - Set up data export and file transfer.
- Filter Fields - Add or remove metadata fields to the application's permissions.
- Email Developer - Email is sent to the developer who created the application. If there are multiple developers on the account, then it will only email the developer who signed up the app.
- Remove - Deletes the application.
CSV or REST?
What does this mean? Your OneRoster server can provide data to vendors using either CSV files or the REST API.
What's the difference?
CSV files are sent to the vendor using the OneRoster format. This requires an additional step to set up the SFTP details and timing of when to send the files, which is explained in the Exporting Data page.
With REST API, the vendors fetch the data directly from your server.
Updated: Feb 2019