Better search+browse interface

[jace]

Hasjob's browsing interface is non-intuitive. Within a post, there are browse links to the location, job type and category, but there is nowhere to find a list of all locations, all job types or all categories.

Hasjob's header area should be expanded to include filters, and users should be able to narrow down the display directly from there (via drop-down menus), or to pull down a tab that shows a map and a list of job types and categories with job counts for each.

[jace]

By "header", I mean the top-level header, where "Hasjob" and the search box are displayed, not the job description sheet's header.

[shreyas-satish]

Search isn't particularly relevant at times. For instance:

In this example, at least 3 out of the 7 results for 'rails' should've been much lower in the search listing (they had rails mentioned as an additional detail in the job description).

[jace]

We had relevancy based ranking earlier, but that confused people and we got complaints that the results were in random order. Sorting by date shut off those complaints.

Of course, it didn't help that Whoosh's relevancy ranking was mystery sauce.

@aruntestgithub and I attempted NLP to extract keywords from listings and tag them with that, but found this was highly dependent on the quality of the post's grammar. @vivekdurai then suggested using the Hunpos tagger as that provided better results. That is now pending.

[jace]

Related: hasgeek/flask-commentease#7

[vivekdurai]

@jace auto tagging is a problem that requires a classifier that processes a tagged set. that will require more work that just the Hunpos tagger. isnt it better to allow the poster to self-tag and then index and search using elastic search. As a related note the problem of ensuring relevancy and quality of posts may be better solved through social proofing and a upvote/downvote system.

[jace]

@vivekdurai self tagging is going to be as inconsistent as Hunpos, but it does have the advantage of giving the user direct control and rewarding engagement. We'll consider that. We're working out ideas for social proofing.

[jace]

Hasjob has had filtered views for a while. Tagging merits a separate ticket.