Symptom
As per the current implementation Providers like Lynda and Harvard MM have courses which are synced via the OCN sync job and stored with SOURCE = null. in the PA_OCN_COURSE while the courses which are pushed via the OCN Odata API, are stored with the SOURCE = API , These duplicate OCN courses cause issue further down the line in other LMS areas.
Environment
Successfactors LMS Version B1805 and Above
Learning Management System B1805 and Above
Resolution
This part of the enhancement would ensure that the existing OCN courses in LMS are updated via the OCN Odata API regardless of the course's origin ( Stored in PA_OCN_COURSE's SOURCE column, values - API or (null) ). So we are Introducing a new bulk API call getOCNCoursesSourceMap() to get the map of course ID concatenated with the provider's ID as its key with the value being the source. Then, for each course, call the respective API depending on the source of the course. If the course is available in the system, it will be updated. Otherwise, create a new OCN course.
The purpose is to update OpenContentNetworkConfiguration override for the customers and set syncCourses for providers LYNDA and HARVARDMM to FALSE , The job will be disable after the first run. (disableJobOnceComplete = true)
This is applicable for B1805 and above versions
Keywords
LRN-31409 , OCN, SOURCE=null, API, OCN to API , KBA , LOD-SF-LMS , Learning Management System , Product Enhancement