The Override_sis_stickiness API parameter will not work correctly on data unless the data was imported initially via SIS (or import API). We use ILP for our integration and this would allow Ellucian to better incorporate sticky functionality with canvas.
The override_sis_stickiness feature seems to be incomplete if it cannot be used with new records created via similar methods than what is used to update.
Solution 1: What this feature would do is allow NEW data created via API to show up as if it were created by SIS, and also allow the "Override_Sis_stickiness" function on the new data (so it can ignore changed the data if admins/instructors have modified something) .
The following APIs would be updated (or some):
- POST /api/v1/accounts/:account_id/users
- POST /api/v1/accounts/:account_id/courses
- POST /api/v1/courses/:course_id/sections
- POST /api/v1/accounts/:account_id/sub_accounts
- POST /api/v1/accounts/:account_id/terms
- POST /api/v1/courses/:course_id/enrollments
- POST /api/v1/groups
This would add a new parameter (option) to ensure the data is getting created as SIS data; so that further updates to data using "Override_Sis_stickiness" would work on the newly created data and correctly ignore.
Solution 2: Rework "Override_Sis_stickiness" to work on records created by API as well, and not just SIS created records.
