Overview:
Sunbird un-enroll service is built to facilitate user to un-enroll from an active open batch As of now open batch is allowing user to do the enrollment , but there is no option for un-enrollment.
Problem Statement:
How to empower Allow user to do the un-enroll enrollment from an active open batch by their own, if batch is not closed or user haven't completed it.
Proposed Solution 1 :
We need to construct Provide a new API for the same. This API needs the user to provide valid userid, batchid and courseid to un-enroll them. For this, there is a need to add a new column namely 'isunenrollmentallowed' (boolean) in the table Unenroll Service API:
...
api for un-enrollment of open batch. This api call will be allowed for open batch only. Api request structure will be as follow.
Url : /api/course/v1/unenroll
{
"request": {
"userId": "string",
"batchId": "string",
"courseId": "string"
}
}
Solution 2 :Once user will un-enroll his/her data will be mark as deleted and won't be visible. Sunbird will provide a new api for un-enrollment for course batch. It will support un-enrollment for open batch and invite only batch both. Participant removal will be decided based on batch type.Request structure will be as follow. Url : /api/course/v1/unenroll
{
"request": {
"userIds": ["user1", "user2"],
"batchId": "batch identifier",
"courseId": "course identifier"
}
}
Accepted solution:
solution 1 is accepted and dev team is going to implement it.
Task Ref : Jira Legacy server System JIRA serverId 2207a759-5bc8-39c5-9cd2-aa9ccc1f65dd key SB-7024
Jira Legacy server System JIRA serverId 2207a759-5bc8-39c5-9cd2-aa9ccc1f65dd key SB-2204