Status | ||||
---|---|---|---|---|
|
...
Content contribution is open for all the public users having valid Google id.
Once user sign in, it would be landed on a page with facility to select TB. TBs will be viewed in grid view. Contributor / Reviewer will see textbooks listed in grid view and grouped by specific category (as applicable).
User will also be able to filter textbooks using any two of the taxonomy framework categories (e.g. Class, Subject)
Upon selecting a textbook user will be redirected to TB detail page.
TB detail page would have an option to select any particular chapter or all chapter from the drop down called “Select Chapters”.
User will also see the following numbers:
Total Contribution
My contribution
Rejected
Under Review
All the chapters should have accordion to expand its nodes.
User should be able to contribute both at chapter and node level.
User should be able to contribute up to 4 levels of TB.
Once contributed, content should be shown under that node with status either of them:
Under Review
Published
Rejected
For every contributed content there should be following options:
Preview (User can preview the content In all the stages)
Edit (Only for content which are either in draft or rejected state)
Move (Only for content which are either in draft or rejected state)
Delete (Only for content which are either in draft or rejected state)
Upon clicking “Add”, User will choose what type of content to be contributed from a platter. (Content types to be contributed, have been already defined for the program by state)
Depending upon the content type appropriate tool with required configuration will be launched to make contributions.
Under contribution either user can upload a content piece (video, pdf) which she already has or user may choose to create a set of questions (for test prep program) corresponding to relevant node/chapter of the textbook.
License Terms:
On contribution page, Creator should have options to select license value from a drop down. However by default state defined license should be auto selected.
MCQs created on program portal will take tenant license by default and no drop down required in this case. However on MCQ content detail page, following text should be there in the bottom:- “By creating content on SunbirdEd, you consent to publish it under the Creative Commons License Framework <https://creativecommons.org/licenses/>.”
In case of solution videos, again they should be tagged to default tenant license. In this case no need to provide other license values in drop down.
While uploading any content, after upload & before final submission (on submission page), user would be required to select the appropriate license term for the uploaded content.
By default tenant license value will be selected however if required user may choose other value from the drop down.
License field is mandatory and can not be left blank.
License drop down value must be fetched from SunbirdEd License Library
To start with following can be the drop down values:
CC BY-NC-SA 4.0
CC BY-NC 4.0
CC BY-SA 4.0
CC BY 4.0
There will be a static text on content submission page which would read following:
...
On consumption side, 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>>". There is no change in the UI design/layout as of now. The text will be wrap if it exceeds that current width of the field.
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
In case of MCQs and Subjective questions, user should also have facility (“Add Solution” button) to provide solution (apart from question and options). However providing solution is optional.
Solution can be either a “video” or “text+image” explanation, which user should be able to select from platter and should be facilitated to upload the same.
While uploading a solution video user should be facilitated to search existing/already uploaded videos either on Diksha or on program portal. User should be able to use those videos, similar to Diskha portal.
While uploading solution video/image, there should be following static license text in the bottom of the upload page:
“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.”
In case of content type (apart from question set) where file is being uploaded, a progress bar should be displayed to track the completion of file upload.
When uploading file, relevant information such as file formats, file size, and link to ‘how-to’ resize videos, ‘how-to’ create videos should be provided.
As long as uploaded content is in draft state, means has not been submitted for review, “Change file” option should be provided.
However “change file” option should not be provided for content which are submitted for review or published.
Contributors will be able to Save & Submit from the contribution page.
Upon clicking on status, user shall be redirected to a page which would have content previewing window/ content player along with the reviewer’s comment.
...
As of today, Review will publish to the textbook directly.
...
Note |
---|
Ignore below section for now! - Rough notes |
Program Portal V1
Use case story
...
Expand | ||
---|---|---|
| ||
|
For each content type
Program user journeys
...