.
Follow the OneRoster 1.1 CSV workflow if you use an
OR CSV-certified vendor, such as TxEIS, or if you are building files from
scratch. To save you time in creating files, you can work with one of
our rostering partners—Clever or ClassLink
.
Note: ● The OneRoster 1.1 standard requires separate sourcedIDs for the same user account if they are tied to multiple roles. This would have caused multiple accounts to be created. HMH has introduced unique logic that looks for all users with matching usernames (username in the data feed, not what you set for a username value in the wizard), which is required per the spec. If multiple staff accounts are tied to the same rostering provider users.username field, we will group these accounts together as a single account, assign the lowest level sourcedID (typically the teacher row) to the data store, and upgrade that account to have the multiple roles of all roles sent for that user. That user will also get these same multiple roles across all organizations included in their accounts.
● We
support OneRoster 1.1 only at this time. Any future versions of
the standard must be publicly released by IMS and then we will
investigate planning priorities to support at a future date. For
the most recent IMS certifications and versions of our products,
visit this site: https://site.imsglobal.org/certifications
|
See Next: Set Up Roster – OneRoster CSV