As we allow for distributed edits and updates to resources in Kolibri itself, potentials for conflicts will occur. In order to handle these conflicts, resources in the Kolibri ecosystem need to be able to:
Track changes made to resources including who made changes and when.
Ability to access previous versions of resources and roll back changes.
Handling for conflicting changes when syncing locally
There are two broad categories of version control to handle:
Editing of metadata, or the swapping out of entire files e.g. the default video file, adding or removing subtitles, changing thumbnails etc.
Granular edits of editable content formats, e.g. rich text editing
Context
As we allow for distributed edits and updates to resources in Kolibri itself, potentials for conflicts will occur. In order to handle these conflicts, resources in the Kolibri ecosystem need to be able to:
There are two broad categories of version control to handle: