Page Comparison

Jira Link : https://project-sunbird.atlassian.net/browse/SB-10786

...

      These API's are generating rollup rollup inside context parameter ("rollup": {
                   "l1": "ORG_001"
                })

       /v1/course/batch/search
       /org/v1/search  
       /user/v1/search
       /v1/course/batch/create (wrong rollups got generated l1 having value rootOrgId, should be courseId)

...

1. CourseBatch, Badge object need to be corrected as instead of CourseBatch we are using Batch and for Badge we are using BadgeClass similarly for location & etc.(need to add new object type for location, system setting,dashboard,role,note)
2. Add validation for Object type should be there when object.id is not null. Do we also need to check for cdata.id and cdata.type validation("cdata": [{
   "id": "0127191638961602563",
   "type": "note"
   },
   {
   "id": null,
   "type": "user"
   }])
3. inside edata  need to pass object type like mentors and participants for batch create and add user to batch APIs.(suggestion)
4. object.type should be user enroll or user or participants or mentors.(for better understanding or clarification)
5. Whats the difference between rollup under context and inside object in telemetry event.
6. In which property of telemetry event we need to store these values.

          x-device-id,x-channel-id,x-app-id