...

To enable this capability, as part of linking asset to a trackable collection, system provides an option (through UI and API) to specify whether the asset “Is optional” - Yes or No. Default value is “No”.

...

Enable closing a trackable collection for modifications

The objective of this is to enable trackable collections to be modified/extended over a period of time, even after publishing them - without impacting the progress tracking. This is to support use cases where modules (sub-folders) within a course are periodically updated. Users can start consuming the modules as and when published. But the calculation of progress tracking happens only once the course is published with all the modules. Once the progress tracking starts, the collection will be closed for any further modification.

To enable the above, any trackable collection will have an attribute “Calculate progress ” “Open for modification” that can take values of “Yes” or “No”. By default it is set to “No”“Yes”. As long as the value is “No”“Yes”, the overall status of the collection progress is not calculated, because the collection might be undergoing modifications. Hence no certificates are generated.

Once the all the content is added to the collection, creator can change value from “Yes” to “No” to “Yes”. Appropriate warning is shown to the user when modifying this value. The same is shown to the reviewer when publishing the collection. Once the value is changed to “Yes” “No” and the collection is published, system calculates the progress based on the rules set for progress calculation.

Once a trackable collection is published with “Calculate progress” “Open for modification” value set to true“No”, the collection can no longer be modified.

...

Once a trackable collection is published, the collection can be modified only if the “Calculate Progress” “Open for modification” value is set to “No”“Yes”. If the “Calculate Progress” “Open for modification” value is set to “Yes”“No”, the collection can no longer be modified.

This has to be enabled both at the UI as well as in API.

In UI, following will happen:

1. When creator submits a trackable collection for review, system checks if the value is “No” and gives a warning message.

2. When reviewer publishes a trackable collection for review, system checks if the value is “No” and gives a warning message.

3. For any live trackable collection with value set to “No”, if the creator tries to edit, a message stating “This cannot be modified as it is closed for modifications.” should be shown.

Deleting a collection

Once a trackable collection is published, the collection can be deleted only if the “Calculate Progress” “Open for modification” value is set to “No”“Yes”. If the “Calculate Progress” “Open for modification” value is set to “Yes”“No”, the collection cannot be deleted.

This has to be enabled both at the UI as well as in API.

In UI, for any live trackable collection with value set to “No”, if a user tries to delete, a message stating “This cannot be deleted as it is closed for modifications.” should be shown.

Common Functionality

This section details the common functionality across trackable and non-trackable collections.

...

1. When a user opens a collection in editor for modification, system checks if there are newer versions present for one or more of the linked assets.

2. In case there are newer versions present, editor indicates the same using a warning popup when the collection is openedis shown with appropriate message.

3. The

   popup has linked assets name and option to update to latest

4. User can select one or more assets (or Select All) and update to latest.

5. The latest version of the selected assets are linked to the collection.

The assets with newer version assets that are of older version (that have latest version not linked) are also indicated in the folder hierarchy (with a different color)

1. Clicking on the asset node will preview the older version.

2. There is an option “View latest version”. Clicking that will open the latest version in a different tab.

3. There is an option to update the version to latest.

4. If user selects the option to update the version to latest, the latest version is linked to the collection and the preview reflects the latest version.

6. There is a “Update all assets” option in the Folders kebab menu (vertical dots). Clicking this will show a confirmation popup. Once user confirms, all linked assets are updated to latest version.

7. In case there are newer versions present, editor indicates the same using a warning popup when the collection is submitted for review. There are options to “Cancel submit” and “Proceed to submit”. “Cancel submit” brings back the user to the editor. “Proceed to submit” will submit the collection for review.

...

1. When a user opens a collection for review, system checks if there are newer versions present for one or more of the linked assets.

2. In case there are newer versions present, editor indicates the same using a warning popup when the collection is opened. The popup has linked assets name (for view only)is shown with appropriate message.

3. The assets that are of older version (that have latest version not linked) are also indicated in the folder hierarchy (with a different color)

   1. Clicking on the asset node will preview the older version.

   2. There is an option “View latest version”. Clicking that will open the latest version in a different tab.

4. The above popup is also shown when user choses “Publish” option. There are options to “Cancel publish” and “Proceed to publish”. “Cancel publish” brings back the user to the review page. “Proceed to publish” will publish the collection.

...