Page Comparison

...

1. Sourcing org admin logs into the system and starts creating a sourcing project

2. The system provides option to select the project scope (the exact labels to be decided)

   1. Seek content for certain target collections

   2. Seek content for a certain framework

3. If user selects the option “Seek content for certain target collections”, the existing flow for “Seeking content for target collections” is triggered.

4. If user selects the option “Seek content for certain framework”, following flow is triggered.

5. The use has following options to select as the project scope:

   1. Framework Type - Available list of framework types in the system. Example: “K-12 Curriculum”, “Continuous Professional Development”. There will be a default framework selected as per system configuration - say “K-12 Curriculum” by default. Selecting framework type is mandatory. Only one framework type can be selected per project.

   2. When a framework type is chosen, the framework available in the tenant of the selected framework type is taken as the framework to be used for the project. The assumption is that there is maximum one framework of given type is configured in the tenant. In case there is no framework of the selected type configured at tenant level, the framework of that type configured at system level is taken. The assumption is that there is maximum one framework of a given type is configured at the system level. In case there are no framework of the selected found either at tenant or system level, system shows an error message “Incorrect framework configuration. Please check with system administrator”.

   3. A set of framework attributes per framework type are configured per tenant to be shown during project creation. The framework attributes are shown based on this configuration. For example, for a “K-12 Curriculum” type of framework, typically the attributes configured will be - Board, Medium, Class, Subject

   4. Dependency of attributes should be taken care when showing the attribute values. For example, if Subject is dependent of Class, the values of Subjects should be populated based on the selected Class.

   5. User can select one or more values from the framework attributes. None of the attributes are mandatory. User also has option to select all.

   6. User has option to select one or more content types - this should show all primary categories of all the non-collection object types (content, question set).

6. Apart from the project scope, user enters other project details that are same as existing project creation flow, except selecting target collections.

7. User can save the project as draft.

8. User can reopen a saved project in draft state. The saved values are displayed. User can modify any values and save.

9. User can publish the project once all required details are provided.

10. The “My Projects” table shows the created project. Below the Project name, instead of “<<>> Digital Textbooks”, it shows “<<framework type>>”, where <<framework type>> is the type of the framework chosen as part of the project scope.

...

Same as that of project with target collections.

Reports

Organization Level Reports

Project level funnel report

Project level funnel report should include sourcing projects that seek content NOT for any target collections. The columns are same as that of sourcing projects that seek content for target collections.

Content details report

Content details report should include sourcing projects that seek content NOT for any target collections.

The columns related to target collection - column G (“Textbook Name”), column H (“Textbook ID”), column I (“Chapter ID”) will be empty for content that is contributed to such projects.

The framework attribute columns (Board, Medium, Grade, Subject) should show the corresponding attribute values of the content.

Project Level Reports

As of now there are no project level reports for sourcing projects that seek content NOT for any target collections.