-
Web developers; have you made a reasonably complicated website (e.g. CRM, ERP, SCM, etc), and successfully implemented a search function?
Yes.
If search is added as an afterthought though, why bother adding it at all? People have pretty high expectations of the ol' text search box. Anything less than 'pretty darn good' is probably not worth bothering with.
Of course, if it's a priority feature, then chuck some money at it and do it right, but as you hint, it's not really something you can hand-roll. If search is a priority, high value feature, then the app needs to be structured with that in mind.
-
Has anyone had success/experience with Lucene or similar?
All the cool kids are using Elasticsearch. Like howard says, rolling your own is for chumps. Get your devs up to speed on Elastic integration, use it for everything, then use the many, many weeks of work that you'll have saved to go down the pub for non-stop celebratory beers.
-
Slow reply, but this very site uses PostgreSQL and the built-in search engine. It's the same search engine that powers Wikipedia.
The only difficult thing in adding search is structuring the search priorities and ensuring that results only contain things you are allowed to view (permissions filtered).
It's basically trivial to add search to a site if the database is PostgreSQL.
You are reading a single comment by @cyclotron3k and its replies.
Click here to read the full conversation.
Howard
bothwell
Velocio
@cyclotron3k
Web developers; have you made a reasonably complicated website (e.g. CRM, ERP, SCM, etc), and successfully implemented a search function?
The last two projects I've been on, search has been a bit of an after-thought. For the developer the code tends to be an unmaintainable and organic mess, and for the end user, the results are poor and often very slow to return.
Has anyone had success/experience with Lucene or similar?