Have "State" as a filter option instead of "City, State" about career-portal HOT 12 CLOSED

Hey, @therealjeffix—

This would be a really neat idea to see come to life. Having custom taxonomies could really reveal some new possibilities to this app. Likely this change would require a solution UI-side. I see that you tried changing the query on the backend, but I don't believe we support that. Have you tried solving this client-side (i.e. via Angular)?

Thanks!
K.

from career-portal.

I agree - we have thousands of open positions all over the country. One thing we do on our custom Bullhorn job portal is a zip code radius search if you enter a city/state or a zip code. This helps grab those positions in the same metro area with a different city name.

We use this REST service as a helper:https://www.zipcodeapi.com/

from career-portal.

@krsween thanks, good to know query changes aren't supported. We looked into aggregating the data post-query into States and ran into a few issues, but we'll give it another go.

from career-portal.

@krsween lets say the user selects "Texas" from the filter list, we have to query for each city in Texas, then merge the results. This also led to 400 Bad Request errors (some kind of throttle or request frequency capping?).

Is this the type of UI-side solution you are suggesting or would you approach it differently?

from career-portal.

Hi, @therealjeffix

I was investigating the issue you reported and noticed that the where clause that you are using has an extra ')'. You have (isOpen = true) AND (address.state='AL')), but it should be (isOpen = true) AND (address.state='AL'). Perhaps fixing this will return the results you want. I hope this helps.

from career-portal.

Hey, @therealjeffix —
The team here swarmed and it looks like there is an API that can return data by state—contrary to my understanding! (Way to go @acrowe2!)

I think this solves a part of the problem in that the initial step of aggregating a series of state queries (by state) may no longer be needed, which gets around API limitations too as there are fewer queries.

Does this level of custom taxonomies solve the entire scope of the problem, or is there a need to have an additional layer on top of this?

K.

from career-portal.

@acrowe2 @krsween let me attempt and get back to you, thanks for looking at this.

Custom taxonomies would be a cool feature, but for now grouping by state will be all I need.

from career-portal.

Our pleasure! Let us know how this goes. I'm going to resolve this issue for now.

from career-portal.

Got it up and running. Thanks again!

from career-portal.

@therealjeffix Can I ask where you go to edit the query? I only have access to this github for a client project, what other access do I need to see backend information? Is this access Bullhorn where they submit job postings to be published?

from career-portal.

@whreed You can edit the query from the app-<###>.js file (in this GitHub repository). If you want access to your client's Bullhorn CRM you'll need to request that from your client, this repository is not the same as access to the software account.

from career-portal.

Do you care to share how you got it to just show states on the side but still keeps city state in the job listing?

from career-portal.