Mailing-List: contact dev-help@manifoldcf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@manifoldcf.apache.org
Date: Thu, 5 Jun 2014 12:18:02 +0000 (UTC)
From: "Karl Wright (JIRA)" <jira@apache.org>
To: dev@manifoldcf.apache.org
Message-ID: <JIRA.12718610.1401970630536.75669.1401970682580@arcas>
In-Reply-To: <JIRA.12718610.1401970630536@arcas>
References: <JIRA.12718610.1401970630536@arcas>
Subject: [jira] [Created] (CONNECTORS-955) Forced Metadata transformation
 connector would be a nice addition
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Karl Wright created CONNECTORS-955:
--------------------------------------

             Summary: Forced Metadata transformation connector would be a nice addition
                 Key: CONNECTORS-955
                 URL: https://issues.apache.org/jira/browse/CONNECTORS-955
             Project: ManifoldCF
          Issue Type: Task
    Affects Versions: ManifoldCF 1.7
            Reporter: Karl Wright
            Assignee: Karl Wright
             Fix For: ManifoldCF next


When transformations are available, forced metadata most naturally fits in as a standalone transformation connector.  We should develop one, and deprecate the Forced Metadata tab.

A larger issue is how to handle deprecations of features in the long run.  The choices are:

- feature continues to exist intact
- feature continues to exist, but there's something special you have to do to make it visible (i.e. in the UI)
- feature simply goes away at some point, breaking backwards compatibility


--
This message was sent by Atlassian JIRA
(v6.2#6252)