[ 
https://issues.apache.org/jira/browse/SOLR-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13269080#comment-13269080
 ] 

Jan Høydahl commented on SOLR-3439:
-----------------------------------

I agree that this makes sense, and will not have any cost.

We could also make the Velocity GUI smart enough to detect whether the document 
is a "product" document, and output name, manufacturer, price, inStock etc.. OR 
whether it is a Tika doc or HTML in which case it prints the title, dynamic 
teaser, document size, document type/MIME etc.

Finally we could add some PDFs to the exampledocs folder!

Do you want to attempt a first patch?
                
> Add "content" field to example schema to make SolrCell easier to use out of 
> the box
> -----------------------------------------------------------------------------------
>
>                 Key: SOLR-3439
>                 URL: https://issues.apache.org/jira/browse/SOLR-3439
>             Project: Solr
>          Issue Type: Improvement
>          Components: contrib - Solr Cell (Tika extraction), Schema and 
> Analysis
>            Reporter: Jack Krupansky
>            Priority: Minor
>             Fix For: 4.0
>
>
> Currently, SolrCell is configured to map Tika "content" (the main body of a 
> document) to the "text" field which is the indexed-only (not stored) 
> catch-all for default queries. That searches fine, but doesn't show the 
> document content in the results, sometimes leading users to think that 
> something is wrong. Sure, the user can easily add the field (and this is 
> documented), but it would be a better user experience to have such a basic 
> feature work right out of the box without any config editing and without the 
> need for the user to read the fine print in the documentation.
> I propose that we add the "content" field to the example schema in the 
> section of fields already defined to support SolrCell metadata. It would be 
> stored and indexed.
> I further propose that a copyField be added for the "title", "description", 
> (and maybe a couple of others) and "content" fields to add them to the "text" 
> field for searching. Again, trying to improve the out of the box user 
> experience. It also simplifies testing - less setup.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to