[
https://issues.apache.org/jira/browse/CONNECTORS-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167891#comment-16167891
]
Karl Wright commented on CONNECTORS-1356:
-----------------------------------------
[[email protected]], I asked mainly because this sounds a bit like
we want a more general framework-supported way of distinguishing between
content migration and indexing into search engines. Maybe repository
connectors can generate both forms of contentURI, and the output connector can
then choose which to use. Or maybe the output connector can "signal" the
repository connector as to what kind to create. I will have to think about
this further though.
> Initial implementation of the CMIS Output Connector
> ---------------------------------------------------
>
> Key: CONNECTORS-1356
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1356
> Project: ManifoldCF
> Issue Type: Task
> Components: CMIS Output Connector
> Reporter: Piergiorgio Lucidi
> Assignee: Piergiorgio Lucidi
> Fix For: ManifoldCF 2.9
>
> Attachments: CMISOutputConnectorSettings.png,
> ResultWithTimestampTreeOnTargetRepo.png, SourceRepoFolder.png
>
> Original Estimate: 672h
> Remaining Estimate: 672h
>
> After we have discussed about the possibility to have some output connector
> dedicated to migrate contents from a specific repo to another one, this is
> the first implementation for the CMIS protocol.
> The discussion is the following:
> http://mail-archives.apache.org/mod_mbox/manifoldcf-dev/201611.mbox/%3CCAEO2op-bjNv4xSTPwGN%3DV2v47Sy8d%2BwKNtd1RpV2PC85y_JAgw%40mail.gmail.com%3E
> The main scenario is migrate contents from any repository type to a
> CMIS-compliant repo.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
