Purpose of this document

This article introduces users to the Eightfold (EF) Workforce Exchange (WFX) Admin Dashboard, including a general overview of the dashboard, information about each dashboard feature, and the benefits of using the dashboard.

Audience

This article is directed toward users of the Workforce Exchange (WFX) Admin Dashboard, usually the admins of the exchange.

Background: Dashboard purpose

The Workforce Exchange (WFX) Admin Dashboard is designed for the following purposes:

• Inform talents activities on the exchange (sign up, job search, applications, etc.)
• Inform case manager activities on the exchange.
• Inform hiring company activities on the exchange.
• Provide job inventory insights.

Tabs overview

• Talents: Sign up & Log in: Provides metrics on visitors, sign up, sign up onboarding flow, etc. of the talents who came to the Exchange.
• Talents: Job Activities: Provides metrics on job search and application activities of the talents and enables dashboard users to slice and dice the data by the demographics and geographics of the talents.
• Case Manager Activities: Provides metrics on case manager (career supporters) activities, including adding and editing talents profiles, job sharing with talents, etc.
• Job Inventory: Provides metrics on jobs posted on the Exchange, including the ones posted directly by the hiring companies and the ones pulled in from job repositories such as NLX.
• Hiring Company Activities: Provides metrics on hiring companies’ activities on the Exchange, including posting jobs and communicating with the talents. It provides job search and application metrics on jobs posted directly by hiring companies.
• Skills: Provides insights on the ‘supply of the skills’ (skills that the talents have), ‘demand of the skills’ (skills that the hiring companies require for their positions), and the ‘supply vs demand of the skills’.

Filter Controls

Dashboard filter controls can be used to refine or subset the data shown in the dashboard. For example, to exclude data from a particular region in a dataset, or to select a certain date range.

Filter controls are located at the top of the dashboard.

Figure 1: Dashboard Controls Overview

The following filter controls are applied to the dashboard:

Activity Date (from - to)

Activity date is the date on which the user performed a certain activity (e.g., create an account, upload a resume, apply for a job). ‘Activity date From - To’ filters control the date range of all charts.

Position Creation/Ingestion Date (from - to)

The position creation date is the date on which the position was created by the hiring companies (who post directly on the Exchange).

Position ingestion date is the date when the position was ingested from a job repository like the NLX.

Time Series Charts Aggregation Level

This control controls the aggregate level of time series charts: weekly, monthly, and quarterly.

For example, when ‘weekly’ is selected, the ‘Accounts created overtime’ chart will show ‘the number of accounts created by week’; if switched to ‘monthly’, the chart will show ‘the number of accounts created by month’ instead.

This control only applies to time series charts.

Figure 2: Time Series Charts Aggregation Level

Breakdown variable

This control controls the breakdown dimension of related tables.

For example, in the ‘Job views by {breakdown variable}’ table on tab ‘Talents - Job Activities’, when ‘Profile Location City’ is selected in the control, the table will show ‘job views by profile location city’; if the control selection is switched to ‘profile gender’, the table will show ‘job views by gender’.

This control only applies to selected tables. The variable selection could be different on different tabs.

Figure 3: Breakdown variable

Figure 4: Breakdown variable - Profile Location City

Figure 5: Breakdown variable - Profile Gender

Job Source (for job activity charts)

This filter control is related to the ‘source’ of the job posted on the Exchange: whether it was posted directly by the hiring company, or it was pulled from a repository like the NLX. For example, if ‘hiring company’ is selected, only the activities on jobs posted directly by hiring companies will be shown on the tab.

Case manager (Case Manager Activity tab)

This filter control filters for specific names of the case managers and shows only the case manager activities of the case manager(s) selected.

Profile - location city/education level/gender/race

This controls which profiles (talents) to be shown based on their location city/education level/gender/race.

Please note that this is information about the profile (talents), not the positions.

Metrics and dimensions calculation

Total citizens (talents) - all time

• Description: Total number of talent profiles that got loaded into the platform, plus talents who joined via the virtual career center.
  • Not all of these talents have created an account on the Exchange or have used the Exchange.
  • Showing all time data. The date range filter is not applicable to this metric.

• Used in tab(s):
  

  • Talents - Sign Up & Log In

• Formula in Quicksight calculation:

  • distinct_count({candidate_id})

• Dataset(s):

  • positions_aggregated

Unique visitors (talents)

• Description: Total number of visitors (talents) on the Exchange, including logged-in and logged-out visitors.
  • Each visitor is identified by ‘vs_cookie’, because logged-out users do not have their user email recorded.
  • Caveat: if a person switched browser/device or cleared their cookies, there will be a new ‘vs_cookie’ assigned to them and this person will be counted twice.

• Used in tab(s):
  

  • Talents - Sign Up & Log In

• Formula in Quicksight calculation:

  • distinct_count({vs_cookie})

  • Filter applied: {namespace} in (‘career_hub’, ‘career_hub_candidate’, ‘career_login’, ‘talent_exchange’)

• Dataset(s):

  • server_log_profile_position_aggregated

Accounts created (talents)

• Description: Number of accounts created on the Exchange. Talents can create an account themselves, or the case managers can create an account for the talents.
  • ‘Account creation by source’ shows whether the account was created by the talent themselves or by the case managers.

• Used in tab(s):
  

  • Talents - Sign Up & Log In

• Formula in Quicksight calculation:

  • distinct_count({candidate_email_id})

  • Filter applied: {account_creation_source} does not equal 'Not account creation event'

• Dataset(s):

  • server_log_profile_position_aggregated

Logged-in users (talents)

• Description: Number of talents logged into the Exchange.
• Used in tab(s):
  • Talents - Sign Up & Log In

• Formula in Quicksight calculation:

  • distinct_count({user_email})

  • Filter applied: {Cleaned event map (general)} equals 'Logged In Users'

• Dataset(s):

  • server_log_profile_position_aggregated

Resume upload (talents)

• Description: Number of talents who have resumes uploaded to the Exchange. Talents can upload resumes to the Exchange themselves, or the case managers can upload the resume for the talents.
  • ‘Resume upload by source’ shows whether the resume upload was done by the talents themselves or by the case managers.

• Used in tab(s):
  

  • Talents - Sign Up & Log In

• Formula in Quicksight calculation:

  • distinct_count({request_path})

  • Filter applied: {Cleaned event map (general)} equals 'resume uploads'

• Dataset(s):

  • server_log_profile_position_aggregated

% Profiles with activation flow initiated (talents)

• Description: Number of profiles initiated the profile activation flow, divided by the total number of profiles with an account created in the selected date range.
  • The profile activation flow is a widget that allows talents to build their profiles by filling in their basic information, preferences, work experience and education, etc.
  • The talents can fill in information in the activation flow themselves, or the case managers can fill in for the talents.
  • This widget shows up during the first time the talent logs into the Exchange. After that users can go to the talent’s profile page to make modifications.

• Used in tab(s):
  

  • Talents - Sign Up & Log In

• Formula in Quicksight calculation:

  • distinct_countIf({activation flow funnel profiles count}, event='profile_edit_metadata_wizard_step0' and (namespace='career_hub_candidate' or namespace='career_hub'))

    / distinct_countIf({candidate_email_id (account creation)}, {account_creation_source} <> 'Not account creation event')

• Dataset(s):

  • server_log_profile_position_aggregated

% Completed profiles (talents)

• Description: Number of profiles who finished the last step in the profile activation flow, divided by the total number of profiles with an account created in the selected date range.
• Used in tab(s):
  • Talents - Sign Up & Log In

• Formula in Quicksight calculation:

  • distinct_countIf({activation flow funnel profiles count}, event='profile_edit_education_wizard_step3' and (namespace='career_hub_candidate' or namespace='career_hub'))

    / distinct_countIf({candidate_email_id (account creation)}, {account_creation_source} <> 'Not account creation event'

• Dataset(s):

  • server_log_profile_position_aggregated

Job views (talents)

• Description: Number of jobs viewed by talents on the exchanges. Talents can view jobs in logged-in or logged-out state.
  • If the same talent views the same job (position_id) more than once, it will only be counted as 1 job view. For example:
    • Talent has viewed position A twice: counted as 1 job view.
    • Talent has viewed position A once and position B once: counted as 2 total job views.
    • Talent has viewed position A twice and position B twice: counted as 2 total job views.

  
  

• Used in tab(s):
  

  • Talents - Job Activities

• Formula in Quicksight calculation:

  • To count logged-in and logged-out combined:
    

    • distinct_countIf(concat(toString({vs_cookie}), '-', toString({position_id})), {Cleaned event map (general)}='Job views')
    
    

  • To count logged-in only:
    

    • distinct_countIf(concat(toString({user_email}), '-', toString({position_id})), {Cleaned event map (general)}='Job views' AND namespace = 'career_hub_candidate')
      

      • With filter: {user_email} exclude (‘loggedout@none.com’, ‘logged_out_candidate@test.com’)
      
      
    
    

  • Both with filter: {incl talents only} = 1
    

    • ifelse(locate(toLower({user_email}), '@test.com') >= 1 AND {user_email} <> 'logged_out_candidate@test.com', 0, {group_id} <> '@test.com', 0,1)
    
    
  
  

• Dataset(s):

  • server_log_profile_position_aggregated

Unique job viewers (talents)

• Description: Similar as ‘Job views’, but count unique talents: number of unique talents who have viewed jobs. Talents can view jobs in logged-in or logged-out state.
• Used in tab(s):
  • Talents - Job Activities

• Formula in Quicksight calculation:

  • To count logged-in and logged-out combined:
    

    • distinct_countIf({vs_cookie},{Cleaned event map (general)}='Job views')
    
    

  • To count logged-in only:
    

    • distinct_countIf({user_email},{Cleaned event map (general)}='Job views' AND namespace = 'career_hub_candidate')
      

      • With filter: {user_email} exclude (‘loggedout@test.com’, ‘logged_out_candidate@test.com’)
      
      
    
    

  • Both with filter: {incl talents only} = 1
    

    • ifelse(locate(toLower({user_email}), '@test.com') >= 1 AND {user_email} <> 'logged_out_candidate@test.com', 0, {group_id} <> '@test.com', 0,1)
    
    
  
  

• Dataset(s):

  • server_log_profile_position_aggregated

Apply clicks (talents)

• Description: Number of apply clicks (click on the ‘Apply’ button on each job post) by talents on the exchanges. Talents can click apply in a logged-in or logged-out state.
  • If the same talent clicks apply on the same job (position_id) more than once, it will only be counted as 1 apply click. For example:
    • Talent has clicked apply on position A twice: counted as 1 apply click.
    • Talent has clicked apply on A once and position B once: counted as 2 total apply clicks.
    • Talent has clicked apply on position A twice and position B twice: counted as 2 total apply clicks.

  
  

• Used in tab(s):
  

  • Talents - Job Activities

• Formula in Quicksight calculation:

  • To count logged-in and logged-out combined:
    

    • distinct_countIf(concat(toString({vs_cookie}), '-', toString({position_id})), {Cleaned event map (general)} = 'Job apply clicks')
    
    

  • To count logged-in only:
    

    • distinct_countIf(concat(toString({user_email}), '-', toString({position_id})), {Cleaned event map (general)}='Job apply clicks' AND {user_email} <> 'loggedout@none.com')
      

      • With filter: {user_email} exclude (‘loggedout@none.com’, ‘logged_out_candidate@test.com’)
      
      
    
    

  • Both with filter: {incl talents only} = 1
    

    • ifelse(locate(toLower({user_email}), '@test.com') >= 1 AND {user_email} <> 'logged_out_candidate@test.com', 0, {group_id} <> 'test.com', 0,1)
    
    
  
  

• Dataset(s):

  • server_log_profile_position_aggregated

Unique users clicked ‘Apply’ (talents)

• Description: Similar to ‘Apply clicks’, but count unique talents: number of unique talents who have clicked apply. Talents can click apply in a logged-in or logged-out state.
• Used in tab(s):
  • Talents - Job Activities

• Formula in Quicksight calculation:

  • To count logged-in and logged-out combined:
    

    • distinct_countIf({vs_cookie}, {Cleaned event map (general)} = 'Job apply clicks')
    
    

  • To count logged-in only:
    

    • distinct_countIf({user_email}, {Cleaned event map (general)}='Job apply clicks' AND {user_email} <> 'loggedout@none.com')
      

      • With filter: {user_email} exclude (‘loggedout@none.com’, ‘logged_out_candidate@test.com’)
      
      
    
    

  • Both with filter: {incl talents only} = 1
    

    • ifelse(locate(toLower({user_email}), '@test.com') >= 1 AND {user_email} <> 'logged_out_candidate@test.com', 0, {group_id} <> 'test.com', 0,1)
    
    
  
  

• Dataset(s):

  • server_log_profile_position_aggregated

Job apply click rate (talents)

• Description: Number of apply clicks divided by number of job views.
• Used in tab(s):
  • Talents - Job Activities

• Formula in Quicksight calculation:

  • To count logged-in and logged-out combined:
    

    • {Total job apply clicks (loggedout + loggedin)} / {Total Job Views (loggedout + loggedin users)}
    
    

  • To count logged-in only:
    

    • {Apply clicks (logged-in)}/{Job views (logged-in)}
      

      • With filter: {user_email} exclude (‘loggedout@none.com’, ‘logged_out_candidate@test.com’)
      
      
    
    

  • Both with filter: {incl talents only} = 1
    

    • ifelse(locate(toLower({user_email}), '@test.com') >= 1 AND {user_email} <> 'logged_out_candidate@test.com', 0, {group_id} <> 'test.com', 0,1)
    
    
  
  

• Dataset(s):

  • server_log_profile_position_aggregated

% users clicked ‘Apply’ (talents)

• Description: Number of unique users who clicked apply divided by number of unique users who viewed jobs.
• Used in tab(s):
  • Talents - Job Activities

• Formula in Quicksight calculation:

  • {Unique users clicked Apply (loggedout + loggedin)}/{Unique Job Viewers (loggedout + loggedin users)}

  • With filter: {incl talents only} = 1
    

    • ifelse(locate(toLower({user_email}), '@test.com') >= 1 AND {user_email} <> 'logged_out_candidate@test.com', 0, {group_id} <> 'test.com', 0,1)
    
    
  
  

• Dataset(s):

  • server_log_profile_position_aggregated

Application submission (talents)

• Description: Number of applications submitted.
  • For positions posted directly by hiring companies, application submission happens in the logged-in Exchange.
  • For positions ingested from repositories such as the NLX, application submission happens outside of Eightfold Exchange, and hence cannot be tracked in Eightfold data.

• Used in tab(s):
  

  • Talents - Job Activities

• Formula in Quicksight calculation:

  • distinct_countIf(concat(toString({user_email}), '-', toString({position_id})), {Cleaned event map (general)}='Job applications')

  • With filters:

    • {incl talents only} = 1
      

      • ifelse(locate(toLower({user_email}), '@test.com') >= 1 AND {user_email} <> 'logged_out_candidate@test.com', 0, {group_id} <> 'test.com', 0,1)
      
      

    • {user_email} exclude (‘loggedout@none.com’, ‘logged_out_candidate@test.com’)
    
    
  
  

• Dataset(s):

  • server_log_profile_position_aggregated

Unique job applicants (talents)

• Description: Similar as application submission, but count unique talents: unique talents who have submitted applications on the Eightfold Exchange.
• Used in tab(s):
  • Talents - Job Activities

• Formula in Quicksight calculation:

  • distinct_countIf(concat(toString({user_email}), '-', toString({position_id})), {Cleaned event map (general)}='Job applications')

  • With filters:
    

    • {incl talents only} = 1
      

      • ifelse(locate(toLower({user_email}), '@test.com') >= 1 AND {user_email} <> 'logged_out_candidate@test.com', 0, {group_id} <> 'test.com', 0,1)
      
      

    • {user_email} exclude (‘loggedout@none.com’, ‘logged_out_candidate@test.com’)
    
    
  
  

• Dataset(s):

  • server_log_profile_position_aggregated

Application completion rate (talents)

• Description: Number of applications submitted divided by number of apply clicks. Application submission data is only available for positions directly posted by hiring companies. Counting job activities in logged-in Exchange only.
• Used in tab(s):
  • Talents - Job Activities

• Formula in Quicksight calculation:

  • {Application submission (logged-in)} / {Apply clicks (logged-in)}

  • With filters:
    

    • {incl talents only} = 1
      

      • ifelse(locate(toLower({user_email}), '@test.com') >= 1 AND {user_email} <> 'logged_out_candidate@test.com', 0, {group_id} <> 'test.com', 0,1)
      
      

    • {user_email} exclude (‘loggedout@none.com’, ‘logged_out_candidate@test.com’)
    
    
  
  

• Dataset(s):

  • server_log_profile_position_aggregated

Avg march score (talents)

• Description: The match score of each job related to the talent’s profile; showing match score of the jobs viewed and the jobs applied to by the talents. Range of the match score is 0 to 5.
• Used in tab(s):
  • Talents - Job Activities

• Formula in Quicksight calculation:

  • N/A

• Dataset(s):

  • server_log_profile_position_aggregated

Case managers logged-in (case managers)

• Description: Number of case managers logged in to the Exchange.
• Used in tab(s):
  • Case Manager Activities

• Formula in Quicksight calculation:

  • distinct_count({user_email})

  • With filters:
    

    • {Cleaned event map (general)} equals 'Case Manager Logins'
    
    
  
  

• Dataset(s):

  • server_log_profile_position_aggregated

Case managers with any talent related activities (case managers)

• Description: Number of case managers who have performed any of the following actions on Exchange: add a candidate, view a talent profile, edit a candidate profile, upload a talent resume, add notes to a profile, share jobs.
• Used in tab(s):
  • Case Manager Activities

• Formula in Quicksight calculation:

  • distinct_countIf({user_email}, {case_manager_ind}=1 AND {Cleaned event map (case manager)} <> 'Other')

• Dataset(s):

  • server_log_profile_position_aggregated

Case managers added a candidate (case managers)

• Description: Number of case managers who have added a candidate.
• Used in tab(s):
  • Case Manager Activities

• Formula in Quicksight calculation:

  • distinct_countIf({user_email},{Cleaned event map (case manager)}='Added a candidate')

  • To calculate the number of talents added: distinct_countIf({event},{Cleaned event map (case manager)}='Added a candidate')

• Dataset(s):

  • server_log_profile_position_aggregated

Case managers viewed a profile (case managers)

• Description: Number of case managers who have viewed the profile of a talent.
• Used in tab(s):
  • Case Manager Activities

• Formula in Quicksight calculation:

  • distinct_countIf({user_email},{Cleaned event map (case manager)}='Viewed a candidates profile')

  • To calculate the number of talents profiles that were viewed: distinct_countIf(concat({referrer_path}," - ",{user_email}) ,{Cleaned event map (case manager)}='Viewed a candidates profile')

• Dataset(s):

  • server_log_profile_position_aggregated

Case managers edited candidate profile (case managers)

• Description: Number of case managers who have edited a talent’s profile.
• Used in tab(s):
  • Case Manager Activities

• Formula in Quicksight calculation:

  • distinct_countIf({user_email},{Cleaned event map (case manager)}='Edited a candidates profile')

  • To calculate the number of talents profiles that were edited: distinct_countIf(concat({referrer_path}," - ",{user_email}) ,{Cleaned event map (case manager)}='Edited a candidates profile')

• Dataset(s):

  • server_log_profile_position_aggregated

Case managers added note (case managers)

• Description: Number of case managers who have added notes to a talent.
• Used in tab(s):
  • Case Manager Activities

• Formula in Quicksight calculation:

  • distinct_countIf({user_email},{Cleaned event map (case manager)}='Added profile notes')

  • To calculate the number of talents profiles with notes added: distinct_countIf(concat({referrer_path}," - ",{user_email}) ,{Cleaned event map (case manager)}='Added profile notes')

• Dataset(s):

  • server_log_profile_position_aggregated

Case managers uploaded resume (case managers)

• Description: Number of case managers who have uploaded resumes for talents.
• Used in tab(s):
  • Case Manager Activities

• Formula in Quicksight calculation:

  • distinct_countIf({user_email},{Cleaned event map (case manager)}='Uploaded a candidates resume')

  • To calculate the number of talents profiles with resumes uploaded by case manager: distinct_countIf(concat({referrer_path}," - ",{user_email}) ,{Cleaned event map (case manager)}='Uploaded a candidates resume')

• Dataset(s):

  • server_log_profile_position_aggregated

Case managers shared a job (case managers)

• Description: Number of case managers who shared jobs with talents.
• Used in tab(s):
  • Case Manager Activities

• Formula in Quicksight calculation:

  • distinct_countIf({user_email},{Cleaned event map (case manager)}='Shared a job')

• Dataset(s):

  • server_log_profile_position_aggregated

Job shares (case managers)

• Description: Number of jobs shared by case managers. If the same job is shared to the same talent multiple times, it is counted as 1 job share.
• Used in tab(s):
  • Case Manager Activities

• Formula in Quicksight calculation:

  • distinct_countIf(concat(toString({position_id}), '-', toString({referrer_path})), namespace= 'career_hub' AND event='position_share_position')=

• Dataset(s):

  • server_log_profile_position_aggregated

Total logged-in users of hiring companies (hiring companies)

• Description: Number of users of the hiring companies logged in to the Exchange.
• Used in tab(s):
  • Hiring Company Activities

• Formula in Quicksight calculation:

  • distinct_count({user_email})

  • With filters:

    • {group_id)} contains 'eightfoldemployer'
    
    
  
  

• Dataset(s):

  • server_log_profile_position_aggregated

Users viewed talent profile (hiring companies)

• Description: Number of users of the hiring companies who have viewed a candidate’s profile.
• Used in tab(s):
  • Hiring Company Activities

• Formula in Quicksight calculation:

  • distinct_countIf({user_email}, {Cleaned event map (hiring company)} = 'View Profile')

  • With filters:
    

    • {group_id)} contains 'eightfoldemployer'
    
    

  • To calculate the number of candidate profiles viewed by a hiring company: distinct_countIf({request_path}, {Cleaned event map (hiring company)} = 'View Profile')

• Dataset(s):

  • server_log_profile_position_aggregated

Users viewed talent resume (hiring companies)

• Description: Number of users of the hiring companies who have viewed a candidate’s resume.
• Used in tab(s):
  • Hiring Company Activities

• Formula in Quicksight calculation:

  • distinct_countIf({user_email}, {Cleaned event map (hiring company)} = 'View Profile Resume')

  • With filters:
    

    • {group_id)} contains 'eightfoldemployer'
    
    

  • To calculate the number of candidates whose resume was viewed by a hiring company: distinct_countIf({request_path}, {Cleaned event map (hiring company)} = View Profile Resume')

• Dataset(s):

  • server_log_profile_position_aggregated

Users contacted talent (hiring companies)

• Description: Number of users of the hiring companies who have contacted a candidate.
• Used in tab(s):
  • Hiring Company Activities

• Formula in Quicksight calculation:

  • distinct_countIf({user_email}, {Cleaned event map (hiring company)} = 'Contact Talent')

  • With filters:
    

    • {group_id)} contains 'eightfoldemployer'
    
    
  
  

• Dataset(s):

  • server_log_profile_position_aggregated

Total open & posted positions (job inventory)

• Description: Number of currently open and posted positions created in the selected date range.
  • For positions directly posted by hiring companies, this is the number of positions that were created in the selected date range, and currently have status ‘open’ or ‘active’.
  • For positions ingested via job repositories such as the ‘NLX’, this is the number of positions that were ingested into the Exchange in the selected date range, and currently have status ‘open’ or ‘active’.
    • Positions not present in the last ingestion are considered 'closed'/'inactive' and thus deleted from the EF database - no longer reported in the dashboard.
    • Positions without a valid ‘hiring company’ name are also not posted in the Exchange or reported in the dashboard.

  • The date range applied to this metric is ‘position creation date or posted date’.

  • For both types of positions, positions with creation/ingestion date larger than 180 days are no longer posted on the Exchange and therefore not reported in the dashboard anymore.

• Used in tab(s):
  

  • Job inventory

• Formula in Quicksight calculation:

  • distinct_count({position_id})

• Dataset(s):

  • positions_aggregated

Talent skills (skills)

• Description: Skills reported by talent (parsed from resume or manually added by talent or case manager). Skills of the talents are considered as the ‘supply’ of the skills in the Exchange.
• Used in tab(s):
  • Skills

• Formula in Quicksight calculation:

  • N/A

• Dataset(s):

  • profile_skills_and_position_skills

Position required skills (skills)

• Description: Skills required by each of the positions in the Exchange (from position calibration, etc.). Position required skills are considered as the ‘demand’ of the skills in the Exchange.
• Used in tab(s):
  • Skills

• Formula in Quicksight calculation:

  • N/A

• Dataset(s):

  • profile_skills_and_position_skills

Datasets

profile_aggregated

This dataset contains all the talent profiles on the Exchange and provides various information of each profile: creation_ts, gender, race, email, etc.

profile_skills_and_position_skills

This dataset contains 2 sets of information: skills of talents and skills required by positions. It is built by the ‘profile skills’ unioning the ‘position skills’.

Figure 6: Profile Skills and Position Skills

positions_aggregated

This dataset contains all the positions posted on the WFX and provides various information of each position: title, creation timestamp, locations, etc. Various group ids are included: hiring company group ids, nlxjobs.com, etc.

server_log_profile_position_aggregated

This dataset provides server log data, which are the user activities data for different personas on the Exchange (talents, case managers, hiring companies); it joins with the profile_aggregated view and positions_aggregated view to provide more insights on these user behaviors.

Figure 7: Server Log Profile Position Aggregated

Frequently asked questions

No frequently asked questions.