...
Root (at the collection/question set level) - This will be for the primary collection category
Folder Node (each node that is a folder in the hierarchy of the collection)
Learning asset linked to a node
Metadata at a folder node level - as of now we can assume all the folder nodes in the hierarchy will have same metadata.
Both the set of fields as well as the layout should be configurable. This is a mandatory config.
Hierarchy
Following should be configurable as part of primary category definition related to collection hierarchy:
...
User should be able to add child folder nodes based on this. For example if this is configured as “2” for a collection category, user should not be able to create more than two levels in the hierarchy. Note: Root node is NOT considered as part of the hierarchy.
...
This provides the label to be displayed to each folder node at a given level in the hierarchy. This is given as hierarchy of level labels - with maximum number of levels as configured above. This is optional. Default shows a label “Unit”. An example of the configuration:
...
There are maximum 3 levels in the hierarchy
Any folder node at level 1 will be labelled as “Chapter”. Any folder node at level 2 will be “Section”. Any folder node at level 3 will be “Subsection”
...
Based on this configuration, collection editor should display the corresponding list of categories of the configured object types, when user tries to either create and link a new asset to a folder node or link existing asset to a folder node. It can also be configured that no assets can be linked at a given level.
This is an optional configuration. Default is all categories of all object types for all levels of the hierarchy, including root.
An example configuration:
Root: <<None>> (no assets can be linked to the root)
Level 1: <<None>> (no assets can be linked to a level 1 node)
Level 2: Collection (assets that are of collection object type only be added to a level 2 node)
Leve 23: Content, Question Set (assets that are of content and question set object type only be added to a level 2 3 node)
Generating and Linking DIAL code
Option of generating and linking DIAL codes to collection should be configurable as part of primary category definition. The configuration can have an option “Enable DIAL code linking” that takes a yes or no values. This is an option optional configuration. Default is “No”.
If this configuration is “Yes”, the collection editor should have option of generating DIAL codes and link to root and any folder node in the collection. Please refer to this page that gives details of DIAL code generation and linking
...
User has option to search for existing assets, select one or more of them and add to a folder node in the collection. An “Add from library” page is opened for the user to search and select existing assets to be linked.
...