Job data extracted from an Applicant Tracking System (ATS) can be transfered as a change or full-feed. A change feed could be time-based (e.g. hourly) or event driven (e.g. new job published or updated job language). When processing a change feed, any existing jobs are updated based on the new data received, new jobs would be created, and requests to delete a job would be processed to make the job inactive. On the other hand, the full-feed includes all the active jobs at the time the data is extracted from the ATS and sent to RMK. Besides update fields in jobs the full-feed process also determines if any active jobs in RMK from this source are no longer in the feed. If there are such active jobs, they would be made inactive.
This article explains how job data is updated in RMK in change feeds as well as in full feeds.
- Recruiting Marketing (RMK)
With a full-feed or change feed, the incoming data is compared with the existing data, based on a sub-set of data values that are hashed to determine the job's “key”. For jobs that are unchanged, based on this key comparison, the incoming data is ignored. Any changes, as well as new jobs would be reflected in RMK.
The key for each job is derivated from the following RMK job fields:
- Customfield1, Customfield2, Customfield3, Customfield4, Customfield5
In case a recruiter changes a field in the ATS that's not a key field, the job data won't be updated in a full-feed or change feed unless the recruiter removes the post and post the job again.
Key Fields, Full-Feed, Change Feed, Changes, ATS, Data Extracted, Job Fields, Updated Fields, Integration, RCM, RMK, Recruiting Marketing, Recruiting Management , KBA , LOD-SF-RMK , Recruiting Marketing , LOD-SF-RMK-INT , Integrations with RCM, SSO, MOB, ONB etc , How To