Hi Hemant,

Joining fields would be naturally something performed by the metadata
adjuster transformation connector. However, it does not currently
perform this function.



Sent from my Windows Phone
From: hemant Jain (JIRA)
Sent: 1/3/2015 10:04 AM
To: [email protected]
Subject: [jira] [Commented] (CONNECTORS-1130) Adding Key value pairs as
filter while crawling documentum content using ManifoldCf

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

hemant Jain commented on CONNECTORS-1130:
-----------------------------------------

Thanks Karl

I will test this and share the update shortly.

I need an additional info: Is there any way add some extra meta field
to the indexed data with value created by joining the value of two or
more existing meta fields or by manipulating the value of existing
meta field.

ie if we have field1 & field2 already in the repository data.
We want to add field3 with value "some contant string"+ value of
field1 + value of field2

Regards
Hemant

> Adding Key value pairs as filter while crawling documentum content using 
> ManifoldCf
> -----------------------------------------------------------------------------------
>
>                 Key: CONNECTORS-1130
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-1130
>             Project: ManifoldCF
>          Issue Type: New Feature
>          Components: Documentum connector
>            Reporter: hemant Jain
>            Assignee: Karl Wright
>             Fix For: ManifoldCF 1.9, ManifoldCF 2.1
>
>
> We are planning to replace Autonomy IDOL by SOLR search
> Currently I am using Autonomy Documentum connector to crawl my documentum 
> data.
> Input to this connector is DQL query with some filters in where clause. ie 
> meta data and value
> Is it possible to use key value pairs as filter while crawling the Documentum 
> content using ManifoldCf GUI?. Please suggest.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to