...
User | Accessing Content | Table - user_content_consumption |
|---|---|---|
A |
<By enrolling to Collection> |
|
A |
<By using platform search> |
|
Use Case | Write Request | Read Request(Condition) | |
|---|---|---|---|
| 1 | user consuming individual content by program search | { “userid”: <<userid>>, “contentid” : <<contentid>> } | userid='<<userid>>' and contentid ='<<contentid>>' and courseid ='<<contentid>>' and batchid ='<<contentid>>' |
| 2 | user consuming content by enrolling to collection through batch | { “userid”: <<userid>>, “contentid” : <<contentid>> “collectionid” : <<courseid>> “batchid” : <<batchid>> } | userid='<<userid>>' and contentid='<<contentid>>' and courseid ='<<courseid>>' and batchid ='<<batchid>>' |
| 3 | user consuming content which can be carried forward by enrolling to collection through program | { “userid”: <<userid>>, “contentid” : <<contentid>> } | userid='<<userid>>' and contentid='<<contentid>>' and courseid ='<<courseid>>' and batchid ='<<programid>>' |
| 4 | user consuming content which cannot be carried forward by enrolling to collection through program | { “userid”: <<userid>>, “contentid” : <<contentid>> “collectionid” : <<courseid>> “batchid” : <<programid>> } | userid='<<userid>>' and contentid='<<contentid>>' and courseid ='<<courseid>>' and batchid ='<<programid>>' |
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.
...