Location Display Behavior

Duplicate Location Display Solution

Administrators define the location levels in Sourcing using the Location User Preference setting, Configuration > Users > [User Settings]. Previously, if the location data that came over from SmartOrg had levels below what was defined in Sourcing, Sourcing would show multiple, duplicate locations representing those lower levels. If, for example, Sourcing was configured with Country, State and City (US, CA, San Francisco) and SmartOrg went a level below that (Country, State, City, Address), each location with a different address would show as a duplicate result, displaying only as US, CA, San Francisco;  Sourcing hid the children. If US, CA, San Francisco had Folsom Street, Lombard Street and Post Street in SmartOrg, Sourcing displayed US, CA, San Francisco three separate times. Now, there are no more duplicate locations representing the elements on the hidden level. Selecting the parent will include the elements for all its children resolving duplicate locations being listed for levels lower than the Location User Preference setting in Sourcing.

Places within Sourcing where this is resolved include:

  • Job Search (with Geolocation Search disabled)

  • Location Selector on Sign-Up page

  • Location Facet in Job Search

  • Location Facet in Campaigns

  • Preferred Locations on Settings page

  • Preferred Locations on Job Alerts sign-up

  • Location picklist in Analytics

Increased Location Display

The limit for the location list in Sourcing is 9,999. Organizations with even larger location tables and a need for more than 9,999 locations may contact Oracle Support and log a Service Request to increase their limit.

Display Jobs on Children of Search String

If users are searching for jobs with Geolocation Search disabled, historically an exact match of the search string must be entered to find jobs in that location. However, now we've added children to the search results of the exact matches for the levels configured in the Location User Preference setting. For example, if the Location User Preference has been configured for the Country, State and City levels (US, CA, San Francisco), and there are children of that string, i.e., Address levels (US, CA, San Francisco, Folsom Street), those children of exact matches are now included in the search results as well.

Note: For performance reasons, when the location searched has fewer levels than the Location User Preference configuration and is higher in the location tree, rather than a child, then it is still the case that only the jobs of an exact match are surfaced.