Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »


Introduction

This story defines the appropriate licensing and attribution details to be provided at the time of content creation and to be displayed at the time of content consumption on DIksha.

JTBD

  • Jobs To Be Done: 1. As a content creator i should be able to view licensing provision of the content at the same time i should be able to provide author and attribution details for the content.      2. As a content consumer i should be able to view the licensing provision and author & attribution details of a content.
  • User Personas: This story is relevant for the users creating or consuming content on Diksha. 

Requirement Specifications

Use Case: Defining appropriate licensing, attribution, creation and ownership fields for a content

The objective of this story is to define various fields (related to licensing, attribution, creation etc) which are to be captured at the time of content creation and to display to user at the time of content consumption.

<Overall Process Workflow>

NA


Use Case: Defining appropriate licensing, attribution, creation and ownership fields for a content 

User Story 1: For Content Creation - Overview

This user story defines the fields (related to licensing, attribution, creation etc) to be captured at the time of content creation. Story is further segregated into three scenarios.

<Main Scenario>

 A new resource (teaching, learning, practice or test content) or Textbook is created on DIKSHA either through uploading a file or using content editor.

  • Replace the following existing fields:
    • Creators
    • Contributors
    • Credit To
    • Owner

Add following fields and their value to be provided by the creator during creation time.

  1. Author: (of the resource) - The person or organization who has authored the content. If the author herself is creating the content on DIKSHA, she can give her name. But if a different person has authored the content and do not have access to DIKSHA, the person creating the content on DIKSHA should provide the original author’s name. This is a free flowing text and is mandatory.
  2. License: There are three types of licenses supported on DIKSHA. The three types are CC-BY, CC-BY-SA, Youtube. All content created on DIKSHA will by default have CC-BY-SA license. For any youtube content, the license will be automatically fetched from youtube and get updated. A message with License details is displayed on editor while creating content (like, the content is licensed as CC-BY-SA, except for Youtube. Youtube is licensed under Youtube license). Deepika to provide exact description to be shown.
  3. Credits:
    1. Copyright:  Person or Organization who owns the copyright. Is a free flowing  text. Default can be name of DIKSHA tenant.
    2. Attributions: List of persons or organizations who have contributed to this content. A free flowing text

<Alternate Scenario 1>

A resource (teaching, learning, practice or test content) or Textbook is created on DIKSHA by copying an existing content.

In this scenario, the same fields has to be provided by the creator as in main scenario.

<Alternate Scenario 2>

In this scenario same fields have to be displayed as in main scenario when user edit the existing content details on Diksha. 

Exception Scenarios

Srl. No.Error / ExceptionExpected Handling






User Story 2: For Content Consumption - Overview

This user story defines the fields (related to licensing, attribution, creation etc) to be displayed at the time of content consumption. Story is further segregated into three scenarios.

<Main Scenario>

Following needs to be displayed on content details page (both on portal and app) when a content is consumed:

  1. Created on DIKSHA by - This is the user name of the user who created the content on DIKSHA
  2. Author - As provided by creator during creation of the content
  3. License Terms - This gives the name and description of the license selected during creation
  4. Published on DIKSHA by - This is the tenant name in which the content is created and published
  5. Credits - Clicking on this, a popup with following details will be shown:
    1. Copyright: As given during creation of the content
    2. Attributions: As given during creation of the content

<Alternate Scenario 1>

In this scenario, user is consuming the content which has been created by copying the existing content. At the time of consumption: On content details page all the details of the content as in main scenario have to be displayed. In addition, it should show the following details from the source content - 

"This content is derived from:

Content: <Content Name of the source from which this content is copied>

Author of Source Content : <Author of the source content>

License Terms: <License Terms of the source content>

Published on DIKSHA by: <Published on DIKSHA by (value of the source content)>"

<Alternate Scenario 2>

In this scenario, user is consuming the existing content whose details have been edited. Following fields shall be displayed to consumer:

  1. Created on DIKSHA by - This is the user name of the user who created the content on DIKSHA
  2. Author - As provided by creator during editing of the content
  3. License Terms - This gives the name and description of the license selected during editing
  4. Published on DIKSHA by - This is the tenant name in which the content is created and published
  5. Credits - Clicking on this, a popup with following details will be shown:
    1. Copyright: As given during editing of the content
    2. Attributions: As given during editing of the content

Exception Scenarios

Srl. No.Error / ExceptionExpected Handling






Wireframes

https://docs.google.com/presentation/d/1WgA7kcYL46gTGhUNf3sAT141o6ZQTi6uROrZdzgOmXc/edit?usp=sharing

For Future Release

JIRA Ticket ID

SB-13042 - Getting issue details... STATUS  Jira ticket this story.

Localization Requirements

NA

Telemetry Requirements

Event NameDescriptionPurpose

Non-Functional Requirements

Performance / Responsiveness RequirementsLoad/Volume RequirementsSecurity / Privacy Requirements



Impact on other Products/Solutions

Product/Solution ImpactedImpact Description


Impact on Existing Users/Data 

User/Data ImpactedImpact Description
Content CreatorContent creator will not see some of the existing fields which are being replaced with new fields for content licensing, authoring and attributions.
Content ConsumerContent consumer will see new fields and values for content licensing, authoring and attributions.
Old App versionsOld App versions should not break and should continue to show old labels and fields for existing and new data.
Existing Data 

New App versions will show new set of labels and fields for existing data.

For "Author" field that is new, it will show blank

For "Copyright" field, value should be mapped from the existing field name "Ownership".

For "Attributions" field, it appends all the values from following as comma separated string:

Creators, Contributors, Attributions under Credits

Existing Data that was a copy of another content

Existing copied content cannot show the information of the source content as it is not available as part of its metadata. This will require a data migration to capture it. It will be raised as a separate ticket in future if required.

So, existing copied content will show "Not available" under "This content is derived from"

Key Metrics

Srl. No.MetricPurpose of Metric




  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.