I am researching ILP v5 to see what the pros/cons are. We're currently using informer to generate CSV files which we then upload via SFTP to Canvas. I've roughly implemented posting the CSV files to canvas, but I like how the SFTP upload sends us an email summary at the end of processing. It seems to process the files on the half-hour, so rather than reinvent the wheel with the email summary we're currently leaning towards keeping the status quo. However, if ILP will push data real-time and handle a large percentage of our needs, we may implement it.
From the posts I've read, it sounds as if we need to implement Publisher/Subscriber flavor of Ethos Integration, and not just the Proxy API. I just can't imagine how ILP would be listening for changes to push over otherwise.
It also sounds like we may still need to push in some CSV SIS Imports for blueprints and employee accounts using our current methods. Unless something has changed, I don't believe that ILP pushes over employee accounts. Only students and faculty.
A few questions that I have are found below. Some have been answered in eCommunities with regards to v4.
Wanted to comment on a recent finding. I've been researching issues relating to JIT provisioning via ADFS and SIS Canvas imports. The response from an SIS tech last September stated that:
To begin, your understanding of 'sticky' fields is correct. It is important to note that the login_id field is also sticky, so if it is ever modified in the UI or through the API, a normal SIS Import cannot affect it. You can send an import with 'Override UI changes' to override these, and can add 'Clear UI changed state' to those types of imports to also 'clear' that sticky status so normal SIS Imports can affect those fields again.
I am not entirely certain what the JIT provisioning system would do if you send a 'new' login_id and an existing SIS ID, but I would suspect it should attach to that User. Depending on whether JIT provisioning changes are considered API changes (and thus sticky), you still may or may not want this to occur.
So it sounds like API calls result in the fields they touch becoming "sticky". Which answers my second bullet: "Does ILP un-sticky fields in its API calls?"
email@example.com, I've shared this into the Canvas Developers group on your behalf. For future reference, anyone who creates a piece of content can use the Share button at the upper right of the page to share the content into any other group of which they're a member.
Yup, that's my understanding. Final grade and the instructor can manually type in the last date of attendance to push over.