Locations, such as city-names could be extracted and added as facet.
A toot does not have location data, but city-names, or areas or agglomarations might show up in the toot. As well as the word "remote".
We could use a database with city-names, and check against that. Some false positives might occur, such as city called "job" that might show up. For that we might need a follow-up feature to deny certain "cities".
When I index this, and I search for "java"
Then I expect a block "region" to appear with the facets "Grand Est", "Nancy", "Metz" and "Luxembourg"
Given a toot with content:
I have an immediate hire position for a Major Incident Manager through TCS. It's fully remote, working for Walgreen's. I'm being moved off the team to another project and need a replacement. #GetFediHired
When I index this, and I search for "TCS"
Then I expect a block "region" to appear with the facet "remote"
If yes, localize it. As a german speaking user I don't feel addressed by the job search.
...
Flockingbird @flockingbird
When you say "localize"do you mean the entire search page? Or just the toots it indexes? Or a feature to "filter only german" or so?
The last one is planned, the second one already implemented (but must be fine-tuned for german) and the first could be put on the backlog.
What do you think?
sadmin
@sadmin@social.tchncs.de
@flockingbird I'd expect a german user interface with a filter based on german cities/regions. With the filter applied only toots appear that advertise jobs in that region. For the language of the toots itself I have no preference. I'd recommend not to exclude english toots that contain job descriptions for jobs in german cities since this is pretty common.
Locations, such as city-names could be extracted and added as facet.
A toot does not have location data, but city-names, or areas or agglomarations might show up in the toot. As well as the word "remote". We could use a database with city-names, and check against that. Some false positives might occur, such as city called "job" that might show up. For that we might need a follow-up feature to deny certain "cities".
given a toot with content:
When I index this, and I search for "linke" Then I expect a block "region" to appear with the facet "Berlin"
Given a toot with content:
When I index this, and I search for "java" Then I expect a block "region" to appear with the facets "Grand Est", "Nancy", "Metz" and "Luxembourg"
Given a toot with content:
When I index this, and I search for "TCS" Then I expect a block "region" to appear with the facet "remote"