[ghall]

Thank you! Would it be more helpful to break this into separate repos by every geography? We have a "remote" folder at the moment: https://github.com/zcor/githubjobs/tree/master/remote

[yayajacky]

Thanks for replying, I saw the remote folder, that’s a good direction, I just don’t know if with github I can watch that single folder for communication.

- from a remote contractor

[gwbas1c]

The problem is that job openings are often for multiple locations. (You can work in our SF or NYC offices.)

In general: Try to avoid organizing your data in hierarchies, and instead navigate by filters. (This is why SQL won over older hierarchal databases.)

[ghall]

We've also been talking about in organizing this into a SQL-like interface, I think there could be a lot of value in job hunting in such a manner... "SELECT * FROM jobs WHERE location = 'seattle' and keyword LIKE '%python%'"

[yayajacky]

If the keyword column is a json blob, you might be able to do it with JSON_CONTAINS:

https://dev.mysql.com/doc/refman/8.0/en/json-search-function...

(Unless you are using mongo on the backend, in which case I am not familiar with that)