Matador Jobs comes with incredible features immediately upon installation, but sometimes you need a little extra. Our goal to make Matador as flexible as possible for you and your business meant we needed to provide a way for you to add additional job fields to your job data. We’re going to show you how.
What Fields Does Matador Import Already?
Before we talk about importing additional fields, let’s cover what Matador already has. We import the following fields to build your typical job page:
- Bullhorn Job ID
- Job Title
- Job Description
- Job Category or Categories
- The Date the Job was Added to Bullhorn
- The Date the Job Listing is Scheduled to Close
- The Status of the Job (ie: Accepting Applications)
- The Address for the Job
- The Client Name, and Web Site
- Various information about compensation including: Type (ie: Contract, Permanent) Pay Rate, Salary and Salary Unit, Benefits, whether Sponsored Relocation is Available, Bonus Package, and Tax Status (ie: W2, 1099).
- Various information about prerequisites, including: Degree (Level) Required, Degree (Type) Required, and Years of Experience Required.
- Data on the assigned users, owners, or public contact for the job so we can optionally send notifications to the recruiters.
- And notes.
Most of that detail is not shown to the user but necessary for building a powerful profile for the job that can be used to improve SEO and search results. Some of this info, isn’t used except when certain settings are turned on, for example, the hiring company name and website.
If you want this information exposed to your users, you or your developer can use the public shortcodes or functions to reveal this information to your users in your website theme or pages.
But what if something is missing? Let’s say your firm wants to highlight jobs for diverse candidates or require certain military experience? You may need to add a custom field to your import.
How to Import an Additional Field
Set Up the Custom Field
First question: does the field exist? If its already in your Bullhorn edit job screens, you’re set. If you need to create it, you should contact Bullhorn support to help you out.
Get the Custom Field Name from Your Field Mappings
This step is advanced, and if you’re unfamiliar with your Field Mappings screen in Bullhorn, it is recommended you ask for assistance from Bullhorn support.
Go into your Field Mappings menu in Bullhorn. If you’re on the “NOVO” UI, this is found by going to
The screenshot below is Matador Job’s test account’s field mappings. While you’re here, you need to find the name of the field in the blue text that matches the label you use to add/update information in that field.
Most custom fields are usually named something that begins with
customText1, but occasionally you may wish to import a Bullhorn-standard field that Matador doesn’t use automatically, like
branchCode for when you wish to style jobs differently based on whether the job is offered out of a New York or LA office.
Add the Filter to Your Site Code
Copy and paste the code from the snippet below to begin your custom field import filter. You can import an unlimited number of fields using this method, but each new field can slow down your site, and we urge caution. Put the code in your Matador Customization file.
Each field should be a key/value array, where the key is the Bullhorn name for the field and the value is an array of arguments.
Each field needs at least two arguments. ‘name’ is the name by which you want Matador to refer to and save the field data. For example, we are importing
customText4 but telling Matador to refer to it as
salaryRange. ‘saveas’ will determine how the data is used by Matador, and to save the data for use in the theme, you should declare it as ‘meta’. Finally, ‘type’ is optional but when passed as ‘string’ or ‘association’ Matador sanitizes the incoming data for security.
Using Your Custom Field Information
You can use the matador_job_field() public function to display custom data from your job or include your custom field in the ‘fields’ args of the
[matador_jobs] shortcodes. You can also use standard WordPress methods of accessing custom fields.