...
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 Relational Metadata - The metadata of the relation between a folder and learning asset linked to a node it.
Metadata at a folder node level - as of now we can assume all the folder nodes folders in the hierarchy will have same metadata.Metadata for learning asset linked
to a node - Relational Metadata
This is the relational metadata that can be added to the relation between an asset in the context of the specific collection and the folder to which it is linked. These attributes have to be stored as part of the relation between the asset and the collectionfolder to which it is linked. Some examples for such metadata are:
Schedule (start and end date) or Duration of the asset
“Track in collection progress” - Yes or No. This defines whether the progress of this asset should be considered as part of the progress of this collection
Note:
Relation metadata attributes are completely different from metadata attributes of the asset that is being linked.
The relational metadata is stored as part of folder to asset relation. So if the same asset is linked to multiple folders within the same collection, it will have different set of relational metadata stored for each link.
The relation metadata can be modified as part of Collection modification. This means, the collection has to be in draft state, for the relation metadata to be modified.
Configuration
The set of attributes as well as the layout should be configurable. This is a mandatory config.
...
Note: Through this process, an asset that is in “draft” state is also linked to the collection. However, the collection cannot be submitted for approval, unless all the linked assets are in “live” state.
Limiting maximum number of assets linked to a node
In both the scenarios - Link existing assets (Add from Library) or Create and link assets - there needs to be an upper limit on maximum number of assets that can be linked to nodes in a collection (at any level of hierarchy).
This limit is driven by the technical considerations for providing smooth & fast performance for consumers. We need to support configurable limits for various object types at system level, e.g. Max number of question = 500, Max number of content = 1200.
This limit would apply in context to both “Create and link an asset to a node” and “Link existing assets to a node”
Create hierarchy through a csv
...
There is an option to update metadata and linked assets through a csv. It is similar to what exists currently for textbooks. The functionality is detailed in this page: Create/Download/Update Collection Hierarchy using a CSV
Review comments
Reviewer has an option of providing comments (as a textbox) when requesting changes from the creator. When the creator opens the collection that is sent back for corrections, there is a comments icon in the editor (as in the current editor). Clicking that opens a textbox showing the latest comments from the reviewer.