-
-
Notifications
You must be signed in to change notification settings - Fork 496
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
location filter in search_jobs doesn't work #475
Comments
I'm having the same issue did you find any solution ? |
I found a workaround, locationUnion can be used instead of locationFallback, I added to the function the location_id parameter and commented out location_name then I added a new query parameter: You can find a list of IDs here: https://support.captaindata.co/hc/en-us/articles/18071222083485-List-of-GeocodeURN-to-use-in-your-Geography-Parameter Below in detail what I changed in the function:
Then you call the function as follows:
It ended up generating this query:
I hope this can help you |
yep, that´s the workaround I found. It is just very painful to go id by id mapping the location. By countries might be feasible, but if you wanna go more detailed, like cities,..give it up. i tried to figure out which function Linkedin is using to relate location with geoId, but no success |
Hi,
when using search_jobs, it seems that the location filter is ignored.
Notice in the example, location: Berlin
/voyagerJobsDashJobCards?decorationId=com.linkedin.voyager.dash.deco.jobs.search.JobSearchCardsCollection-174&count=10&q=jobSearch&query=(origin:JOB_SEARCH_PAGE_QUERY_EXPANSION,keywords:engineer,locationFallback:Berlin,selectedFilters:(timePostedRange:List(r86400)),spellCorrectionEnabled:true)&start=0
The search returns only results from my current country, not even an accurate location such as the city, (i guess taken from the browser cookies).
Anybody knows how this filter actually works?
The text was updated successfully, but these errors were encountered: