Angie Addison:Hi Tasia Weatherly this is timely I've been working with one of our vendors on the school and department modeling this week. Our current OneRoster implementation does output on org both the school levels and departments. However as I'm sure you've noticed nothing is parented so you can't link them together. And then the courses are all parented to the higher school parent id. I had a request in to have our group fix this so that the course is mapped to the parent dept id and then in orgs the departments are parented by the appropriate school level id and so on. However, we hit a little bump this week in that while the OneRoster schema only supports a one to one relationship on both: each org level can only have one parent and each course can only have one parent, our model actually supports one to many. Courses can belong to multiple departments, and departments can belong to multiple school levels (schools). We're struggling with what to do in this situation or what the expected outcome would be. Output the many rows in courses i.e. one for each department related to and then just dedupe at the enrollment level? Maybe this isn't the same issue your'e having but looked related so figured I'd give it a shot. Thanks!
We too started using ClassLink and when pulling the data from OneRoster the demographics and grades are missing. Any updates on this?
We are now able to get grade levels from our OneRoster integration between Classlink and Blackbaud, but we are still not getting any demographic information.
Same here. Yesterday, we were able to pull the grades but the demographics still remain a main issue.
Jackie Gerry: Same here. Yesterday, we were able to pull the grades but the demographics still remain a main issue.
Jackie Gerry:
@Angie Addison Do you know if there are any upcoming plans to include a OneRoster demographics file so third parties like Classlink can collect that additional data? Some of our applications need to see birthdate, gender, etc, and until Classlink can get this from Blackbaud we have to upload a supplemental file manually.
Hi @Tasia Weatherly ! Good news - BB has spun up a dedicated integrations team (in K12) for SKY API, OneRoster and a handful of other API needs. I'm passing along your message to Evan York, our Product Manager on that new team so hopefully he can update you soon on the plans for OneRoster phase 2.
Oh great, thanks Angie!