manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wright (JIRA)" <>
Subject [jira] [Commented] (CONNECTORS-1130) Adding Key value pairs as filter while crawling documentum content using ManifoldCf
Date Sun, 28 Dec 2014 15:39:13 GMT


Karl Wright commented on CONNECTORS-1130:

where a_status='Effective' and (lower(dsm_doc_classification) <> 'secret'

Hi Hemant,

I think you may have misunderstood my question.  The attributes you seem to be limiting on
are "a_status" and "dsm_doc_classification".  My question was, how do I obtain the list of
attribute *names* to present for filtering, not how to present the attribute *values* for

Looking at the existing code, I already have the ability to obtain attribute names for each
given document type.  This is used presently to allow you to select the attributes to include
for metadata on a per-document-type basis.  But filtering could be added that would also be
specified per-document-type using similar logic.  Is this what you are looking for?  If not,
you still need to explain how to obtain a list of attribute names to filter on that would
apply to all document types.

> Adding Key value pairs as filter while crawling documentum content using ManifoldCf
> -----------------------------------------------------------------------------------
>                 Key: CONNECTORS-1130
>                 URL:
>             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

View raw message