Asynchronous contribution process by whitelisted contributors
Overview
The current contribution process supported by the sourcing solution is a point to point, synchronous pipe model. The whole process is initiated by a sourcing organization when they have specific content needs. This does not allow for an open flow of content supply onto the sourcing repository. Hence the contribution doesn't happen at a large scale.
To reduce this friction and enable large scale contributions, sourcing solution need to support an asynchronous mode, platform model of content contributions. Sourcing repository is like a warehouse, where contributors should be able to put their content in the warehouse anytime, irrespective whether there is a specific need by a sourcing organization at that point of time.
However, enabling such a process to any contributor might result in its misuse and the warehouse might become a private repo. So contributors who can contribute asynchronously have to be whitelisted/approved first. This may be enabled only for organizations and not individuals.
There are three major parts to enabling this:
Whitelisting a contributor organization
Whitelisted contributor organization creating/uploading content onto warehouse - without any specific sourcing project.
Sourcing organizations being able to search the content from the whitelisted contributors, review and present it for consumption.
High-level Workflows
Workflow Details
Whitelisting content contributors
Request for Whitelisting by a contribution org
Contribution org admin enrolls their organization as contribution org on the platform (existing flow)
Contribution org admin logs
There is an option to “Request for whitelisting” on the admin page.
Clicking the option will open a Request for whitelisting page.
The page contains
A set of text fields to enter (TBD)
A link to guidelines for a whitelisted contributor
Option to create sample content
Status: This will be “Initiated” first
User has an option to save the request and submit the request.
Once the admin fills in required details, the required information is saved.
User can again click on “Request for whitelisting”. The same page is opened with the saved details, with the status as “Initiated”.
User can modify/add and finally submit the request.
A popup to agree terms and conditions is opened. User has an option to accept by selecting a check box. Once accepted, the option to submit is enabled.
Once submitted, the status will change to “Pending Approval”.
A notification is sent to all sourcing organization admins that have access privilege of whitelisting a contributor.
When the user opens the “Request for whitelisting” page, the details are shown in a read only mode, with the status “Pending Approval”.
View and Whitelist a contribution org by a sourcing org
One or more sourcing organizations can be configured (through backend) to have access privilege of whitelisting a contributor.
The sourcing org admin that have access privilege of whitelisting a contributor logs in.
Any new requests are shown as new request in the new notification option.
The user sees an option for “Contributor whitelisting”
The user clicks on the option and a page with list of contributors that have requested for whitelisting appears
Each entry shows the contributor name, requested date, status, and approver name.
Status will show “Pending” or “Approved”
Approver name will have the name of the sourcing org that approved the request, if the request has been approved. Else it will be blank.
Clicking on the contributor name will open up the whitelisting request form and shows the required details.
User can view all the details (including sample content uploaded). If the request is not approved yet, the user has option to approve. User is shown a confirmation dialog and upon confirmation, the contributor is whitelisted.
Contributor is sent a notification about the approval.
When the contributor opens the “Request for whitelisting” page, the details are shown in a read only mode, with the status as “Approved”.
Content contributions from whitelisted contributors
Contributor org admin views workspace and assigns users
Admin of a whitelisted contributor org logs into the system
There is an option called “My workspace” is shown
User clicks the option.
A page similar to the project page opens. There are two tabs
Contents
Add users to workspace
Contents tab has the following details
Table showing all the contents created by all contributors of the org in the workspace
Overall status numbers
Option to filter contents
Option to create new content
“Add users to workspace” tab is exactly same as the current “Add user to project” tab.
Admin can add one or more users, part of the organization, to the workspace as contributors or reviewers. Note a user can be added as both Contributor and Reviewer to a project.
Contributor views workspace and creates content
Contributor of a whitelisted contributor org logs into the system. The user is added as a contributor to the workspace by the admin.
There is an option called “My workspace” is shown
User clicks the option.
A page similar to the project page opens. There is a “Contents” tab
Contents tab has the following details
Table showing all the contents created by him/her in the workspace
Overall status numbers
Option to filter contents
Option to create new content
User clicks “Create new” content option.
User is shown all types (primary categories) of content and question sets configured in the system.
User selects a content or question set type (primary category).
The corresponding editor is opened.
User creates/upload content, enters required metadata and saves the content.
The content is in “Draft” state by default. User previews the content.
User sends content for review. The content is changed to “Approval Pending” state.
Tagging content with multiple frameworks
As part of creation or editing of a content, contributor will be able to tag content to one or more frameworks available in the system. These values are tagged as organization framework(s).
The edit details form shows a dropdown with list of all framework types available in the system.
User selects one of the framework types.
A dropdown with list of all framework names available in the system for the selected framework type are shown.
User selects one of the frameworks. There is an option “Tag framework metadata”. User clicks the option.
A tree selection dialog (similar to Topic selection) is opened.
The tree shows list of all metadata categories in the selected framework as the first level nodes. For example, a K-12 framework shows the following nodes - Board, Medium, Class, Subject, Topics
Each node shows all the values of that metadata category under it.
Note: The dependencies between the metadata categories are ignored.
User can select one or more values from the nodes.
Note: If a non-leaf node is selected, all the nodes under that are automatically selected.
User can search metadata values using a search box (similar to current Topics selector)
User can see selected list of metadata values (similar to current Topics selector)
User selects one ore more values of the metadata categories and saves.
The selected values are saved along with the value of the corresponding framework
User can select more frameworks as above (one by one) and tag with corresponding values.
Review views workspace and reviews content
Reviewer of a whitelisted contributor org logs into the system. The user is added to the workspace as a reviewer by the admin.
There is an option called “My workspace” is shown
User clicks the option.
A page similar to the project page opens. There is a “Contents” tab
Contents tab has the following details
Table showing all the contents created by all the org contributors in the workspace - that are in either approval pending or approved status.
Overall status numbers
Option to filter contents
Option to create new content (in case the user is also added as a contributor)
User clicks on a content that is in “Approval Pending” status.
Content page is opened. This is exactly same as the content page opened for a reviewer currently.
Content preview is shown
There are options to “Request for corrections”, “Approve”, “Reject”, “Edit Details”
User can edit the configured set of metadata using Edit Details option
User can Request for corrections by adding comments. The content goes to “Corrections Pending” state.
User can Approve the content. The content goes to “Approved” status.
User can Reject the content. The content goes to “Not Approved” status.
Contributor edits and resubmits content for review
A contributor can edit content in “Corrections Pending” status or “Not Approved” status and again send for review.
The same flow as above applies.
Use content contributed by whitelisted contributors
Search and use by sourcing organization
This flow describes how a sourcing organization can use the content from whitelisted contributors that is present in the warehouse. Currently, the only way a sourcing organization can use existing content is by the contributors of the same organization searching and adding existing content to a sourcing project. Currently the existing content that can be added this way is a set of curated content (called ‘MVC’ content).
Sourcing organization can use content from whitelisted contributors in the same flow.
Contributor of the sourcing organization logs into the system (contribution portal)
The user sees the sourcing project to which he/she is assigned as a contributor
The contributor opens the sourcing project. Project page is opened with list of collections in the sourcing project.
User opens a collection. The collection hierarchy is shown. Each section in the hierarchy has two options “Create new”, “Add from Library”.
User clicks on “Add from Library”. “Add from Library” screen is opened.
Apart from other existing filter options, there is an additional dropdown option to filter with the following values:
Curated content (MVC)
Content from contributors
User can select one ore more options. By default, nothing is selected. In case no option is selected, no filter is applied for this option (it means content comes both the sets).
User selects one or more options and applies filter.
In case the value “Content from contributors” is selected in the filter,
The content from whitelisted contributors that is in “Approved” state (approved by contribution org reviewers) is searched and shown.
Following additional filters are provided
A dropdown that has list of whitelisted contributor organizations
A checkbox that has “Only content that is already used by a sourcing organization”
Following details are shown for each content from whitelisted contributors
Contributor Organization that contributed the content
Sourcing Organization that has whitelisted the contributor org
Sourcing Organization that has published the content for consumption (if any)
User can select a content and add to the collection (same as existing functionality)
When the collection is reviewed by reviewer in contribution portal (in case two level review is enabled), the reviewer can only Accept or Reject the content (cannot send back for corrections).
When the collection is reviewed by sourcing org reviewer (in sourcing portal), the reviewer can only Accept or Reject the content (cannot send back for corrections).
Search and use by the contributor
The contributor of the whitelisted contribution org should be able to use the content created by them in their workspace that got approved, in any of the sourcing projects. This flow describes how this can be done.
Contributor logs into the system
Contributor opens the sourcing project to which she is assigned as contributor
The list of target collections are shown.
User opens a collection. The collection hierarchy is shown. Each section in the hierarchy has two options “Create new”, “Add from workspace”.
User clicks on “Add from workspace”. A screen similar to “Add from Library” screen is opened.
This screen shows only the content created by this user and is approved by the contribution org reviewer.
User can select one ore more options and applies filter.
User can select a content and add to the collection (same as existing functionality)
When the collection is reviewed by contribution org reviewer,
If the content is already published for consumption, the reviewer can only Accept or Reject the content (cannot send back for corrections).
If the content is not published for consumption, the reviewer can Accept, Reject or Send back for corrections.
When the collection is reviewed by sourcing org reviewer,
If the content is already published for consumption, the reviewer can only Accept or Reject the content (cannot send back for corrections).
If the content is not published for consumption, the reviewer can Accept, Reject or Send back for corrections.