"For developers, that means integrating with individual schools on a one-to-one basis, and that just doesn’t scale"
sadly, it still means this exact thing for Clever's devs. good luck to them - it's a dirty job, but someone's gotta do it.
sadly, it still means this exact thing for Clever's devs. good luck to them - it's a dirty job, but someone's gotta do it.
Example integration flow of SIS to LMS: SIS client (pull) <- business rule filters <- integration itself -> business rule filters -> LMS client (push)
Example integration flow of LMS to SIS: LMS client (pull) <- business rule filters <- integration itself -> business rule filters -> SIS client (push)
Examples of system clients: https://github.com/rockymadden/brainhoney.js https://github.com/rockymadden/masteryconnect.js
Example of K-12 specific spec that is often so mangled into most codebases it causes bugs: https://github.com/rockymadden/lti.js
Some I've done (almost a cartesian product): Infinite Campus, BrainHoney, MasteryConnect, Moodle, IFAS, Blackboard, Safari Montage, Edgenuity, netTrekker, PowerSchool, Canvas, dozens more...
For the vast majority of schools their data is syncing with their apps within a few minutes of them signing up. This is something that wouldn't be possible if we had to white glove every new school.
Clever basically says "Here is the data that we need" which is basically a handful of simple flat files each covering some aspect of school data.
The school is responsible for extracting that data and getting it to Clever (which usually translates into their SIS vendor extracting the data).
Luckily most SIS vendors serve many more than one school district so they get the extract done once and all of their clients are covered.