TI1 - 2022/23 - Must do - Plan out integration future state and how to get there, for future sync

Size	Medium
Budget Epic Name	CTP Maintenance Budget
Jira Epic	Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.
Feature Lead	Alistair Spark
Team	Alex Yeung Segun Babalola Nikola Bozhkov

We need to plan out how we are going to re-integrate Moodle-SITS (and how CMIS integration fits in), considering all the changes in API integration patterns planned in ISD.

Would prefer if we could design something that could be re-usable across many institutions, not just products at UCL.

Key drivers:

move to API based integration model & remove requirement for co-located Moodle and MIM databases
retain Moodle data integrity in case of a SITS CI
focus on high value features - faster enrolment, grade sync, etc
do just enough architectural runway to enable this to happen & deal with technical debt afterwards - any quick wins to enable faster iteration?
re-usability of the integration (Moodle community vs UCL) - tension or synergy?

This feature will produce the plan for the implementation which will then be carried out through TI1, 2 & 3 and beyond.

These two features could be part of the plan:

But at this point, too early to commit to the TI as we need to have the plan first.

Note:

This would typically fall under Ops but this is part of the architectural runway for the next phase of CLC work so moving this to be run within CLC Feature Team. Budget wise, remains a Maintenance activity.