Candidate Mapping Custom Metadata Records

All Textkernel Source! setup procedures are available here.

As with the previous Search! import functionality, Candidate A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider. field mappings (Candidate_Mapping__mdt) must be configured to instruct the parser which fields to extract from the incoming candidate data.

The Textkernel Automation API API, or Application Programming Interface, is used by customers to create custom career portals or to take advantage of Data Mirror/DataMart. Bullhorn prefers to use REST API. supports only JSON data, so the JSON Path and JSON Node values must be set to function correctly.

Candidate Mapping Record Fields

The below fields on the Candidate Mapping records are relevant for TK An abbreviation for Textkernel Source! Importing:

Setting	Value
Label	Used to identify the mapping. Some label values are reserved for Skills Mappings (see below).
Object	The Object that this mapping is for. For TK Source!, this should be either "Contact", "TR1__EducationHistory__c", or "TR1__EmploymentHistory__c".
Field API Name	The API Name of the field on the object.
JSON Path	The path through the import JSON to where the data resides. i.e. personal.address.
JSON Node	The field to extract from the JSON relative to the JSON Path. . city. Supports the use of basic formatting (spaces, commas etc), allowing the extraction of multiple values into a single field. i.e. streetNumberBase streetName, city, postalCode results in "123 Main Street, Reading, RG12 3AB".
Default Value	If the extracted value is blank, use this value instead.
Action When used in ATS or Search and Match UI, one of multiple actions available after user has selected a sub-set of Candidates	What action should be performed if there has already been data mapped to this field.  For Textkernel Source!, the default is to override the value, unless Action is set to Merge. In that case, the new value will be appended to the end with a semicolon (;) between.

Candidate Mappings

The Candidate Mappings can be separated into four areas:

Contact

• Contact Mappings contain the basic one to one mappings for the contact record.
• They mostly have an Object field of "Contact".

Education History

• Education History Mappings are processed for each Education History entry found in the imported data.
• They have anObject of "TR1__EducationHistory__c".
• The JSON Path value should point to where in the JSON the Education History list is found. i.e. educationHistory.
• The JSON Node value should point to which field within the Education History element should be extracted. i.e. instituteName.

Employment History

• Employment History Mappings are processed for each Employment History entry found in the imported data.
• They have anObject of "TR1__EmploymentHistory__c".
• The JSON Path value should point to where in the JSON the Employment History list is found. i.e. employmentHistory.
• The JSON Node value should point to which field within the Education History element should be extracted. i.e. employerName.

Skills

Textkernel Source! skills parsing is supported through the use of four special candidate mapping entries with specific label values. These mappings have an Object value of "Contact", but they're given special treatment. They're used to handle the flattening of several skill nodes found in the incoming data into a single text field on the contact.

The special candidate mapping entries include:

• Languages
• Computer Skills
• Professional Skills
• Soft Skills

Example Basic Mappings

Below are some basic default mappings:

Setting	Value	Setting	Value	Setting	Value
FirstName	Contact	FirstName	personal	firstName
LastName	Contact	LastName	personal	lastName
DateOfBirth	Contact	TR1__Birthdate__c	personal	dateOfBirth
StreetAddress	Contact	OtherStreet	personal.address	streetNumberBase streetName
EducationLevel	TR1__EducationHistory__c	TR1__DegreeType__c	educationHistory	levelCodeDescription
EducationStartDate	TR1__EducationHistory__c	TR1__StartDate__c	educationHistory	startDate
EducationEndDate	TR1__EducationHistory__c	TR1__EndDate__c	educationHistory	endDate
EducationInstitute	TR1__EducationHistory__c	TR1__SchoolName__c	educationHistory	instituteName
EmployerName	TR1__EmploymentHistory__c	TR1__EmployerName__c	employmentHistory	employerName
EmploymentStartDate	TR1__EmploymentHistory__c	TR1__StartDate__c	employmentHistory	startDate
EmploymentEndDate	TR1__EmploymentHistory__c	TR1__EndDate__c	employmentHistory	endDate
EmploymentJobTitle	TR1__EmploymentHistory__c	TR1__Title__c	employmentHistory	jobTitle
Computer Skills	Contact	TR1__Systems_Experience__c	skills.computerSkill	name
Languages	Contact	TR1__Language__c	skills.languageSkill	languageCodeDescription
Professional Skills	Contact	TR1__Skills__c	skills.otherSkill	name	Merge
Soft Skills	Contact	TR1__Skills__c	skills.softSkill	name	Merge

Next Procedure

Configure Imports List View