Course to Batch to Learner flow #410
Replies: 3 comments 5 replies
-
@vishaldeltech - Course unlock should be at a batch level instead of course level. For example, A course can have multiple batches and each batch can have a different unlock schedule. It will be useful if there are any visual flows depicting how the functional usecases will be enabled by this architecture. @rhwarrier @reshmi-nair @vrayulu @maheshkumargangula @pallakartheekreddy - Please go thru this proposal and share your feedback. |
Beta Was this translation helpful? Give feedback.
-
The whole idea of bring in the batch construct is to be able to mangage specifics for the cohort - including start/ end dates, rules of completion, choice of content served via the course, etc. Maybe you could look at adding some more rules based on user role/ sub-role etc. But you should also go back at take a look at the data - especially sub-roles. We need to ensure that the data that is available is clean and usable. (it is a randomly growing field, from what I remember) Going down to learner level assets sounds like a bit of an overkill - if there are a group of similar learners who need access to a specific set of assets, won't it make sense to have a batch for such a group ? Learner level configurability points to a need for personalised learning journeys. Maybe we should not try to force fit the existing course construct for such a use case. |
Beta Was this translation helpful? Give feedback.
-
@parthlawate @rhwarrier @reshmi-nair @vishaldeltech @mathewjpallan @maheshkumargangula - Sharing the confluence docs as discussed in today's meeting: |
Beta Was this translation helpful? Give feedback.
-
Hi folks
We have a business case of custom batch-level assets added to a course (visible only to that specific batch), and learner-level assets visible only to a specific learner. Due dates, and class timings can also be set up at batch/learner level relative to an event. We still need course updates to flow to the learner. We are thinking of meeting the business requirement by managing 3 layers for course consumption. Here are the details of the 3 layers
Layer 1 at Course
In the existing course structure, we add the following capabilities
Layer 2 at Batch
Batch maintains a separate layer that saves modifications for each node/content of the course. The modifications can allow the following to be controlled at the batch level
Layer 3 at Learner
At the learner level, another layer is maintained that saves modifications at the learner level. These modifications apply over the layer maintained by the batch
How the 3 layers work
At runtime when a learner accesses a course,
What happens if the course gets updated after publish
The batch and learner layer work with node/content references in the course. So any modification moves with changes in the structure of the course. For unresolved conflicts, if any, the batch manager will have the fix them for their batch
Requesting feedback from the community on the approach
Beta Was this translation helpful? Give feedback.
All reactions