o0111 / ruralcafe

Automatically exported from code.google.com/p/ruralcafe
0 stars 0 forks source link

Add a snippet from search result page for each search result #1

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Snippet of result in search results would help a lot to avoid dumb links. 
Currently the search results just show the URL result and the page title.

Since the Lucene index doesn't have the content stored, to implement this the 
actual page would probably need to be opened in the cache and the snippet 
containing the search terms should be returned. This would be pretty slow for a 
lot of results. If we also reduce the number of search results returned to 10 
or 50 at most it might be ok.

Original issue reported on code.google.com by shouldab...@gmail.com on 3 Oct 2010 at 6:44

GoogleCodeExporter commented 8 years ago
I added a snippet from each Google search result.

To add snippets from the lucene.net index is rather tricky:
The content IS actually in the index and there is an additional library 
(lucene.net.contrib), with which you can access tools that would be useful to 
get content snippets. You can only install lucene.net.contrib with the nuget 
package manager, but then we have a version conflict with the old lucene.net 
version in our repo. We cannot simply remove that old version, as BzReader 
relies on that specific verion.

Using lucene.net.contrib we wouldn't have to search for the snippets ourselves 
by opening the files. That would help a lot. Any ideas?

Original comment by satiaher...@gmx.de on 5 Jun 2013 at 5:28

GoogleCodeExporter commented 8 years ago
See r80. We do find content snippets from local cache now, but often the 
results are not satisfactory.

Original comment by satiaher...@gmx.de on 24 Jun 2013 at 11:01

GoogleCodeExporter commented 8 years ago
Results are "OK" now. We do only find snippets from actual text content on the 
website, but sumetimes the sentences are not complete, or it starts with the 
"." from the previous sentence.

Anyway I think this is fine and therefore fixed.

Original comment by satiaher...@gmx.de on 26 Jun 2013 at 11:17