Anyone connecting Go Guardian with One Roster?

Josceline Reardon

I'm trying to add use GoGuardian with OneRoster, but have hit a roadblock.

GoGuardian is:

#1. Is saying They don't currently support v1p1 for this integration (however they have a One Roster connection)?

#2. That they do not have any SFTP information to add to my OneRoster Integration in Blackbaud (which is how you set it to update nightly).

Blackbaud Support says "we do use the v1p1 base URL for both oAuth 1.0 and oAuth 2.0 in our system. The URLs that the third party would be using to connect with our system is https://api.sky.blackbaud.com/afe-rostr/ims/oneroster/v1p1."

Stephen Boyle

@Josceline Reardon
Hi Josceline,

If GoGuardian only supports OneRoster v1.2, then connecting via API won't work b/c we only support v1.1 currently. I'm not sure if GoGuardian can use v1.1 csv files, but I tend to doubt it. There are several changes that would definitely impact a straight v1.2 implementation
- Namely:

• there are 8 new file types in the zip file
• roles.csv is a new file that handles the v1.1 user fields for role and orgSourcedIds.
• And probably anything in the gradebook related files

Sorry the news isn't better.

Josceline Reardon

@Stephen Boyle thank you! You are always so helpful, so I'll also ask if you know anything about this: We do have an odd thing going on where our One Roster is pulling some people with the “Parent of Withdrawn” roles We have no way of knowing this, except that I was emailing the Parents that did not have an SMS # from my OneRoster export and a few people responded and said we no longer go to your school. Sure enough, when I looked them up, they were “Parents of Withdrawn Students”, but they export as parents. I have a case in and escalated it today because these exports pull to our emergency text communication system.

Thanks for any information you might have. Have a great weekend.

Stephen Boyle

@Josceline Reardon
That is something we are taking up in the next couple of weeks. There are various scenarios that are still under research to make sure we are following the spec for the file format. For instance, we know we will remove w/d students with no pertinent class enrollment information. Though, w/d student that do have data, like gradebook grades, may need to stay. I'll have more on that soon. The API returns these students but marks them ‘tobedeleted’. The export files don't have that indicator in the bulk file format that we support, so we will look into the expected handling of them when we take up this work.

Hope that helps.

Ryan Matyjasik

@Stephen Boyle Is there a current plan for implementing OneRoster v1.2? This standard is over a year old and includes vital usability aspects such as ability to sync preferred names and non-binary gender. How long can we expect this implementation to take?

5.2.1 Enhanced User Demographics Support
OneRoster 1.2 includes support for users who wish to be referenced by a first, middle or last name that is different then their legal name via the addition of 3 new properties; preferredFirstName, preferredMiddleName, and preferredLastName to the 'user' class. Additionally, OneRoster 1.2 adds support for learners with non-binary genders via additions to the associated vocabulary set.

Stephen Boyle

@Ryan Matyjasik
Implementation of OneRoster v1.2 is not currently planned. We are developing the scope of work to address it, so that we can put it in the plan. The support for some of the new fields, such as the new preferred name fields, is also dependent on current projects underway to introduce those fields for users in BEM.

Hayley Field

@Stephen Boyle I wanted to check back as this would be highly appreciated as I am in the same predicament as Josceline with attempting to automate and sync to GoGuardian. If there is any way that this could be updated for 1.2.