Although we've spent a lot of time making our overrides UI as easy to use as possible, you might still have a use case that requires you to set overrides in bulk, or via some automated process. While we're still working on building out documentation around our "Meta API" (our API for interacting with Edlink as a platform, rather than data for an individual school), we're still happy to help you get something up and running.
If this is a use case that you're interested in, please contact your Edlink client success manager and they will point you in the right direction.
Here are some use cases where programmatic overrides may help you:
- Maintaining legal compliance around privacy (e.g., masking data for particular users).
- Adding controls to your own user interface that allows teachers to delete classes or enrollments that should not be imported.
- Adding the ability to create people, classes (and so on) in your application that do not exist in the LMS / SIS without compromising the integrity of your dataset (i.e. so you don't have to worry about "clobbering" this data on your next sync with Edlink).