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

Grant Ingersoll commented on SOLR-2129:
---------------------------------------

bq. I can change the current hardcoded mapping mechanism using instead a simple 
mapping between UIMA extracted types/features and field names defined inside 
solrconfig.xml

Try to reuse the same syntax as the mapping in the ExtractingRequestHandler.

bq. A different option could be to develop a SolrCASConsumer component in UIMA 
(similar to Lucas [1], Lucene CAS Consumer) providing full control on how UIMA 
annotations and features can be mapped to Solr fields, but on UIMA side 

I've been struggling with these kinds of questions a lot lately.  That is, the 
marriage of two projects.  Where should the code go?  Setting up another ASF 
project is a pain in the amount of hoops to jump through.  Apache Labs doesn't 
cut it for a number of reasons.  Hosting on Github or Google Code is OK, but 
loses the ASF community aspect.  Sigh.

bq. Regarding point 2 the jars are already under contrib/uima/lib so I can 
modify the sample solrconfig.xml adding the proper <lib> tag.

Yep, exactly what I had in mind.

> Provide a Solr module for dynamic metadata extraction/indexing with Apache 
> UIMA
> -------------------------------------------------------------------------------
>
>                 Key: SOLR-2129
>                 URL: https://issues.apache.org/jira/browse/SOLR-2129
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Tommaso Teofili
>            Assignee: Robert Muir
>         Attachments: lib-jars.zip, SOLR-2129-asf-headers.patch, 
> SOLR-2129.patch
>
>
> Provide components to enable Apache UIMA automatic metadata extraction to be 
> exploited when indexing documents.
> The purpose of this is to get unstructured information "inside" a document 
> and create structured metadata (as fields) to enrich each document.
> Basically this can be done with a custom UpdateRequestProcessor which 
> triggers UIMA while indexing documents.
> The basic UIMA implementation of UpdateRequestProcessor extracts sentences 
> (with a tokenizer and an hidden Markov model tagger), named entities, 
> language, suggested category, keywords and concepts (exploiting external 
> services from OpenCalais and AlchemyAPI). Such an implementation can be 
> easily extended adding or selecting different UIMA analysis engines, both 
> from UIMA repositories on the web or creating new ones from scratch.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to