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.
CC BY-NC 4.0 : This license is Creative Common Attribution- Non Commercial - https://creativecommons.org/licenses/by-nc/4.0/legalcode
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.
“By creating any type of content (resources, books, courses etc.) on DIKSHA, you consent to publish it under the Creative Commons License Framework. Please choose the applicable creative commons license you wish to apply to your content.”
“Upload File” page will also have static text at the bottom. Sample static text:
UPLOADING / LINKING CONTENT: “By uploading content on DIKSHA, you confirm that you are publishing it under a Creative Commons license that is compatible with the copyright license of the original work and are giving appropriate credit to the original author of the content.”
A Youtube video has one of the two license types:
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 and is non-editable.
Assets will have the default license configured for the tenant. User cannot change the license. A static text is shown in the asset upload page. Sample text:
“I understand and confirm that all resources and assets created through the content editor or uploaded on the platform shall be available for free and public use without limitations on the platform (web portal, applications and any other end user interface that the platform would enable) and will be licensed under terms & conditions and policy guidelines of the platform. In doing so, the copyright and license of the original author is not infringed. ”
If the asset is a Youtube video, the current validation exists as it is (), i.e., the video should have a "Creative Commons Attribution" license.
However, the license value is mapped to CC-BY 4.0 of DLL and the asset license value is updated to CC-BY 4.0 as given in the DLL.
There is no additional filter for license value required in the search.
When reviewer opens content to review, in the content details below the content, License information of the content is displayed.
License Name | Description | URL | Final Text to be displayed on consumption page <Name> <Description> <URL> |
CC BY-NC-SA 4.0 | For details see below: | CC BY-NC-SA 4.0 For details see below: | |
CC BY-NC 4.0 | For details see below: | CC BY-NC 4.0 For details see below: | |
CC BY-SA 4.0 | For details see below: | CC BY-SA 4.0 For details see below: | |
CC BY4.0: | For details see below: | CC BY4.0 For details see below: | |
Standard YouTube License | Standard YouTube License |
UI design PPT - Refer slide 5 - https://docs.google.com/presentation/d/1WgA7kcYL46gTGhUNf3sAT141o6ZQTi6uROrZdzgOmXc/edit#slide=id.g5cc8799187_0_45
An optional section that describes functionality that may not be completed within a release
N/A
N/A
N/A
Product/Solution Impacted | Impact Description |
---|---|
Content Bulk Upload Format | Since we are providing an option to choose license to content creator from portal, it is important that we take care of this for bulk upload process as well. We need to add one additional column in bulk upload sheet to capture license value for each content piece being uploaded. Following to consider:
|
Use this section to capture the impact of this use case on existing users or data. To add or remove rows in the table, use the table functionality from the toolbar.
User/Data Impacted | Impact Description |
---|---|
Specify whether existing users or data is impacted by this use case | Explain how the users/data will be impacted. |
Specify the key metrics that should be tracked to measure the effectiveness of this use case in the following table. To add or remove rows, use the table functionality from the toolbar
Srl. No. | Metric | Purpose of Metric |
---|---|---|
Specify the metric to be tracked | Explain why this metric should be tracked. e.g. tracking this metric will show the scale at which the functionality is used, or tracing this metric will help measure learning effectiveness, etc. | |