Understanding Search Resume Response

Getting started with the new Search Resume API requires you to pull information from several different sources.The table below describes the main list of search parameters.

Parameters are optional and can be omitted. The same way, some parameters have default values. That means if there are no values for some parameters in the search request, service will use default values.

Response Fields

Name Description
resumeSearchRequest Query parameters
suggestionList Suggestion
resumePreviews Contains resume items described below
navigationQueryGroups Contains dimensions and number of matches for current query

Resume Fields for Preview

Name Description
refno Id of current resume found
title Resume title provided by job seeker
sectorCode Business sector provided by job seeker
location Location provided by job seeker
locationId Location Id provided by job seeker
yearsExperience Experience provided by job seeker
updateDate Last date of resume update
snippets Text with first 30 words of the CV with marked words
labelTranslations locale=”en” Translation for the specified locale

Navigation

The descriptions of the XML parameters are listed below.

Parameter Name Description
navigationQueryGroup Contains the data of parameter group.
navigationParameter Name of the parameter.
navigationQueries Contains the data of navigation queries.
navigationQuery Contains the data of navigation query.
value Id of matched dimension, value of the parameter.
occurrences Number of times when this parameter’s value occurs for the current dimension.
link Contains query to refine/delete current dimension.
labelTranslations locale=”en” Specifies the language of the translation.
dictTranslations locale=”en” Specifies the language of the dictionary.
translation Contains the data for the pecified language.
path Specifies the path to the value in the dictionary.
content Value of the translation.

The example of the navigation XML is placed below.

<ns2:navigationQueryGroups>
<ns2:navigationQueryGroup>
<ns2:navigationParameter>currency</ns2:navigationParameter>
<ns2:navigationQueries>
<ns2:navigationQuery>
<ns2:value>GBP</ns2:value>
<ns2:occurrences>4</ns2:occurrences>
<ns2:link>http://app.ws.pilot.efinancialcareers.com/v1/resume-search?work-sector-name=EQUITY&currency=GBP</ns2:link>
<ns2:labelTranslations locale="en"/>
<ns2:dictTranslations locale="en">
<ns2:translation>
<ns2:path>ws.currencyType.dict.GBP</ns2:path>
<ns2:content>£</ns2:content>
</ns2:translation>
</ns2:dictTranslations>
</ns2:navigationQuery>
</ns2:navigationQueries>
</ns2:navigationQueryGroup>
<ns2:navigationQueryGroups>

The example image of how the navigation works is placed below. The initial set of data has 4 packs, each pack is described with 2 parameters: tea type and country name. The search results depend on the current selection in the navigation control section. If tea type is selected, that will decrease the number of the results. For example, if user selects the “Black” tea, the results will be “Pack 1” and “Pack 2”.

Navigation Schema

 

Our clients include