...
Handling View Service different consumption and tracking Use-cases:
Use Case - #1 - When the user tries to consume or track the content outside batch - will be storing the higher hierarchy with content id while consuming
Use Case - #2 - When the user tries to consume the content/course within batch/program - will be storing the higher hierarchy with respective fields
Use Case - #3- When the user tries to track his/her or batch/program status - will be capturing the entire status from aggregated table - user_activity_agg for status
...
Note: Currently batch-id field will be holding the context id data internally
Content View Lifecycle:
When the user view the content in context of a collection and batch, for the first time its start, progress update and end triggers are processed. Revisit (2nd - nth view) of the content will be ignored to process and update the DB.
...