Loxo Source gives you flexibility, accuracy, and control of your search and can be maximized with the full power of Boolean. Boolean strings are one of the best ways to identify the top echelon of your candidates for each job. Continue reading to learn more about how to best use Boolean with fields in Loxo Source.
You can read more about Boolean Basics to get started. This article outlines more advanced Boolean strings to use when searching in Loxo Source.
Searchable Fields in Loxo Source
In the table below, you'll see all of the fields that you can search using Boolean within Loxo Source. Each field has a specific Boolean reference name that works in the Boolean search bar.
When you search these specific fields in Loxo Source using those specific Boolean reference names, you are searching only the entries in those fields, instead of keywords across a full profile.
For example, you could search Loxo Source for people who have had the title of "VP of Sales" in any of their current or previous roles. To do that, you would enter the following string:
experience_titles:"VP of Sales"
Or you could search Loxo Source for people with the current title of VP of Sales. That Boolean string would look like:
current_experience_titles:"VP of Sales"
The above two searches are different than just typing "VP of Sales" into the keyword/boolean search box because they are searching specifically past title and current title fields only. Without specifying which field you're looking for the results in, the search will scan the entire profile for the keywords.
Utilizing these types of boolean will return you results with your keywords in them, not strictly just those titles. For example "VP of Sales" may return you "VP of Sales and Marketing." As long as your keyword in is the title, the profile will be shown.
So, how do you know the specific Boolean field names in Loxo?
Listed below are the most common fields that you can use for Boolean searches in Loxo Source. One key formatting tip to keep in mind when conducting such searches: there is no space after the colon.
field_name:"search words"
Boolean Field Names |
|
name first_name last_name description education_organizations education_credentials education_start_dates education_end_dates experience_titles experience_company_names experience_descriptions current_experience_titles current_experience_company_names current_experience_descriptions | past_experience_titles past_experience_company_names past_experience_descriptions past_experience_company_names skills npi certification_display_names certification_institutions gender specialties credentials languages |
Refining Boolean Search Results
To further refine and enhance your search results, there are additional Boolean syntaxes you can use:
Quotation Marks " ": Use these for exact phrases. For example, searching "Java Script" ensures results contain this exact phrase, whereas typing Java Script without the quotations could return results for either word (java or script).
Parentheses ( ): These are used to group alternative terms together. For example, typing (java OR python) groups these terms as one unit in the search.
They are also the secret sauce to a great Boolean search. As your queries get longer, parentheses are as necessary to the structure of your search as the location of your Boolean operators.For example, if your query looks like this:
java AND (web development OR multithreading OR databases) NOT "CI/CD" OR "Python" OR "memory manag*"
The above string will only use the NOT operator to exclude the "CI/CD" entry, and you will get very different results compared to using parentheses around all of the OR logic added after NOT, as shown below:
java AND (web development OR multithreading OR databases) NOT ("CI/CD" OR "Python" OR "memory manag*")
Asterisk (*): This acts as a wildcard. It's useful for capturing various forms of a word. For example, "memory manag*" will find both singular and plural forms as well as variations in the ending, such as "memory management" and "memory managing."
Related Topics