| Table of Contents | ||||
|---|---|---|---|---|
|
...
A user with “admin” role logs in to sourcing portal. The admin role is set at a tenant level (currently through backend). The user sees a “Workspace” option. Admin can create assets, review and publish assets, delete published assets.
A user with “Creator” role logs in to sourcing portal and opens Workspace. The user can creates assets, modify his/her existing assets and send them for review.
A user with “Reviewer” role logs in to sourcing portal and opens Workspace. The user can review assets created by other users that are up for review and publish them or reject or sends back for corrections.
A user with both “Creator” and “Reviewer” role logs into sourcing portal and opens Workspace. The user can create assets, review assets created by other users that are up for review and publish them or reject or sends back for corrections.
A user with either ‘Creator’ or ‘Reviewer’ role clicks on ‘Workspace’ from the SunbirdEd consumption portal. They are redirected to the ‘Workspace’ tab in the sourcing portal with an option to return to the SunbirdEd consumption portal.
User Roles
There are three user roles. All the roles are assigned at tenant level through backend process as of now.
...
Create assets in Workspace. Modify and Delete assets in draft state created by them.
Note: A user with creator role can create any type of assets - like collection, content, question set.
Reviewer
A user with Org Admin role can do following operations in the Workspace:
...
For a user with Admin or Creator role, “My Content” page is shown in the workspace.
There is an option to “Create/Upload Content”. Clicking on that option shows all the primary categories configured in that tenant in a popup. It will show the collection categories first
User can click on a category to create an asset of that type.
Based on the primary asset configuration, the corresponding editor is opened to create the asset.
User can save the content. The content is saved as Draft.
User can use “Open” option to edit an existing content in Draft.
Collection should support all the existing features of the collection editor such as:
Generating and Downloading DIAL codes. Linking DIAL codes to folders
Upload/Update ToC using csv. Download ToC as csv
Link contents to folders
Editors have option to send the asset for review.
User can send an asset for review. When an asset is sent for review, all the reviewers get a notification (as existing in current Workspace functionality).
When an asset that is in “Review Pending” state is opened using Open option, the asset is opened in view only mode in the corresponding editor.
User has option to “Delete” against assets that are in Draft state. Clicking this option prompts a confirmation. Upon confirmation, the asset is deleted.
...
A user with Admin or Reviewer role will be able to see “Other Content” tab in the Workspace.
This tab contains the assets in “Review Pending”, “Published” or “Rejected” state. These are assets created by any creator of that tenant in Workspace, other than the current user.
User can open an asset in “Review Pending” state. Corresponding editor for review is opened. User can review and has options to “Send for corrections” or “Publish”.
Publishing an asset publishes the asset in sourcing repo as well as publishes it to consumption repo. The asset page shows a link to the published asset in the consumption repo.
When a collection is published into consumption repo,
it should link to all the corresponding assets in the consumption repo. The same in case of question set with questions.
A QR code linked to a folder in the collection, should point the folder of the published collection in the consumption repo.
“Send for corrections” changes the state of the asset to Draft. When an asset is sent for corrections, the creator of the asset gets a notification (as existing in current Workspace for Reject functionality).
...
When a user who has “Creator” role can only be assigned as collaborator to an asset.
When the user with creator role logs in and opens the workspace, the “My Content” tab shows the assets created by the user as well as the assets to which he/she is assigned as a collaborator.
There is a filter (in advanced filters popup) to filter assets for which the user is a collaborator.
User can open an asset that he/she is a collaborator and modify, save, send for review similar to a creator.
A collaborator will not be able
To add other collaborators (this is taken care through the editor functionality)
Delete the asset. Delete option is not shown against the assets for which the user is a collaborator and not the creator.
Note: From implementation standpoint, if it is easier to show assets that a user is collaborating on in a separate tab (like “Collaborations”), we can go with that approach too.
Sourcing project with target collection
...