Single Sourcing Solution Home

Key Objective

Space to brainstorm, design, define solutions and plan the single sourcing solution. Key goals of this activity is to create single solution that caters to all the needs of content sourcing - source content using different models and manage published content. This also includes separation of sourcing repository from consumption repository.

Key Terminology

Learning Asset - An object that can be created and targeted to a group of users who can consume it in appropriate context of learning. This can be an individual object such as a worksheet, explanation content, course assessment that can be consumed, or it can be a collection of objects such as a Digital Textbook, Course etc.

Sourcing Organization - Organization that sources learning assets for their needs and publishes it for consumption. “Sourcing” of content includes all supply-side processes and management of learning assets, such as - creating, reviewing, assembling, modifying, publishing of any learning asset. Learning assets can be created in-house or sourced from external organization.

Contributor - Any organization or individual who creates and contributes learning assets that can be used by a sourcing organization for publishing and consumption. Note a contributor can contribute learning assets to multiple sourcing organizations.

Reviewer - A reviewer is an individual who reviews learning assets and approves/rejects/send back for corrections. Reviewer can belong to a contributing organization or a sourcing organization.

Sourcing Project - A sourcing project encapsulates a set of sourcing activities, typically for a set of common needs, and have an associated schedule to it.

Object - This is an internal representation (tech design) of a learning asset. Any learning asset is internally defined and stored as an object. An object type is defined by generalizing a set of attributes and behavior.

Category - Category is an external representation of a learning asset that is defined based on specific domain/solution.

The different object types and categories are detailed here:https://project-sunbird.atlassian.net/wiki/spaces/CO/pages/1572634683

Problem Statement

Currently there are two front-end tools to create and manage assets and content.

  1. A “workspace” that is part of common portal (both for consumption and creation). This has been the front-end UI for creating managing assets since the beginning of Sunbird ED. This is used to create content by internal creators of the sourcing organization. Content created through this tool resides in the same repository as that is used by consumption.

  2. A Sunbird coKreat (vdn) portal (sourcing and contributor) that is used for sourcing content from contributors (external or internal) by creating sourcing projects. Content created through this tool resides in sourcing repository. Once the content is reviewed and approved by the sourcing organization reviewers, the content is published in consumption repository.

Users have to go through two different tools which is not efficient and causes confusion. The two front-end tools are also use different versions of software and hence maintenance also becomes difficult.

Solution

The solution is to:

  1. Build a common front-end that can cater to all sourcing activities described above

  2. The single front-end solution will take care of generalization and externalization so that it can easily be extended to support new object types and categories.

  3. Have separate repositories for sourcing and consumption. Only published assets are pushed to consumption repository and available for consumption