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

Maciej Lizewski commented on CONNECTORS-552:
--------------------------------------------

My first idea was to store needed data in same structures as job specification 
(DocumentSpecification class). It could be done by extending jsp scripts that 
render specification page editjob.jsp (render additional tabs) and execute.jsp 
to handle this data and put it in specification object before (or after) call 
to jobs processSpecificationPost. Applying those parameters could be done in 
ingestDocument function of object providing IProcessActivity to 
processDocuments... that would give minimal impact on database structure (in 
fact no changes required).


                
> Forced solr attributes in job specification and/or configuration
> ----------------------------------------------------------------
>
>                 Key: CONNECTORS-552
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-552
>             Project: ManifoldCF
>          Issue Type: Improvement
>          Components: Framework crawler agent
>            Reporter: Maciej Lizewski
>
> Would be nice if there was a globally managed tab (like "connection" or 
> "scheduling") for job specification (or configuration) allowing to force some 
> solr attributes. It could look and work similar to "Solr Field Mapping" 
> allowing to specify name=value associations.
> I am thinking about such case:
> Index all documents from repository X, and set then "source" attribute to 
> "repository X". Then I could filter results to those that came from specified 
> source. But I think there can be other possibilities, like: index all 
> documents from windows share and set them field "client" to "Client X", 
> because all documents there are associated with one client and I would like 
> to have filters, facets on such field (and I cannot fetch such value from 
> documents because people never set meta tags...).
> Real life: I have three document sources: Samba share with some project 
> documents, internal wiki system, mantis bug tracker. I would like to query 
> Solr for "all documents from wiki, which contain phrase XXXX".

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to