Introduction

Currently DIKSHA supports only one license when a content is created or uploaded onto DIKSHA. However, NCERT and content providers like Khan Academy have different license types (such as CC-BY-SA, CC-BY-SA-NC etc.). Hence it is required that DIKSHA support multiple types of licenses for content. However all the licenses should comply to CC framework.

JTBD

• Jobs To Be Done: All tenants on DIKSHA know about the supported licenses and ensure content created or uploaded by them have proper license on it. Consumers of content also get to know the correct license information of the content they consume
• User Personas: State Admin, Content Providers, Content Creators, Content Consumers

Requirement Specifications

1. Configuration

• A set of licenses supported across DIKSHA should be configured - henceforth referred to as DLL (DIKSHA License List).
• The configuration will have a name and description text of the license. Examples:
  • CC BY-NC-SA 4.0: This license is Creative Commons Attribution-NonCommercial-ShareAlike - https://creativecommons.org/licenses/by-nc-sa/4.0/legalcode

  • CC BY-NC 4.0 : This license is Creative Common Attribution- Non Commercial -  https://creativecommons.org/licenses/by-nc/4.0/legalcode

  • CC BY-SA 4.0: This license is Creative Commons Attribution-ShareAlike - https://creativecommons.org/licenses/by-sa/4.0/legalcode
  • CC BY4.0:  This license is Creative Commons Attribution - https://creativecommons.org/licenses/by/4.0/legalcode
  • Standard Youtube License: This is the standard license of any Youtube content

• Each tenant can configure a default license from the DLL. Example for some of the tenant as follows:
1. Khan Academy content: CC BY-NC-SA 4.0
2. NCERT content: CC BY-SA 4.0
3. State created content: CC BY4.0

All the configuration happens through back end script (no front-end for self-service), as part of tenant creation process. For all existing tenants, it will happen as a one time update.

2. Creation

New Content

• During the creation of any content (resource, textbook, course, collection), by default any content created in that tenant will have license as defined by the tenant.
• However content creator has an option to select any license from DLL. Edit Details page of Content Editor has a "License" field that displays a drop-down list of licenses (license name) from DLL.
• Default license configured for that tenant will be selected by default.

• Edit Details page of Content Editor will have a static text at the bottom. Sample static text:

        “By creating content on DIKSHA, you consent to publish it under the Creative Commons License Framework - https://creativecommons.org/licenses/. Please choose the applicable  creative commons license you wish to apply to your content.”

Upload Content

“Upload File” page will also have static text at the bottom. Sample static text:

"By uploading content on DIKSHA, you confirm that you are publishing it under a Creative Commons license (https://creativecommons.org/licenses/) that is compatible with the copyright license of the original work and are giving appropriate credit to the original author of the content."

Uploading Youtube video

A Youtube video has one of the two license types:

1. Standard Youtube License
2. Creative Commons License

Both these licenses are part of the DLL list. When a Youtube video is uploaded, system extracts the license information from Youtube and map it to one of the licenses in DLL and automatically updates the license value accordingly. When user opens Edit Details page of the uploaded Youtube video, the extracted license is displayed.

Copied Content

• When a content is copied, the license will be retained as it is. It cannot be modified.
• "License" field of Edit Content Details page for any copied content will display the license name of the original content and remains disabled.
• Even if the original content is modified, the license of the copied content retains the license that is present at the time of copying the content.

Upload Asset (video, audio, image)

TBD

Review

When reviewer opens content to review, in the content details below the content, License information of the content is displayed.

3. Consumption

• The name and description text of the license selected during the creation of content is shown on content details page against License Terms attribute (both in portal and mobile). 

              <<License Name>>: <<License Description>>

• License of a content is not shown at any other place except content detail page (need to be removed from the end page of the content player)

4. Existing Content

• Get the default license value for each content provider.
• Existing content license value should be updated as per default license value provided by each content provider for its tenant. This is applicable both for contents which already has any existing license value as well as contents for which license field is blank.
• Some of the values for default license details for tenants are as follows:
1. Khan Academy content: CC BY-NC-SA 4.0 (Attribution-NonCommercial-ShareAlike) - https://creativecommons.org/licenses/by-nc-sa/4.0/legalcode
2. NCERT content: CC BY-SA 4.0 (Attribution-ShareAlike) - https://creativecommons.org/licenses/by-sa/4.0/legalcode
3. State created content: CC BY4.0 (Attribution) - https://creativecommons.org/licenses/by/4.0/legalcode

                         <Other values to be updated>

• For States content: Set default license value to "CC BY4.0 (Attribution) - https://creativecommons.org/licenses/by/4.0/legalcodefor" for all contents whether contents do have existing license value or license field is blank, except Youtube License. Do not update the existing youtube content licenses.
• Update the values for all existing content based on above logic.

<Alternate Scenario 1>

Exception Scenarios

Wireframes

UI design PPT - Refer  slide 5 - https://docs.google.com/presentation/d/1WgA7kcYL46gTGhUNf3sAT141o6ZQTi6uROrZdzgOmXc/edit#slide=id.g5cc8799187_0_45  

For Future Release

JIRA Ticket ID

<Use Case 1 - User Story 2> Overview

Localization Requirements

Telemetry Requirements

Non-Functional Requirements

Impact on other Products/Solutions

Impact on Existing Users/Data 

Key Metrics