Product tier: Available to Expert tier
There are three main data tables / objects in the Business Intelligence Connector data set:
A candidate (person) can submit any number of applications onto any number of jobs (i.e. can apply to any number of jobs, or apply many times to the same job)
Only one application can be submitted for a single job. This information is summarized in the
An individual can also have a prospect application which is a separate record that can be assigned to multiple jobs, departments, or offices. When the prospect is turned into a candidate, a unique candidate record is created. Prospect applications can also be assigned to no jobs, departments, or offices without breaking.
There is a boolean dimension named
prospect on the
applications table which indicates whether an application is an actual application on a job, or is a prospect application.
The candidates in tbl_candidates can be associated with the following candidate-level data tables using the Candidate ID.
The applications in the
applications data table can be associated with the following application-level data tables using the
The jobs in the
jobs data table can be associated with the following job-level data tables using the
Process and Applicant Tracking Data
As applications progress through the recruiting process, the following process and applicant tracking data is generated for each Application ID.
|Moving through stages||The 'application_stages' data table represents each stage of the job that the application can be in, and the enter and exit times for each stage; null data exists for stages that applications have not entered yet.|
Though it is best practice, it is not required to schedule an interview in order to submit a scorecard (thus you can have more scorecards than scheduled interviews).
There are a few stand-alone tables not associated with candidates, applications, or jobs:
User-level data tables
Candidate_surveys (responses are anonymous)
Every other data table is a simple mapping table that maps an ID number to the name of the item represented (e.g., the 'attributes' data table maps an Attribute ID to the name of the attribute).