The Content service uses the Graph engine to communicate with Neo4j. The Graph engine expects schema definitions for each object type. It validates the data object with the object definition during various CRUD operations.
Knowledge has been the differentiator of the human race from other species for a long time. Humans had understood the importance of knowledge and passed it to next-generation via stone carving, writing on leaf and manuscript etc.
In the era of the digital age, learning and knowledge transfer has also become digital. Now all the knowledge is getting transferred via digital means.
Learning Assets is the core entity to serve the learning need of a user under the content of any domain. Learning assets can be Story, Quiz, Game, Instruction simulation etc. Learning Assets can manifest in formats such as Audio, Video, Slides, Documents etc.
It can cater to different user groups in a domain eg. In the school education context, learning assets for different user groups such as student, teacher and parent can be served via different types of assets such as learning content, video explanation etc organised in a textbook structure.
Learning Assets is a generalized object created using the knowledge microservices. Learning assets (Content Object) is a configurable entity that can be extended to serve tons of use cases in multiple domains
Lifecycle of learning assets is a 5 stage cyclic process, Learning Assets follow maker checked method for assets creations.
Draft --> Review --> Publish --> Package --> Update
The initial stage of asset creation is Draft. In this stage asset creation happens. After the creation asset move to the Review stage_._ In the review stage, __ the reviewer approves, reject or request changes in the assets. Reject and request change assets move back to the Draft stage. While approved assets move to Publish stage.
Packaging follows immediately after the Publish stage. In the Package stage, an asset is prepared for online and offline usage. For online usage (streaming), assets are prepared for streaming flows. For offline assets are package and bundle to be used offline, Offline usage involves assets downloads first and uses later.
This is the master definition for Types of items that are supported on sunbird.
Example from education - Question set is an object
Analogous example from the real-world - A foot wear is an object
An object is the core system entity through which any type of asset is managed. Services such as creation, modification, publishing, discovery, consumption - are built around the core objects.
Since an object is the core entity that can be used across multiple use cases in multiple ways, it has to be defined, managed and support wide variety of behaviours, in a very generalized way, so that it can be easily reused in wide range of use cases.
{% embed url="https://project-sunbird.atlassian.net/wiki/spaces/CO/pages/1572536374/Object+Types" %}
For further explanation of objects and categories can be found in the following videos:
Understanding Content Architecture of Sunbird
Understand Collection Architecture : Enabling Organised and Contextual Experience